[cooperation-wg] Update on the IANA Transition Process

Thanks Paul,

   Patrik

On 22 apr 2014, at 19:07, Paul Rendek <rendek at ripe.net> wrote:

> 
> Signed PGP part
> Hello Patrik,
> 
> Thanks for bringing up this point. In my opinion it is one of the core
> quesitons the RIPE community and RIPE NCC membership need to discuss
> during the this process and a great place to start.
> 
> In relation to the specific IANA functions relating to the management of
> the global Internet number resource pool, the RIPE NCC feels that there
> is a strong, stable and open process by which policy is made and
> implemented.
> 
> This includes a community body, the NRO Number Council, tasked with
> ensuring that all phases of the regional and global policy development
> processes have been correctly concluded. In this sense, practical
> "oversight" of the IANA policy development processes already lies with
> the community.
> 
> The NTIA’s statement is an invitation to officially acknowledge its own
> absence from this process - potentially a straightforward minimal
> process for the Internet numbers. As we note on the "What is Oversight?"
> page of our website, however, there is another aspect to "oversight"
> that is the role of contracting party. In this role, the oversight
> holder (currently NTIA) has the power to dictate the terms of the IANA
> functions contract and determine who will be contracted to carry out
> that role. There has recently been some discussion of this on both the
> ICANN IANA transition and 1Net mailing lists.
> 
> The RIPE NCC’s position will be formed by the input of the RIPE
> community and RIPE NCC membership. Our initial discussions, both
> internally and informally with others have considered the possibility of
> this oversight responsibility also shifting to the global RIR
> policy-making community. This could very well see an increased role for
> the NRO Number Council.
> 
> While the notion of removing the NTIA oversight is no news inside our
> community, it is early days in the actual discussion of roles and
> acountability. I for one am very interested to hear what our community
> has to say.
> 
> Your point will be one that will lead us into a discussion I feel we
> need to have. Building a strong, solid position for the RIPE NCC will
> depend on the active and informed input of our community.
> 
> So at this point, we welcome any thoughts on this or any other issues
> related to the NTIA transition to be sent to this list. I look forward
> to our discussion here on the list and at the upcoming Cooperation WG
> session in Warsaw.
> 
> Cheers,
> Paul
> 
> 
> On 4/17/14 6:10 PM, Patrik Fältström wrote:
> > Paul,
> >
> > Thanks for this description.
> >
> > Do you think you can more explicitly describe the audit mechanisms
> that exists today, and what RIRs do view in the future, given the NTIA
> oversight over IANA is going away? Is the NRO Number Council looking at
> IANA today (in a similar way as IAB/IETF is), or just the result of the
> RIR coordination, and do you envision that role increase?
> >
> > It is a bit unclear in your message below. At least for me, and if I
> am wrong and it is there, my apologies.
> >
> >    Regards, Patrik
> >
> > On 17 Apr 2014, at 15:35, Paul Rendek <rendek at ripe.net> wrote:
> >
> >> 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 at 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
> >>
> >
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/cooperation-wg/attachments/20140423/e7b85f9b/attachment.sig>