Jump to content

ICANN Bylaws: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
Caterina (talk | contribs)
14,326 edits
No edit summary
JP (talk | contribs)
Bureaucrats, Check users, lookupuser, Administrators, translator
3,197 edits
 
(65 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{RightTOC}}
<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
 
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!


The Bylaws in full can be found [http://www.icann.org/en/general/bylaws.htm here]. A summary of each section is as follows:
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


===Article 1. Mission and Core Values===
PlotData=
* '''1.1 Mission'''
  bar:Amendments width:30 mark:(line,white) align:left fontsize:M
** To coordinate the global Internet's system of identifiers (domain names/[[DNS]], [[IP Address]]es, [[AS]] numbers, and protocol port and parameter numbers), and ensure that the system is stable and secure.
* '''1.2 Core Values'''
** Preserve and enhance operational stability, reliability, security, and global interoperability of the Internet.
** Respect the innovation, creativity, and flow of information made possible by the Internet, not interfering with such
** Delegate to other relevant entities when appropriate
** Seek and support broad, informed participation in ICANN activities
** Depend on market mechanisms to promote and sustain industry competition
** Introduce and promote competition in regards to domain name registration
** Employ open and transparent policy development mechanisms
** Make decisions neutrally, objectively, and fairly
** Act with speed while also ensuring all effective parties are provided the opportunity to input
** Remain accountable for the Internet community
** Despite being a private sector organization, respect input from public sector, including governments or other public authorities


===Article 2. Powers===
  from:10/01/1998 till:12/15/2002  color:og shift:($dx,0)
* '''2.1 General Powers'''
  at:10/01/1998 shift:($dx,-5) text:"ICANN Formed"
** The [[ICANN Board|Board]] shall either exercise or observe the exercising of ICANN's powers. It acts with a majority vote.
  from:12/15/2002 till:08/27/2009  color:evo shift:($dx,0)
* '''2.2 Restrictions'''
  at:12/15/2002 shift:($dx,-5) text:"[[2002 Evolution and Reform Process|Evolution & Reform Amendments]]"
** ICANN is not a domain name [[registry]], [[registrar]], or [[IP]] address registry.
  at:06/26/2003 shift:($dx,-5) text:"[[ccNSO|Amended to form ccNSO]]"
* '''2.3 Non-Discriminatory Treatment'''
  at:02/28/2006 shift:($dx,-5) text:"[[CcNSO Policy Development Process - Country Codes|ccNSO structure amended]]"
** ICANN shall not discriminate against any party.
  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:"[[First GNSO Organizational Review|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 Functions Stewardship Transition|IANA Transition Amendments]]"
  from:09/08/2019 till:$now color:squo shift:($dx,0) text:"Current Bylaws"
 
 
</timeline>


===Article 3. Transparency===
{{RightTOC}}
* '''3.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]].
** ICANN and its constituent bodies shall act in an open, transparent, and fair manner.
* '''3.2 Website'''
** ICANN shall maintain a publicly accessible website
* '''3.3 Manager of Public Information'''
** 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.
* '''3.4 Meeting Notices and Agendas'''
** At least seven days prior to a Board Meeting, notice of the meeting and its agenda must be posted.
* '''3.5 Minutes and Preliminary Reports'''
** 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.
** 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.
** 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.
** In no later than one day after they are approved, meeting minutes shall be made publicly available on the website, except in special circumstances.
* '''3.6 Notice and Comment on Policy Actions'''
** 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.
** When practical, an in-person public forum must be held for the discussion of proposed policy in accordance with [[ICANN Bylaws#Article 6: Board of Directors|Section 6(1)(b)]] of these Bylaws.
** 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.
* '''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.


===Article 4. Accountability and Review===
The current version of the ICANN Bylaws can be found [https://www.icann.org/resources/pages/governance/bylaws-en here].  
* '''4.1 Purpose'''
** 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'''
** ICANN shall have a process by which a person or entity can request review or reconsideration of an action that they have been affected by.
** A person or entity may submit a Reconsideration Request if he/she/it has been adversely affected by staff actions or inactions that contradict existing policy; or if an action or inaction by the ICANN Board resulted in the failure to consider submitted materials.
** The Board shall designate a [[Board Governance Committee]], whose responsibility shall be to evaluate Reconsideration Requests.
** ICANN shall absorb the normal administrative costs of a Reconsideration Request. In the case of determined extraordinary costs, the party seeking reconsideration shall have the opportunity to either withdraw the request or bear the cost.
** All Reconsideration Requests must be submitted by email within 30 days of the action or inaction requiring reconsideration.
** All Reconsideration Requests shall be posted publicly on the website.
** The BCG may request information from the Board, the requesting party, or a third party.
** The BCG must submit its considerations to the Board within ninety days of the request's submission, unless impractical. The final recommendation shall be posted on the website.
** The Board is not required to follow the considerations of the BCG. The Board's decision shall be posted on the website.
** The BCG shall submit an anual summary of all Reconsideration Requests
* '''4.3 Independent Review of Board Actions'''
** In addition to the above reconsideration review policy, ICANN shall have a separate process for the third-party review of Board actions allegedly inconsistent with the Bylaws.
** Any person materially affected by Board decision or action that is inconsistent with the Bylaws may file for an independent review of that decision or action.
** Such requests shall be referred to the Independent Review Panel (IRP), which shall be operated by an independent, international arbitration provider (IRP Provider)
** The IRP Provider shall establish operating rules and procedures, subject to the approval of the ICANN Board.
** The IRP may request further information from the party seeking review, the ICANN Board, [[Supporting Organizations]], or other parties.
** Individuals holding an official postion or office within the ICANN structure are not eligible to serve on the IRP.
** Proceedings shall be conducted via email or by other Internet means in order to keep review costs down. When necessary, the IRP may hold telephone meetings.
** The IRP shall make its declarations in writing. All petitions, claims, and declarations shall be posted on the website when they become available. The IRP may discretionarily deign to keep certain information confidential, at the submitting party's request.
** IRP declarations shall be considered at the next Board Meeting.
* '''4.4 Periodic Review of ICANN Structure and Operations'''
** The Board shall enact the periodic review of the performance and operation of each [[SO|Supporting Organization]], each Supporting Organization Council, each [[Advisory Committee]] (other than the [[Governmental Advisory Committee]], which shall provide its own review mechanisms), and the [[Nominating Committee]]. The review shall be conducted by an entity or entities independent from the organization under review.
** These reviews shall be conducted no less frequently than every five years.
** The results of these reviews shall be posted on the website for public comment, which shall be considered by the Board at the next opportunity.


===Article 5: Ombudsman===
==Evolution Over Time==
* '''5.1 Office of Ombudsman'''
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.
** There shall be an Office of Ombudsman, managed by an Ombudsman, to support the [[ICANN Staff]] as much as the Board determines to be appropriate and feasible. The position shall be full time, with salary and benefits as determined by the Board. The term shall last two years initially, and is subject to renewal. The dismissal of the Ombudsman requires a 3/4 majority vote from the Board.
** The budget for the Office of Ombudsman shall be determined by the ICANN Board as part of the annual budget process. The Ombudsman shall submit a proposed budget to the President for consideration.
* '''5.2 Charter'''
** The Ombudsman shall act as a neutral dispute resolution practitioner for matters that do not invoke Section 2 or Section 3 of  [[ICANN Bylaws|Article IV]]. The Ombudsman shall serve as an objective advocate for fairness, and seek to evaluate and possibly resolve complaints about unfair or inappropriate treatment by ICANN staff, the Board, or ICANN constituent bodies, using conflict resolutions tool such as negotiation, facilitation, and "shuttle diplomacy."
* '''5.3 Operations'''
** The Ombudsman shall facilitate the fair, impartial, and timely resolution of complaints that affect the ICANN community, excluding employees and vendors/suppliers, against the ICANN Board or staff, which are not subject of either the Reconsideration or Independent Review Policies. They may not be personally biased in any way, or have a personal stake in any outcome.
** The Ombudsman may use his or her own discretion to accept or decline to act on a complaint or question. Additionally, the Ombudsman shall have no authority to act with respect to internal administrative matters, personnel matters, issues relating to membership on the Board, or issues related to vendor/supplier relations.
** The Ombudsman has the right to access (but not to publish, if confidential) all information necessary to his/her decision-making.
** The Ombudsman must comply with all internal conflicts-of-interest and confidentiality policies.
* '''5.4 Interaction with ICANN and Outside Entities'''
** No ICANN employee, Board member, or other internal organization member may impede the Ombudsman's contact with the ICANN community and vice-versa.
** ICANN staff and other participants must observe and respect the determinations made by the Ombudsman.
** Contact with the Ombudsman does not constitute as notice to ICANN of any particular action or cause of action.
** The Ombudsman may not take any action not outlined in the Bylaws.
* '''5.5 Annual Report'''
** The Ombudsman must publish an annual report consisting of a consolidated analysis of the years complains and resolutions. It shall be posted on the website.


===Article 6: Board of Directors===
===Mission and Core Values===
* '''6.1 Composition of the Board'''
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:
** The ICANN Board of Directors shall consist of sixteen voting members, called Directors. In addition, five non-voting Liaisons shall be designated, in accordance with Section 9 of this Article.
<blockquote>In particular, ICANN:
* '''6.2 Directors and Their Selection; Election of Chairman and Vice-Chairman'''
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 />
** The Directors shall consist of eight voting members selected by the [[Nominating Committee]], two voting members selected by the [[Address Supporting Organization]], two voting members selected by the Country Code Names Supporting Organization, two voting members selected from the Generic Names Supporting Organization, one voting member selected from the [[At-Large Community]], and the previous President of the Board, who shall also be a voting member.
2. Coordinates the operation and evolution of the DNS root name server system.<br />
** The Nominating Committee shall ensure that the delegates it selects are a good representation of of ICANN's diversity in geography, culture, skills, experience, and perspective. The number of Directors selected from any one Geographic Region shall not exceed five, with the aim to have representatives from each region.
3. Coordinates policy development reasonably and appropriately related to these technical functions.<ref name="mission02" /></blockquote>
** The Supporting Organizations and At-Large Community shall also, in conjunction, ensure the same diversity as the above. No two Directors selected by a Supporting Organization shall be citizens from the same country or of countries located in the same Geographic Region.
** The Board shall annually elect a Chairman and Vice-Chairman from among the Directors, not including the President.
* '''6.3 Criteria for Selection of Directors'''
** Chosen Directors shall be accomplished persons of integrity, objectivity, and intelligence, with sound judgement, open mind, and the ability to work well in groups. They must have prior understanding of ICANN's mission and the organizations potential impact on the global Internet community. In aggregate, they must represent the broadest cultural and geographical diversity, and demonstrate a collective understanding of gTLD registries and registrars, ccTLD registries, IP address registries, Internet technical standards and protocols, policy-development procedures, legal traditions, and the public interest. Finally, they must be willing to serve as volunteers, and must have strong communication skills with written and spoken English.
* '''6.4 Additional Qualifications'''
** No official from a government or multinational entity may serve on the ICANN Board.
** No person who serves on any Supporting Organization Council, including as a liaison, shall simultaneously serve as a Director or liaison to the Board.
** Persons serving on the Nominating Committee ar ineligible for selection to Board positions.
* '''6.5 International Representation'''
** Selection of Directors must follow the set diversity provisions, which is that at least one Director must be from each Geographic Region, and no more than five may come from the same region. The Geographic Regions are defined as: Europe; Asia/Australia/Pacific; Latin America/Caribbean islands; Africa; and North America.
* '''6.6 Directors' Conflicts of Interest'''
** Directors are required to make known all possible conflicts of interests at least once a year.
* '''6.7 Duties of Directors'''
** Directors must act on what they believe to be in the best interest for ICANN, and not the organization that they represent, their employers, or anyone else.
* '''6.8 Terms of Directors'''
** The terms of the Directors shall be staggered, always starting at the close of a meeting.
** A term lasts until the successor commences the next term, or until they resign or are removed.
** At least two months prior to the commencement of the annual meeting, the organizations represented on the Board shall submit their nominations to the Secretary for those positions needing to be filled.
** No Director may serve more than three consecutive terms.
** The President of the organization may only serve as Director for as long as they also serve as President.
* '''6.9 Non-Voting Liaisons'''
** There shall be one Liaison voted from the [[Governmental Advisory Committee]], one from the [[Root Server System Advisory Committee]], one from the [[Security and Stability Advisory Committee]], one from the [[Technical Liaison Group]], and one from the [[Internet Engineering Task Force]].
** The term of a Non-Voting Liaison shall begin at the conclusion at the end of each annual meeting.
** Non-Voting Liaisons shall serve unpaid, as volunteers.
** There is no limit to how long a liaison may serve.
** Liaisons are entitled to attend Board Meetings, participate in Board discussions and deliberations, and have access to all materials provided to the Board for such uses. They have no other rights of the Directors.
* '''6.10 Resignation of a Director or Non-Voting Liaison'''
** A Board Member may resign at any time, either by verbal notice at any Board Meeting followed by written notice to the Secretary, or by written notice to the President.
* '''6.11 Removal of a Director or Non-Voting Liaison'''
** A Director may be removed by a 3/4 vote of the Board, not including the vote of the candidate for removal.
** Any non-noting liaison of the Board, with the exception of the Government Advisory Board liaison, by a 3/4 vote of the ICANN Board, following the notification of the liaison's organization.
* '''6.12 Vacancies'''
** A vacancy or vacancies in the Board shall be deemed to exist in that case of the death, resignation, or removal of any Board Member; or an authorized increase in the number of Board Members; or the incarceration of an existing Board Member. A vacancy shall be filled by the Nominating Committee, unless the vacancy is for the representative from a Supporting Organization, in which case that organization shall fill the vacancy. If the vacancy is the President of ICANN, it shall be filled as per [[ICANN Bylaws#Article 8: Officers|Article 8]] of these Bylaws.
** Liaison vacancies shall be determined and filled by the organization for which the position serves.
* '''6.13 Annual Meetings'''
** An annual meeting shall be held at the principal ICANN office for the purpose of electing officers. The meeting may be held elsewhere if the Board so choses, at a maximum of every 14 months.
* '''6.14 Regular Meetings'''
** Regular meetings shall be held as designated by the Board.
* '''6.15 Special Meetings'''
** Special meetings may be called, with the requirement of at least one fourth of the Board to be in attendance.
* '''6.16 Notice of Meetings'''
** Notice of all meetings shall be delivered to all Directors and liaisons in one of the following manners: personally, telephone, email, first class/air mail, or fax.
* '''6.17 Quorums'''
** A majority of all Directors currently in office constituted a quorum.
* '''6.18 Action by Telephone or Other Communication Equipment'''
** Directors of the Board or other Committees may use telecommunication methods in lieu of attending meetings as long as all members of the board can speak to and hear one another.
* '''6.19 Action Without Meeting'''
** An action may be taken without a meeting if all members provide written consent to such.
* '''6.20 Electronic Meeting'''
** Communication via email may substitute any other communication required in writing.
* ''6.21 Rights of Inspection'''
**
* '''6.22 Compensation'''
** The Chair of the Board is entitled to reasonable compensation for his/her services. All other Directors are not entitled to compensation, although the Board may authorize the reimbursement of reasonable expenses incurred as part of their duties.
* '''6.23 Presumption of Assent'''
** Any Director present at a meeting shall be assumed to have assented to a Board decision unless their dissent or abstention is recorded in the minutes, or they provide written notice.


===Article 7: Nominating Committee===
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:
* '''7.1 Description'''
<blockquote>Specifically, ICANN:
** A [[Nominating Committee]] shall be designated to select all ICANN Board members except the President and those chosen by Supporting Organizations. The Committee may also be assigned to make other selections as well.
* '''7.2 Composition'''
** The Nominating Committee shall consist of one non-voting Chair, selected by the ICANN Board; one non-voting Chair-Elect, selected by the ICANN Board to serve as an advisor; a non-voting liaison appointed by the [[Root Server System Advisory Committee]]; a non-voting liaison appointed by the [[Security and Stability Advisory Committee]]; a non-voting liaison appointed by the [[Governmental Advisory Committee]]; five voting delegates selected by the [[At-Large Advisory Committee]]; seven delegates from the [[Generic Names Supporting Organization]], with the following breakdown: one delegate from the [[Registry Stakeholder Group]], one from the [[Registrars Stakeholder Group]], one from the [[ISPC|Internet Service Providers Constituency]], one from the [[IPC|Intellectual Property Constituency]], one selected by the [[Non-Commercial Users Constituency]], and one each from the small and large businesses sections of the [[BC|Business Users Constituency]]; one delegate from the [[Country Code Names Supporting Organization]]; one delegate from the [[Generic Names Supporting Organization]]; one delegate from the [[Internet Engineering Task Force]]; one from the [[Technical Liaison Group]]; and one non-voting Associate Chair, appointed by the Chair.
* '''7.3 Terms'''
** Each voting delegate shall serve a one year term. They may not serve two consecutive terms; two years must elapse between terms.
** Terms for voting delegates begin and end at the conclusion of annual meetings.
** Terms for non-voting liaisons serve terms as designated by their appointing organization.
** Upon the end of the Chair's term, the Chair-Elect shall become Chair, pending Board approval.
** Vacancies are to be filled by the original appointing organization.
** Vacancies shall not effect the Nominating Committee's obligation to fulfill their responsibilities.
* '''7.4 Criteria for Selection of Nominating Committee Delegates'''
** Nominating Committee delegates should be persons


* '''7.5 Diversity'''
    (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:
**


* '''7.6 Administrative and Operation Support'''
        *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
** It is ICANN's duty to provide administrative support to the Nominating Committee.
        *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.
* '''7.7 Procedures'''
** The NomCom shall adopt whatever operating procedures it deems necessary, and will publish them on the website.
* '''7.8 Ineligibility for Selection by Nominating Committee'''
** Persons on the NomCom are not eligible to be selected for service in any other ICANN body.
* '''7.9 Ineligibility for Service on Nominating Committee'''
** No persons who are paid employees or consultants of ICANN may serve on the NomCom.


=== Article 8: Address Supporting Organization ===
    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.
* '''8.1 Description'''
** The Address Supporting Organization ([[ASO]]) shall advise the ICANN Board on topics relating to Internet addresses.
* '''8.2 Address Council'''
** The ASO shall have an Address Council, which is to consist of members of the NRO Number Council.
** The Address Council will appoint two delegates to the ICANN Board.


===Article 9: Country-Code Names Supporting Organization===
    (ii) Facilitates the coordination of the operation and evolution of the DNS root name server system.
* '''9.1 Description'''
** The Country-Code Names Supporting Organization ([[ccNSO]]) is a policy-development body that is responsible for developing and recommending policies related to country-code top level domains ([[ccTLD]]s) to the ICANN Board, for creating consensus across the ccNSO community, and for coordinating with other [[Supporting Organizations]], committees, and constituencies.
* '''9.2 Organization'''
** The ccNSO consists of ccTLD managers who have agreed in writing to participate in the organization, as well as a ccNSO council for the actual management of the policy development process.
* '''9.3 ccNSO Council'''
** The ccNSO Council shall consist of three persons selected by ccNSO members and three selected by the [[Nominating Committee]], as well as liaisons and observers.
** Each of the following organizations shall appoint one liaison to the ccNSO Council: the [[Governmental Advisory Committee]], the [[At-Large Advisory Committee]], and each of the five Regional Organizations ([[RALO]]s). These liaisons may not vote on ccNSO matters, but otherwise are on equal terms with the other council members. Designations, including length of term, are made in writing to the ICANN Secretary. Recalling or replacing a liaison may happen at any time.
** The ccNSO may exchange observers with any other Supporting Organization's council.
** A regular ccNSO Council Member term shall start at the conclusion of an annual meeting, and shall end at the third annual meeting thereafter.
** A ccNSO Council Member may resign at any time with written notice to the ICANN Secretary and a copy to the Council Chair.
** A member may me removed from the Council if he or she misses three or more consecutive meetings without sufficient cause. They may also be removed for grossly inappropriate behavior. The removal of a member requires a 2/3 majority vote of the rest of the Council.
** A vacancy on the Council will exist upon the death, resignation or removal of a member of the Council. The vacancy is to be filled in the same manner by which the original member was chosen.
** The role of the ccNSO Council is to coordinate and administer the affairs of the ccNSO and to manage the development of policy recommendations related to country codes.
** The ccNSO Council shall fill two of is own seats via written ballot or by majority action at a meeting.
** Rules and procedures may be adopted as necessary, as long as they are consistent with the ICANN Bylaws. These shall be published on the website.
** CcNSO action shall take place at regularly scheduled meetings. These meetings may happen no fewer than four times per year, and shall be open to the public unless deemed otherwise by a majority vote.
** Notice of place and time of meetings of the Council shall be provided to each ccNSO Council member, liaison, and observer at least 21 days prior to each meeting. An agenda shall be posted at least seven days prior to each meeting.
** Members may participate in meetings in person or through electronic communication, provided that all members may hear and speak to each other. Minutes shall be posted on the website by the ICANN Secretary.
* '''9.4 Membership'''
** Members of the ccNSO are ccTLD Managers. A ccTLD Manger is an organization or entity responsible for managing an ISO 3166 country-code top-level domain, and is noted in the [[IANA]] database as such.
** Any ccTLD Manager may become part of the ccNSO by submitted the proper application to the proper person. A member may resign by giving written notice.
** Receipt of IANA services is not contingent on ccNSO  or RALO membership.
** The Geographic Region for a ccTLD Manager is designated by the location of the ccTLD's country, not the location of the Manager.
** CcTLD Managers may designate, in writing, a person, organization, or entity to represent it. If no person is designated, the ccTLD Manager shall be represented by the person, organization, or entity listed as the administrative contact in the IANA database.
** There shall be an open, annual meeting of ccNSO members, coordinated by the ccNSO Council.
** ccNSO Council Members shall be selected from each Geographic Region via a nomination process, followed by an election if necessary.
** Any ccNSO Member may nominate a person from their own Geographic Region to serve on the Council. The nomination must be seconded by another member from the same Geographic Region.
** If there are no more nominated individuals for a Geographic Region than there are seats for that Geographic Region, then all those nominated are appointed. If there are more nominees than there are seats, a written ballot election shall be held.
**
**
* '''9.5 Regional Organizations'''
** The ccNSO may designate a Regional Organization for each ICANN Geographic Region. These organizations must be open to membership to any ccTLD Manager within its Geographic Region. A 2/3 majority vote of the ccNSO Council is required to designate or de-designate an organization as its region's Regional Organization.
* '''9.6 ccNSO Policy-Development Process and Scope
** The scope of the ccNSO's policy development role is described in [[ICANN Bylaws#Annex C|Annex C]] of these Bylaws. Any changes to these must first be recommended to and then approved by the ICANN Board.
** The process for the development of policy and recommendation to the Board is outlined in [[ICANN Bylaws#Annex B|Annex B]] of these Bylaws. The process is called the ccNSO Policy-Development Process, or ccPDP.
* '''9.7 Staff Support and Funding'''
** The ccNSO Council may request the support of an ICANN Staff member, who shall serve as the ccNSO Staff Manager. The ccNSO may alternatively select their own ccNSO Staff Manager, at its own expense. The ccNSO Staff Manager's duties shall be designated by the ccNSO Council Chair.
** The ccNSO Council may request administrative and operational support from ICANN. The ccNSO Council may, at its own expense, hire alternative or additional administrative support.
** The ccNSO Council shall establish membership fees in order to pay for ccNSO expenses, as agreed upon by the members.
** The ICANN Secretary shall manage all secretarial duties for the ccNSO.


===Article 10: Generic Names Supporting Organization===
    (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>


<ref>[http://www.icann.org/en/general/bylaws.htm ICANN Bylaws]</ref>
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==

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

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

Retrieved from "https://icannwiki.org/index.php?title=ICANN_Bylaws&oldid=1341185"