[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 MinimumAllocation 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 ]
Sascha Luck
lists-ripe at c4inet.net
Fri Mar 28 17:41:44 CET 2014
All, On Mon, Mar 24, 2014 at 02:18:44PM +0100, Marco Schmidt wrote: >You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2014-01 > >We encourage you to review this proposal and send your comments to I don't think this proposal takes into account operational reality. The fact of the matter is, that there is a lower limit to what allocation size is operationally useful to a LIR (unless the routing community is prepared to accept /32s in the DFZ). Add to that the extra complexity of reverse delegating </24 zones that is mentioned elsewhere in the thread and the likely outcome is a mess. I think the better way to do this would be to: - retain the /22 min-alloc size until the last /8 is gone - possibly change the *transfer* policies to allow transfers of /24< x </22 - implement something like 2014-01 but with a min-alloc size of /24 when that happens - review after a year(?) with a view to whether any smaller allocation size is actually *operationally useful* to LIRs I do not want to go back to the not-so-long-ago days of having to concoct fiction in order to get a useful amount of resources out of the NCC. rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the MinimumAllocation 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 ]