June 2024 - address-policy-wg

RIPE 88 Address Policy WG - Draft Minutes Published
by Leo Vegoda 01 Jul '24

01 Jul '24

Dear Address Policy WG, We’ve received the minutes of the RIPE 88 meeting and the RIPE NCC has published them for your review. https://www.ripe.net/community/wg/active-wg/ap/minutes/ripe-88-address-poli… We'd like to thank Adonis and Alun from the RIPE NCC for preparing the draft for us. Please review the minutes and provide feedback if you think there is something missing or incorrect. Kind regards, Leo Vegoda, for the Address Policy WG co-chairs

3 4

RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
by Angela Dall'Ara 20 Jun '24

20 Jun '24

Dear Colleagues, The RIPE policy “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” has been updated to align with the implementation of NWI4, done in Whois release 1.112, which added the option to change the status of an IPv4 allocation object in the RIPE Database from “ALLOCATED PA” to “ALLOCATED-ASSIGNED PA” when the whole address space is assigned to the LIR infrastructure or for use by an End User with services provided by the issuing LIR. The new document is called ripe-826 and is available at: https://www.ripe.net/publications/docs/ripe-826/ Please note that also the following has been updated: 1) In the Abstract: The link to the webpage where to find information on the Address Policy WG from https://www.ripe.net/participate/ripe/wg/ap to https://www.ripe.net/community/wg/active-wg/ap/ 2) In 1.1 Scope: The link to the webpage listing the RIPE community’s policies: from https://www.ripe.net/ripe-policies to https://www.ripe.net/publications/docs/ripe-policies/ 3) In 5.3 Sub-Allocations The option to ask for a conversion of PI to PA via LIR Portal has been added. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

Updated Approach to IPv6 Transfer Requests
by Marco Schmidt 19 Jun '24

19 Jun '24

Dear colleagues, During the Address Policy WG session at RIPE 88, I presented on the topic of IPv6 stockpiling by several members [1]. There was widespread support from the working group that our application of IPv6 needs to evolve, emphasising the importance of enforcing policy requirements for transfers of IPv6 allocations. In light of this, the RIPE NCC will now prioritise enforcing policy requirements when evaluating IPv6 allocation transfer requests. Since transferred resources are no different than allocations made by the RIPE NCC, if the receiving party of a transfer request already holds an IPv6 allocation, they must document the need for another allocation according to the policy requirements for subsequent allocations [2][3]. This means the receiving party must demonstrate how they have utilised their existing allocation or justify the need for a new one. In the case of an IPv6 allocation transfer, a successfully deployed network on that range would be considered a valid new need. This updated approach will be applied to any new transfer request submitted from today. Please note, this updated approach only applies to transfer requests under RIPE policies. If the change of holdership of an IPv6 allocation is due to a company merger or acquisition, the RIPE NCC will process this change in accordance with relevant RIPE NCC procedures. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://ripe88.ripe.net/wp-content/uploads/presentations/73-RIPE88-Feeback-… [2] https://www.ripe.net/publications/docs/ripe-807/#2-1-transfer-requirements [3] https://www.ripe.net/publications/docs/ripe-738/#52-subsequent-allocation

2 3