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

DRAFT ASN assignment critera revisited
by Urban Suhadolnik 02 Apr '25

02 Apr '25

Dear Colleagues, Following RIPE 89 Address policy WG, I was asked to prepare a new policy for ASN assignment criteria together with Tobias. We've compared the ASN assignment criteria at other RIRs, current proposals at other RIR and followed various conversations at RIPE community events. After some internal feedback from Alex, Leo and PDO we feel that this draft is ready for the mailing list. I would like to ask all of you for feedback on the proposal and on the text of the proposal. Best, Urban and Tobias _____________________________ Summary of Proposal This policy proposal changes the requirements for ASN assignments. Under the new policy, any organization or LIR (in case of multiple LIR per ASN) may request a single ASN without justification. Additional ASNs can be assigned if the requester provides a unique external routing policy and demonstrates peering with a third party. The proposed changes reflect the reality that the current requirements are unenforceable in practice [1] and that ASNs are no longer a scarce resource since the complete introduction and global acceptance of 32-bit ASNs. The aim of this policy is to simplify requirements for new ASN, while making the requirements enforceable in practice and avoiding exponential burn of 32bit ASN space. [1] - Personal ASN Open House Recap - RIPE NCC - Page 5 https://ripe89.ripe.net/wp-content/uploads/presentations/88-Personal-ASN.pdf <https://ripe89.ripe.net/wp-content/uploads/presentations/88-Personal-ASN.pdf> Policy text: Current policy text *2.0 Assignment Criteria* In order to help decrease global routing complexity, a new AS Number should be used only if a new external routing policy is required, see RFC1930. A network must be multihomed in order to qualify for an AS Number. When requesting an AS Number, the routing policy of the Autonomous System must be provided. The new unique routing policy should be defined in RPSL language, as used in the RIPE Database. The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE NCC either directly or through a sponsoring LIR. AS Number assignments are subject to the policies described in the RIPE NCC document entitled “Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region”. New policy text *2.0 Assignment Criteria* Any organization OR LIR, in case an organization has more than one LIR, may be issued a single Autonomous System Number (ASN) upon request. Organizations and LIRs may be issued additional ASNs. Requirements for additional ASNs are: * Unique external routing policy of the Autonomous System must be provided. The uniqueness of the routing policy includes the announced prefixes. * Autonomous System must peer with a third party. When requesting an AS Number to be visible in the GRT, the routing policy of the Autonomous System must be provided. The new unique routing policy should be defined in RPSL language, as used in the RIPE Database. Otherwise, documentation on the non-visible purpose, e.g., a reference to the assigned IXP LAN prefixes, must be provided. Reasonable periodic use cases MAY be allowed. A benefit statement for such MUST be provided. The requester has 6 months after the ASN has been issued to fulfil the criteria for which the application was approved. Approval of an additional ASN MAY depend on fulfilment of criteria and up-to-date documentation on existing ASNs. In case of an ASN visible in the GRT, RIPE NCC confirms that the ASN fulfils the criteria by checking publicly visible state in the GRT. In case of off-GRT ASN, RIPE NCC may ask for operational proof of fulfilling the criteria. Failing to provide sufficient proof is considered as not fulfilling the criteria. The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE NCC either directly or through a sponsoring LIR. AS Number assignments are subject to the policies described in the RIPE NCC document entitled “Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region." Rationale There are valid technical reasons for having a single homed ASN. BGP and RPSL has appeared to be a very robust way of exchanging routing information. Schemes where customer's have their own IP space would benefit by using a dedicated ASN to communicate routing information over BGP. Conservation measures currently implemented are not really helpful anymore. They reduce visibility and make operating and troubleshooting of networks more complex. Arguments supporting the proposal Four octet (32 bit) ASNs were defined in May 2007 in RFC 4893. It has taken several years for routing equipment in general use to catch up, but with 32 bit AS numbers, ASN are not a scarce resource anymore. IANA has assigned 402332 ASN to RIRs which is ~0.01 % of available 32 bit ASN space. While RIRs have assigned only around, 88400 to network operators, which represents ~0,002 % of available 32 bit ASN. Our policies should reflect that, and we should utilize number resources in such a way to help network operators reduce operational complexity and increase visibility for operating and troubleshooting networks. Lastly, the current ASN requirements have appeared to be unenforceable in practice. Many AS start by fulfilling the multihomed requirement, but then turn single-homed over time, while others have never become multihomed in the first place. Half of allocated ASN by RIPE don't fulfil the requirements [1] This proposal removes the requirement for the first Autonomous System Number for an organisation or LIR (in case an organisation has more than one LIR) and introduces a set of requirements that are reasonable, will not deplete the pool of available ASN and be enforceable for RIPE NCC. [1] - Personal ASN Open House Recap - RIPE NCC - Page 5 https://ripe89.ripe.net/wp-content/uploads/presentations/88-Personal-ASN.pdf <https://ripe89.ripe.net/wp-content/uploads/presentations/88-Personal-ASN.pdf> Arguments against the proposal Simplified availability of ASN will result in an increase of Autonomous Systems on the GRT. While depletion of available ASN will not be a problem in the foreseeable future, there could be an increase of complexity of the GRT which will increase the requirements on processing power and memory of network equipment. Counterarguments: * An increase of Autonomous systems might not have as big of effect on hardware requirements as one might think at first. Conservation measures for cases presented in RFC1930 and RFC2280 and others conserve only the AS number, and do not conserve the processing power and memory needed to process the announced prefixes. When a foreign prefix (e.g. PI) as announced (via e.g. private ASN) from an AS (e.g. ISP) it still creates a separate entry in the routing table. * This policy shouldn't cause any significant increase of complexity of GRT, because best practices from RFC1930 were not used. New technologies built on easy availability of AS numbers could exponentially increase the request rate for new AS numbers Counterarguments: * New RIPE NCC fees, particularly "per ASN" fee, mitigates this to some extent. However, current per ASN fee of 50€, would in practice not stop such technology from being developed based on cost alone. On the other hand, an increase of fees would jeopardize small and private ASN end-users. Risk of mass (hundreds or thousands) ASN requests exist. The effect of this policy should be reviewed within a reasonable timeframe after implementing.

8 31

New Address Policy WG Co-Chair Nomination Announcement
by Alex Le Heux 27 Mar '25

27 Mar '25

Dear Address Policy WG, We are delighted to announce that we have a candidate for the open Address Policy WG co-chair seat: Franziska Lichtblau. The Working Group will make its selection during the Address Policy WG session at RIPE 90 in Lisbon. As a reminder, the Working Group selects a new co-chair every year. It is not too early to start thinking about nominating yourself for next year. If you are interested in serving as a co-chair of this Working Group, you are welcome to speak to Leo or me, to learn what we do off-list. Mirjam and Niall, as RIPE Chair and Vice Chair are also happy to answer any questions you have. And, you can also seek input from RIPE NCC staff and previous co-chairs. Our selection process is documented here: https://www.ripe.net/community/wg/active-wg/ap/address-policy-wg-chair-sele… You can also read the Job Description here: https://www.ripe.net/publications/docs/ripe-692/ A RIPE Working Group Chair Training course is available at the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16 Kind regards, Alex Le Heux, for the co-chairs

1 0

2024-02 New Version Policy Proposal (IPv6 Initial Allocations /28)
by Angela Dall'Ara 27 Mar '25

27 Mar '25

Dear colleagues,    RIPE policy proposal 2024-02, "IPv6 Initial Allocations /28 " is now available for discussion again.   This proposal aims to change the initial IPv6 allocation size from /29 to /28.  Following the last round of discussion, this proposal has been updated and it is now at version 2.0.  The main differences from version 1.0 are that it allows the provision without additional documentation of initial allocations from /32 up to /28, instead of /32 or /28, and only a single existing allocation extension 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 four-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 28 March 2025.     Kind regards,    Angela Dall'Ara   Policy Officer   RIPE NCC

7 11

Status of 2024-01 Revised IPv6 PI Assignment Policy ?
by Jori Vanneste 13 Mar '25

13 Mar '25

Dear Address Policy WG, There was a lot of traction related to 2024-01 during the last few months of 2024, but it seems this has fallen silent. Does anybody know the current status of said proposal? I'm asking this as the policy would help me quite a bit in regards to my network, as I currently have 9 different /48 PI assignments I would like to consolidate, preferrably without renumbering. (both objects and DNS-wise, with the nibble boundaries and whatnot) I also believe I am far from the only network with this issue, as some of the customers at my employer have noted similar issues at the time. Hence, I was following this proposal quite closely, and find it unfortunate to see no further information on it. I'm aware the PDP states that a 4-week inactivity constitutes a withdrawal, but I am curious if this is the case here? Looking forward to any further information or replies. :) Kind regards, Jori Vanneste

3 3

Nominations Open: New Address Policy WG Co-Chair Sought
by Alex Le Heux 05 Feb '25

05 Feb '25

Dear Address Policy Working Group, You can now nominate yourself as a potential co-chair for the Address Policy WG. You do this by writing to apwg-chairs(a)ripe.net with your name and your affiliation. Please do not self-nominate on this list. Send your nomination by 15 March. We will publish the list of candidates on 24 March. The candidates may then introduce themselves to the list. The Working Group will make its selection during the Address Policy WG session at RIPE 90 in Lisbon. If you are interested in serving as a co-chair of this Working Group, you are welcome to speak to Leo or me, to learn what we do off-list. Mirjam and Niall, as RIPE Chair and Vice Chair are also happy to answer any questions you have. And, you can also seek input from RIPE NCC staff and previous co-chairs. Our selection process is documented here: https://www.ripe.net/community/wg/active-wg/ap/address-policy-wg-chair-sele… You can also read the Job Description here: https://www.ripe.net/publications/docs/ripe-692/ A RIPE Working Group Chair Training course is available at the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16 Kind regards, Alex Le Heux, for the co-chairs

2 1

New Address Policy WG Co-Chair Sought (Timeline)
by Leo Vegoda 06 Jan '25

06 Jan '25

Dear Address Policy WG, This is the timeline for selecting a new co-chair for the Address Policy WG. ◆ 3 February - 15 March – Candidates self-nominate by mailing apwg-chairs(a)ripe.net ◆ 24 March - 11 May – Candidates names are published, candidates can describe themselves to the list ◆ 12 - 16 May – The WG selects the new co-chair during the Address Policy WG session at RIPE 90 in Lisbon If you are interested in serving as a co-chair of this Working Group, you are welcome to speak to Alex or me, to learn what we do off-list. Mirjam and Niall, as RIPE Chair and Vice Chair are also happy to answer any questions you have. And, you can also seek input from RIPE NCC staff and previous co-chairs. Our selection process is documented here: https://www.ripe.net/community/wg/active-wg/ap/address-policy-wg-chair-sele… You can also read the Job Description here: https://www.ripe.net/publications/docs/ripe-692/ A RIPE Working Group Chair Training course is available at the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16 Kind regards, Leo Vegoda, for the co-chairs

1 0

RIPE 89 Address Policy WG - Draft Minutes Published
by Leo Vegoda 18 Dec '24

18 Dec '24

Dear Address Policy WG, We’ve received the minutes of the RIPE 89 meeting and the RIPE NCC has published them for your review. https://www.ripe.net/community/wg/active-wg/ap/minutes/ripe-89-address-poli… We'd like to thank Alun and Antony 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 & Alex le Heux Address Policy WG co-chairs

1 0

Authorised ASN attribute
by Lu Heng 10 Dec '24

10 Dec '24

Hi During leasing of IPs, and varieties of routing database, often causing confusions among upstream and we have spend significant amount of time help for verification. why not we include an authorises ASN attribute in assignment to simplify the authorization? An idea for discussion -- -- Kind regards. Lu

3 2

New Address Policy WG Co-Chair Sought
by Leo Vegoda 26 Nov '24

26 Nov '24

Dear Address Policy WG, As we announced at RIPE 89, we want to recruit a third co-chair. We will ask the Working Group to finalise its selection at RIPE 90, in Lisbon. We will communicate a selection timeline early in 2025. If you are interested in serving as a co-chair of this Working Group, you are welcome to speak to Alex or me, to learn what we do off-list. Mirjam and Niall, as RIPE Chair and Vice Chair are also happy to answer any questions you have. And, you can also seek input from RIPE NCC staff and previous co-chairs. You can also read the Job Description here: https://www.ripe.net/publications/docs/ripe-692/ A RIPE Working Group Chair Training course is available at the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16 Kind regards, Leo Vegoda, for the co-chairs

1 0

2024-01 New Policy Proposal (Revised IPv6 PI Assignment Policy)
by Angela Dall'Ara 21 Nov '24

21 Nov '24

Dear colleagues, A new RIPE Policy Proposal, 2024-01, "Revised IPv6 PI Assignment Policy" is now available for discussion. This proposal aims to define End Sites and requirements for “IPv6 PI Assignments” and “Assignments from IPv6 Allocations”, clarifies permitted use cases and introduces IPv6 PI issuance at the Nibble boundary and new principles for aggregation and registration. You can find the full proposal at: https://www.ripe.net/community/policies/proposals/2024-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 proposer. Taking in consideration the holiday period, the Address Policy WG Chairs decided to allow five weeks for this initial phase. At the end of the Discussion Phase, the proposer, 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 18 September 2024. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

12 31