Hi Rajesh The endpoint behavior is implicit in the NLRI and not encoded in the LIB/WLIB field of the service Sid. SRv6 with its extensibility of programmable endpoint behaviors makes SRv6 very powerful as the 16 bit service Sid field can be programmed for any forwarding behavior desired.
In this case for example the L3 VPN service Sid is advertised per RFC 9252 with update packing of the 128 bit service Sid, SID structure sub sub tlv with offset, with locator common part encoded in prefix Sid and variable part label encoded in the NLRI SAFI 128. On the receiving end the PE unpacks and based on the offset reassembles the 128 bit prefix for the service Sid. Thanks Gyan On Thu, Dec 25, 2025 at 12:18 AM Rajesh M <mrajesh= [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 ? > > > > Thanks > > Rajesh > > > > Juniper Business Use Only > _______________________________________________ > BESS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
