June 2016 - CWG-Stewardship

Draft Provisions for PTI Bylaws/Contract-Annex C (Sections 7and 8)
by Lise Fuhr July 20, 2016

July 20, 2016

Dear CWG, As you might recall we have earlier discussed how to ensure that Annex C section 7 and 8, from the CWG Proposal, could be ensured in the PTI Bylaws and Contract. Sidley has sent the attached draft which we will cover at the next CWG call as part of the Client Committee update. Best, Jonathan and Lise

2 1

FW: [IOTF] Revised PTI staffing rationale
by Jonathan Robinson July 7, 2016

July 7, 2016

All, Please be aware of this recently published revised PTI staffing positon from ICANN's implementation team. Lise & Jonathan From: Yuko Green [mailto:yuko.green@icann.org] Sent: 24 June 2016 02:06 To: iotf(a)icann.org Subject: [IOTF] Revised PTI staffing rationale Dear members of IOTF, Attached, please find the revised PTI staffing rationale that reflects the discussion from the last IOTF call #13. We welcome any feedback you may have. Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: <mailto:yuko.green@icann.org> yuko.green(a)icann.org <http://www.icann.org/> www.icann.org

2 2

Implementation Planning Update (Volume 3)
by Grace Abuhamad July 7, 2016

July 7, 2016

Original link: https://www.icann.org/news/blog/iana-stewardship-transition-implementation-… 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 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 is currently posted for a 30-day public comment period through 10 July 2016. · Public Comment Forum · Submit Comment to Forum · Comments Forum 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 updateICANN’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 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/ 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. · Public Comment Page · Submit a Comment to the Forum · Comments Forum 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: · Draft Restated Articles of Incorporation [PDF, 78 KB] · Comparison of draft Restated Articles to Current Articles [PDF, 75 KB] 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:

4 3

ICANN 56: IANA Stewardship Transition Implementation Planning Update - recordings available
by Yuko Green June 30, 2016

June 30, 2016

Dear members of IOTF and CWG, Thank you for your participation in the IANA Stewardship Transition Implementation Planning Update session in Helsinki today. For those of you who missed the live presentation, here is the audio and AC room recordings: AC Room: https://icann.adobeconnect.com/p3vd5t893rd/ Audio: https://www.icann.org/uploads/iana_work_session_asset/attachment/361/1467302 978861ICANN56_IANA_Stewardship_Transition_Implementation_Planning_Update.mp3 The transcript and the presentation materials will be posted in the coming days at https://www.icann.org/stewardship-implementation under "Meetings & Work Sessions" section. For those that are traveling, have a safe trip back home! Regards, Yuko Green Strategic Programs Manager Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: <mailto:yuko.green@icann.org> yuko.green(a)icann.org <http://www.icann.org/> www.icann.org

1 0

Update on the RZMA
by Grace Abuhamad June 30, 2016

June 30, 2016

Dear all, The RZMA can be found here: https://www.icann.org/iana_imp_docs/63-root-zone-maintainer-agreement-v-1-0. This agreement is posted for a 30-day public review period before it will be signed. In addition, ICANN has published the Proposed Amendment to .COM Registry Agreement for a 43-day public comment period. The public comment page is here: https://www.icann.org/public-comments/com-amendment-2016-06-30-en and the public comment will run through 12 August 2016. The blog below is a starting point should you have any questions. Best, Grace From: <cwg-stewardship-bounces(a)icann.org> on behalf of Grace Abuhamad <grace.abuhamad(a)icann.org> Date: Tuesday, June 28, 2016 at 4:04 PM To: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: [CWG-Stewardship] Root Zone Management Transition Update: Preservation of Security, Stability and Resiliency Original link: https://www.icann.org/news/blog/root-zone-management-transition-update-pres… Root Zone Management Transition Update: Preservation of Security, Stability and Resiliency On March 4, 2015, the U.S. National Telecommunications and Information Administration (NTIA) officially requested that ICANN and Verisign work together to develop a proposal on how best to transition theNTIA administrative role associated with root zone management in a manner that maintains the security and stability of the Internet’s domain name system. NTIA previously announced that the transition of this aspect of its administrative role was a process separate from but parallel to the IANA stewardship transition. Verisign and ICANN submitted a proposal to NTIA that contained two primary elements. First, the teams would build and test a parallel root zone management system that would simulate root zone management functions without NTIA’s current authorization role. That system is now approaching the completion of its 90-day defect free testing phase. Second, in anticipation of the release of Verisign from root zone management obligations by NTIA under the Cooperative Agreement, the teams began work on a commercial agreement between ICANN and Verisign for the continued performance of root zone management functions. We are pleased to announce that ICANN and Verisign have completed the discussions and negotiations for the root zone maintainer services agreement (RZMA). Since the early days of the Internet, Verisign has been providing “registration services” under its Cooperative Agreement with NTIA, which was broadly defined to include root zone management functions and Top Level Domain registry services. NTIA recognized that root zone management aspects of the IANA functions contract are “inextricably intertwined” with the Cooperative Agreement. Given the unified nature of the present Cooperative Agreement, much of the root zone infrastructure itself is “inextricably intertwined” with Verisign’s TLD operations for .com: the servers that provide root services are hosted at every .com resolution site (over 100 locations). These servers share bandwidth, routing and monitoring with the .com operations, and the servers use the same code base as the .com TLDname servers and are operated and maintained by the same operation and engineering group. On the provisioning side, the root zone’s provisioning system is derived from the .com Shared Registration System (SRS), using the structure, schema, and software used for .com provisioning operations. Verisign builds and signs the root zone today using the same cryptographic facilities used for .com as well as signing software derived from that used for signing .com. Importantly, Verisign’s root zone operations are also within the .com’s Denial of Service attack detection and mitigation framework including independent internal and external monitoring and packet filtering at all layers. A key component of ensuring security of the root operations was making sure that those operations continued to benefit from its historic association with the .com operations. The RZMA is intended to maintain stable, secure, and reliable operations of the root zone not only for direct root zone management service customers (Registry Operators, Registrars and Root Server Operators), but also to maintain the security and stability of the Internet’s domain name system. This was achieved by a simple extension of the .com Registry Agreement to coincide with the term of the new RZMA. Regarding the RZMA, some of the key features include: · Requiring Verisign and ICANN to work together in good faith to preserve the security, stability and resiliency of the root zone and root zone management system consistent with the security and stability of the Internet. · Detailing ICANN’s responsibility to authenticate, verify, and submit to Verisign changes to the service data comprised in the Root Zone File. · Establishing service level requirements for Verisign to process, edit, generate and publish the Root Zone File, including an accelerated path to update the service data in the Root Zone File in cases of emergency. · Describing ICANN and Verisign’s key-signing obligations, which are to be performed in a secure, transparent and accountable manner. · Providing that the integrity of the service data of the Root Zone File and the Verisign systems performing the root zone maintainer function will be operated under a business continuity plan with the same product support level as maintained by the .com DNS resolution service and .com SRS, respectively. · Setting forth that Verisign will participate as a member of the future Root Zone Evolution Review Committee. · Providing for continuity of the security and stability of the root zone through a one-year transition process which may be initiated by a community driven process under which Verisign continues to perform the root zone maintainer function while ICANN implements a public RFP process to identify and onboard a new provider. · Setting out the development of an emergency transition process for extraordinary events. · Requiring ICANN and Verisign to meet quarterly to prioritize potential changes and updates to the services, including service levels and to prioritize a roadmap for implementation of such changes that may be effected through a built in change control process. What’s left to be done? Soon, we will post the RZMA for public review and the .com registry agreement amendment for public comment, after which our respective boards of directors will be asked to approve the agreements. The .com extension will be sent to NTIA for review and approval according to their processes. -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE.

1 0

Re: [CWG-Stewardship] Updated draft of responses in PTI Bylaws-AoI table
by Seun Ojedeji June 30, 2016

June 30, 2016

Hi, I assume it's the board votes that would determine who is more qualified and not any external sources, other than that, my +1 to Chuck's suggested edit. Regards Sent from my LG G4 Kindly excuse brevity and typos On 28 Jun 2016 4:41 p.m., "Gomes, Chuck" <cgomes(a)verisign.com> wrote: Greg/James, Are you saying that you believe the chair must be one of the NomCom appointees? If so, what if neither of the non-Nom nominated directors is as qualified as one of the ICANN appointed directors (excluding he PTI President) or if the NomCom nominated directors are not able to commit the extra time needed to be chair? Why limit the possibilities? It seems to me that we would want the best qualified leader to serve as Board chair. I agree with Seun’s concern but I would be okay with language along this line: “The Board chair should be one of the NomCom appointees unless they are unable to serve in that capacity or if one of the other directors (excluding the President) are more qualified.” Chuck *From:* cwg-stewardship-bounces(a)icann.org [mailto: cwg-stewardship-bounces(a)icann.org] *On Behalf Of *Greg Shatan *Sent:* Tuesday, June 28, 2016 3:07 AM *To:* James Gannon *Cc:* Lise Fuhr; cwg-stewardship(a)icann.org *Subject:* Re: [CWG-Stewardship] Updated draft of responses in PTI Bylaws-AoI table Agee with Matt and James. Greg On Tue, Jun 28, 2016 at 2:42 AM, James Gannon <james(a)cyberinvasion.net> wrote: Agree with Matt for the record. -J *From: *<cwg-stewardship-bounces(a)icann.org> on behalf of Matthew Shears < mshears(a)cdt.org> *Date: *Tuesday 28 June 2016 at 09:34 *To: *Seun Ojedeji <seun.ojedeji(a)gmail.com> *Cc: *Lise Fuhr <lise.fuhr(a)difo.dk>, "cwg-stewardship(a)icann.org" < cwg-stewardship(a)icann.org> *Subject: *Re: [CWG-Stewardship] Updated draft of responses in PTI Bylaws-AoI table To be clear I don't agree with the proposed change by Seun to 5.4 for the reasons that were fully discussed in the meeting in which we agreed the text. On Tuesday, 28 June 2016, Seun Ojedeji <seun.ojedeji(a)gmail.com> wrote: Dear Co-Chairs, May I know if these comments of mine are received and would be implemented as proposed especially as there is no opposition on the suggestions from the list? Regards Sent from my LG G4 Kindly excuse brevity and typos On 27 Jun 2016 01:49, "Seun Ojedeji" <seun.ojedeji(a)gmail.com> wrote: Hello, Somehow this skipped my raider, while this is already late, i could not come swallow 2 points from the final text. Section 5.4: I am quite concerned and wonder why we include the following text: "The Chairperson should be a NomCom nominated director". The board does the selection of chair person, so there is NO reason why ICANN appointed board member cannot be the chairperson if the board wants it. I don't think i dig turning the nomcom nominees into the defacto source of chairperson-hood. It seem to me that we are seeing them as more superior and trustworthy that the rest which is not necessarily always the case. Ofcourse i am with the rest of the response to that question. Section 7.1: I am concerned by this conclusion "The Corporation will not need additional officers therefore the board does not need this capability." as i think its an unnecessary lock-in and can have unforeseen implications in future. I will be fine with something that reads like below: "The Corporation should not need additional officers therefore the board may not need this capability. However such may be done with a unanimous votes from board subject to member(s) approval." Regards On Thu, Jun 16, 2016 at 9:41 PM, Grace Abuhamad <grace.abuhamad(a)icann.org> wrote: Dear all, Following the CWG-Stewardship call today, here attached are the latest redline and clean versions of the PTI response table to deliver to Sidley. Please review in the next 24h before we consider these final. Thank you, Grace -- *Grace Abuhamad* Manager, Public Policy *ICANN | Internet Corporation for Assigned Names and Numbers* 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 *Interested in the IANA Stewardship Transition? * *LEARN MORE <https://www.icann.org/stewardship-accountability>. STAY UPDATED <https://www.icann.org/stewardship-accountability#status>. FOLLOW <https://twitter.com/icann>. ENGAGE <https://www.icann.org/stewardship-accountability#involved>. * *From: *<iotf-bounces(a)icann.org> on behalf of Grace Abuhamad < grace.abuhamad(a)icann.org> *Date: *Wednesday, June 15, 2016 at 6:49 PM *To: *"Gomes, Chuck" <cgomes(a)verisign.com>, "iotf(a)icann.org" <iotf(a)icann.org > *Cc: *"cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> *Subject: *Re: [IOTF] Updated draft of responses in PTI Bylaws-AoI table Good catch Chuck. Per your comment and Matthew’s agreement, I was supposed to delete the sentence beginning with “Member approval NOT required….”. I’ll make the edit in the Google doc and await any further comments before circulating a new version in time for the CWG call. Thank you, Grace -- *Grace Abuhamad* Manager, Public Policy *ICANN | Internet Corporation for Assigned Names and Numbers* 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 *Interested in the IANA Stewardship Transition? * *LEARN MORE <https://www.icann.org/stewardship-accountability>. STAY UPDATED <https://www.icann.org/stewardship-accountability#status>. FOLLOW <https://twitter.com/icann>. ENGAGE <https://www.icann.org/stewardship-accountability#involved>. * *From: *"Gomes, Chuck" <cgomes(a)verisign.com> *Date: *Wednesday, June 15, 2016 at 6:35 PM *To: *Grace Abuhamad <grace.abuhamad(a)icann.org>, "iotf(a)icann.org" < iotf(a)icann.org> *Cc: *"cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> *Subject: *RE: Updated draft of responses in PTI Bylaws-AoI table The edits look good to me. Was the second option in Section 7.6.1 supposed to be deleted? “Board may approve delegation of responsibilities or powers of President. Member approval NOT required for the prescription of additional duties by the board to the President.[1] <#m_3446823907640759009_m_-5374238543218927457_m_42350650225925> [2] <#m_3446823907640759009_m_-5374238543218927457_m_42350650225925> Member approval required for the prescription of additional powers by the board to the President.” Chuck *From:* iotf-bounces(a)icann.org [mailto:iotf-bounces@icann.org <iotf-bounces(a)icann.org>] *On Behalf Of *Grace Abuhamad *Sent:* Wednesday, June 15, 2016 5:16 PM *To:* iotf(a)icann.org *Cc:* cwg-stewardship(a)icann.org *Subject:* [IOTF] Updated draft of responses in PTI Bylaws-AoI table Dear all, Per the discussion on today’s IOTF call, here attached is a redline version of the edits discussed on the call and a clean version to present to the CWG-Stewardship on Thursday. Thank you for your patience in the live editing process! --Grace -- *Grace Abuhamad* Manager, Public Policy *ICANN | Internet Corporation for Assigned Names and Numbers* 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 *Interested in the IANA Stewardship Transition? * *LEARN MORE <https://www.icann.org/stewardship-accountability>. STAY UPDATED <https://www.icann.org/stewardship-accountability#status>. FOLLOW <https://twitter.com/icann>. ENGAGE <https://www.icann.org/stewardship-accountability#involved>. * *From: *Grace Abuhamad <grace.abuhamad(a)icann.org> *Date: *Monday, June 13, 2016 at 4:47 PM *To: *<iotf(a)icann.org> *Cc: *"cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> *Subject: *Reminder: Please review the responses in PTI Bylaws table Dear all, In absence of the IOTF call today, I would just like to remind you to take some time to review the Google doc table of CWG responses on the PTI Bylaws. There are some notes and live edits made during the last IOTF call, and some comments from Chuck and Avri. The link to the document is: https://docs.google.com/document/d/1rmsp569qRxkWtNSNrJsZzENxFKLwbXVcTDWSGZJ… . I think (but will let the Chairs confirm) that the plan is still to have CWG-Stewardship sign-off in time (or during) the CWG-Stewardship meeting on Thursday 16 June. Following group sign-off, the Client Committee would then be able to share the responses with Sidley for incorporation into the PTI Bylaws. Thank you, Grace -- *Grace Abuhamad* Manager, Public Policy *ICANN | Internet Corporation for Assigned Names and Numbers* 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 *Interested in the IANA Stewardship Transition? * *LEARN MORE <https://www.icann.org/stewardship-accountability>. STAY UPDATED <https://www.icann.org/stewardship-accountability#status>. FOLLOW <https://twitter.com/icann>. ENGAGE <https://www.icann.org/stewardship-accountability#involved>. * *From: *Grace Abuhamad <grace.abuhamad(a)icann.org> *Date: *Wednesday, June 8, 2016 at 6:00 PM *To: *<iotf(a)icann.org> *Cc: *"cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> *Subject: *Process for IANA Bylaws - CWG Questions & Issues from Sidley Dear all, Per the email below, steps 1 & 2 have been completed: the CWG-Stewardship Chairs have provided initial responses, and the staff have matched these responses to the transcript of the CWG-Stewardship meeting from last week. The initial responses are available in a Google doc for the IOTF’s comments at: https://docs.google.com/document/d/1rmsp569qRxkWtNSNrJsZzENxFKLwbXVcTDWSGZJ…. Please note that the CWG-Stewardship list is copied for information. Anyone on either of these lists should feel free to review and comment on the initial responses, but the responsibility lies primarily with the IOTF at this stage. I will let the Chairs clarify the timeline for review, but my understanding is that we would like to have CWG-Stewardship sign-off in time (or during) the CWG-Stewardship meeting on Thursday 16 June. Following group sign-off, the Client Committee would then be able to share the responses with Sidley for incorporation into the PTI Bylaws. Thank you, Grace -- *Grace Abuhamad* Manager, Public Policy *ICANN | Internet Corporation for Assigned Names and Numbers* 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 *Interested in the IANA Stewardship Transition? * *LEARN MORE* <https://www.icann.org/stewardship-accountability>*. **STAY UPDATED* <https://www.icann.org/stewardship-accountability#status>*. * *FOLLOW* <https://twitter.com/icann>*. **ENGAGE* <https://www.icann.org/stewardship-accountability#involved>*. * *From: *<cwg-stewardship-bounces(a)icann.org> on behalf of Jonathan Robinson < jrobinson(a)afilias.info> *Organization: *Afilias *Reply-To: *Jonathan Robinson <jrobinson(a)afilias.info> *Date: *Monday, June 6, 2016 at 4:04 AM *To: *"cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> *Subject: *[CWG-Stewardship] Process for IANA Bylaws - CWG Questions & Issues from Sidley All, The substance and process for dealing with CWG Bylaws was discussed this on last week’s CWG call and then followed up by Lise & myself. Based on the discussions within the CWG, we propose the following course of action in order to get through the work as efficiently as possible. 1. Chairs will make a first attempt at answering / providing relevant input on the Sidley questions 2. Staff will review chairs’ input for consistency with the CWG meeting discussions 3. Answers / input to be shared with IOTF group for further review / development 4. Answers / input to be shared with CWG for further review / development 5. Answers / input to be shared via Client Committee with Sidley for incorporation into IANA Bylaws Thank-you Lise & Jonathan ------------------------------ I lean toward this approach. It seems to me that the PTI Board should have this authority on its own; also, it would cause delays if they had to wait to get ICANN approval, causing unnecessary delays. for so long as such powers were strictly limited according to the PTI mission/role etc. _______________________________________________ IOTF mailing list IOTF(a)icann.org https://mm.icann.org/mailman/listinfo/iotf -- ------------------------------------------------------------------------ *Seun Ojedeji, Federal University Oye-Ekiti web: * *http://www.fuoye.edu.ng <http://www.fuoye.edu.ng> **Mobile: +2348035233535 <%2B2348035233535>* *alt email:seun.ojedeji@fuoye.edu.ng <email%3Aseun.ojedeji(a)fuoye.edu.ng>* Bringing another down does not take you up - think about your action! _______________________________________________ IOTF mailing list IOTF(a)icann.org https://mm.icann.org/mailman/listinfo/iotf _______________________________________________ CWG-Stewardship mailing list CWG-Stewardship(a)icann.org https://mm.icann.org/mailman/listinfo/cwg-stewardship _______________________________________________ CWG-Stewardship mailing list CWG-Stewardship(a)icann.org https://mm.icann.org/mailman/listinfo/cwg-stewardship

3 5

Re: [CWG-Stewardship] Now--> Implementation Planning Update in Helsinki
by Grace Abuhamad June 30, 2016

June 30, 2016

Dear all, Please see attached the presentation from today’s implementation update. Best, Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: <cwg-stewardship-bounces(a)icann.org> on behalf of Grace Abuhamad <grace.abuhamad(a)icann.org> Date: Thursday, June 30, 2016 at 12:34 PM To: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: [CWG-Stewardship] Now--> Implementation Planning Update in Helsinki Please join us to the IANA Stewardship Transition Implementation Planning Update in Helsinki. This session will provide an update on implementation planning activities and timelines associated with the IANA Stewardship Transition, jointly presented by IOTF and ICANN. Agenda: · Opening Remarks · Implementation Updates · Q&A Adobe Connect: https://icann.adobeconnect.com/hel56-veranda1 English Audio Stream (HIGH): http://stream.icann.org:8000/hel56-veranda1-en.m3u English Audio Stream (LOW): http://stream.icann.org:8000/hel56-veranda1-en-lo.m3u -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE.

1 0

Now--> Implementation Planning Update in Helsinki
by Grace Abuhamad June 30, 2016

June 30, 2016

Please join us to the IANA Stewardship Transition Implementation Planning Update in Helsinki. This session will provide an update on implementation planning activities and timelines associated with the IANA Stewardship Transition, jointly presented by IOTF and ICANN. Agenda: · Opening Remarks · Implementation Updates · Q&A Adobe Connect: https://icann.adobeconnect.com/hel56-veranda1 English Audio Stream (HIGH): http://stream.icann.org:8000/hel56-veranda1-en.m3u English Audio Stream (LOW): http://stream.icann.org:8000/hel56-veranda1-en-lo.m3u -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE.

1 0

ICANN Signs SLA with RIRs and Finalizes 2016 Supplemental Agreement with IETF
by Grace Abuhamad June 29, 2016

June 29, 2016

Original link: https://www.icann.org/news/announcement-2016-06-29-en ICANN Signs Service Level Agreement with Regional Internet Registries and Finalizes 2016 Supplemental Agreement with Internet Engineering Task Force Today the Regional Internet Registries (RIRs) and the Internet Corporation for Assigned Names and Numbers (ICANN) signed the Service Level Agreement (SLA) for the IANA Numbering Services at ICANN56 in Helsinki, Finland. This agreement will become effective on the date of the transition. To read more and review this agreement, which documents the planned arrangements for provision of IANA numbering services after the IANA Stewardship Transition, please visit here. ICANN also finalized a Memorandum of Understanding (MoU) Supplemental Agreement with the Internet Engineering Task Force (IETF) for the performance of the protocol parameters functions. This is one of the requirements of the IANA Stewardship Transition package of proposals. This agreement will become effective on the date of the transition. Review the MoU Supplemental Agreement here [PDF, 147 KB].

1 0

Re: [CWG-Stewardship] [IOTF] Updated draft of responses in PTI Bylaws-AoI table
by Grace Abuhamad June 28, 2016

June 28, 2016

Dear all, Following the CWG-Stewardship call today, here attached are the latest redline and clean versions of the PTI response table to deliver to Sidley. Please review in the next 24h before we consider these final. Thank you, Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: <iotf-bounces(a)icann.org> on behalf of Grace Abuhamad <grace.abuhamad(a)icann.org> Date: Wednesday, June 15, 2016 at 6:49 PM To: "Gomes, Chuck" <cgomes(a)verisign.com>, "iotf(a)icann.org" <iotf(a)icann.org> Cc: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: Re: [IOTF] Updated draft of responses in PTI Bylaws-AoI table Good catch Chuck. Per your comment and Matthew’s agreement, I was supposed to delete the sentence beginning with “Member approval NOT required….”. I’ll make the edit in the Google doc and await any further comments before circulating a new version in time for the CWG call. Thank you, Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: "Gomes, Chuck" <cgomes(a)verisign.com> Date: Wednesday, June 15, 2016 at 6:35 PM To: Grace Abuhamad <grace.abuhamad(a)icann.org>, "iotf(a)icann.org" <iotf(a)icann.org> Cc: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: RE: Updated draft of responses in PTI Bylaws-AoI table The edits look good to me. Was the second option in Section 7.6.1 supposed to be deleted? “Board may approve delegation of responsibilities or powers of President. Member approval NOT required for the prescription of additional duties by the board to the President.[1] [2] Member approval required for the prescription of additional powers by the board to the President.” Chuck From: iotf-bounces(a)icann.org [mailto:iotf-bounces@icann.org] On Behalf Of Grace Abuhamad Sent: Wednesday, June 15, 2016 5:16 PM To: iotf(a)icann.org Cc: cwg-stewardship(a)icann.org Subject: [IOTF] Updated draft of responses in PTI Bylaws-AoI table Dear all, Per the discussion on today’s IOTF call, here attached is a redline version of the edits discussed on the call and a clean version to present to the CWG-Stewardship on Thursday. Thank you for your patience in the live editing process! --Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: Grace Abuhamad <grace.abuhamad(a)icann.org> Date: Monday, June 13, 2016 at 4:47 PM To: <iotf(a)icann.org> Cc: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: Reminder: Please review the responses in PTI Bylaws table Dear all, In absence of the IOTF call today, I would just like to remind you to take some time to review the Google doc table of CWG responses on the PTI Bylaws. There are some notes and live edits made during the last IOTF call, and some comments from Chuck and Avri. The link to the document is: https://docs.google.com/document/d/1rmsp569qRxkWtNSNrJsZzENxFKLwbXVcTDWSGZJ…. I think (but will let the Chairs confirm) that the plan is still to have CWG-Stewardship sign-off in time (or during) the CWG-Stewardship meeting on Thursday 16 June. Following group sign-off, the Client Committee would then be able to share the responses with Sidley for incorporation into the PTI Bylaws. Thank you, Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: Grace Abuhamad <grace.abuhamad(a)icann.org> Date: Wednesday, June 8, 2016 at 6:00 PM To: <iotf(a)icann.org> Cc: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: Process for IANA Bylaws - CWG Questions & Issues from Sidley Dear all, Per the email below, steps 1 & 2 have been completed: the CWG-Stewardship Chairs have provided initial responses, and the staff have matched these responses to the transcript of the CWG-Stewardship meeting from last week. The initial responses are available in a Google doc for the IOTF’s comments at: https://docs.google.com/document/d/1rmsp569qRxkWtNSNrJsZzENxFKLwbXVcTDWSGZJ…. Please note that the CWG-Stewardship list is copied for information. Anyone on either of these lists should feel free to review and comment on the initial responses, but the responsibility lies primarily with the IOTF at this stage. I will let the Chairs clarify the timeline for review, but my understanding is that we would like to have CWG-Stewardship sign-off in time (or during) the CWG-Stewardship meeting on Thursday 16 June. Following group sign-off, the Client Committee would then be able to share the responses with Sidley for incorporation into the PTI Bylaws. Thank you, Grace -- Grace Abuhamad Manager, Public Policy ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 Direct: +1 202 249 7545 | Mobile: +1 310 200 7638 Interested in the IANA Stewardship Transition? LEARN MORE. STAY UPDATED. FOLLOW. ENGAGE. From: <cwg-stewardship-bounces(a)icann.org> on behalf of Jonathan Robinson <jrobinson(a)afilias.info> Organization: Afilias Reply-To: Jonathan Robinson <jrobinson(a)afilias.info> Date: Monday, June 6, 2016 at 4:04 AM To: "cwg-stewardship(a)icann.org" <cwg-stewardship(a)icann.org> Subject: [CWG-Stewardship] Process for IANA Bylaws - CWG Questions & Issues from Sidley All, The substance and process for dealing with CWG Bylaws was discussed this on last week’s CWG call and then followed up by Lise & myself. Based on the discussions within the CWG, we propose the following course of action in order to get through the work as efficiently as possible. 1. Chairs will make a first attempt at answering / providing relevant input on the Sidley questions 2. Staff will review chairs’ input for consistency with the CWG meeting discussions 3. Answers / input to be shared with IOTF group for further review / development 4. Answers / input to be shared with CWG for further review / development 5. Answers / input to be shared via Client Committee with Sidley for incorporation into IANA Bylaws Thank-you Lise & Jonathan I lean toward this approach. It seems to me that the PTI Board should have this authority on its own; also, it would cause delays if they had to wait to get ICANN approval, causing unnecessary delays. for so long as such powers were strictly limited according to the PTI mission/role etc.

8 12