From jaap at nlnetlabs.nl Tue Dec 2 12:09:54 2014 From: jaap at nlnetlabs.nl (Jaap Akkerhuis) Date: Tue, 02 Dec 2014 12:09:54 +0100 Subject: [cooperation-wg] Webinars Announced: CWG On Naming Related Functions Public Consultation on Draft Transition Proposal Message-ID: <201412021109.sB2B9sYK088448@bela.nlnetlabs.nl> 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 . jaap From andrei.robachevsky at gmail.com Tue Dec 2 14:46:45 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Tue, 02 Dec 2014 14:46:45 +0100 Subject: [cooperation-wg] Initial text for the Post-Transition Oversight and Accountability Arrangements Message-ID: <547DC2C5.9090008@gmail.com> 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-understanding/) 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From nurani at netnod.se Mon Dec 8 11:21:44 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 8 Dec 2014 11:21:44 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft Agenda - CRISP Team Teleconference 1 - Tuesday, 9 December 2014 References: <54843126.2040508@ripe.net> Message-ID: 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 > Subject: [NRO-IANAXFER] Draft Agenda - CRISP Team Teleconference 1 - Tuesday, 9 December 2014 > Date: 7 december 2014 11:51:18 CET > To: ianaxfer at 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 at 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 at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Tue Dec 9 17:53:01 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Tue, 9 Dec 2014 17:53:01 +0100 Subject: [cooperation-wg] CRISP Team Holds First Teleconference Message-ID: <55C9A406-E571-4BA7-B14C-2717C618BE71@netnod.se> 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 at 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 http://www.netnod.se From daniel.karrenberg at ripe.net Wed Dec 10 13:47:36 2014 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 10 Dec 2014 13:47:36 +0100 Subject: [cooperation-wg] CRISP Team Holds First Teleconference In-Reply-To: <55C9A406-E571-4BA7-B14C-2717C618BE71@netnod.se> References: <55C9A406-E571-4BA7-B14C-2717C618BE71@netnod.se> Message-ID: <548840E8.3080305@ripe.net> Nurani, thank you. It is re-assuring to hear that the CRISP team has started its work. Is there a single URL where one can find general information about the team, minutes and agendas; and hopefully soon draft proposals? Having something like that would be extremely useful and increase the perception of transparency. I would be delighted to pass such a pointer to the ICG because we cannot hope to make our common, quite ambitious, time schedule without keeping abreast of what the communities are doing. Daniel From nurani at netnod.se Wed Dec 10 16:14:06 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Wed, 10 Dec 2014 16:14:06 +0100 Subject: [cooperation-wg] CRISP Team Holds First Teleconference In-Reply-To: <548840E8.3080305@ripe.net> References: <55C9A406-E571-4BA7-B14C-2717C618BE71@netnod.se> <548840E8.3080305@ripe.net> Message-ID: <9D067A44-89AC-4986-A622-1FA12C7430BC@netnod.se> Daniel, Thank you. Yes, I agree that it from a transparency perspective, is important that the work of the CRISP team (timelines, agendas, notes, produced documents etc) is documented and made publicly available. That is certainly the intention. I believe the NRO secretariat is working on providing this space in one single place on their website. As soon as we have this, we'll send it on to the Cooperation Working Group. (It is my understanding that this will happen in the coming 24 hours.) Kind regards, Nurani On 10 dec 2014, at 13:47, Daniel Karrenberg wrote: > Nurani, > > thank you. It is re-assuring to hear that the CRISP team has started its > work. > > Is there a single URL where one can find general information about the > team, minutes and agendas; and hopefully soon draft proposals? > > Having something like that would be extremely useful and increase the > perception of transparency. I would be delighted to pass such a pointer > to the ICG because we cannot hope to make our common, quite ambitious, > time schedule without keeping abreast of what the communities are doing. > > Daniel From nurani at netnod.se Thu Dec 11 08:48:11 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 11 Dec 2014 08:48:11 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] CRISP Team 2nd Teleconference Thursday December 11th 2014 @ 13:00 UTC References: <4CEB9B72-7DDD-4C6A-8680-6DF6EA953BD8@nro.net> Message-ID: 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 > Date: 10 december 2014 08:35:30 CET > To: > 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 at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WebEx_Meeting.ics Type: text/calendar Size: 3977 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisb at ripe.net Thu Dec 11 13:52:17 2014 From: chrisb at ripe.net (Chris Buckridge) Date: Thu, 11 Dec 2014 13:52:17 +0100 Subject: [cooperation-wg] CRISP Team Holds First Teleconference In-Reply-To: <9D067A44-89AC-4986-A622-1FA12C7430BC@netnod.se> References: <55C9A406-E571-4BA7-B14C-2717C618BE71@netnod.se> <548840E8.3080305@ripe.net> <9D067A44-89AC-4986-A622-1FA12C7430BC@netnod.se> Message-ID: <9DD43D42-B8D3-493F-BBA3-CB046E1098AC@ripe.net> Hi all, Following up on Nurani?s comment, this information has now been made available on the NRO website: https://www.nro.net/crisp-team Chris On 10 Dec 2014, at 16:14, Nurani Nimpuno wrote: > Daniel, > > Thank you. > > Yes, I agree that it from a transparency perspective, is important that the work of the CRISP team (timelines, agendas, notes, produced documents etc) is documented and made publicly available. That is certainly the intention. > > I believe the NRO secretariat is working on providing this space in one single place on their website. As soon as we have this, we'll send it on to the Cooperation Working Group. (It is my understanding that this will happen in the coming 24 hours.) > > Kind regards, > > Nurani > > > > On 10 dec 2014, at 13:47, Daniel Karrenberg wrote: > >> Nurani, >> >> thank you. It is re-assuring to hear that the CRISP team has started its >> work. >> >> Is there a single URL where one can find general information about the >> team, minutes and agendas; and hopefully soon draft proposals? >> >> Having something like that would be extremely useful and increase the >> perception of transparency. I would be delighted to pass such a pointer >> to the ICG because we cannot hope to make our common, quite ambitious, >> time schedule without keeping abreast of what the communities are doing. >> >> Daniel > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2608 bytes Desc: not available URL: From andrei.robachevsky at gmail.com Thu Dec 11 14:07:49 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Thu, 11 Dec 2014 14:07:49 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft for discussion In-Reply-To: <20141211130346.GE26759@apb-laptoy.apb.alt.za> References: <20141211130346.GE26759@apb-laptoy.apb.alt.za> Message-ID: <54899725.3030104@gmail.com> 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 To: ianaxfer at 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) -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP IANA PROPOSAL Draft 10122014-clean.docx Type: application/octet-stream Size: 36449 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From andrei.robachevsky at gmail.com Thu Dec 11 15:22:35 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Thu, 11 Dec 2014 15:22:35 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft for discussion In-Reply-To: <54899725.3030104@gmail.com> References: <20141211130346.GE26759@apb-laptoy.apb.alt.za> <54899725.3030104@gmail.com> Message-ID: <5489A8AB.30503@gmail.com> Dear colleagues, Apologies for sending this draft in a proprietary format. We will ensure that in the future we communicate materials in a more portable form. Please find the document attached as a PDF. Regards, Andrei Andrei Robachevsky wrote on 11/12/14 14:07: > 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 > To: ianaxfer at 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) > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP IANA PROPOSAL Draft 10122014-clean.pdf Type: application/pdf Size: 166872 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From nurani at netnod.se Thu Dec 11 15:32:30 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 11 Dec 2014 15:32:30 +0100 Subject: [cooperation-wg] Minutes from the first CRISP teleconference Message-ID: 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP December 9 meeting DRAFT NOTES.pdf Type: application/pdf Size: 67510 bytes Desc: not available URL: -------------- next part -------------- From roland at internetpolicyagency.com Thu Dec 11 17:17:18 2014 From: roland at internetpolicyagency.com (Roland Perry) Date: Thu, 11 Dec 2014 16:17:18 +0000 Subject: [cooperation-wg] Minutes from the first CRISP teleconference In-Reply-To: References: Message-ID: <+3KGv7IOOciUFAOv@internetpolicyagency.com> >Action: GV to create a private, closed mailing list for CRISP members >as soon as possible. What?? -- Roland Perry From daniel.karrenberg at ripe.net Thu Dec 11 17:37:13 2014 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Thu, 11 Dec 2014 17:37:13 +0100 Subject: [cooperation-wg] Minutes from the first CRISP teleconference In-Reply-To: <+3KGv7IOOciUFAOv@internetpolicyagency.com> References: <+3KGv7IOOciUFAOv@internetpolicyagency.com> Message-ID: <5489C839.6050603@ripe.net> On 11.12.14 17:17 , Roland Perry wrote: > >Action: GV to create a private, closed mailing list for CRISP members > >as soon as possible. > > What?? The ICG has a mailing list fort conducting committee work: . That list is publicly archived but has posting rights only for committee members and support staff. I guess 'closed' here is intended to mean something like that. But I am only speculating ..... From andrei.robachevsky at gmail.com Thu Dec 11 17:56:03 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Thu, 11 Dec 2014 17:56:03 +0100 Subject: [cooperation-wg] Minutes from the first CRISP teleconference In-Reply-To: <+3KGv7IOOciUFAOv@internetpolicyagency.com> References: <+3KGv7IOOciUFAOv@internetpolicyagency.com> Message-ID: <5489CCA3.3090401@gmail.com> Roland, Roland Perry wrote on 11/12/14 17:17: >>Action: GV to create a private, closed mailing list for CRISP members >>as soon as possible. > > What?? In the interest of efficiency it was decided to crease an internal closed mailing list to allow quick editing iterations on the proposed response and use the ianaxfer list as intended for engaging with the community, and soliciting and discussing their feedback. At the CRISP Team call toady we again discussed this matter and I think (the confirmed notes will be released tomorrow) decided to provide public archives. Regards, Andrei -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From marty at akamai.com Thu Dec 11 19:43:39 2014 From: marty at akamai.com (Hannigan, Martin) Date: Thu, 11 Dec 2014 13:43:39 -0500 Subject: [cooperation-wg] Minutes from the first CRISP teleconference In-Reply-To: <5489CCA3.3090401@gmail.com> References: <+3KGv7IOOciUFAOv@internetpolicyagency.com> <5489CCA3.3090401@gmail.com> Message-ID: > On Dec 11, 2014, at 11:56, Andrei Robachevsky wrote: > > Roland, > > Roland Perry wrote on 11/12/14 17:17: >>> Action: GV to create a private, closed mailing list for CRISP members >>> as soon as possible. >> >> What?? > > In the interest of efficiency it was decided to crease an internal > closed mailing > list to allow quick editing iterations on the proposed response and use > the ianaxfer list as intended for engaging with the community, and > soliciting and discussing their feedback. > > At the CRISP Team call toady we again discussed this matter and I think > (the confirmed notes will be released tomorrow) decided to provide > public archives. > > Regards, > > Andrei > That's sounds like a decent compromise. Best, -M< From nurani at netnod.se Mon Dec 15 23:13:57 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 15 Dec 2014 23:13:57 +0100 Subject: [cooperation-wg] Minutes from the CRISP team teleconference 11 December 2014 Message-ID: <4DAA81E9-DD1E-4D47-B2E3-0BA66A905972@netnod.se> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP-December-11-meeting-DRAFT-NOTES-v2.pdf Type: application/pdf Size: 64871 bytes Desc: not available URL: -------------- next part -------------- -- Nurani Nimpuno Head of Outreach & Communications, Netnod , http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden --------------------------------------------- From paf at frobbit.se Tue Dec 16 07:24:13 2014 From: paf at frobbit.se (=?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?=) Date: Tue, 16 Dec 2014 07:24:13 +0100 Subject: [cooperation-wg] Third document from SSAC on IANA Stewardship Transition Published Message-ID: <22583382-FEE5-47B6-8E3D-52C79224BD9E@frobbit.se> 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) SAC-068 : SSAC Report on the IANA Functions Contract (10 October 2014) SAC-069 : SSAC Advisory on Maintaining the Security and Stability of the IANA Functions Through the Stewardship Transition (10 December 2014) 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Message signed with OpenPGP using GPGMail URL: From nurani at netnod.se Tue Dec 16 14:32:41 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Tue, 16 Dec 2014 14:32:41 +0100 Subject: [cooperation-wg] CRISP Team 3rd Teleconference Wed December 17th Webex Details References: <952BE8BB-30E5-494C-A906-2E4BD66E436F@nro.net> Message-ID: <0AB37BE3-DAB1-4EE6-9A06-B0C7C0AA5101@netnod.se> Dear Colleagues, Please find below the details of the third CRISP Team teleconference. CRISP teleconferences are open to observers. (All CRISP related information is gathered at: https://www.nro.net/crisp-team) Kind regards, Nurani On behalf of the RIPE CRISP Team ---------------------------------------------------------- Nurani Nimpuno Head of Outreach & Communications, Netnod http://www.netnod.se Begin forwarded message: > From: German Valdez > Subject: [NRO-IANAXFER] CRISP Team 3rd Teleconference Wed December 17th Webex Details > Date: 11 december 2014 17:08:55 CET > To: > > > Hi > > This is an invitation to follow the CRISP Team 3rd Teleconference that will be held on Wednesday December 17th at 13:00 UTC. > > CRISP Teleconference are opened for observers. > > Webex Details below > > regards > > German Valdez > NRO > > ====== > > > CRISP Team 3rd Teleconference > Wednesday, December 17, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: 704 944 471 > 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: 704 944 471 > 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 at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WebEx_Meeting.ics Type: text/calendar Size: 3977 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisb at ripe.net Thu Dec 18 09:49:45 2014 From: chrisb at ripe.net (Chris Buckridge) Date: Thu, 18 Dec 2014 09:49:45 +0100 Subject: [cooperation-wg] Fwd: Invitation CRISP Team 4th Teleconference Thursday 18th December 2014 13:00 UTC References: Message-ID: <852EB019-9B8B-4847-9C8F-1E4893B58037@ripe.net> Dear colleagues, Please find below the details to join a CRISP team teleconference today at 13:00 UTC. This call was added to the CRISP timeline on yesterday?s teleconference. Best regards, Chris Buckridge, RIPE NCC Begin forwarded message: > From: German Valdez > Subject: [NRO-IANAXFER] Invitation CRISP Team 4th Teleconference Thursday 18th December 2014 13:00 UTC > Date: 17 Dec 2014 16:57:49 GMT+1 > To: > > > Hi > > This is an invitation to participate as observer of the next CRISP Team teleconference to be held on Thursday December 18th 2014 at 13:00 UTC. Webex information below > > Information of previous meetings, including webex audio files, can be found at > > http://www.nro.net/crisp-team > > Regards > > German Valdez > NRO > > > CRISP Team 4th Teleconference > Thursday, December 18, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: 704 791 188 > 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: 704 791 188 > 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 at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2608 bytes Desc: not available URL: From maria at sunet.se Thu Dec 18 11:37:07 2014 From: maria at sunet.se (=?utf-8?Q?Maria_H=C3=A4ll?=) Date: Thu, 18 Dec 2014 11:37:07 +0100 Subject: [cooperation-wg] Minutes session 1 and 2 Cooperation WG at RIPE69 Message-ID: Hi all Here below you find the minutes from both Cooperation WG sessions Thursday 5th November 2014, at RIPE69 in London. We wish you all a Merry Xmas and a Happy New Year! See you soon again! Best, Maria, Meredith, Alain co-chairs Cooperation WG Session 1 - IANA Oversight Transition and Internet Governance After giving a brief background to the IANA stewardship discussions, Chris Buckridge presented on the processes currently underway at the RIR community level (including the formation of the Consolidated RIR IANA Stewardship, or CRISP, team) and global level to develop a stewardship transition proposal to the United States government. He also detailed the current draft RIPE community principles that have been distributed on the Cooperation Working Group mailing list and the subject of some discussion, and gave an outline of what the RIPE NCC believes a Service Level Agreement between the RIRs and the IANA functions operator would look like. He concluded with a summary of discussions to date in the other RIR communities. Athina Fragkouli gave a presentation on the inter-related process going on to ensure and enhance the accountability of all organisational players related to the IANA functions, including the RIRs and ICANN. Paul Rendek led an open discussion of the issues raised in the two presentations and of the RIPE communities position in relation to IANA stewardship. Randy Bush noted that the Internet Engineering Task Force (IETF) already has a Service Level Agreement in place with ICANN regarding ICANN?s management of the IANA functions relating to protocol parameters, and asked if the plans for an RIR-IANA SLA were being coordinated with IETF participants. Athina noted that the RIPE NCC and CRISP team will look to coordinate with the IETF and investigate opportunities to build on what they have already developed. Daniel Karrenberg agreed with Athina, and speaking as a member of the IANA Stewardship Transition Coordination Group (ICG), noted that it is an explicit part of the process that all communities talk to each other while developing their parts of the proposal. He stressed that the current time line cannot be met should the ICG receive incompatible proposals and added that when the CRISP team is constituted, ICG members will do their best to help ensure that the CRISP team does not work in isolation. Patrik F?ltstr?m and Chris Buckridge noted the documents produced by ICANN's Security and Stability Advisory Committee (SSAC) on the IANA functions themselves and the existing contractual relationships that currently relate to their operation. Randy also noted that there can be no accountability without transparency - he suggested that ICANN has not been a good example of transparency, while some of the RIRs have done better in this regard. Alexander Isavnin noted that organisations are ?accountable? to someone, and the question of to whom ICANN or the RIRs are accountable will be important to many stakeholders, particularly in government. He also suggested that informed community contribution to this process will rely on published analysis of the existing documents and arrangements. Salam Yamout, noting the ICANN accountability process, suggested that we think about longer term goals for ICANN and its accountability. Paul Rendek suggested that this highlighted the importance of ensuring that the IANA stewardship and ICANN accountability are considered separately (as Athina noted in her presentation on the Enhancing ICANN Accountability Cross Community Working Group) and particularly the need to emphasise that longer term accountability goals not hinder the IANA stewardship transition. He noted that while the RIRs are not perfect, they can provide an example in terms of what specific ICANN accountability issues will need to be resolved ahead of the IANA stewardship transition. Carsten Schiefner asked whether the RIPE NCC and community were regarding it as settled that ICANN would continue in its role as IANA functions operator. Responding, Daniel Karrenberg noted that while there is not clear consensus for the long-run, minimal change to a working system has been identified as an important goal by the community; in the short-term, that means ICANN continuing in the role. He added that the RIRs have been happy with ICANN's performance of these duties, but he stressed that moving forward, the RIRs need to make sure a contract is in place and that the term and options for termination of that contract are clearly spelled out. He also noted that not specifying ICANN in the role at this stage of the process would be seen as a specific political statement. Tahar Schaa asked what are the risks in this process are, and whether the RIPE NCC has an opinion on whether this is a good thing or a risky thing. Paul Rendek noted that the idea of this transition is not new, and that while there was some risk that this process would end up with no change to the status quo, the status quo was actually working. He noted, however, that a failure to transition the NTIA out of its current role would have political repercussions, as highlighted in discussion at the recent meeting in Brussels with RIPE NCC, CENTR and EU government representatives. Filiz Yilmaz described IANA stewardship as a colossal opportunity and a chance to bring RIR principles to parts of the Internet community where accountability has not been so clear. In terms of risk, she agreed that maximum stability must be prioritised at all stages of the discussion and in any eventual SLA, but we don?t want to see the process get stuck and it is important that the RIR legal teams taking a lead here. Ashley Heineman of the NTIA offered her thanks for the invitation to sit in on the session, and stressed the importance of the NTIA understanding what the communities are thinking. She noted that the NTIA is happy to be a resource in terms of answering questions about their role and the existing contracts. Sandy Murphy noted that the NTIA did not promise that they would accept the final proposal that it receives, and asked whether that has changed. Ashley noted that while this has not changed, the NTIA and the U.S. government are very committed to transition process, and as long as the proposal is within the framework of clear basic requirements laid out in the initial announcement, the NTIA are happy to review with the intention of approving the proposal. Jason Schiller noted that the output of the recent LACNIC meeting suggests that the contracting party would be Number Resource Organization (NRO), while the current RIPE draft says that the RIRs would be the contracting parties. Axel Pawlik noted that the NRO is not incorporated, and that any legal agreement would need to be signed by the RIRs. Patrik F?ltstr?m noted that when it comes to merging proposals from the three communities (names, numbers and protocol parameters), the names is unique, as this is the only place that NTIA has an operational role - he stressed that it will therefore be important for the CRISP team to work with communities that have slightly different needs. Paul Rendek agreed that the names community does not have the same kind of communities or processes. Patrik noted that for IANA to work, there needs to be trust between the requestor of IANA changes and the IANA functions operator that makes those changes, and this is a central issue to the stewardship transition discussion. Randy Bush noted that he understands that the IETF and the RIRs have been happy with ICANN?s performance as IANA operator for many years, and that in these cases, IANA is essentially a bookkeeper for the Internet. But he too noted that the situation for names is different. Heather Schiller questioned what about this process would improve the transparency of ICANN itself, and suggested that this was one of the most problematic issues. Paul Rendek noted that the RIRs are not entrenched in ICANN, but that the RIRs can demonstrate our own accountability, and we can help with building the community there. Heather argued that monetisation of the DNS means that in the ICANN context, little attention is paid to the RIRs and the numbering community, but the operation of ICANN is important to this community. Paul agreed, but noted that while ICANN accountability is a long discussion, a proposal for IANA stewardship is needed by next summer. Hans Petter Holen suggested that it is important for the community to look at what RIPE NCC is: an organisation accountable to its members via the Executive Board, and also accountable to RIPE as an open policy forum. He stressed that the IANA operator should be accountable to ?us? (the global Internet) - if that means entering into a contract with a non-transparent, open organisation, we need to make sure that our lawyers ensure that we have the contractual power over that organisation. He noted that in terms of names, ICANN needs to be more accountable, but that the big question for the RIR communities is, can we trust an organisation that?s not yet open and transparent? Paul Rendek suggested that no responsible administration (including the NTIA) would release stewardship of these functions to a new, untested process, and therefore we need to stay true to our existing principles, not make up new ones. John Curran noted that the existing policy authorities are already recognised, the current system works and we can keep ICANN in place without much changing. However, such a change could mean that the RIRs are eternally in this stewardship role, meaning the RIRs need to make sure that they are accountable to their communities. The ability for someone else to intervene goes away with the change being proposed. Jim Reid argued that we need to avoid being sidetracked by ICANN accountability issues, which may never be fully solved, and focus on the issues relating to the IANA functions issues, which are clearly understood. Randy Bush disagreed, arguing that the community is responsible not just to people in this room, but to the users, and while taking on ICANN accountability is a large problem, the pressure to get the IANA stewardship transition successfully completed may provide us with the only chance to solve the bigger accountability issue. Ruediger Volk noted that while the RIPE NCC is accountable to the relatively small stakeholder group of RIPE operators, it must also consider users and the broader world, and he noted that in other RIR discussions (in LACNIC for instance), the communities have seen a need to reach out further. He noted that this may be walking into a swamp, but it is a question that the RIPE community needs to ask. Paul Rendek noted that while LACNIC have raised the issue of whether RIR community processes fit the definition of multistakeholder, the RIPE community unquestionably operates according to bottom-up, open, inclusive processes, and we should stay true to those principles in any IANA proposal. Paul Rendek also noted that other discussions about the IANA stewardship issues have been facilitated by the RIPE NCC in regional meetings and network operator groups across the service region. The resounding impression from those events is community members asking ?how will this affect my business and my relationship with RIPE NCC??. Paul closed the discussion and encouraged everyone to continue the discussions on the Cooperation Working Group mailing list. Session 2 Securing the Internet Post-Snowden: Securing hardware with Cryptech, Randy Bush Randy Bush provided an update on Cryptech, a community project to develop a Hardware Security Module. He briefly described the project, gave an update on its progress to date and outlined what the project needs from the technical community, policymakers, industry partners and supporters generally. Meredith Whittaker asked when the HSMs would be in production. Randy noted that the goal of the project is open source design, rather than actual production, but that as part of their work, the project partners plan to produce around 50 laptop boards in coming month for people to play with. Vesna Manojlovic asked for more specific details on how people in the RIPE community could help. Randy noted that money would be very useful to progressing the project, but that any additional crypto, hardware or software tool chain expertise would also be useful. Shane Kerr asked about plans for certification. Randy noted that while there are no immediate plans for certification, the project partners do have FIPS certification in mind. The expectation is that someone using the Cryptech designs could make a FIPS-certified product. Sasha van Geffen asked whether this was simply shifting the security problem to the production side of things, particularly given the patent environment surrounding chip design. Randy noted that the project includes an academic with expertise in patent law, and all efforts are made to use well?known open algorithms, so they are not too worried about patents. He conceded that trojans are more of a concern. Sasha clarified that he was asking how they can ensure that their design is actually built into machines as intended. Randy agreed that this is a challenge - if you pay Juniper to put the Cryptech HSM on a board, how do you know that you are getting that design? Designing for testability of the whole production process, not just the random number generator itself, is vital. Meredith Whittaker noted that auditability is a major issue, and also a subject under consideration in the ?Caring for the Core Infrastructure Commons? BoF session. Patrik F?ltstr?m asked whether the Cryptech team was working with any certification agencies to ensure that those agencies can use the final design, and volunteered his assistance in that. Randy pointed out that they were deliberately not working with agencies, as they are wary of how strongly their engineering decisions are influenced by any part of the culture, but that they believe they can design for certification. But he stressed the importance of engagement of engineers from other places, noting that they have a Russian crypto designer on the team, but are unable to get anyone from China. Measuring and Preserving Freedom of Expression Online Technology, Policy, and the Need to Engage Local Communities, Amelia Andersdotter Amelia Andersdotter, a former Member of the European Parliament (MEP), spoke about the need for better engagement by technical community (and the public more generally) with legislative processes and the parliamentarians that have a role in those processes. Amelia noted her past experience as a recently-unseated Swedish MEP for the Pirate Party, and her hope that she might use this experience to help people engage with the European Parliament. She noted the challenge in having local constituencies engage in larger legislative processes, but noted that Parliament is quite different from national regulators or governments Ministries and departments, as the Parliamentarians are directly accountable to voters, whereas government employees are often more comfortable and stable in their role. Amelie highlighted copyright reform as an issue that can affect people directly, and which is the subject of a current legislative proposal coming from the European Commission. She noted that this proposal has been very contentious, and there has been significant public participation, but she emphasised that the outcome of this discussion will affect the way decisions are made about technical issues. One strategy that Amelia emphasised to effectively influence discussion in the European Parliament was to engage directly with the local councils rather than parliamentarians or larger government structures. This is because the local councils have a key role in selecting the lists of MEP candidates for each party, giving them a stronger voice in the process. Alexander Isavnin thanked Amelia for her presentation, but noted that it spoke only about engaging the institutions of the European Union, and asked how it might relate to engagement in Russia. Amelia noted that the former Russian president had been the only leader to ever discuss full reform of the Berne Convention [for the Protection of Literary and Artistic Works], but that that this did not seem to have carried over to the current administration. Alexander asked whether Amelia felt Internet services should be regarded as utility services for everyone and regulated accordingly. Amelia emphasised her belief that a competitive market is important, and while not seeing telecommunications as ?critical infrastructure?, it is vital to allow as many people as possible to have access. She stressed the importance of action at the local level, looking at municipalities that have provided wifi access and other initiatives. Carsten Schieffner noted that MEPs are bombarded with many issues, and asked how local communities could make themselves heard. Amelia noted that (absent money to pay lobbyists) you need to find someone whose time and attention will be valuable to an MEP, and again emphasised the role of municipal councillors - she noted that the challenge is getting those local councillors interested in your issue. George Michaelson noted what he saw as very problematic legislative proposals coming out of the European Commission (EC) in recent years last year, and noted his general scepticism of technology when it comes to advancing social issues. Amelia agreed that there had been justified criticism of EC proposals in the past, but that on the copyright issue there has been a useful public consultation, more than 5000 citizens contributing (a summary of these contributions is available on the EC website). But she stressed that, given the large corporations with a stake in these discussions, it is only through public engagement that any idea of the public good will be preserved and reflected in the legislation. What Does it Mean to be a Socially Responsible ISP? Sacha van Geffen Sacha van Geffen of Dutch ISP Greenhost discussed his organisation?s work with activist communities, their approach to privacy preservation and making ecologically responsible choices. Chris Baker from DYN noted that while Tor may be good, it is often used by criminals, and asked what tools Greenhost are using to keep botnets and other abuse in check. Sacha noted that highways also cater to criminals, but agreed that there are good policies you can set to Tor exit nodes to minimise problems. He agreed that there is some collateral damage, but also suggested that criminals have more sophisticated strategies than just using Tor. Chris suggested that it was also better to hedge across a range of technologies rather than focusing on a well-known technology like Tor, which Sacha agreed was important. ISP Interconnection and Consumer Internet Performance, Collin Anderson Collin Anderson, an independent researcher with the University of Pennsylvania and the Open Technology Institute, discussed his collaborative work using open data to measure the impact of ISP relationships on consumer Internet access. Shane Kerr suggested that this might seem to be work that the regulator should be doing, and asked how much impact it was likely to have in directing policies? Colin stated that the success of study is based on the number of civil society organisations citing it, on regulators interacting with the data, and on how much the work informs the public debate. He also noted that research teams like his provide infrastructure that a lot of governments cannot afford at this time, so if any way of getting this data into the governmental conversations is a success. From nurani at netnod.se Thu Dec 18 12:07:01 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 18 Dec 2014 12:07:01 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Update on Timeline Re: Timeline (Re: [Iana-transition] 1st CRISP Meeting Notes) References: <54924D7B.9030505@nic.ad.jp> Message-ID: FYI. Nurani Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Update on Timeline Re: Timeline (Re: [Iana-transition] 1st CRISP Meeting Notes) > Date: 18 december 2014 04:43:55 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > I would like to update there has been a change in CRISP team timeline in > publishing the initial draft. > > First draft to be published : 19 Dec 2014 > Second draft to be published : 8 Jan 2015 > Final proposal to be sent to ICG: 15 Jan 2015 > > The next CRISP team Teleconference is scheduled on Thursday December > 18th 2014 at 13:00 UTC. > > To join as an observer, please see a seperate meeting invitation sent > out by German. The call is open to observers as all CRISP Team > Teleconferences. > > > Regards, > Izumi Okutani > > (2014/12/12 20:11), Izumi Okutani wrote: >> Dear Colleagues, >> >> >> You can see the latest timeline of our schedule from here: >> >> https://www.nro.net/wp-content/uploads/CRISP-Team-Timeline-141211.pdf >> >> The current plan is to publish and share on this list >> >> - the initial draft on 18th Dec 2014 >> - 2nd draft on 5th Jan 2015 >> >> We'll keep you posted in case there are any changes. >> >> Our next call is schedule on 17th Dec 13:00 UTC, as the Webex invitation >> has already been sent out on this list earlier by German. >> >> >> Regards, >> Izumi >> From andrei.robachevsky at gmail.com Fri Dec 19 11:34:43 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Fri, 19 Dec 2014 11:34:43 +0100 Subject: [cooperation-wg] First Draft, Seeking Feedback: Internet Numbers Community IANA Stewardship Proposal Message-ID: <5493FF43.6020309@gmail.com> Dear colleagues, The Consolidated RIR IANA Stewardship Proposal (CRISP) team has now published the first draft of an Internet numbers community proposal for the future of the IANA stewardship. The draft is available here: https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf Feedback from the global numbers community is now being sought. This feedback can be sent to the global NRO IANA stewardship discussion list, , or can be sent to the appropriate regional mailing lists. The RIPE CRISP representatives will be closely following discussions on the RIPE Cooperation Working Group mailing list, as well as the global discussion. We would strongly encourage those RIPE community members with an interest in this topic to contribute to the global discussion on . The deadline for all feedback on this first draft is Monday 5 January 2015. The CRISP team will then produce a further draft by 8 January, which will be open for final feedback from the communities before submission to the IANA Stewardship Transition Coordination Group (ICG) by 15 January. The RIPE CRISP representatives circulated some draft text of an initial proposal to the RIPE Cooperation WG mailing list on 28 November. We felt that this draft captured the RIPE community input. A key addition in this first CRISP draft is the formation of a community-based Review Committee. This committee would produce an annual, non-binding report on the performance of the IANA operator, a concept that evolved from the Multistakeholder Oversight Numbers Council (MONC) that was originally proposed by the LACNIC community. We feel that this Review Committee addresses the concerns expressed by the LACNIC community, while not creating unnecessary complex new structures. We look forward to hearing from the RIPE community on this important process. Best regards, Andrei Robachevsky, on behalf of the RIPE CRISP representatives Important Links ?? Subscribe to the RIPE Cooperation Working Group mailing list: http://www.ripe.net/mailman/listinfo/cooperation-wg/ Suscribe to the NRO IANA Transfer mailing list: https://www.nro.net/mailman/listinfo/ianaxfer Information on the CRISP team and its work [includes members, charter, teleconference minutes and audio]: https://www.nro.net/crisp-team Public archive of the internal CRISP mailing list: https://www.nro.net/pipermail/ianaxfer/ RIR community timeline for IANA stewardship discussion and links to regional outputs: https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs-engagement-in-iana-stewardship-transition-process RIPE NCC IANA stewardship information: https://www.ripe.net/iana-stewardship-transition -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From andrei.robachevsky at gmail.com Fri Dec 19 15:19:35 2014 From: andrei.robachevsky at gmail.com (Andrei Robachevsky) Date: Fri, 19 Dec 2014 15:19:35 +0100 Subject: [cooperation-wg] Archives of the internal CRISP mailinglist are available online Message-ID: <549433F7.8010700@gmail.com> Dear colleagues, Let me apologise for a wrong url I provided in my previous mail ("First Draft, Seeking Feedback: Internet Numbers Community IANA Stewardship Proposal") when referring to the public archives of the CRISP internal mailinglist. The correct archives location is: https://www.nro.net/pipermail/crisp/ Regards, Andrei -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 244 bytes Desc: OpenPGP digital signature URL: From nurani at netnod.se Mon Dec 22 00:08:49 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 22 Dec 2014 00:08:49 +0100 Subject: [cooperation-wg] Fwd: CRISP 5th Teleconference Monday December 22nd at 13:00 UTC References: <536B55D6-221A-487D-B031-05DE87BA7B5E@nro.net> Message-ID: Dear colleagues, Please find information about the fifth teleconference of the CRISP team below. The CRISP teleconferences are open to observers. Kind regards, Nurani Begin forwarded message: > From: German Valdez > Date: 21 december 2014 12:44:15 CET > To: > Subject: [NRO-IANAXFER] CRISP 5th Teleconference Monday December 22nd at 13:00 UTC > > > Hi > > This is an invitation to join the 5th CRISP Teleconference > > Webex details below > > Regards > > German Valdez > NRO > > ===== > > > CRISP Team 5th Teleconference > Monday, December 22, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > https://ripencc.webex.com/ripencc/j.php?MTID=m0348482bacaeff18e36634cd53cce3b1 > > Meeting number: > 707 682 475 > 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: 707 682 475 > Global call-inbers | Toll-free calling restrictions > > Add this meeting to your calendar. > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Mon Dec 22 15:13:47 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 22 Dec 2014 15:13:47 +0100 Subject: [cooperation-wg] Fwd: First Draft, Seeking Feedback: Internet Numbers Community IANA Stewardship Proposal References: <5493FF43.6020309@gmail.com> Message-ID: <9C05AECB-E61C-4655-8F91-694C81934F97@netnod.se> Dear colleagues, Apologies for the interruption as most of you are probably starting your Christmas holidays. But I would like to ask you all in the gentlest way possible, to get on the global NRO IANA stewardship discussion list (ianaxfer at nro.net) and provide any comments you may have to the first draft. As Andrei's mail points out, the timeline is unfortunately very short. We need feedback on the first draft on 5 January 2015. So far, there are very few comments, and I can see no comments from the RIPE community, who I know has valuable input to give. Thanks, Nurani On behalf of the RIPE CRISP team Begin forwarded message: > From: Andrei Robachevsky > Subject: [cooperation-wg] First Draft, Seeking Feedback: Internet Numbers Community IANA Stewardship Proposal > Date: 19 december 2014 11:34:43 CET > To: RIPE Cooperation Working Group > > Dear colleagues, > > The Consolidated RIR IANA Stewardship Proposal (CRISP) team has now > published the first draft of an Internet numbers community proposal for > the future of the IANA stewardship. The draft is available here: > https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf > > Feedback from the global numbers community is now being sought. This > feedback can be sent to the global NRO IANA stewardship discussion list, > , or can be sent to the appropriate regional mailing > lists. The RIPE CRISP representatives will be closely following > discussions on the RIPE Cooperation Working Group mailing list, as well > as the global discussion. We would strongly encourage those RIPE > community members with an interest in this topic to contribute to the > global discussion on . > > The deadline for all feedback on this first draft is Monday 5 January > 2015. The CRISP team will then produce a further draft by 8 January, > which will be open for final feedback from the communities before > submission to the IANA Stewardship Transition Coordination Group (ICG) > by 15 January. > > The RIPE CRISP representatives circulated some draft text of an initial > proposal to the RIPE Cooperation WG mailing list on 28 November. We felt > that this draft captured the RIPE community input. A key addition in > this first CRISP draft is the formation of a community-based Review > Committee. This committee would produce an annual, non-binding report on > the performance of the IANA operator, a concept that evolved from the > Multistakeholder Oversight Numbers Council (MONC) that was originally > proposed by the LACNIC community. We feel that this Review Committee > addresses the concerns expressed by the LACNIC community, while not > creating unnecessary complex new structures. > > We look forward to hearing from the RIPE community on this important > process. > > Best regards, > Andrei Robachevsky, on behalf of the RIPE CRISP representatives > > > Important Links > ?? > Subscribe to the RIPE Cooperation Working Group mailing list: > http://www.ripe.net/mailman/listinfo/cooperation-wg/ > > Suscribe to the NRO IANA Transfer mailing list: > https://www.nro.net/mailman/listinfo/ianaxfer > > Information on the CRISP team and its work [includes members, charter, > teleconference minutes and audio]: > https://www.nro.net/crisp-team > > Public archive of the internal CRISP mailing list: > https://www.nro.net/pipermail/ianaxfer/ > > RIR community timeline for IANA stewardship discussion and links to > regional outputs: > https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs-engagement-in-iana-stewardship-transition-process > > RIPE NCC IANA stewardship information: > https://www.ripe.net/iana-stewardship-transition > > From nurani at netnod.se Mon Dec 29 13:48:02 2014 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 29 Dec 2014 13:48:02 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] CRISP 6th Teleconference Monday December 29th at 13:00 UTC + Agenda References: <549DB403.7050609@lacnic.net> Message-ID: <6779EEBE-3C21-407D-8DD2-37EA4191474C@netnod.se> Dear colleagues, Please find the details of today's CRISP teleconference below. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno on behalf of the RIPE CRISP team -- Nurani Nimpuno Head of Outreach & Communications, Netnod , http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden --------------------------------------------- Begin forwarded message: > From: Maria Gayo > Subject: [NRO-IANAXFER] CRISP 6th Teleconference Monday December 29th at 13:00 UTC + Agenda > Date: 26 december 2014 20:16:19 CET > To: ianaxfer at nro.net > Reply-To: mgayo at lacnic.net > > > > This is an invitation to join the 6th CRISP Teleconference and the agenda > > AGENDA > > TC 13:00 Mon 29th Dec 2014 > > 1.Agenda Review > > 2. Actions Review > a. Minutes > b. Publication of the edited version > c. Version control > d. List issues on NRO-IANAXFER > e. User friendly recordings > > > 3. Review Feedback and actions needed > a. Regional lists > b. Publishing of issues list > c. Addressing each issue > - IRP issues (domain & database) > - Review Committee > - other issues > > 4. Preparation for the 2nd draft > a. Volunteers: drafting text and communications > b. Any Coordination? IETF, ICANN CWG > > > 5. AOB > -------- > > > Regards > > Mar?a Gayo > (on behalf of the NRO Secretariat) > > > Webex details below > > ------------------------- > > > CRISP Team 6th Teleconference > Monday, December 29, 2014 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: > 704 502 792 > 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: 704 502 792 > 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. > -- > Mar?a Gayo > Coordinadora de Comunicaciones > Communications Coordinator > # 4206 > Casa de Internet de > Latinoam?rica y el Caribe > Rambla Rep. de M?xico 6125 > 11400 Montevideo-Uruguay > +598 2604 22 22 www.lacnic.net > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mail Attachment.png Type: image/png Size: 5594 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mail Attachment.png Type: image/png Size: 6213 bytes Desc: not available URL: From hph at oslo.net Wed Dec 31 16:18:24 2014 From: hph at oslo.net (Hans Petter Holen) Date: Wed, 31 Dec 2014 16:18:24 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] NRO-NC role in Review Committee In-Reply-To: <20141231130056.GI2079@apb-laptoy.apb.alt.za> References: <20141231130056.GI2079@apb-laptoy.apb.alt.za> Message-ID: <54A413C0.7080606@oslo.net> I would like to draw your attention to a particular item in the IANAXFER proposal: It would be appreciated if more community members found some time between the festivities to read and comment on the proposals. -------- Forwarded Message -------- Subject: [NRO-IANAXFER] NRO-NC role in Review Committee Date: Wed, 31 Dec 2014 15:00:56 +0200 From: Alan Barrett To: ianaxfer at nro.net There has been a suggestion that the work of the "Review Committee" proposed in the CRISP draft should be handled by the NRO-NC, or alternatively, that the chair of the NRO-NC should be co-opted to serve on the Review Committee. The CRISP Team believes that is would be wise to to keep the operational performance review process independent of the policy development process. Because the NRO-NC (or ASO-AC) has a role in global policy development, we think that the proposed Review Committee should be independent of the NRO-NC. The draft proposal says "The NRO Executive Council shall establish a Review Committee that will advise and assist the NRO Executive Council in its periodic review. Any such Review Committee should be a team composed of representatives from each RIR region ...". The CRISP Team has not discussed how many members the Review Committee might have, or what procedure the NRO EC might follow in choosing the members. --apb (Alan Barrett) _______________________________________________ ianaxfer mailing list ianaxfer at nro.net https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: