- cooperation-wg - mailman.ripe.net

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