Difference between revisions of "ICANN Bylaws"

From ICANNWiki
Jump to navigation Jump to search
Line 12: Line 12:
 
Define $dx = 25 # shift text to right side of bar
 
Define $dx = 25 # shift text to right side of bar
 
Define $now= 10/01/2021
 
Define $now= 10/01/2021
 +
 +
Colors
 +
  id:og color:skyblue legend:Original Bylaws
 +
  id:evo color:limegreen legend:Evolution & Reform
 +
  id:gnso color:lavender legend:GNSO 1 Amendments
 +
  id:gtld color:tan1 legend:New gTLD Program
 +
  id:iana color:coral legend:IANA Functions Transition
 +
  id:squo color:drabgreen legend:Current Bylaws
  
 
PlotData=
 
PlotData=
 
   bar:Amendments width:30 mark:(line,white) align:left fontsize:L
 
   bar:Amendments width:30 mark:(line,white) align:left fontsize:L
  
   from:10/01/1998 till:12/15/2002  color:skyblue shift:($dx,0) text:"Original Bylaws"
+
   from:10/01/1998 till:12/15/2002  color:og shift:($dx,0)
   from:12/15/2002 till:08/27/2009  color:lavender shift:($dx,0) text:"[[2002 Evolution and Refom Process|2002 Evolution & Reform]]
+
  at:10/01/1998 shift:($dx,-5) text:"ICANN Formed"
 +
   from:12/15/2002 till:08/27/2009  color:evo shift:($dx,0)
 +
  at:12/15/2002 shift:($dx,-5) text:"[[2002 Evolution and Reform Process|Evolution & Reform Amendments]]"
 
   at:06/26/2003 shift:($dx,-5) text:"[[ccNSO|Amended to form ccNSO]]"
 
   at:06/26/2003 shift:($dx,-5) text:"[[ccNSO|Amended to form ccNSO]]"
 
   at:02/28/2006 shift:($dx,-5) text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"
 
   at:02/28/2006 shift:($dx,-5) text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"
   at:02/15/2008 shift:($dx,0) text:"Changes to At-Large Structure Applications"
+
   at:02/15/2008 shift:($dx,-5) text:"Changes to At-Large Structure Applications"
   from:08/27/2009 till:04/10/2012  color:limegreen shift:($dx,0) text:"[[First GNSO Organizational Review|GNSO 1 Amendments]]"
+
   from:08/27/2009 till:04/10/2012  color:gnso 
   at:09/30/2009 shift:($dx,0) text:"Organizational Reviews every 5 years"
+
  at:08/27/2009 shift:($dx,-5) text:"[[First GNSO Organizational Review|GNSO 1 Amendments]]"
   at:10/28/2010 shift:($dx,0) text:"Creation of At-Large Director seat"
+
   at:09/30/2009 shift:($dx,-5) text:"Organizational Reviews every 5 years"
   at:12/08/2011 shift:($dx,0) text:"New Annex A - GNSO PDP"
+
   at:10/28/2010 shift:($dx,-5) text:"Creation of At-Large Director seat"
   from:04/10/2012 till:05/27/2016 color:tan1 shift:($dx,0) text:"[[New gTLD Program]]"
+
   at:12/08/2011 shift:($dx,-5) text:"New Annex A - GNSO PDP"
   at:07/30/2014 shift:($dx,0) text:"Changes to GAC-related provisions"
+
   from:04/10/2012 till:05/27/2016 color:gtld
   from:05/27/2016 till:09/08/2019  color:coral shift:($dx,0) text:"[[IANA Functions Stewardship Transition|IANA Transition]]"
+
  at:04/10/2012 shift:($dx,-5) text:"[[New gTLD Program]]"
   from:09/08/2019 till:$now color:drabgreen shift:($dx,0) text:"Current Bylaws"
+
   at:07/30/2014 shift:($dx,-5) text:"Changes to GAC-related provisions"
 +
   from:05/27/2016 till:09/08/2019  color:iana
 +
  at:05/27/2016 shift:($dx,-5) text:"[[IANA Functions Stewardship Transition|IANA Transition Amendments]]"
 +
   from:09/08/2019 till:$now color:squo shift:($dx,0) text:"Current Bylaws"
 
    
 
    
 
    
 
    

Revision as of 20:03, 30 September 2021

EasyTimeline 1.90


Timeline generation failed: 8 errors found
Line 11: Colors

- Invalid statement. No '=' found.


Line 12: id:og color:skyblue legend:Original Bylaws

- New command expected instead of data line (= line starting with spaces). Data line(s) ignored.

 



Line 20: from:10/01/1998 till:12/15/2002 color:og shift:(25,0)

- PlotData invalid. Attribute 'color' has unknown color 'og'.

 Specify command 'Color' before this command.



Line 22: from:12/15/2002 till:08/27/2009 color:evo shift:(25,0)

- PlotData invalid. Attribute 'color' has unknown color 'evo'.

 Specify command 'Color' before this command.



Line 27: from:08/27/2009 till:04/10/2012 color:gnso

- PlotData invalid. Attribute 'color' has unknown color 'gnso'.

 Specify command 'Color' before this command.



Line 32: from:04/10/2012 till:05/27/2016 color:gtld

- PlotData invalid. Attribute 'color' has unknown color 'gtld'.

 Specify command 'Color' before this command.



Line 35: from:05/27/2016 till:09/08/2019 color:iana

- PlotData invalid. Attribute 'color' has unknown color 'iana'.

 Specify command 'Color' before this command.



Line 37: from:09/08/2019 till:10/01/2021 color:squo shift:(25,0) text:"Current Bylaws"

- PlotData invalid. Attribute 'color' has unknown color 'squo'.

 Specify command 'Color' before this command.



The Bylaws for Internet Corporation for Assigned Names And Numbers is the foundational governance document for ICANN.[1] The bylaws define the mission of ICANN, establish rules for the structure and operation of the SOs and ACs, and establish mechanisms for community engagement with the ICANN organization. The bylaws have undergone numerous revisions over the course of ICANN's history in response to reform efforts, policy development processes, and recommendations from organizational and specific reviews.

The current version of the ICANN Bylaws can be found here.

Evolution Over Time

Initially, ICANN's bylaws were similar to many young nonprofit organizations, with some specialized articles. Provisions that specified procedural and operational components of the organization, that might otherwise be defined by a statutory default, were included.[2] The original bylaws anticipated the formation and operation of three supporting organizations: the Address Supporting Organization, the Domain Name Supporting Organization, and the Protocol Supporting Organization. In addition, the bylaws made it possible for the board to form and empower committees, and set the stage for three advisory committees to be formed: the Government Advisory Committee, the Root Server System Advisory Committee, and an advisory committee on membership, until such time as the question of At-large representation was answered satisfactorily.[2] As events arose and the ICANN community became more engaged with policy development and review functions, the bylaws grew and changed to more specifically describe and define ICANN's role, obligations, and process.

Mission and Core Values

Prior to 2002, the bylaws did not contain any mention of the organization's mission, or its core values.[2] During the 2002 Evolution and Reform Process, the Evolution and Reform Committee (ERC) recommended the inclusion of these sections to enshrine the guiding principles and goals of ICANN in its governance documents. At the time of the December 2002 omnibus amendments to the bylaws, the mission and core values sections were added as the new Article 1.[3] The organization's mission statement was defined within the narrow scope of coordination and protection of "Internet's unique identifier systems." The article specified:

In particular, ICANN:

1. Coordinates the allocation and assignment of the three sets of unique identifiers for the Internet, which are: a. Domain names (forming a system referred to as "DNS"); b. Internet protocol ("IP") addresses and autonomous system ("AS") numbers; and c. Protocol port and parameter numbers.
2. Coordinates the operation and evolution of the DNS root name server system.

3. Coordinates policy development reasonably and appropriately related to these technical functions.[3]

This mission statement remained the same until the IANA Functions Transistion, which among other things incorporated the Affirmation of Commitments into the bylaws, and anticipated the creation of a subsidiary entity under ICANN to manage IANA functions oversight. In October of 2016, Article 1 was amended to describe the broadened scope of ICANN's Mission:

Specifically, ICANN:

(i) Coordinates the allocation and assignment of names in the root zone of the Domain Name System ("DNS") and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains ("gTLDs"). In this role, ICANN's scope is to coordinate the development and implementation of policies:

*For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and *That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet's unique names systems.

The issues, policies, procedures, and principles addressed in Annex G-1 and Annex G-2 with respect to gTLD registrars and registries shall be deemed to be within ICANN's Mission.

(ii) Facilitates the coordination of the operation and evolution of the DNS root name server system.

(iii) Coordinates the allocation and assignment at the top-most level of Internet Protocol numbers and Autonomous System numbers. In service of its Mission, ICANN (A) provides registration services and open access for global number registries as requested by the Internet Engineering Task Force ("IETF") and the Regional Internet Registries ("RIRs") and (B) facilitates the development of global number registry policies by the affected community and other related tasks as agreed with the RIRs.

(iv) Collaborates with other bodies as appropriate to provide registries needed for the functioning of the Internet as specified by Internet protocol standards development organizations. In service of its Mission, ICANN's scope is to provide registration services and open access for registries in the public domain requested by Internet protocol development organizations.[4]

The October 2016 amendment also added some provisos and clarifications regarding the mission. Article 1.1(b) through (d) state: that ICANN shall not act outside its mission; that ICANN has no governmental regulatory authority and shall not regulate the use of or content transmitted via the Internet's unique identifier system beyond the scope described in Article 1.1(a); that no registry or registrar can challenge the validity of its agreement with ICANN on the basis that the contract is contrary to ICANN's mission; and similarly, that no party can claim that ICANN's 2016-2020 strategic plan is contrary to its mission.[4]

References

  1. ICANN.org - Bylaws(English)
  2. 2.0 2.1 2.2 ICANN.org Archive - Original Bylaws, November 6, 1998
  3. 3.0 3.1 ICANN.org Bylaws Archive - Article 1, as amended December 15, 2002
  4. 4.0 4.1 ICANN.org Bylaws Archive - Bylaws, as amended October 1, 2016