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] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Previous message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Next message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Mar 28 15:13:45 CET 2014
Hi, >> Once a /25 is transferred the original allocation changes and the NCC cannot delegate the reverse for the whole /24 that contains the /25 to the LIR. It's not the LIR's address space anymore. > > You are right. Basically what you are saying, the NCC would not approve > the transfer as long as the above is not solved. That would seem appropriate to me. I'm not sure what the current procedures for this are at the moment, but the end result should be like that, yes. > I am wondering whether this is (or should be) enforced in case of transfers > out of a /16 allocation. Why not? It is an issue for any delegation that is not on a multiple of 8 bits (/8, /16 and /24). We currently already have reverse tree delegations of multiple /24s for those that have an allocation from a /17 to a /25. That isn't new. The only new part would be to re-organise some parts of the tree before transferring the corresponding address space. Cheers, Sander
- Previous message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Next message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]