December 2014 - cooperation-wg

Third document from SSAC on IANA Stewardship Transition Published
by Patrik Fältström 16 Dec '14

16 Dec '14

SSAC has just made the third document of three on IANA Stewardship Transition available. The three documents are: SAC-067 : Overview and History of the IANA Functions (15 August 2014) <https://www.icann.org/en/system/files/files/sac-067-en.pdf> SAC-068 : SSAC Report on the IANA Functions Contract (10 October 2014) <https://www.icann.org/en/system/files/files/sac-068-en.pdf> SAC-069 : SSAC Advisory on Maintaining the Security and Stability of the IANA Functions Through the Stewardship Transition (10 December 2014) <https://www.icann.org/en/system/files/files/sac-069-en.pdf> The first two (SAC-067 and SAC-068) are documents trying to objectively present The IANA Function and The Contract between ICANN and NTIA respectively. The third is an SSAC evaluation of the current situation, or as we (SSAC) say ourselves: > In this Advisory, the SSAC considers issues that may affect the security and stability of the DNS both during and after the transition of the NTIA’s stewardship role for the IANA Functions We in this document make the following recommendations: > Recommendation 1: The operational communities (protocol parameters, names, and numbers) that have been invited to submit proposals should determine 1) whether or not the requirements and deliverables defined in the IANA Functions Contract should be retained, and if so which ones; 2) whether or not additional external controls are necessary for requirements that should be retained; and 3) if additional external controls are necessary, how and by whom they should be administered. > > Recommendation 2a: Each of the communities should determine whether or not existing mechanisms outside of the IANA Functions Contract are sufficiently robust to hold the IANA Functions Operator accountable to the affected communities for the proper performance of the IANA Functions after the IANA Functions Contract expires; and if they are not, the communities should determine what additional accountability mechanisms will be needed. > > Recommendation 2b: Each of the communities should review and (if necessary) enhance its policy development process to ensure that all of the instructions that it provides to the IANA Functions Operator are clear and implementable. > > Recommendation 3: Each of the communities should investigate and clarify the process for handling the possibility of governmental sanctions and restrictions (e.g., the protocol for obtaining OFAC2 licenses where U.S. sanctions might interfere with the ability to execute proper instructions to IANA) following the stewardship transition. > > Recommendation 4: As part of the transition process, each of the affected communities should consider the extent to which the importance of transparency and freedom from > improper influence in the performance of the IANA Functions might require additional mechanisms or other safeguards. > > Recommendation 5: Noting the stability and efficiency of existing structures, processes, and mechanisms for the management of the root zone, the SSAC recommends that any proposal to replace NTIA’s final authorization of root zone changes with an alternative be at least as reliable, resilient, and efficient as the current process. > > Recommendation 6: Effective arrangements should be made for the reliable and timely performance of all aspects of the root zone management process post-transition, including inter-organization coordination if the post-transition RZM process involves more than one root zone management partner. > > Recommendation 7: NTIA should clarify the processes and legal framework associated with the role of the Root Zone Maintainer after transition. Regards, Patrik Fältström SSAC Chair

1 0

Minutes from the CRISP team teleconference 11 December 2014
by Nurani Nimpuno 15 Dec '14

15 Dec '14

Dear Colleagues, Please find attached the minutes from the CRISP team teleconference that took place on 11 December 2014. All CRISP related information is available from the NRO website: https://www.nro.net/crisp-team Kind regards, Nurani on behalf of the RIPE CRISP Team -- Nurani Nimpuno Head of Outreach & Communications, Netnod <nurani(a)netnod.se>, http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden ---------------------------------------------

1 0

Minutes from the first CRISP teleconference
by Nurani Nimpuno 11 Dec '14

11 Dec '14

Dear Colleagues, Please find attached the minutes from the first CRISP team teleconference. All CRISP related information is available from the NRO website: https://www.nro.net/crisp-team Kind regards, Nurani

5 4

Fwd: [NRO-IANAXFER] Draft for discussion
by Andrei Robachevsky 11 Dec '14

11 Dec '14

Colleagues, This is the initial draft shared on the ianaxfer mailinglist that the CRISP Team is taking as a baseline for discussions. I think it would be better if you direct your comments directly to the ianaxfer mailinglist. Regards, Andrei -------- Original Message -------- Subject: [NRO-IANAXFER] Draft for discussion Date: Thu, 11 Dec 2014 15:03:46 +0200 From: Alan Barrett <apb(a)cequrux.com> To: ianaxfer(a)nro.net The attached draft document will be discussed during the CRISP teleconference, which has just begun. This is a rough draft intended as input to the discussion process. --apb (Alan Barrett)

1 1

CRISP Team Holds First Teleconference
by Nurani Nimpuno 11 Dec '14

11 Dec '14

Dear colleagues, The Consolidated RIR IANA Stewardship Proposal (CRISP) team held its first public teleconference on 9 December 2014 at 13:00 UTC. Nurani Nimpuno, Andrei Robachevsky and Paul Rendek participated in the call from the RIPE community. A number of preliminary decisions were made during the teleconference. Izumi Okutani (APNIC community representative) was elected as the Chair of the CRISP team, with Alan Barrett (AFRINIC community representative) elected as Vice Chair. It was also agreed that a second CRISP team mailing list should be established for internal discussion between the CRISP team members, though the focus on transparency via the ianaxfer(a)nro.net must remain a priority for the group. This transparency will also extend to regular feedback from the RIPE CIRSP team to the RIPE Cooperation Working Group on CRISP team progress. It was noted by all that the timeline for the CRISP team to complete its work is very aggressive, with plans to have the final document produced by 15 January 2015. With that in mind, a draft timeline of teleconferences was discussed, with the next call scheduled to take place on 11 December at 13:00 UTC (that is, in two days' time). Ahead of that call, CRISP team members will share any drafting work already undertaken at the regional level, along with a report on recent discussions held between the Regional Internet Registry directors and the RIR staff CRISP team members. As with today's teleconference, information on how to join the upcoming CRISP teleconferences as an observer will be sent to the Cooperation Working Group. Best regards, Nurani on behalf of the RIPE CRISP team ---------------------------------------------------------- Nurani Nimpuno, Head of Outreach & Communications, Netnod <nurani(a)netnod.se> http://www.netnod.se

3 3

Fwd: [NRO-IANAXFER] CRISP Team 2nd Teleconference Thursday December 11th 2014 @ 13:00 UTC
by Nurani Nimpuno 11 Dec '14

11 Dec '14

Dear colleagues, You will find details on the second teleconference of the CRISP team below. Please note that these teleconferences are open to silent observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: German Valdez <german(a)nro.net> > Date: 10 december 2014 08:35:30 CET > To: <ianaxfer(a)nro.net> > Subject: [NRO-IANAXFER] CRISP Team 2nd Teleconference Thursday December 11th 2014 @ 13:00 UTC > > > Hi > > Below it's webex information to join to the 2nd CRISP Team teleconference to be held on December 11th 2014 @ 13:00 UTC > > Regards > > German Valdez > NRO > > > > > > > > > > German Valdez invites you to join this WebEx meeting. > > CRISP Team 2nd Teleconference > Thursday, December 11, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: 703 084 125 > Meeting password: crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 703 084 125 > Global call-in numbers | Toll-free calling restrictions > > Add this meeting to your calendar. > > Can't join the meeting? Contact support. > > IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] Draft Agenda - CRISP Team Teleconference 1 - Tuesday, 9 December 2014
by Nurani Nimpuno 08 Dec '14

08 Dec '14

Dear Colleagues, For your information. Please note that the CRISP teleconferences are open to the public. Kind regards, Nurani Nimpuno on behalf of the RIPE CRISP team -- ---------------------------------------------------------- Nurani Nimpuno Head of Outreach & Communications, Netnod http://www.netnod.se Begin forwarded message: > From: Paul Rendek <rendek(a)ripe.net> > Subject: [NRO-IANAXFER] Draft Agenda - CRISP Team Teleconference 1 - Tuesday, 9 December 2014 > Date: 7 december 2014 11:51:18 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > I am pleased to see that we have agreed on the first teleconference of the CRISP team to be held on Tuesday, 9 December 2014 @ 13:00 UTC. > > Below, please find a draft agenda for the proposed meeting. Michael Abejuela brought forward a few items that I believe are all covered in the draft agenda. > > If there are any other items not covered by this agenda please bring them forward to be included prior to the teleconference. > > I have added the webex/phone details below as a reference. I look forward to seeing you all on the teleconference call this week. > > Kind Regards, > > Paul Rendek > Director of External Relations > RIPE NCC > > === > Draft Agenda for CRISP teleconference 1 > > 1. Working Method > • Chair, Vice-Chair of the CRISP team > • ianaxfer(a)nro.net mailing list > • Teleconferences > • Quorum > • Timeline for teleconferences > • Decision-making mechanism > • Drafting tools > > 2. Scope of Activity > > 3. Producing an ICG RFP Response > • Survey of current drafting activity > • RIRs > • Other communities (IETF, CWG) > • Process for making progress > • Divide into sections, sub-teams > • Existing arrangements, > IANA stewardship process > description > • Proposed arrangements > • Timeline for drafting > > > > CRISP Team 1st Teleconference > Tuesday, December 9, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: 703 261 254 > Meeting password: crisp > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 703 261 254 > Global call-in numbers | Toll-free calling restrictions > Add this meeting to your calendar. > > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Initial text for the Post-Transition Oversight and Accountability Arrangements
by Andrei Robachevsky 02 Dec '14

02 Dec '14

Dear colleagues, As RIPE-selected members of the Consolidated RIR IANA Stewardship Proposal (CRISP) team, part of our preparation for this process has involved drafting some initial text in response to the IANA Coordination Group’s Request For Proposals (RFP). This text takes what we understand to be the RIPE community’s position and principles and distills them into a specific proposal. In preparing this text we have noted the drafting work of other stakeholders, including the ARIN CRISP team and the IETF’s ianaplan Working Group. To be clear, this text will form the basis of our position as we begin discussions with representatives from the other RIR communities; the final response to the ICG’s RFP may look somewhat different, depending on outcome of the full CRISP team's discussions. We would like to share our draft text on Section 3 of the RFP document, which covers the details of the proposal itself. We would appreciate any community feedback on the proposal we have drafted: ======= > III. Proposed Post-Transition Oversight and Accountability > Arrangements > > This section should describe what changes your community is proposing > to the arrangements listed in Section II.B in light of the > transition. If your community is proposing to replace one or more > existing arrangements with new arrangements, that replacement should > be explained and all of the elements listed in Section II.B should be > described for the new arrangements. Your community should provide its > rationale and justification for the new arrangements. > > If your community’s proposal carries any implications for the > interface between the IANA functions and existing policy arrangements > described in Section II.A, those implications should be described > here. > > If your community is not proposing changes to arrangements listed in > Section II.B, the rationale and justification for that choice should > be provided here. A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on the continuity of Internet number-related IANA services provided by ICANN or the ongoing community processes for development of policies relating to those services. However, it would remove a significant element of oversight from the current system. The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA functions operator's accountability to the open, bottom-up numbers community. The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five Regional Internet Registries (RIRs). The contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the global Policy Development Process (gPDP). The agreement would include specific requirements for performance and reporting, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. As noted in numerous NRO communications over the past decade, the RIRs have been very satisfied with the performance of ICANN in the role of IANA functions operator. Taking this into account, and considering the strong desires expressed in the five RIR communities' IANA stewardship discussions for stability and a minimum of operational change, the Internet numbering community believes that ICANN should remain in the role of IANA functions operator for at least the initial term of the new contract. - The RIRs will coordinate with their communities and the ICANN Board to develop an IANA Service Level Agreement by June 2015. The processes for developing, agreeing and implementing policy relating to management of the global Internet number resource pools would require no change to accommodate this new arrangement. The text of the ICANN ASO MoU (https://aso.icann.org/documents/memorandums-of-understanding/memorandum-of-…) meets the current and anticipated requirements for a community-driven global policy development process. As an additional measure of security and stability, the RIRs have documented their individual accountability and governance mechanisms, and asked the community-based Number Resource Organization Number Council (NRO NC) to undertake a review of these mechanisms and make recommendations for improvements that may be warranted given the nature of the stewardship transition for Internet number resources. - The RIRs will coordinate with coordinate with the NRO NC to identify any areas covered by the RIR Governance Matrix that require further attention and address those issues by June 2015. ====== We will share further information on the timing of the upcoming CRISP team teleconference shortly. Best regards, Andrei Robachevsky on behalf of the RIPE CRISP team

1 0

Webinars Announced: CWG On Naming Related Functions Public Consultation on Draft Transition Proposal
by Jaap Akkerhuis 02 Dec '14

02 Dec '14

All, No doubt Lots of folks have seen this, but in case you didn't, the announcement is about: "Following the request of the National Telecommunications and Information Administration (NTIA) for ICANN to "convene a multistakeholder process to develop a plan to transition the U.S. government stewardship role" with regard to the IANA Functions and related root zone management, a Cross Community Working Group (CWG) was tasked with developing a consolidated transition proposal for the elements of the IANA Functions relating to the Domain Name System (DNS). The CWG has now published its draft transition proposal for public comment. Comments can be submitted until 22 December at 23:59 UTC." and can be found at <https://www.icann.org/news/announcement-3-2014-12-01-en>. jaap

1 0