August 2016 - Accountability-Cross-Community

another important milestone
by Thomas Rickert Aug. 16, 2016

Aug. 16, 2016

All, in addition to the blog post that Hillary sent to the list, you might find these links interesting. Thanks to Larry and team for such a timely and positive response to the latest ICANN status report. Best, Thomas Letter to ICANN CEO Marby Regarding IANA Stewardship Transition Status Update https://www.ntia.doc.gov/other-publication/2016/letter-icann-ceo-marby-rega… <https://www.ntia.doc.gov/other-publication/2016/letter-icann-ceo-marby-rega…> Blog: Update on the IANA Transition https://www.ntia.doc.gov/blog/2016/update-iana-transition <https://www.ntia.doc.gov/blog/2016/update-iana-transition>

2 1

Notes, recordings, transcript for WS2 Ombudsman Subgroup Meeting #2 - 16 August
by MSSI Secretariat Aug. 16, 2016

Aug. 16, 2016

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Ombudsman Subgroup Meeting #2 – 16 August 2016 will be available here: https://community.icann.org/x/7wSsAw A copy of the notes and action items may be found below. Thank you. With kind regards, Brenda Brewer MSSI Projects & Operations Assistant ICANN - Internet Corporation for Assigned Names and Numbers Notes 1 Call Admin and Roll Call/Apologies Sebastien Bachollet 2. Welcome – Opening Remarks – Meeting schedule (3 min SBT) · Asja Hemrajani: Possible to change 1900UTC proposed meetings to either of the two other slots? · Sebastien Bachollet: ACTION ITEM Propose this in an email to the group. 3. Action items Call #1 DT Ombudsman (10 min SBT and all) · Sebastien Bachollet: Use of Ombuds vs Ombudsman. Dependencies between the sub-groups. Most groups have coordination participants except for CEP and IRP. Evaluate current Ombuds charter vs international best practices. Work can be split into 4 parts Independence, Neutrality and impartiality, Confidentiality and Informality and other standards. · Mike Silber: overly complex? should we not look at this holistically? · Sebastien Bachollet: do not disagree just trying to break down the work. · Herb Waye: we could possibly compare the types of Ombudsman roles (legislative, university etc.). There are quite a lot of variation between these types. · Mike Silber: could we ask someone from the current ombud's office to start with that? Always easier to work from a draft. could the Ombuds office do such a first rough draft? · Ed Morris: Edward Morris: Point I'm trying to make: Other groups and the entire CCWG have at times attempted to give the Ombudsman powers and responsibilities that go far beyond the traditional remit of an Ombudsman (i.e. fairness). George Sadowsky in Istanbul opined that what we were really talking about was more of an Inspector General than an Ombudsman. Has anyone considered this or, and perhaps Herb can chip in here, whether some of the things that have or may be proposed are beyond the Ombudsmans competence and how we should handle that. Or was George correct in stating we might want to first see if we want an Ombuddy or something else? · Mike Silber: Ed - valid point but IMO the way to do this is to look at the powers and framework. Then to hire candidates who embody those · Edward Morris: Let's sort what the powers are we want to give the position then figure out what the position should be. · Mike Silber: a very good example is the South African "Public Protector" and I will try find time to right a few lines about that · Herb Waye: agree there are limitations. Informality is critical. An Inspector General takes this in a completely different direction and is not an Ombuds role. · Asha Hemrajani: Agree with EM - we have to look at function and role and then we can look at how they perform that role. So we need a draft to get going. · Sebastien Bachollet: doing everything at once is difficult. 4. Discuss our work plan [short and medium term] (15 min) 5. Next Meeting (5 min) · Monday August 22, 1900 UTC. · Sebastien Bachollet: any questions for the next call Presentation by the past and current ICANN Ombuds? · Sivasubramanian: Mr Waye, are there examples of "informality" that you are talking about? And the boundaries for informality? Could it be possible that at times lack of respectful attention could pass as informality? · Herb Waye: I can address informality next week during the presentation · Sebastien Bachollet: Robin can you be the liaison with the IRP group? RG agrees. 6. AOB (5 min) · Sebastien Bachollet: any other business - none? Adjourned. Documents Presented · CCWG_WS2_DT_Ombuds_#2_V1[3].pdf<https://community.icann.org/download/attachments/61605103/CCWG_WS2_DT_Ombud…>

1 0

[Blog] Implementation Planning, Execution, and NTIA’s Response
by Hillary Jett Aug. 16, 2016

Aug. 16, 2016

Original link: https://www.icann.org/news/blog/implementation-planning-execution-and-ntia-… Implementation Planning, Execution, and NTIA’s Response In order to fulfill the tasks assigned by NTIA<https://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transitio…> and the community-developed proposals for the IANA stewardship transition<https://www.icann.org/news/announcement-2016-03-10-en>, ICANN and the multistakeholder community have dedicated significant time and resources over the past eight months developing plans for implementation. The ICANN community and staff continue to work hard to ensure that all necessary tasks are completed and the proposals can be implemented in a timely manner in advance of 30 September 2016 to allow the IANA functions contract to expire. On 9 June 2016, NTIA requested<https://www.icann.org/en/system/files/correspondence/strickling-to-crocker-…> that ICANN submit an implementation planning status report by 12 August 2016. Last Friday, ICANN submitted<https://www.icann.org/en/system/files/correspondence/marby-to-strickling-12…> a report<https://www.icann.org/en/system/files/files/iana-stewardship-implementation…> to NTIA that stated: “All required tasks specified in NTIA’s 9 June 2016 letter are complete, and all other tasks in support of the transition are either in a final review stage or awaiting approval, which will be complete in advance of 30 September 2016 to allow the IANA functions contract to expire.” In a letter to ICANN today<https://www.ntia.doc.gov/files/ntia/publications/20160816marby.pdf>, NTIA stated, “NTIA has thoroughly reviewed the report. Based on that review, barring any significant impediment, NTIA intends to allow the IANA functions contract to expire as of October 1.” ICANN is pleased with NTIA’s statement and is focused on the remaining tasks to be completed by 30 September 2016: · Finalize the PTI Bylaws<https://www.icann.org/public-comments/draft-pti-bylaws-2016-07-12-en>: ICANN is currently incorporating comments received during the public comment process that ran from 12 July-11 August and will post a final version on 18 August. · Finalize the ICANN-PTI Naming Function Agreement<https://www.icann.org/public-comments/iana-naming-function-agreement-2016-0…>, which includes the customer service complaint and escalation mechanisms defined by the CWG-Stewardship: This Agreement is currently out for public comment until 9 September 2016, and a final version will be posted on 16 September 2016. · Finalize the ICANN-PTI Services Agreement<http://mm.icann.org/pipermail/cwg-stewardship/2016-August/005522.html>: The Agreement is currently being reviewed and discussed with the multistakeholder community, and a final version will be posted on 16 September 2016. In addition, there are four agreements and documents that have been finalized and require signatures, or ICANN Board and/or PTI Board approval before they can be considered complete: · The Root Zone Maintainer Agreement. · The ICANN-PTI Protocol Parameters Subcontracting Agreement. · The ICANN-PTI Numbers Subcontracting Agreement. · The PTI Conflict of Interest Policy, Board Code of Conduct, and Expected Standards of Behavior. I encourage anyone who is interested in the details of both the completed and ongoing implementation tasks to read ICANN’s 31-page implementation planning status report<https://www.icann.org/en/system/files/files/iana-stewardship-implementation…>. ICANN is confident that everything will be implemented in advance of 30 September 2016 to allow the IANA functions contract to expire. The global multistakeholder community, with the support of ICANN the organization, is ready for the IANA stewardship transition to occur.

1 0

Clarifying the Observer Role in the Subgroups
by Greg Shatan Aug. 14, 2016

Aug. 14, 2016

Co-Chairs and Staff, We need some clarification of the Observer role in the Subgroups. Conceptually, are the Observers essentially "spectators" or do they have the ability to participate in some fashion? Specifically: 1. Will Observers get call invitations? 2. Can Observers join Adobe Connect and/or phone bridge for the call? 3. If yes, can Observers speak and/or write in the chat, or are they required to be silent/non-participating? 4. Do Observers receive the mailing list posts along with everyone else? 5. Will Observers have posting rights to the email list? Clarification of these specific issues as soon as possible will be most helpful to the functioning of the Subgroups. Thank you. Greg

6 9

Re: [CCWG-ACCT] Clarifying the Observer Role in the Subgroups
by Alan Greenberg Aug. 14, 2016

Aug. 14, 2016

Perhaps I am alone, but I find it useful to listen to meetings when they are happening as opposed to after the fact. Perhaps I am just insufficiently disciplined, but going back and listening to recordings is something I often just don't get to. Listening live also has the benefit of being able to back-channel Skype to those on the call. The AC and dial-in bridge for the GNSO Council meetings is strictly controlled. A few years ago, they set up an audio stream accessible via the web for people to listen in real time (if I remember correctly, it was done partially or largely at Avri's request). I have no idea what it costs, but I suspect the ongoing costs are minimal and the only effort is to connect the audiocast to the teleconference audio stream at the start of the meeting. Perhaps this can be investigated. Messages to the general list saying the meetings will happen is also desirable, even if not linked to the AC and bridge info. It is a push technology instead of pull. Alan At 14/08/2016 10:34 AM, Bernard Turcotte wrote: >Greg et al., > >Answers inserted in your questions below but it >is important to note the the role of Observers was meant to be just that: > >On Sat, Aug 13, 2016 at 10:50 PM, Greg Shatan ><<mailto:gregshatanipc@gmail.com>gregshatanipc(a)gmail.com> wrote: >Co-Chairs and Staff, >We need some clarification of the Observer role in the Subgroups. >Conceptually, are the Observers essentially >"spectators" or do they have the ability to participate in some fashion? >Specifically: > >1. Will Observers get call invitations? > >âNo - in part this is because there is no way >to distinguish between Observers and >Participantsâ on teleconferences or in Adobe - >as such if Observers were to participate in >these there would be no point in having the >differentiation between Observers and Active >Participants. It is however important to note >that there is no restrictions on who can be an >Active Participant or an Observer and that >people can join either or switch between them at >any time. I will copy below the published >definitions of these here to remind people of the difference between these two: > > * As an active participant who wishes to > engage in the day-to-day discussions of the > particular topic. Each active participant is > expected to spend at least 3-5 hours per week > on sub-group work and will have posting rights to the mailing list. > * As an observer who wishes to follow the > topic discussion but not actively participate > at the sub-group level. Observers are not > expected to spend time on sub-group work and > will not have posting rights to the mailing list. > >2. Can Observers join Adobe Connect and/or phone bridge for the call? > >âThat is up to the rapporteurs for that group >as staff will not police this - but again since >calls are being recorded, transcribed and notes >taken it was felt observers would not be deprived of any information. >â > >3. If yes, can Observers speak and/or write in >the chat, or are they required to be silent/non-participating? > >âAs noted above there is no automated way of , >and staff will not police, enforcing any >limitation on Observers in Adobe, as such there >is nothing which would prevent them from fully participating. >â > >4. Do Observers receive the mailing list posts along with everyone else? > >âYes. >â > >5. Will Observers have posting rights to the email list? > >âNo. > > >Hope this helps. > >Cheers > >B.â > >Clarification of these specific issues as soon >as possible will be most helpful to the functioning of the Subgroups. >Thank you. >Greg >_______________________________________________ >Accountability-Cross-Community mailing list ><mailto:Accountability-Cross-Community@icann.org>Accountability-Cross-Community(a)icann.org > >https://mm.icann.org/mailman/listinfo/accountability-cross-community > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;DM5PR03MB2714;9:a9KNcB6O9eRBM7KS0KpTbmPZzRfhtKUbVTv7FFvd8WpxvUI4SGHuOnDpExU8UvlEOPadgePUdik7FzTgNnYkWUD0d+raJ1vUuv7AGWLaiPsJ6RuMcWw13zoT88F9IP0rf7s/iuaMhAipwyyAIt9nBZ3JDLlZc0wPYshVKG1o0VAeyC8gptNoLB1ArbYQpN66Ywrc4bgAUK0LDhz6VDqSkA== > >_______________________________________________ >Accountability-Cross-Community mailing list >Accountability-Cross-Community(a)icann.org >https://mm.icann.org/mailman/listinfo/accountability-cross-community

2 1

Re: [CCWG-ACCT] Clarifying the Observer Role in the Subgroups
by Seun Ojedeji Aug. 14, 2016

Aug. 14, 2016

Since I am observer on jurisdiction subgroup though I should post here: Thanks, FWIW I think item 5 is working just fine as observers posts don't make it to the list(which is right). The archive is where to confirm that, as my post didn't make it to the list. Nevertheless, there could be a mistake in the settings of a particular user which i believe can always be communicated to staff for correction. Speculating further, on item 3 if indeed there is the option to easily grant observer non-texting/talking role in AC then that would have been applicable to observers. However I couldn't find that feature [1], otherwise observers should at minimum be able to do 1,2,4 and I will also add 3 so long as they are not participating in decision making. Cheers! 1. https <https://helpx.adobe.com/adobe-connect/using/getting-started-administering-a…> ://helpx.adobe.com/adobe-connect/using/getting-started-administering-accounts.html#working_with_compliance_and_control_settings <https://helpx.adobe.com/adobe-connect/using/getting-started-administering-a…> Sent from my LG G4 Kindly excuse brevity and typos On 14 Aug 2016 03:50, "Greg Shatan" <gregshatanipc(a)gmail.com> wrote: Co-Chairs and Staff, We need some clarification of the Observer role in the Subgroups. Conceptually, are the Observers essentially "spectators" or do they have the ability to participate in some fashion? Specifically: 1. Will Observers get call invitations? 2. Can Observers join Adobe Connect and/or phone bridge for the call? 3. If yes, can Observers speak and/or write in the chat, or are they required to be silent/non-participating? 4. Do Observers receive the mailing list posts along with everyone else? 5. Will Observers have posting rights to the email list? Clarification of these specific issues as soon as possible will be most helpful to the functioning of the Subgroups. Thank you. Greg _______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community(a)icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

1 0

[Announcement] CANN Submits Implementation Planning Status Report to NTIA
by Hillary Jett Aug. 12, 2016

Aug. 12, 2016

Original link: https://www.icann.org/news/announcement-3-2016-08-12-en ICANN Submits Implementation Planning Status Report to NTIA ICANN today submitted an implementation planning status report<https://www.icann.org/en/system/files/files/iana-stewardship-implementation…> [PDF, 932 KB] to the National Telecommunications and Information Administration (NTIA), in response to a request<https://www.icann.org/en/system/files/correspondence/strickling-to-crocker-…> [PDF, 339 KB] NTIAmade on 9 June 2016. ICANN and the various stakeholder groups have worked tirelessly to complete the tasks specified byNTIA and the global multistakeholder community. The following implementation tasks are complete: · On May 27, 2016, the ICANN Board approved the revisions to the ICANN Bylaws. · On June 24, 2016, ICANN signed the 2016 Supplemental Agreement with the Internet Engineering Taskforce (IETF). · On June 29, 2016, ICANN signed the Service Level Agreement (SLA) with the five Regional Internet Registries (RIRs). · On July 5, 2016, ICANN and Verisign successfully completed the 90-day parallel testing period on the Root Zone Management System. · On August 9, 2016, the ICANN Board approved the amendments to the ICANN Articles of Incorporation. · On August 10, 2016, the membership of the Customer Standing Committee (CSC) was approved. · On August 10, 2016, the Incorporation Documents for the "Post-Transition IANA" organization were filed and received by the California Secretary of State, under the name Public Technical Identifiers (which will be more commonly referred to as PTI). · On August 12, 2016, the Root Zone Evolution Review Committee (RZERC) was formed. Significant progress has been made on the following implementation tasks, which will be complete in advance of September 30, 2016<x-apple-data-detectors://11>: · On August 18, 2016<x-apple-data-detectors://12>, the final PTI Bylaws will be published. These will incorporate comments received through the ICANN public comment process, which ran from July 12, 2016 to August 11, 2016. Once published, the PTI Bylaws will be ready for ICANN and PTI Board approval. · On September 16, 2016<x-apple-data-detectors://14>, the ICANN-PTI Naming Function Agreement will be published. It is undergoing a 30-day ICANN public comment process, which will close on September 9, 2016<x-apple-data-detectors://15>. The final Agreement will be published on September 16, 2016<x-apple-data-detectors://16>. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature. · The customer service complaint and escalation mechanisms defined by the domain names community were incorporated into the Naming Function Agreement. · On September 16, 2016<x-apple-data-detectors://17>, the ICANN-PTI Services Agreement will be published. It is currently being reviewed and discussed with the community. Once published, the Agreement will be ready forICANN and PTI Board approval and signature. · Several agreements and documents are complete and ready for signature or Board approval, which will be complete in advance of September 20, 2016<x-apple-data-detectors://18>: · On August 2, 2016, the ICANN-PTI Protocol Parameter Subcontracting Agreement was completed and is ready for ICANN and PTI signature. · On August 9, 2016, the ICANN Board approved the Root Zone Maintainer Agreement. ICANN, Verisign, and NTIA will coordinate a date to sign it. · On August 11, 2016, the Service Level Expectations (SLEs) for the domain names community were completed and are ready for incorporation into the final Naming Function Agreement. The Naming Function Agreement requires ICANN and PTI Board approval. · On August 11, 2016 the ICANN-PTI Numbers Subcontracting Agreement was completed and is ready for ICANN and PTI signature. · On August 12, 2016, the PTI governance documents, including the conflict of interest policy, Board code of conduct and expected standards of behavior were completed after an ICANNpublic comment process and are ready for PTI Board adoption. ICANN, working with the multistakeholder community, confirms that all required IANA functions stewardship transition tasks specified in NTIA's June 9, 2016 letter are complete, and all other tasks in support of the IANA stewardship transition are either in a final review stage or awaiting approval, which will be complete in advance of September 30, 2016<x-apple-data-detectors://25> to allow the IANA functions contract to expire. Review the IANA Stewardship Transition Proposal Implementation Planning Status Report for more information: https://www.icann.org/en/system/files/files/iana-stewardship-implementation… [PDF, 932 KB].

1 0

ICANN Submits Implementation Planning Status Report to NTIA
by Bruce Tonkin Aug. 12, 2016

Aug. 12, 2016

From: https://www.icann.org/news/announcement-3-2016-08-12-en ICANN Submits Implementation Planning Status Report to NTIA ICANN today submitted an implementation planning status report [PDF, 932 KB] to the National Telecommunications and Information Administration (NTIA), in response to a request [PDF, 339 KB] NTIA made on 9 June 2016. ICANN and the various stakeholder groups have worked tirelessly to complete the tasks specified by NTIA and the global multistakeholder community. The following implementation tasks are complete: *On May 27, 2016, the ICANN Board approved the revisions to the ICANN Bylaws. *On June 24, 2016, ICANN signed the 2016 Supplemental Agreement with the Internet Engineering Taskforce (IETF). *On June 29, 2016, ICANN signed the Service Level Agreement (SLA) with the five Regional Internet Registries (RIRs). *On July 5, 2016, ICANN and Verisign successfully completed the 90-day parallel testing period on the Root Zone Management System. *On August 9, 2016, the ICANN Board approved the amendments to the ICANN Articles of Incorporation. *On August 10, 2016, the membership of the Customer Standing Committee (CSC) was approved. *On August 10, 2016, the Incorporation Documents for the "Post-Transition IANA" organization were filed and received by the California Secretary of State, under the name Public Technical Identifiers (which will be more commonly referred to as PTI). *On August 12, 2016, the Root Zone Evolution Review Committee (RZERC) was formed. Significant progress has been made on the following implementation tasks, which will be complete in advance of September 30, 2016: *On August 18, 2016, the final PTI Bylaws will be published. These will incorporate comments received through the ICANN public comment process, which ran from July 12, 2016 to August 11, 2016. Once published, the PTI Bylaws will be ready for ICANN and PTI Board approval. *On September 16, 2016, the ICANN-PTI Naming Function Agreement will be published. It is undergoing a 30-day ICANN public comment process, which will close on September 9, 2016. The final Agreement will be published on September 16, 2016. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature. *The customer service complaint and escalation mechanisms defined by the domain names community were incorporated into the Naming Function Agreement. *On September 16, 2016, the ICANN-PTI Services Agreement will be published. It is currently being reviewed and discussed with the community. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature. *Several agreements and documents are complete and ready for signature or Board approval, which will be complete in advance of September 20, 2016: *On August 2, 2016, the ICANN-PTI Protocol Parameter Subcontracting Agreement was completed and is ready for ICANN and PTI signature. *On August 9, 2016, the ICANN Board approved the Root Zone Maintainer Agreement. ICANN, Verisign, and NTIA will coordinate a date to sign it. *On August 11, 2016, the Service Level Expectations (SLEs) for the domain names community were completed and are ready for incorporation into the final Naming Function Agreement. The Naming Function Agreement requires ICANN and PTI Board approval. *On August 11, 2016 the ICANN-PTI Numbers Subcontracting Agreement was completed and is ready for ICANN and PTI signature. *On August 12, 2016, the PTI governance documents, including the conflict of interest policy, Board code of conduct and expected standards of behavior were completed after an ICANN public comment process and are ready for PTI Board adoption. ICANN, working with the multistakeholder community, confirms that all required IANA functions stewardship transition tasks specified in NTIA's June 9, 2016 letter are complete, and all other tasks in support of the IANA stewardship transition are either in a final review stage or awaiting approval, which will be complete in advance of September 30, 2016 to allow the IANA functions contract to expire. Review the IANA Stewardship Transition Proposal Implementation Planning Status Report for more information (see attached) https://www.icann.org/en/system/files/files/iana-stewardship-implementation…

1 0

[Announcement] ICANN Announces the Formation of the CSC and RZERC
by Hillary Jett Aug. 12, 2016

Aug. 12, 2016

Original link: https://www.icann.org/news/announcement-2016-08-08-en ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition ICANN today announced the formation of the Customer Standing Committee (CSC) and the Root ZoneEvolution Review Committee (RZERC). Both newly formed committees are requirements for the completion of the IANA Stewardship Transition by the CWG-Stewardship. The CSC will perform the operational oversight of the performance of the IANA naming function, a role currently performed by NTIA. In its oversight role, the CSC will monitor the performance of the IANAnaming function against agreed service level expectations. The CSC may also initiate reviews and make recommendations for post-transition changes to service level expectations. For more information, please see the CSC Charter<https://www.icann.org/iana_imp_docs/41-csc-charter-v-v1> [PDF, 139 KB] or the CSC Scope and Responsibilities<https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2> [PDF, 82.3 KB]. Per the CSC Charter, the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) Councils have approved the full slate of the membership<https://www.icann.org/en/stewardship-implementation/customer-standing-commi…>. The RZERC will review proposed architectural changes to the content of the root zone, the systems (including both hardware and software components) used in executing changes to the root zone and the mechanisms used for distribution of the root zone. It will also make recommendations related to those changes for consideration by the ICANN Board. The ICANN Board's approval of recommendations developed through the RZERC will replace NTIA’s current role in approval of architectural changes to the root zone. The ICANN Board adopted the RZERC Charter<https://www.icann.org/en/system/files/files/revised-rzerc-charter-08aug16-e…> [PDF, 50 KB], finalized through public comment<https://www.icann.org/public-comments/draft-rzerc-charter-2016-06-10-en>, on 10 August 2016. See the full committee here<https://www.icann.org/en/stewardship-implementation/formation-of-a-root-zon…>. These committees will not become operational unless and until the expiration of the IANA Functions Contract. Additional details on ICANN's implementation planning efforts can be found at https://www.icann.org/stewardship-implementation.

1 0

Updated Articles of Incorporation
by Bruce Tonkin Aug. 12, 2016

Aug. 12, 2016

Hello All, The Board approved the updated Articles of Incorporation at its meeting on 9 Aug 2016. Thanks for the all the feedback from the CCWG that led to the revised Articles on Incorporation. Regards, Bruce Tonkin From: https://www.icann.org/resources/board-material/resolutions-2016-08-09-en Whereas, on 14 March 2014, the National Telecommunications and Information Administration (NTIA) of the United States Department of Commerce announced its intention to transition the stewardship of the IANA Functions to the global multistakeholder community. Whereas, on 10 March 2016, Internet Corporation for Assigned Names and Numbers (ICANN) accepted and transmitted to the US National Telecommunications and Information Agency the following transition documents: (i) the IANA Stewardship Transition Coordination Group's IANA Stewardship Transition Proposal, (the "ICG Proposal") and (ii) the Cross Community Working Group on Enhancing ICANN Accountability's Work Stream 1 Report (collectively, the "Transition Proposals"). Whereas, the ICANN Articles of Incorporation need to be restated in order to align with the new ICANN Bylaws and for consistency with the Transition Proposals. Whereas, ICANN lawyers worked diligently with the independent counsel to the CCWG-Accountability to develop Restated Articles of Incorporation for ICANN. Those Restated Articles were posted for public comment for over 40 days. Whereas, upon the close of the comments, a detailed analysis of the comments was performed and modifications were made to the Articles in response to the public comments. ICANN coordinated with the independent law firms on the revisions. Whereas, ICANN's General Counsel has asserted that the proposed Restated ICANN Articles of Incorporation remain consistent with the Transition Proposals and recommends that the Board approve the amendment to ICANN's Articles and authorize ICANN to proceed to filing at the appropriate time. Resolved (2016.08.09.06), the ICANN Board approves the proposed amendments to ICANN's Articles of Incorporation, which shall be deemed effective upon the expiration the IANA Functions Contract between ICANN and NTIA. Resolved (2016.08.09.07), the ICANN Board authorizes ICANN's CEO, or his designee, to proceed with the filing of the Restated Articles of Incorporation once they are effective.

6 7