[arin-ppml] transfer conditions

Ted Mittelstaedt tedm at ipinc.net
Mon May 9 23:54:56 EDT 2011


On 5/9/2011 6:09 PM, Matthew Kaufman wrote:
>
> On May 9, 2011, at 3:49 PM, Ted Mittelstaedt wrote:
>
>> 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.
>
>
> All of the versions of the LRSA, and all of the modifications of "The RSA" are "an RSA"

oops, good catch!  Damn I'm going to have to get sneakier in my thinking!

Ted

>>
>> I wouldn't like it, but obviously ARIN does not like forcing the recieving party to sign an RSA,
>
> No, they're fine with "an RSA", just not "The RSA and Only The RSA"
>
> Matthew Kaufman
>
>




More information about the ARIN-PPML mailing list