Page History
Item | Description | Bylaw section | Bylaw text | Issue | Bylaw type | Change mechanism | Priority | Change time |
|---|---|---|---|---|---|---|---|---|
1. | Definition of ccNSO members. Identified by PDP WG Retirement. Additional issue, reference on overall IDN PDP WG. See letter chair PDP WG: https://ccnso.icann.org/en/ about/deerhake-to-council- 13jan19-en.pdf | Article 10.4 | For purposes of this Article 10, a ccTLD manager is the organization or entity responsible for managing an ISO 3166 country-code top- level domain, or under any later variant, for that country-code top-level domain. | Highlighted part does not make sense. No consultation ccNSO. Original: For purposes of this Article, a ccTLD manager is the organization or entity responsible for managing an ISO 3166 country-code top- level domain and referred to in the IANA database under the current heading of "Sponsoring Organization", or under any later variant, for that country-code top- level domain. Underlying issue: reference to Sponsoring Organisation as included in IANA database | S | Letter to the Board, requesting change. | High (urgent and important). | Letter to Board requesting change has been send. Response with questions received. Response has been send in February 2021 |
| 2 | Voting mechanism in Article 10 and Annex B to be reviewed. if one organization manages two ccTLDs from different Territories | Article 10.4 (a), Annex B, 13 | Updated text section 10.4 (a). Annex B: "the vote of the members shall be electronic and members votes" | Some organizations manage two or more ccTLDs of different countries. Should voting be limited to one vote per entity? to ensure parity of members who run multiple ccTLDs. Note, Organizations or entities who run multiple IDN ccTLDs related to one (1) country or territory will be at a maximum have one (1) vote | S | Bylaw change | M | |
3. | Reference to non-ccNSO member for IFRT. See letters Council to the Board: https://ccnso.icann.org/sites /default/files/field- attached/sataki-to-chalaby- et-al-06dec18-en.pdf .
Issue not only relevant for current and future IFRTs, also for Special IFR. | Section 18.7 (a) & (b)
Section 18.12 (b) referencin g section 18.7 (a) and (b) | One non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO, appointed by the ccNSO | With growing number of members, attracting non- ccNSO member becomes difficult, if not impossible. See overview of membership as well | F | Request Board to change after consultation of community. Bylaw change must be supporte by the Empowered Community | Medium (important, needs to be resolved in next 2 years) | Letter to the Board send. Public comment closed 16 July 2019. Completed. Bylaw has been changed 28 November 2019 |
4. | Reference to non-ccNSO member for Special Cross- community WG for separation | Section 19.5 SCWG Compositi on | One non-ccNSO ccTLD representative who is associated with a ccTLD registry operator that is not a representative of the ccNSO, appointed by the ccNSO; | With growing number of members, attracting non- ccNSO member has proven to be very difficult, if not impossible. In event of SCWG high risk | F | Request Board to change after consultation of community | Medium (important, needs to be resolved in next 2 years) | |
5. | Change of reference in Section 4.3 ( IRP) to delegation and Redelgation | Section 4.3 ( c ) (ii) | Notwithstanding any other provision in this Section 4.3, the IRP's scope shall exclude all of the following:
(ii) Claims relating to ccTLD delegations and re- delegations. … | Lamguage in Bylaws is not consistent with language FoI and IANA NAmng Function Contract. Should be: Delegations, transfers, revocations and retirement ( after adoption of the policy) | F | Request Board to change after consultation of community | Medium (important, needs to be resolved when ccPDP 3 is submitted to the Board or as part of it as recommen dation by ccPDP 2 WG 2) | |
6. | Bylaw require ccNSO AGM. To date never conducted. | Section 10. 4 (f) | There shall be an annual meeting of ccNSO members, which shall be coordinated by the ccNSO Council. Annual meetings should be open for all to attend, and a reasonable opportunity shall be provided for ccTLD managers that are not members of the ccNSO as well as other non-members of the ccNSO to address the meeting. To the extent practicable, annual meetings of the ccNSO members shall be held in person and should be held in conjunction with meetings of the Board, or of one or more of ICANN's other Supporting Organizations. | Recurring point of discussion also contained in the 2004 Rules. To date no need to designate one of the meeting as AGM. ccNSO is NOT a member organization for example like an association. | S | Request Board to change after consultation of community | Low. Recurring point of discussion also contained in the Bylaws. | Suggestion: By the time 2004 Rules are updated and adopted. |
7. | Date ccNSO members elected Councillors take their seat | Section 10.3 (d) i | The regular term of each ccNSO Council member shall begin at the conclusion of an ICANN annual meeting and shall end at the conclusion of the third ICANN annual meeting thereafter | Practice has evolved since inception of the creation of the ccNSO that elected Councillors take their seat at the first meeting of the calander year (Commuity Forum) | S | Request Board to change after consultation of community | Low. Recurring point of discussion also contained in the Bylaws. | Suggestion: By the time 2004 Rules are updated and adopted. |
