April 2016 - IOTF - lists.icann.org

ICANN 56 scheduling
by Alissa Cooper May 9, 2016

May 9, 2016

I was thinking that it’s probably around the time that ICANN staff are starting to put together the agenda for ICANN 56 (although you all would know better than me, since the ICG is not meeting). I think given the timing of ICANN 56 it will be important to have a session where an implementation update can be provided by this group, including both the community reps and the ICANN staff, and the community can have an opportunity to comment and ask questions. Wanted to flag that idea in case agenda requests are already going in. I will not be in Helsinki but will follow remotely. Alissa

5 5

Draft ICANN Bylaws language around ICANN-PTI Contract amendment
by Yuko Green April 27, 2016

April 27, 2016

Dear members of the IOTF, During today's call #7, one of the action items was to find the specific language within the draft ICANN Bylaws how the ICANN-PTI contract may be amended. Please review below the language taken from the draft Bylaws currently posted for the public comment: Section 16.3. IANA NAMING FUNCTION CONTRACT (a) On or prior to 1 October 2016, ICANN shall enter into a contract with PTI for the performance of the IANA naming function (as it may be amended or modified, the "IANA Naming Function Contract") and a related statement of work (the "IANA Naming Function SOW"). Except as to implement any modification, waiver or amendment to the IANA Naming Function Contract or IANA Naming Function SOW related to an IFR Recommendation or Special IFR Recommendation approved pursuant to Section 18.6 or an SCWG Recommendation approved pursuant to Section 19.4 (which, for the avoidance of doubt, shall not be subject to this Section 16.3(a)), ICANN shall not agree to modify, amend or waive any Material Terms (as defined below) of the IANA Naming Function Contract or the IANA Naming Function SOW if a majority of each of the ccNSO and GNSO Councils reject the proposed modification, amendment or waiver. The following are the "Material Terms" of the IANA Naming Function Contract and IANA Naming Function SOW: (i) The parties to the IANA Naming Function Contract and IANA Naming Function SOW; (ii) The initial term and renewal provisions of the IANA Naming Function Contract and IANA Naming Function SOW; (iii) The manner in which the IANA Naming Function Contract or IANA Naming Function SOW may be terminated; (iv) The mechanisms that are available to enforce the IANA Naming Function Contract or IANA Naming Function SOW; (v) The role and responsibilities of the CSC (as defined in Section 17.1), escalation mechanisms and/or the IFR (as defined in Section 18.1); (vi) The IANA Naming Function Contract's provisions requiring that fees charged by PTI be based on direct costs and resources incurred by PTI; (vii) The IANA Naming Function Contract's prohibition against subcontracting; (viii) The availability of the IRP as a point of escalation for claims of PTI's failure to meet defined service level expectations; (ix) The IANA Naming Function Contract's audit requirements; and (x) The requirements related to ICANN funding of PTI. 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

IOTF Call #7 - Meeting Notes (27 April 2016 @ 19:00 UTC)
by Yuko Green April 27, 2016

April 27, 2016

Dear members of the IOTF, Please see below the meeting notes and chat history from today's IOTF call. The presentation material, audio and AC room recordings are now posted at https://www.icann.org/stewardship-implementation under "Meetings & Work Sessions" section. The transcript will be made available within the next few days. *** Meeting Notes *** Implementation Oversight Task Force (ITOF) call #7 27 Apr 2016 @ 19:00 UTC Please note that this meeting is being recorded. To mute or unmute, select *6 (Star-Six) If you would like to review the last call(s), the recordings and presentation materials are posted publicly here: https://www.icann.org/stewardship-implementation Agenda: 1. Opening Remarks 2. Implementation Items * RZERC Charter: Obtain final agreement from IOTF on the draft circulated * IANA Escalation Mechanism: Is there any other comments and feedback from the IOTF on Chuck's clarification? * Document Review Process & Timeline: 1) Continue discussion regarding document review process, and 2) review timeline 3. AOB 4. Closing Remarks Notes: Apology - Donna A, Jonathan R IANA Escalation Mechanism * Response provided by Chuck is based on the discussion with the design team. * Keep this item open until next Wednesday call Action Items: * RZERC charter - Remove the "(possibly as Chair)" from Composition section (ICANN) * RZERC charter - Delete "AS" from the first sentence from "Records of Proceedings" (ICANN) * RZERC charter - Add "minutes shall be posted as soon as possible" at Records & Proceeding section (ICANN) * RZERC charter - Replace "as prudent" with "as appropriate" at the last section of the Meetings (ICANN) * Forward the term sheet of the PTI formation documents to the client committee for Sidley's review (ICANN) * ICANN-PTI Contract - Add Annex M as an additional input source (ICANN) * Pull language off of draft ICANN bylaws re: ICANN-PTI contract and circulate to IOTF mail list (ICANN) * ICANN to discuss internally how the ICANN-PTI contract can be shared before the whole draft is ready (ICANN) ***Chat History*** Yuko Green: Hello everybody, welcome t o IOTF call #7 matthew shears: hi could you remind me when the RZERC doc was circulated - thanks Yuko Green: @Matthew: It was Monday at 7pm PDT through IOTF mailing list from Trang matthew shears: OK thanks Allan MacGillivray: Hi everyone. That's me on 5335. Yuko Green: Who may be phone # 5335? Chuck Gomes: Hi all Yuko Green: Thank you Allan matthew shears: phone is live Allan James Gannon: Hi All Yuko Green: You have scrolling control as RZERC charter is on slide 4 and 5 James Gannon: Yeah I think that was from the proposal but can be done away with now matthew shears: that needs to be made clear then Alissa Cooper: I still think this is over-specifying a bunch of details that should be left to the committee itself, but I am giving up on that line of argument Alissa Cooper: the document needs an edit pass for grammar James Gannon: Works for me matthew shears: in the last sentence under meetings what does the word prudent refer to? matthew shears: shouldn't it read as appropriate? Cheryl Langdon-Orr (CLO): lol James Gannon: If Chcuk is happy I am matthew shears: + 1 to Chuck's clarifications Avri Doria: sound like reasonable repsonses to me. Avri Doria: and as a member of that team they were what i remembered. Cheryl Langdon-Orr (CLO): th Avri Doria: is there an open issue of incompatitiblity between this and the agreed plan? Avri Doria: makes sense to wait for a another week. Avri Doria: to make sure that is is closed. Cheryl Langdon-Orr (CLO): not that I am aware of (yet) Avri but NP with another weeek Avri Doria: next call is a good compromise Chuck Gomes: Does Paul want a full week? Cheryl Langdon-Orr (CLO): next Wed call if we run the Mon one as well Paul Kane: agree matthew shears: where does responsibility for drafting the contract between ICANN and PTI lie? Alissa Cooper: that's on the next slide matthew shears: :) thanks matthew shears: shouldn't the IOTF review the full draft before it goes to the CWG? Grace Abuhamad: The document was forwarded to the Client Committee here: http://mm.icann.org/pipermail/cwg-client/2016-April/000440.html Grace Abuhamad: It's the process Chuck Gomes: It seems to me that the full drafts can be reviewed by the IOTF at the same time that Sidley is reviewing them. matthew shears: ok Chuck Gomes: When are the ICANN Bylaws targeted for approval? Paul Kane: Agree Alissa matthew shears: 27th May? Chuck Gomes: Thanks Matthew. matthew shears: understood - lets do it inparallel with Sidley Cheryl Langdon-Orr (CLO): yup Russ Housley: This structure impacts all of the operational communities, so we would like to know the proposed way forward as soon as possible James Gannon: +1 Russ matthew shears: + 1 Russ James Gannon: Principles in bylaws and details in contract would be what i expected Trang Nguyen: @Russ: Understood, Russ. Chuck Gomes: I have to drop off. Thanks all. matthew shears: I think that it would be useful of key parts of teh contract were shared as they were available rather than waiting on the full draft Lise Fuhr: Bye Chuck James Gannon: I think thats still a little fuzzy Trang at the moment James Gannon: On how much control there is over that contract from the provisions in the ICANN bylaws matthew shears: assuming the ICANN bylaws don't change Alan Greenberg: I suspect it will be easier to change the PTI Bylaws than the PTI-ICANN contract. Cheryl Langdon-Orr (CLO): thx Greg Paul Kane: Alan - agree Paul Kane: But Bylaws have a formal process matthew shears: + 1 Alissa on structure matthew shears: and +1 on review as well Alan Greenberg: Don't recall for sure, but I think PTI Bylaws are purely up to PTI Board. Appealable because ultimately controlled by ICANN, but no community process. Russ Housley: @Alan: One contract with three parts or three options is fine. A contract for the naming functions with options for the other two is quite different Alan Greenberg: @Russ, my reference was just with regard to Pauls statement about things in the PTI Bylaws as opposed to the contract. Paul Kane: Agree Lise matthew shears: we would also read the whole but it might expedite things and assuage some concerns along the way Lise Fuhr: @Trang it is more the structure than the details Allan MacGillivray: Many of the principles in Annex C that are important to the ccTLD community are also in the darft contract terms that were attached to the CWG proposal. They were deemed to be so important that they are mentioned twice so we need them reflected in nthe bylaws and the PTI contract. Lise Fuhr: Thank you Trang Avri Doria: thanks matthew shears: thanks all Lise Fuhr: All James Gannon: thanks trang thanks yuko Allan MacGillivray: Thanks everyone. 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

FW: IOTF Call #7 - Agenda and Presentation Material
by Nathalie Vergnolle April 27, 2016

April 27, 2016

Dear IOTF members, We are experiencing difficulties with the iotf email list. Re-sending in case you did not receive previous emails from Yuko. Attached, please find a couple of slides regarding the timeline for the PTI related documents. Also included on the slides are proposed review processes for these documents for discussion on today's call. Regards, Nathalie From: iotf-bounces(a)icann.org<mailto:iotf-bounces@icann.org> [mailto:iotf-bounces@icann.org] On Behalf Of Yuko Green Sent: Tuesday, April 26, 2016 6:49 PM To: iotf(a)icann.org<mailto:iotf@icann.org> Subject: [IOTF] IOTF Call #7 - Agenda and Presentation Material Dear IOTF members, Attached, please find the presentation material for Wednesday's IOTF Call #7 (27 April, 19:00 UTC / 12pm PDT / 3pm EDT / Thursday at 6am AEDT). The agenda of the call is: 1. Opening Remarks 2. Implementation Items - RZERC Charter: Obtain final agreement from IOTF on the draft circulated - IANA Escalation Mechanism: Is there any other comments and feedback from the IOTF on Chuck's clarification? - Document Review Process & Timeline: 1) Continue discussion regarding document review process, and 2) review timeline 1. AOB 2. Closing Remarks 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: yuko.green(a)icann.org<mailto:yuko.green@icann.org> www.icann.org<http://www.icann.org/>

1 0

IOTF Call #7 - Agenda and Presentation Material
by Yuko Green April 27, 2016

April 27, 2016

Dear IOTF members, Attached, please find the presentation material for Wednesday's IOTF Call #7 (27 April, 19:00 UTC / 12pm PDT / 3pm EDT / Thursday at 6am AEDT). The agenda of the call is: 1. Opening Remarks 2. Implementation Items - RZERC Charter: Obtain final agreement from IOTF on the draft circulated - IANA Escalation Mechanism: Is there any other comments and feedback from the IOTF on Chuck's clarification? - Document Review Process & Timeline: 1) Continue discussion regarding document review process, and 2) review timeline 3. AOB 4. Closing Remarks 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 2

Fwd: Annex C Sections 7 and 8 of the CWG report
by Paul M Kane - CWG April 27, 2016

April 27, 2016

Trang May I request an update. It seems to have missed inclusion in the Agenda Yoko sent out. Thanks Paul ----- Forwarded message from Paul M Kane - CWG <paul.kane-cwg(a)icb.co.uk> ----- Date: Tue, 26 Apr 2016 21:11:12 +0100 From: Paul M Kane - CWG <paul.kane-cwg(a)icb.co.uk> Reply-To: Paul M Kane - CWG <paul.kane-cwg(a)icb.co.uk> Subject: Annex C Sections 7 and 8 of the CWG report To: Trang Nguyen <trang.nguyen(a)icann.org> Hi Trang Hope all is well Following on from last week's call, can you please give us an update tomorrow on the Action item: - Section 7 & 8 of annex C: could be included in the ICANN Bylaws, PTI bylaws or in the ICANN-PTI contract. ICANN to flag this item with lawyers to make sure it gets included. (ICANN) Many thanks Best Paul ----- End forwarded message -----

3 2

Update on RZERC Charter
by Trang Nguyen April 26, 2016

April 26, 2016

Dear IOTF members: This is an update that the RZERC charter has been updated to reflect input provided on IOTF Call #5. The updated charter has been sent to Alan Greenberg to review and comment in his capacity as the lead of design team F. It will be circulated to the IOTF when ready. Warm regards, Trang

1 1

Update on RZMA
by Trang Nguyen April 26, 2016

April 26, 2016

All, There was a request for an update regarding the Root Zone Maintainer Agreement (RZMA) to be provided on today's IOTF call. As ICANN was unable to provide this update on the call due to time constraint, this update is being sent to the IOTF mail list. On 16 March 2016, Akram published a blog that provided an update regarding the ongoing discussions that ICANN and Verisign are engaged in to finalize the RZMA. The blog can be found at https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-sta…. Since the publication of this blog, ICANN and Verisign continue to engage in discussions to finalize the few remaining open items. The target completion date that we shared with the CWG on the last call two weeks ago was mid-April. Although ICANN and Verisign have made progress, that target completion date will be pushed to end of April. Once a draft RZMA is finalized, it will be posted for public review. Warm regards, Trang Nguyen

4 6

IANA Operational Escalation Mechanisms
by Trang Nguyen April 22, 2016

April 22, 2016

Dear Chuck, As a follow-up to today’s IOTF call, I am reaching out to summarize the 2 areas relating to Annex I and Annex J that we are seeking clarification. 1. Annex I: IANA Customer Service Complaint Resolution Process for Naming Related Functions Section 1 of paragraph 1140 of the CWG proposal says: “Customer Service Complaint Resolution Process – This process is for anyone who has a complaint about IANA services. The CWG-Stewardship has modified the current process used by ICANN by adding some steps at the end. For further details, please see Annex I.” This text implies that the only modifications to the current IANA Customer Service Complaint Resolution Process (http://www.iana.org/help/escalation-procedure) are the addition of new steps to Phase 2 of the process as reflected in Annex I. The current IANA Service Complaint Resolution Process has the following escalation steps: › IANA Function Liaison for Root Zone Management › IANA Functions Program Manager › ICANN President and CEO › ICANN Ombudsman However, paragraph 1367 of Annex I, which falls in the part of the process where we were not expecting changes due to the language of paragraph 1140, states: “The complainant could send an e-mail to escalation(a)iana.org<mailto:escalation@iana.org> and provide the ticket numbers of the requests where the problem arose. If the problem is not resolved, IANA staff will escalate the problem to the following team members in this order as applicable: › IANA Function Liaison for Root Zone Management; › IANA Functions Program Manager; and › Ombudsman (voluntary step).” We would like to get a clarification as to whether the omission of "ICANN President and CEO” in paragraph 1367 of Annex I was as intentional or accidental. 2. Annex J: IANA Problem Resolution Process (for IANA naming services only) Annex J contains 3 flowcharts. Flowcharts #1 and #3 are titled the same “IANA Problem Resolution Process,” but the contents of the flowcharts differ. We would like clarification as to whether the differences are intentional and if yes, under what circumstances would the process in each flow chart apply. Lastly, for agenda setting purpose, please let us know when you think you’ll be able to provide the clarification. We are scheduled to have 2 calls next week, one on Monday and another on Wednesday. Thank you, Chuck! Trang

2 2

IOTF Call #6 - Meeting Notes (20 April 2016 @ 19:00 UTC)
by Yuko Green April 20, 2016

April 20, 2016

Dear members of the IOTF, Please see below the meeting notes and chat history from today's IOTF call. The presentation material is now posted at https://www.icann.org/stewardship-implementation under "Meetings & Work Sessions" section. The audio recording and transcript will be made available within the next few days. Unfortunately due to technical issue, the AdobeConnect room recording was not completed though the recording was started at the beginning of the call. We are working with IT to identify the issue to avoid this from happening on the future calls. My apology for this inconvenience. ***Meeting Notes*** Implementation Oversight Task Force (ITOF) call #6 20 April 2016 @ 19:00 UTC Please note that this meeting is being recorded. To mute or Unmute, select *6 (Star-Six) If you would like to review the last call(s), the recordings and presentation materials are posted publicly here: https://www.icann.org/stewardship-implementation Agenda: 1. Opening Remarks 2. Implementation Items PTI Formation Document Review process IANA Escalation Mechanisms 3. AOB Paul Kane's question RZMA question 4. Closing Remarks Notes: PTI Formation documents are: - Bylaws - Articles of Incorporation - Conflict of Interest Policy Action Items: - Share Document Review Process & Timeline slide with Client Committee to discuss their involvement and Sidley's. (ICANN) - Share PTI formation documents term sheets with Client Committee (and potentially with Sidley). (ICANN) - IANA CS Complaint Resolution Process - is the CEO step no longer part of the process? Chuck will look into the question raised and get back to this group via the email list. (Chuck Gomes) - IANA Problem Resolution Process - Annex J - Flowchart 1 and 3 have the same title but one swimlane different. Chuck will look into it and get back to this group via the email list. (Chuck Gomes) - Section 7 & 8 of annex C: could be included in the ICANN Bylaws, PTI bylaws or in the ICANN-PTI contract. ICANN to flag this item with lawyers to make sure it gets included. (ICANN) - Share the rough timeline of implementation item documents during the next call (ICANN) - Review the ICANN Bylaws for the mentioning of the ICANN-PTI contract (ICANN) ***Chat History*** James Gannon: Will we have audio in the AC room for the call? James Gannon: Yup can hear Lise Fuhr: Good evening Chuck Gomes: I am 3200. Allan MacGillivray: Tht's me at 5335 Paul Kane: To be clear there will there be PTI Bylaws as it is a seperate affilaite company Paul Kane: ? Alissa Cooper: What section of the bylaws will the PTI Purpose be drawn from? Jonathan Robinson: Apologeis for late arrival Jonathan Robinson: Had a minor IT glitch Nathalie Vergnolle: Yes, there will be separate PTI bylaws Paul Kane: Thanks Nathalie Yuko Green: @Alissa, that would be are covered in Section 16.2 and Annex D (Articles 1 &2). Lise Fuhr: Thank you Trang Yuko Green: @Alissa, the language was circulated via IOTF mail on 15 April Alissa Cooper: ok, thanks, will find it matthew shears: + 1 Paul on PTI bylaws Paul Kane: Agree Trang Paul Kane: This group is here to help you get it right then it needs ratification by the groups CWG/SO etc matthew shears: agree bylaws and AoI should go to Sidley matthew shears: + 1 Chuck Paul Kane: Chuck agree Greg Shatan: With my clilent committee hat on, I'm happy to step in to the review at that point, suggeted by Chuck. Cheryl Langdon-Orr (CLO): agree totally Jonathan Jonathan Robinson: Reminder of the role of client committee. Not a committee to take decisions but to facilitate effective interaction with the lawyers to ensure that we use them efficiently / cost-effectively. Lise Fuhr: @Jonathan agree Avri Doria: wasn't this the CSC group. matthew shears: seems unusual that it would go to GDD James Gannon: Agree Matt Donna Austin, Neustar: @Avri, wasn't what the CSC group? matthew shears: PTYI BOard is not on the escalation path in the slide Cheryl Langdon-Orr (CLO): hmmm matthew shears: PTI Board would come after the IANA functions manager as the IANA functions manager is on the PTI Board if I recall correctly Cheryl Langdon-Orr (CLO): that resonates Matthrw Donna Austin, Neustar: This is for individual complaints Jonathan Robinson: What does the reference CWG 1367 mean? Paul Kane: How long wil this take? If there is a problem there needs to be a quick fix ..... Avri Doria: i guess i am missing the problem here. this seems to accurately reflect stage 1. Avri Doria: i do not think it was an omission James Gannon: Its actually para 367 in our proosal Johnathan James Gannon: *proposal Avri Doria: 1367 Cheryl Langdon-Orr (CLO): the proposed Yuko Green: 1367 refers to the paragraph number from ICG proposal Jonathan Robinson: Thanks Yuko. I was looking for the reference in the original CWG proposal matthew shears: If this is for individuals the proposed escalation path on the screen makes sense matthew shears: (not the current one) Paul Kane: Today there is GDD - but tomorrow there will be PTI Board Yuko Green: @jonathan, that would be paragraph 367 from CWG proposal Jonathan Robinson: Thank-you Yukp Cheryl Langdon-Orr (CLO): yes Avri thus the *proposed* Alan Greenberg: I have no problem with the ICANN CEO being removed. Was just curious that it was there today. Paul Kane: Agree Avri .... no longer there Donna Austin, Neustar: @Alan - I think it is at the complainant's discretion to take their complaint to the ICANN President & CEO, something anyone can do, not just as it relates to IANA Cheryl Langdon-Orr (CLO): THX Chuck matthew shears: + 1 Avri and + 1 Paul on speed and efficiency Cheryl Langdon-Orr (CLO): agree Donna Paul Kane: Donna - redelegation will (likely) be settled in Court - but technical operations need to involve The Managemnt of PTI- ie the Board Avri Doria: agree with Donna and that is a reasonable option James Gannon: Yes for emercengy technical issues there is the 24x7 escalation process Avri Doria: i think the right hand table corresponds to what we included in the plan. James Gannon: +1 Avri Cheryl Langdon-Orr (CLO): YUP Donna Austin, Neustar: I think the short answer to Trang's quesiton is there was no oversight. Cheryl Langdon-Orr (CLO): I will say again *the proposal* Allan MacGillivray: +1 Jonathan on agreeing to the current CWG proposal (right hand chart) and moving on. The IANA Functions Manager can always discuss this with the CEO. So, let's move on. Avri Doria: while the PRI may be a service provider to GDD, i did not think the IFPM would be a report of the GDD president except in so far as the GDD prez is on PTI board. Avri Doria: ... PTI ... Avri Doria: they wanted to be sure there was no oversight. good due dillgence. Donna Austin, Neustar: @Alan, it was an example Donna Austin, Neustar: a bad one, but just an example. Paul Kane: ccTLD are not ICANN - they are local and IANA confirm local and report to ICANN Alan Greenberg: @Donna, yes, but one that I tdon't think is possible, so was curious if I was missing something. Alan Greenberg: @Paul, yes, but ultimately IANA only takes action after action of the ICANN Board - today. Alan Greenberg: ICANN Boardpresumably verifying that local issues meet RFC Donna Austin, Neustar: @Alan, I was looking for examples at short notice and used a bad one. Paul Kane: ICANN verify that the ransfer is correct (ie Registrants have been safely transferred) - ie stability of the ccTLD users Paul Kane: Secure and stability of the DNS ..... Cheryl Langdon-Orr (CLO): Alan reefer back nee to the FOI for Delegations lokking to both RFC 1591 and the GAC Priciples relsting to Delegations Alan Greenberg: @Donna :-) Paul Kane: Bylaws... makes most sense... Thanks James Gannon: Para 264 for refernce Paul Kane: Thanks Trang Donna Austin, Neustar: I have to drop from the call. thanks all Alissa Cooper: I have a different question to ask under AOB, if we have time Lise Fuhr: I have to leave at the top of the hour Paul Kane: Note taker - It is ICANN Bylaws and also PTI bylaws matthew shears: + 1 Alissa - both sets of bylaws are key Yuko Green: @Paul, thank you Paul Kane: THanks .... Yuko ( remove Either) Paul Kane: Thasnk Yuko Green: Thank you Paul James Gannon: I dont think that the CCWG would provide much control over ICANNs ability to create and modify contracts Alissa Cooper: it is currently referenced in 1.1(d), but not for the effect that Chuck was describing James Gannon: Unless the wording was places directly into the bylaws and not just a reference James Gannon: +1 Paul James Gannon: Yes that it being done in other areas Paul Kane: Thanks all James Gannon: thanks all Jonathan Robinson: Thank-you Trang Cheryl Langdon-Orr (CLO): Thnks everyone...Bye Greg Shatan: Bye all! 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