[101741] in North American Network Operators' Group
Re: request for help w/ ATT and terminology
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Wed Jan 16 18:42:43 2008
Date: Wed, 16 Jan 2008 18:41:28 -0500
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <49900C758A716C499CE8C56BF0CB52710814D94B@newexch01.ohana.watg.com>
Errors-To: owner-nanog@merit.edu
--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Some networks (of note, the larger ones) have registered a "customer
ASN". The idea is that networks advertised from their backbone ASN
should only be the ones they own, and all customers who have no ASN
use the customer ASN to originate their block. In most cases the
contract prohibits using the customer ASN with another provider;
it is only to be used to single home to the one network.
I have no personal experience with AT&T in this configuration, but
with several other networks they would prefer an eBGP session where
they send you a default and you send them your prefix using the ASN
they assign. Aside from keeping the prefixes segregated by ASN it
also makes the routing policy a lot simpler. Typically things
announced by the backbone ASN may appear in prefix lists across the
network, while the customer ASN is "just another session".
One of the more interesting "big network" problems is the front
line support tend to not be creative thinkers, and also tend to
believe their internal terminology is industry standard speak. This
can make it difficult to get what you want.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFHjpYnNh6mMG5yMTYRAtTpAJoDLC3688QL7QVoi/a6e0D7mgQTPgCePXUc
tZch/zWNqDFnnzjNyjixekc=
=pBS5
-----END PGP SIGNATURE-----
--Dxnq1zWXvFF0Q93v--