Hi Allan,

Thank you for your questions. I’ll address the 3 main questions from your email, but will need to perform some more internal consultation before responding to your notes and questions within the SLA Change process document:

Item 1 -RAPS: I included milestones for the RAPs simply because this is another activity we would like to finalize and bring to closure. It has no dependencies on the SLA processes. I can remove those milestones to their own chart to reduce confusion.

Item 2 – IANA Naming Function Contract Change approval. To clarify any confusion:

The IANA Naming Function Contract can be amended in three ways:

(1) For items defined as “Material Terms” to the Contract, in Section 16.3 (a) of the ICANN Bylaws, by agreement of ICANN and PTI, subject to a rejection right of the majority of each of the ccNSO and GNSO Councils.

(2) For all other items, by written agreement of ICANN and PTI (Section 14.3 of the Contract); or

(3) Unilateral change by ICANN in alignment with an IFR/Special IFR/SCWG Recommendation (Section 7.3 of the Contract).

As the anticipated change is not within the Material Terms, and this change is not out of an IFR, this amendment is properly effectuated through written agreement of ICANN and PTI. There is no requirement in the ICANN or PTI Bylaws, or in the Contract, that the CSC has an approval right over amendments.

Of course, ICANN and PTI both recognize that the CSC has an interest in understanding that the Contract is being changed in the way that ICANN and PTI have agreed it would be, and the effect of that change is appropriate. ICANN is in the process of finalizing the exact text of an amendment that will do the following things: (1) amend Annex A at Section 2 to remove the SLA tables that currently exist; (2) amend the language that is currently at Section 2.g to identify that the SLA tables will be maintained at a specific website, and that those tables may only be modified through the SLA Change Process, which will also be maintained at a specific website. ICANN will provide that text to the CSC as it is available, and in advance of the public comment. If the CSC has fundamental concerns over the form of the amendment, we encourage the CSC to flag those concerns for ICANN and PTI. ICANN also encourages the CSC to participate in the public comment process.

Item 3 - “ICANN can direct PTI to initiate a SLA change request” is a reference to the IANA Naming Functions contract which specifies requirements for PTI to notify and consult with ICANN. This is added in support of the earlier text in the document that “None of the requirements in the process for amending IANA Naming SLAs override any obligations within the IANA Naming Functions Contract.”

Regards,

Amy Creamer

GDD Strategic Project Manager

Global Domains Division (GDD)

Internet Corporation for Assigned Names and Numbers (ICANN)

Direct Line: +1 310 578 8910

Mobile: +1 424 537 8917

Email: amy.creamer@icann.org

Skype: amy_creamer

www.icann.org

From: ICANN-CSC <icann-csc-bounces@icann.org> On Behalf Of Allan MacGillivray
Sent: Tuesday, November 13, 2018 6:40 AM
To: Maria Otanes <maria.otanes@icann.org>; ICANN-CSC@icann.org
Subject: Re: [ICANN-CSC] Agenda: CSC November Meeting 25, Friday, 16 November, 19:00-21:00 UTC

Ria – thanks to you and ICANN/PTI for all of this material. I just have a couple of quick questions that I am hoping we can get answered before Friday’s call.

On the chart outlining the milestones under the item ‘IANA Contractual Change Submitted for Public Comment’, in the “Overview Materials’, there are a number of ‘tasks’ specific to the changes to the RAPs. Is this just a mistake, or do you see the SLA change process and RAP changes as being integrated?
The milestones makes no reference to CSC approving, nor even reviewing, the amendments to the IANA Naming Functions Contract. Is this an oversight? And do you have any sense of when this draft might be available?
On the document “Process for Amending the IANA Naming Service Level Agreements” there is a footnote which says “ICANN can direct PTI to initiate a SLA change request”. Is this a reference to an existing ICANN authority? If not, and it is intended to create such an authority, perhaps a full clause would be better. I have a couple of other minor drafting questions, noted in the attached.

Thanks

Allan

From: ICANN-CSC <icann-csc-bounces@icann.org> On Behalf Of Maria Otanes
Sent: Monday, November 12, 2018 5:36 PM
To: ICANN-CSC@icann.org
Subject: Re: [ICANN-CSC] Agenda: CSC November Meeting 25, Friday, 16 November, 19:00-21:00 UTC

Dear CSC,

Please find the attached documents from the GDD team on SLA Change Mechanism.

Inventory List:

Overview Materials: document provides some visuals for document requirements, the process flow for amending the IANA Naming Functions Contract: Annex A, a text based project plan and the same plan but in a more visual calendar format.

SLA Amendment Process_Draft for Consideration: this is the latest process version for how to amend a SLA. Please note we have now shown how the original table format which created 4 categories of SLA change types is fully captured in the process.

Procedure for Modifying the Process for Amending the IANA Naming Service Level Agreements: latest version for a mechanism allowing us to change the SLA Amendment Process.

The Wiki Space has also been updated with the latest documents: https://community.icann.org/x/_QXVBQ

Thank you,

Ria

From: ICANN-CSC <icann-csc-bounces@icann.org> on behalf of Maria Otanes <maria.otanes@icann.org>
Date: Friday, November 9, 2018 at 4:15 PM
To: "ICANN-CSC@icann.org" <icann-csc@icann.org>
Subject: [ICANN-CSC] Agenda: CSC November Meeting 25, Friday, 16 November, 19:00-21:00 UTC

Dear CSC,

Please find the agenda for the November CSC meeting in the Wiki space below and attached.

The next call will be held next Friday, 16 November, at 19:00-21:00 UTC.

The Wiki agenda page can be found here: https://community.icann.org/x/_QXVBQ

Have a great weekend,

Ria

_______________________________________________________________________________________________

Ria Otanes

Secretariat Operations Coordinator

Internet Corporation for Assigned Names and Numbers (ICANN)

Telephone: +1 202 249 7540

Mobile: +1 202 679 5185

Skype: maria.otanes.icann

Washington, DC Office | UTC-5