Changes

12 bytes added , 2 years ago

→‎Evolution Over Time

Line 22: Line 22:

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:og shift:($dx,0)

Line 52: Line 52:

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

Line 61: Line 61:

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:

Line 77: Line 77:

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

JP

Bureaucrats, Check users, lookupuser, Administrators, translator

3,197

edits

Changes

ICANN Bylaws (view source)

Revision as of 18:30, 7 December 2021