nanog mailing list archives

Re: BGP communities usage for route origin, entry point


From: Jared Mauch <jared () puck Nether net>
Date: Wed, 19 Jun 2002 12:39:08 -0400


        Many providers document their communities
on webpages:

eg:
http://info.us.bb.verio.net/routing.html#communities
http://cw-rr.cw.net/community_receive.htm
http://cw-rr.cw.net/community_announce.htm

        you probally just need to find the uunet specific webpage
as it realtes to this.

        - jared

On Tue, Jun 18, 2002 at 08:13:50PM -0400, Thomas Kernen wrote:


This started off as me being curious as to why a UUNet engineer I was
talking to told me he could not understand why a network would support a
feature such as BGP communities for identifying the origin of a
route/network entry point. I tried to explain to him the advantage of being
able to quickly identify where a route originates from (geographically),
type of interconnect, type of "peer" (in this case I use peer for any BGP
peer, customer or transit). I explained that it could be usefull for
debugging and gaining more background info (route analysis is one of my
favorite tasks) and some of the major and minor networks do provide such a
feature/service.

Still the engineer could not understand why and only saw this as a security
issue, well I guess when you work for a network that does not provide any
public looking glass or route server it's not really a surprise </rant>

This triggered a thought, do many people actually use BGP communities to
pinpoint a route origination point/type, and if so for what purpose
(debugging, analysis, other)

Thomas

PS: If UUNet do actually support this feature please tell me who I should
contact.

-- 
Jared Mauch  | pgp key available via finger from jared () puck nether net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.


Current thread: