Domain Name Supporting Organization: Difference between revisions
Marked this version for translation |
→Structure: +ref |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Prior to 2003, the '''Domain Name Supporting Organization''' ('''DNSO''') was one of the three [[ICANN]] [[SO|supporting organizations]] called for under the [[ICANN Bylaws]]<ref>[http://www.dnso.org/ dnso.org]</ref>, being formally established in March 31, 1999<ref>https://www.icann.org/en/system/files/files/timeline-icann-in-history-28sep23-en.pdf</ref>. It has since been replaced by the [[GNSO|Generic Names Supporting Organization]] (GNSO).<ref>[http://www.apricot.net/apricot99/dnso/cfp-singapore.html apricot.net]</ref> The DNSO advised the ICANN Board about handling issues related to the [[DNS|Domain Name System]] (DNS). Its primary agenda was to discuss how and when to expand the Internet by adding new [[TLD]]s beyond [[.com]].<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | |||
Prior to 2003, the '''Domain Name Supporting Organization''' ('''DNSO''') was one of the three [[ICANN]] [[SO|supporting organizations]] called for under the [[ICANN Bylaws]] | |||
The DNSO chair at the time of restructuring, [[Thomas Roessler]], wrote "At some point of time between 9:10 and 9:40 a.m. Amsterdam time on Sunday [15 December 2002], the DNSO ceased to be (and will, perhaps not unlike a phoenix from the ashes, become the GNSO).." His entire farewell email can be found [http://www.dnso.org/clubpublic/ga/Arc11/msg01325.html here]. | The DNSO chair at the time of restructuring, [[Thomas Roessler]], wrote "At some point of time between 9:10 and 9:40 a.m. Amsterdam time on Sunday [15 December 2002], the DNSO ceased to be (and will, perhaps not unlike a phoenix from the ashes, become the GNSO).." His entire farewell email can be found [http://www.dnso.org/clubpublic/ga/Arc11/msg01325.html here]. | ||
== Structure == | == Structure == | ||
The DNSO was comprised of two bodies: the Names Council (NC), which was made up of elected representatives from the DNSO Constituencies, and the General Assembly (GA), made up of all interested entities and individuals.<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | The DNSO was comprised of two bodies: the Names Council (NC), which was made up of elected representatives from the DNSO Constituencies, and the General Assembly (GA), made up of all interested entities and individuals.<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | ||
One of the biggest complaints with the structuring of the DNSO came from [[ccTLD]] registry operators, who felt that the SO was mainly concerned with gTLDs and that they needed their own separate organization. On October | One of the biggest complaints with the structuring of the DNSO came from [[ccTLD]] registry operators, who felt that the SO 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 transition to 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 - Montreal]] in June 2003.<ref>[http://law.bepress.com/context/uiuclwps/article/1097/viewcontent Law.Bepress.com]</ref> | ||
=== DNSO Constituencies === | === DNSO Constituencies === | ||
The initial constituencies of the DNSO were as follows<ref>https://www.media-visions.com/icann-dnso.htm#Responsibilities</ref>: | |||
The initial constituencies of the DNSO were as follows: | |||
* [[ccTLD]] [[Registry|Registries]] | * [[ccTLD]] [[Registry|Registries]] | ||
* [[gTLD]] Registries | * [[gTLD]] Registries | ||
| Line 22: | Line 18: | ||
* [[Registrar]]s<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | * [[Registrar]]s<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | ||
== DNSO Process == | == DNSO Process == | ||
# The DNSO served in an advisory role to the [[ICANN Board]] and provided the Board with substantive policies related to the [[DNS]]. | # The DNSO served in an advisory role to the [[ICANN Board]] and provided the Board with substantive policies related to the [[DNS]]. | ||
# The DNSO first needed to reach a consensus before submitting requests to the Board. | # The DNSO first needed to reach a consensus before submitting requests to the Board. | ||
# All the recommendations made by the DNSO to the Board were made open to all [[SO|Supporting Organizations]] (SOs) so that they could comment. | # All the recommendations made by the DNSO to the Board were made open to all [[SO|Supporting Organizations]] (SOs) so that they could comment. | ||
The ICANN Board accepted the recommendations of the DNSO only if: | The ICANN Board accepted the recommendations of the DNSO only if: | ||
* The policy is in the interest of the Corporation and helps to further the purposes of the Corporation | * The policy is in the interest of the Corporation and helps to further the purposes of the Corporation | ||
* The policy is consistent with the Articles and Bylaws of the Corporation | * The policy is consistent with the Articles and Bylaws of the Corporation | ||
| Line 38: | Line 31: | ||
* The policy is not opposed by other Supporting Organizations | * The policy is not opposed by other Supporting Organizations | ||
The Board would not adopt any recommendation by the DNSO unless the votes, excluding those of the DNSO-selected Directors, are in favor of adoption by the Board. If the Board is not satisfied with a recommendation then it can return it to the DNSO for further consideration, citing the reasons for its declination. If the DNSO still fails to make the policy acceptable, then the ICANN Board may initiate, modify or amend and then approve the recommendation.<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | The Board would not adopt any recommendation by the DNSO unless the votes, excluding those of the DNSO-selected Directors, are in favor of adoption by the Board. If the Board is not satisfied with a recommendation then it can return it to the DNSO for further consideration, citing the reasons for its declination. If the DNSO still fails to make the policy acceptable, then the ICANN Board may initiate, modify or amend and then approve the recommendation.<ref name="link2">[http://www.media-visions.com/icann-dnso.htm#Responsibilities media-visions.com]</ref> | ||
== References == | == References == | ||
{{reflist}} | {{reflist}} | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[category: ICANN Bodies]] | [[category: ICANN Bodies]] | ||
[[Category:Articles with Chinese]] | [[Category:Articles with Chinese]] | ||
__NOTOC__ | __NOTOC__ | ||
Latest revision as of 18:29, 28 August 2024
Prior to 2003, the Domain Name Supporting Organization (DNSO) was one of the three ICANN supporting organizations called for under the ICANN Bylaws[1], being formally established in March 31, 1999[2]. It has since been replaced by the Generic Names Supporting Organization (GNSO).[3] The DNSO advised the ICANN Board about handling issues related to the Domain Name System (DNS). Its primary agenda was to discuss how and when to expand the Internet by adding new TLDs beyond .com.[4]
The DNSO chair at the time of restructuring, Thomas Roessler, wrote "At some point of time between 9:10 and 9:40 a.m. Amsterdam time on Sunday [15 December 2002], the DNSO ceased to be (and will, perhaps not unlike a phoenix from the ashes, become the GNSO).." His entire farewell email can be found here.
Structure[edit | edit source]
The DNSO was comprised of two bodies: the Names Council (NC), which was made up of elected representatives from the DNSO Constituencies, and the General Assembly (GA), made up of all interested entities and individuals.[4]
One of the biggest complaints with the structuring of the DNSO came from ccTLD registry operators, who felt that the SO 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.[5] This action prompted and expedited the transition to 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 - Montreal in June 2003.[6]
DNSO Constituencies[edit | edit source]
The initial constituencies of the DNSO were as follows[7]:
- ccTLD Registries
- gTLD Registries
- Commercial and Business entities
- Non-Commercial Domain Name Holders
- Internet Service Providers (ISPs) and Connectivity Providers
- Trademark
- Registrars[4]
DNSO Process[edit | edit source]
- The DNSO served in an advisory role to the ICANN Board and provided the Board with substantive policies related to the DNS.
- The DNSO first needed to reach a consensus before submitting requests to the Board.
- All the recommendations made by the DNSO to the Board were made open to all Supporting Organizations (SOs) so that they could comment.
The ICANN Board accepted the recommendations of the DNSO only if:
- The policy is in the interest of the Corporation and helps to further the purposes of the Corporation
- The policy is consistent with the Articles and Bylaws of the Corporation
- The policy was framed through an open and fair process
- The policy is not opposed by other Supporting Organizations
The Board would not adopt any recommendation by the DNSO unless the votes, excluding those of the DNSO-selected Directors, are in favor of adoption by the Board. If the Board is not satisfied with a recommendation then it can return it to the DNSO for further consideration, citing the reasons for its declination. If the DNSO still fails to make the policy acceptable, then the ICANN Board may initiate, modify or amend and then approve the recommendation.[4]