Jump to content

ICANN Bylaws: Difference between revisions

From ICANNWiki
Caterina (talk | contribs)
No edit summary
JP (talk | contribs)
 
(118 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TOC right}}
<timeline>
The '''ICANN Bylaws''' are the internal rules set forth for [[ICANN]] by the [[ICANN Board]].
ImageSize  = width:600 height:1200
PlotArea  = left:50 right:50 bottom:20 top:20
AlignBars  = early


The Bylaws in full can be found [http://www.icann.org/en/general/bylaws.htm here]. A summary of each section is as follows:
DateFormat = mm/dd/yyyy
Period    = from:01/01/1998 till:12/31/2022
TimeAxis  = orientation:vertical
ScaleMajor = unit:year increment:1 start:1998
ScaleMinor = unit:month increment:1 start:01/01/1998
Legend = left:400 top:1000 columns:1
Define $dx = 25 # shift text to right side of bar
Define $now= 10/01/2021 #Keep updated!


====Article 1. Mission and Core Values====
Colors=
* 1.1 Mission
  id:og value:skyblue legend:Original_Bylaws
: To coordinate the global Internet's system of identifiers (domain names/[[DNS]], [[IP Addresses]], [[AS]] numbers, and protocol port and parameter numbers), and ensure that the system is stable and secure.
  id:evo value:limegreen legend:Evolution_&_Reform
* 1.2 Core Values
  id:gnso value:lavender legend:GNSO_1_Amendments
:
  id:gtld value:tan1 legend:New_gTLD_Program
  id:iana value:coral legend:IANA_Functions_Transition
  id:squo value:drabgreen legend:Current_Bylaws


====Article 2. Powers====
PlotData=
* 2.1 General Powers
  bar:Amendments width:30 mark:(line,white) align:left fontsize:M
: The [[ICANN Board|Board]] shall either exercise or observe the exercising of ICANN's powers. It acts with a majority vote.
* 2.2 Restrictions
: ICANN is not a domain name [[registry]], [[registrar]], or [[IP]] address registry.
* 2.3 Non-Discriminatory Treatment
: ICANN shall not discriminate against any party.


====Article 3. Transparency====
  from:10/01/1998 till:12/15/2002  color:og shift:($dx,0)
* 3.1 Purpose
  at:10/01/1998 shift:($dx,-5) text:"ICANN Formed"
: ICANN and its constituent bodies shall act in an open, transparent, and fair manner.
  from:12/15/2002 till:08/27/2009  color:evo shift:($dx,0)
* 3.2 Website
  at:12/15/2002 shift:($dx,-5) text:"[[2002 Evolution and Reform Process|Evolution & Reform Amendments]]"
: ICANN shall maintain a publicly accessible website
  at:06/26/2003 shift:($dx,-5) text:"[[ccNSO|Amended to form ccNSO]]"
* 3.3 Manager of Public Information
  at:02/28/2006 shift:($dx,-5) text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"
: There shall be a staff position titled Manager of Public Information, whose duty it is to coordinate the various aspects of public participation, under direction of the President.
  at:02/15/2008 shift:($dx,-5) text:"Changes to At-Large Structure Applications"
* 3.4 Meeting Notices and Agendas
  from:08/27/2009 till:04/10/2012  color:gnso 
: At least seven days prior to a Board Meeting, notice of the meeting and its agenda must be posted.
  at:08/27/2009 shift:($dx,-10) text:"[[First GNSO Organizational Review|GNSO 1 Amendments]]"
* 3.5 Minutes and Preliminary Reports
  at:09/30/2009 shift:($dx,5) text:"Organizational Reviews every 5 years"
: All minutes of Board and Supporting Organizations meetings shall be compiled promptly, approved by the originating body, and forwarded to the ICANN Secretary for posting on the website.
  at:10/28/2010 shift:($dx,-5) text:"Creation of At-Large Director seat"
: In no later than two business days, any resolutions passed by the Board shall be made publicly available on the website, except in special circumstances.
  at:12/08/2011 shift:($dx,-10) text:"New Annex A - GNSO PDP"
: In no later than seven business days, any actions taken by the Board as result of a meeting shall be made publicly available on the website, except in special circumstances.
  from:04/10/2012 till:05/27/2016 color:gtld
: In no later than one day after they are approved, meeting minutes shall be made publicly available on the website, except in special circumstances.
  at:04/10/2012 shift:($dx,0) text:"[[New gTLD Program]]"
* 3.6 Notice and Comment on Policy Actions
  at:07/30/2014 shift:($dx,-5) text:"Changes to GAC-related provisions"
: ICANN must provide public notice on the website of policies and policy changes being considered and the reasoning behind them, at least twenty-one days prior to any action being taken. Resonable opportunities for public comment must be made prior to Board action. In the cases where policy action affect public policy concerns, the opinion of the [[GAC]] must be requested and heeded.
  from:05/27/2016 till:09/08/2019  color:iana
: When practical, an in-person public forum must be held for the discussion of proposed policy in accordance with [[ICANN Bylaws#6.1 Section 6(1)(b)]] of these Bylaws.
  at:05/27/2016 shift:($dx,-5) text:"[[IANA Functions Stewardship Transition|IANA Transition Amendments]]"
: After taking action, the Board must make public the meeting minutes, including the vote of each Director and any public statement they wish to include.
  from:09/08/2019 till:$now color:squo shift:($dx,0) text:"Current Bylaws"
* 3.7 Translation of Documents
 
: ICANN shall facilitate the translation of final public documents into the appropriate languages, as appropriate and to the extend possible given the organization's budget.
 
</timeline>


====Article 4. Accountability and Review====
{{RightTOC}}
* 4.1 Purpose
The '''Bylaws for Internet Corporation for Assigned Names And Numbers''' is the foundational governance document for [[ICANN]].<ref name="current">[https://www.icann.org/resources/pages/governance/bylaws-en ICANN.org - Bylaws](English)</ref> The bylaws define the mission of ICANN, establish rules for the structure and operation of the [[Supporting Organizations|SOs]] and [[Advisory Committee|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 Process|policy development processes]], and recommendations from [[ICANN Reviews|organizational and specific reviews]].
: This article sets forth the processes for reconsideration and independent review of ICANN's actions and the periodic review of ICANN's structure and procedures, in a way that reinforces ICANN's core values as stated in [[ICANN Bylaws#Article 1. Mission and Core Values|Article 1]], and transparency as stated in [[ICANN Bylaws#Article 3. Transparency|Article 3]] of these Bylaws.
 
* 4.2 Reconsideration
The current version of the ICANN Bylaws can be found [https://www.icann.org/resources/pages/governance/bylaws-en 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.<ref name="ogbylaws">[https://www.icann.org/resources/unthemed-pages/bylaws-1998-11-06-en ICANN.org Archive - Original Bylaws], November 6, 1998</ref> 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 [[Governmental 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.<ref name="ogbylaws" /> 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.<ref name="ogbylaws" /> 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.<ref name="mission02">[https://www.icann.org/resources/unthemed-pages/bylaws-2002-12-15-en#I ICANN.org Bylaws Archive - Article 1], as amended December 15, 2002</ref> The organization's mission statement was defined within the narrow scope of coordination and protection of "Internet's unique identifier systems." The article specified:
<blockquote>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.<br />
2. Coordinates the operation and evolution of the DNS root name server system.<br />
3. Coordinates policy development reasonably and appropriately related to these technical functions.<ref name="mission02" /></blockquote>
 
This mission statement remained the same until the [[IANA Functions Stewardship Transition]], 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:
<blockquote>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.<ref name="ianabylaws">[https://www.icann.org/resources/pages/bylaws-2016-09-30-en ICANN.org Bylaws Archive - Bylaws], as amended October 1, 2016</ref></blockquote>
 
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.<ref name="ianabylaws" />


<ref>[http://www.icann.org/en/general/bylaws.htm ICANN Bylaws]</ref>
==References==
==References==
{{reflist}}
[[Category: Glossary]]
[[Category: Glossary]]

Latest revision as of 18:30, 7 December 2021

<timeline> ImageSize = width:600 height:1200 PlotArea = left:50 right:50 bottom:20 top:20 AlignBars = early

DateFormat = mm/dd/yyyy Period = from:01/01/1998 till:12/31/2022 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:1 start:1998 ScaleMinor = unit:month increment:1 start:01/01/1998 Legend = left:400 top:1000 columns:1 Define $dx = 25 # shift text to right side of bar Define $now= 10/01/2021 #Keep updated!

Colors=

 id:og value:skyblue legend:Original_Bylaws
 id:evo value:limegreen legend:Evolution_&_Reform
 id:gnso value:lavender legend:GNSO_1_Amendments
 id:gtld value:tan1 legend:New_gTLD_Program
 id:iana value:coral legend:IANA_Functions_Transition
 id:squo value:drabgreen legend:Current_Bylaws

PlotData=

 bar:Amendments width:30 mark:(line,white) align:left fontsize:M
 from:10/01/1998 till:12/15/2002  color:og shift:($dx,0) 
 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:"Evolution & Reform Amendments"
 at:06/26/2003 shift:($dx,-5) text:"Amended to form ccNSO"
 at:02/28/2006 shift:($dx,-5) text:"ccNSO structure amended"
 at:02/15/2008 shift:($dx,-5) text:"Changes to At-Large Structure Applications"
 from:08/27/2009 till:04/10/2012  color:gnso  
 at:08/27/2009 shift:($dx,-10) text:"GNSO 1 Amendments"
 at:09/30/2009 shift:($dx,5) text:"Organizational Reviews every 5 years"
 at:10/28/2010 shift:($dx,-5) text:"Creation of At-Large Director seat"
 at:12/08/2011 shift:($dx,-10) text:"New Annex A - GNSO PDP"
 from:04/10/2012 till:05/27/2016 color:gtld 
 at:04/10/2012 shift:($dx,0) text:"New gTLD Program"
 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 Transition Amendments"
 from:09/08/2019 till:$now color:squo shift:($dx,0) text:"Current Bylaws"
 
 

</timeline>

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[edit | edit source]

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 Governmental 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[edit | edit source]

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 Stewardship Transition, 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[edit | edit source]

  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