Re: Can one Destination Address appear in both Tunnel Encap Attribute and in MP_REACH_NLRI ?

Linda,

I’m not sure if I understand your question completely. Pls see comments inline.

On 10/10/19, 1:56 AM Linda Dunbar from [email protected]<mailto:[email protected]> said >

Dear authors:
draft-ietf-idr-tunnel-encaps specifies the The Tunnel Encapsulation attribute as an optional transitive BGP Path
attribute, with code point 23.

Yes, that’ right.

Does it mean Tunnel Encapsulation Attribute is listed at the same level as MP_REACH_NLRI (Code Point 14) in the Path Attributes lists shown in the following captured packets from Wireshark?

Like you mention, the Tunnel Encapsulation Attribute is a Path attribute, so it is a matter to displaying all the path attributes, one can display in the ascending order of the Code Points.

If a Destination address is already listed in the MP_RACH_NLRI, is it listed again in the Tunnel Encap subTLV (if it can be reached via some tunnel, such as VxLAN/GRE/?

I’m not clear what you mean here. The MP_REACH provides the reachability information while the Tunnel Encapsulation Attribute provides the Tunnel details (remote-endpoint, encapsulation, etc). The presence of Tunnel Encapsulation attribute in an update that carries MP_REACH attribute indicates the data path destined for prefixes encoded in the NLRI field of MP_REACH.

Thanks.

srihari…


[cid:[email protected]]


Does the Tunnel Encapsulation Attributes have the same fields as MP_REACH_NLRI (RFC4760)?
Or the Tunnel Encapsulation Attributes is the “Network Layer Reachability Information” field of MP_REACH_NLRI?

[cid:[email protected]]


Thank you very much,

Linda Dunbar

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr