- cooperation-wg - mailman.ripe.net

Fwd: [NRO-IANAXFER] Draft Agenda Re: CRISP 17th Teleconference Wednesday April 8th 2015 20:00 UTC
by Nurani Nimpuno 08 Apr '15

08 Apr '15

FYI. Please find below the agenda for tonight's CRISP Team conference call. Kind regards, Nurani Nimpuno on behalf of the RIPE CRISP Team > Begin forwarded message: > > Date: 8 april 2015 12:00:20 CEST > From: Izumi Okutani <izumi(a)nic.ad.jp> > To: ianaxfer(a)nro.net > Subject: [NRO-IANAXFER] Draft Agenda Re: CRISP 17th Teleconference Wednesday April 8th 2015 20:00 UTC > > Colleagues, > > > Please see below the draft agenda for the coming CRISP Team call at > UTC20:00 8th Apr. > > As in all CRISP Team calls, it is open to anyone to join as an observer. > > > Regards, > Izumi > > ---- > 1. Agenda Review > > 2. Election of the Vice-Chair > (To be chaired by non-voting member) > > 3. Actions Review > a. Notes from the last meeting > b. FAQ, CRISP Slides > c. Message to ICG about CWG-Stewardship > d. Share future steps with the community > e. Confirm with NRO about RIR's official response > (on proposal, future steps) > > 4. Update > a. ICG > b. RIR communities (including ARIN35) > c. CWG-Stewardship (Names) Co-Chairs, IETF > d. GAO > > 6. Confirm Status & Next Steps > a. SLA, Review Committee > b. Community engagement, engagement with RIRs > c. IPR > > 7. Next Meeting > > 8. AOB > ---- > > On 2015/04/08 13:05, German Valdez wrote: >> Hi >> >> CRISP 17th Teleconference will take place on Wednesday April 8th 2015 at >> 20:00 UTC. Meeting as usual is open to observers >> >> Sorry for the short notice. >> >> regards >> >> German Valdez >> NRO >> >> >> *CRISP Team 17th Meeting* >> Wednesday, April 8, 2015 >> 8:00 pm | Greenwich Time (Reykjavik, GMT) | 2 hrs >> >> *Join WebEx meeting >> <https://ripencc.webex.com/ripencc/j.php?MTID=m9a21de42cf3b6330390d4f0824c18…> >> https://ripencc.webex.com/ripencc/j.php?MTID=m9a21de42cf3b6330390d4f0824c18… >> >> Meeting number: 700 520 727 >> 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: 700 520 727 >> Global call-in numbers >> <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=382164…> | >> Toll-free calling restrictions >> <http://www.webex.com/pdf/tollfree_restrictions.pdf> >> >> >> >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer(a)nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] CRISP 17th Teleconference Wednesday April 8th 2015 20:00 UTC
by Nurani Nimpuno 08 Apr '15

08 Apr '15

FYI. Nurani Nimpuno on behalf of the RIPE CRISP Team > Begin forwarded message: > > From: German Valdez <german(a)nro.net> > Date: 8 april 2015 06:05:30 CEST > To: <ianaxfer(a)nro.net> > Subject: [NRO-IANAXFER] CRISP 17th Teleconference Wednesday April 8th 2015 20:00 UTC > > Hi > > CRISP 17th Teleconference will take place on Wednesday April 8th 2015 at 20:00 UTC. Meeting as usual is open to observers > > Sorry for the short notice. > > regards > > German Valdez > NRO > > > CRISP Team 17th Meeting > Wednesday, April 8, 2015 > 8:00 pm | Greenwich Time (Reykjavik, GMT) | 2 hrs > > Join WebEx meeting <https://ripencc.webex.com/ripencc/j.php?MTID=m9a21de42cf3b6330390d4f0824c18…> > https://ripencc.webex.com/ripencc/j.php?MTID=m9a21de42cf3b6330390d4f0824c18… <https://ripencc.webex.com/ripencc/j.php?MTID=m9a21de42cf3b6330390d4f0824c18…> > Meeting number: 700 520 727 > 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: 700 520 727 > Global call-in numbers <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=382164…> | Toll-free calling restrictions <http://www.webex.com/pdf/tollfree_restrictions.pdf> > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

[anti-abuse-wg] Meeting with Law Enforcement Agencies (LEAs)
by Marco Hogewoning 23 Mar '15

23 Mar '15

On 20 Mar 2015, at 11:13, Sascha Luck [ml] <aawg(a)c4inet.net> wrote: > On Fri, Mar 20, 2015 at 04:31:53PM +0100, Marco Hogewoning wrote: > >> In response to feedback from the RIPE community, a more detailed >> report of this meeting has been prepared and is available here: >> https://www.ripe.net/ripe/meetings/lea-meetings/ripe-ncc-law-enforcement-me… > > Can I suggest that this be posted on ncc-announce also? I'm sure the > level of "partnership" with LEAs is of interest to the wider > membership beyond the subscribers of anti-abuse-wg. Dear Sascha, We have cooperated with NCA over the past several years to organise this specific annual event. We work together to shape the agenda, making sure it has relevance to the LEAs, and NCA also helps to make sure the relevant agencies receive an invitation. We have also taken your suggestion and shared this report with the membership via the ncc-announce mailing list. Regards Marco Hogewoning RIPE NCC

1 0

Meeting with Law Enforcement Agencies (LEAs)
by Marco Hogewoning 20 Mar '15

20 Mar '15

Dear Colleagues, We recently held our seventh meeting for Law Enforcement Agencies (LEAs), in partnership with the British National Crime Agency (NCA) and the other RIRs. Held on 12 March 2015, the purpose of this meeting was to discuss trends and developments that might impact the operations of LEAs and to gather the global law enforcement community’s perspective. A number of key points arose throughout the day: - The RIPE NCC highlighted that much of the information that LEAs required was publicly available and did not require a Dutch court order - Attendees agreed that the current multi-stakeholder model of Internet governance was preferable, but felt that LEAs and governments needed to engage more effectively within the existing structures - The relatively slow adoption of IPv6 and the spread of IP address sharing technologies such as Carrier Grade NAT will increasingly create issues around identifying specific end users - LEAs felt that cooperation with the private sector is extremely important and could improve greatly, but it was also understood that this came with additional costs In response to feedback from the RIPE community, a more detailed report of this meeting has been prepared and is available here: https://www.ripe.net/ripe/meetings/lea-meetings/ripe-ncc-law-enforcement-me… We would like to thank the NCA for its help in putting together this day and are looking forward to continue our engagement with the global law enforcement community. We are happy to answer any questions you may have about this meeting or our LEA engagement activities in general. Regards, Marco Hogewoning External Relations Officer - Technical Advisor RIPE NCC

4 3

Fwd: [CRISP-TEAM] Draft agenda Re: WebEx meeting invitation: CRISP Team 16th Teleconference Friday, March 13 2015
by Nurani Nimpuno 13 Mar '15

13 Mar '15

Please find below the agenda for the CRISP Call today. (Apologies for the lateness of this mail.) Kind regards, Nurani on behalf of the RIPE CRISP team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [CRISP-TEAM] Draft agenda Re: WebEx meeting invitation: CRISP Team 16th Teleconference Friday, March 13 2015 > Date: 11 mars 2015 04:51:42 CET > To: German Valdez <german(a)nro.net>, "crisp(a)nro.net" <crisp(a)nro.net> > > CRISP Team, > > > Please see below the draft agenda for the coming CRISP Team meeting this > Friday, 13th March. > > I welcome your feedback on anything else you'd like to discuss. > > Thanks German for the inivitation for the meeting to the CRISP Team > mailing list. > > Would you help us send the invitation to the global IANAXFER list as > well? I'll follow up about the agenda. > > ---- > 1. Agenda Review > > 2. Actions Review > a. Agenda for 15th Meeting > b. Response to the ICG on incompatibilities > c. Questions from the ICG > > 3. Key updates > a. Update from ICG discussions (if any) > b. Discussions at APNIC39 Conference > > 4. Next steps: Preparing Implementation > a. SLA and Review Committee > b. the role of the CRISP Team > > 5. Handling of comments for the proposal > a. From the ICG > b. Informal feedback from others > c. FAQ > > 6. Other operational communities > a. Names discussions > b. Handling of IPR > > 7. Future Call > a. Needs basis/pre-plan monthly > > 6. AOB > ---- > > > Thanks, > Izumi > > > On 2015/03/10 22:37, German Valdez wrote: >>> >>> *CRISP Team 16th Teleconference* >>> Friday, March 13, 2015 >>> 1:00 pm | Greenwich Time (Reykjavik, GMT) | 2 hrs >>> >>> *Join WebEx meeting* >>> <https://ripencc.webex.com/ripencc/j.php?MTID=m6e865d620513c70c8eab435c0e4dc…> >>> >>> Meeting number: 701 646 062 >>> 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: 701 646 062 >>> Global call-in numbers >>> <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=376300…> | >>> Toll-free calling restrictions >>> <http://www.webex.com/pdf/tollfree_restrictions.pdf> >>> >>> Add this meeting >>> <https://ripencc.webex.com/ripencc/j.php?MTID=mcb35d3ee6ba599275ee56bf933e99…>to >>> your calendar. >>> >>> Can't join the meeting?Contact support. <https://ripencc.webex.com/ripencc/mc> >>> >>> 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. >>>

1 0

Fwd: [CRISP-TEAM] WebEx meeting invitation: CRISP Team 16th Teleconference Friday, March 13 2015
by Nurani Nimpuno 10 Mar '15

10 Mar '15

FYI. The CRISP team will hold its 16th teleconference this Friday 14:00 CET. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP Team Begin forwarded message: > From: German Valdez <german(a)nro.net> > Subject: [CRISP-TEAM] WebEx meeting invitation: CRISP Team 16th Teleconference Friday, March 13 2015 > Date: 10 mars 2015 14:37:58 CET > To: <crisp(a)nro.net> > > > Dear Team > > Please find below the webex information for this Friday Teleconference. > > Please let me know if I can forward the invitation in the global list. > > Thanks > > German > > >> Begin forwarded message: >> >> Date: 10 March 2015 11:24:57 pm AEST >> From: German Valdez <messenger(a)webex.com> >> Reply-To: <german(a)nro.net> >> To: <german(a)nro.net> >> Subject: (Forward to others) WebEx meeting invitation: CRISP Team 16th Teleconference >> >> You can forward this invitation to others. >> Hello, >> German Valdez invites you to join this WebEx meeting. >> >> CRISP Team 16th Teleconference >> Friday, March 13, 2015 >> 1:00 pm | Greenwich Time (Reykjavik, GMT) | 2 hrs >> >> Join WebEx meeting >> Meeting number: 701 646 062 >> 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: 701 646 062 >> 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. > > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

IANA Stewardship and ICANN Accountability Dominate ICANN 52 Discussions
by Chris Buckridge 23 Feb '15

23 Feb '15

Dear colleagues, The 52nd ICANN meeting was held in Singapore from 8-12 February, attracting around 1800 participants on-site, as well as numerous remote participants. The issues surrounding the transition of IANA stewardship and ICANN accountability were again at the top of the agenda, and RIPE community members and RIPE NCC staff contributed to these discussions. Discussion of the CRISP Team Proposal As discussed in the RIPE Cooperation Working Group and elsewhere, the Internet numbers community submitted its proposal for future stewardship of the number-related IANA functions to the IANA Stewardship Transition Coordination Group. This proposal, and the counterpart proposal regarding the IANA protocol parameter registries developed within the Internet Engineering Task Force (IETF), were discussed in various ICANN 52 sessions, with representatives of the CRISP team, including Izumi Okutani (CRISP team Chair), Alan Barrett (CRISP team Vice-chair) and Nurani Nimpuno (RIPE CRISP team representative) contributing to discussions and ensuring all aspects of the numbers community IANA stewardship proposal were correctly understood. The meeting provided opportunities for the RIR senior staff, CRISP team members, members of the ICG, ICANN staff, NTIA staff and representatives of the other IANA affected communities to discuss implementation and operational questions arising from the community proposals already delivered. It also provided an opportunity for initial discussions between legal personnel from the RIRs and ICANN regarding development of the Service Level Agreement covering operation of the IANA Numbering Services (as defined in the numbers community IANA proposal). Links to all of the sessions dealing with IANA stewardship transition are available at: https://ripe.net/iana-discussions ICANN Accountability The Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) met numerous times during the week to continue its work identifying and developing solutions to accountability concerns, with a particular focus on those issues which the group identifies as critical ahead of the IANA stewardship transition. The link between these accountability solutions and a successful transition of the IANA stewardship was again emphasised by participants including Lawrence Strickling, the Assistant Secretary for Communications and Information and Administrator with the National Telecommunications and Information Administration (NTIA). RIPE NCC’s Athina Fragkouli is participating in the CCWG-Accountability as an ASO representative (alongside Izumi Okutani, Fiona Asonga and Jorge Villa), and will seek feedback from the RIPE community and provide updates as the group’s work progresses. Progress on the Naming Community Proposal Discussions during the week also focused heavily on the proposal currently under development by the Cross-Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (commonly referred to as the CWG-Stewardship). The CWG-Stewardship’s recent announcement regarding a revised timeline that would see its proposal delivered to the ICG in June 2015 was of particular interest. There were also discussions on the substantive concerns about whether ICANN itself or a new, external contracting company would hold the stewardship of the names-related IANA functions. The Chairs of the CWG-Stewardship have released a statement summarising developments coming out of ICANN 52: https://www.icann.org/news/announcement-4-2015-02-12-en In addition, the ICANN Board issued a statement clarifying that it will promptly forward the proposals received from the ICG and the CCWG-Accountability to the NTIA, without modification: https://www.icann.org/news/announcement-3-2015-02-12-en Best regards, Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

Fwd: [NRO-IANAXFER] The CRISP Team Response to "Process concern regarding the RIR proposal development process "
by Nurani Nimpuno 07 Feb '15

07 Feb '15

Dear colleagues, Please find below the email sent by the CRISP chair Izumi Okutani to the global ianaxfer(a)nro.net mailing list. The mail addresses concerns raised by some members of the list after the submission of the CRISP proposal to the IANA Stewardship Transition Coordination Group (ICG). We very much welcome your input in this discussion, as some of the points raised concerns the amount of community support this proposal holds. Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Fwd: The CRISP Team Response to "Process concern regarding the RIR proposal development process " > Date: 4 februari 2015 20:54:59 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear all, > > > This is the CRISP Team Response to "Process concern regarding the RIR > proposal development process ", which is another post to icg-forum. > > Again, I welcome your comments and feedback about our reponse which is > likely to be a reference to the ICG. > > Explicit expressing support would be extremely helpful as well. > > > > Regards, > Izumi > > > -------- Forwarded Message -------- > Subject: The CRISP Team Response to "Process concern regarding the RIR > proposal development process " > Date: Thu, 05 Feb 2015 04:43:25 +0900 > From: Izumi Okutani <izumi(a)nic.ad.jp> > To: icg-forum(a)icann.org > CC: crisp(a)nro.net <crisp(a)nro.net> > > Dear ICG members, > > > On 20 January 2015 Richard Hill wrote to the icg-forum list with a > number of concerns about the CRISP team process. > > http://forum.icann.org/lists/icg-forum/msg00020.html > > The concerns expressed by Mr Hill were considered in depth during the > CRISP team proposal development process and had been discussed on the > ianaxfer mailing list with Mr Hill as well as other community members. > > The positions taken by the CRISP team was based on the consensus > position of the community. > > > Richard Hill wrote: > >> Certain legal questions were raised in discussions on the CRISP > mailing list >> (NRO IANAXFER), in particular regarding jurisdiction and dispute > resolution. >> The CRISP team apparently did not include anybody who had appropriate > legal >> expertise and it chose not to request outside legal expertise, see: >> https://www.nro.net/pipermail/ianaxfer/2015-January/000322.html > > Mr Hill’s objections to the position adopted by the CRISP team were well > documented in his emails to the ianaxfer mailing list, and were > discussed at length on the CRISP teleconferences (notes and audio > archives of these calls are available at https://nro.net/crisp-team) > Additionally, they were included in the CRISP team’s matrix of community > comments and concerns posted at: > https://www.nro.net/crisp-iana-xfer-summary-discussion-08012015 > > The CRISP team’s final position is effectively summarised in the text of > our response to the ICG RFP: > > “The RIRs, as the contractual party of this agreement, will draft the > specific language of this agreement. During the drafting process, the > RIRs are expected to consult their respective RIR communities, and that > the drafting process will be guided by the principles listed below.” > [Response to the ICG RFP on the IANA from the Internet Number Community, > p11] > > The RFP response then lists 11 IANA Service Level Agreement Principles. > This was based on taking into account of feedback on the ianaxfer > mailing list, to bring the proposal back to describing high level > principles. > > The CRISP team’s position took into account the concerns raised by Mr > Hill, and addressed some points he has raised, such as describing in the > proposal that RIRs are expected to consult their respective RIR > communities, as quoted earlier. > > The CRISP Team was also informed by other feedback received via the > ianaxfer mailing list, particularly those mails which explicitly > supported the approach of delegating contract authorship to the RIR > legal teams. Posts by Hans Petter Holen (7 Jan,10 Jan) Seun Ojedeji (7 > Jan) Gerard Ross (11 January), Jim Reid (12 January), Andrew Dul (12 > January) and Dmitry Burkov (13 January) specifically endorsed this view. > All of these mails can be read at: > https://www.nro.net/pipermail/ianaxfer/2015-January/date.html > > A further concern noted by Mr Hill: >> That is, how can NTIA be expected to approve a proposal when important >> details are left open and have not been reviewed or endorsed by the global >> multi-stakeholder community? > > The CRISP team has crafted a proposal that reflects the value that the > community places on the number-related IANA functions. This is reflected > in the proposal to safeguard the RIR communities’ stewardship over these > functions via a contractual relationship. It is the responsibility of > the parties to a contract to negotiate a contract. The CRISP team > believes that by directing the RIRs to consult with their communities > and by laying down the principles mentioned above, we have established a > framework within which the RIR legal staff can effectively negotiate in > the best interests of the community. > > Finally, Mr Hill has expressed that "there was limited input and the > outcome was largely influenced by the CRISP team and the RIR staff”. As > noted above, there were numerous posts to the ianaxfer mailing list, > many of which touched specifically on the issues discussed by Mr Hill. > From 17 October 2014 to 29 January 2015 there were 372 mails to the > ianaxfer list and 134 subscribers - information on the list is available > at: https://www.nro.net/mailman/listinfo/ianaxfer > > I hope that this is a useful explanation of the CRISP team’s position in > regard to the issues raised by Mr Hill. I am of course happy to discuss > any of these issues in greater depth if this would be helpful. > > > Yours sincerely, > > Izumi Okutani > Chair, the CRISP Team > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

5 4

Fwd: [NRO-IANAXFER] IANA stewardship transition session at ICANN52 Singapore (2/8 & 2/9)
by Nurani Nimpuno 06 Feb '15

06 Feb '15

FYI. Nurani Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Date: 6 februari 2015 14:00:55 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > Subject: [NRO-IANAXFER] IANA stewardship transition session at ICANN52 Singapore (2/8 & 2/9) > > Colleaugues, > > > There will be two sessions at ICANN32 Singapore Meeting that cover the > IANA stewardship transition. > > You can join both sessions remotely. > > The seond session will be sharing overview of proposals/situation of all > three operational communities of the IANA function, and have discussions > with the participants. There will be presentation on the CRISP Team's > work for the number resources. > > > * Sunday, 8 February 2015 17:30 to 19:00 SGT > - IANA Stewardship Transition/Enhancing ICANN Accountability > Information Session > - > http://singapore52.icann.org/en/schedule/sun-iana-stewardship-accountability > > * Monday, 9 February 2015 10:15 to 13:00 SGT > - Responses to the ICG RFP Regarding the IANA Stewardship Transition > - http://singapore52.icann.org/en/schedule?date=2015-02-09 > > > Regards, > Izumi > > > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] The CRISP Team Response to "CRISP - Process Concerns"
by Nurani Nimpuno 06 Feb '15

06 Feb '15

Dear colleagues, Please find below another email sent by the CRISP chair Izumi Okutani to the global ianaxfer(a)nro.net mailing list. As stated in my previous mail, we very much welcome the RIPE community's continued input in this discussion on the ianaxfer(a)nro.net mailing list. Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Fwd: The CRISP Team Response to "CRISP - Process Concerns" > Date: 4 februari 2015 20:53:49 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear all, > > > I would like to share the CRISP Team Response to "CRISP - Process > Concerns", which has been posted to icg-forum. > > I welcome your comments and feedback about our reponse which is likely > to be a reference to the ICG. > > Explicit expressing support would be extremely helpful as well. > > > > Regards, > Izumi > > > -------- Forwarded Message -------- > Subject: The CRISP Team Response to "CRISP - Process Concerns" > Date: Thu, 05 Feb 2015 04:37:01 +0900 > From: Izumi Okutani <izumi(a)nic.ad.jp> > To: icg-forum(a)icann.org > > Dear ICG members, > > > On 22 January 2015 Guru Acharya wrote to the icg-forum list with a > number of concerns about the CRISP team process. > > http://forum.icann.org/lists/icg-forum/msg00024.html > > The CRISP Team was not able to confirm concrete evidence/facts on these > concerns, as explained below. > > We also note that while present as an observer on a number of CRISP > teleconferences, we did not observe Guru Archaya raising any of these > concerns on ianaxfer(a)nro.net mailing list or on any of the regional > community lists on which the CRISP process was being discussed. > > > Guru Acharya writes: > >> I would like to highlight the following concerns about the process > adopted >> by CRISP, which disqualify it from satisfying the criteria of following a >> bottom-up multi-stakeholder process as mandated by the NTIA. >> >> 1) Top-down composition and selection of CRISP team: The CRISP team was a >> closed group selected by the RIR executive committee by way of an > interview >> process. Interested participants were excluded from the working group if >> they did not successfully qualify for the interviews conducted by the RIR >> executive committee. The selection criteria for the candidates was > not made >> public by the RIR executive committee. This is important given that >> non-CRISP participants were excluded from the decision-making process. > > > Before setting up the CRISP Team, RIRs published the process for > producing a single proposal from the global IP addressing community to > the NTIA, and there was an opportunity for discussions on the public > <ianaxfer(a)nro.net> mailing list as below: > > On 16 October the five RIRs published a process for producing a single > proposal from the global IP addressing community to the NTIA. > https://www.nro.net/news/iana-stewardship-consolidated-rir-iana-stewardship… > > According to this process the CRISP team would consist of 15 members, > two appointees from each RIR region who are not RIR staff, and one RIR > staff member from each region, who shall assist with the submission > development effort. Each RIR was to appoint their CRISP team members by > a method of its own choosing by 15 November 2014. There was some > discussion on the public <ianaxfer(a)nro.net> mailing list on 21 October > about standardising a CRISP team selection process across all five RIR > regions, but no broader community support was expressed for this change. > See: > https://www.nro.net/pipermail/ianaxfer/2014-October/000016.html > > Following this announcement each of the five RIRs announced an open call > for participants, to which any one could express their interest, as well > as the process according to which the selection of the CRISP members > would be conducted. The process and relevant announcements of each RIR > are described in the Internet Number Community Response to the ICG RFP > (sections VI.B.1-VI.B.5 on "Community Process"). > > In most cases the RIR executive committees made the final selection of > CRISP representatives from community volunteers. At no point in the > process were any explicit objections raised to any of the CRISP team > members, nor were any appeals made by volunteers not selected to join > the CRISP team. > >> >> 2) Top-down decision-making by the CRISP team: While the general > public was >> invited to provide comments for the draft proposals prepared by > CRISP, they >> were excluded from the decision-making process. Commenters were merely >> informed that their input had either been accepted or rejected by the > CRISP >> team after due consideration. Notably, non-CRISP participants were not >> allowed to contribute to CRISP's tele-conferences or CRISP's internal >> mailing list, where the actual decision-making took place. Mere >> consultation of the general public without their involvement in the >> decision-making process does not constitute a bottom-up multi-stakeholder >> process. > > > Each of the RIR communities had conducted discussions on the IANA > stewardship transition for the IANA Numbering Services and the role of > the CRISP Team is to consolidate it as a single global proposal. > > https://www.nro.net/nro-and-internet-governance/iana-oversight/consolidated… > > The proposal to establish a CRISP team was distributed to all of the RIR > communities and the <ianaxfer(a)nro.net> mailing list established on 16 > October 2015. The first CRISP team teleconference was held on 9 December > 2015. This provided the community with nearly two months during which > they could comment on or object to any elements of the proposal to set > up the CRISP team (as noted above, there was some discussion around 21 > October relating to CRISP team selection processes, but there was not > community support for changing the proposed process). > > The CRISP team members agreed with the arrangements laid out in the > proposal (while developing some additional mechanisms, including the > internal CRISP mailing list and a working definition of quorum for the > group). CRISP team members also understood a key part of their role to > be facilitating input from the regional communities, and this was > evident throughout the process - teleconference notes from the third > teleconference onwards record various CRISP team members conveying input > from their regional mailing lists. > > Invitations to join the CRISP Team Teleconferences as observers were > sent to <ianaxfer(a)nro.net> mailing list, which were forwarded to mailing > lists of RIR regions by the CRISP Team members. > > Subscription to <ianaxfer(a)nro.net> mailing list was open to anyone, and > there was no restrictions on posting comments to the list, including > making comments about the CRISP Team discussions at any of the CRISP > Team Teleconferences. > > A concrete record of all the concerns raised by the community on various > mailing lists was prepared by the CRISP team and made available at: > https://www.nro.net/wp-content/uploads/NRODiscussionList_20150116.pdf > > This spreadsheet indicated the issue, the initial mail in which the > issue was raised, the CRISP team's discussion of the issue and the > current CRISP team position. This clearly demonstrates that the process > of community participation facilitated by the CRISP team worked smoothly > to address a wide range of community input throughout the process. > >> >> 3) Lack of information and transparency: The CRISP team had two mailing >> lists. The mailing list used internally by the CRISP team was a closed >> mailing list that was not publicly archived till after the proposal was >> finalised. This resulted in community evaluation of the process and >> proposal in the absence of requisite information about the reasons > for any >> decisions. > > As noted in the initial CRISP team proposal and charter, "The CRISP team > shall also work through a public mailing list and the archive of such > mailing list will be publicly available. The name of the mailing list > will be <ianaxfer(a)nro.net>. > > At its initial teleconference, CRISP team members suggested that a > separate mailing list for use by CRISP team members only would be useful > in the interest of efficiency and to allow quick editing iterations on > the proposed response. > https://www.nro.net/wp-content/uploads/CRISP-December-9-meeting-DRAFT-NOTES… > > While there was general agreement, concerns about transparency were also > noted, resulting in a commitment to publish archives of the internal > list at the time of publishing the first draft (19 December 2014). The > archive was publicly available from this point and some CRISP team > members shared a link to the archive with their communities directly. A > direct link to this mailing list archive was posted to the ianaxfer > mailing list and on the NRO CRISP webpage after 8 January 2015 due to an > oversight, while the archives were publicly made available when the > first draft of the proposal was published on 19 December. > > The archive of the internal mailing list is available at: > https://www.nro.net/pipermail/crisp/ > > It is possible to confirm from our announcements that links to the > archives of the CRISP team mailing list was intended to be shared from > publication of the first draft proposal: > > "Details of all the CRISP team's work to date, including recordings, > minutes and agendas of all CRISP teleconferences and a public archive > of the internal CRISP team mailing list, are available at: > https://nro.net/crisp-team" > > https://www.nro.net/news/first-draft-proposal-of-the-internet-number-commun… > > https://www.nro.net/news/internet-number-community-iana-stewardship-proposa… > > >> >> 4) Refusal to deal with essential aspects of the proposal: The CRISP team >> refused to deal with essential aspects of proposal such as the contract >> renewal process, contract duration, jurisdiction, arbitration process, >> review process, high level details of the contract, intellectual property >> rights, charter of the review team and service levels. The CRISP team > cited >> these essential aspects as outside the scope of the CRISP mandate. If the >> CRISP mandate is indeed so limited, then its incomplete proposal > should be >> returned to the RIR community with the suggestion of expanding the > mandate >> of the CRISP team. Note that the charter of the CRISP team, which was >> prepared by the NRO EC in a top-down manner, does not suggest that such >> essential aspects should be excluded from the proposal. This limited >> interpretation of the agenda and issues by the CRISP team is against the >> ethos of a bottom-up multi-stakeholder process. > > As noted above, a concrete record of all the concerns raised by the > community on various mailing lists was prepared by the CRISP team and > made available at: > https://www.nro.net/crisp-iana-xfer-summary-discussion-08012015 > > This spreadsheet, the records and notes from CRISP teleconferences and > the archived mails on both the internal and public mailing lists > demonstrate that the CRISP team closely considered all issues, concerns > or suggestions raised by the community via ianaxfer(a)nro.net or the > regional discussion lists. Where specific suggestions were not reflected > in the proposal, detailed justification was provided to the community > via the ianaxfer mailing list. > > While the CRISP team did note certain constraints on its remit, as it > understood that remit, the issues noted by Guru Acharya were addressed > specifically in the following mails to the public <ianaxfer(a)nro.net> > mailing list: > > Contract details in general, including renewal process, duration: > https://www.nro.net/pipermail/ianaxfer/2015-January/000213.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000135.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000143.html > > Jurisdiction: > https://www.nro.net/pipermail/ianaxfer/2015-January/000331.html > > Arbitration process: > https://www.nro.net/pipermail/ianaxfer/2015-January/000331.html > > Review process: > https://www.nro.net/pipermail/ianaxfer/2014-December/000134.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000172.html > > Intellectual property rights: > https://www.nro.net/pipermail/ianaxfer/2014-December/000145.html > https://www.nro.net/pipermail/ianaxfer/2014-December/000127.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000342.html > https://www.nro.net/pipermail/ianaxfer/2015-January/000173.html > > Charter of the review team: > https://www.nro.net/pipermail/ianaxfer/2015-January/000320.html > > While developing the proposal, the CRISP team was conscious about its > remit and responsibility. In the process of addressing issues and the > elements of the proposal the team felt that it was important to identify > the critical components and implementation requirements, rather than > work out the actual implementation details. Our position was that the > latter should be developed by qualified RIR legal teams following the > best practices in this field. As stated in the response to the ICG "The > RIRs, as the contractual party of this agreement, will draft the > specific language of this agreement. During the drafting process, the > RIRs are expected to consult their respective RIR communities, and that > the drafting process will be guided by the principles listed below." > [Response to the ICG RFP on the IANA from the Internet Number Community, > p11] > > We believe that the proposal submitted to the ICG meets the expectations > of the numbers community, while not extending into areas beyond the > authority or expertise of the CRISP team. > > I hope that this effectively addresses the issues raised in this email, > and I would be happy to expand further on any issues you feel could > benefit from more explanation. > > > Yours sincerely, > Izumi Okutani > Chair, the CRISP Team > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

3 2

Fwd: [NRO-IANAXFER] Webex Invitation CRISP Team Teleconference Thursday February 5th 2015 at 13:00 UTC
by Nurani Nimpuno 05 Feb '15

05 Feb '15

FYI. (Apologies for the lateness of this mail.) Begin forwarded message: > From: German Valdez <german(a)nro.net> > Subject: [NRO-IANAXFER] Webex Invitation CRISP Team Teleconference Thursday February 5th 2015 at 13:00 UTC > Date: 4 februari 2015 16:38:13 CET > To: <ianaxfer(a)nro.net> > > Hi > > Please find below webex information for CRISP Team Teleconference to be held on Thursday February 5th 2015 at 13:00 UTC > > Regards > > German Valdez > NRO > > > > > CRISP Team 15th Meeting > Thursday, February 5, 2015 > 1:00 pm | UTC | 1 hr > > Join WebEx meeting > Meeting number: 704 052 432 > 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: 704 052 432 > Global call-in numbers | Toll-free calling restrictions > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Contribute to the EuroDIG 2015 Planning Meeting
by Chris Buckridge 26 Jan '15

26 Jan '15

Dear colleagues, On Tuesday, 27 January (tomorrow), EuroDIG, the European Dialogue on Internet Governance, will hold an open planning meeting in Sofia, Bulgaria, for the annual EuroDIG meeting, which will also be held in Sofia in June: www.eurodig.org/get-involved/planning-meeting/ The planning meeting is open to the public, with remote participation options available. Participants will consider themes and topics for inclusion on the EuroDIG agenda, based on the submissions received during last year’s open call. This is an important opportunity to help shape the European Internet governance discussion and ensure that issues of importance to the RIPE community are included on the agenda. A few thoughts on how to participate: - As noted above, there will be remote participation available, allowing you to follow all discussions in real time via Webex: https://intgovforum.webex.com/intgovforum/j.php?MTID=m0928b71d1e86068d0d651… - RIPE NCC staff and other participants will be tweeting throughout the day, noting any important developments or topics - you can follow via the #EuroDIG hashtag, and RIPE NCC staff will be monitoring tweets with this hashtag, so you can contribute to the discussion in this way. - A report on outcomes from this meeting will be sent to the Cooperation Working Group mailing list, and further discussion here is welcome. The RIPE NCC is an institutional partner of EuroDIG and is pleased to be contributing to the planning and coordination of the upcoming EuroDIG 2015 event. Best regards, Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

ICG Update on Circle ID
by Chris Buckridge 21 Jan '15

21 Jan '15

Hi all, After the flurry of recent activity on this list regarding the CRISP team’s work on a numbers community proposal to the IANA Stewardship Transition Coordination Group (ICG), things have been comparatively quiet over the last few days. But the IANA stewardship transition process is far from over - ICG Chair, Alissa Cooper, has posted an article discussing the global process so far and the next steps for the ICG. It makes for a good summary of events so far and preview of what to expect over the coming months: http://www.circleid.com/posts/20150120_iana_transition_planning_proceeding_… In addition, the RIPE NCC has posted an short video on the RIR community and CRISP processes to date and a high-level preview of next steps: https://www.youtube.com/watch?v=ihB4ZyDvFwM Hopefully both of these will help inform the RIPE community’s continuing participation in the IANA stewardship transition process. Best regards, Chris — Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

Fwd: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community
by Nurani Nimpuno 16 Jan '15

16 Jan '15

Dear Colleagues, Please find below the Internet numbers community's response to the RFP issued by the IANA Stewardship Coordination Group (ICG), submitted by the Consolidated RIR IANA Stewardship Proposal (CRISP) Team. As the CRISP Chair Izumi Okutani notes, we have observed several explicit expressions of support for our proposal, and we believe that there was consensus from the Internet numbers community on the CRISP proposal. We would like to thank everyone in the RIPE community who has contributed with input and guidance in this process. Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE team (Paul Rendek, Andrei Robachevsky & Nurani Nimpuno) Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community > Date: 16 januari 2015 00:26:26 CET > To: icg-proposal(a)icann.org > Cc: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear Alissa Cooper and the ICG members, > > > On behalf of the Consolidated RIR IANA Stewardship Proposal Team (CRISP > Team), I respectfully submit the attached response to the IANA > Stewardship Transition Coordination Group Request for Proposals on the > IANA from the Internet Number Community. > > > Best Regards, > Izumi Okutani > Chair, CRISP Team > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

2 1

Fwd: [CRISP-TEAM] Draft Agenda for 14th CRISP TeamTeleconference
by Nurani Nimpuno 15 Jan '15

15 Jan '15

FYI Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [CRISP-TEAM] Draft Agenda for 14th CRISP TeamTeleconference > Date: 15 januari 2015 13:46:53 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net>, "crisp(a)nro.net" <crisp(a)nro.net> > > Dear Colleagues, > > Please find below the draft agenda for coming 14th CRISP Team > Teleconference at UTC13:00 15th Jan. > > CRISP Team 14th Teleconference > Thursday January 15th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db… > <https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db…> > > As in all CRISP Team calls, it is open to observers. > > --- > 1. Agenda Review > > 2. Actions Reivew > a. Minutes > b. Header of the proposal > > 3, Summary of the comments status > > 4. Outstanding issues > > 5. Definitions > > 6. Announcement > > 7. Cover Letter > > 8. Issues list > > 9. Next Steps > a. Reconfirm the pen > b. Reconfirm Timeline > > 10. AOB > --- > > > > > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Draf Agenda for CRISP Team 13th Teleconference Re: CRISP Team Next Week Teleconferences
by Nurani Nimpuno 14 Jan '15

14 Jan '15

FYI Nurani Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Draf Agenda for CRISP Team 13th Teleconference Re: CRISP Team Next Week Teleconferences > Date: 14 januari 2015 12:06:39 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear Colleagues, > > Please find below the draft agenda for coming 13th CRISP Team > Teleconference at UTC13:00 14th Jan. > > As in all CRISP Team calls, it is open to observers. > >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> > https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6… > <https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6…> > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. NRO CRISP Website improvement > > 3. Confirm texts to be incorporated > a. Suggested edits > b. Consulting the community about SLA > c. Review Committee selection > d. Contract Fee > e. Move description of RIRs, NRO, NRO EC > f. reconfirm numbering scheme > g. II.B.3.i. NTIA > h. IIIA3 SLA > i. I.D. > j. VI. description of APNIC region process > > 4. What to revert back > > 5.Agree on a common term > a. Internet number community > b. the IANA Number Services Operator > c. singular/plural > > 6. Confirm Timeline > > 7. Next Meeting > > 8. AOB > > --- > > Best Regards, > Izumi Okutani > The CRISP Team > > > On 2015/01/10 0:18, German Valdez wrote: >> Hi >> >> CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC >> >> Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. >> >> CRISP Team 11th Teleconference >> Monday January 12th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc… <https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc…> >> >> CRISP Team 12th Teleconference >> Tuesday January 13th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52… <https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52…> >> >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6… <https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6…> >> >> CRISP Team 14th Teleconference >> Thursday January 15th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db… <https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db…> >> >> Kind regards >> >> German Valdez >> NRO >> >> >> >> >> >> _______________________________________________ >> CRISP mailing list >> CRISP(a)nro.net >> https://www.nro.net/mailman/listinfo/crisp >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] Draft agenda for 12th CRISP Team Telelconference Re: CRISP Team Next Week Teleconferences
by Nurani Nimpuno 13 Jan '15

13 Jan '15

fyi Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Draft agenda for 12th CRISP Team Telelconference Re: CRISP Team Next Week Teleconferences > Date: 13 januari 2015 13:08:24 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > Please find below the draft agenda for coming 12th CRISP Team > Teleconference at UTC13:00 13th Jan. > > As in all CRISP Team calls, it is open to observers. > > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. NRO CRISP Website improvement > c. HTML and text versions > d. Metadata in docx file > > 3. Confirm discussions status > a. each RIR region > b. global list > > 4. Editorial suggestions > a. Confirm status > b. Paul Wilson's suggested changes > c. Timeline to work > > 5. Confirm status of editorial suggestions > a. Community review SLA > b. Review Committee > c. Contract Fee > > 6. CRISP Team positions per issue > a. Continue discussions in RIR meetings > b. Consistence in IPR description > IIIA2 and IIIA3iii > c. Comment from Pindar Wong > d. Further input about cost > > 7. Timeline and how we work for the final submission > a. Schedule > b. Who does what > > 8. Next Meeting > > 9. AOB > --- > > > On 2015/01/10 0:18, German Valdez wrote: >> Hi >> >> CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC >> >> Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. >> >> CRISP Team 11th Teleconference >> Monday January 12th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc… <https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc…> >> >> CRISP Team 12th Teleconference >> Tuesday January 13th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52… <https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52…> >> >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6… <https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6…> >> >> CRISP Team 14th Teleconference >> Thursday January 15th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db… <https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db…> >> >> Kind regards >> >> German Valdez >> NRO >> >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer(a)nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Second draft of the Internet numbers community proposal on the transition of the IANA stewardship.
by Maria Häll 13 Jan '15

13 Jan '15

Dear all The Consolidated RIR IANA Stewardship Proposal (CRISP) team have published the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. I strongly support this draft proposal, as an important step to strengthen the Internet numbers community’s position further on in this process. Thx to the CRISP team for all your work! _________________________________ Best regards, Maria Häll (speaking only as myself) Co-chair Coop WG / CEO SUNET - Swedish University Network

2 1

Fwd: [NRO-IANAXFER] Final call for comments closed Re: Internet Number Community IANA Stewardship Proposal: Final Call for Comments
by Nurani Nimpuno 13 Jan '15

13 Jan '15

Dear Colleagues, Thank you all for your valuable input on the CRISP draft proposal. Please see the mail below from the CRISP Chair Izumi Okutani about the next steps in incorporating the input received and developing the final version to be submitted to the ICG. Kind regards, Nurani On behalf of the CRISP RIPE team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Final call for comments closed Re: Internet Number Community IANA Stewardship Proposal: Final Call for Comments > Date: 13 januari 2015 03:32:49 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear Colleagues, > > > Thank you for all the inputs you have given to the second draft of our > proposal. > > > The CRISP Team now has moved into developing our proposal to be > submitted to the ICG on 15th Jan based on the comments received before > 12 Jan 2015, 23:59 UTC. > > > > Best Regards, > Izumi Okutani > The CRISP Team > > On 2015/01/13 2:57, Izumi Okutani wrote: >> Dear Colleagues, >> >> >> This is a reminder that the CRISP Team will close to receive all >> comments for the second draft of our proposal as of : >> >>> Second draft comments close : 12 Jan 2015, 23:59 UTC >> >> >> Please send in all your comments before the above time, for the CRISP >> Team to consider your input in developing the final proopsal to be >> submitted to the ICG. >> >> >> Thank you to those who have expressed and shared your comments on this >> list already. >> >> >> Best Regards, >> Izumi Okutani >> The CRISP Team >> >> >> On 2015/01/09 1:21, Izumi Okutani wrote: >>> Dear colleagues, >>> >>> >>> Please find the second draft of the Internet numbers community's >>> response to the Request For Proposals issued by the IANA Stewardship >>> Coordination Group (ICG). >>> >>> This draft has been prepared by the Consolidated RIR IANA Stewardship >>> Proposal (CRISP) Team, with considerations of feedback received from the >>> global community on <ianaxfer(a)nro.net> mailing list. >>> >>> We have incorporated the following key points in the second draft: >>> >>> - Additional description on contract details, review committee and >>> intellectual property rights >>> - Description revised on Section V. NITA Requirements and VI. >>> Community Process for more clarity >>> - No changes are made to key elements of the proposal >>> >>> The CRISP Team have considered all comments expressed on >>> <ianaxfer(a)nro.net> mailing list before the deadline of 5th Jan 2015, and >>> would now like to make the final call for comments from the global >>> community on the draft proposal, before submitting to the ICG. >>> >>> Second Draft proposal: >>> ------------------------ >>> Clean Version : >>> <http://www.nro.net/crisp-proposal-second-draft> >>> >>> Redline Version: >>> <http:/www.nro.net/crisp-proposal-second-draft-change-control> >>> >>> The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC >>> Feedback should be sent to : <ianaxfer(a)nro.net> mailing list >>> >>> Community Inputs Considered by the CRISP Team: >>> ------------------------------------------ >>> You can check the status of the issues raised by the community and >>> proposed the CRISP Team positions at: >>> >>> <http://www.nro.net/crisp-iana-xfer-summary-discussion-08012015> >>> >>> Key dates: >>> ----------- >>> Second draft to be published : 8 Jan 2015 >>> Second draft comments close : 12 Jan 2015, 23:59 UTC >>> Final proposal to be sent to ICG : 15 Jan 2015 >>> >>> How to Engage in Discussions: >>> ----------------------------- >>> All global discussions, for the CRISP team to consider as community >>> feedback, will be conducted at <ianaxfer(a)nro.net> mailing list. >>> All the CRISP Team discussions are open to observers. >>> >>> Next Step: >>> ----------- >>> In developing the final draft based on further feedback, the CRISP >>> Team will ensure it has completed considerations of all substantial >>> issues raised by the global community, which are compiled in the >>> published issues list. The proposal will only incorporate issues that >>> the CRISP team believes have received consensus support from the >>> community. >>> >>> References: >>> ------------ >>> * Discussions by the CRISP Team >>> Details of all the CRISP team's work to date, including recordings, >>> minutes and agendas of all the CRISP Team teleconferences and a >>> public archive of the internal CRISP team mailing list, are >>> available at: >>> https://nro.net/crisp-team >>> >>> * Other links: >>> - The ICG request for proposals: >>> <https://www.icann.org/news/announcement-3-2014-09-03-en> >>> >>> - The IANA Stewardship Transition Discussion in each RIR region: >>> <http://www.nro.net/timeline-engagement> >>> >>> - First Draft proposal (Edited version) >>> <http://www.nro.net/crisp-proposal-first-draft-1-1> >>> >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments
by Nurani Nimpuno 12 Jan '15

12 Jan '15

Dear colleagues, Today the Consolidated RIR IANA Stewardship Proposal (CRISP) team publishes the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. This is intended as a final call for community feedback ahead of the submitting the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. We understand that many in the RIPE community have a strong interest in this process, and feedback provided in this working group and elsewhere has been crucial in reaching the current draft. While there is still an opportunity to provide comments on the current text, we would also like to strongly encourage RIPE community members in favour of this proposal to express their support on this list or via the ianaxfer(a)nro.net mailing list. A quantifiable level of community support may be important in strengthening the Internet numbers community’s position later in the IANA stewardship transition process. As previously, the timeline for responding is quite tight, with a deadline of Monday, 12 January, for all comments. Best regards, Nurani Nimpuno on behalf of the RIPE CRISP team Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments > Date: 8 januari 2015 17:21:08 CET > To: "ianaxfer(a)nro.net" <ianaxfer(a)nro.net> > > Dear colleagues, > > > Please find the second draft of the Internet numbers community's > response to the Request For Proposals issued by the IANA Stewardship > Coordination Group (ICG). > > This draft has been prepared by the Consolidated RIR IANA Stewardship > Proposal (CRISP) Team, with considerations of feedback received from the > global community on <ianaxfer(a)nro.net> mailing list. > > We have incorporated the following key points in the second draft: > > - Additional description on contract details, review committee and > intellectual property rights > - Description revised on Section V. NITA Requirements and VI. > Community Process for more clarity > - No changes are made to key elements of the proposal > > The CRISP Team have considered all comments expressed on > <ianaxfer(a)nro.net> mailing list before the deadline of 5th Jan 2015, and > would now like to make the final call for comments from the global > community on the draft proposal, before submitting to the ICG. > > Second Draft proposal: > ------------------------ > Clean Version : > <http://www.nro.net/crisp-proposal-second-draft> > > Redline Version: > <http:/www.nro.net/crisp-proposal-second-draft-change-control> > > The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC > Feedback should be sent to : <ianaxfer(a)nro.net> mailing list > > Community Inputs Considered by the CRISP Team: > ------------------------------------------ > You can check the status of the issues raised by the community and > proposed the CRISP Team positions at: > > <http://www.nro.net/crisp-iana-xfer-summary-discussion-08012015> > > Key dates: > ----------- > Second draft to be published : 8 Jan 2015 > Second draft comments close : 12 Jan 2015, 23:59 UTC > Final proposal to be sent to ICG : 15 Jan 2015 > > How to Engage in Discussions: > ----------------------------- > All global discussions, for the CRISP team to consider as community > feedback, will be conducted at <ianaxfer(a)nro.net> mailing list. > All the CRISP Team discussions are open to observers. > > Next Step: > ----------- > In developing the final draft based on further feedback, the CRISP > Team will ensure it has completed considerations of all substantial > issues raised by the global community, which are compiled in the > published issues list. The proposal will only incorporate issues that > the CRISP team believes have received consensus support from the > community. > > References: > ------------ > * Discussions by the CRISP Team > Details of all the CRISP team's work to date, including recordings, > minutes and agendas of all the CRISP Team teleconferences and a > public archive of the internal CRISP team mailing list, are > available at: > https://nro.net/crisp-team > > * Other links: > - The ICG request for proposals: > <https://www.icann.org/news/announcement-3-2014-09-03-en> > > - The IANA Stewardship Transition Discussion in each RIR region: > <http://www.nro.net/timeline-engagement> > > - First Draft proposal (Edited version) > <http://www.nro.net/crisp-proposal-first-draft-1-1> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

4 3

Fwd: [CRISP-TEAM] CRISP Team Next Week Teleconferences
by Nurani Nimpuno 09 Jan '15

09 Jan '15

Fyi Nurani Begin forwarded message: > From: German Valdez <german(a)nro.net> > Date: 9 januari 2015 16:18:28 CET > To: <ianaxfer(a)nro.net> > Cc: crisp(a)nro.net > Subject: [CRISP-TEAM] CRISP Team Next Week Teleconferences > > Hi > > CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC > > Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. > > CRISP Team 11th Teleconference > Monday January 12th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc… > > CRISP Team 12th Teleconference > Tuesday January 13th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52… > > CRISP Team 13th Teleconference > Wednesday January 14th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6… > > CRISP Team 14th Teleconference > Thursday January 15th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db… > > Kind regards > > German Valdez > NRO > > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [CRISP-TEAM] Agenda for the 10th call
by Nurani Nimpuno 09 Jan '15

09 Jan '15

fyi Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [CRISP-TEAM] Agenda for the 10th call > Date: 9 januari 2015 11:22:18 CET > To: "crisp(a)nro.net" <crisp(a)nro.net> > > CRISP Team, > > > This is the draft agenda for today's call, at UTC13:00 9th Jan. > > It's not a must to disucuss agenda item 6 today. > > We are receiving e-mail inputs for item 5, so hopefully not as bad as it > looks! > > I'll send this to the IANAXFER list shortly but still feel free to add > anything else. > > > ---- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Announcements to relevant stakeholders > > 3. Confirm pending issues > a. LACNIC region chart > b. Numbering scheme in Section III > c. Possibility of reformatting Section III > d. PDF of issues list > e. CRISP Website improvements > > 4. Confirm comments received > a. Each RIR region > b. Global list > > 5. CRISP Team position per issue > a. More details of dispute resolution > b. Reflect low input in RIR processes Section VI > c. Option of having NRO as an operator > d. Change in ICANN Bylaws for global PDP > e. SLA text is a must to approve the proposal > f. No of past arbitration cases: to backup the proposal > g. How to know whether arbitration works > h. Editorial comments (Link, LACNIC region coverage) > > 6. Preparation for the final draft > a. Who will take care of which section > b. Timeline of each preparation phase > c. Time to submit to ICG > d. Updating issues list > > 7. Next Meeting > a. Reconfirm schedule of future CRISP Calls > b. Date of the 11th Call > > 8. AOB > ---- > > > Thanks, > Izumi > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [CRISP-TEAM] Webex information CRISP Team 10th Teleconference Friday January 9th 2015 13:00 UTC
by Nurani Nimpuno 09 Jan '15

09 Jan '15

fyi Begin forwarded message: > From: German Valdez <german(a)nro.net> > Subject: [CRISP-TEAM] Webex information CRISP Team 10th Teleconference Friday January 9th 2015 13:00 UTC > Date: 8 januari 2015 10:21:58 CET > To: <ianaxfer(a)nro.net>, <crisp(a)nro.net> > > > Hi > > Please find below webex information for the CRISP Team 10th Teleconference to be held on Friday January 9th 2015 at 13:00 > > Regards > > German Valdez > NRO > > > CRISP Team 10th Teleconference > Friday, January 9, 2015 > 1:00 pm | UTC | 1 hr > > Join WebEx meeting > Meeting number: 704 117 664 > 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 117 664 > Global call-in numbers | Toll-free calling restrictions > > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Last minute CRISP Team Teleconference January 8th 2015 13:00 UTC
by Nurani Nimpuno 08 Jan '15

08 Jan '15

fyi Begin forwarded message: > From: German Valdez <german(a)nro.net> > Subject: [NRO-IANAXFER] Last minute CRISP Team Teleconference January 8th 2015 13:00 UTC > Date: 8 januari 2015 14:13:42 CET > To: <ianaxfer(a)nro.net> > > > Hi > > On behalf of CRISP Team I’m attaching a webex invitation to follow their meeting right now. > > Meeting was called in very last minute to finalise details for the publication of the second draft proposal for the ICG > > Meeting is running right now and you are invited to join and follow the discussion/ > > Regards > > German Valdez > NRO > > > > Thursday, January 8, 2015 > 12:47 pm | UTC | 1 hr > > Join WebEx meeting > Meeting number: 707 924 572 > Meeting password: 12345 > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 707 924 572 > Toll-free calling restrictions > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [CRISP-TEAM] Draft Agenda for the 7th call Re: CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC
by Nurani Nimpuno 07 Jan '15

07 Jan '15

FYI Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [CRISP-TEAM] Draft Agenda for the 7th call Re: CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC > Date: 7 januari 2015 12:17:30 CET > To: crisp(a)nro.net > > Dear Colleagues, > > > Below is the draft agenda for the coming 7th CRISP Team Teleconference on Wednesday 7th January 2015 at 13:00 UTC. > > This is open to any observers as usual. > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Version Control of the drafts > c. Announcement of the comments closed on the IANAXFER list > > 2. Issues after the last call > a. Contract details (continued discussions) > b. Defining Review Commitee process > c. Community engagement in developing contract > > 3. Confirm status of issues > a. Issues to be reviewed on the ML (no discusssions at the call) > b. Reflecting CRISP Team positions per issues > (IRP, Review Commitee, SLA) > c. Issues Status list > > 4. Preparation for the 2nd draft announcement > a. draft announcement & its timing > b. Deadline of comments to be submitted for texts > c. Timing to share the updated version within CRISP Team > > 5. Next call > > 6. AOB > --- > > > Regards, > Izumi Okutani > CRISP Team > > On 2015/01/06 4:54, Maria Gayo wrote: >> Please find below webex information for the 9th CRISP Team teleconference to be >> held on Wednesday 7th January 2015 at 13:00 UTC >> >> Regards >> >> María Gayo >> (on behalf of the NRO Secretariat) >> >> >> -------- >> >> ***CRISP Team 9th Teleconference* >> >> Wednesday, January 7th, 2015 >> >> 1:00 pm UTC >> >> *Join Webex meeting >> *https://lacnic.webex.com/lacnic/j.php?MTID=me72f52dfbfd3075087e0f7d746af0391 >> >> Meeting number: 576 519 399 >> >> Meeting password: lcn2015 >> >> *Join by phone* >> >> 1-877-668-4490 Call-in toll-free number >> >> 1-408-792-6300 Call-in toll number >> >> Access code: 576 519 399 >> >> *Add this meeting to your calendar :* >> >> https://lacnic.webex.com/lacnic/j.php?MTID=m2d0e4b80f02040f773c0643a4b428587 >> >> Can´t join this meeting? Contact support https://lacnic.webex.com/lacnic/mc or >> florencia(a)lacnic.net <mailto:florencia@lacnic.net> Phone: 598-26042222 >> >> Embedded Image >> *María Gayo* >> Coordinadora de Comunicaciones >> Communications Coordinator >> *# 4206* >> Embedded Image >> *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 <http://www.lacnic.net> >> >> >> >> _______________________________________________ >> CRISP mailing list >> CRISP(a)nro.net >> https://www.nro.net/mailman/listinfo/crisp >> > > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Thank you for the feedback and update on CRISP Team Status
by Nurani Nimpuno 07 Jan '15

07 Jan '15

FYI. Nurani Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Thank you for the feedback and update on CRISP Team Status > Date: 7 januari 2015 09:48:14 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > CRISP Team would like to thank everyone who have provided your inputs to > the first draft of our proposal. > > We have closed comments for the first draft, and completed to form CRISP > Team's position on all issues express on <ianaxfer(a)nro.net> mailing list > at the 8th CRISP Team call, at UTC13:00 Mon 5th Jan. > > CRISP Team is now working to publish the second draft, which is planned > to be published on Thu 8th Jan. We will make an announcement on this > mailing list, and call for comments from the global community once it is > published, as we did for the first draft. > > In the meantime, attached is the status list of issue raised on > <ianaxfer(a)nro.net> for you to confirm status of CRISP Team > considerations. Please note this is to be updated as our work progresses. > > We are planning to publish the updated issues status list when we > publish our second draft. > > Thank you once again for taking your time to review the first draft of > our proposal and sharing your views. > > > Best Regards, > Izumi Okutani > CRISP Team Chair > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [CRISP-TEAM] CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC
by Nurani Nimpuno 07 Jan '15

07 Jan '15

FYI. A placeholder extra teleconference has been scheduled today at 14.00 CET, to discuss any outstanding issues before the finalisation of the 2nd draft of the CRISP proposal. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: Maria Gayo <mgayo(a)lacnic.net> > Subject: [CRISP-TEAM] CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC > Date: 5 januari 2015 20:54:09 CET > To: crisp(a)nro.net > Reply-To: mgayo(a)lacnic.net > > Please find below webex information for the 9th CRISP Team teleconference to be held on Wednesday 7th January 2015 at 13:00 UTC > > > > Regards > > María Gayo > (on behalf of the NRO Secretariat) > > > -------- > > CRISP Team 9th Teleconference > > Wednesday, January 7th, 2015 > > 1:00 pm UTC > > Join Webex meeting https://lacnic.webex.com/lacnic/j.php?MTID=me72f52dfbfd3075087e0f7d746af0391 > > Meeting number: 576 519 399 > > Meeting password: lcn2015 > > Join by phone > > 1-877-668-4490 Call-in toll-free number > > 1-408-792-6300 Call-in toll number > > Access code: 576 519 399 > > Add this meeting to your calendar : > https://lacnic.webex.com/lacnic/j.php?MTID=m2d0e4b80f02040f773c0643a4b428587 > > Can´t join this meeting? Contact support https://lacnic.webex.com/lacnic/mc or florencia(a)lacnic.net Phone: 598-26042222 > 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 _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Draft Agenda for 8th Teleconfererence Re: CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC
by Nurani Nimpuno 05 Jan '15

05 Jan '15

fyi Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Draft Agenda for 8th Teleconfererence Re: CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > Date: 5 januari 2015 11:40:43 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > Please see the draft agenda for CRISP Team 8th Teleconference January > 5th 2015 @ 13:00 UTC. > > Observers are welcome to join the call as usual. > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Recordings of past meetings > c. Version control of drafts > > 3. Confirm new comments since the 7th call > a. Each RIR region > b. Global list > > 3. Follow up of issues discussed > a. IPR > b. Contract > c. Review Commitee > > 4. Issues not yes discussed > a. Details of the Review Process > b. RIR Accountability, > c. Determining consensus for the final draft > > 6. Preparation for the 2nd draft > a. Topics to be reflected in the 2nd draft > b. Announcement > > 7. Next Meeting > > 8. AOB > --- > > > Regards, > Izumi Okutani > CRISP Team > > On 2015/01/03 0:03, German Valdez wrote: >> Hi >> >> Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC >> >> Regards >> >> German Valdez >> NRO >> >> >> ====== >> >> CRISP Team 8thTeleconference >> Monday, January 5, 2015 >> 1:00pm | UTC | 2 hr >> >> Join WebEx meeting >> https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362… <https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362…> >> >> Meeting number: >> 701 103 817 >> Meeting password: >> crispteam >> >> Join by phone >> 0800-051-3810 Call-in toll-free number (UK) >> +44-203-478-5289 Call-in toll number (UK) >> Accesscode: 701 103 817 >> Global call-in numbers | >> >> https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012… <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012…> >> >> Toll-free calling restrictions >> >> http://www.webex.com/pdf/tollfree_restrictions.pdf <http://www.webex.com/pdf/tollfree_restrictions.pdf> >> >> >> Add this meeting to your calendar. >> >> Can't join the m Contact support. >> >> IMPORTANT NOTICE: Please note thatsession. >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer(a)nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Last Day to Comment on IANA Stewardship Draft
by Chris Buckridge 05 Jan '15

05 Jan '15

Dear colleagues, A reminder that today is the last day for commenting on the first draft of the Internet numbers community’s IANA stewardship proposal. The draft, produced by the Consolidated RIR IANA Stewardship Proposal (CRISP) team, is available at: https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf After the comment period closes, the CRISP team will prepare a second public draft, based on the feedback received. The timeline for the remaining CRISP team work is: Second draft to be published: 8 Jan 2015 Final proposal to be sent to IANA Stewardship Transition Coordination Group (ICG): 15 Jan 2015 The CRISP team will hold its eighth teleconference today, 5 January, at 13:00 UTC. Details on how to join the call as an observer are included at the end of this email. More background on the IANA stewardship transition process is available at: https://www.ripe.net/iana-oversight-transition Details on the CRISP team, including members, timelines and working methods, are available at: https://nro.net/crisp-team Best regards, Chris Buckridge RIPE NCC ====== CRISP Team 8thTeleconference Monday, January 5, 2015 1:00pm | UTC | 2 hr Join WebEx meeting https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362… Meeting number: 701 103 817 Meeting password: crispteam Join by phone 0800-051-3810 Call-in toll-free number (UK) +44-203-478-5289 Call-in toll number (UK) Accesscode: 701 103 817 Global call-in numbers: https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012… Toll-free calling restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

1 0

Video archives of CRISP teleconferences available
by Nurani Nimpuno 05 Jan '15

05 Jan '15

Dear colleagues, Just a quick note to let you know that video archives of all CRISP teleconferences are publicly available (on youtube) from the NRO website (in addition to the audio files and minutes published). You will find all CRISP related information, including the latest draft proposal text, a matrix of all input received, and the process timeline at: https://www.nro.net/crisp-team Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE 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

Fwd: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC
by Nurani Nimpuno 04 Jan '15

04 Jan '15

Dear colleagues, Please find details below about the 8th CRISP teleconference. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: German Valdez <german(a)nro.net> > Subject: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > Date: 2 januari 2015 16:03:18 CET > To: <ianaxfer(a)nro.net>, <crisp(a)nro.net> > > Hi > > Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC > > Regards > > German Valdez > NRO > > > ====== > > CRISP Team 8thTeleconference > Monday, January 5, 2015 > 1:00pm | UTC | 2 hr > > Join WebEx meeting > https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362… > > Meeting number: > 701 103 817 > Meeting password: > crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Accesscode: 701 103 817 > Global call-in numbers | > > https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012… > > Toll-free calling restrictions > > http://www.webex.com/pdf/tollfree_restrictions.pdf > > > Add this meeting to your calendar. > > Can't join the m Contact support. > > IMPORTANT NOTICE: Please note thatsession. > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published
by Nurani Nimpuno 04 Jan '15

04 Jan '15

Dear colleagues, Firstly, a very happy new year to all of you! :) I hope you all had a well deserved rest. As you may know, the CRISP team, tasked with coming up with a proposal for the Internet numbers community on the IANA stewardship transition, has published a first draft. We would warmly welcome any comments you have on this draft, on the global <ianaxfer(a)nro.net> mailing list. The deadline for feedback on this draft is 5 January. The second draft will be distributed on 8 January, and the very final proposal is due for submission 15 January. 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 --------------------------------------------- Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: Re: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published > Date: 2 januari 2015 19:17:09 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > > This is a friendly reminder that the deadline for providing feedback to the first draft of the proposal from Internet Number Community on IANA Stewardship is: 5 January 2015. > > Based on the request made by a community member on this mailing list, please find below the text format of the first proposal. This is identical to the edited version of the first proposal published at: > > https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-Draft-24122014-c… > > We continue to welcome your feedback on <ianaxfer(a)nro.net> mailing list. > > > > Best Regards, > > Izumi Okutani > Chair, Consolidated RIR IANA Stewardship Proposal (CRISP) team > > ------------------------------------------------------------------------------- > Draft Response to the Internet Coordination Group Request for > Proposals on IANA from the RIR community > 1. Proposal type > > Identify which category of the IANA functions this submission proposes to address: > > [ ] Names > [ 口] Numbers > [ ] Protocol Parameters > > > > I. Description of Community’s Use of IANA > > This section should list the specific, distinct IANA services or activities your community relies > on. For each IANA service or activity on which your community relies, please provide the following: > > · A description of the service or activity. > · A description of the customer(s) of the service or activity. > · What registries are involved in providing the service or > activity. > · A description of any overlaps or interdependencies between > your IANA requirements and the > functions required by other customer communities > > ------- > · A description of the service or activity. > > The relevant IANA activities to the number resource communities are the allocation of IPv4 addresses, IPv6 addresses, and Autonomous System Numbers (“ASNs”) to the Regional Internet Registries (“RIRs”) as well as the delegation of the “IN-ADDR.ARPA” and “IP6.ARPA” DNS trees in accordance with the allocation of IPv4 and IPv6 addresses. > > · A description of the customer(s) of the service or activity. > > The RIRs manage the registration and distribution of Internet number resources (IPv4 and IPv6 addresses and ASNs) to members within their service regions. The five RIRs in operation at this point in time are: > > AFRINIC Serving Africa Founded in 2005 > APNIC Serving the Asia Pacific region Founded in 1993 > ARIN Serving North America Founded in 1997 > LACNIC Serving South America and the Caribbean Founded in 2001 > RIPE NCC Serving Europe, Central Asia and the Middle East Founded in 1992 > > The five RIRs manage the distribution and registration of Internet number resources at the regional level, having received blocks of unused resources from the global pools managed by the IANA operator. The RIRs also facilitate the policy development processes of their > respective communities. > > The five RIRs have a long-standing and straightforward operational relationship with IANA. IANA maintains the global pools of Internet number resources from which the RIRs receive allocations to distribute to their communities. The RIRs also coordinate with IANA to correctly register any resources that are returned to the global pools. Collectively, the system for administering Internet number resources is referred to as the "Internet Number Registry System" and is described > in detail in RFC 7020. > > ------- > · What registries are involved in providing the service or > activity. > > The most relevant IANA registries are the IPv4 address registry, the IPv6 address registry, and the ASN registry. Delegation of “IN-ADDR.ARPA” and “IP6.ARPA”domain names also requires interaction with the .ARPA zone registry. > > ------- > · A description of any overlaps or interdependencies between > your IANA requirements and the > functions required by other customer communities. > > The Internet Engineering Task Force (“IETF”) is responsible for policy relating to the entire IP address space and AS number space. Through the IANA protocol parameters registries, the IETF delegates unicast IP address ("IANA IPv4 Address Space Registry" and "IPv6 Global Unicast Allocations Registry") and AS number space (“ASN Registry) to the RIR system [RFC7020]. Note that within each IANA registry, there are also reserved values or ranges, and special-purpose registries, which are outside the Internet Numbers Registry System and instead administered under the direction of the IETF. The delineation of the specific ranges delegated to the Internet Number Registry system is provided in RFC 7249. It is expected that the boundary between IETF-managed and Internet Number Registry-managed parts of the number spaces may change from time to time, with agreement between the IETF and the RIRs. Potential reasons for changes include the possibility > that the IETF may release some previously reserved space for general use, or may reserve some previously unused space for a special purpose. > The global Internet community also depends upon the IANA operator for administration of the special-purpose “IN-ADDR.ARPA” and “IP6.ARPA” DNS zones which are associated with IPv4 and IPv6 number resources respectively. These zones are delegated to IANA by the Internet Architecture Board (“IAB”) and “[s]ub-delegations within this hierarchy are undertaken in accordance with the IANA’s address allocation practices” (RFC3172). The IANA operator administers these zones as “agreed technical work items” per the IETF- Internet Corporation for Assigned Names and Numbers (“ICANN”) IANA MoU. It is important to note that this work is outside the scope of the National > Telecommunications and Information Administration (“NTIA”) contract. > > Relevant links: > IETF-ICANN MoU Concerning the Technical Work of the Internet Assigned Numbers Authority: > https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-en > “The Internet Numbers Registry System”, RFC 7020: https://tools.ietf.org/html/rfc7020 “Internet > Numbers Registries”, RFC 7249: https://tools.ietf.org/html/rfc7249 > > > > II. Existing, Pre-Transition Arrangements > > This section should describe how existing IANA-related arrangements work, prior to the transition. > > A. Policy Sources > > This section should identify the specific source(s) of policy which must be followed by the IANA functions operator in its conduct of the services or activities described above. If there are distinct sources of policy or policy development for different IANA activities, then please describe these separately. For each source of policy or policy development, please provide the following: > > · Which IANA service or activity (identified in Section I) is > affected. > · A description of how policy is developed and established and > who is involved in policy development and establishment. > · A description of how disputes about policy are resolved. > · References to documentation of policy development and dispute > resolution processes. > > ------- > · Which IANA service or activity (identified in Section I) is > affected. > > The Internet number resource registries. > > It is important to note that allocations of Internet number resources from IANA to the RIRs and its registrations in IANA registries, as well as delegations of “IN-ADDR.ARPA” and “IP6.ARPA” domains, described in Section I, are conducted between IANA and the RIRs without involvement by the NTIA. > > ------- > · A description of how policy is developed and established and > who is involved in policy development and establishment. > > The policies under which the IANA operator manages the global pools of Internet number resources (excluding those address ranges reserved by the IETF for specific technical purposes) are developed and agreed by the five RIR communities via open, transparent and bottom-up policy development processes. Each RIR community engages in its own regional policy development process; these processes are open to all stakeholders regardless of specific background or interest. Links to each of the five regional Policy Development Processes (“PDPs”) are included under in the RIR Governance Matrix published on the Number Resource Organization (“NRO”) website [www.nro.net/about-the-nro/rir-governance- matrix]. > > Any individual may submit a global proposal. Each RIR community must ratify an identical version of the proposed policy. The NRO Executive Council (“NRO EC”) then refers the coordinated proposal to the Address Supporting Organization (“ASO”) Address Council (“ASO AC”), which reviews the process by which the proposal was developed and, under the terms of the ASO Memorandum of Understanding (“ASO MoU”), passes it to the ICANN Board of Directors for ratification as a global policy. > > There are currently three global policies relating to management of the global pools of IPv4 addresses, IPv6 addresses and AS Numbers [https://www.nro.net/policies] > > (a) IANA Policy for Allocation of IPv6 Blocks to Regional Internet Registries; > (b) IANA Policy for Allocation of ASN Blocks to Regional Internet Registries; and > (c) Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. > > There is a fourth global policy agreed by the RIR communities, ICP-2, "Criteria for Establishment of New Regional Internet Registries". > > The global Policy Development Process (“gPDP”) described in “Global Policy Development Process Document” [https://www.nro.net/documents/global-policy-development- process] is used for all of the number-related IANA activities described in Section I, but the policy that > “IN-ADDR.ARPA” and “IP6.ARPA” domains must be delegated following IPv4 and IPv6 address allocations is specified by the IETF (most recently in RFC 3172). > > ------- > · A description of how disputes about policy are resolved. > > The gPDP is formally described in "Attachment A" of the ASO MoU, signed by ICANN and the RIRs in 2004 (and signed by AFRINIC when it was established as the fifth RIR in 2005). This MoU includes provisions for resolving disputes between ICANN and the RIRs or their communities. It is important to note that while the gPDP allows for the ICANN Board to dispute the outcome of a consensus community decision (escalating to mediation between ICANN and the RIRs), it does not include any role for the IANA contract holder (currently the NTIA). The ASO MoU is an agreement between the RIR communities and ICANN; NTIA has no oversight role in policy-making as regards management of the global Internet number resource pools, and its transition out of its current role would have minimal effect on the policy-making framework. > > A separate MoU, the NRO MoU, establishes the NRO as "a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs", and includes provisions for dispute resolutions between RIRs on issues relating to global policy development or implementation. > > It is the responsibility of the NRO Number Council (“NRO NC”), a group comprising three community members selected by each of the five RIR communities, to confirm that the documented RIR PDPs have been followed in the development and approval of a new policy or policy change. Further, this group reviews the policy followed by each of the RIR communities to assure itself that the significant viewpoints of interested parties were adequately considered,and only after this confirmation does it then consider forwarding global policy proposals to the ICANN Board for ratification. > > The NRO NC also acts in the role of the ICANN ASO AC, and as such, presents the agreed global policy proposal to the ICANN Board for ratification and operational implementation. > > The ICANN Board reviews the received global number resource policy proposals and may ask questions and otherwise consult with the ASO Address Council and/or the individual RIRs acting collectively > through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate. If the ICANN Board rejects the proposed policy, it delivers to the ASO ACa statement of its concerns with the proposed policy, including in particular an explanation of the significant viewpoints that were not adequately considered during the regular RIR processes. By agreement of all RIRs, the ASO AC may forward a new proposed policy (either reaffirming the previous proposal or > a modified proposal) to the ICANN Board. If the resubmitted proposed policy is rejected for a second time by ICANN, then the RIRs or ICANN shall refer the matter to mediation. > > In case of disputes where mediation has failed to resolve the dispute, the ICANN ASO MoU agreement provides for arbitration via ICC rules in the jurisdiction of Bermuda or such other location as is agreed between the RIRs and ICANN. It is also worth noting that the RIRs have been participating (as the ASO) in the periodic independent review processes for Accountability and Transparency (ATRT) that is called for per ICANN’s Bylaws. > > ------- > · References to documentation of policy development and dispute > resolution processes. > > Relevant links: > ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou > NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding > About the NRO Number Council: https://www.nro.net/about-the-nro/the-nro-number-council RIR > Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix > Global Policies: https://www.nro.net/policies > > > > B. Oversight and Accountability > > This section should describe all the ways in which oversight is conducted over IANA’s provision of the services and activities listed in Section I and all the ways in which IANA is currently held accountable for the provision of those services. For each oversight or accountability mechanism, please provide as many of the following as are applicable: > > · Which IANA service or activity (identified in Section I) is > affected. > · If the policy sources identified in Section II.A are affected, > identify which ones are affected and explain in what way. > · A description of the entity or entities that provide oversight > or perform accountability functions, including how individuals > are selected or removed from participation in those entities. > · A description of the mechanism (e.g., contract, reporting > scheme, auditing scheme, etc.). > This should include a description of the consequences of the > IANA functions operator not meeting the standards established > by the mechanism, the extent to which the output of the > mechanism is transparent and the terms under which the > mechanism may change. > · Jurisdiction(s) in which the mechanism applies and the legal > basis on which the mechanism rests. > > ------- > · Which IANA service or activity (identified in Section I) is > affected. > > The Internet number resource registries. > > ------- > · If the policy sources identified in Section II.A are affected, > identify which ones are affected and explain in what way. > > 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 currently provided by ICANN. However, it would remove a significant element of oversight from the current system. > > There is no contractual obligation directly to the Internet number resource community for the IANA operator to provide IANA registry services for the Internet number registries; IANA services for > the Internet number registries are provided by ICANN since its formation as a result of the NTIA IANA Functions contract and hence IANA services for the Internet number registries are presently > subject to change per that agreement. > > ------- > · A description of the entity or entities that provide oversight > or perform accountability functions, including how individuals > are selected or removed from participation in those entities. > > All institutional actors with a role in management of Internet number resources are accountable to the open communities that make and agree on the policies under which those resources are distributed and registered. The mechanisms used to ensure and enforce this accountability differ for each of these actors. > > 1. NTIA > ICANN, as the current operator of the IANA functions, is obligated by the NTIA agreement to carry out management of the global IP address and AS Number pools according to policies developed by the communities. > > While the IANA operator escalation and reporting mechanisms are public in nature, the Internet number community is primarily represented in oversight of the IANA operator performance by the RIRs, which are member-based based organizations with elected governance boards. > Currently, the NTIA does not have an oversight role in this regard. > > The ultimate consequence of failing to meet the performance standards or reporting requirements is understood to be a decision by the contracting party (the NTIA) to terminate or not renew the IANA > functions agreement with the current contractor (ICANN). > > 2. The Regional Internet Registries > > Administration by the IANA operator consists predominantly of processing of requests from the RIRs for issuance of additional number resources. The five RIRs are intimately familiar with global number resource policies under which the requests are made and maintain communications with the IANA operations team throughout the request process. > > The RIRs are not-for-profit membership associations, and as such are accountable to their members by law. The specific governance processes for each RIR differ depending on where they have been established and the decisions made by their membership, but in all RIRs, members have the right to vote individuals onto the governing Board and to vote on specific funding or operational resolutions. > > At the same time, an RIR's registration and allocation practices are directed by policies developed by its community. Each RIR community's PDP defines how these policies are developed, agreed and accepted for operational implementation. > > The corporate governance documents and PDPs of each RIR and its community are accessible via the RIR Governance Matrix, published on the NRO website. > > ------- > · A description of the mechanism (e.g., contract, reporting > scheme, auditing scheme, etc.). > This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is > transparent and the terms under which the mechanism may change. > > The NTIA IANA Agreement currently defines obligations of the IANA operator for Internet number resources. > > This obligation is specifically noted in section C.2.9.3 of the NTIA agreement: > > C.2.9.3 Allocate Internet Numbering Resources --The Contractor shall have responsibility for allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space based on established guidelines and policies as developed by interested and affected parties as enumerated in Section C.1.3. > > The NTIA agreement also lays out specific deliverables for the IANA operator (ICANN) to produce as a condition of the agreement (see "Section F – Deliveries and Performance"), including performance > standards developed in cooperation with the affected parties (in the case of the Internet number resource pools, the affected parties include the RIRs and their communities), customer complaint > procedures and regular performance reporting. > > These deliverables are met by ICANN via monthly reporting on their performance in processing requests for the allocation of Internet number resources; these reports include IANA operator performance against key metrics of accuracy, timeliness, and transparency, as well as the performance metrics for individual requests. The IANA operations team also provides escalation procedures for use in resolving any issues with requests, as per the "IANA Customer Service Complaint Resolution Process". > > ------- > · Jurisdiction(s) in which the mechanism applies and the legal > basis on which the mechanism rests. > > Jurisdiction for this current mechanism is the United States of America under applicable Federal government contracting laws and regulations. > > Relevant links: > NTIA IANA Agreement: http://www.ntia.doc.gov/page/iana-functions-purchase-order > ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou > NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding > IANA Customer Service Complaint Resolution Process: http://www.iana.org/help/escalation- procedure > IANA Performance Standards Metrics Report: http://www.iana.org/performance/metrics > RIR Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix > > > > 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. > > ------- > The elements of this proposal are as follows: > > (1) ICANN to continue as the IANA functions operator on number > resources; > (2) Service level agreement with the IANA functions operator on > number resources; and > (3) Establishment of a Review Committee, with representatives > from each RIR, to advise the NRO EC on the review of the > IANA functions operator’s performance and meeting of > identified service levels. > > To maintain stability and continuity in operations of the Internet number-related IANA services, very minimal changes to the arrangements listed in Section II.B are proposed, including the identification of the proposed initial IANA functions operator. 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. > > 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 currently provided by ICANN. 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. Other than the replacement of the NTIA with the five RIRs as the party(ies) with whom the IANA functions operator would contract for provision of Internet number-related IANA services, the overall arrangements in Section II.B would remain with no change. > > The proposed arrangement involves the same IANA service or activity, policy sources identified in Section II.A are unaffected, the entities that provide oversight or perform accountability functions (the RIRs) remain the same, the consequence for failure to meet performance standards remains termination or decision not to renew the IANA functions agreement with the then-current contractor, and jurisdiction will be dependent on the chosen IANA functions operator. > > The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five 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 gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, 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. IANA operations should be > reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. > > To ensure the service level defined in the proposed contract is maintained and provided by the IANA functions operator, the NRO EC will conduct periodic reviews of the service level of the IANA number resource functions that serves each RIR and their respective communities. The NRO EC shall establish a Review Committee that will advise and assist the NRO EC in its periodic review. Any such Review Committee should be a team composed of representatives from each RIR region that will, as needed, undertake a review of the level of service received from the IANA functions operator and report to the NRO EC any concerns regarding any observed failure by the IANA functions operator to meet its contractual obligations under the proposed contract. Any such Review Committee will advise the NRO EC in its capacity solely to oversee the performance of the IANA number resource functions and the Review Committee’s advice and comment will be limited to the processes followed in the IANA functions operator’s performance under the proposed contract. > > 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. > > This proposal carries no implication for the interface between IANA functions and existing policy arrangements described in Section II.A. The text in "Attachment A" of the ICANN ASO MoU 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. > > > IV. Transition Implications > > This section should describe what your community views as the implications of the changes it proposed in Section III. These implications may include some or all of the following, or other > implications specific to your community: > > · Description of operational requirements to achieve continuity > of service and possible new service integration throughout the > transition. > · Risks to operational continuity and how they will be addressed. > · Description of any legal framework requirements in the absence > of the NTIA contract. > · Description of how you have tested or evaluated the > workability of any new technical or > operational methods proposed in this document and how they > compare to established arrangements. > > ------- > · Description of operational requirements to achieve continuity > of service and possible new service integration throughout the > transition. > · Risks to operational continuity and how they will be addressed. > > The intent of the proposal described above is to: > > 1. Minimize risks to operational continuity of the management of the Internet number- related IANA functions, and; > 2. Retain the existing framework for making those policies that describe the management of the global Internet number resource pools, as this framework is already structured to ensure open, bottom-up development of such policies. > > Under current arrangements, the NTIA is responsible for extending or renewing the IANA functions agreement, and setting the terms of that contract. A new contract with the five RIRs and the IANA functions operator as signatories would shift the responsibility for renewing, setting terms or terminating the contract to the RIRs, who would coordinate their decisions via the NRO EC (made up of the RIR Directors and Chief Executives). Decisions made regarding the contract would be based on operational circumstances, past performance and input from open, regional communities. > > The shift from the existing contractual arrangement to another contractual arrangement (perhaps relying on a set of distinct contracts) covering the IANA functions operator’s ongoing management > of all the IANA functions should result in no operational change for management of the global Internet number resource pools. This will help minimize any operational or continuity risks associated with stewardship transition. > > By building on the existing Internet registry system (which is open to participation from all interested parties) and its structures, the proposal reduces the risk associated with creating new organizations whose accountability is unproven. > > The necessary agreement proposed for IANA operation services for the Internet number registries can be established well before the NTIA target date for transition (September 2015), as there are no changes to existing service levels or reporting that are being proposed, only a change in contracting party to align with the delegated policy authority. > > ------- > · Description of any legal framework requirements in the absence > of the NTIA contract. > > The necessary legal framework in the absence of the NTIA contract will be fulfilled by the proposed agreement between the IANA functions operator and the five RIRs. As stated in Section III above, > 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 gPDP as well as > management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, 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. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. > > The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. The contract would also provide for jurisdiction and governing law regarding the new arrangement. > > ------- > · Description of how you have tested or evaluated the > workability of any new technical or > operational methods proposed in this document and how they > compare to established arrangements. > · Risks to operational continuity and how they will be addressed. > > This proposal does not propose any new technical or operational methods. There is inclusion of a proposed Review Committee to be established by the five RIRs acting cooperatively and coordinating > through the NRO EC; however, this does not carry any new operational method as the IANA functions operator would remain accountable to the party with whom it is contracting, in this case, the five RIRs in place of the NTIA. The proposed Review Committee is a tool for the five RIRs to evaluate and review performance of the IANA functions provided. > > > > V. NTIA Requirements > > Additionally, NTIA has established that the transition proposal must meet the following five requirements: > > · Support and enhance the multistakeholder model; > · Maintain the security, stability, and resiliency of the > Internet DNS; > · Meet the needs and expectation of the global customers and > partners of the IANA services; > · Maintain the openness of the Internet. > · The proposal must not replace the NTIA role with a > government-led or an inter-governmental organization solution. > > This section should explain how your community’s proposal meets these requirements and how it responds to the global interest in the IANA functions. > > ------- > The proposal for the IANA stewardship transition for the Internet number registries builds upon the existing, successful framework used by the Internet number community today. The major characteristics of this approach include: > > 1. Global number policy development which is open and transparent to any and all participants > 2. Continuance of existing IANA service levels, escalation processes, and reporting mechanisms > 3. Maintenance of independent review and ratification for developed global Internet number resource policy > 4. Continued use of periodic third-party independent reviews of accountability and transparency of processes > 5. No change of the existing IANA operator for maximum stability and security of operational processes and systems > 6. Accountable, member-based, globally-distributed RIR organizations providing routine IANA operational oversight for the Internet number registries > 7. No new organization is proposed. However, a new process within the RIR structures is proposed, where a Review Committee is established to advise and assist the NRO EC in its periodic review of the service level provided by the IANA functions operator. > > As a result of the approach taken (and its characteristics as outlined above), it is clear that the proposal from the Internet number community meets the stated NTIA requirements. > > > VI. Community Process > > This section should describe the process your community used for developing this proposal, including: > > · The steps that were taken to develop the proposal and to > determine consensus. > · Links to announcements, agendas, mailing lists, consultations > and meeting proceedings. > · An assessment of the level of consensus behind your > community’s proposal, including a description of areas of > contention or disagreement. > > ------- > 1. Regional and global process > > Each of the five RIR communities is discussing the IANA stewardship issues via mailing lists, at their RIR meetings and in other community forums. While these discussions have been uniformly open and transparent, with all discussions archived on mailing lists and meeting records, each community has adopted a specific process of their own choosing to reach an agreed community output. > > The results from the five regional processes fed a global process that produced this document. More details about the regional and global processes are given below, interspersed with links to relevant documents. > > 2. AFRINIC regional process: > The AFRINIC community held a consultative meeting on 25 May to 6 June 2014 during the Africa Internet Summit (AIS'2014) in Djibouti in the "IANA oversight transition" workshop. As a follow up to the meeting, AFRINIC setup a mailing list to provide a platform for the African > Internet community to discuss the IANA Oversight Transition process. The mailing list was announced on July 4, 2014 to develop a community position. The list and its archives can be found at: > https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight > > A Dedicated web portal was setup for sharing information on the IANA stewardship transition with the AFRINIC community and is also available at http://afrinic.net/en/community/iana-oversight-transition > > AFRINIC also conducted a survey seeking community input on the IANA Stewardship Transition. The results of the survey are published > at: http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%2… > %20transition.pdf > > > The last face-to-face meeting at which IANA oversight transition consultations were held with the community was during the AFRINIC-21 meeting in Mauritius, 22-28 November 2014. The recordings of > the session are available at http://meeting.afrinic.net/afrinic-21/en/vod > > Discussions continued on the ianaoversight(a)afrinic.net mailing list, until the closure of the comments from the number resources communities set by the CRISP Team on 12th Jan 2015. > > 3. APNIC regional process: > APNIC, as the secretariat for the APNIC community has set up a public mailing list (announced on 1 Apr 2014) to develop a community position, and have discussions about the proposal from the region on IANA stewardship transition: http://mailman.apnic.net/mailman/listinfo/IANAxfer > > Webpage, dedicated to sharing up-to-date information on the IANA stewardship transition was set up, for the APNIC community members and wider community members who are interested in this issue can be updated: http://www.apnic.net/community/iana-transition > > Draft proposal was discussed at the dedicated session at the APNIC 38 Meeting, which saw the general community consensus. The meeting provided > remote participation tools to enable wider participation from communities across Asia Pacific and beyond, with live webcasts well as Adobe Connect virtual conference room. > > https://conference.apnic.net/38/program#iana > > The discussions continued on the "ianaxfer(a)apnic.net." mailing list, > until the closure of the comments from the number resources communities set by CRISP Team as 12th Jan 2015. > > 4. ARIN regional process: > > <TBD> > > 5. LACNIC regional process: > > > <TBD> > > 6. RIPE regional process: > The RIPE community agreed at the RIPE 68 Meeting in May 2014 that the development of a community position on IANA stewardship should take place in the RIPE Cooperation Working Group, and via that working group's public mailing list: https://www.ripe.net/ripe/mail/wg- lists/cooperation > > The RIPE NCC, as secretariat for the RIPE community, also facilitated discussions on the IANA stewardship in national and regional forums across the RIPE NCC service region. Summaries of these discussions were posted to the RIPE Cooperation Working Group mailing list and on the RIPE website: > https://www.ripe.net/iana-discussions > > Between September and November 2014, RIPE community discussion centered around developing a set of principles reflecting the communities primary concerns in the development of an alternative IANA stewardship arrangement. These discussions are reflected in the discussions on the mailing list from that time: http://www.ripe.net/ripe/mail/archives/cooperation- wg/ > > Discussions at the RIPE 69 Meeting in November 2014 saw general community consensus on the principles discussed on the mailing list, and support expressed for the three community members selected to join the Consolidated RIR IANA Stewardship Proposal (CRISP) team. > > RIPE Cooperation Working Group Session: https://ripe69.ripe.net/programme/meeting- plan/coop-wg/#session1 > RIPE 69 Closing Plenary Session: https://ripe69.ripe.net/archives/video/10112/ > > ------- > 7. Global process (CRISP Team) > On 16 October 2014, the NRO EC proposed the formation of a Consolidated RIR IANA Stewardship > > Proposal (CRISP) team to develop a single Internet numbering community proposal to the IANA Stewardship Coordination Group (ICG). Each RIR community selected three members (two community members and one RIR staff) to participate in the team. The participants selected were: > > AFRINIC Region > Alan P. Barrett – Independent Consultant > Mwendwa Kivuva – Network Infrastructure Services, University of Nairobi Ernest Byaruhanga (Appointed RIR staff) > > ARIN Region > Bill Woodcock – President and Research Director of Packet Clearing House > John Sweeting – Sr. Director, Network Architecture & Engineering at Time Warner Cable > Michael Abejuela (Appointed RIR staff) > > APNIC Region > Dr Govind – CEO NIXI > Izumi Okutani – Policy Liaison JPNIC > Craig Ng (Appointed RIR staff) > > LACNIC Region > Nico Scheper - Curacao IX > Esteban Lescano - Cabase Argentina > Andrés Piazza (Appointed RIR staff) > > RIPE NCC Region > Nurani Nimpuno – Head of Outreach & Communications at Netnod > Andrei Robachevsky – Technology Programme Manager at the Internet Society Paul Rendek (Appointed > RIR staff) > > Steps and timeline for proposal development and links to announcements, mailing lists, and > proceedings - https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for… > engagement-in-iana-stewardship-transition-process > > ------- > 8. Assessment of consensus level > <TBD> > > <END> > > On 2014/12/29 20:43, Izumi Okutani wrote: >> Dear Colleagues, >> >> >> CRISP Team has published an editorial version of the Internet >> numbers community's response to the Request For Proposals issued by the >> IANA Stewardship Coordination Group (ICG): >> >> http://www.nro.net/crisp-proposal-first-draft-1-1 >> >> From the initial draft we published on 19th Dec [*], we have made >> editorial changes only. No changes are made in contents of the proposal. >> >> [*] >> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf >> >> The editorial changes are intended to clarify our answers to RFP, by >> re-ordering answers in the same order as questions listed in each >> Section. Some small additions have been made to address points that had >> not been answered in the earlier draft. Finally, there are some changes >> made for stylistic reasons. >> >> The deadline of the comments to be submitted to <ianaxfer(a)nro.net> >> mailing list remains the same: Monday 5th Jan 2015. >> >> Please let us know if you have any questions about version 1.1 of our >> draft proposal, and we continue to welcome feedback from the community. >> >> >> Best Regards, >> Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

3 4

Fwd: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC
by Nurani Nimpuno 02 Jan '15

02 Jan '15

Fyi. The CRISP teleconferences are open to observers. Nurani Begin forwarded message: > From: German Valdez <german(a)nro.net> > Date: 2 januari 2015 16:03:18 CET > To: <ianaxfer(a)nro.net>, <crisp(a)nro.net> > Subject: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > > Hi > > Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC > > Regards > > German Valdez > NRO > > > ====== > > CRISP Team 8thTeleconference > Monday, January 5, 2015 > 1:00pm | UTC | 2 hr > > Join WebEx meeting > https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362… > > Meeting number: > 701 103 817 > Meeting password: > crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Accesscode: 701 103 817 > Global call-in numbers | > > https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012… > > Toll-free calling restrictions > > http://www.webex.com/pdf/tollfree_restrictions.pdf > > > Add this meeting to your calendar. > > Can't join the m Contact support. > > IMPORTANT NOTICE: Please note thatsession. > > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Draft Agenda for 7th CRISP Teleconference Re: CRISP 7th Teleconference Friday January 2nd at 13:00 UTC
by Nurani Nimpuno 02 Jan '15

02 Jan '15

FYI. Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Draft Agenda for 7th CRISP Teleconference Re: CRISP 7th Teleconference Friday January 2nd at 13:00 UTC > Date: 2 januari 2015 01:50:29 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > This is the draft agenda for the coming 7th CRISP Teleconference on Friday January 2nd at 13:00 UTC. > > The call is open to observers as usual - please see the invitation from the NRO Secretariat for details of joining the call. > > ---- > 1. Agenda Review > > 2. Actions Review > a. Mintutes from the last meeting > b. Recordings > c. Publish Issues status list on NRO Website > d. Issues raised (IRP,Contract,Review Team) > > 3. Feedback from the community > a. Other RIR community list > b. Status of continued topics > c. New topics raised > > 4. Next Steps > a. CRISP Team's general direction per issue > b. Volunteers to work on wording and communication > c. Updating the issues list > > 5. Next Meeting > > 6. AOB > ---- > > > Regards, > Izumi Okutani > > > On 2014/12/31 20:13, Maria Gayo wrote: >> >> >> >> This is an invitation to join the 7th CRISP Teleconference. >> >> Regards >> >> >> María Gayo >> (on behalf of the NRO Secretariat) >> >> Webex details below >> >> -------------- >> >> >> *CRISP Team 7th Teleconference* >> >> Friday, January 2, 2015 >> >> 1:00 pm | UTC | 2 hr >> >> *Join WebEx meeting* >> <https://ripencc.webex.com/ripencc/j.php?MTID=m0b67a2ead64ae579fec90d2cf3b63…> >> >> Meeting number: >> >> >> >> 700 449 709 >> >> 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: 700 449 709 >> >> Global call-in numbers >> <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012…> | >> Toll-free calling restrictions <http://www.webex.com/pdf/tollfree_restrictions.pdf> >> >> Add this meeting >> <https://ripencc.webex.com/ripencc/j.php?MTID=m29807507d0cdda74b855bdc6249d6…>to >> your calendar. >> >> Can't join the meeting? Contact support. <https://ripencc.webex.com/ripencc/mc> >> >> 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. >> >> >> >> >> >> >> >> -- >> Embedded Image >> *María Gayo* >> Coordinadora de Comunicaciones >> Communications Coordinator >> *# 4206* >> Embedded Image >> *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 <http://www.lacnic.net> >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer(a)nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [CRISP-TEAM] CRISP Team 7th Teleconference Friday January 2nd at 13:00 UTC
by Nurani Nimpuno 01 Jan '15

01 Jan '15

Dear colleagues, Please find details below about the 7th CRISP teleconference. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: Maria Gayo <mgayo(a)lacnic.net> > Date: 31 december 2014 12:17:43 CET > To: crisp(a)nro.net > Subject: [CRISP-TEAM] CRISP Team 7th Teleconference Friday January 2nd at 13:00 UTC > Reply-To: mgayo(a)lacnic.net > > > This is an invitation to join the 7th CRISP Teleconference. > > Regards > > > María Gayo > (on behalf of the NRO Secretariat) > > Webex details below > > -------------- > > > CRISP Team 7th Teleconference > Friday, January 2, 2015 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: > 700 449 709 > 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: 700 449 709 > 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 > _______________________________________________ > CRISP mailing list > CRISP(a)nro.net > https://www.nro.net/mailman/listinfo/crisp

1 0

Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published
by Nurani Nimpuno 01 Jan '15

01 Jan '15

FYI. Nurani Nimpuno Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > Subject: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published > Date: 29 december 2014 12:43:23 CET > To: ianaxfer(a)nro.net > > Dear Colleagues, > > > CRISP Team has published an editorial version of the Internet > numbers community's response to the Request For Proposals issued by the > IANA Stewardship Coordination Group (ICG): > > http://www.nro.net/crisp-proposal-first-draft-1-1 > > From the initial draft we published on 19th Dec [*], we have made > editorial changes only. No changes are made in contents of the proposal. > > [*] > https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf > > The editorial changes are intended to clarify our answers to RFP, by > re-ordering answers in the same order as questions listed in each > Section. Some small additions have been made to address points that had > not been answered in the earlier draft. Finally, there are some changes > made for stylistic reasons. > > The deadline of the comments to be submitted to <ianaxfer(a)nro.net> > mailing list remains the same: Monday 5th Jan 2015. > > Please let us know if you have any questions about version 1.1 of our > draft proposal, and we continue to welcome feedback from the community. > > > Best Regards, > Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) > > _______________________________________________ > ianaxfer mailing list > ianaxfer(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] NRO-NC role in Review Committee
by Hans Petter Holen 31 Dec '14

31 Dec '14

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 <apb(a)cequrux.com> To: ianaxfer(a)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(a)nro.net https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Fwd: [NRO-IANAXFER] CRISP 6th Teleconference Monday December 29th at 13:00 UTC + Agenda
by Nurani Nimpuno 29 Dec '14

29 Dec '14

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 <nurani(a)netnod.se>, http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden --------------------------------------------- Begin forwarded message: > From: Maria Gayo <mgayo(a)lacnic.net> > Subject: [NRO-IANAXFER] CRISP 6th Teleconference Monday December 29th at 13:00 UTC + Agenda > Date: 26 december 2014 20:16:19 CET > To: ianaxfer(a)nro.net > Reply-To: mgayo(a)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(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

First Draft, Seeking Feedback: Internet Numbers Community IANA Stewardship Proposal
by Andrei Robachevsky 22 Dec '14

22 Dec '14

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, <ianaxfer(a)nro.net>, 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 <ianaxfer(a)nro.net>. 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… RIPE NCC IANA stewardship information: https://www.ripe.net/iana-stewardship-transition

2 1

Fwd: CRISP 5th Teleconference Monday December 22nd at 13:00 UTC
by Nurani Nimpuno 22 Dec '14

22 Dec '14

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 <german(a)nro.net> > Date: 21 december 2014 12:44:15 CET > To: <ianaxfer(a)nro.net> > 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=m0348482bacaeff18e36634cd53cce… > > 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(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

Archives of the internal CRISP mailinglist are available online
by Andrei Robachevsky 19 Dec '14

19 Dec '14

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

1 0

Fwd: [NRO-IANAXFER] Update on Timeline Re: Timeline (Re: [Iana-transition] 1st CRISP Meeting Notes)
by Nurani Nimpuno 18 Dec '14

18 Dec '14

FYI. Nurani Begin forwarded message: > From: Izumi Okutani <izumi(a)nic.ad.jp> > 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(a)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 >>

1 0

Minutes session 1 and 2 Cooperation WG at RIPE69
by Maria Häll 18 Dec '14

18 Dec '14

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.

1 0

Fwd: Invitation CRISP Team 4th Teleconference Thursday 18th December 2014 13:00 UTC
by Chris Buckridge 18 Dec '14

18 Dec '14

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 <german(a)nro.net> > 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: <ianaxfer(a)nro.net> > > > 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(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

CRISP Team 3rd Teleconference Wed December 17th Webex Details
by Nurani Nimpuno 16 Dec '14

16 Dec '14

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 <german(a)nro.net> > Subject: [NRO-IANAXFER] CRISP Team 3rd Teleconference Wed December 17th Webex Details > Date: 11 december 2014 17:08:55 CET > To: <ianaxfer(a)nro.net> > > > 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(a)nro.net > https://www.nro.net/mailman/listinfo/ianaxfer

1 0

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 16 Dec '14

16 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