[NCUC-DISCUSS] [Info] IANA Stewardship Transition Planning Update
aicha chebbi
a.j.chebbi at gmail.com
Thu Apr 28 22:59:27 CEST 2016
Thank you.
Le 28 avr. 2016 9:54 PM, "romina florencia Cabrera" <romicabrera83 at gmail.com>
a écrit :
> thank you
>
> 2016-04-27 21:47 GMT-03:00 Rafik Dammak <rafik.dammak at gmail.com>:
>
>> Hi everyone.
>>
>> please find below an update regarding the IANA stewardship transition
>> planning. Those involved in the CWG (Cross-Community Working Group on IANA
>> Stewardship transition) can add some context and background to this.
>>
>> Best Regards,
>>
>> Rafik
>>
>>
>> ---------- Forwarded message ----------
>>
>>
>> Original link:
>> https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1
>>
>> IANA Stewardship Transition Planning Update (Volume 1)
>>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>> <https://www.icann.org/news/blog/iana-stewardship-transition-planning-update-volume-1#>
>>
>> This update marks the beginning of an initiative mentioned by Akram
>> Atallah in his 12 April 2016 blog, aimed at keeping interested stakeholders
>> up to date on the latest developments and progress relating to
>> implementation planning for the IANA Stewardship Transition, the
>> proposal for which is currently under review by NTIA.
>>
>> These updates will detail what work has been identified based on the
>> proposals of the IANA Stewardship Transition Coordination Group (ICG)
>> and the Cross Community Working Group on Enhancing ICANN Accountability
>> (CCWG-Accountability), and provide insight into what is happening on a
>> week-to-week basis.
>>
>> Our goal is to provide consistent, structured updates that give any
>> interested party access to latest information, documents and announcements.
>> We will also post direct links to the mailing lists where conversations are
>> taking place on each of the planning elements.
>>
>> ICANN has identified work that must be completed for the transition to
>> occur successfully. The planned work has been mapped across 14 projects
>> and grouped into 3 tracks. You can find more information on the ICANN
>> website here <https://www.icann.org/stewardship-implementation>.
>>
>> *- Trang Nguyen, Senior Director of Strategic Programs*
>>
>>
>> *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 systems; and the development, and execution of an
>> agreement with Verisign as the root zone maintainer.*
>>
>> Root Zone Management System (RZMS) Parallel Testing
>>
>> *Status update:*
>>
>> In accordance with the plan
>> <https://www.ntia.doc.gov/files/ntia/publications/root_zone_administrator_proposal-relatedtoiana_functionsste-final.pdf> submitted
>> to NTIA, ICANN and Verisign completed system code changes and began a
>> 90-day “parallel testing” period on Wednesday, 6 April 2016. This is a key
>> planning step to ensure the continued security and stability of the Root
>> Zone Management System (RZMS) operation after the successful completion
>> of the IANA Stewardship Transition, currently projected for September
>> 30, 2016.
>>
>> It has been almost 3 weeks since the start of parallel testing and
>> everything is going smoothly. Click here to view Verisign’s daily Parallel
>> Operations Root Zone Management System Comparisons
>> <http://www.verisign.com/rzms-parallel-ops/index.html> 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:*
>>
>> % ICANN and Verisign Announce Start of 90-day Root Zone Management
>> System “Parallel Testing” Period
>> <https://www.icann.org/news/announcement-2016-04-08-en>
>>
>> 2 Verisign Daily Parallel Operations Root Zone Management System
>> Comparisons <http://www.verisign.com/rzms-parallel-ops/index.html>
>>
>> *Mailing list(s):*
>>
>> None.
>> Root Zone Maintainer Agreement (RZMA)
>>
>> *Status update:*
>>
>> ICANN and Verisign continue to engage in discussion to prepare for a
>> RZMA. The current plan for completion of a draft RZMA is the end of this
>> month.
>>
>> *Documents/announcements posted:*
>>
>> None.
>>
>> *Mailing list(s):*
>>
>> None.
>>
>>
>> *Stewardship Transition*
>>
>> *The Stewardship Transition planning track contains projects to prepare
>> relationship documentation 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 Agreement (SLA) for the IANA Numbering Services
>>
>> *Status update:*
>>
>> On Wednesday, 20 April 2016, the Number Resource Organization (NRO)
>> published an announcement
>> <https://www.nro.net/news/updated-5-1-and-signature-version-of-the-sla-for-the-iana-numbering-services>
>> regarding version 5.1 of the SLA document.
>>
>> The SLA will be submitted to the ICANN Board for consideration and
>> adoption when the NRO andICANN establish a mutually agreed upon date.
>>
>> *Documents/announcements posted:*
>>
>> % Updated 5.1 and Signature Version of the SLA for the IANA Numbering
>> Services
>> <https://www.nro.net/news/updated-5-1-and-signature-version-of-the-sla-for-the-iana-numbering-services>
>>
>> 2 Service Level Agreement for IANA Numbering Services (v5.1)
>> <https://www.nro.net/wp-content/uploads/SLAv5-proposedfinal-clean.pdf>
>>
>> *Mailing list(s):*
>>
>> + https://www.nro.net/pipermail/ianaxfer/
>> Post-Transition IANA (PTI)
>>
>> *Status update:*
>>
>> ICANN continues to work on the plan for PTI implementation that the
>> Implementation Oversight Task Force (IOTF) requested, as well as the
>> ICANN-PTI contract.
>> *What is the IOTF?*
>> The IOTF was formed following ICANN55 in Marrakech. The IOTF offers a
>> channel for ICANN to request insights or clarifications to ensure that
>> ICANN and the community remain aligned on ICANN’s implementation
>> planning efforts of the ICG Proposal. The group was formed to include
>> the co-Chairs and Design Team leads of the Cross Community Working Group to
>> Develop an IANA Stewardship Transition Proposal on Naming Related
>> Functions (CWG-Stewardship), and has since grown to also include
>> representatives from the ICG, Numbering Resources community and Protocol Parameters
>> community.
>>
>>
>> *Documents/announcements posted this week:*
>>
>> None.
>>
>> *Mailing list:*
>>
>> + http://mm.icann.org/pipermail/iotf/
>> Root Zone Evolution Review Committee (RZERC)
>>
>> *Status update:*
>>
>> ICANN continues to work with the IOTF to finalize the terms of the RZERC
>> Charter. A revised charter
>> <http://mm.icann.org/pipermail/iotf/attachments/20160426/405cdac1/DRAFTRZERCCharter-V3-CLEAN-0001.docx> was
>> circulated to the IOTF on 25 April 2016.
>>
>> *Documents/announcements:*
>>
>> 2 Root Zone Evolution Review Committee (RZERC) Charter (v3)
>> <http://mm.icann.org/pipermail/iotf/attachments/20160426/405cdac1/DRAFTRZERCCharter-V3-CLEAN-0001.docx>
>>
>> *Mailing list:*
>>
>> + http://mm.icann.org/pipermail/iotf/
>> IANA Customer Service Escalation Mechanism
>>
>> *Status update:*
>>
>> ICANN received clarification
>> <http://mm.icann.org/pipermail/iotf/2016-April/000056.html> from the
>> IOTF regarding the IANA Customer Service Complaint Resolution Process
>> for Naming Related Functions and IANA Problem Resolution Process (for
>> IANA naming services only) referenced in Annex I and J of the
>> CWG-Stewardship proposal
>> <https://community.icann.org/pages/viewpage.action?pageId=53779816>.
>>
>> As next step, ICANN will update relevant process documentations for
>> these processes.
>>
>> *Documents/announcements:*
>>
>> None.
>>
>> *Mailing list:*
>>
>> + http://mm.icann.org/pipermail/iotf/
>>
>>
>> Accountability Enhancements
>>
>> *The Accountability Enhancements track contains plans to implement
>> 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 ICANNAccountability (CCWG-Accountability).*
>> ICANN's Bylaws
>>
>> *Status update:*
>>
>> ICANN has posted proposed draft new Bylaws for a 30-day public comment
>> from *21 April - 21 May 2016* to allow any interested party to review
>> and provide feedback.
>>
>> 2 Public Comment Page
>> <https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en>
>>
>> + Submit Comment to Forum
>> <http://comments-draft-new-bylaws-21apr16@icann.org/>
>>
>> + Comments Forum
>> <http://forum.icann.org/lists/comments-draft-new-bylaws-21apr16/>
>>
>> The proposed draft of the new ICANN Bylaws was developed collaboratively
>> by the ICANN legal team and the independent counsel hired to advise the
>> CCWG-Accountability and the CWG-Stewardship.
>>
>> In developing the draft new ICANN Bylaws, the attorneys consulted a
>> Bylaws Coordination Group populated with both community and Board members,
>> as well as with the CWG-Stewardship and the CCWG-Accountability.
>>
>> Adoption of the new Bylaws by the ICANN Board is anticipated for on or
>> around 27 May 2016. Once new ICANN Bylaws have been adopted, ICANN will
>> notify NTIA. Once adopted, the Bylaws are expected to go into effect if
>> NTIA approves of the IANA Stewardship Transition Proposal and the IANA Functions
>> Contract expires.
>>
>> *Documents/announcements:*
>>
>> 2 Draft New ICANN Bylaws
>> <https://www.icann.org/en/system/files/files/proposed-new-bylaws-20apr16-en.pdf>
>>
>> 2 Comparison of Draft New ICANN Bylaws to Current Bylaws
>> <https://www.icann.org/en/system/files/files/proposed-new-bylaws-redline-20apr16-en.pdf>
>>
>> *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/
>>
>>
>>
>> _______________________________________________
>> Ncuc-discuss mailing list
>> Ncuc-discuss at lists.ncuc.org
>> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>>
>>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20160428/1fc03b2c/attachment-0002.html>
More information about the Ncuc-discuss
mailing list