Action Items

Action: Staff will send a stable document version by end of day Thursday.

Action (Grace): edit Webinar announcement to make clear that, at the time of the webinars, we will have provided the final version

Notes

1. Opening Remarks

· Majority of meeting will be focused on item 4 (recent edits, changes, etc)

· Be sure that the essence is captured (staff can assist with wording)

2. Update on Public Comments

· Mechanics & process: broke down by sections of the document.

· Finalizing the Review Tool & Responses: basing the document as of June 1st before the first draft final version was sent out.

· Lengthy 250-page document, but we will make sure everyone will have time to review

4. 2nd Reading of Final Proposal

· This version includes Avri, Greg and most of Sidley

· Edit footnote 3 (related to paragraph 105): The CSC is not a legal entity. (second sentence: switch "or" to "and")

· In IFR section (and Annex F), "Periodic reviews should occur at no more than five-year intervals."

· If a Special review occurs within a short period, allow for some flexibility

· Para 123: needs to be internally consistent and checked for relevant position in the document (ref: that CSC is further defined later in document, for example)

· Question of escalation to GNSO

· SLEs will be updated and submitted along with proposal( but perhaps not as extensive as was presented in Istanbul)

· Paragraph 141: "or equivalent community mechanism derived from the CCWG-Accountability process" (possible to bracket/footnote different points in the text)

· Paragraph 167: staff assets and coherence of PTI is important, but not sure that the last sentence adds clarity yet.

· Paragraph 170: Not accurate that CSC is multistakeholder (remove the word and use 'customer-based instead)

· Add footnote to paragraph 169 about .INT (footnote is currently in Annex to section II, so duplication here would be helpful)

· Paragraph 275: composition of IFRT does not have extra RySG member (only the SCWG does)

· Annex S: Term sheet would be the subject of negotiation between PTI and ICANN (with PTI having independent advice). This term sheet is an example/draft and precursor to the ICANN-PTI Contract. ---> use the word "sample" instead of "draft"

Further reading of the document on Tuesday but there is a deadline cut-off on Sunday 7 June for comments/edits.

Action: Staff will send a stable document version by end of day Thursday.

Action (Grace): edit Webinar announcement to make clear that, at the time of the webinars, we will have provided the final version