- cooperation-wg - mailman.ripe.net

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

15 Dec '14

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

1 0

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

11 Dec '14

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

5 4

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

11 Dec '14

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

1 1

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

11 Dec '14

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

3 3

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

11 Dec '14

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

1 0

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

08 Dec '14

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

1 0

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

02 Dec '14

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

1 0

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

02 Dec '14

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

1 0

IANA Stewardship Transition
by Jaap Akkerhuis 29 Nov '14

29 Nov '14

Announcement about "IANA Stewardship Transition Cross Community Working Group (CWG) on Naming Related Functions" . Chairs' Statement with progress update and route ahead: <https://www.icann.org/news/announcement-2014-11-28-en> jaap

1 0

The RIPE Consolidated RIR IANA Stewardship Proposal (CRISP) work
by Nurani Nimpuno 28 Nov '14

28 Nov '14

Dear colleagues, At RIPE 69, at the beginning of November 2014, the RIPE community selected three representatives (two community members and one RIPE NCC staff member) to participate in the Consolidated RIR IANA Stewardship Proposal (CRISP) team. The RIPE CRISP team members are: - Andrei Robachevsky (Internet Society) - Nurani Nimpuno (Netnod) - Paul Rendek (RIPE NCC staff) The CRISP team is tasked with preparing a common proposal on behalf of the global numbering community for stewardship of the IANA functions. This proposal is to be passed to the IANA Stewardship Coordination Group (ICG), which has asked that proposals from the three affected communities be formatted around a Request for Proposals (RFP) template produced by the ICG. The members of the CRISP team selected by the RIPE community will work with CRISP team representatives from the other regions to develop this RFP. Their work will be guided by the principles agreed by the RIPE community (see below) and they will ensure that the community remains informed as to the progress and direction of discussions in the CRISP team. Communication to the RIPE community will be via the RIPE Cooperation Working Group mailing list. The principles agreed by the RIPE community, as understood (and updated) by the RIPE CRISP team members, are: - The RIPE community asks its selected CRISP team representatives to work with the other RIRs to produce a common proposal for a legally binding agreement (such as a Service Level Agreement) between ICANN and the RIRs to replace the Internet number-related elements of the ICANN-NTIA agreement. - This proposal should meet the requirements of the Request For Proposals (RFP) produced by the IANA Stewardship Transition Coordination Group (ICG). - The proposal should bring the provisions of the agreement related to the services and service levels up-to-date with current requirements where necessary. - This work should be coordinated with the other users of the IANA function as much as practical, with the aim of producing a proposed arrangement that is compatible with the proposed arrangements of the other IANA users. - The RIPE community asks its CRISP team representatives to keep it informed about progress and content of the proposal. - The RIPE community asks the CRISP team to complete the proposal and to submit it to the ICG before 15 January 2015. The RIPE CRISP team have also identified what we see as an additional principle, not currently made explicit: - Changes to the policy-making structures or processes relating to the IANA registries are not within the scope of the IANA stewardship discussion. At this stage, we (as RIPE CRISP team members) would appreciate any feedback from the community on these principles. The timeline for the CRISP team’s work is very aggressive, and we plan to provide regular updates to this working group, both on the substance of the proposal being developed, the text under discussion and the CRISP team's timeline and processes (including information about public teleconferences). Best regards, Nurani Nimpuno on behalf of the RIPE CRISP team

2 1

RIPE NCC and EuroDIG: Open Call for Input [Deadline 31 December]
by Chris Buckridge 27 Nov '14

27 Nov '14

Dear colleagues, EuroDIG, the European Dialogue on Internet Governance, is an open forum that meets annually to discuss Internet governance issues of relevance to Internet stakeholders in Europe. EuroDIG 2015 will take place from 4-5 June 2015 in Sofia, Bulgaria. What issues do you think should be on the agenda? There is currently an open call for input on topics and issues to be considered in the EuroDIG 2015 programme: http://www.eurodig.org/get-involved/call-for-proposals/ This open call will close on 31 December 2014, and all input received will be considered shaping the agenda of the 2015 event. The planning process will include an opportunity for online community evaluation of the input received and an open planning meeting to take place in Sofia in January 2015. The RIPE NCC recently signed a Memorandum of Understanding to serve as a EuroDIG institutional partner for the next three years, contributing with other institutional partners to the event’s planning and coordination. The RIPE NCC’s goal in this role is to help ensure a strong Internet technical community presence in European Internet governance discussions, providing expert technical input and placing governance issues relevant to the technical community on the EuroDIG agenda. RIPE community members are invited to take an active role in contributing to EuroDIG and its planning process - even if you are not able to attend the event in June, this open call is an important opportunity to help shape the European Internet governance agenda. Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC

1 0

Proposed Charter for Enhancing ICANN Accountability Cross Community Working Group (CCWG)
by Athina Fragkouli 20 Nov '14

20 Nov '14

Dear colleagues, Following my presentation to the Cooperation Working Group last Thursday, 6 November, on the process to enhance ICANN accountability, the Enhancing ICANN Accountability Cross Community Working Group (CCWG) has now published a Draft Charter: https://community.icann.org/download/attachments/49359098/Enhancing%20ICANN… The Draft Charter includes, among other things, a problem statement, goals and objectives, scope, and proposed areas for work. It was developed by a Drafting Team made up of representatives from a range of ICANN Supporting Organizations (‭SO‬) and Advisory Committees (‭AC‬) : https://community.icann.org/display/acctcrosscomm/Drafting+Team+Membership Under the Draft Charter, the CCWG is expected to organise its activities into two Work Streams: Work Stream 1 is focused on mechanisms enhancing ‭ICANN‬ accountability that must be in place or committed to within the time frame of the ‭IANA‬ Stewardship Transition; and Work Stream 2 is focused on addressing accountability topics for which a timeline for developing solutions and full implementation may extend beyond the ‭IANA‬ Stewardship Transition. Each ‭ICANN‬ Supporting Organization (‭SO‬) and Advisory Committee (‭AC‬) will consider the proposed Draft Charter during their upcoming November meetings. Following the adoption of the charter, the relevant SOs and ACs will identify representatives to serve on the CCWG. In addition, a call for volunteers to join the CCWG will be launched, so that anyone interested in this effort may join and participate. The CCWG is expected to commence its deliberations in late November or early December. For your reference, here is the link to my presentation to the Cooperation Working Group last Thursday, 6 November: https://ripe69.ripe.net/archives/video/10069/ Best regards, Athina Fragkouli, RIPE NCC

2 2

ITU Plenipotentiary 2014: RIPE NCC Report
by Chris Buckridge 18 Nov '14

18 Nov '14

Dear colleagues, The International Telecommunication Union (ITU) Plenipotentiary 2014 took place over three weeks in Busan, South Korea from 20 October to 7 November. The RIPE NCC has published a report on the conference, detailing our engagement at the event, proposals of concern and an analysis of the conference outcomes: https://www.ripe.net/reports/pp-14 Best regards, Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

Change in the ICANN GAC
by Gordon Lennox 13 Nov '14

13 Nov '14

"In October 2014, the Chair of ICANN’s Governmental Advisory Committee (GAC), Heather Dryden of Canada, stood down after four years at the helm. She and incoming ICANN GAC Chair Thomas Schneider of Switzerland discuss the role, the past and the future, and governments’ role within ICANN." http://www.emilytaylor.eu/icann-gac-exclusive-change-at-top/

1 0

Workshop on evolution of Internet Governanace
by Gordon Lennox 12 Nov '14

12 Nov '14

Workshop on evolution of Internet Governance and US transition of IANA stewardship, 12 November, Brussels: agenda and audio call-in details You will find below the agenda as well as call-in details that you can share with colleagues and contacts who may be interested but are not able to join us in person. Agenda (timing only indicative) 1000 – Scene-setting 1. Introduction / scene-setter - EC’s Megan Richards and ICANN’s Jean-Jacques Sahel 2. Overview of the Internet Governance ecosystem & ICANN - presentations by: - Frederic Donck, Internet Society (ISOC) - Jean-Jacques Sahel, ICANN 3. Q&A 1040 - The IANA stewardship transition process 4. Presentation of the stewardship transition process – Jean-Jacques Sahel, ICANN - Discussants: - Michael Niebel, European Commission and member of the IANA Stewardship transition coordination group ICG) - Konstantinos Komaitis, ISOC 5. Q&A then break 1130 – Enhancing Accountability and Governance 6. Presentation of the accountability and governance review - Jean-Jacques Sahel, ICANN - Discussants: - Matthew Shears, CDT - Peter van Roste, CENTR 7. Q&A / discussion End 1245 with wrap-up by ICANN and DG CONNECT, then networking lunch. Conference dial-in details: An Adigo line is available for anyone to listen in to the discussion: from Belgium +32 78 480 286, Conference ID: 956544 ; for other countries, please visit:http://adigo.com/icann.

1 0

RIPE Community Selects CRISP Team Members
by Serge Radovcic 10 Nov '14

10 Nov '14

Dear colleagues, Following an open call for community volunteers, the RIPE Chair, Hans Peter Holen, has confirmed the appointment of two individuals from the RIPE community to the Consolidated RIR IANA Stewardship (CRISP) team. Nurani Nimpuno, Head of Outreach & Communications at Netnod, and Andrei Robachevsky, Technology Programme Manager at the Internet Society will join Paul Rendek, RIPE NCC Director of External Relations, as the three CRISP representatives from this service region. The CRISP team will develop a single, consolidated proposal on behalf of the Internet numbering community for the future stewardship of the IANA functions. This work will be based on the output of discussions in the five RIR communities. Each community will select two community members and one RIR staff member by 15 November to participate in the CRISP team. All of the CRISP team’s work will be done transparently, via a public mailing list: ianaxfer(a)nro.net. Subscription options and public archives of this list are available at: https://www.nro.net/mailman/listinfo/ianaxfer More information on the CRISP team is available at: https://www.nro.net/crisp-team Best regards, Serge Radovcic Chief Communications Officer RIPE NCC

1 0

Seeking RIPE Community Volunteers for CRISP Team
by Paul Rendek 06 Nov '14

06 Nov '14

Dear colleagues, We are seeking two qualified individuals to join the Consolidated RIR IANA Stewardship Proposal (CRISP) Team as voluntary representatives of the RIPE community. This team will be responsible for producing the Number Community proposal on the IANA stewardship transition for submission to the IANA Stewardship Transition Coordination Group (ICG) by 15 January 2015. For background and details of the CRISP Team, please see: https://www.nro.net/crisp-team Each RIR region will appoint three members to the CRISP Team: one RIR staff member and two community representatives. Volunteers for the two community representative positions should send their nomination to the Cooperation Working Group mailing list (<cooperation-wg(a)ripe.net>) by the close of the first session of the Cooperation Working Group on Thursday, 6 November at 12:30 UTC. Nominations should include your full name, affiliation, and a brief statement of qualifications and interest or a link to your CV or biography. The RIPE Chair, Hans Petter Holen, in consultation with the RIPE NCC Executive Board, will select two representatives, and will bring forward these names to the RIPE 69 Plenary session on Friday, 7 November, for endorsement by the community. The successful candidates will be contacted by email. For background on the IANA stewardship transition process, please see: https://ripe.net/iana-oversight-transition Best regards, Paul Rendek Director of External Relations RIPE NCC

4 3

Digital rights
by Gordon Lennox 05 Nov '14

05 Nov '14

EDRi is an organisation in Brussels that represents a number of European digital rights organisations. They publish a regular news-letter. It can be worthwhile subscribing if you are interested in what governments are doing in this area. Some of it can be quite surprising! The web-version of the latest edition of their news-letter is here. https://edri.org/edri-gram/12-21/ The contents include: • Hungary's Internet tax postponed but not yet abolished • CJEU: Embedding not a copyright infringement • Poland: New project on public institutions' surveillance practices • Finland: Web service to request verifying of secret registry data • The “Google tax” that is not a Google tax • Samaritans RADAR monitor tweets • FTDI: Is the law criminal? :-) Gordon

1 0

Surveillance
by Gordon Lennox 05 Nov '14

05 Nov '14

I have been talking to various people about an event last week in Brussels. It was called DemoSec and was the joint final event for three EU-funded projects. Details of the event can be found here: DemoSec: Democracy and Security http://www.jointfinalevent2014.eu Details of each of the three projects can be found here: IRISS: Increasing Resilience in Surveillance Societies http://irissproject.eu RESPECT: Rules, Expectations & Security through Privacy-Enhanced Convenient Technologies http://respectproject.eu SURVEILLE: Surveillance: Ethical Issues, Legal Limitation, and Efficiency http://www.surveille.eu The information available is very variable between the projects. But RESPECT alone received €3492687 funding. So a significant amount of work. SURVEILLE has though made available a number of reports. Their paper on a "Terrorism Prevention Scenario" and the related paper on NSA may be of particular interest. See: http://www.surveille.eu/index.php/research/publications/ :-) Gordon

1 0

Key Developments From ICANN 51
by Chris Buckridge 30 Oct '14

30 Oct '14

Dear colleagues, The 51st ICANN meeting was held in Los Angeles, USA, from 11-16 October 2014, with questions surrounding the IANA stewardship transition and the accountability of ICANN driving much of the agenda. More information about key developments from the ICANN 51 meeting is available at: https://www.ripe.net/internet-coordination/news/announcements/icann-51-cont… Regards, Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

Fwd: arin-announce IANA Stewardship Transition Proposal Survey and Mailing List
by Hans Petter Holen 28 Oct '14

28 Oct '14

Hi, This was circulated on the ARIN list earlier this month. It may be of interest to us to know the thoughts of ARIN community members. -------- Original Message -------- Subject: [arin-announce] IANA Stewardship Transition Proposal Survey and Mailing List Date: Mon, 13 Oct 2014 15:38:37 -0400 From: ARIN <info(a)arin.net> To: arin-announce(a)arin.net As a part of the Regional Internet Registry (RIR) system, the ARIN community has been called to contribute to the ongoing global multistakeholder discussion on the IANA Stewardship Transition. The feedback from the ARIN community will be part of the contribution provided by the Number Resource Organization (NRO) to the IANA Stewardship Transition Coordination Group (ICG) in response to their recent "Request for Proposals (RFP) for ?IANA? Stewardship Transition Proposal?. ???" https://www.icann.org/news/announcement-3-2014-09-03-en We would also like your opinion on number of specific points detailed in a short survey at: https://www.surveymonkey.com/s/IANA_stewardship This survey will be open from 13 October to 20 October 2014, and the results will be made available to the community on 24 October 2014. We have also created a public mailing list (iana-transition(a)arin.net) to facilitate open community discussion in the region regarding the IANA Stewardship Transition planning process. We encourage you to subscribe and participate in this dialog by visiting http://lists.arin.net/mailman/listinfo/iana-transition To learn more about this and other mailing lists hosted by ARIN, visit the Mailing List page: https://www.arin.net/participate/mailing_lists/ Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN)

2 1

Request for clarification of the process
by Richard Hill 22 Oct '14

22 Oct '14

I refer to the message at: http://www.ripe.net/ripe/mail/archives/cooperation-wg/2014-October/000620. html It says "The RIPE community asks the RIPE NCC to complete the [IANA transition] proposal and to submit it to the ICG before January 15th 2015." Does RIPE NCC refer to the staff of the RIR? That is, is the proposal going to be written by the staff and directly submitted to the ICG? Or is the proposal going to be submitted for discussion to this (or some other) mailing list? Please recall that the IANA transition process is supposed to involve the global multi-stakeholder community, and not just the RIPE community. Best, Richard

4 10

Initial Draft: RIPE Community IANA Stewardship Proposal
by Chris Buckridge 22 Oct '14

22 Oct '14

Dear colleagues, The RIPE NCC, working closely with the Cooperation Working Group Co-chairs and the RIPE Chair, has produced the following draft RIPE community proposal regarding the IANA stewardship. This text should not be regarded as final - it is intended to act as a basis for discussions in this working group over the coming weeks. There will also be a dedicated session at RIPE 69 in London on Thursday, 6 November, to discuss these issues. Remote participation will be available for those unable to be present. Best regards, Chris Buckridge, RIPE NCC RIPE Community IANA Stewardship Proposal [DRAFT] ———————————————————————— The RIPE community asks the RIPE NCC to work with the other RIRs to produce a common proposal for a legally binding agreement (such as a Service Level Agreement) between ICANN and the RIRs to replace the Internet number-related elements of the ICANN-NTIA agreement. This proposal should meet the requirements of the Request For Proposals (RFP) produced by the IANA Stewardship Transistion Coordination Group (ICG). The proposal should bring the provisions of the agreement related to the services and service levels up-to-date with current requirements where necessary. This work should be coordinated with the other users of the IANA function as much as practical, with the aim of producing a proposed arrangement that is compatible with the proposed arrangements of the other IANA users. The RIPE community asks the RIPE NCC and the other RIRs keep it informed about progress and content of the proposal. The RIPE community asks the RIPE NCC to complete the proposal and to submit it to the ICG before January 15th 2015.

2 2

Test
by Richard Hill 16 Oct '14

16 Oct '14

I seem not to have received some messages posted to this list, so I'm sending this as a test. Richard

1 0

RIPE NCC and CENTR Hold Joint Meeting With Governments
by Chris Buckridge 03 Oct '14

03 Oct '14

Dear colleagues, The RIPE NCC and CENTR, the European country code top-level domain (TLD) organisation, held a meeting on Wednesday, 1 October 2014, in Brussels, Belgium, for governments and regulators to discuss issues of relevance to both the RIPE and CENTR communities. The meeting was part of the CENTR General Assembly and was held adjacent to a meeting of the European Commission High Level Group on Internet Governance, attracting approximately 100 representatives from governments, industry and the Internet technical community. Dominating the agenda was a discussion of the Internet Assigned Numbers Authority (IANA) oversight transition process that is currently ongoing. Paul Rendek, RIPE NCC Director of External Relations, participated in a panel with Nominet’s Martin Boyle and Afnic’s Mathieu Weill, chaired by Peter Vergote, Chairman of the CENTR Board of Directors. This panel addressed the discussion process currently underway in the RIPE and TLD communities regarding both the IANA stewardship and ICANN accountability. The RIPE NCC presentation described the relationship between the Regional Internet Registries (RIRs) and IANA, the model of regional Internet number policy development, efforts to document the RIRs’ accountability to their stakeholders, the discussion of IANA stewardship in the RIPE community, and some of the key principles that have emerged from that discussion. These principles include a preference for minimal operational change and to build on existing structures and processes to formalise the RIR communities’ role as stewards of global Internet number registration. The panel was followed by vibrant discussion, with many governments and other attendees contributing. Many expressed concern about the timeline leading up to the expiration of the current contract in September 2015, and the challenge of reaching an agreement on a proposal for future IANA oversight upon which all affected communities can agree. RIPE NCC Chief Scientist Daniel Karrenberg was among those who stressed the importance of early and effective communication between all parties to assure the best chance of a widely accepted outcome to the process. Several governments also suggested the possibility of a neutral third-party assuming the oversight role currently held by the National Telecommunications and Information Administration (NTIA). Others noted that such an arrangement would be contrary to preferences already expressed in the RIR and Internet Engineering Task Force (IETF) communities. The meeting also included discussion of upcoming Internet governance events, particularly the International Telecommunications Union (ITU) Plenipotentiary 2014 (PP14). Chris Buckridge presented on the RIPE NCC's priorities going into this event, and the focus on providing expert technical advice to ITU Member States, particularly when discussions touch on issues such as IP address registration, allocation and policy-making. Presentation slides delivered by the RIPE NCC are available online: https://www.ripe.net/ripe/meetings/roundtable/october-2014/presentations Additional information on the IANA oversight transition is available at: https://www.ripe.net/iana-oversight-transition/ The next RIPE NCC Roundtable Meeting for Governments and Regulators will be held in early 2015, with details to be announced closer to the event itself. Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC

1 0

Principles for a RIPE Proposal on IANA Oversight
by Chris Buckridge 24 Sep '14

24 Sep '14

Dear colleagues, The RIPE NCC is working closely with the Cooperation Working Group Co-chairs and members of the RIPE community to draft a proposal on the future oversight of the IANA functions. To assist in the process, we developed a straightforward set of principles based primarily on the discussions in this working group at RIPE 68 and on the working group’s mailing list. Feedback from the working group on the three areas listed below, on whether to express agreement or otherwise, and on any other related issues or questions is a vital part of this process. We would appreciate this feedback by the end of September. At the beginning of October, we plan to present a rough draft proposal to the working group for further discussion ahead of the RIPE 69 Meeting in London. Further background information, including a detailed overview of the NTIA IANA functions contract and a timeline for the five RIR community discussion processes, was recently published on the NRO website: https://www.nro.net/iana-oversight Best regards, Chris Buckridge RIPE NCC -------------- Background The Regional Internet Registry (RIR) communities have successful, long-established processes for making Internet number resource policy at the global and regional levels. These processes are defined as being open to all interested parties, transparent in their processes and operations, and driven by the community themselves in a “bottom-up” fashion via consensus-based decision-making processes. These processes operate at the regional level to create policies that address regional needs and interests. More rarely, they serve to create global policies regarding the top level of the Internet number registration hierarchy. These global policies are implemented by the IANA operator, a role currently fulfilled by ICANN. RIR policy development processes pre-date ICANN and the current NTIA IANA functions contract. The NTIA plays no explicit role in making or directing policy for the operation of those IANA functions relating to Internet number resources. The current processes and structures have resulted in excellent operation of the IANA functions relating to Internet number administration by ICANN, under policy direction from the RIR communities. 1. The following are priorities for the RIPE community: - There should be minimal operational change. The current processes for IANA operation and related policy-making are effective and allow for the participation of all interested parties. - Any new oversight mechanism should incorporate and build on the existing RIR community policy-making processes. - The RIR communities are ultimately accountable for the management of those IANA functions relating to management of the global Internet number resource pools, and this should be reflected in any new oversight mechanisms defined in a global proposal to NTIA. 2. A model for IANA oversight endorsed by the RIPE community should include the following elements: - ICANN has historically managed operation of the IANA functions well, and should continue to do so at this time. - The IANA functions operator must be answerable and accountable to the communities that it serves. The number resource community is represented in such accountability processes by the membership-based RIR organisations. - Funding arrangements to cover the staff, equipment and other operational costs associated with operation of the IANA functions should be transparent and stable. - Efforts should be made to maintain the IANA functions as a “bundle”, managed by a single operator. - This does not necessarily imply a single, central point of oversight authority. Any proposed oversight mechanism should reflect the legitimate authority of different communities for specific functions as they relate to number resources, domain names and protocol parameters. 3. RIPE community input to the IANA Stewardship Transition Coordination Group (ICG), which is responsible for developing a global proposal to NTIA, will be developed according to the following process: - Discussion in the RIPE community is centralised in the RIPE Cooperation Working Group. - The RIPE community discussion will aim to produce an output document by 1 December 2014. - The RIPE Cooperation Working Group Chairs will be responsible for assessing community consensus on this output document. - This RIPE output document will be sent to the Number Resource Organization Executive Council (made up of the five RIR CEOs), who will compile a single NRO input to the ICG. - A representative of the NRO Number Council will confirm that text compiled by the NRO EC accurately reflects the output of the five RIR community discussions. - The NRO proposal will be shared with the five RIR communities ahead of submission to the ICG. - Any global proposal produced by the ICG will be conveyed back to the RIPE community via the RIPE Cooperation Working Group to allow for discussion of any objections or concerns.

9 40

IGF community impressions of the IGF
by Chris Buckridge 24 Sep '14

24 Sep '14

Dear colleagues, The RIPE NCC funded the participation of several RIPE community members at the recent Internet Governance Forum in Istanbul. We have now published an article on RIPE Labs, compiling brief interviews with three of those RIPE community participants on their experiences and thoughts on the event: https://labs.ripe.net/Members/chrisb/ripe-community-impressions-of-igf-2014 Best regards, Chris Buckridge, RIPE NCC

1 0

Call for nominations: IGF MAG
by Chris Buckridge 17 Sep '14

17 Sep '14

Dear colleagues, Please note the email forwarded below - volunteers from the technical community are being sought to participate in the Internet Governance Forum (IGF) Multistakeholder Advisory Group (MAG). The MAG develops the programme and schedule of the IGF, and includes 55 members from governments, the private sector, civil society, and the academic and technical communities. More information about the MAG is available at: http://www.intgovforum.org/cms/magabout Best regards, Chris Buckridge, RIPE NCC > From: Elizabeth Oluoch <oluoch(a)isoc.org> > Date: Tuesday, September 16, 2014 5:58 AM > > > Dear All, > > Under-Secretary-General of UNDESA, Mr. Wu Hongbo, has issued a public request for nominations for the 2015 Multistakeholder Advisory Group, which will advise the Secretary-General of the United Nations on the programme and schedule of the IGF 2015 meeting. The aim is to rotate one third of MAG members. > > The Internet Society (ISOC) is coordinating a process leading to recommendations of representatives of the Internet technical community for the renewal of the MAG. > > Individuals interested in being suggested by the NomCom set up for this purpose are invited to read more about the process and to fill in a submission template by 1 October: http://www.internetcollaboration.org/wp-content/uploads/sites/12/2014/09/20… > > Any questions or requests for additional information can be sent to: information.itcg(a)gmail.com. > > Useful links: > IGF website: http://www.intgovforum.org/cms/ > About the MAG:: http://www.intgovforum.org/cms/magabout > > Thank you and best regards, > > Elizabeth Oluoch > Public Policy Coordinator > Internet Society

1 0

Key elements of the transition of IANA stewardship
by Richard Hill 10 Sep '14

10 Sep '14

NOTE: this message has been cross-posted individually to the RIR mailing lists dealing with this issue. Here are some things that appear to me to be key elements for the transition of the IANA stewardship. At present, the "RIRs are an interested and affected party of the IANA contract because IANA holds ultimate responsibility for allocated and unallocated IPv4, IPv6 and Autonomous System Number address spaces. IANA delegates IP and ASN address blocks to the RIRs on a needs-based approach according to global policies agreed by all the Regional Internet Registries (RIRs). The global policy development process is described in the ICANN Address Supporting Organization (ASO) memorandum of understanding. ICANN and the Number Resource Organization (NRO) signed this MoU in 2004. The NRO is an unincorporated organization created in 2003 as a coordination mechanism for the RIRs. The NRO fulfills the role, responsibilities and functions of the ASO as defined within the ICANN Bylaws." (This is a citation from the document at: https://blog.apnic.net/wp-content/uploads/2014/09/NRO-RELATIONSHIP-IANA.pdf ) The Mou between ICANN and the NRO is at: https://aso.icann.org/about-the-aso/aso-memorandum-of-understanding/ That MoU specifies how ICANN's ASO is constituted and provides that "Under this agreement the ICANN Board will ratify proposed global policies in accordance with the Global Policy Development Process, using review procedures as determined by ICANN." Thus, the ICANN Board has ultimate responsibility for IP address policies. This is consistent with the ICANN Bylaws. Up to now, under the IANA functions contract with the NTIA, ICANN was clearly bound to defer to the RIRs for what concerns IP address policies. If there is no contract between ICANN and some external entity, then ICANN would have unrestricted ultimate authority over IP addresses. That is, the ICANN Board could, if it considered it appropriate, override RIR policies. This puts too much power in the ICANN Board which, under ICANN's current structure, is not accountable to any external entity. It would appear desirable that the IANA functions should be contracted for by the served communities, that is, by the NRO/RIRs for what concerns IP addresses. And indeed the draft proposal presented by APNIC on 8 September 2014 envisages a Service Level Agreement between ICANN and NRO and also a non-binding Affirmation of Committments between ICANN and NRO. These proposals are found in the slide show contained in the web page at: http://blog.apnic.net/2014/09/08/iana-session-apnic-38-a-discussion-propos al/ But a non-binding Affirmation of Committments, coupled with a Service Level Agreement, are not the equivalent of a contract for the IANA functions. Thus, it would appear more appropriate to adopt the same approach that has been adopted by the IETF regarding protocol parameters, namely a Memorandum of Understanding (which appears to be a contract) between the NRO and ICANN for the IP addresses. The Memorandum of Understanding between ICANN and the IETF is at: https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-e n and http://tools.ietf.org/html/rfc2860 That text could easily be modified to refer to NRO and IP addresses instead of IETF and protocol parameters. However, item 4 of the text should be modified so that it reads as follows: "4. Agreed technical work items. ICANN agrees, notwithstanding any provisions in its Bylaws or other corporate documents that might be construed differently, that during the term of this MOU it shall cause IANA to comply ..." In addition, consideration should be given to adding a choice of law clause and a dispute resolution clause, presumably referring to arbitration rather than to national courts. There was extensive discussion (but no agreement) on the IANA Transition mailing list regarding whether or not the fact that a US court could, in theory, order ICANN/IANA to do something contrary to agreed community policies is an issue and, if so, whether anything should be proposed to deal with that issue, such as proposing that the entity that performs the IANA function should have immunity of jurisdiction, or that the entity should have redundant sites in more than one jurisdiction. If there is support for dealing with that issue, then some text could be added. Finally, and in addition to the above, article I.1 of the ICANN Bylaws should be modified to make it clear that it is the NRO that has the overall responsibility for the coordination and allocation and assignment of IP addresses. That change is needed because, at present, article I.1 of the ICANN Bylaws implies that ICANN has the overall responsibility for the coordination and allocation and assignment of IP addresses. Best, Richard

1 0

RIPE NCC Report on IGF 2014
by Chris Buckridge 05 Sep '14

05 Sep '14

Dear colleagues, The ninth annual Internet Governance Forum (IGF) concluded on Friday, 5 September, in Istanbul, Turkey. Over the course of the week, RIPE NCC staff and RIPE community members contributed to many of the workshops and main sessions. These sessions looked at topics like the impact of carrier-grade NAT technology on users and policymakers, the IANA oversight transition process, cybersecurity and capacity building. You can find more information about the week’s discussions, and the RIPE NCC’s involvement, on the RIPE NCC website: https://www.ripe.net/internet-coordination/news/ripe-ncc-report-on-igf-2014 Best regards, Chris Buckridge Senior External Relations Officer RIPE NCC

1 0

Update on IANA Oversight Discussions: ICG Meeting and IETF 90
by Chris Buckridge 30 Jul '14

30 Jul '14

Dear colleagues, In recent weeks, two significant community discussions regarding the transition of oversight of the IANA functions have taken place. The following summaries are provided as feedback to the RIPE community - an online version of these summaries, containing links to more detailed reports and information, is available at: https://www.ripe.net/internet-coordination/news/industry-developments/updat… Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC ——— First Meeting of the ICG The IANA Stewardship Transition Coordination Group (ICG) held its first meeting in London on 17-18 July 2014. This group has been established to coordinate input from the various relevant communities and IANA stakeholders, moving towards development of a global transition plan. Discussions and outcomes of the meeting are documented on the ICANN website. Adiel Akplogan and Paul Wilson, the CEOs of AFRINIC and APNIC respectively, took part in the meeting as representatives of the Number Resource Organization (NRO), and Hartmut Glaser, NRO Number Council member from the LACNIC region, represented the Address Supporting Organization (ASO). In addition, Daniel Karrenberg, RIPE NCC Chief Scientist, participated as one of two representatives of the Root Server System Advisory Committee (RSSAC). Key points from this meeting: • ICG members strongly asserted the group’s independence from ICANN. • The constructive atmosphere in the meeting resulted in the successful definition of a draft charter [PDF] and organisational principles for ICG. • The draft charter acknowledges that parts of the proposal will be developed in parallel across three main pillars (names, numbers and protocol parameters), coordinated by the respective operational communities. • The draft charter also makes it clear that the ICG does not expect to create substantive content in the proposals itself. Should serious further work be needed on the proposals, the ICG expects to send them back to the respective communities to do that work. • The group agreed to the request from the ICANN Government Advisory Committee (GAC) for five seats (rather than the proposed two). • The ICG recognised that there is a very tight schedule for developing a global proposal to the NTIA for transition of IANA oversight, and called on the various communities to produce input to a global proposal by the end of 2014. • There were around 100 remote observers for both days of the meeting. • The next meeting of the ICG is being planned for 6 September 2014 in Istanbul, Turkey. IETF 90 IANAPLAN BoF Session On 24 July 2014, during the Internet Engineering Task Force (IETF) meeting in Toronto, a dedicated Birds-of-a-Feather (BoF) session was held to discuss the IANA oversight transition. Approximately 150 people participated on-site, with more participating remotely. The session was chaired by Andrew Sullivan and Marc Blanchet. Session materials, including minutes and presentations, are available from the IETF website. Key points from this session: • Alissa Cooper reported on the first meeting of the ICG, and noted that the IETF community will take the lead in drafting a proposal regarding the protocol parameters. • Participants strongly supported the notion that the current arrangements (both contractual and operational) should not change significantly as a result of the transition process. • It was agreed that there should be reviews to ensure that: • Current procedures and relationships are sufficiently documented • The transition of oversight will not require significant changes of the current arrangements • In terms of IETF process, there was agreement that, while the Internet Architecture Board (IAB) should take a leading role, there should be a dedicated Working Group formed to act as sounding board and confirm rough consensus on the proposed transitioning plans. This working group could act as a focal point for other stakeholders to relay input back to the IETF.

2 1

IANA Stewardship Coordination Group Meeting
by Chris Buckridge 17 Jul '14

17 Jul '14

Dear colleagues, As noted previously, a Coordination Group has been formed to facilitate development of a global proposal to the NTIA for its transition out of the IANA oversight role. This Coordination Group meets for the first time today and tomorrow (17-18 July) in London: https://www.icann.org/news/announcement-2014-07-16-en Please note that a Virtual Meeting Room has been set up to allow the community to follow the meeting remotely: https://icann.adobeconnect.com/coordinationgroup/ An agenda for the meeting is available here: https://www.icann.org/en/system/files/files/agenda-stewardship-coordination… Best regards, Chris Buckridge, RIPE NCC

1 0

ICANN 50: Talking IANA and Accountability
by Chris Buckridge 01 Jul '14

01 Jul '14

Dear colleagues, The RIPE NCC has published a brief summary of discussions at last week’s ICANN 50 meeting on issues including the IANA oversight transition and ICANN accountability. The news item also includes links to the transcripts and audio archives of these sessions: https://www.ripe.net/internet-coordination/news/industry-developments/icann… Best regards, Chris Buckridge, RIPE NCC

2 1

Updated IANA Oversight Transition Process
by Chris Buckridge 16 Jun '14

16 Jun '14

Dear colleagues, Following a public comment period during which more than 50 submissions were received, ICANN has posted an updated description of the “Process to Develop the Proposal and Next Steps” in relation to the transition of the NTIA’s stewardship of the IANA functions: https://www.icann.org/news/announcement-2014-06-06-en The page details all of the changes made to the initial draft, which was published in April. A couple of key points: - The title "Coordination Group” has replaced the original "Steering Group" - The number of participants has increased from 22 participants to 25, including the addition of numerous stakeholder groups and an IANA expert liaison - The number of representatives from the Address Supporting Organization (ASO) has decreased from two to one - Representatives are to be selected by their communities, not by the ICANN Board and Government Advisory Committee (GAC) - Coordination Group members are to be announced by 2 July (but preferably before or during the ICANN 50 meeting, which runs from 22-26 June), with an expected first public meeting to be held in mid-July The number of Internet number resource community representatives on the Coordination Group totals three - two from the Number Resource Organization (NRO), and one from the Address Supporting Organization (ASO). More information on the RIPE community contribution to the development of a proposal regarding transition of the NTIA’s oversight of IANA, including summaries of discussions at recent RIPE community events, is available at: https://ripe.net/iana-oversight-transition Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC

1 0

Open Call to join IGF Best Practices Forums Preparatory Process
by Filiz Yilmaz 12 Jun '14

12 Jun '14

Dear all, Please note this call: http://www.intgovforum.org/cms/open-call-to-join-igf-best-practices-forums-… Kind regards Filiz

1 0

Minutes of the Coop-WG meeting during RIPE 68 in Warsaw - Updated
by Alain Van Gaever 11 Jun '14

11 Jun '14

Dear All, Following modifications proposed by Jim and Daniel, please find below the updated minutes of the Coop-WG meeting in Warsaw In case you have any further comments/updates please let us know Alain ------- Beginning of Minutes ------- Cooperation Working Group Draft Agenda Thursday, 15 May, 11:00 – 12:30 A. Administrative Matters The co-chairs opened the meeting. New co-chairs Meredith Whittaker and Alain Van Gaever introduced themselves and briefly outlined their hopes for the working group, specifically ensuring that the content is relevant and of practical use to the RIPE community. The minutes from RIPE 67 were approved, as was the agenda for RIPE 68. B. Content Blocking • B1. A Technical Overview of Content Blocking Methods – Pier Carlo Chiodi, Olaf Kolkman Olaf Kolkman gave an overview of the work done by Pier Carlo Chiodi on content blocking on the Internet and other work in the same area. Outlining a number of strategies employed by those wishing to block content, he noted that blocking is done most effectively at the end-point (or origin of the content), and that blocking in the network involves a variety of trade-offs. Lars-Johan Liman noted that even “legitimate” blocking has collateral damage, and pointed to the example of the hotel network, where the interception of traffic prevents the use of DNSSEC. He suggested that in such situations it is best if the effects of the blocking are stated upfront for users. Andrei Robachevsky recalled a paper produced by ISOC (prepared around the time of the SOCA/PIPA/ACTA legislative proposals), and noted that security and hidden costs are all important, and public policy makers need to be made aware of these negative impacts. Olaf pointed out that users will do whatever they can to get to blocked content, and that this can also have potential negative effects (including a greater viral footprint or exposing backdoors to computer systems). Alexander Isavnin asked participants in the room who thought their countries were doing blocking, and whether they thought it was being abused. Richard Barnes noted that these issues reinforce the importance of an end-to-end strategy, and agreed that the hotel network is a good example of how blocking can break important security elements like DNSSEC. Jim Reid noted that blocking access to specific content can mean that broader services are blocked. He had advised on a case where one of the questions asked was "what else would be affected if we prevented port 80 access for this particular domain?”. The only person who could provide a definitive answer would be the administrator of the web server at that IP address and they would be unlikely to cooperate with anyone intending to blocking traffic for that address. • B2. Telex: A Proposal For Circumventing Censorship in the Network – Eric Wustrow Eric Wustrow outlined the Telex project, which has been developed to circumvent content blocking measures. The system provides a means of connecting users to blocked content via a mechanism that is invisible to the censoring technology. He encouraged ISPs to contribute to the work with advice and prototype deployment assistance. Robert Kisteleki noted that PGP key distribution may be a bottleneck in the Telex system. Eric noted that the paper discusses some of these issues, including preventing censors from distributing “bad” public keys. He suggested that having a central Telex entity that is known and trusted will be important to mitigate these risks. He also noted that getting information into areas subjected to censorship is often less difficult than might be supposed. • B3. Web Censorship Circumvention: Challenges and Opportunities – Walid Al-Saqaf Walid Al-Saqaf outlined his project to map URL filtering via crowdsourcing, which is developing longitudinal data, while allowing contributing users to access blocked websites via his own servers. He presented a range of data and analysis obtained from this work, including content blocking methods and strategies. He noted the need to make people more aware of the range of circumvention tools and solutions available, and that speed, security and anonymity are all important to users. He also described his plans for the future, including open-sourcing his own project and cooperating with similar projects. Andrei Robachevsky asked whether the project looked at which means of blocking were most common. Walid stated that he has done some analysis of this, using the packet headers - the more data he can get, the better this analysis will be. Meredith Whittaker noted that the Open Observatory of Network Interference (OONI) project, coordinated by the Tor team, is also doing work in this area and is generating public data. Alexander Isavnin suggested that a RIPE task force might be a useful vehicle for RIPE community members interested in this issue. Walid agreed that the technical community, and particularly its relationship to civil society actors in this space, needs to be further explored and understood. C. IANA Transition Chris Buckridge and Paul Rendek of the RIPE NCC presented background information on the U.S. Government’s announcement of its intention to transition out of its IANA functions oversight role. They noted that any proposal for a future model of IANA administration needs to come from a global, multi-stakeholder development process, and that RIPE and the RIPE NCC are key IANA stakeholders. They suggested that the RIPE community’s discussion of these issues should be centred around the Cooperation Working Group, with the RIPE NCC assisting in facilitating input to that process from regional events and voices. Rob Blokzijl warned that any process involving ICANN will necessarily be complicated and political. On a technical point, he noted that future RIPE NCC presentations on this subject should include the RIPE NCC’s reverse DNS interactions with IANA, which may be more regular than the number resource requests already noted. He further noted that the RIPE NCC’s direct interactions with the NTIA itself were non-existent, and stressed that the processes developed by RIPE and the other RIR communities already met the requirements laid out by the NTIA as necessary for oversight of the IANA functions. Danniel Karrenberg recalled that this is not the first time this discussion has taken place, and that the RIPE community has historically taken an active part in the discussion around the formation of ICANN and the organisation and delivery of IANA services. He stressed the legitimacy and credibility of the RIR community processes in policy-making and argued against over-complicating the situation. He also noted that the IANA is three distinct groups of functions (number resources, the DNS root zone and protocol parameters), and the RIPE community discussions should focus primarily on the number resource functions; if difficulties in defining governance processes for the DNS root zone threaten to derail the oversight transition process, the community should be explicitly prepared to propose unbundling those functions and taking oversight of the numbering functions. Malcolm Hutty disagreed with the perception that NTIA oversight was not important, and stressed that this oversight has protected the policy-making relationship with ICANN itself. He noted that policy regarding the DNS is determined by the ICANN community and imposed on registrars, meaning that users essentially have to submit to ICANN policies. RIPE and the RIR communities determine their own policies with regard to Internet number management, but it may be conceivable that ICANN would decide it wants to set these policies in future and impose them on the RIPE community. He argued that a credible external oversight function must be retained to prevent this. Nurani Nimpuno argued that the RIR communities should take ownership of this issue, as custodians of the Internet number resources, and that the community members should be contributing to the broader discussion, while maintaining a focus on the numbering functions. She also stressed that the communities should be pro-active in defining terms like “multi-stakeholder” and “openness” which appear in the NTIA requirements. Jim Reid agreed with Malcolm Hutty on the importance of preventing ICANN mission-creep, and on the need to tightly define the relationship between the IANA operator and the RIR communities. He also warned that achieving consensus on a community proposal may be difficult, and suggested that there should be a fallback position to allow for RIPE and the RIPE NCC to make a meaningful contribution to the global discussion. Jari Arkko noted the evolution that has occurred in how the IETF and IAB manage oversight of the protocol parameters and their relationship to IANA. He agreed that the RIPE community needs to take ownership of this and take charge of what needs to change or not change. Olaf Kolkman, also an active participant in the IETF, noted the efforts in the IETF to align on a principle-based approach, with the most important principle being that the IETF controls its own destiny. Ensuring that people are empowered to participate in these discussions will help the debate going forward, and the community needs to provide guidance - developing a set of principles may be a good first step. Olaf suggested RFC 6220 as a good starting point. Salam Yamout provided some perspective from the government side, particularly in the Arab world - notably the perception that the United States has control of the Internet, and governments’ strong focus on DNS-related issues. She noted that governments concerns centre primarily around ICANN. Phil Rushton urged the community to be aware of events in other forums, including the UN, WSIS and the ITU - while there is not the need for everyone to be directly involved, we need to be aware of what governments are thinking and the where they still need to be convinced by the RIR communities. Daniel Karrenberg argued that the community does not need another level of oversight for protection, and noted that the RIR communities already have solid agreements in place with ICANN, which ICANN cannot unilaterally change. He stressed the importance (and his optimism) of achieving community consensus on a proposal. He suggested that the RIPE community should avoid being drawn into the discussions about governance and oversight of DNS root zone management and stick to its purview of Internet number resources. Paul Wilson noted that the IANA functions comprise three quite different areas (numbers, protocol parameters and DNS), and that only one of these (the DNS) is controversial - the IAB has stated its readiness to take responsibility for the protocol parameters, and the RIR communities should also, in the very near future, be ready to make such a statement regarding the number functions. He and Adiel Akplogan agreed that strengthening the RIR processes, ensuring that they are consistent, clear, accessible and well documented, is vital. Sandy Murphy warned that the outcome of this process may impact our current model of Internet governance, and stressed the need for the RIR communities to have their voice heard. She also asked about the ICANN consultation timeline, specifically the call for comments on its proposed process, and whether this process is now set. Paul Rendek noted that there is expected to be more information on ICANN’s planning in time of the ICANN 50 Meeting, which takes place in London in June. Chris Buckridge also noted that all relevant information, including links to the relevant ICANN web, is posted on the ripe.net website. D. Interconnection • D1. The Internet, the Internets, and Splinternets – Peter Koch Peter Koch discussed the proposals coming from Germany for establishing a separate “German” Internet. Randy Bush noted the experience of the Saudi industry, after the regulator decided that no traffic between two Saudi users should leave the country, and pointed out that IXPs are a key element facilitating this. There was a question as to whether the German-only email system used the DNS (which would generate its own cross-border traffic). Peter noted that the one he mentioned uses special domains, but DNS leakage was of less concern than the actual content of the messages. Alain Van Gaever asked about the rate of take-up. Peter didn’t have figures to hand, but noted that there are incentives, it is early in the deployment, and the operators are targeting users of existing email services. Brian Nisbet said that while he can see what’s being attempted, it never succeeds and generally breaks things that the users want to do. Peter stressed that walking away from the discussion probably isn’t the right strategy, and that users often learn what they want from marketing campaigns. Expanding on the question of what users want, Meredith Whittaker noted that users want security, and the technical community needs to be a public voice stating that this is not the way to achieve that. Marco Davids noted an initative in the Netherlands using a closed user group in BGP - this doesn't combat traffic monitoring, but rather helps mitigate DDOS attacks, and if users (such as banks) are under attack the group can be closed to users outside the Netherlands. Olaf Kolkman asked whether any EU research funding had been channeled to this, and whether the project could lead to some sort of European standardisation. Peter noted that the work is based on IETF standards. Jean Jacque Sahel noted that the European Commission has publicly said that this is all a very bad idea. Jaap Akkerhuis recalled a proposal from Italy to establish a trusted network for digital mail. Olaf Kolkman and Peter Koch, summarising some of the discussion’s key points, suggested that we are moving intelligence to the core of the network, and the core is represented by big players. The technical community cannot just dismiss these initiatives - there are some laudable goals behind them, and we need to engage in the discussion. • D2. Interconnection: Russia, the EU, and Internet Cooperation and Governance – Igor Milashevskiy Igor Milashevskiy, representing the Russian government in its first RIPE Meeting, shared some perspectives on that government’s view of the Internet and related public policy. The Russian government sees the Internet as a driver of development, with the Russian Internet market the biggest in Europe - 68 million users, more than 56 million people use Internet every day, including a significant percentage outside big cities. The Russian language is also the second largest in Internet, there are slightly fewer than five million .ru domains and more than 800,000 .рф domains. Speaking from personal perspective, he noted that the RIPE NCC is a reference organisation in the Internet space, and the target is to restore trust and confidence to the Internet environment, and develop international tools for preventing improper use of the Internet. Ho noted that the main actor in the Intenet is the user, and if those users have certain rights in the offline world - access to information, privacy, secrecy of communication and freedom of opinion - we have to protect those rights online. The process to do this has just begun, and the Russian government believes there are no rights without duties, no freedom without responsibility. He also suggested that the role of governments in Internet governance needs to be recognised. NETmundial was a good and innovative attempt to include all stakeholders, but the outcome document doesn’t reflect all the contributions. Ciprian Nica, participating remotely, asked how and who should define the proper purposes of using the Internet. Igor explained that the Internet is a universal tool, and can be used for a wide range of purposes, but that its primary purpose should be to make users’ lives richer. Desiree Milosevich asked if there could be some elaboration on the Russian government’s issues with the NETmundial statement. Igor noted that this is in the public record of the Russian statements. Paul Rendek extended his thanks to Igor and the Russian government for their increased willingness to engage with the RIPE community and RIPE NCC, and welcomed Igor's attendance at the RIPE Meeting. E. Making the Internet a Little Bit Safer Cryptographically - Randy Bush Randy Bush discussed the development of an open public architecture for hardware security modules. The goal is a design (not a product) that is scalable, composable and assured. He stressed that the project needs people to audit the code. Aaron Kaplan asked where to get a development board. Randy noted that the boards are available for 170 USD. Aaron also noted that it would be a good idea to have the testing procedure online and publicly available. Eric Wuster agreed that this is good work and asked why go the FPGA route rather than using a small embedded chip. Randy noted that some of the applications need speed, particularly some of the encryption stuff. Regarding chips though, Randy noted that the FPGA Verilog was first done in Python, meaning there is a Python version and a Verilog version. Eric also asked about how the project is sourcing hardware random number generators. Randy replied that they are currently investigating this issue. F. Policy Radar • F1. RIPE NCC Updates, including NETmundial and IGF Developments – Chris Buckridge Chris Buckridge gave an update on the wide range of Internet governance events taking place in the coming months, including the ITU Plenipotentiary 2014 that is scheduled to take place in October. He highlighted the links between many of these events, particularly in terms of broader strategies. He noted suggestions from earlier sessions that the RIPE NCC provide more targeted information for the community, and reported that the RIPE NCC is investigating the best method for doing this. Phil Rushton noted that the technical community can have significant impact on events at the Plenipotentiary via their input to Member State delegations. He also noted that while NETmundial produced a good outcome for the multi-stakeholder model, other forums, such as the CSTD Working Group on Enhanced Cooperation, saw much less support for multi-stakeholder processes and governance. • F2. Co-chair Updates and Working Group Initiatives Meredith Whittaker closed the session by reiterating the goals of co-chairs, particularly the need to engage people who are affected by Internet governance and public policy issues, but don't currently take an active interest. She noted options such as producing white papers, using RIPE Meeting time for more workshop-style events, and other ideas for the working group to serve as a RIPE community “brains trust” for those involved in public policy discussions. Nurani Nimpuno noted her support for the co-chairs’ approach and stressed the need to bring discussions back to specific issues and make the topics practical for RIPE community participants. The co-chairs closed the meeting. --------------------- End of Minutes ---------------------------------

1 0

Minutes of the Coop-WG meeting during RIPE 68 in Warsaw - Part 2
by Alain Van Gaever 10 Jun '14

10 Jun '14

Dear all, The text in my mail yesterday was the summary of the IANA discussion - the full minutes of the working groups session are now below. My apologies for the confusion! Alain > > ------- Beginning of Minutes ------- > > Cooperation Working Group Draft Agenda > > Thursday, 15 May, 11:00 – 12:30 > > A. Administrative Matters > > The co-chairs opened the meeting. New co-chairs Meredith Whittaker and > Alain Van Gaever introduced themselves and briefly outlined their hopes for > the working group, specifically ensuring that the content is relevant and > of practical use to the RIPE community. > > The minutes from RIPE 67 were approved, as was the agenda for RIPE 68. > > > B. Content Blocking > > • B1. A Technical Overview of Content Blocking Methods – Pier Carlo > Chiodi, Olaf Kolkman > > Olaf Kolkman gave an overview of the work done by Pier Carlo Chiodi on > content blocking on the Internet and other work in the same area. Outlining > a number of strategies employed by those wishing to block content, he noted > that blocking is done most effectively at the end-point (or origin of the > content), and that blocking in the network involves a variety of trade-offs. > > Lars-Johan Liman noted that even “legitimate” blocking has collateral > damage, and pointed to the example of the hotel network, where the > interception of traffic prevents the use of DNSSEC. He suggested that in > such situations it is best if the effects of the blocking are stated > upfront for users. > > Andrei Robachevsky recalled a paper produced by ISOC (prepared around the > time of the SOCA/PIPA/ACTA legislative proposals), and noted that security > and hidden costs are all important, and public policy makers need to be > made aware of these negative impacts. Olaf pointed out that users will do > whatever they can to get to blocked content, and that this can also have > potential negative effects (including a greater viral footprint or exposing > backdoors to computer systems). > > Alexander Isavnin asked participants in the room who thought their > countries were doing blocking, and whether they thought it was being abused. > > Richard Barnes noted that these issues reinforce the importance of an > end-to-end strategy, and agreed that the hotel network is a good example of > how blocking can break important security elements like DNSSEC. > > Jim Reid noted that blocking access to specific content can mean that > broader services are blocked. He noted a case that he had provided advice > on, where one of the questions asked was "what would happen if we switched > off port 80 access on this particular domain?” - the only person who knows > is the webmaster of the domain, but that person is unlikely to happily > cooperate in the blocking of their domain. > > • B2. Telex: A Proposal For Circumventing Censorship in the Network – Eric > Wustrow > > Eric Wustrow outlined the Telex project, which has been developed to > circumvent content blocking measures. The system provides a means of > connecting users to blocked content via a mechanism that is invisible to > the censoring technology. He encouraged ISPs to contribute to the work with > advice and prototype deployment assistance. > > Robert Kisteleki noted that PGP key distribution may be a bottleneck in > the Telex system. Eric noted that the paper discusses some of these issues, > including preventing censors from distributing “bad” public keys. He > suggested that having a central Telex entity that is known and trusted will > be important to mitigate these risks. He also noted that getting > information into areas subjected to censorship is often less difficult than > might be supposed. > > • B3. Web Censorship Circumvention: Challenges and Opportunities – Walid > Al-Saqaf > > Walid Al-Saqaf outlined his project to map URL filtering via > crowdsourcing, which is developing longitudinal data, while allowing > contributing users to access blocked websites via his own servers. He > presented a range of data and analysis obtained from this work, including > content blocking methods and strategies. He noted the need to make people > more aware of the range of circumvention tools and solutions available, and > that speed, security and anonymity are all important to users. He also > described his plans for the future, including open-sourcing his own project > and cooperating with similar projects. > > Andrei Robachevsky asked whether the project looked at which means of > blocking were most common. Walid stated that he has done some analysis of > this, using the packet headers - the more data he can get, the better this > analysis will be. > > Meredith Whittaker noted that the Open Observatory of Network Interference > (OONI) project, coordinated by the Tor team, is also doing work in this > area and is generating public data. > > Alexander Isavnin suggested that a RIPE task force might be a useful > vehicle for RIPE community members interested in this issue. Walid agreed > that the technical community, and particularly its relationship to civil > society actors in this space, needs to be further explored and understood. > > C. IANA Transition > > Chris Buckridge and Paul Rendek of the RIPE NCC presented background > information on the U.S. Government’s announcement of its intention to > transition out of its IANA functions oversight role. They noted that any > proposal for a future model of IANA administration needs to come from a > global, multi-stakeholder development process, and that RIPE and the RIPE > NCC are key IANA stakeholders. They suggested that the RIPE community’s > discussion of these issues should be centred around the Cooperation Working > Group, with the RIPE NCC assisting in facilitating input to that process > from regional events and voices. > > Rob Blokzijl warned that any process involving ICANN will necessarily be > complicated and political. On a technical point, he noted that future RIPE > NCC presentations on this subject should include the RIPE NCC’s reverse DNS > interactions with IANA, which may be more regular than the number resource > requests already noted. He further noted that the RIPE NCC’s direct > interactions with the NTIA itself were non-existent, and stressed that the > processes developed by RIPE and the other RIR communities already met the > requirements laid out by the NTIA as necessary for oversight of the IANA > functions. > > Danniel Karrenberg recalled that this is not the first time this > discussion has taken place, and that the RIPE community has been vocal in > its preference for the US government stepping away from this oversight role > since the late 1990s. He stressed the success of the RIR community > processes in policy-making and argued against over-complicating the > situation. He also noted that the IANA is three distinct groups of > functions (number resources, the DNS root zone and protocol parameters), > and the RIPE community discussions should focus primarily on the number > resource functions; if difficulties in defining governance processes for > the DNS root zone threaten to derail the oversight transition process, the > community should be explicitly prepared to propose unbundling those > functions and taking oversight of the numbering functions. > > Malcolm Hutty disagreed with the perception that NTIA oversight was not > important, and stressed that this oversight has protected the policy-making > relationship with ICANN itself. He noted that policy regarding the DNS is > determined by the ICANN community and imposed on registrars, meaning that > users essentially have to submit to ICANN policies. RIPE and the RIR > communities determine their own policies with regard to Internet number > management, but it may be conceivable that ICANN would decide it wants to > set these policies in future and impose them on the RIPE community. He > argued that a credible external oversight function must be retained to > prevent this. > > Nurani Nimpuno argued that the RIR communities should take ownership of > this issue, as custodians of the Internet number resources, and that the > community members should be contributing to the broader discussion, while > maintaining a focus on the numbering functions. She also stressed that the > communities should be pro-active in defining terms like “multi-stakeholder” > and “openness” which appear in the NTIA requirements. > > Jim Reid agreed with Malcolm Hutty on the importance of preventing ICANN > mission-creep, and on the need to tightly define the relationship between > the IANA operator and the RIR communities. He also warned that achieving > consensus on a community proposal may be difficult, and suggested that > there should be a fallback position to allow for RIPE and the RIPE NCC to > make a meaningful contribution to the global discussion. > > Jari Arkko noted the evolution that has occurred in how the IETF and IAB > manage oversight of the protocol parameters and their relationship to IANA. > He agreed that the RIPE community needs to take ownership of this and take > charge of what needs to change or not change. > > Olaf Kolkman, also an active participant in the IETF, noted the efforts in > the IETF to align on a principle-based approach, with the most important > principle being that the IETF controls its own destiny. Ensuring that > people are empowered to participate in these discussions will help the > debate going forward, and the community needs to provide guidance - > developing a set of principles may be a good first step. Olaf suggested RFC > 6220 as a good starting point. > > Salam Yamout provided some perspective from the government side, > particularly in the Arab world - notably the perception that the United > States has control of the Internet, and governments’ strong focus on > DNS-related issues. She noted that governments concerns centre primarily > around ICANN. > > Phil Rushton urged the community to be aware of events in other forums, > including the UN, WSIS and the ITU - while there is not the need for > everyone to be directly involved, we need to be aware of what governments > are thinking and the where they still need to be convinced by the RIR > communities. > > Daniel Karrenberg argued that the community does not need another level of > oversight for protection, and noted that the RIR communities already have > solid agreements in place with ICANN, which ICANN cannot unilaterally > change. He stressed the importance (and his optimism) of achieving > community consensus on a proposal. He again suggested that the RIR > communities should make every effort to unlink the number-related IANA > functions from the DNS. > > Paul Wilson noted that the IANA functions comprise three quite different > areas (numbers, protocol parameters and DNS), and that only one of these > (the DNS) is controversial - the IAB has stated its readiness to take > responsibility for the protocol parameters, and the RIR communities should > also, in the very near future, be ready to make such a statement regarding > the number functions. He and Adiel Akplogan agreed that strengthening the > RIR processes, ensuring that they are consistent, clear, accessible and > well documented, is vital. > > Sandy Murphy warned that the outcome of this process may impact our > current model of Internet governance, and stressed the need for the RIR > communities to have their voice heard. She also asked about the ICANN > consultation timeline, specifically the call for comments on its proposed > process, and whether this process is now set. Paul Rendek noted that there > is expected to be more information on ICANN’s planning in time of the ICANN > 50 Meeting, which takes place in London in June. > > Chris Buckridge also noted that all relevant information, including links > to the relevant ICANN web, is posted on the ripe.net website. > > D. Interconnection > > • D1. The Internet, the Internets, and Splinternets – Peter Koch > > Peter Koch discussed the proposals coming from Germany for establishing a > separate “German” Internet. > > Randy Bush noted the experience of the Saudi industry, after the regulator > decided that no traffic between two Saudi users should leave the country, > and pointed out that IXPs are a key element facilitating this. > > There was a question as to whether the German-only email system used the > DNS (which would generate its own cross-border traffic). Peter noted that > the one he mentioned uses special domains, but DNS leakage was of less > concern than the actual content of the messages. > > Alain Van Gaever asked about the rate of take-up. Peter didn’t have > figures to hand, but noted that there are incentives, it is early in the > deployment, and the operators are targeting users of existing email > services. > > Brian Nisbet said that while he can see what’s being attempted, it never > succeeds and generally breaks things that the users want to do. Peter > stressed that walking away from the discussion probably isn’t the right > strategy, and that users often learn what they want from marketing > campaigns. Expanding on the question of what users want, Meredith Whittaker > noted that users want security, and the technical community needs to be a > public voice stating that this is not the way to achieve that. > > Marco Davids noted an initative in the Netherlands using a closed user > group in BGP - this doesn't combat traffic monitoring, but rather helps > mitigate DDOS attacks, and if users (such as banks) are under attack the > group can be closed to users outside the Netherlands. > > Olaf Kolkman asked whether any EU research funding had been channeled to > this, and whether the project could lead to some sort of European > standardisation. Peter noted that the work is based on IETF standards. Jean > Jacque Sahel noted that the European Commission has publicly said that this > is all a very bad idea. > > Jaap Akkerhuis recalled a proposal from Italy to establish a trusted > network for digital mail. > > Olaf Kolkman and Peter Koch, summarising some of the discussion’s key > points, suggested that we are moving intelligence to the core of the > network, and the core is represented by big players. The technical > community cannot just dismiss these initiatives - there are some laudable > goals behind them, and we need to engage in the discussion. > > > • D2. Interconnection: Russia, the EU, and Internet Cooperation and > Governance – Igor Milashevskiy > > Igor Milashevskiy, representing the Russian government in its first RIPE > Meeting, shared some perspectives on that government’s view of the Internet > and related public policy. The Russian government sees the Internet as a > driver of development, with the Russian Internet market the biggest in > Europe - 68 million users, more than 56 million people use Internet every > day, including a significant percentage outside big cities. The Russian > language is also the second largest in Internet, there are slightly fewer > than five million .ru domains and more than 800,000 .рф domains. > > Speaking from personal perspective, he noted that the RIPE NCC is a > reference organisation in the Internet space, and the target is to restore > trust and confidence to the Internet environment, and develop international > tools for preventing improper use of the Internet. > > Ho noted that the main actor in the Intenet is the user, and if those > users have certain rights in the offline world - access to information, > privacy, secrecy of communication and freedom of opinion - we have to > protect those rights online. The process to do this has just begun, and the > Russian government believes there are no rights without duties, no freedom > without responsibility. > > He also suggested that the role of governments in Internet governance > needs to be recognised. NETmundial was a good and innovative attempt to > include all stakeholders, but the outcome document doesn’t reflect all the > contributions. > > Ciprian Nica, participating remotely, asked how and who should define the > proper purposes of using the Internet. Igor explained that the Internet is > a universal tool, and can be used for a wide range of purposes, but that > its primary purpose should be to make users’ lives richer. > > Desiree Milosevich asked if there could be some elaboration on the Russian > government’s issues with the NETmundial statement. Igor noted that this is > in the public record of the Russian statements. > > Paul Rendek extended his thanks to Igor and the Russian government for > their increased willingness to engage with the RIPE community and RIPE NCC, > and welcomed Igor's attendance at the RIPE Meeting. > > > E. Making the Internet a Little Bit Safer Cryptographically - Randy Bush > > Randy Bush discussed the development of an open public architecture for > hardware security modules. The goal is a design (not a product) that is > scalable, composable and assured. He stressed that the project needs people > to audit the code. > > Aaron Kaplan asked where to get a development board. Randy noted that the > boards are available for 170 USD. Aaron also noted that it would be a good > idea to have the testing procedure online and publicly available. > > Eric Wuster agreed that this is good work and asked why go the FPGA route > rather than using a small embedded chip. Randy noted that some of the > applications need speed, particularly some of the encryption stuff. > Regarding chips though, Randy noted that the FPGA Verilog was first done in > Python, meaning there is a Python version and a Verilog version. > > Eric also asked about how the project is sourcing hardware random number > generators. Randy replied that they are currently investigating this issue. > > F. Policy Radar > > • F1. RIPE NCC Updates, including NETmundial and IGF Developments – Chris > Buckridge > > Chris Buckridge gave an update on the wide range of Internet governance > events taking place in the coming months, including the ITU Plenipotentiary > 2014 that is scheduled to take place in October. He highlighted the links > between many of these events, particularly in terms of broader strategies. > He noted suggestions from earlier sessions that the RIPE NCC provide more > targeted information for the community, and reported that the RIPE NCC is > investigating the best method for doing this. > > Phil Rushton noted that the technical community can have significant > impact on events at the Plenipotentiary via their input to Member State > delegations. He also noted that while NETmundial produced a good outcome > for the multi-stakeholder model, other forums, such as the CSTD Working > Group on Enhanced Cooperation, saw much less support for multi-stakeholder > processes and governance. > > • F2. Co-chair Updates and Working Group Initiatives > > Meredith Whittaker closed the session by reiterating the goals of > co-chairs, particularly the need to engage people who are affected by > Internet governance and public policy issues, but don't currently take an > active interest. She noted options such as producing white papers, using > RIPE Meeting time for more workshop-style events, and other ideas for the > working group to serve as a RIPE community “brains trust” for those > involved in public policy discussions. > > Nurani Nimpuno noted her support for the co-chairs’ approach and stressed > the need to bring discussions back to specific issues and make the topics > practical for RIPE community participants. > > The co-chairs closed the meeting. --------------------- End of Minutes --------------------------------- On Wed, Jun 4, 2014 at 7:58 PM, Alain Van Gaever <avangaev(a)gmail.com> wrote: > Dear all, > > Please find below the minutes of the Coop-WG meeting during RIPE 68 in > Warsaw. > WG members are welcome to suggest further edits or changes. > > Hope to see you all in London for RIPE-69 ! > > Meredith, Maria & Alain > Co-Chairs of the Coop-WG > > > PS Thanks for Chris for producing the notes! > > ---- beginning of minutes ---- > > Location: Warsaw, Poland > > Attendance: Approximately 150 > > - Minutes of the session > - Full transcript of the session > <https://ripe68.ripe.net/archives/steno/39/> > - Video of the session and information slide-pack > <https://ripe68.ripe.net/archives/video/216/> > > Major points coming out of the discussion: > > 1. The RIR communities need to assert their ownership of issues > regarding the distribution and registration of Internet number resources. > This transition is an opportunity to more solidly formalise that ownership, > with minimal change to the existing policy-making and operational processes. > 2. While the IANA functions (as a bundle) present a number of complex > issues, identifying a future model for the IANA Internet number registry > functions should be straightforward. The policy-making and operational > processes relating to the IANA Internet number registry functions are solid > and have been in place for many years, and they have never included an > explicit oversight role for the NTIA. > 3. The Regional Internet Registries must ensure that their processes > and policies are clearly defined, well documented, transparent and > accessible. > 4. While the RIPE NCC will facilitate discussion of these issues > throughout the service region (including at community regional events), the > RIPE Cooperation Working Group will serve as the central venue for RIPE > community discussion and development of any proposal relating to the future > of the IANA functions. > > > > Some additional points made during the discussion: > > - Speakers reported on the progress of the Internet Architecture Board > (IAB) and the Internet Engineering Task Force (IETF) in establishing their > ownership and authority over protocol parameter registries maintained by > IANA. > - Several speakers noted the dangers arising from this process, > particularly the potential for an outcome that does not solidly define and > protect the community-driven, bottom-up control and development of IANA > policy. > - Several speakers noted the interest that governments throughout the > world are taking in this process and that government voices will be a > factor in the final outcome. > - Several speakers stressed the importance of reaching RIPE community > consensus on a proposal or position, with this process potentially seen as > a test-case for bottom-up policy making. > - Several speakers argued strongly that any RIR proposal should aim to > separate the IANA number management functions from oversight of the other > IANA functions. > > > > --------- End of minutes ------ >

3 2

IANA discussions: ENOG 7
by Chris Buckridge 06 Jun '14

06 Jun '14

Dear colleagues, Following on from Alain’s email, I would like to note a couple of items relating to discussions of the IANA oversight transition in the RIPE community. The Eurasian Network Operators' Group (ENOG) held its seventh meeting in Moscow on 26-27 May, the week after RIPE 68. There was a discussion of the IANA oversight transition at that meeting, and a brief summary of that discussion is provided below: > ENOG 7, 27 May 2014 > Attendance: Approximately 150 > > Major points coming out of the discussion: > - Additional ways in which the RIPE NCC interacts with the IANA include reverse DNS and running the K-root name server. > - It is important to note that the oversight function will not transition to a government-based body. > - The technical community has not had any issues with the U.S. government's conduct of its oversight of these functions for the past 20+ years - any new model should not complicate the current system and processes. > - The RIPE NCC is not interested in DNS operations and should not be put under that umbrella. > - The community should ensure that operators are protected from possible commercial interests, given that some of ICANN’s activities, such as the registration of domain names, are profit-making. As noted in the RIPE 68 session, the RIPE Cooperation Working Group is the official venue for community discussion of this issue. For this reason, the RIPE NCC will ensure that any discussion in other RIPE community forums is fed back to this list. Summaries of these discussions will also be posted on the RIPE website: http://ripe.net/iana-discussions Any comments or responses to this process or on the substance of the summaries should be posted to this mailing list. Best regards, Chris Buckridge Senior External Relations Officer, RIPE NCC

4 5

Minutes of the Coop-WG meeting during RIPE 68 in Warsaw
by Alain Van Gaever 04 Jun '14

04 Jun '14

Dear all, Please find below the minutes of the Coop-WG meeting during RIPE 68 in Warsaw. WG members are welcome to suggest further edits or changes. Hope to see you all in London for RIPE-69 ! Meredith, Maria & Alain Co-Chairs of the Coop-WG PS Thanks for Chris for producing the notes! ---- beginning of minutes ---- Location: Warsaw, Poland Attendance: Approximately 150 - Minutes of the session - Full transcript of the session <https://ripe68.ripe.net/archives/steno/39/> - Video of the session and information slide-pack <https://ripe68.ripe.net/archives/video/216/> Major points coming out of the discussion: 1. The RIR communities need to assert their ownership of issues regarding the distribution and registration of Internet number resources. This transition is an opportunity to more solidly formalise that ownership, with minimal change to the existing policy-making and operational processes. 2. While the IANA functions (as a bundle) present a number of complex issues, identifying a future model for the IANA Internet number registry functions should be straightforward. The policy-making and operational processes relating to the IANA Internet number registry functions are solid and have been in place for many years, and they have never included an explicit oversight role for the NTIA. 3. The Regional Internet Registries must ensure that their processes and policies are clearly defined, well documented, transparent and accessible. 4. While the RIPE NCC will facilitate discussion of these issues throughout the service region (including at community regional events), the RIPE Cooperation Working Group will serve as the central venue for RIPE community discussion and development of any proposal relating to the future of the IANA functions. Some additional points made during the discussion: - Speakers reported on the progress of the Internet Architecture Board (IAB) and the Internet Engineering Task Force (IETF) in establishing their ownership and authority over protocol parameter registries maintained by IANA. - Several speakers noted the dangers arising from this process, particularly the potential for an outcome that does not solidly define and protect the community-driven, bottom-up control and development of IANA policy. - Several speakers noted the interest that governments throughout the world are taking in this process and that government voices will be a factor in the final outcome. - Several speakers stressed the importance of reaching RIPE community consensus on a proposal or position, with this process potentially seen as a test-case for bottom-up policy making. - Several speakers argued strongly that any RIR proposal should aim to separate the IANA number management functions from oversight of the other IANA functions. --------- End of minutes ------

1 0

Re: [cooperation-wg] cooperation-wg Digest, Vol 29, Issue 6
by Wout de Natris 20 May '14

20 May '14

Gordon, Weren't regulators in telecoms in the late 90s meant to go in straight through the front door and break open the market? (Where necessary.) Make interconnection and special access possible by forcing access and setting prices, etc.? In those days I was not under the impression to be working on "the edges". What I get from your analyses, the main point BEREC's stating, is not so far beside what happened in the late 90s, at least in NL. New developments should be supported, but not through harming other/traditional services. And isn't that what the concern is about? Wout > From: cooperation-wg-request(a)ripe.net > Subject: cooperation-wg Digest, Vol 29, Issue 6 > To: cooperation-wg(a)ripe.net > Date: Tue, 20 May 2014 12:00:05 +0200 > > Send cooperation-wg mailing list submissions to > cooperation-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ripe.net/mailman/listinfo/cooperation-wg > or, via email, send a message with subject or body 'help' to > cooperation-wg-request(a)ripe.net > > You can reach the person managing the list at > cooperation-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cooperation-wg digest..." > > > Today's Topics: > > 1. BEREC - Network Neutrality (Gordon Lennox) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 May 2014 10:32:45 +0200 > From: Gordon Lennox <gordon.lennox.13(a)gmail.com> > Subject: [cooperation-wg] BEREC - Network Neutrality > To: Cooperation WG <cooperation-wg(a)ripe.net> > Message-ID: <1895B0B2-692B-49D0-A29C-FAC5A053528D(a)gmail.com> > Content-Type: text/plain; charset=windows-1252 > > BEREC have just issued a press release commenting on the Parliament's modified proposal and recalling some of their concerns with the Commission's initial proposal. About network neutrality they write: > > <<BEREC supports the promotion of and the clear commitment of the European Parliament to the principle of net neutrality. This is in line with BEREC?s public position, and indeed BEREC has been deeply involved with the subject since 2010, since when it has developed a set of principles and guidelines that can be implemented and adapted by national regulatory authorities, under the existing framework. The internet has proven to be highly innovative, thanks to certain fundamental principles such as the separation of network and application layer, the best effort principle and universal connectivity. This innovation should be safeguarded, both on the edges and within the network. > > BEREC recognizes that guaranteeing an open internet is a challenging objective, not least given its complex and dynamic ecosystem. Yet, the Commission?s original proposal would turn a flexible and progressive regulatory regime (under the 2009 Framework) into a rigid regulatory system and the European Parliament has generally retained this approach. > > BEREC would instead prefer an approach based on principles rather than detailed rules and which provides NRAs with the necessary powers to ensure that those principles (such as the ones developed by BEREC on what constitutes reasonable traffic management and on the relationship between specialized services and internet access services) are respected. Under such an approach, national regulators would be pursuing the same objective and enforcing the same principles, but the specific triggers and thresholds for regulatory intervention in a given market could be adapted to address national circumstances. > > If a rules-based approach is nonetheless to be pursued, then further work would be required to ensure that the definitions and rules were legally precise, future-proof and enforceable in practice. While some of the language in the text adopted by European Parliament draws upon BEREC previous publications on the subject, improving the original Commission?s proposals, it does not yet meet these standards. A balanced approach to promoting net neutrality on the Internet in parallel to the provision of specialised services is a difficult challenge. BEREC considers that specialised services should be clearly separated (physically or virtually) from internet access services at the network layer, to ensure that sufficient safeguards prevent degradation of the internet access services. Therefore BEREC welcomes the European Parliament?s acknowledgement of this principle. However, some inconsistencies in the proposed rules and definitions still raise legal and policy concerns.>> > > http://berec.europa.eu/eng/news_consultations/whats_new/2203-berec-publishe… > > So if you want network neutrality then you need regulation? The only question left is what kind. One indication of where they see the limits can perhaps be found in the sentence "This innovation should be safeguarded, both on the edges and within the network." > > I feel this is a significant shift. I cannot remember regulators looking in detail at what happens within traditional networks. They limited themselves to the "edges". > > Gordon > > > > > > > > > End of cooperation-wg Digest, Vol 29, Issue 6 > *********************************************

3 3

BEREC - Network Neutrality
by Gordon Lennox 20 May '14

20 May '14

BEREC have just issued a press release commenting on the Parliament's modified proposal and recalling some of their concerns with the Commission's initial proposal. About network neutrality they write: <<BEREC supports the promotion of and the clear commitment of the European Parliament to the principle of net neutrality. This is in line with BEREC’s public position, and indeed BEREC has been deeply involved with the subject since 2010, since when it has developed a set of principles and guidelines that can be implemented and adapted by national regulatory authorities, under the existing framework. The internet has proven to be highly innovative, thanks to certain fundamental principles such as the separation of network and application layer, the best effort principle and universal connectivity. This innovation should be safeguarded, both on the edges and within the network. BEREC recognizes that guaranteeing an open internet is a challenging objective, not least given its complex and dynamic ecosystem. Yet, the Commission’s original proposal would turn a flexible and progressive regulatory regime (under the 2009 Framework) into a rigid regulatory system and the European Parliament has generally retained this approach. BEREC would instead prefer an approach based on principles rather than detailed rules and which provides NRAs with the necessary powers to ensure that those principles (such as the ones developed by BEREC on what constitutes reasonable traffic management and on the relationship between specialized services and internet access services) are respected. Under such an approach, national regulators would be pursuing the same objective and enforcing the same principles, but the specific triggers and thresholds for regulatory intervention in a given market could be adapted to address national circumstances. If a rules-based approach is nonetheless to be pursued, then further work would be required to ensure that the definitions and rules were legally precise, future-proof and enforceable in practice. While some of the language in the text adopted by European Parliament draws upon BEREC previous publications on the subject, improving the original Commission’s proposals, it does not yet meet these standards. A balanced approach to promoting net neutrality on the Internet in parallel to the provision of specialised services is a difficult challenge. BEREC considers that specialised services should be clearly separated (physically or virtually) from internet access services at the network layer, to ensure that sufficient safeguards prevent degradation of the internet access services. Therefore BEREC welcomes the European Parliament’s acknowledgement of this principle. However, some inconsistencies in the proposed rules and definitions still raise legal and policy concerns.>> http://berec.europa.eu/eng/news_consultations/whats_new/2203-berec-publishe… So if you want network neutrality then you need regulation? The only question left is what kind. One indication of where they see the limits can perhaps be found in the sentence "This innovation should be safeguarded, both on the edges and within the network." I feel this is a significant shift. I cannot remember regulators looking in detail at what happens within traditional networks. They limited themselves to the "edges". Gordon

1 0

Panel on Internet Governance - watch now!
by Chris Buckridge 13 May '14

13 May '14

Dear colleagues, This is a quick note that the RIPE 68 Meeting is currently underway, and you can now tune in to watch a panel session on Internet governance: https://ripe68.ripe.net/live/main/ More details on the panel here: https://ripe68.ripe.net/programme/meeting-plan/plenary/#tue3 Best regards, Chris Buckridge, RIPE NCC

1 0

RIPE 68 Co-op WG now published
by Meredith Whittaker 07 May '14

07 May '14

Hi all, In our role as co-chairs, Alain, Maria, and I have worked with Chris and others to put together an agenda for next week that's now live and published. https://ripe68.ripe.net/programme/meeting-plan/coop-wg/ We're looking forward to it, and to your comments, of course. Cheers! Meredith -- Meredith Whittaker Program Manager, Google Research Google NYC

1 0

BEREC - Network Neutrality and Quality Monitoring
by Gordon Lennox 03 May '14

03 May '14

I know it is late but BEREC has just had a public consultation on: "Monitoring quality of services in the context of network neutrality" based on a draft report, a draft which I think is still worth reading. See: http://berec.europa.eu/eng/news_consultations/ongoing_public_consultations/… Regards, Gordon

3 3

REMINDER: One Week to Comment on IANA Transition Process Proposal
by Chris Buckridge 01 May '14

01 May '14

Dear colleagues, This is a brief reminder that a deadline of Thursday, 8 May has been set for public comment on the "Draft Proposal, Based on Initial Community Feedback, of the Principles and Mechanisms and the Process to Develop a Proposal to Transition NTIA's Stewardship of the IANA Functions": <http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08a…> This document is a preliminary step in the multi-stakeholder process to develop a future model of IANA administration and outlines the process by which that development will take place. It’s most significant concrete proposal is the creation of a "steering group" made up of various IANA stakeholder representatives (including the Address Supporting Organization and the Number Resource Organization) to steward the global discussion and development process. A public comment on the proposal was posted earlier this week by the Internet Architecture Board (IAB): <http://www.iab.org/wp-content/IAB-uploads/2014/04/iab-response-to-20140408-…> Anyone with an interest is encouraged to send their comments on the draft proposal to <ianatransition(a)icann.org>. Further background on the IANA functions and the significance of this transition process for the RIPE community is available at: <http://ripe.net/iana-transition> There will also be an opportunity for further RIPE community discussion of the IANA transition in next month's Cooperation Working Group session at RIPE 68: <https://ripe68.ripe.net/programme/meeting-plan/coop-wg/> Best regards, Chris Buckridge, RIPE NCC

1 0

NETmundial Concludes With Multistakeholder Statement
by Chris Buckridge 25 Apr '14

25 Apr '14

Dear colleagues, The RIPE NCC has posted a brief report on the conclusion of NETmundial in São Paulo, Brazil: https://www.ripe.net/internet-coordination/news/industry-developments/netmu… There will be further reporting on NETmundial on the agenda of the RIPE Cooperation Working Group session at RIPE 68 next month. Best regards, Chris Buckridge, RIPE NCC

1 0

Update on the IANA Transition Process
by Paul Rendek 23 Apr '14

23 Apr '14

Dear colleagues, As noted in earlier discussions, the National Telecommunications and Information Administration (NTIA), an agency of the U.S. Department of Commerce, has announced that it intends to transfer key Internet domain functions (the IANA functions) to the global multi-stakeholder community. An open process to develop a model for future IANA administration is now underway. The RIPE NCC has published a section on its website that provides background information on the IANA functions, the role of oversight of IANA and the RIPE NCC’s relationship to IANA. The pages also detail the process for development of the future IANA model, and the opportunities for the RIPE community and RIPE NCC membership to contribute: http://ripe.net/iana-transition The RIPE NCC would like to highlight several key points to help stimulate community discussion in this area: - The IANA function covers three separate areas: Internet resources, domain names and protocol assignments on behalf of the IETF. The primary concern for the RIPE NCC is ensuring the continued fair, efficient and stable management of Internet number resources in any future model or arrangement. - The RIPE NCC and the other RIRs actually have relatively few interactions with IANA. We receive allocations of Internet number resources according to global policies developed using the same bottom-up processes as in our regional communities. To date, the U.S. Government’s oversight of IANA has never been exercised to affect IANA operations or policy development relating to Internet number resources. - The RIPE community and the RIPE NCC work together using a well-established model of bottom-up, open and inclusive processes. These attributes, which underpin all RIPE NCC and RIPE community activities, are essential elements of a "multi-stakeholder" model, specified by the NTIA as a requirement for any proposal to move forward. - The RIRs have developed their own robust structures to allow for cooperation and coordination on a global level, most notably through the Number Resource Organization (NRO), which represents all five RIRs working cooperatively. The NRO Number Council, which is comprised of members from the five RIR communities (and which also plays the role of the ICANN Address Supporting Organization Address Council), currently provides oversight of the global policy development process as it pertains to Internet number resources. It is important that the RIPE NCC membership and the RIPE community's voices are heard in these discussions, as key stakeholders in how the global pool of Internet number resources is managed. Following discussion with the co-chairs of the RIPE Cooperation Working Group, we suggest that RIPE community discussion be focused in this working group, both on the mailing list and in RIPE Meeting sessions. This arrangement will allow anyone with an interest to participate or follow discussions, without the need to attend events in person. You can subscribe to the RIPE Cooperation Working Group mailing list at: https://www.ripe.net/ripe/mail/wg-lists/cooperation At RIPE 68 in Warsaw, there will be a discussion on the future of the IANA functions in the Cooperation Working Group session on 15 May (remote participation will be available): https://ripe68.ripe.net/programme/meeting-plan/ There will be opportunities to consider these issues in all RIPE-related venues, including ENOG, MENOG and other regional meetings. The RIPE NCC will also use its Roundtable Meetings to engage with governments and regulators on this topic. Finally, there are channels for global discussion, including the ICANN-hosted mailing list <ianatransition(a)icann.org>: https://mm.icann.org/mailman/listinfo/ianatransition The RIPE NCC will actively participate in the global development process that is being convened by ICANN. The RIPE NCC will be informed and directed by our community and membership on the best way forward with this transition. Kind regards, Paul Rendek Director of External Relations RIPE NCC

2 3

NETmundial HUB - CENTR Background paper
by Wim Degezelle 16 Apr '14

16 Apr '14

Hi All, CENTR will organise the Brussels Hub for next weeks NETmundial meeting in São Paulo. This means that during the meeting all who are interested are welcome to join us in the CENTR office to follow the sessions, discuss and give life input to the meeting in Brazil. If you want to join please RSVP before April 22, noon CET at secretariat(a)centr.org . (first come first served) Details at https://centr.org/CENTRpaper_NETmundial-April2014 . CENTR has published a background paper (including a tentative agenda for NETmundial). You can download it at https://centr.org/CENTRpaper_NETmundial-April2014 . CENTR will be represented at NETmundial by Peter Van Roste (General Manager), Lise Fuhr (.dk / CENTR Board), Richard Weil (.at/ CENTR Board) and many other members. Kind Regards Wim signature2

1 0