Jump to content

CcNSO: Difference between revisions

From ICANNWiki
Dustin Loup (talk | contribs)
No edit summary
Dustin Loup (talk | contribs)
No edit summary
Line 18: Line 18:
| linkedin        =  
| linkedin        =  
| twitter        =  
| twitter        =  
| keypeople      = [[Byron Holland]], Chair<br>[[Keith Davidson]], VIce-Chair<br>[[Giovanni Seppia]], Rep to [[NomCom]]<br>[[Bart Boswinkel]], Support and Adviser<br> [[Kristina Nordström]], Secretariat<br> [[Gabriella Schittek]], Contact and Coordination
| keypeople      =  
}}
}}
The '''Country Code Names Supporting Organization (ccNSO)''' is an advisory body within [[ICANN]] created by and for [[ccTLD]] managers. The ccNSO is a consortium of working groups and the ccNSO Council, and it works in conjunction with other supporting organizations and bodies within ICANN.  
The '''Country Code Names Supporting Organization (ccNSO)''' is a body within [[ICANN]] created by and for [[ccTLD]] managers. It provides a forum for topical issues relating to ccTLDs from a global perspective.<ref>[https://ccnso.icann.org ccNSO.icann.org]</ref>


As of August 2013, the ccNSO has 138 members, with Rwanda (.rw) being the latest to join.<ref>[http://www.icann.org/en/resources/policy/update/update-aug13-en.htm#3 Update Aug 13, ICANN.org] Published Aug 14, Retrieved Aug 14th</ref>
As of February 2018, the ccNSO has 165 members.


==Overview==
==Overview==
One of the biggest complaints with the structuring of ICANN's [[DNSO]] came from [[ccTLD]] registry operators, who felt that the [[SO|supporting organization]] was mainly concerned with gTLDs and that they needed their own separate organization. On October, 29, 2002, the country code managers emphasized their dissatisfaction by withdrawing completely from the DNSO.<ref>[http://www.ccwhois.org/elections/ Elections, ccWHois.org]</ref> This action prompted and expedited the replacement of the DNSO with the [[GNSO]], which was created in December, 2002. Work began on creating the [[Country Code Names Supporting Organization]] (ccNSO) in September, 2002, culminating in the creation of the ccNSO at [[ICANN Montreal]] in June, 2003.<ref>[http://law.bepress.com/context/uiuclwps/article/1097/viewcontent Law.Bepress.com]</ref>
The ccNSO provides a platform for nurturing consensus, technical cooperation, skill building and to facilitate for best practices for [[ccTLD]]s and their managers.


The ccNSO is the forum for global discussions and debates regarding issues related to ccTLDs.
The ccNSO also develops and recommends global policies to the ICANN Board for issues relating to ccTLDs. These processes are managed by the ccNSO Council and typically organized through Working Groups. The limited number of issues addressed by this policy development process include issues such as the introduction of Internationalised Domain Name (IDN) ccTLDs.


In order to nurture consensus, the ccNSO also offers a platform for technical cooperation and development of practical skills for [[ccTLD]] managers. The best practices among ccTLD managers are  shared within Working Group forums for improved development and cooperation. They also then share their recommendations with the [[ICANN Board]].<ref>[http://ccnso.icann.org/about CcNSO General Information]</ref>
The ccNSO provides ccTLD managers a way to work together with other stakeholders and communities, such as the Government Advisory Committee (GAC) or the Generic Names Supporting Organisation (GNSO).<ref>[http://ccnso.icann.org/about CcNSO General Information]</ref>


During the last few years of activity, the ccNSO has mainly focused and worked on the development of fast track [[ccTLD]] introduction in conjunction with [[IDN]]s, as well as the implementation of ccTLD changes according to [[ICANN]]'s bylaws.<ref>[http://ccnso.icann.org/about CcNSO focus]</ref>
==History==
One of the biggest complaints with the structuring of ICANN's [[DNSO]] came from [[ccTLD]] registry operators, who felt that the [[SO|supporting organization]] was mainly concerned with gTLDs and that they needed their own separate organization. On October, 29, 2002, the country code managers emphasized their dissatisfaction by withdrawing completely from the DNSO.<ref>[http://www.ccwhois.org/elections/ Elections, ccWHois.org]</ref> This action prompted and expedited the replacement of the DNSO with the [[GNSO]], which was created in December, 2002. Work began on creating the [[Country Code Names Supporting Organization]] (ccNSO) in September, 2002, culminating in the creation of the ccNSO at ICANN 17 in June, 2003.<ref>[http://law.bepress.com/context/uiuclwps/article/1097/viewcontent Law.Bepress.com]</ref>


===ccNSO Membership===
===ccNSO Membership===
In order to become a ccNSO member an application must be filled out; however, there are no fees or costs incurred by becoming a ccNSO member. Joining the ccNSO is easy but is limited to to ccTLD Managers, as per the [[ICANN Bylaws#Article 9: Country-Code Names Supporting Organization|ICANN Bylaws Article IX]]).<ref>[http://ccnso.icann.org/ccnso/applications CcNSO Membership Application]</ref>
Membership in the ccNSO is open to all ccTLD managers responsible for managing an ISO 3166 country-code top-level domain, but there are no fees or costs incurred by becoming a ccNSO member.<ref>[https://ccnso.icann.org/en/ccnso/applications ccNSO Membership]</ref>
 
The following rules apply:
# Membership of the ccNSO is open for all ccTLD managers responsible for managing an ISO 3166 country-code top-level domain;<ref>[http://ccnso.icann.org/about CcNSO Membership]</ref>
# Any organization managing an IDN ccTLD is eligible for ccNSO membership;
# Multiple memberships are not given to entities that work with synchronized ccTLDs.<ref>[http://aptld.org/file/2010oct/112c_Hiro_IDNatAPTLD.pdf CcNSO Membership Questions]</ref>
 
===ccNSO Responsibilities===
Besides supplying and providing a platform for technical cooperation and a forum for ccTLD related problems and issues, the ccNSO has other responsibilities, such as:
* Advising the [[ICANN Board]] on global policies related to ccTLD issues.
* Policy development through the ccNSO Council.
* Cooperate with ccTLD managers and stakeholders of ICANN;
* Organize effective working groups.


==ccNSO Council==
==ccNSO Council==
Line 81: Line 70:


'''Nominating Committee Appointees'''
'''Nominating Committee Appointees'''
* [[Ching Chiao]] (Term ends at [[Annual Meeting]] 2017)
* [[Christelle Vaval]] (Term ends at [[Annual Meeting]] 2018)
* [[Christelle Vaval]] (Term ends at [[Annual Meeting]] 2018)
* [[Jian Zhang]] (Term ends at [[Annual Meeting]] 2019)
* [[Jian Zhang]] (Term ends at [[Annual Meeting]] 2019)


The ccNSO also contributes one member to [[ICANN]]'s NomCom, this position is currently held by [[Giovanni Seppia]].<ref>[http://nomcom.icann.org/members-2011.htm NomCom.ICANN.org]</ref>
The ccNSO also contributes one member to [[ICANN]]'s NomCom, this position is currently held by [[Jörg Schweiger]].<ref>[https://www.icann.org/nomcom2017/#members ICANN's NomCom]</ref>


==References==
==References==

Revision as of 11:17, 14 February 2018

Industry: ccTLDs
Founded: 2003
Website: CCNSO.ICANN.org

The Country Code Names Supporting Organization (ccNSO) is a body within ICANN created by and for ccTLD managers. It provides a forum for topical issues relating to ccTLDs from a global perspective.[1]

As of February 2018, the ccNSO has 165 members.

Overview[edit | edit source]

The ccNSO provides a platform for nurturing consensus, technical cooperation, skill building and to facilitate for best practices for ccTLDs and their managers.

The ccNSO also develops and recommends global policies to the ICANN Board for issues relating to ccTLDs. These processes are managed by the ccNSO Council and typically organized through Working Groups. The limited number of issues addressed by this policy development process include issues such as the introduction of Internationalised Domain Name (IDN) ccTLDs.

The ccNSO provides ccTLD managers a way to work together with other stakeholders and communities, such as the Government Advisory Committee (GAC) or the Generic Names Supporting Organisation (GNSO).[2]

History[edit | edit source]

One of the biggest complaints with the structuring of ICANN's DNSO came from ccTLD registry operators, who felt that the supporting organization was mainly concerned with gTLDs and that they needed their own separate organization. On October, 29, 2002, the country code managers emphasized their dissatisfaction by withdrawing completely from the DNSO.[3] This action prompted and expedited the replacement of the DNSO with the GNSO, which was created in December, 2002. Work began on creating the Country Code Names Supporting Organization (ccNSO) in September, 2002, culminating in the creation of the ccNSO at ICANN 17 in June, 2003.[4]

ccNSO Membership[edit | edit source]

Membership in the ccNSO is open to all ccTLD managers responsible for managing an ISO 3166 country-code top-level domain, but there are no fees or costs incurred by becoming a ccNSO member.[5]

ccNSO Council[edit | edit source]

The ccNSO is overseen by its council, which is in charge of coordinating the functions of the larger group and managing its policy recommendations. The councillors lead many ccNSO discussions and aim to develop official community positions for their board recommendations. Between the 3 ICANN conferences the council makes a point of meeting via conference calls.

There are 3 councillors per global region, and also 3 councillors chosen by ICANN's NomCom. A term on the Council lasts three years, and the election cycle is staggered so that each year there are a total of 18 councillors representing 5 regions. The additional 3 chosen by the NomCom are chosen to represent a business perspective from outside the ccTLD community. All councillors are able to be re-appointed following the conclusion of their term.[6]

Councillors[edit | edit source]

Current councillors include:[7]

Africa:

Asia Pacific

Europe

Latin America

North America

Nominating Committee Appointees

The ccNSO also contributes one member to ICANN's NomCom, this position is currently held by Jörg Schweiger.[8]

References[edit | edit source]