[CCWG-ACCT] [blog] IANA Stewardship Transition Implementation Planning Update (Volume 3)

Fri Jun 3 21:46:14 UTC 2016

Original link:  https://www.icann.org/news/blog/iana-stewardship-transition-implementation-planning-update-volume-3

IANA Stewardship Transition Implementation Planning Update (Volume 3)
ICANN is compiling weekly 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 to remove NTIA's Root Zone Administrator (RZA) role, parallel testing of the production and parallel test system 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:

We are 58 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.

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 have nearly finalized the last outstanding details of the RZMA. The agreement will be posted publicly once it is finalized. 

Documents/announcements posted:

None.

Stewardship Transition
The Stewardship Transition planning track contains projects to prepare relationship documentations 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:
Fix an inconsistency in the “Content” section
Update the document to remove references to Annex A and refer to section 4.3 for a general description of services
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 MoUSupplemental 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:

CSC Scope and Responsibilities

CSC Candidates Qualification Requirements

CSC Charter

CSC Charter FAQ

CSC Charter Clarification

Request for Appointment of Members and Liaisons to the CSC

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 will be posted for public comment.

Documents/announcements posted this week:

Draft RZERC Charter (v5)

Mailing list:

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

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

Post-Transition IANA (PTI)

Status update:

Formation documents for the PTI were circulated to the community on 13 May 216. ICANN is currently working with the community and their 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 is 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 updateICANN’s governance documents, and to operationalize new community powers defined by the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability).

Amending ICANN's Bylaws

Status update:

ICANN's legal team distributed the summary and analysis of Public Comments and the proposed revisedICANN 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.
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
On 27 May 2016, the ICANN Board issued resolutions (2016.05.27.01-2016.05.27.04) adopting the newICANN 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/

 Independent Review Process (IRP)

Status update:

The CCWG-Accountability formed a Working Party called the IRP Implementation Oversight Team (IOT)to define the enhanced IRP procedures. This work is intended to operationalize the IRP enhancements that were defined by the CCWG-Accountability in its Work Stream 1 proposal.

Documents/announcements posted:

None.

Mailing list:

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160603/8f4ce770/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4590 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160603/8f4ce770/smime-0001.p7s>