ASN and Peering Problem

Wed Dec 8 21:40:03 UTC 2004

Assuming that this is in North America (this is NAnog, afterall), they
should probably apply to ARIN for both the /22 (if they can justify that
much space) and the ASN, or, get the ASN from ARIN and the space from you.

As of policy 2002-3, ARIN will assign /22s to end users that have need of
a unique routing policy and meet other tests necessary for such an 
assignment.
These are the same tests you would be required to hold them to for you to
assign them a PA /22.

Owen

--On Wednesday, December 8, 2004 13:59 -0600 Adi Linden <adil at adis.on.ca> 
wrote:

>
> We currently have two /19 that we advertise on a single ASN. A client
> would like to obtain /23 or /22 from us. This is not a problem, except
> that their primary internet provider is someone else, other than us.
> I think that they would need to have their own ASN to advertise their
> portion of our ip space to their peers.
>
> My question is, should we provide the ASN or should they apply for an ASN?
> What is the minimum block considered routable, is it reasaonable to
> advertise a /23 on its own ASN?
>
> Are there any other solutions I haven't thought of?
>
> Thanks,
> Adi

-- 
If this message was not signed with gpg key 0FE2AA3D, it's probably
a forgery.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20041208/773c6169/attachment.sig>