Initial Draft: RIPE Community IANA Stewardship Proposal
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.
Hi, To get the discussion going on the principles outlined below, I have added my comments and is eager to see feedback from others,
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.
I think this makes sense. It is important that the numbering community comes up with one joint proposal.
This proposal should meet the requirements of the Request For Proposals (RFP) produced by the IANA Stewardship Transistion Coordination Group (ICG).
That is wise. Even more important is that it meets the requirements from the US governments.
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 is perhaps the bulk of the job. Without the US Governemet IANA contract - what provisions needs to be taken into the RIR-IANA agreements directly.
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.
There has been a discussion on the IETF list on separability of IANA functions. As IP addresses is a protocol parameter that seems natural, but may not be a hard requirement. Coordination is good as long as we produce a good proposal that serves our community and internet users in general with regards to number resources.
The RIPE community asks the RIPE NCC and the other RIRs keep it informed about progress and content of the proposal.
This is very important.
The RIPE community asks the RIPE NCC to complete the proposal and to submit it to the ICG before January 15th 2015.
Sounds like a reasonable requirement. I think one of the important principles we should add is that the proposal should build on our existing framework and governance structure as described in https://www.nro.net/about-the-nro/rir-governance-matrix for the RIPE NCC. Hans Petter -- Hans Petter Holen Mobile +47 45 06 60 54 | hph@oslo.net | http://hph.oslo.net
In the report from the ARIN meeting there is a reference to the process in the ARIN region: https://www.arin.net/participate/meetings/reports/ARIN_34/ppm_notes.html#anc...
participants (2)
-
Chris Buckridge -
Hans Petter Holen