October 2014 - address-policy-wg

Re: [address-policy-wg] [policy-announce] 2014-05 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of Internet Resources)
by Erik Bais 14 Oct '14

14 Oct '14

Hi, Thank you for the analyses. > You can find the full proposal and the impact analysis at: > https://www.ripe.net/ripe/policies/proposals/2014-05 I see some issues that aren't consistent in the wording of the policy, especially in terms of Legacy and PI space holders (non-members) and: > Address space may only be re-allocated to another resource holder who is a member of an RIR that allows transfers. Both PI space holders and Legacy holders are not always members of an RIR. I'm speaking with my RIPE region community member experience here. So it could be that in for instance ARIN or APNIC all resource holders are members of the RIR, but here in the RIPE region that isn't (always) the case. > When Internet number resources are transferred from another RIR, the RIPE NCC will work with the resource holder to fulfil any requirements of the sending RIR. Suggested wording: When Internet number resources are transferred from another RIR to the RIPE Region, the RIPE NCC will work with the receiving party and the resource holder and the sending RIR to confirm the qualification requirements in order to complete transfer. It is more specific to the intend, however as the RIPE NCC is put in a position to check if the receiving party qualifies following a needs assessment according to the policy of another RIR, the RIPE NCC needs to be in contact with the receiving party, the resource holder and the sending RIR. On the part of arbitration, the policy as it is described in the Summary of the Proposal is a nightmare I think.. The Summary of the proposal states : > If another RIR has a different policy, the RIPE NCC should create an operational procedure that satisfies the requirements of both RIRs in order to allow transfers to and from its service region I understand the intend of what it stated, but I don't think that the NCC should be put in a position where Axel would come opposite from the board of ARIN or APNIC and have them sort out the procedure, without a proper arbitration procedure in place outside the RIR's ... What if a transfer isn't going as planned and it does pass the arbitration in the RIPE region ... the sending RIR doesn't agree with the arbitration out-come ... And what is next ? Will the NCC take the other RIR to court ? Or is there an arbitration process for RIR's ? Personally I think that the policy should state that the party in the RIPE Region should deal with the arbitration in the RIPE region and that the sending or receiving party in the other RIR should convert to the arbitration in their respective RIR. Or agree by agreement which of the 2 RIR's their arbitration will be used (and with that choice to apply their policy) if we keep the policy as it is currently on the table.. If the intent of the policy, as it is currently, is that the RIPE NCC should adhere to the policy of the more strict assignment policy of the other RIR, state in the policy specifically that the other RIR needs to do the need justification checking with the receiving party and approve the transfer prior to submitting the transfer for processing to the RIPE NCC. They have the best knowledge of the policy in that specific RIR and if they don't agree with the justification or qualification of the receiving party, their arbitration can also be used, without getting the RIPE NCC in a squeeze between a rock and a hard place or putting a requirement in place for the RIPE NCC staff that they should get intimately familiar with other RIR their addressing policy. If the other RIR approves the transfer based on their current policy at that time (as if it is an intra-rir transfer ) it can be submitted to the RIPE NCC for administrative processing, as the RIPE NCC has a more liberal addressing policy towards transfers than any other RIR. I hope that I've made my point on the topic and with that also suggested a way forward. I really don't like a policy that has too many open ends or topics that we haven't addressed enough and already know up-front that the other RIR's don't agree with. Regards, Erik Bais

2 1

Re: [address-policy-wg] 2014-05 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of Internet Resources)
by Nick Hilliard 13 Oct '14

13 Oct '14

On 13/10/2014 14:09, Marco Schmidt wrote: > You can find the full proposal and the impact analysis at: > > https://www.ripe.net/ripe/policies/proposals/2014-05 > > And the draft document at: > > https://www.ripe.net/ripe/policies/proposals/2014-05/draft The RIPE NCC analysis says: "Existing RIPE Policies will be applied to IPv4 resources." It may be a good idea to note explicitly in the policy that as long as the transfer is in effect, RIPE policy applies to the resources. This isn't explicit in the policy. Conversely, it would also be sensible to assume that resources transferred out of the region will be subject to the receiving RIR. The purpose of stating this explicitly is to ensure that it's clear to all parties that only one set of rules apply, and that once a transfer has taken place, another RIR can't come knocking at some time in the future and make a claim that maybe they had changed their minds after all. It also stops conditional or transitive policy claims, i.e. "we'll transfer to you on condition that ..." or even worse "we'll transfer to you and our conditions are binding on any future transfers". suggested text: > 2.0 Transferring Internet Resources to the RIPE NCC Service Region > > The RIPE NCC shall accept all transfers of Internet number resources to > its service region, provided they comply with the policies relating to > transfers within its service region. Internet Resources transferred to > the RIPE NCC Service Region will be subject exclusively to RIPE policy > for the duration of the transfer. > > When Internet number resources are transferred from another RIR, the > RIPE NCC will work with the resource holder to fulfil any requirements > of the sending RIR. > > 3.0 Transferring Internet Resources from the RIPE NCC Service Region > > When transferring Internet numberresources to another RIR, the RIPE > NCC will follow the transfer policies that apply within its own service > region. The RIPE NCC will also comply with the commitments imposed by > the receiving RIR, in order to facilitate the transfer. Internet > Resources transferred to another RIR will be subject exclusively to > that RIR's number resourcing policy for the duration of the transfer. Nick

1 0

2014-05 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 13 Oct '14

13 Oct '14

Dear colleagues, The draft document for version 2.0 of the policy proposal 2014-05, "Policy for Inter-RIR Transfers of Internet Resources" has now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 1.0 include: - Replacing the term "LIR" with "resource holder" - Removing the reference to legacy resources from IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region - Defining special conditions for legacy resources in the inter-RIR transfer policy - Rewording the second argument opposing the proposal You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-05 And the draft document at: https://www.ripe.net/ripe/policies/proposals/2014-05/draft We encourage you to read the draft document text and send any comments to <address-policy-wg(a)ripe.net> before 11 November 2014. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 Review Period extended until 20 October 2014 (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 13 Oct '14

13 Oct '14

Dear colleagues, The Review Period for the proposal 2014-04, "Relaxing IPv6 Requirement for Receiving Space from the Final /8 has been extended until 20 October 2014. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0