Thank you for forwarding this Robin. Best, -Michael On Wed, Jul 27, 2016 at 12:42 AM, Robin Gross <[log in to unmask]> wrote: > Begin forwarded message: > > > *From: *Hillary Jett <[log in to unmask]> > *Date: *July 26, 2016 at 1:45:49 PM PDT > *To: *CCWG-Accountability <[log in to unmask]> > *Subject: **[CCWG-ACCT] IANA Stewardship Transition Implementation > Planning Update (Volume 4)* > > Original link: > https://www.icann.org/news/blog/iana-stewardship-transition-implementation-planning-update-volume-4 > > > 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 > <https://www.icann.org/news/announcement-2016-07-14-en> the 90-day > parallel testing period of theRoot 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 > <http://www.verisign.com/rzms-parallel-ops/index.html> 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 > <https://www.icann.org/en/stewardship-implementation/root-zone-management-system-parallel-testing> > . > > > *Documents/announcements posted:* > > 90-day Root Zone Management System "Parallel Testing" Period Ends > Successfully <https://www.icann.org/news/announcement-2016-07-14-en> > > Verisign Daily Parallel Operations Root Zone Management System Comparisons > <http://www.verisign.com/rzms-parallel-ops/index.html> > > Second RZMS Monthly Progress Report > <https://www.icann.org/iana_imp_docs/55-rzms-parallel-testing-monthly-report-2-v-06jun16> > > > Root Zone Maintainer Agreement (RZMA) > > *Status update:* > > ICANN and Verisign have completed > <https://www.icann.org/news/blog/root-zone-management-transition-update-preservation-of-security-stability-and-resiliency> > the discussions and negotiations for the Root Zone Maintainer Services > Agreement (RZMA). On 29 June 2016, ICANN published the RZMA > <https://www.icann.org/iana_imp_docs/63-root-zone-maintainer-agreement-v-1-0> for > a 30-day public review period. > > > *Documents/announcements posted:* > > Root Zone Management Transition Update: Preservation of > Security, Stability and Resiliency > <https://www.icann.org/news/blog/root-zone-management-transition-update-preservation-of-security-stability-and-resiliency> > > Root Zone Maintainer Services Agreement > <https://www.icann.org/iana_imp_docs/63-root-zone-maintainer-agreement-v-1-0> > > ------------------------------ > *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 > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160715/92175b9a/PreliminarySLEData-0001.pdf> > 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 > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160715/92175b9a/PreliminarySLEData-0001.pdf> > > > *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 > <https://www.icann.org/news/announcement-2016-06-29-en> the SLA for the > IANA Numbering Services > <https://www.nro.net/wp-content/uploads/ICANN-RIR-SLA-signature25May16.pdf> > . > > 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 > <https://www.icann.org/news/announcement-2016-06-29-en> > > > *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) > <https://www.icann.org/iana_imp_docs/59-2016-icann-ietf-mou-supplemental-agreement-v-1-0> > 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 > <https://www.icann.org/news/announcement-2016-06-29-en> > > Memorandum of Understanding (MoU) Supplemental Agreement with the Internet > Engineering Task Force (IETF) > <https://www.icann.org/iana_imp_docs/59-2016-icann-ietf-mou-supplemental-agreement-v-1-0> > > > Customer Standing Committee (CSC) > > *Status update:* > > The deadline for appointing organizations to send candidate selections is > Friday, 22 July 2016. ICANNwill 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 > <https://www.icann.org/public-comments/draft-rzerc-charter-2016-06-10-en>. > 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 > <https://www.icann.org/public-comments/draft-pti-articles-incorporation-2016-07-01-en> > > 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 > <https://www.icann.org/public-comments/pti-governance-documents-2016-07-08-en> > > 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 > <https://www.icann.org/public-comments/draft-pti-bylaws-2016-07-12-en>* > > 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: > > · Draft Naming Function Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/NamingFunctionAgreement-Draftasof15July2016-0001.pdf> > > · Draft Number Subcontracting Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/RIRSubcontractAgreement-Draftasof15July2016-0001.pdf> > > · Draft Protocol Parameter Subcontracting Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/IETFSubcontractAgreement-Draftasof15July2016-0001.docx> > > · Draft ICANN-PTI Intercompany Services Agreement headers > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/ICANN-PTIServicesAgreementHeaders-Draftasof15July2016-0001.pdf> > > > *Documents/announcements posted:* > > Draft PTI Articles of Incorporation > <https://www.icann.org/en/system/files/files/draft-pti-articles-incorporation-01jul16-en.pdf> > > Draft PTI Bylaws > <https://www.icann.org/en/system/files/files/draft-pti-bylaws-12jul16-en.pdf> > > Draft PTI Conflict of Interest Policy > <https://www.icann.org/en/system/files/files/draft-pti-coi-08jul16-en.pdf> > > Draft PTI Board Code of Conduct > <https://www.icann.org/en/system/files/files/draft-pti-code-of-conduct-08jul16-en.pdf> > > > Draft PTI Expected Standard of Behavior > <https://www.icann.org/en/system/files/files/draft-pti-expected-standards-08jul16-en.pdf> > > Draft Naming Function Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/NamingFunctionAgreement-Draftasof15July2016-0001.pdf> > > Draft Number Subcontracting Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/RIRSubcontractAgreement-Draftasof15July2016-0001.pdf> > > Draft Protocol Parameter Subcontracting Agreement > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/IETFSubcontractAgreement-Draftasof15July2016-0001.docx> > > Draft ICANN-PTI Intercompany Services Agreement Headers > <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20160716/63d8860e/ICANN-PTIServicesAgreementHeaders-Draftasof15July2016-0001.pdf> > > > *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 > <https://forum.icann.org/lists/comments-draft-restated-articles-incorporation-27may16/> > 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) > <https://community.icann.org/pages/viewpage.action?pageId=59643726>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 <https://community.icann.org/display/WEIA/IRP-IOT+Meetings>. > > > *Documents/announcements posted:* > > None. > > > *Mailing list:* > > http://mm.icann.org/pipermail/iot/ > > > _______________________________________________ > Accountability-Cross-Community mailing list > [log in to unmask] > https://mm.icann.org/mailman/listinfo/accountability-cross-community > > >