Hello Siva, and others,

While the idea of enabling simultaneous advertisement of MPLS label and SRv6 
SID is interesting, I'm a bit concerned about the role of the RR in this 
solution and its operation in a transition case.

The concern is that modification of label information may lead to loss of 
connectivity.



"If the RR does not support this capability, it MUST continue to operate 
according to standard BGP route reflection procedures."

In this case, advertising peers/clients will not encode their updates according 
to this draft?

Figure 1 distinguishes ingress / egress PE, maybe change this to advertising / 
receiving (relative to the RR)?


In a transition scenario, different types of PEs, in different stages of 
transition may be connected to the RR

MPLS only => should receive the MPLS label

  *
not support draft

SRv6/MPLS => should receive both ?

  *
not supporting draft
  *
supporting draft

SRv6 only => should receive SRv6 SID

  *
not supporting draft
  *
supporting draft


If the RR rewrites the MPLS label to Implicit NULL, SRv6 SID remains. A 
receiving RR client will no longer receive the MPLS label information, correct?
Couldn't this be a problem for some of the SRv6/MPLS PEs that require both to 
be present?

cheers,
    Eduard


________________________________
From: Sivabalan, Siva <[email protected]>
Sent: Monday, July 06, 2026 17:35
To: [email protected] <[email protected]>
Cc: Shah, Himanshu <[email protected]>; Dhillon, Param Preet 
<[email protected]>; [email protected] <[email protected]>; 
[email protected] <[email protected]>
Subject: [bess] [BESS] New Draft: Dual MPLS and SRv6 Service Advertisement in 
the Absence of Transposition

You don't often get email from [email protected]. Learn why 
this is important<https://aka.ms/LearnAboutSenderIdentification>

Hi,



We have submitted a new Internet-Draft:



Title: Dual MPLS and SRv6 Service Advertisement in the Absence of Transposition



Filename: draft-many-bess-rfc9252-dual-sid-00



URL: https://datatracker.ietf.org/doc/draft-many-bess-rfc9252-dual-sid/



The draft proposes a backward-compatible extension to RFC 9252

allowing advertisement of both an MPLS Service Label and an SRv6

Service SID within a single route.



Comments and feedback are welcome.



Thanks,

Authors


_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to