[ppml] Policy Proposal: IPv4 Transfer Policy Proposal
Scott Leibrand
sleibrand at internap.com
Mon Feb 11 23:33:49 EST 2008
- Previous message: [ppml] Policy Proposal: IPv4 Transfer Policy Proposal
- Next message: [ppml] Policy Proposal: IPv4 Transfer Policy Proposal
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Williamson wrote: > On Mon, Feb 11, 2008 at 11:56:29AM -0500, Howard, W. Lee wrote: > >>> 8.4.3 Conditions on the IPv4 address block to be transferred: >>> >>> * The IPv4 block must comply with applicable ARIN requirements, >>> including minimum allocation size (i.e. NRPM 4.2.2., 4.2.4., >>> 4.3.2., 4.3.6.). However, an IPv4 allocation or >>> assignment of /24 >>> or larger, but smaller than the current minimum >>> allocation size, >>> may be transferred as a whole resource, but may not be >>> subdivided. >>> >> Is this intended to mean swamp space can remain swampy, but other >> space can't be subdivided in /24? It looks like it says the block >> must meet minimum transfer size, unless it's a /24 or larger. >> > > I'm also a bit confused by this. It does seem to imply that I cannot > get a PI /24 from ARIN directly, but I could get one transferred to > me. That seems unexpected. If the intent is to permit resources > already allocated at some size that is presently below the minimum > requirements (i.e., the swamp), this should get some different > verbiage. If the intent is really to permit transfers down to the /24 > limit, we should go ahead and change the minimum allocation and > assignment sizes to match. > Yes, that is the intent: to encourage efficient use of unused swamp space by allowing it to be transferred after IANA exhaustion. This policy does not do anything to change the minimum allocation size: that may be a good idea, but should be a separate policy proposal IMO. -Scott
- Previous message: [ppml] Policy Proposal: IPv4 Transfer Policy Proposal
- Next message: [ppml] Policy Proposal: IPv4 Transfer Policy Proposal
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the PPML mailing list