[43506] in North American Network Operators' Group
RE: Communities
daemon@ATHENA.MIT.EDU (E.B. Dreger)
Tue Oct 16 11:48:07 2001
Date: Tue, 16 Oct 2001 15:47:08 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Kevin Gannon <kgannon@lancomms.ie>
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
"'nanog@merit.edu'" <nanog@merit.edu>
In-Reply-To: <4159668C5AA7D4118A40001083FD704256846D@ccgate.lancomms.ie>
Message-ID: <Pine.LNX.4.20.0110161541430.13013-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> Date: Tue, 16 Oct 2001 09:55:12 +0100
> From: Kevin Gannon <kgannon@lancomms.ie>
> I've been thinking about other information that could be
> conveyed in communities. For instance, bandwidth, delay and
> packet loss. If each router along the way modifies such a
> community (should probably be an extended one) then a much
> richer set of information would be available to multihomers to
> aid in route selection.
[ snip ]
I'd toyed with the bandwidth idea... let's say that we create
0xffff:1, :2, :3, and :4 to mean sub-T1, T3, OC3, and >= OC12.
Arbitrary and simplified for sake of example.
Whenever a router forwards, it tags with the appropriate speed.
Thus, if :1 is set, you _know_ this path has a sub-T1 link. Of
course, some places might use bogus tags to try hiding their
connectivity... but an upstream could use a route-map to let
the truth escape.
Thus, with proper administration by upstreams, !set{:1|:2|:3|:4}
would indicate no participants along the way. However, if this
were to gain momentum among the biggest three dozen ASen, I think
that we'd have a very accurate system. Even the top one dozen
could do a very good job, considering how many connect directly
to them...
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
