The community attribute is simply a label, what you do with that label
is your concern. It's almost like intra-company mail, everyone in the
company (AS) knows what to do (as long as you tell them to) with
this mail, how to forward it, whether to allow it or deny it, but someone
outside of your AS will most likely ignore whatever communities you
set unless you specifically tell them what your communities mean, and
still, it's optional for an external AS to do anything based on your
communities. You can't really force them to interpret it.
--
Omachonu Ogali
missnglnk@...
http://www.informationwave.net/~missng
----- Original Message -----
From: <felixr@...
To: <isp-bgp@isp-bgp.com>
Sent: Sunday, September 09, 2001 9:42 AM
Subject: COMMUNITY attribute


> Hi All !
>
> Does COMMUNITY attribute, as transitive attribute, allows AS path
> manipulation not only on the provider side, but also on the provider of
the
> provider side (i.e. the upstream provider of some provider) ?
>
> I mean, suppose AS100 is a customer of AS1, which in turn is a customer,
or
> even a peer, of another provider, lets say AS2. Suppose that AS2
inaccurately
> redistribute AS1 routes (AS100 routes aggregated by AS1, thus AS100 routes
> are also inaccurately redistributed). Is there any mean to override AS2
> policies which, of course, concern AS1 routes ?
>
> Thanks,
> Felix.
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ISP-Planet: The Intelligence Center for the ISP Community
> http://www.isp-planet.com/
> Where the world evolves around your ISP-Business
>




>


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ISP-Planet: The Intelligence Center for the ISP Community
http://www.isp-planet.com/
Where the world evolves around your ISP-Business

Replies

COMMUNITY attribute, felixr