June 2014 - address-policy-wg

Re: [address-policy-wg] 2014-05 New Policy Proposal (Policy for Inter-RIR Transfers of Internet Resources)
by sandrabrown＠ipv4marketgroup.com 06 Jun '14

06 Jun '14

On Thu, Jun 5, 2014 at 2:25 PM, Jan Ingvoldstad <frettled(a)gmail.com> wrote: > On Thu, Jun 5, 2014 at 7:30 PM, Scott Leibrand <scottleibrand(a)gmail.com> > wrote: > >> Overall, this policy looks good to me. However, I believe there is one >> problem with the text. The language regarding recipients in other regions >> requires that the recipient be an LIR. However, the transfer policies of >> the other regions do not make any such distinction. Therefore, I believe it >> would be more appropriate to use the word organization instead of LIR when >> referring to recipients in other regions. >> > > That's a fair point. > > -When Internet number resources are transferred to another RIR, the RIPE > NCC will work with the destination RIR to allow the transfer to the > receiving LIR. > +When Internet number resources are transferred to another RIR, the RIPE > NCC will work with the destination RIR to allow the transfer to the > receiving organization. > > Like that? > Yes. ________________________ I am in agreement with Scott and Jan on this revision..."LIR" becomes "receiving organization". Thank you to you both. - Sandra Also: -Address space may only be re-allocated to another LIR that is a member of an RIR that allows transfers. The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation. +Address space may only be re-allocated to another organization that is a member of an RIR that allows transfers. The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation. However, that may have implications for intra-RIR transfers, so you might need to separate out the two cases if you don't want to imply that non-LIR organizations can receive transfers in the RIPE region. Maybe something like "to another LIR in the RIPE region, or an organization that is a member of an RIR that allows transfers." -Scott _______________ Replacing "LIR" with "organization" should also be ok within the context of RIPE Transfer Policy. - Sandra _________________

1 0

Re: [address-policy-wg] [sig-policy] RIPE Policy Text for Inter-RIR Transfers - 2014-05
by Sander Steffann 05 Jun '14

05 Jun '14

Hi John, Op 5 jun. 2014, om 16:54 heeft John Curran <jcurran(a)arin.net> het volgende geschreven: > On Jun 5, 2014, at 7:24 AM, Skeeve Stevens <skeeve(a)eintellegonetworks.com> wrote: > >> Here is the policy text being proposed in RIPE for Inter-RIR Transfers - 2014-05 >> >> https://www.ripe.net/ripe/policies/proposals/2014-05 I think this policy should be discussed on the RIPE address policy mailing list. Feedback in other places does not have much effect ;) CC'ing APWG now. > From the proposed policy text (with labels added for reference) - > > (a) > When Internet number resources are transferred to another RIR, the RIPE NCC will work with the destination RIR to allow the transfer to the receiving LIR. > > (b) > When Internet number resources are transferred from another RIR, the RIPE NCC will work with its member LIR to fulfil any requirements of the sending RIR. > > (c) > If resources are transferred as legacy resources, the RIPE NCC will apply the legacy policy when accepting these resources. > > The intent of the above text may not be clear with respect to resources coming from > another region (b) which are presently "legacy" resources in that region, i.e. it might > be possible to reasonable argue that the policy intent is (b) or (c) for that case. When receiving resources from another region then (b) will always apply. At a minimum the RIRs have to work together to keep the databases consistent. If the originating RIR tells the RIPE NCC that those resources are legacy resources then the receiver can choose to have them treated as legacy resources in the RIPE region as well. But the policy does not allow conversion in the other direction. If ARIN would tell the RIPE NCC that the resources are *not* legacy resources (not ever, or not anymore) then they can not not be treated as legacy after transfer. > (Not a comment in favor or opposition to the proposed policy; just seeking clarity so > that implementation, if it were adopted, has solid alignment with the policy intent.) Thanks. Please continue the discussion on the RIPE APWG list ;) Cheers! Sander

1 0

2012-02 Policy Proposal Withdrawn (Policy for Inter-RIR transfers of IPv4 address space)
by Marco Schmidt 03 Jun '14

03 Jun '14

Dear colleagues, The proposal 2012-02, "Policy for Inter-RIR transfers of IPv4 address space" has been withdrawn. It is now archived and can be found at: https://www.ripe.net/ripe/policies/proposals/2012-02 Reason for withdrawal: The proposer of 2012-02 proposed 2014-05, a new inter-RIR transfer policy. 2014-05 focuses on being aligned with internal resource transfers as well as being more cohesive with the policies of other RIRs. As a consequence, the proposer decided to withdraw 2012-02. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-05 New Policy Proposal (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 03 Jun '14

03 Jun '14

Dear colleagues, A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-05 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 2 July 2014. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-03 Draft Document and Impact Analysis will be produced (Remove Multihoming Requirement for AS Number Assignments)
by Marco Schmidt 02 Jun '14

02 Jun '14

Dear colleagues, The discussion period for the proposal described in 2014-03, "Remove Multihoming Requirement for AS Number Assignments" has ended. A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-03 Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0