Skip to main content

IANA Stewardship Transition Implementation Planning Update (Volume 3)

ICANN is compiling updates on the progress of the IANA Stewardship Transition and Enhancing ICANN Accountability implementation planning efforts. This information is positioned to help inform interested stakeholders on the recent developments in the processes, upcoming key dates, and latest documents and drafts that occur over the timeframe.
 

Root Zone Management

The Root Zone Management implementation planning track contains projects relating to changes to the root zone management system (RZMS) to remove NTIA's authorization process, parallel testing of the production and parallel test RZMS, and the development and execution of an agreement with Verisign as the root zone maintainer.

Root Zone Management System (RZMS) Changes to Remove Root Aone Administrator (RZA) Role and Support Parallel Testing


Status update:

We are 75 days into the 90-day parallel testing period and everything continues to go smoothly. Click here to view Verisign’s daily Parallel Operations Root Zone Management System Comparison Reports of all the root zone files generated.

ICANN will be posting the second of three Monthly Reports on RZMS Parallel Testing Progress during the testing period in the coming days. The report will be available on ICANN’s dedicated Parallel Testing webpage.

In the event that no unexplained differences in root zone files are identified between the production RZMS and the parallel test RZMS, the testing period will end successfully on 5 July 2016.

Documents/announcements posted:

Verisign Daily Parallel Operations Root Zone Management System Comparisons

 

Root Zone Maintainer Agreement (RZMA)


Status update:

ICANN and Verisign are working to finalize the last outstanding details of the RZMA. The agreement will be posted for public review once it is finalized.

Documents/announcements posted:

None.

 

Stewardship Transition

The Stewardship Transition planning track contains projects to prepare agreements with the operational communities, creation of a Post-Transition IANA (PTI) entity, establishment of a Customer Standing Committee (CSC) and a Root Zone Evolution Review Committee (RZERC), operationalizing the IANA customer service escalation mechanisms and Service Level Agreements (SLAs).

Service Level Expectations (SLEs) for Naming Community


Status update:

The ongoing work to define performance targets for the naming community is on track. ICANN has been collecting SLE data since March, and based on the data received, aims to propose performance targets to the SLE Design Team of the Cross Community Working Group Names (CWG-Stewardship) for their consideration in July.

In addition to collecting data, ICANN is also working to develop an online dashboard that will display the final performance targets and actual performance against targets.

Documents/announcements posted:

None.

Mailing list:

http://mm.icann.org/pipermail/dt1

 

Service Level Agreement (SLA) for the IANA Numbering Services


Status update:

The Number Resource Organization (NRO) published a version 5.2 of the SLA to remove any references to an Annex as the description in Article 4.3 is sufficient for the purposes of the SLA.

On 27 May 2016, the ICANN Board issued a resolution (2016.05.27.06) approving the SLA for signing. Once signed, the SLA will go into effect upon the successful completion of the transition.


Documents/announcements posted:

Service Level Agreement for the IANA Numbering Services (Final Signature Document)

Redline of changes between SLA versions 5.1 and 5.2


Mailing list:

https://www.nro.net/pipermail/ianaxfer/

 

Memorendum of Understanding (MoU) Supplemental Agreement for the Internet Engineering Task Force (IETF)


Status update:

On 27 May 2016, the ICANN Board issued a resolution (2016.05.27.07) approving the MoU Supplemental Agreement for signing. Once signed, the agreement will go into effect upon the successful completion of the transition.


Documents/announcements posted:

None.


Mailing list:

None.

  

Customer Standing Committee (CSC)


Status update:

On 1 June, ICANN sent a Request for Appointment of Members and Liaisons to the CSC to the Chairs and co-Chairs of all of ICANN’s Supporting Organizations, Advisory Committees, and the Registry Stakeholder Group.

The request asks that the respective organizations to initiate their processes to appoint candidates to serve as members and liaisons to the CSC.

The deadline for appointing organizations to send candidate selections is 22 July.


Documents/announcements posted:


Mailing list:

http://mm.icann.org/pipermail/cwg-stewardship/

http://mm.icann.org/pipermail/iotf

 

Root Zone Evolution Review Committee (RZERC)


Status update:

A draft charter for the RZERC has been finalized and is currently posted for a 30-day public comment period through 10 July 2016.

Once the RZERC Charter has been adopted, ICANN will take the steps necessary to form the committee, which will become operational upon the successful completion of the transition.


Documents/announcements posted:

Draft Root Zone Evolution Review Committee Charter
 

Mailing list:

http://mm.icann.org/pipermail/cwg-stewardship/

http://mm.icann.org/pipermail/iotf/

 

Post-transition IANA (PTI)


Status update:

The Bylaws and Articles of Incorporation for PTI were circulated to the community on 13 May 2016. ICANN’s legal team is currently working with the CWG-Stewardship’s independent legal counsel to revise the draft documents. Once the documents are finalized they will be posted for public comment.

Additionally, ICANN shared a draft implementation approach for PTI to the IOTF on 24 May. Discussions with the IOTF on this proposed approach are ongoing.

Documents/announcements posted:

Draft PTI Implementation Approach
 

Mailing list:

http://mm.icann.org/pipermail/cwg-stewardship/

http://mm.icann.org/pipermail/iotf/

 

Accountability Enhancements

The Accountability Enhancements Planning track contains projects to plan for implementation of enhancements to ICANN’s Independent Review and Reconsideration Request processes, to update ICANN’s governance documents, and to operationalize new community powers defined by the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability).

ICANN's New Bylaws


Status Update:

ICANN's legal team distributed the summary and analysis of Public Comments and the proposed revised ICANN Bylaws to the ICANN Board and Bylaws Coordination Group on 25 May 2016. The external legal teams affirmed that the New Bylaws reflected the Proposals’ recommendations. These resources were also made available on the public comment page.

On 27 May 2016, the ICANN Board issued resolutions (2016.05.27.01-2016.05.27.04) adopting the new ICANN Bylaws. ICANN transmitted the new Bylaws to the U.S. Department of Commerce’s National Telecommunications and Information Administration (NTIA) that same day.

The new ICANN Bylaws will be deemed effective upon the expiration the IANA Functions Contract between ICANN and NTIA.


Documents/announcements posted:

Summary Report of Public Comments

Detailed Chart of ICANN's Analysis of the Comments

Proposed New Bylaws (Revised to address comments)

Redline of Bylaws (Changes from 20 April)

Memo to Bylaws Coordination Group on Items for Consideration


Mailing list(s):

http://mm.icann.org/pipermail/bylaws-coord/

http://mm.icann.org/pipermail/accountability-cross-community/

http://mm.icann.org/pipermail/cwg-stewardship/

http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/

 

ICANN's Updated Articles of Incorporation


Status update:

ICANN’s Draft Restated Articles of Incorporation are currently posted for a 40-day public comment period through 6 July 2016.

Any interested party may review and provide feedback on the draft Restated Articles during the public comment period. The comments will be analyzed and incorporated for the ICANN Board prior to its consideration of the adoption of the Restated Articles.

Restated Articles must be adopted as part of the implementation planning process. Once adopted, the Restated Articles are expected to go into effect upon the successful completion of the transition.

Documents/announcements posted:


Mailing list:

None.

 

Independent Review Process (IRP)


Status update:

The CCWG-Accountability formed a Working Party called the IRP Implementation Oversight Team (IOT) to define procedures for the enhanced IRP process defined by the CCWG-Accountability in its Work Stream 1 proposal.


Documents/announcements posted:

None.

Mailing list:

http://mm.icann.org/pipermail/iot/

Comments

    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."