Hi All, As per RFC 8669, 5. <https://datatracker.ietf.org/doc/html/rfc8669#section-5> Advertising BGP Prefix-SID Attribute<https://datatracker.ietf.org/doc/html/rfc8669#name-advertising-bgp-prefix-sid-> A BGP speaker that advertises a path received from one of its neighbors SHOULD advertise the BGP Prefix-SID received with the path without modification as long as the BGP Prefix-SID was acceptable. If the path did not come with a BGP Prefix-SID attribute, the speaker MAY attach a BGP Prefix-SID to the path if configured to do so. The content of the TLVs present in the BGP Prefix-SID is determined by the configuration.
QUERY: BGP speaker receives BGP Prefix-SID attribute with "SRv6 tunnel for label route" TLV" only , now can BGP speaker append "Label-Index TLV" to the BGP Prefix-SID attribute , if configured to do so (irrespective of nexthop self configured or not) Thanks Rajesh Juniper Business Use Only
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
