This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2023-01 New Policy Proposal (Reducing IXP IPv4 assignment default size to a /26)
- Previous message (by thread): [address-policy-wg] 2023-01 New Policy Proposal (Reducing IXP IPv4 assignment default size to a /26)
- Next message (by thread): [address-policy-wg] 2023-01 New Policy Proposal (Reducing IXP IPv4 assignment default size to a /26)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Wed Jan 11 15:18:54 CET 2023
Dear Radu, I'm happy to provide some clarification. The current IPv4 IXP policy states "Once they require a larger assignment, they must return their current one (or existing PI used as an IXP peering LAN)" [1] It is the RIPE NCC's understanding that this condition applies to IXP assignments provided under this policy and to older regular PI assignments if they were provided exclusively for IXP peering LANs. Other IP ranges that might be used for IXP services, such as parts of an IPv4 allocation (ASSIGNED PA), do not fall under this condition. As you mentioned, the proposed new wording on this topic is very similar, and the RIPE NCC would apply the same understanding if this proposal would become a RIPE policy. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://www.ripe.net/publications/docs/ripe-733#61 On 11/01/2023 12:14, Radu-Adrian FEURDEAN wrote: > Hello, > > Would somebody from NCC be able to clarify how would the wording "must return the existing assignment (or existing PI used as an IXP peering LAN)" (proposed text 6.1.4 and 6.1.5) be interpreted/implemented for the case of IXPs that use ASSIGNED PA space for the peering LAN. OK, it's the same wording that already exists in the current policy, but a clarification is welcome. > > Otherwise the proposal seems reasonable. > > On Mon, Jan 9, 2023, at 11:40, Angela Dall'Ara wrote: >> Dear colleagues, >> >> A new RIPE Policy Proposal, 2023-01, "Reducing IXP IPv4 assignment >> default size to a /26" >> is now available for discussion. >> >> The goal of this proposal is to extend the lifetime of the IXP IPv4 >> address pool and to motivate IXPs to implement the exchange of IPv4 >> routing information over IPv6. >> >> You can find the full proposal at: >> https://www.ripe.net/participate/policies/proposals/2023-01 >> >> 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 proposer. >> >> 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 at ripe.net before 7 February 2023. >> >> >> Kind regards, >> >> Angela Dall'Ara >> Policy Officer >> RIPE NCC >> >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or >> change your subscription options, please visit: >> https://mailman.ripe.net/
- Previous message (by thread): [address-policy-wg] 2023-01 New Policy Proposal (Reducing IXP IPv4 assignment default size to a /26)
- Next message (by thread): [address-policy-wg] 2023-01 New Policy Proposal (Reducing IXP IPv4 assignment default size to a /26)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]