Skip to main content

IANA Stewardship Transition Implementation Planning Update (Volume 4)

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 role, 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 Zone Administrator (RZA) Role and Support Parallel Testing


Status update:

On 6 July 2016, ICANN and Verisign successfully completed the 90-day parallel testing period of the Root Zone Management System (RZMS).

During the testing period, zero unexplained differences were found between the production RZMS and the parallel test version of the RZMS, which has the U.S. National Telecommunications and Information Administration (NTIA) authorization step removed.

You can view daily comparison reports created during the testing period on Verisign's website. Additionally, monthly progress reports for the testing period are available on ICANN's designated Root Zone Management System Parallel Testing webpage.
 

Documents/announcements posted:

90-day Root Zone Management System "Parallel Testing" Period Ends Successfully

Verisign Daily Parallel Operations Root Zone Management System Comparisons

Second RZMS Monthly Progress Report 

 

Root Zone Maintainer Agreement (RZMA)


Status update:

ICANN and Verisign have completed the discussions and negotiations for the Root Zone Maintainer Services Agreement (RZMA). On 29 June 2016, ICANN published the RZMA for a 30-day public review period.


Documents/announcements posted:

Root Zone Management Transition Update: Preservation of Security, Stability and Resiliency

Root Zone Maintainer Services Agreement
 


 

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:

As noted previously, ICANN has been collecting SLE data over the past 3 ½ months in order to propose performance targets to the SLE Design Team of the Cross Community Working Group Names (CWG-Stewardship) for their consideration.

An analysis of the aggregated data, as well as ICANN’s proposed thresholds for the SLEs, are provided in a summary report that was circulated to the community last week. ICANN will be holding a call this week to discuss the report and demo the dashboard that will be used to report on PTI’s actual performance against agreed-to thresholds with the CWG-Stewardship,


Documents/announcements posted:

Preliminary Review of Service Level Expectation Data


Mailing list:

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

 

Service Level Agreement (SLA) for the IANA Numbering Services


Status update:

ICANN and the Regional Internet Registries (RIRs) have signed the SLA for the IANA Numbering Services.

The agreement will become effective on the date of the transition.


Documents/announcements posted:

ICANN Signs Service Level Agreement with Regional Internet Registries and Finalizes 2016 Supplemental Agreement with Internet Engineering Task Force


Mailing list:

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

 

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


Status update:

ICANN has signed the 2016 Memorandum of Understanding (MoU) Supplemental Agreement with the Internet Engineering Task Force (IETF) for the performance of the protocol parameters functions.

The agreement will become effective on the date of the transition.


Documents/announcements posted:

ICANN Signs Service Level Agreement with Regional Internet Registries and Finalizes 2016 Supplemental Agreement with Internet Engineering Task Force

Memorandum of Understanding (MoU) Supplemental Agreement with the Internet Engineering Task Force (IETF)

  

Customer Standing Committee (CSC)


Status update:

The deadline for appointing organizations to send candidate selections is Friday, 22 July 2016. ICANN will then forward the appointments to the ccNSO and GNCO Councils for final approval of the full CSC membership.


Documents/announcements posted:

None.


Mailing list:

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

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

 

Root Zone Evolution Review Committee (RZERC)


Status update:

A public comment period on the RZERC draft charter was closed on 10 July 2016. In total, 7 individuals and organizations submitted comments. ICANN staff is currently finalizing an analysis of the comments received.

ICANN hopes to be able to begin forming the committee soon. The RZERC will become operational upon the successful completion of the transition.


Documents/announcements posted:

None.


Mailing list:

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

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

 

Post-transition IANA (PTI)


Status update:

There are currently three public comment periods underway for the formation of PTI. Any interested party may review and provide feedback on these important PTI formation documents.
 

1) Draft PTI Articles of Incorporation

The proposed draft of the PTI Articles of Incorporation was developed to meet the community proposal recommendation that a new legal entity be formed to perform the three IANA functions.

The Articles were drafted to the ICG and CWG-Stewardship proposals, which were developed through public processes, and adopted by the ICANN Board and transmitted to NTIA on 10 March 2016. The public comment process provides the community with an opportunity to comment on whether the drafted Articles are inconsistent with the proposals, and is not intended to be a forum for the reconsideration of the proposals.

Closes: 31 July 2016 at 23:59 UTC


2) PTI Governance Documents

The governance documents include the:

  • Draft PTI Conflict of Interest Policy
  • Draft PTI Board Code of Conduct
  • Draft PTI Expected Standard of Behavior

The Conflict of Interest Policy and Board Code of Conduct were developed to strengthen PTI’s governance practices, and the Expected Standard of Behavior was developed to guide PTI's Board, staff, customers and broader community on expected standards to guide their participation.

Each of these documents is modeled off of the versions already in force in ICANN, and the public comment period is intended to seek comments on conformance of these documents to PTI.

Closes: 7 August 2016 at 23:59 UTC


3) Draft PTI Bylaws

PTI Bylaws contains PTI's governance requirements, including composition of the Board, conduct of Board meetings, powers of the Board and PTI officers, and budgeting, planning and record keeping requirements. 

The Bylaws were drafted to meet the ICG and CWG-Stewardship proposals, which were developed through public processes, and adopted by the ICANN Board and transmitted to NTIA on 10 March 2016. The public comment process provides the community with an opportunity to comment on whether the drafted Bylaws are inconsistent with the proposals, and is not intended to be a forum for the reconsideration of the proposals.

Closes: 11 August 2016 at 23:59 UTC


In addition, ICANN has circulated to the community drafts of the ICANN-PTI contracts for review, including:


Documents/announcements posted:

Draft PTI Articles of Incorporation

Draft PTI Bylaws

Draft PTI Conflict of Interest Policy

Draft PTI Board Code of Conduct 

Draft PTI Expected Standard of Behavior

Draft Naming Function Agreement

Draft Number Subcontracting Agreement

Draft Protocol Parameter Subcontracting Agreement

Draft ICANN-PTI Intercompany Services Agreement Headers


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 Updated Articles of Incorporation


Status update:

The 40-day public comment period on ICANN’s Draft Restated Articles of Incorporation was extended by one week, and closed on 13 July 2016. In total, 6 submissions were received during the comment period.

ICANN staff is currently finalizing an analysis of the comments received.


Documents/announcements posted:

None.


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 supplemental procedures for the enhanced IRP process defined by the CCWG-Accountability in its Work Stream 1 proposal.

The IOT has held 5 meetings and all resources and archives can be found here.


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