[76380] in North American Network Operators' Group
Re: ASN and Peering Problem
daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Dec 8 16:40:24 2004
Date: Wed, 08 Dec 2004 13:40:03 -0800
From: Owen DeLong <owen@delong.com>
To: Adi Linden <adil@adis.on.ca>, nanog@merit.edu
In-Reply-To: <Pine.CYG.4.58.0412081345530.2564@citabria>
Errors-To: owner-nanog-outgoing@merit.edu
--==========9B5B4D8D98E12303A8DC==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=20
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@adis.on.ca>=20
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
--=20
If this message was not signed with gpg key 0FE2AA3D, it's probably
a forgery.
--==========9B5B4D8D98E12303A8DC==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFBt3Szn5zKWQ/iqj0RAqUZAJ4y8E8ISvhS77yGem4fLeAvT1OFUwCePgQH
xDxJ5kxkOS9dmpfqgwvnZTU=
=xpyo
-----END PGP SIGNATURE-----
--==========9B5B4D8D98E12303A8DC==========--
