Hi all,
For reference, below are the Bylaw articles referenced in the Review Team’s discussion this week:
ARTICLE 1 Mission, Commitments and Core Values
Article 1: https://www.icann.org/resources/pages/governance/bylaws-en/#article1
Section 1.1. Mission
(a) The mission of the Internet Corporation for Assigned Names and Numbers ("ICANN") is to ensure the stable and secure operation of the Internet's unique identifier systems as described in
this Section 1.1(a) (the "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.
(b) ICANN shall not act outside its Mission.
(c) ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet's unique identifiers or the content that such services carry or provide, outside the express
scope of Section 1.1(a). For the avoidance of doubt, ICANN does not hold any governmentally authorized regulatory authority.
Article 4: https://www.icann.org/resources/pages/governance/bylaws-en/#article4
Section 4.6. Specific Reviews
(c) Security, Stability, and Resiliency Review
(ii) The issues that the review team for the SSR Review ("SSR Review Team") may assess are the following:
(A) security, operational stability and resiliency matters, both physical and network, relating to the coordination of the Internet's system of unique identifiers;
(B) conformance with appropriate security contingency planning framework for the Internet's system of unique identifiers; and
(C) maintaining clear and globally interoperable security processes for those portions of the Internet's system of unique identifiers that ICANN coordinates.
(iii) The SSR Review Team shall also assess the extent to which ICANN has successfully implemented its security efforts, the effectiveness of the security efforts to deal with actual and potential
challenges and threats to the security and stability of the DNS, and the extent to which the security efforts are sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the DNS, consistent with ICANN's Mission.
(iv) The SSR Review Team shall also assess the extent to which prior SSR Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted
in the intended effect.
(v) The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened.
Article 18 IANA Naming Function Reviews
Article 18: https://www.icann.org/resources/pages/governance/bylaws-en/#article18
Section 18.1. IANA NAMING FUNCTION REVIEW
The Board, or an appropriate committee thereof, shall cause periodic and/or special reviews (each such review, an "IFR") of PTI's performance of the IANA naming function against the contractual
requirements set forth in the IANA Naming Function Contract and the IANA Naming Function SOW to be carried out by an IANA Function Review Team ("IFRT") established in accordance with Article 18, as follows:
(a) Regularly scheduled periodic IFRs, to be conducted pursuant to Section 18.2 below ("Periodic IFRs"); and
(b) IFRs that are not Periodic IFRs, to be conducted pursuant to Section 18.12 below ("Special IFRs").
From:
<ssr2-review-bounces@icann.org> on behalf of Karen Mulberry <karen.mulberry@icann.org>
Date: Monday, March 20, 2017 at 12:37 PM
To: Emily Taylor <emily.taylor@oxil.co.uk>
Cc: SSR2 Review Team Email List <ssr2-review@icann.org>
Subject: Re: [Ssr2-review] [Ext] Re: Bylaws Article 18 IANA Naming Function Reviews
Dear Emily,
Here are the two bylaw articles that apply to SSR Reviews from the meeting last week.
ARTICLE 1 Mission, Commitments and Core Values
Article 1:
https://www.icann.org/resources/pages/governance/bylaws-en/#article1
Section 1.1. Mission
(a) The mission of the Internet Corporation for Assigned Names and Numbers ("ICANN") is to ensure the stable and secure operation of the Internet's unique identifier systems as described in this Section
1.1(a) (the "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.
(b) ICANN shall not act outside its Mission.
(c) ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet's unique identifiers or the content that such services carry or provide, outside the express scope of Section
1.1(a). For the avoidance of doubt, ICANN does not hold any governmentally authorized regulatory authority.
Article 4:
https://www.icann.org/resources/pages/governance/bylaws-en/#article4
(c) Security, Stability, and Resiliency Review
(ii) The issues that the review team for the SSR Review ("SSR Review Team") may assess are the following:
(A) security, operational stability and resiliency matters, both physical and network, relating to the coordination of the Internet's system of unique identifiers;
(B) conformance with appropriate security contingency planning framework for the Internet's system of unique identifiers; and
(C) maintaining clear and globally interoperable security processes for those portions of the Internet's system of unique identifiers that ICANN coordinates.
(iii) The SSR Review Team shall also assess the extent to which ICANN has successfully implemented its security efforts, the effectiveness of the security efforts to deal with actual and potential challenges and
threats to the security and stability of the DNS, and the extent to which the security efforts are sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the DNS, consistent with ICANN's Mission.
(iv) The SSR Review Team shall also assess the extent to which prior SSR Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended
effect.
(v) The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened.
Karen Mulberry
Multistakeholder Strategy and Strategic Initiatives (MSSI)
ICANN
From:
Emily Taylor <emily.taylor@oxil.co.uk>
Date: Monday, March 20, 2017 at 12:20 PM
To: Karen Mulberry <karen.mulberry@icann.org>
Cc: "ssr2-review@icann.org" <ssr2-review@icann.org>
Subject: [Ext] Re: [Ssr2-review] Bylaws Article 18 IANA Naming Function Reviews
Dear Karen
Thank you for this reference.
If I understand correctly, then, the Post Transition IANA will be subject to
separate, periodic reviews relating to the performance of that function. I don't see security, stability and resiliency included in the provisions set out at Bylaw 18. So, is there any guidance on whether and to what extent SSR2 is expected to cover
Post Transition IANA as part of its scope?
Kind regards
Emily
On Mon, Mar 20, 2017 at 6:00 PM, Karen Mulberry <karen.mulberry@icann.org> wrote:
Bylaws Article 18 IANA Naming Function Reviews
We thought that this might assist the RT as it considers the SSR2 Review’s scope of work.
Article 18: https://www.icann.org/resources/pages/governance/bylaws-en/#article18[icann.org]
Karen Mulberry
Director, Multistakeholder Strategy and Strategic Initiatives (MSSI)
ICANN
12025 Waterfront Dr., Suite 300
Los Angeles, CA 90094
Phone: +1 424 353 9745
_______________________________________________
Ssr2-review mailing list
Ssr2-review@icann.org
https://mm.icann.org/mailman/listinfo/ssr2-review
--
Emily Taylor
CEO, Oxford Information Labs
Associate Fellow, Chatham House; Editor, Journal of Cyber Policy
PLEASE NOTE MY NEW EMAIL ADDRESS AND CONTACTS AS OF 1 JANUARY 2017
Magdalen Centre, Oxford OX4 4GA | T: 01865 582885
E: emily.taylor@oxil.co.uk |
D: 01865 582811 | M: +44 7540 049322
Registered office: 37 Market Square, Witney, Oxfordshire OX28 6RE. Registered in England and Wales No. 4520925. VAT No. 799526263
.