[arin-ppml] REVISED: Draft Policy ARIN-2012-8: Aligning 8.2 and 8.3 Transfer Policy
owen at delong.com
Mon Nov 19 20:22:39 EST 2012
+1 -- I support Dave's suggested rewording.
On Nov 19, 2012, at 12:38 PM, David Farmer <farmer at umn.edu> wrote:
> On 11/19/12 13:48 , Chris Grundemann wrote:
>> On Mon, Nov 19, 2012 at 12:26 PM, Owen DeLong <owen at delong.com> wrote:
>>> 3. Suggest updating the minimum transfer size specification to reflect "Current ARIN minimum allocation or assignment policy as defined in section 4 or section 6 or the original assignment size, whichever is smaller." since over time we have seen changes in these minimums and I would prefer that the transfer policy automatically track other policy changes.
>> I believe that would effectively allow everyone to transfer v4/28s
>> today based on 4.10 - is this something the community wants to allow?
>> More feedback in this area would also be helpful.
> No, I think Owen is mostly right, but I would change the order and simplify for additional clarity to;
> "* The minimum transfer size is, the original allocation size or the current applicable minimum allocation size in current policy, whichever is smaller."
> I believe that means you can transfer the original allocation size what ever it is and if you want to transfer something else it must conform to current policy, that means /28 within the range reserved in 4.10 and /24 for a small multihomed end user, or a /22 for a multihomed ISP, etc...
> Put another way, if you are doing only a partial transfer then you can't break things up smaller than current policy allows, and if the current block is already smaller, than you can only transfer the whole block.
> David Farmer Email: farmer at umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029 Cell: 1-612-812-9952
More information about the ARIN-PPML