[OCCAID] Communities question

[James]

On Sat, Jan 15, 2005 at 03:59:26PM +0100, Peter Salanki wrote:
> Ah, so 900x is for OCCAID prefixes and 3xxx is for peer prefixes?

Nah.. 9000 and 3000 are both OCCAID related. Its just that 9000 is
strictly OCCAID related where as 3000 is for-downstream prefixes.
3000 and 9000 are the set we announce to peers and transits.

To downstreams/customers, 3000, 9000 and 2000 are announced, aka
full-routes.

The peer prefixes are part of 30071:2000 area (transit/peer comm's).
Some of 2xxxx is transits, two of that are routes received from peers..

-J

> 
> 2005-01-15 kl. 15.48 skrev James:
> 
> >On Sat, Jan 15, 2005 at 01:01:08PM +0100, Peter Salanki wrote:
> >>Well, I get that part. But the difference between the two stated is
> >>what I don't get :)
> >
> >30071:3000 identifies Customer community in general..
> >
> >Then we have location code for customers...
> >
> >3010 means originated from ZOA (San Francisco/Oakland area).
> >3020 means originated from ZBW (Boston area).
> >
> >and so on and so forth as listed in 
> >http://www.occaid.org/occaid-bgp.html
> >
> >Same story with 9xxxx. 9000 identifies internal originated.
> >Then 9010, 9020, etc are location codes.
> >
> >Does this help you? :) Let me know if not..
> >
> >-J
> >
> >>
> >>
> >>2005-01-15 kl. 09.59 skrev Michael Nicks:
> >>
> >>>On 01/15/05 09:29:30 +0100, Peter Salanki wrote:
> >>>>What does the Member ("Customer") Communities Identifier
> >>>>Community do? (i.e. 30071:3010). I thought it was the same as OCCAID
> >>>>Originated Communities Identifier
> >>>>Community at first sight.
> >>>>
> >>>>Thanx
> >>>>
> >>>>/Peter Salanki
> >>>>Port80 AB (AS16150)
> >>>
> >>>To my understanding, it is to tag incoming routes received from a 
> >>>peer
> >>>with a certain community to make it easy to locate where a route
> >>>originated
> >>>from. E.g, Sprint transit routes are tagged with 30071:2300,
> >>>
> >>>route-views.occaid.org> sh bgp community 30071:2300
> >>>BGP table version is 0, local router ID is 65.126.230.78
> >>>Status codes: s suppressed, d damped, h history, * valid, > best, i -
> >>>internal
> >>>Origin codes: i - IGP, e - EGP, ? - incomplete
> >>>
> >>>  Network          Next Hop            Metric LocPrf Weight Path
> >>>*  2001:220::/32    2001:4830::4                           0 30071
> >>>6175 4725 3748 9270 i
> >>>*                   2001:4830::5                           0 30071
> >>>6175 4725 3748 9270 i
> >>>*                   2001:4830:1::1                         0 30071
> >>>6175 4725 3748 9270 i
> >>>*                   2001:4830::3             1             0 30071
> >>>6175 4725 3748 9270 i
> >>>*>                  2001:4830::2             0             0 30071
> >>>6175 4725 3748 9270 i
> >>>*                   2001:4830::1             0             0 30071
> >>>6175 4725 3748 9270 i
> >>>*  2001:230::/35    2001:4830::4                           0 30071
> >>>6175 4725 3748 i
> >>>*                   2001:4830::5                           0 30071
> >>>6175 4725 3748 i
> >>>[snip - etc]
> >>>
> >>>-M
> >>>
> >>>-- 
> >>>Michael Nicks				     IOPort Technologies, LLC
> >>>nicksm at ioport.com			
> >>>1(913)-378-6516			
> >>>
> >>>_______________________________________________
> >>>OCCAID Mailing List: http://www.occaid.org
> >>>schednetisr(NETISR_COFFEE); inq=&coffeebreak_intrq;
> >>>
> >>>Occaid at cnacs.occaid.org is the list posting address.
> >>>db-admin at cnacs.occaid.org is the human contact address.
> >>>See below URL for subscribe/unsubscribe and list options:
> >>>http://mailman.twdx.net/mailman/listinfo/occaid
> >>
> >>_______________________________________________
> >>OCCAID Mailing List: http://www.occaid.org
> >>schednetisr(NETISR_COFFEE); inq=&coffeebreak_intrq;
> >>
> >>Occaid at cnacs.occaid.org is the list posting address.
> >>db-admin at cnacs.occaid.org is the human contact address.
> >>See below URL for subscribe/unsubscribe and list options:
> >>http://mailman.twdx.net/mailman/listinfo/occaid
> >
> >-- 
> >James Jun                                            TowardEX 
> >Technologies, Inc.
> >Technical Lead                      Boston IPv4/IPv6 Web Hosting, 
> >Colocation and
> >james at towardex.com            Network design/consulting & 
> >configuration services
> >cell: 1(978)-394-2867           web: http://www.towardex.com , noc: 
> >www.twdx.net

-- 
James Jun                                            TowardEX Technologies, Inc.
Technical Lead                      Boston IPv4/IPv6 Web Hosting, Colocation and
james at towardex.com            Network design/consulting & configuration services
cell: 1(978)-394-2867           web: http://www.towardex.com , noc: www.twdx.net