<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title></title>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0);">
<div style="font-size: 14px; font-family: Calibri, sans-serif;">Dear All,</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;">Please find below the notes from today’s CWG-Stewardship Meeting for your review. The recordings and transcript will get circulated shortly.</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;">Best regards,</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;">Marika</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><b>Notes CWG-Stewarship Meeting 21 October 2015</b></div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><br>
</div>
<div>
<div><i>1. Opening remarks </i></div>
<div>Welcome of CCWG-Accountability Chairs and Trang Nguyen, ICANN Staff Implementation Team</div>
<div><br>
</div>
<div><i>2. CCWG-Accountability </i> </div>
<div>A. Update from CCWG-Accountability co-Chairs </div>
<ul>
<li>See light at the end of the tunnel</li><li>See presentation that focused on core points that relate to the CWG-Stewardship </li><li>CCWG-Accountability is not changing the policy-making aspects of the ICANN community - important to emphasise.
</li><li>Current status of SO/ACs remains the same</li><li>Areas of concern in public comment: reallocation/ concentration of power; membership rights/risk of capture.</li><li>Three phases for community decisions - 1) Engagement, 2) Escalation, 3) Enforcement</li><li>Moving towards consensus instead of voting in the community forum - consensus defined by the level of support, not only the level of objections</li><li>Enforcement is ultimate mechanism - discussing membership and designator member</li><li>Based on feedback from community and ICANN, a number of modifications have been made in relation to the budget requirements, but the CCWG-Accountability is of the view that the current proposal meets the CWG-Stewardship requirements. PTI budget would be
ring-fenced and subject to separate veto.</li><li>Enforcement mechanism would also be able to deliver other aspects of CWG-Stewardship requirements. CCWG Accountability currently evaluating the differences of the two models (Designator / Single Member) to determine the differences, but also ensure that
all the requirements are met. In both models, all SO/ACs would be involved in the decision-making process. </li></ul>
<div>B. Impacts for CWG-Stewardship dependencies </div>
<ul>
<li>When available, CWG-Stewardship will review final proposal to confirm that its requirements are met. </li></ul>
<div><i>3. Implementation </i> </div>
<div>A. Update on planning from ICANN (see also session at 15:30) </div>
<ul>
<li>See presentation</li><li>Implementation timeline anticipated to be a minimum of 4 months</li><li>Administrative prep is already taking place, followed by planning and pre-work while the proposal would be in the NTIA Review & Implementation phase</li><li>Implementation would commence after NTIA approval. Until that time status quo is maintained.
</li><li>On September 30, 2016 a contract would need to be in place with the Root Zone Maintainer to ensure continuity and stability. Is being negotiated with VeriSign - continuation of current services, but allows for change after transition if so determined by
the community. </li><li>DT O to work with ICANN Staff on FY17 Budget Planning. ICANN Management will finalise assumptions on Transition/PTI by 15 January 2016.</li></ul>
<div>B. CWG-Stewardship role & oversight </div>
<ul>
<li>CWG-Stewardship will likely need to play a role in review and possible oversight of the work of staff implementation to make sure it meets the intent of the policy recommendations. </li></ul>
<div>C. SLEs </div>
<div>DT has captured current process. Approx. 80% of current log files will be able to address the SLEs identified. Using parallel track process to populate the SLE. Looking forward to receiving the data so that SLE can be populated. Once that has happened
it will be circulated to the CWG-Stewardship. Note, NTIA will need to approve sharing of data first before that further steps can be taken. </div>
<div> </div>
<div>D. IPR </div>
<div>Need a small team to draft requirements which are then reverted back to the CWG-Stewardship for approval. This team should also factor in the proposals submitted by the other communities. The other communities are looking forward to working with CWG-Stewardship
on this topic.</div>
<div><br>
</div>
<div><i>4. Legal </i> </div>
<div>A. Progress update on Bylaws drafting </div>
<div>See update provided by email by Legal Advisors </div>
<div>B. Issues for the CWG </div>
<div>TBD</div>
<div><br>
</div>
<div><i>5. AOB </i></div>
<div><i><br>
</i></div>
<div><i>6. Closing remarks</i></div>
<ul>
<li>Pick up items on list</li><li>Schedule meeting for week of 2 November.</li></ul>
</div>
</body>
</html>