Re: [Idr] 5575bis nit - ASes in extended communities

[Jeffrey Haas <[e-mail]>]

On Wed, Feb 12, 2020 at 06:41:36PM -0500, Jeffrey Haas wrote:
> In RFC 5575 and 5575-bis, we have several extended communities defined.
> 
> :    +-----------+----------------------+--------------------------------+
> :    | community | action               | encoding                       |
> :    +-----------+----------------------+--------------------------------+
> :    | 0x8006    | traffic-rate-bytes   | 2-byte ASN, 4-byte float       |
> :    | TBD       | traffic-rate-packets | 2-byte ASN, 4-byte float       |
> :    | 0x8007    | traffic-action       | bitmask                        |
> :    | 0x8008    | rt-redirect AS-2byte | 2-octet AS, 4-octet value      |
> :    | 0x8108    | rt-redirect IPv4     | 4-octet IPv4 addres, 2-octet   |
> :    |           |                      | value                          |
> :    | 0x8208    | rt-redirect AS-4byte | 4-octet AS, 2-octet value      |
> :    | 0x8009    | traffic-marking      | DSCP value                     |
> :    +-----------+----------------------+--------------------------------+
> : 
> :                Table 2: Traffic Action Extended Communities
> 
[...]
> While the AS number is largely an advisory number for the features in
> question, it does potentially have impact on policy.
> 
> My recommendation would be we add some text roughly like the following:
> Add "In the circumstance that this specification is utilized in a BGP
> Confederation [RFC 5065], AS Numbers used by these Traffic Action Extended
> Communities SHOULD be the BGP speaker's Confederation Identifier AS."

Thinking slightly further, the text should be:
"In the circumstance that this specification is utilized in a BGP
Confederation [RFC 5065], AS Numbers used by the Traffic Rate Extended
Communities SHOULD be the BGP speaker's Confederation Identifier AS."

The AS numbers for redirect are provisioned from VRF import policy and
wouldn't be touched.

-- Jeff