Re: 16-bit ASN kludge

[Owen DeLong <owen () delong com>]

I think the general idea of dividing ASNs into LEAF and TRANSIT categories
is a good one.  A method of determining which ASs need to know about
a given LEAF AS is needed, and, I think a lot of optimizations may well
be possible.

Like I said, I think it requires some additional thought and refinement,
but, I like the general idea.

Owen


--On Saturday, December 4, 2004 3:03 AM +0000 "Edward B. Dreger" 
<eddy+public+spam () noc everquick net> wrote:

> OD> Date: Fri, 03 Dec 2004 18:09:48 -0800
> OD> From: Owen DeLong
>
> OD> I think all the meaningful parties have already pretty much agreed on
> OD> 32bit ASNs in BGP4.  I think that will be coded in the routers well
> before OD> any attribute-based thing for 32bit ASNs is.  As such, I don't
> see much OD> point to kludging this instead of just going for it assuming
> a 32bit world.
>
> Then belay my 16-bit ramblings.  I'm probably a bit naive in thinking a
> new attribute would be passed along by enough transits to be useful; an
> "adopt this incompatible protocol or become an island" approach may well
> be needed.
>
> I still have to wonder if some leaf optimizations are possible.  Perhaps
> an incompatible protocol would leave more implementation wiggle room.
>
>
> Eddy
> --
> Everquick Internet - http://www.everquick.net/
> A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
> Bandwidth, consulting, e-commerce, hosting, and network building
> Phone: +1 785 865 5885 Lawrence and [inter]national
> Phone: +1 316 794 8922 Wichita
> ________________________________________________________________________
> DO NOT send mail to the following addresses:
> davidc () brics com -*- jfconmaapaq () intc net -*- sam () everquick net
> Sending mail to spambait addresses is a great way to get blocked.



--
If it wasn't crypto-signed, it probably didn't come from me.

Attachment: _bin
Description: