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

[Dawn Martin]

ARIN's current justifications are:
a) Unique Routing Policy

   Please explain how your routing policy is different from your provider.

b) Multi-homed Site

   If your organization is currently multi-homed, please explain exactly
   how you are connected to the Internet to include the following
   information:
 
         i)  Exterior gateway protocol to be used
        ii)  The IP network addresses that will make up your AS
       iii)  Technical point of contact information for each of your
             upstream providers/peers should include:

In this discussion we are talking about b. 

Most of our cutomers are using BGP, for ARIN to issue the ASN the
customer HAS to have the IP blocks and the tech contacts.

So, if we require the customer to have an ASN to get the block
and ARIN requires them to have a netblock before they get the ASN.
Where do they go? APNIC?

Either, this policies wording needs to change or ARIN's jusitifcation
for an AS number needs to change. 

Which is it? I would rather see this policies wording changed.

-Dawn Martin


Quoth Sweeting, John (John.Sweeting at teleglobe.com):
> 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
> 
> 
> On Mon, Nov 05, 2001 at 01:16:18PM -0700, Barbara Roseman wrote:
> > During the ARIN Advisory Council meeting of October 30th the AC voted to
> > accept this policy and forward it to the ARIN BOT with the following
> > amendments
> > 
> > Original Proposal:   A downstream customer's multihoming requirement will
> >                 serve as justification for a /24 reassignment from
> >                 their upstream ISP regardless of host requirements.
> > 
> > -Customer must cite their asn as justification for address space
> > -Customer may receive space from only one of its upstream providers
> > without additional justification
> > 
> > This a last call for community comment on this policy prior to the
> > ARIN Board of Trustees review of the proposed policy. This policy
> > will be posted on the ARIN website and the ARIN Public Policy email
> > list. Please send your comments to ppml at arin.net. This last call
> > will expire on 23:59 EST 19 Nov 16, 2001.
> > 
> > 
> > ---
> > Barbara Roseman
> > Sr. Manager, FACT
> > Global Crossing
> > Office: +1 408-542-0147
> > Cell: +1 917-498-1677
> > broseman at gblx.net
> > 
> > 
> > 
> > 
> >