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/address-policy-wg@ripe.net/
[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
Thu Jan 12 13:36:24 CET 2023
Dear Radu, Yes, that is correct. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC On 11/01/2023 15:41, Radu-Adrian FEURDEAN wrote: > On Wed, Jan 11, 2023, at 15:18, Marco Schmidt wrote: >> 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. > So when the time comes (and provided the other conditions are met) it would be possible to request a /23 in grow an IXP currently using a /24 "ASSIGNED PA", with nothing to return to the NCC (the rest of the allocation being in use). > > Is that correct ? >
- 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 ]