[107613] in North American Network Operators' Group
Re: why not AS number based prefixes aggregation
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Mon Sep 8 11:36:49 2008
Date: Mon, 08 Sep 2008 17:36:39 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <75cb24520809080830v212f3761g3807aa95fcf1144b@mail.gmail.com>
Cc: NANOG <nanog@merit.edu>
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDC22B1513628A3AFC6BD5583
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Christopher Morrow wrote:
> On Mon, Sep 8, 2008 at 9:20 AM, yangyang. wang <wyystar@gmail.com> wrot=
e:
>> Hi, everyone:
>>
>> For routing scalability issues, I have a question: why not deploy =
AS
>> number based routing scheme? BGP is path vector protocol and the shor=
test
>> paths are calculated based on traversed AS numbers. The prefixes in th=
e same
>> AS almost have the same AS_PATH associated, and aggregating prefixes
>> according to AS will shrink BGP routing table significantly. I don't k=
now
>> what comments the ISPs make on this kind of routing scheme.
>=20
> you might look at LISP, which is sort of like 'route by asn', with
> some other benefits added as well.
>=20
> <http://www.nanog.org/mtg-0706/Presentations/lightning-farinacci.pdf>
NANOG site changed, thus that is now:
http://www.nanog.org/meetings/nanog40/presentations/lightning-farinacci.p=
df
and:
http://www.nanog.org/meetings/nanog41/presentations/lisp-nanog-abq.pdf
Also check http://www.lisp4.net/ as they are actually testing this in
live environments :)
Greets,
Jeroen
--------------enigDC22B1513628A3AFC6BD5583
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFIxUaHKaooUjM+fCMRAsw4AJwPO0Ly44Ov1a9Kq6UYaglKYyw0YgCeKvL0
62c2Dx5I9Dp918tDpoSg7n8=
=F73Z
-----END PGP SIGNATURE-----
--------------enigDC22B1513628A3AFC6BD5583--
