[arin-ppml] transfer conditions

[Ted Mittelstaedt]

On 5/8/2011 10:48 AM, Jimmy Hess wrote:
> On Sat, May 7, 2011 at 11:04 PM, Matthew Kaufman<matthew at matthew.at>  wrote:
>
>> Why don't we just start by disallowing all transfers smaller than, say, /19... and then adjusting that downward (in block size... upward in mask length) as the market shows that it can't function with the simultaneous combination of needs-justification-requirements and minimum-block/aggregate-sizes?
>
> Why don't we start by disallowing all transfers smaller than the
> minimum allocation size for the block?
>
> And  use  /22  as the minimum allocation size for any legacy block of
> which  /16s were assigned'
> /20 as the minimum allocation size for any legacy block of size /8  or
> shorter were assigned?
>
> ARIN allocates prefixes longer than /19,  so  /19  restriction seems a bit much
>

I would be willing to accept a /24 minimum size transfer AS LONG AS it
was tied to a mandate for the receiving party to sign an RSA.

I wouldn't like it, but obviously ARIN does not like forcing the 
recieving party to sign an RSA, so this way, we both get equally
something that we don't like.

Ted

> --
> -JH
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.