> >
> > Hello Michael,
> >
> > > is not the case in AS6453 (Teleglobe). Out of curiosity,
> how did you
> > > source that info?
> >
> > You got a point! This is an error in the paper :(
Hi Kris,
>
> I'm not sure this is an error. AS8938 is claiming in their
> IRR remarks that they are setting 8938:2100 on prefixes
> learned from AS6453 (not AS6453 setting this community).
>
> aut-num: AS8938
> ...
> remarks: all routes from TeleGlobe tagged with 8938:2100
gin-b1d-core1#sh ip b reg ^8938_
BGP table version is 275750669, local router ID is 66.110.0.93
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i62.29.128.0/17 66.110.0.107 0 100 0 8938 i
* i 66.110.0.107 0 100 0 8938 i
*>i 66.110.0.107 0 100 0 8938 i
* i 66.110.0.107 0 100 0 8938 i
* i 66.110.0.107 0 100 0 8938 i
* i 66.110.0.107 0 100 0 8938 i
<snip/>
gin-b1d-core1#sh ip bgp com 8938:2100
gin-b1d-core1#
because we control the set of communities that we accept at import time
(to the well-known ones and the set of values that we operate on).
mh
>
> Kris
>
>
>
> > >> -----Message d'origine-----
> > >> De : Benoit Donnet [mailto:[EMAIL PROTECTED]
> > >> Envoyé : mardi 4 décembre 2007 10:56 À : [email protected] Objet :
> > >> [GROW] On BGP Communities
> > >>
> > >> Dear Grow Working Group,
> > >>
> > >> During the past years, we have seen an increasing usage
> of the BGP
> > >> community attribute. For instance, in a recent BGP table
> > dump from
> > >> routeviews, 99% of the routes stored by the router carries BGP
> > >> communities.
> > >>
> > >> In this context, we are currently working on a BGP community
> > >> taxonomy, i.e., we want to classify and document communities
> > >> according to their usage. We describe our taxonomy on the
> > following
> > >> url: http://inl.info.ucl.ac.be/communities
> > >>
> > >> Based on this taxonomy, we tried to collect as much as possible
> > >> information on BGP communities. This was a daunting task as we
> > >> mainly relied on public database, such as whois server
> and ISP web
> > >> sites.
> > >>
> > >> Our current database of classified BGP communities
> > currently contains
> > >> more than 27,000 entries.
> > >>
> > >> As researchers, we are now in the process of writing a
> > paper on our
> > >> work on BGP communities.
> > >>
> > >> We plan to submit this paper to ACM SIGCOMM Computer
> Communication
> > >> Review for the April issue. This is an editorial paper (max. 4
> > >> pages).
> > >>
> > >> You can find a preprint of the paper at the following
> URL: http://
> > >> inl.info.ucl.ac.be/communities or directly at http://
> > >> inl.info.ucl.ac.be/system/files/communities.pdf
> > >>
> > >> Any comments on the paper is welcome.
> > >>
> > >> Thank you very much.
> > >>
> > >> Keep on Rockin'
> > >>
> > >> Dr. Benoit Donnet & Prof. Olivier Bonaventure
> > >>
> > >> --
> > >> Dr. Benoit Donnet
> > >> Université Catholique de Louvain (UCL) Faculté des Sciences
> > >> Appliquées - Département d'Ingénierie Informatique (INGI) Place
> > >> Sainte Barbe, 2 1348 Louvain-la-Neuve Belgium
> > >> Phone: +32 10 47 87 18
> > >> Home page: http://inl.info.ucl.ac.be/donnet
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> GROW mailing list
> > >> [email protected]
> > >> https://www1.ietf.org/mailman/listinfo/grow
> > >>
> > >>
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > GROW mailing list
> > > [email protected]
> > > https://www1.ietf.org/mailman/listinfo/grow
> >
> > --
> > Dr. Benoit Donnet
> > Université Catholique de Louvain (UCL) Faculté des Sciences
> Appliquées
> > - Département d'Ingénierie Informatique (INGI) Place Sainte Barbe, 2
> > 1348 Louvain-la-Neuve
> > Belgium
> > Phone: +32 10 47 87 18
> > Home page: http://inl.info.ucl.ac.be/donnet
> >
> >
> >
> >
> >
> > _______________________________________________
> > GROW mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/grow
> >
>
>
_______________________________________________
GROW mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/grow
