Introduction to the ccNSO and Updates A. D. BADIEL ccNSO Liaison for AfTLD

1. Introduction to the ccNSO and Updates A. D. BADIEL ccNSO Liaison for AfTLD badiel@onatel.bf http://www.aftld.org http://www.ccnso.org Marrakesh, June 2006

2. Content • Brief overview of ICANN • The ccNSO • The cc Policy Development Process • Why should we join the ccNSO? • Miscellaneous

3. 1. Brief overview of ICANN • ICANN (Internet Corporation for Assigned Names and Numbers), non profit organization responsible for: • IP Ressources management (IANA) • Internet protocols and indentificators management • Top Level Domains (ccTLD, gTLD) management • Protocols identificators assignment • Root servers system management • Etc. • ICANN is composed of sub-organisations such as: • ALAC (At-Large Advisory Committee) : responsible for the Internet communities interests defense • ASO (Address Supporting Organization) : which is in charge of issues related to IP adresses • ccNSO (country code Name Supporting Organization):which adresses issues related to the country code Top Level Domains (ex. .sn, .fr, .za, etc.)

4. Brief overview of ICANN (c’d) • GAC (Government Advisory Committee): which represents the governments voices amoung the ICANN community • gNSO (generic Name Supporting Organization) which adresses issues related to generic Top Level Doamins (eg. .com, .org, .int, .tv, .info, etc.) • RSSAC (Root-Server System Advisory Committee) which adresses technical issues related to DNS roorservers • SSAC (Security and Stability Advisory Committee) which adresses issues related to the Security and Stability of the Internet • Etc. • There are some other organizations working with ICANN: • AfTLD, APTLD, LACTLD, CENTR, NATLD • IETF: Internet Engineering Task Force • IRTF: Internet ResearchTask Force • IAB: Internet Architecture Board • ISOC: Internet Society • W3C: World Wide Web Consortium • Etc.

5. Brief overview of ICANN (end) ICANN current organzation chart:

6. 2. The ccNSO 2.1. What’s the ccNSO? The ccNSO (country code Name Supporting Organization), one of the key sub-organizations of ICANN, is in charge of: • Developing global policies related to the ccTLDs • Making some proposals and recommendations to the ICANN Board on the ccTLDs • Nurturing consensus among the ccNSO community • Dealing with ccTLDs activities among the ICANN community • Coordinating ccTLDs related issues with the ICANN other Supporting Organizations • Etc.

7. The ccNSO (c’d) • The ccNSO is made of a council where all the 5 régions* of the world are represented by 3 councillors; The African councillors are: • Victor CIZA (Burundi) • Dr. Paulos B. NYIRENDA (Malawi) • Mohamed EL BASHIR (Sudan) *NB: The 5 regions are Africa, Asia, Europe, Latin America & North America • The ccNSO counts one liaison per continent: I am your liaison since June 2005 • The ccNSO also includes : • Committees • Working groups • Members • Regional organizations: AfTLD, CENTR, LACTLD, APTLD, NATLD

8. The ccNSO (c’d) 2.2. The Working Groups (WG): • Accountability Framework WG : • An informal initiative of the ccNSO with the purpose to develop a set of criteria for AF between ICANN and ccTLD managers • A statement to specify clearly what a ccTLD manager should be accountable to ICANN for and what ICANN should be accountable to the ccTLD manager for • A formalization of relationship between ICANN and ccTLD managers

9. The ccNSO (c’d) • Budget Fees to ICANN WG: • ICANN activities benefit to ccTLDs; eg. Stability and Security of the Internet (30% of ICANN budget): • IANA function services • DNSSEC deployment • IDNs • Root-servers management • Etc. • Assistance of ICANN in ccPDP: issue manager, liaison,… • ICANN requires some contribution from the ccTLDs • Report available at: http://www.icann.org/presentations/eva-ccnso-wellington-28mar06.pdf

10. The ccNSO (c’d) • GAC/ccNSO WG purpose: • Improve collaboration between the ccTLDs and the governments • Nurture consensus to avoid or even to solve conflicts between ccTLDs policies and national laws • ccNSO/IDN: • Study the impact of IDNs introduction on TLDs • Work jointly with the gNSO on IDN issues • M. EL BASHIR is the African councillor in that WG http://gnso.icann.org/issues/idn-tlds/issues-report-28may06.htm

11. The ccNSO (c’d) • IANA WG: • Goal: improve IANA services to ccTLDs • African representatives: M. El Bashir (.sd) & A. Levin (.za) • Scope of the WG: • Review IANA procedures for ccTLD zone file changes (except redelegations) • Recommandations to IANA on procedures improvements • Review of interaction mechanisms betw. ccTLDs & IANA • Review & improvement of documentation provided by IANA to the ccTLDs • Review & improvement of metrics used to monitor IANA sces performance • Docs available at: http://ianawg.ccnso.org/

12. The ccNSO (c’d) The ccNSO also has two WG on: • Secretariat & ccNSO fees : • Seeking for a good proposal to host the ccNSO secretariat • Studying the ccNSO functioning budget • The WSIS : • Following the World Summit on Information Society process for the ccNSO All the documents related to the ccNSO activities are available online at: http://www.ccnso.icann.org/

13. 3. The cc Policy Development Process (ccPDP) • A mechanism for the cccNSO council to develop policies by consensus amoung the ccNSO community and address them to the ICANN board for approval • A council recommendation is adopted if: • At least 50% of the members vote • Among the voters, if 66% vote in favor the recommendation • For instance, the ccNSO has initiated a ccPDP to improve the ICANN bylaws related to the ccTLDs (http://www.icann.org/general/bylaws.htm#IX); precisely concerning: • ICANN Bylaws Article IX : Country-Code Names Supporting Organization • Annex B: ccNSO Policy-Development Process • Annex C: the Scope of the ccNSO • The details of those recommendations are: • Council Recommendation 1: Issue A—NO BINDING POLICY FOR NON-MEMBERS OF THE CCNSO • Council Recommendation:Change Article IX Section 4.2 in accordance with Proposal A to resolve Issue A as defined in the Issues report.

14. Recommendations details (c’d) • Council Recommendation 2: Issue B—IANA SERVICES • Council Recommendation: Change Article IX Section 4.3 in accordance with Proposal B to resolve Issue B as definedin the Issues report • Council Recommendation 3:Issue C —AMENDMENT OF ARTICLE IX • Council Recommendation:Change Article IX Section 6 in accordance with Proposal C to resolve Issue C as definedin the Issues report • Council Recommendation 4: Issue D—SETTING BINDING POLICIES • Council Recommendation: Change Article IX Section 4.10 and Annex B sections 2, 3 and 15 in accordance withProposal D to resolve Issue D as defined in the Issues report.

15. Recommendations details (c’d) • Council Recommendation 5: Issue E—BINDING POLICIES OUTSIDE CCPDP • Council Recommendation: Change Article IX Section 1 in accordance with Proposal E to resolve Issue E as definedin the Issues report • Council Recommendation 6: Issue F—CHANGES TO CCPDP AND SCOPE • Council Recommendation: Change Article IX Section 6 in accordance with Proposal F to resolve Issue F as definedin the Issues report • Council Recommendation 7: Issue I—MEMBERSHIP QUORUM VOTING ON PDP RECOMMENDATIONS • Council Recommendation: Change Annex B Section 13 of the ICANN bylaws in accordance with Proposal I to resolveIssue I as defined in the Issues report.

16. Recommendations details (end) • Council Recommendation 8: Issue J—REJECTION OF PDP RECOMMENDATIONS BY THE ICANN BOARD • Council Recommendation: Change Annex B Section 15(2c) of the ICANN Bylaws in accordance with Proposal J to resolve Issue J as defined in the Issue Report • The member report PDP is available : http://www.ccnso.icann.org or at http://www.aftld.org

17. 4. Why should African ccTLDs join the ccNSO? • African ccTLDs face some problems such as: • DNS instability in some African countries. • DNS insecurity due to some attacks (eg. DDoS). • Lack of DNS root server in Africa (only a few mirrors in some countries) • Lack of IPv6 and DNSSEC experimentation at a great scale. • Lack of collaboration and cooperation between African ccTLDs. • Insufficiency of training. • ccNSO is an opportunity offered to African ccTLDs managers to: • Cooperate and exchange experience with other ccTLD managers • To be aware of any policy development related to ccTLDs • Take part in the Internet development process at a decision level • Contribute to the Internet development and stability in Africa and in the world • But first: participate in the AfTLD development! • To join the ccNSO:http://www.ccnso.org/about/Joining/Form.htm#

18. 5. Miscellaneous • A proposal was received from .tw to host the ccNSO secretariat; discussions are still going on • Victor Ciza (African ccNSO councillor) stepped down and was re-nominated for 3 years • The ICANN board adopted 7 of the 8 recommendations at the Wellington ICANN meeting • The remaining recommendation shall be adopted at this ICANN meeting: See http://ccnso.icann.org/pdps/bylaws-sup-rec-24may06.pdf

19. Thanks for your attention! http://www.ccNSO.org

20. Questions?