Hi Rajesh, Getting to this late, as I missed it over my holiday break.
Please check inline below. On Thu, Dec 25, 2025 at 10:48 AM Rajesh M <[email protected]> wrote: > Hi All, > > > > *As per rfc, SRv6 Endpoint Behavior (2 octets):* > > The opaque SRv6 Endpoint Behavior (i.e., value 0xFFFF) MAY be used when the > > advertising router wishes to abstract the actual behavior of its locally > instantiated SRv6 SID. > > > > Query : > > When an ingress router receives Endpoint Behavior with value 0xffff, > within SRv6 L3 Service TLV what should be the behavior ? > > > > When an ingress router receives Endpoint Behavior with value 0xffff, > within SRv6 L2 Service TLV what should be the behavior ? > KT> Rather than just the TLV, the BGP route is more important and indicates the type of service and the context. In most cases, the ingress PE behavior is not changed by the behavior signaled - it simply uses the SID when doing the encapsulation of the service flow. This is how the opaque behavior works. The only exception is those BGP routes that advertise SIDs with arguments (see RFC9819) where the ingress needs to understand the behavior (also the structure) to know how to encode the argument. Thanks, Ketan > > > Thanks > > Rajesh > > > > Juniper Business Use Only >
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
