Changes

<timeline>

<timeline>

ImageSize  = width:500 height:1200

ImageSize  = width:600 height:1200

PlotArea  = left:50 right:50 bottom:20 top:20

PlotArea  = left:50 right:50 bottom:20 top:20

AlignBars  = justify

AlignBars  = early

DateFormat = mm/dd/yyyy

DateFormat = mm/dd/yyyy

Period    = from:01/01/1998 till:12/31/2022

Period    = from:01/01/1998 till:12/31/2022

TimeAxis  = orientation:vertical order:reverse

TimeAxis  = orientation:vertical  

ScaleMajor = unit:year increment:1 start:1998

ScaleMajor = unit:year increment:1 start:1998

ScaleMinor = unit:month increment:1 start:01/01/1998

ScaleMinor = unit:month increment:1 start:01/01/1998

Define $dy = 25 # shift text to right side of bar

Colors=

PlotData=

PlotData=

   bar:Amendments width:30 mark:(line,white) align:left fontsize:L

   bar:Amendments width:30 mark:(line,white) align:left fontsize:M

   from:10/01/1998 till:12/15/2002  color:skyblue 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 text:""[[2002 Evolution and Refom Process|2002 Evolution & Reform]]

  at:10/01/1998 shift:($dx,-5) text:"ICANN Formed"

   at:06/26/2003 shift:(0,25) align:left text:"[[ccNSO|Amended to form ccNSO]]"

   from:12/15/2002 till:08/27/2009  color:evo shift:($dx,0)

   at:02/28/2006 shift:(0,-25) align:left text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"

  at:12/15/2002 shift:($dx,-5) text:"[[2002 Evolution and Reform Process|Evolution & Reform Amendments]]"

   at:02/15/2008 shift:(0,25) align:left text:"Changes to At-Large Structure Applications"

   at:06/26/2003 shift:($dx,-5) text:"[[ccNSO|Amended to form ccNSO]]"

   from:08/27/2009 till:04/10/2012  color:limegreen text:"[[First GNSO Organizational Review|GNSO 1 Amendments]]"

   at:02/28/2006 shift:($dx,-5) text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"

   at:09/30/2009 shift:(0,-25) text:"Organizational Reviews every 5 years"

   at:02/15/2008 shift:($dx,-5) text:"Changes to At-Large Structure Applications"

   at:10/28/2010 shift:(0,25) text:"Creation of At-Large Director seat"

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

   at:12/08/2011 shift:(0,-25) text:"New Annex A - GNSO PDP"

  at:08/27/2009 shift:($dx,-10) text:"[[First GNSO Organizational Review|GNSO 1 Amendments]]"

   from:04/10/2012 till:05/27/2016 color:tan1 text:"[[New gTLD Program]]"

   at:09/30/2009 shift:($dx,5) text:"Organizational Reviews every 5 years"

   at:07/30/2014 shift:(0,25) text:"Changes to GAC-related provisions"

   at:10/28/2010 shift:($dx,-5) text:"Creation of At-Large Director seat"

   from:05/27/2016 till:09/08/2019  color:coral text:"[[IANA Functions Stewardship Transition|IANA Transition]]"

   at:12/08/2011 shift:($dx,-10) text:"New Annex A - GNSO PDP"

   from:09/08/2019 till:$now color:drabgreen text:"Current Bylaws"

   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 Functions Stewardship Transition|IANA Transition Amendments]]"

   from:09/08/2019 till:$now color:squo shift:($dx,0) text:"Current Bylaws"

    

    

    

    

==Evolution Over Time==

==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 [[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.<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.

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===

===Mission and Core Values===

3. Coordinates policy development reasonably and appropriately related to these technical functions.<ref name="mission02" /></blockquote>

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 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:

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:

<blockquote>Specifically, ICANN:

     (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>

     (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" />  

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" />

==References==

==References==