Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
  • Category: (replace this text with one of the following categories: Administration/Budget, ccTLD, gTLD, IP, ICANN Structure, International Agreement) ICANN Structures
  • Topic: ccNSOTopic: (replace this text with a keywords from title)
  • Board meeting date: 6 March 2004
  • Resolution number: 04.25, 04.26, 04.27, 04.28
  • URL for Board minutes/resolution: http://www.icann.org/en/minutes/rome-resolutions-06mar04.htm
  • Status: (replace this text with: Completed, Ongoing, Suspended)

Summary
(replace this text with the a one-sentence summary of the resolution) Board recognizes the the announcement of the constituted ccNSO as posted on 1 March 2004 and directs staff to post the proposed Bylaw amendments for public comment.

Text
Whereas, beginning in March 2002 the ICANN community engaged in intensive discussion, led by the Committee on ICANN Evolution and Reform (ERC), concerning reforms to ICANN's procedures and organizational structures;

Whereas, one important goal of the 2002 ICANN reform process was development of a Country-Code Names Supporting Organization (ccNSO);unmigrated-wiki-markup

Whereas, the Board resolved \ [03.106\] to adopt the amendments to the bylaws shown in Appendix A to these minutes;unmigrated-wiki-markup

Whereas, the Board resolved that there be a ccNSO Launching Group, with the authority to solicit additional ccTLD managers to join with the members of such Launching Group to eventually comprise the ccNSO, to be deemed constituted once thirty members joined \ [03.109\], and the authority to establish a schedule and procedures for the selection of the initial ccNSO Council \ [03.110\]; andunmigrated-wiki-markup

Whereas, the Board further resolved \ [03.111\] that such Launching Group shall not have the authority (a) to initiate a ccPDP or (b) otherwise engage in development of substantive policies, or (c) select on behalf of the ccNSO any director or observer or other participant in any ICANN body;

Whereas, the ccNSO Launching Group announced on 1 March 2004 the formation of the ccNSO, with participation of over 30 ccTLD managers with at least four within each Geographic Region.

...

Whereas, the ccNSO Launching Group has provided to staff additional language changes of the ccNSO Bylaws for clarification purposes, and staff has reviewed and approved the additional ccNSO Bylawsunmigrated-wiki-markup

Resolved, \ [04.25\] the Board recognizes and warmly welcomes the announcement of the constituted ccNSO as posted on 1 March 2004;unmigrated-wiki-markup

Resolved, \ [04.26\] the Board requests that staff post the proposed clarifications to the ccNSO Bylaws on the ICANN Website for public comment;unmigrated-wiki-markup

Resolved, \ [04.27\] the Board agrees to consider those proposed ccNSO Bylaws during the next Board Meeting.unmigrated-wiki-markup

Resolved, \ [04.28\] the Board warmly thanks the ccNSO Launching Group for their hard work and looks forward to having the ccNSO Council meet at the next ICANN meeting.

Implementation Actions

  • (replace this text with specific Action Item)
    • Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)
    • Due date: (replace this text with Due Date)
    • Completion date: (replace this text with Date action was implemented, if different from due date)
  • (replace this text with specific Action Item)
    • Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)
    • Due date: (replace this text with Due Date)
    • Completion date: (replace this text with Date action was implemented, if different from due date)

Other Related Resolutions

  • (replace this text with links to related resolutions)

Additional Information

...

  • Post proposed corrections to Bylaws on the ICANN website for public comment.
    • Responsible entity: ICANN staff
    • Due date: None provided
    • Completion date: 11 March 2004
  • Consider proposed ccNSO Bylaws during next Board Meeting. 
    • Responsible entity: Board
    • Due date: 19 April 2004
    • Completion date: 19 April 2004

Other Related Resolutions

Additional Information

Explanatory text does not modify or override Resolutions.  See Board Resolutions Page for more information.

Note: The "Add Comment" box below is for sharing information about implementation of this resolution. Off-topic comments will be removed.