Re: When can NLRI and Withdrawn Route info be modified?

[Brad Smith <[e-mail]>]

>   The answer to the following may be obvious, by definition, but I want
>   to make sure I understand... is it true that an ATOMIC_AGGREGATE will
>   only be generated in a situation where an AGGREGATE attribute would
>   also be generated? (Even writing this I realize that it could be read
>   as "is it true that aggregation is done only when aggregation is being
>   done"... but I'll leave the question on the table:).
> 
> There is no such thing as an aggregate attribute.  There's no real way to
> tell if a route is an aggregate or not.  There are intelligent guesses
> (does it have an AA, or are there any AS sets in the path), but those aren't
> sure things and should not be relied upon.

Ooops... I meant "AGGREGATOR".  The (short) section in the RFC describing
this says:

    AGGREGATOR is an optional transitive attribute which may be included
    in updates which are formed by aggregation (see Section 9.2.4.2).  A
    BGP speaker which performs route aggregation may add the AGGREGATOR
    attribute which shall contain its own AS number and IP address.

Is this also not widely implemented?

Thanks,

Brad