And how this regex from RFC8294 maps to
https://www.rfc-editor.org/rfc/rfc7432.html#section-7.6 ?
+ '(6(:[a-fA-F0-9]{2}){6})|'
+ '(([3-57-9a-fA-F]|[1-9a-fA-F][0-9a-fA-F]{1,3}):'
+ '[0-9a-fA-F]{1,12})';
I interpret it as entire type 6 (high order octet type 0x06) is
called Route Target not only 0x06 as high order and 0x02 as
low-order (sub-type).
That is my point.
- - -
Beside if so why none of the specs updates the RFC4360 were real definition of
Route Target present ?
Thx,
R.
On Tue, Nov 22, 2022 at 11:47 PM Jeff Haas <[email protected]> wrote:
> https://www.rfc-editor.org/rfc/rfc7432.html#section-7.6
>
> It’s right there in the name.
>
> Sent from my iPad
>
> On Nov 22, 2022, at 4:23 PM, Robert Raszuk <[email protected]> wrote:
>
>
> Hi Jeff,
>
>
>> > and RFC7432, the encoding
>> > pattern is defined as:
>> >
>> > 0:2-octet-asn:4-octet-number
>> > 1:4-octet-ipv4addr:2-octet-number
>> > 2:4-octet-asn:2-octet-number.
>> > 6:6-octet-mac-address.
>>
>> Type 6 is the ESI-import route-target specified in RFC 7432.
>>
>
> I am not sure where RFC7432 defines a new Route Target.
>
> In fact RFC 7432 is referring to RFC7153 which allocates sub-type 0x02 (ES
> Import) for EVPN Extended Community Type 0x06 - but none of the above
> touches Route Target.
>
> To recap ... Route Target Extended Communities high order octet can be
> 0x00, 0x01 or 0x02.
>
> EVPN Extended Community type is 0x06.
>
> Both are completely different and IMO calling EVPN Extended Community as
> "Route Target" is not right.
>
> Thx,
> R.
>
>
>
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg
