- address-policy-wg - mailman.ripe.net

2024-02 New Version Policy Proposal (IPv6 Initial Allocations /28 and extension to /28)
by Angela Dall'Ara 25 Sep '25

25 Sep '25

Dear colleagues,   A new version of RIPE policy proposal 2024-02 "IPv6 Initial Allocations /28 and extension to /28" is now available for discussion.  Following the last round of discussion, this proposal has been updated and it is now at version 4.0.  The main difference from version 3.0 is that it allows the extension without additional documentation of a single allocation per LIR instead of per Member. You can find the full proposal at: https://www.ripe.net/community/policies/proposals/2024-02/ As per the RIPE Policy Development Process (PDP), the purpose of this six-week Discussion Phase is to discuss the proposal and provide feedback to the proposers. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal.   The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781  We encourage you to review this proposal and send your comments to  address-policy-wg(a)ripe.net before 7 November 2025.   Kind regards,   Angela Dall'Ara Policy Officer RIPE NCC

1 0

2024-02 (IPv6 Initial Allocations /28)
by Leo Vegoda 16 Sep '25

16 Sep '25

Dear Address Policy WG, The Review Phase for proposal 2024-02 (IPv6 Initial Allocations /28) has ended. Comments included: - discussion on the impact of using the term "Member" instead or "LIR" - a suggestion to break the proposal into two separate parts to accommodate the new terminology - a disagreement that there is a need to extend from /29 to /28 - a description of a use case for the /28 The proposers have been working on an updated version of the proposal designed to address feedback. This update will get a new Discussion Phase. The RIPE NCC will publish the updated proposal soon. We'd like to thank the proposers and everyone who participated in the discussion so far. Alex, Franziska, and Leo Your co-chairs

1 0

Country Codes Now Included in Transfer Statistics
by Marco Schmidt 15 Jul '25

15 Jul '25

Dear colleagues, We are pleased to inform you that as from today (15 July 2025), country codes will be added to transfer statistics: https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/tra… For transfers within the RIPE NCC service region, country codes of both parties involved in the transfer are visible. For transfers between the RIPE NCC and another Regional Internet Registry (RIR) (Inter-RIR), the country code of the party within the RIPE NCC service region is displayed. In addition to country codes, the statistics also indicate whether a transfer was temporary. This update reflects our commitment to improving transparency and is the result of feedback and support from the RIPE community. It was built on the discussions held in the Address Policy Working Group and highlighted during the Registration Services update at RIPE 89: https://ripe89.ripe.net/archives/video/1469/ It is worth noting that: - Country codes are based on ISO 3166: https://www.iso.org/iso-3166-country-codes.html - The country codes shown reflect the information available at the time the transfer was processed. Please let us know if you have any questions or comments. Marco Schmidt Manager Registration Services RIPE NCC

1 0

RIPE 90 Address Policy WG - Draft Minutes Published
by Franziska Lichtblau 30 Jun '25

30 Jun '25

Dear Address Policy WG, We have received the minutes for the APWG sessions at RIPE90 and the NCC has published them for your review: https://www.ripe.net/community/wg/active-wg/ap/minutes/ripe-90-address-poli… We'd like to thank Antony and Virgile from the NCC for preparing the draft for us. Please review the minutes and provide feedback if you find anything missing or incorrect. Best regards, Leo Vegoda, Alex le Heux, Franziska Lichtblau Address Policy WG co-chairs

1 0

Feedback on reviewing the RIPE policy documentation
by Angela Dall'Ara 17 Jun '25

17 Jun '25

Dear colleagues, Following up on the final point of my presentation [1] at RIPE 90, I would like to invite your feedback on the review of RIPE policy documentation. Currently, we have multiple policy documents, and we often hear that it can be challenging to identify which document outlines the applicable policy for a specific request. Additionally, the documents follow different formats, and not all of the content is directly relevant to understanding the core policies. To address this, it may be beneficial to consolidate policies related to the same topic into a single, clear, and well-structured document. More specifically we have: Three policy documents regarding IPv6: - ripe-738: IPv6 Address Allocation and Assignment Policy (https://www.ripe.net/publications/docs/ripe-738/ <https://www.ripe.net/publications/docs/ripe-738/>) - ripe-451: IPv6 Address Space Policy For Internet Exchange Points (https://www.ripe.net/publications/docs/ripe-451/ <https://www.ripe.net/publications/docs/ripe-451/>) - ripe-636: IPv6 Addresses for Internet Root Servers in the RIPE Region (https://www.ripe.net/publications/docs/ripe-636/ <https://www.ripe.net/publications/docs/ripe-636/>) Two policy documents regarding transfers: - ripe-807: RIPE Resource Transfer Policies (https://www.ripe.net/publications/docs/ripe-807/ <https://www.ripe.net/publications/docs/ripe-807/>) - ripe-806: Voluntary Transfer Lock (https://www.ripe.net/publications/docs/ripe-806/ <https://www.ripe.net/publications/docs/ripe-806/>) Two policy documents regarding provider independent resource holders requirements: - ripe-637: Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region (https://www.ripe.net/publications/docs/ripe-637/ <https://www.ripe.net/publications/docs/ripe-637/>) - ripe-603: Publication of Sponsoring LIR for Independent Resources (https://www.ripe.net/publications/docs/ripe-603/ <https://www.ripe.net/publications/docs/ripe-603/>) In order to avoid generating too much traffic on the APWG ML, I kindly ask that you send your responses directly to me at pdo(a)ripe.net answering the following questions. *Content structure * In the new policy document: A) Would including only the Abstract, Introduction and Policy Text from each existing document be enough? B) Could each document’s Rationale, Attribution and Acknowledgements be referenced via footnotes? C) Could the Definitions and Goals be published in a separate document? *Preferred way forward* Which approach would you prefer? 1) The RIPE community to set up a Task Force to redact new documents 2) The RIPE community to propose new documents for discussion through the PDP 3) The RIPE NCC to propose new documents for discussion through the PDP 4) Another approach (it could be that you are fine with leaving thing as they are, but if you have another idea, please explain) Please share your thoughts by 31 May. I will compile and summarise the feedback received and share it with the WG. Thank you in advance for your time and input. Kind regards, Angela Dall’Ara Policy Officer RIPE NCC [1] https://ripe90.ripe.net/archives/video/1611/(from 10:15 )

1 1

2025-01 End of Discussion Phase (ASN assignment criteria revisited)
by Leo Vegoda 11 Jun '25

11 Jun '25

Dear Address Policy WG, As you’ve seen, Urban and Tobias are working on an update to 2025-01: ASN assignment criteria revisited. They will take account of the feedback received. This is a summary of the feedback. Eight people expressed support for the proposal on the mailing list and at the microphone at RIPE 90. In addition to supporting the proposal they almost unanimously requested that the text should be simplified. A new discussion phase will start when the new version of the proposal is published. The RIPE NCC will update the proposal page and announce the publication when the new draft is ready. You can find all current policy proposals at: https://www.ripe.net/community/policies/current-proposals/ You can read our Policy Development Process at: https://www.ripe.net/publications/docs/ripe-781/ Kind regards, Leo Vegoda, for the Address Policy WG co-chairs

1 0

2025-01 New Policy Proposal (ASN assignment criteria revisited)
by Angela Dall'Ara 05 Jun '25

05 Jun '25

Dear colleagues, A new RIPE Policy Proposal, 2025-01, "ASN assignment criteria revisited" is now available for discussion. This proposal aims to to simplify requirements for new ASNs, while ensuring that the requirements are enforceable in practice and preventing the exponential exhaustion of 32-bit ASN space. You can find the full proposal at: https://www.ripe.net/community/policies/proposals/2025-01/ As per the RIPE Policy Development Process (PDP), the purpose of the Discussion Phase is to discuss the proposal and provide feedback to the proposers. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal. The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781 We encourage you to review this proposal and send your comments to address-policy-wg(a)ripe.net before 4 June 2025. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

9 13

2024-02 Review Phase (IPv6 Initial Allocations /28)
by Angela Dall'Ara 23 May '25

23 May '25

Dear colleagues, Policy proposal 2024-02, "IPv6 Initial Allocations /28 ", is now in the Review Phase. This proposal aims to change the initial IPv6 allocation size from /29 to /28 and allow one IPv6 allocation extension per member to /28 without justification. This proposal has been updated and it is now at version 3.0. The main difference from version 2.0 is that one IPv6 allocation extension up to /28 without justification is allowed per member instead of per LIR. The RIPE NCC has prepared an impact analysis on this proposal to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/community/policies/proposals/2024-02/ https://www.ripe.net/participate/policies/proposals/2024-02#impact-analysis And the draft document at: https://www.ripe.net/participate/policies/proposals/2023-04/draft As per the RIPE Policy Development Process (PDP), the purpose of this four-week Review Phase is to continue the discussion of the proposal taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and to send any comments to address-policy-wg(a)ripe.net before 11 June 2025. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

8 11

FYI: Address Policy List now on moderation
by Franziska Lichtblau 20 May '25

20 May '25

Dear Address Policy Working Group, due to recent events we as chair team decided to put this list on moderation. Some of your posts may be delayed. Thanks for your understanding, Franziska on behalf of the Address Policy co-Chairs

1 0

Posts in NANOG
by info＠netstyle.io 16 May '25

16 May '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I kindly bring my following two linked posts in NANOG to the attention of the RIPE community: https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/25GSIL2… https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/LBIRATB… Kind Regards, Elad -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsG5BAEBCgBtBYJoJzmXCZCAS+uEnipSW0UUAAAAAAAcACBzYWx0QG5vdGF0 aW9ucy5vcGVucGdwanMub3JnAp3tbij5bDCxR4d9UVJ3Ntg5owLa3wDEL9Tt nqr1c5sWIQTD50Y2bI5NSOj/nnWAS+uEnipSWwAAy8AP/2ztVrMghrN7Pn40 c75LaNy5ia4fMUOu/LRZwOa0LyLAmIQUFtfxy/Pn9PxnP/wkqfGYyg3ReRFQ u2V3Q5Zs29tL+SgTKE0WZvzCFa/z9rGJfE5/Hx7nTD2s6s+ldoRUUJkb0ian JL+NqIEc9jlZJJ55MkGgcvjlCbnRXiyKk5tWnE01YeLrnMmcsAe3sJMiNt2Y xhnMwsKxpTE39z7DTHT0rGpS22CdNBsLxe+peNx8SlBW7JXfQziyT/05nu7g 9cKFWioQ+JExQ14URM1O/tiQ0jxIEKUtG5Gxm6sUlrrmy2dw8I776FPYU5Ab 02dF4c7l9OSax+/JW9QsHeKaNegq3kzMAbxCTtMqNix75MgDujeAEEp3tAHN cd4qLLgrHcS+XEc6Lekg23CKVcqVlD38rXILI4yOm4kjhOBY6lf0KU4/QzmF dYwSuW3+SubpHS1fUlCYJSds7RnMsoy++a54hf0J/csDbQked1zVSZ+eMmYP SBqnJ3X3NbBq6jQ8Ciou4llgs73yn529umqN7N/OEd/TA8K33ScyRKxgcAwC 7A9VHQlWG8Zrwt8s3LXIjuURTFICoiiD0wsk+K/xN1QGlG4lyPpGl1dB99yR VSY9qm8hZg0fdwoZKkKRrhGfHNIitKWO4Ew+GSPwGTosa6Ns0BlgEI9PT2uj bEt2pLEa =Z78a -----END PGP SIGNATURE-----

3 4