December 2014 - address-policy-wg

Policy Proposal Implemented: 2014-02, "Allow PI transfer"
by Ioanna Spyroulia 03 Dec '14

03 Dec '14

Dear colleagues, We are pleased to announce that we have implemented policy proposal 2014-02, "Allow IPv4 PI transfer”. In accordance with the new policy, End Users can transfer complete or partial blocks of Provider Independent (PI) IPv4 address space that were previously assigned to them by the RIPE NCC. To initiate a PI transfer, the sponsoring LIR of either the transferring or receiving End User should open a ticket with the RIPE NCC by sending an email to lir-help(a)ripe.net. The procedure describing the requirements for PI transfers can be found at: https://www.ripe.net/lir-services/resource-management/ipv4-transfers/transf… The list of all PI assignments transferred under this policy can be found at: https://www.ripe.net/lir-services/resource-management/ipv4-transfers/table-… The archived policy proposal can be found at: https://www.ripe.net/ripe/policies/proposals/2014-02 The updated RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", is available at: https://www.ripe.net/ripe/docs/ripe-623 Kind regards, Ioanna Spyroulia RIPE NCC Registration Services

3 3

Policy Proposal Implemented: 2014-02, "Allow PI transfer"
by Sakun Alexey 01 Dec '14

01 Dec '14

Hi! My question is: is it possible in accordance with a new policy to transfer PI-block from End User to LIR, not to another End User? So LIR becomes valid owner of PI-block and then convertes this PI block to PA in accordance with this procedure: http://www.ripe.net/lir-services/resource-management/converting-pi-to-pa. Here, https://www.ripe.net/lir-services/resource-management/ipv4-transfers/transf… it is written : ... Any legitimate holder of IPv4 PI space can transfer this to another End User or _*MEMBER*_ in the RIPE NCC service region, provided:.. As i understand - it is possible? Thank you. -- Best regards, Alexey

2 1

Re: [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Gert Doering 01 Dec '14

01 Dec '14

Dear Address Policy WG, while I can understand that beaches and drinks are more attractive than policy work, we have a proposal here that needs a bit of caring - this one is in Review Phase until Friday, and has received exactly one comment yet (strong support). I could use a *bit* more feedback here... thanks, Gert Doering, Address Policy WG Chair On Thu, Jul 31, 2014 at 01:30:43PM +0200, Marco Schmidt wrote: > > Dear colleagues, > > The draft document for version 2.0 of the policy proposal 2014-04, > "Relaxing IPv6 Requirement for Receiving Space from the Final /8", > has now been published, along with an impact analysis conducted by > the RIPE NCC. > > Some of the differences from version 1.0 include: > > - Extending the fulfilment of the IPv6 requirement to include any > globally routable unicast IPv6 address block > - Related wording adjustments in the summary and rationale of the proposal > > > You can find the full proposal and the impact analysis at: > > https://www.ripe.net/ripe/policies/proposals/2014-04 > > and the draft document at: > > https://www.ripe.net/ripe/policies/proposals/2014-04/draft > > We encourage you to read the draft document text and send any comments > to address-policy-wg(a)ripe.net before 29 August 2014. > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > > Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

21 46