corrected: Policy 2001-2, Multihoming is sufficient justifica tion for /24 from provider (fwd)

[Barbara Roseman]

The current ARIN ASN registration guidelines read as follows:

"In order to be assigned an ASN, each requesting organization must provide
ARIN with verification that it has one of the following:

"A unique routing policy (its policy differs from its border gateway
peers)
"A multi-homed site.

"ASNs are issued based on current need. An organization should request an
ASN only when it is already multi-homed or will immediately become
multi-homed."

The "immediately become multi-homed" section seems most relevant to this
discussion. I would suggest that for the purposes of the ASN request
template, an acceptable statement for b) ii)  could be "/24 to be provided
by upstream provider x or y".

I agree with Cathy that we need to get Registration Services to make the
call on this one so we aren't creating what Einar identified as a Catch
22.

-Barb

On Tue, 6 Nov 2001, Sweeting, John wrote:

> agree, the customer should have the ASN from ARIN before being considered
> for approval under this policy by their providers.
>

> -----Original Message-----
> From: CJ Wittbrodt [mailto:cjw at duchess.groovy.com]
> Sent: Monday, November 05, 2001 7:04 PM
> To: Sweeting, John
> Cc: 'Einar Bohlin'; ppml at arin.net
> Subject: Re: corrected: Policy 2001-2, Multihoming is sufficient
> justifica tion for /24 from provider (fwd)
>
>
>
> You know ISPs already get this informationfrom their customers
> to determine whether they are multihomed or not and they already
> give the customer a /24 based on that.  They have to provide
> that justification before they can get more address space from
> ARIN.  If the customer has to go to ARIN, prove it's multihoming
> to get an ASN, then it should be able to use that ASN and justification
> to get the block.  I think what we need is clarification of what
> ARIN requires of someone requesting an ASN.  Sure someone could lie
> but if they are going to they already are to get the ASN.  I suspect
> that ARIN requires some proof like signed contracts, etc, to verify
> that they are going to multihome.  Wouldn't that be enough?
>
> ---CJ
>
>     From: "Sweeting, John" <John.Sweeting at teleglobe.com>
>     Subject: RE: corrected: Policy 2001-2, Multihoming is sufficient
> justifica
> 	     tion for /24 from provider (fwd)
>     That would leave a big hole for anyone to say that they intend to become
>     multi-homed. They should already have address space assigned to them but
>     probably in a much smaller block, such as a /28 or so, and then once
> they
>     become multi-homed they would want a /24 so they would have a better
> chance
>     of not being filtered. My feeling is that they should have an ASN before
>     being able to justify a /24 under this policy.
>
>     -----Original Message-----
>     From: Einar Bohlin [mailto:ebohlin at UU.NET]
>     Sent: Monday, November 05, 2001 5:40 PM
>     To: ppml at arin.net
>     Subject: Re: corrected: Policy 2001-2, Multihoming is sufficient
>     justification for /24 from provider (fwd)
>
>
>     The following requirement makes the policy unworkable
>     and should be replaced:
>
>     "-Customer must cite their asn as justification for address space"
>
>     There's a catch-22 here in that ARIN won't give
>     the customer an ASN until the customer has a net,
>     and the ISP won't be able to give the customer the /24
>     until the customer can show their ASN.  This
>     won't work.
>
>     It should be "-Customer cites intent to multihome as
>     justification for address space".  This lets ARIN
>     continue to do their job of registering AS numbers,
>     and allows ISPs to conduct business with their customers.
>
>     FYI I tried to see the original wording, but the
>     link on the ARIN main site is broken (LAST CALL:
>     Policy 2001-2... points to ASO election results).
>
>     Regards,
>
>     Einar Bohlin
>     IP Planning Analyst
>     WorldCom, Inc.
>     Phone: USA 703 886-7362
>     email: einar.bohlin at wcom.com
>