[Teas] Re: [spring] Re: [mpls] Re: Comments during Spring session - Re: Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
Robert Raszuk <robert@raszuk.net> Tue, 17 November 2026 19:40 UTC
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 6581752 for <teas@ietf.org>; Tue, 17 Nov 2026 19:40:37 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=raszuk.net header.s=google header.b="QBhm5/ou"; spf=pass (mx.ietf.org: domain of robert@raszuk.net designates 2607:f8b0:4864:20::f2c as permitted sender) smtp.mailfrom=robert@raszuk.net; dmarc=none; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-qv1-xf2c.google.com with SMTP id 6a1803df08f44-91eb46044c4so1128396d6.1 for <teas@ietf.org>; Tue, 17 Nov 2026 11:40:37 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1794944431; cv=none; d=google.com; s=arc-20260327; b=E+IQmBoQplu0AFSZwXNccrVv+JoHqUnt9NIZ8cJIbWfU+hL3WIChH4jxprwY9qBFjU /fbGOXw3v2It8CPKh6/+VBq9KRfws72RsYhxu7pyAE5Fx/yX/L+8pV0IU+2FE/WK9eeF mHK96jI64Af5tFekWwaAjzjHjt29XKVJCpBMYvPV1FXVYbQa4cHbmV95LCqOj1PJ2KFi bVr3p0yQ1Lg5F0yYQvo8RFtgN/fzWeyICQMFie2U6pfheJe3BLM7XWEYGGiAJPZxkwPg feSrEnHKVGSN/LK+21jzvr6+m8cVU5hhrfveh0eK5NuccK+4lxytgklPHhE6+wufQ1yg +JXw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=cvyHjuDKrA3plQCOqV1BjSVRn8iPA1CcQguJHGJ6Qnc=; fh=FuxptJzUQgO/bXlCjoau1jatBq2sDL+aCZeAGa0PG0Q=; b=CxbeX7hnSG5f7lrs/3y8sPCxcz0U/GWLT9OffI0Luy+4PLt3jovqnsrVrYEbXmJi2k MuSF+F1AIhbEZZS4GZ3vfOUoiuBrp4SYsTDkYDIjxzMZyHvUdCZENkJettOGFFCM/BIj meXDJf1SB5AkNLsEmj/QmEQl2GtAgFqsALUNTkxFmsWkpn4iI510aGOvDXax5xApdixy TEIUDbw1991LZwC2LBwhtBTZRFW9CrUXBLrFl0ZaTRm8ES7DyBnTsqsL1XZpYeUsnmiy qYMtc0AUpuCiW+vDcimeX2RRKE5F+xL61+zaNSu3eknlwsrki+LLfonqyVFk1NSHKFbS o99w==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1794944431; x=1795549231; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=cvyHjuDKrA3plQCOqV1BjSVRn8iPA1CcQguJHGJ6Qnc=; b=QBhm5/ouiPauSDlDjTvmr4u6F4UAUZgeIW8rca+yvYbOMAUyUs5EZ8PWbcNir4zPHu +3yefxWozRV8dUbj5+no6KZ+2ez21+klvulgIPIfn2gk4Yl4In02fZX6kNoFtAfNgNXa atMcSB+9F2RfmCctsn0MVEYlVPv150N+UxXK7ukHin3/KEumRSrN11KVzu240HNk+oM6 pA0rLkw+enbHtFRFzfCNEU0K93WCtxihzKNNUS1AdTQSuY8dzlcUbdU3Gcx+IMm5Vh6L 7UyXIdPsArxXrd+aai4/98k4pEo2qQENgH+3T2HncBRZV7QRSFgMO+cYuqyh2l2+SbCR FkSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1794944431; x=1795549231; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=cvyHjuDKrA3plQCOqV1BjSVRn8iPA1CcQguJHGJ6Qnc=; b=hwmJ20Rtvvtdb3x1qtSyTIwllnojezcRWwvKop+lMMaCt+pMHKh9xhOre3vIlhhCT5 PysWUwH3BJMnz3MNPUFlmAkiQ9Tsb3R+etNbnvpOlJcsNvnF0zCGwwB6353ZPzbwoXhf rvHzLNgfjf7isRM7k+J1TzyE41IdK4LjDaHBU46U3MTqKvQrq5rE2jeXQVkkG8Xyddc4 MENTtSiBge03SwxWYbXlH103d8CCoLRLNCU4D2iHPgxzlizLRSlzGil9qiEhEHuVBECi C2ZRwJiJY4aKHf73H69yArYmFcmlPgQgUZgDagc6dEScltRQODSVN6iY23OC+mlgqVNe ZtCA==
X-Forwarded-Encrypted: i=1; AL+hErEHcndsPcM5RoCcu+drWpatZqDs5owFdFMS0+jM924ttlrSTDZNDOv8YlyGOp6kDi2VWONa@ietf.org
X-Gm-Message-State: APuU4Z/oc1iWeIu0VsoJn38dYoALJLwc/wrqtKuSspYmjR08WYeCex96 oZtEMdFrEMxnRrKtx9sdCwoEOvcYa0g+iPUYmDOdnrvxKSDdayF/vPz5oZlDKIk7cy+BX8GKSjZ SyS83dgTcB+BNt7QdbJVSJbltEbvAM2Aj8ayy05ijVw==
X-Gm-Gg: AZFdTZfTPdmPOOXugQWLIOpqG8+xxZnA7YX/IZfS7XgKO5Iv+ueaWOr/gU/99luE+Lr 7zXXydsP7HVZyEQ34zYl0HDo4ikB7hStFNSdAUJS2c2lO9kfevto19fKVrfNglRTwd3M/v8Qtw6 Vj/W/AQ4FGoTiBXxcOnU91KNRb8mvV//1TNn2clvXBpBcBFi1ZtDIBG9wanX7tem0BPTpcB9z0u EU04bDrvUQECsfBsu02j+dfhK3JMulQ1EDpevmdqlDXWv2OxK+oEryB7ywprOHsrTgA//K90OGj 5PEEqCtq8saNLn1Hx3v2Tkmwul1tYR3XUx1+njU/60koZyQfQEe6Eu6ac3nq1owdV5hQX87aEjr Z0eyiYqt2uA5hv1pGmh4YWNQ6/dkjtsz8jPhY
X-Received: by 2002:a05:6214:2a48:b0:91f:319b:b6bb with SMTP id 6a1803df08f44-92114fbe3e6mr2773496d6.55.1794944430416; Tue, 17 Nov 2026 11:40:30 -0800 (PST)
MIME-Version: 1.0
References: <179358330469.1013311.4077472205935423431@dt-datatracker-7dc874ff8f-sl5zv> <LV8P220MB19144B62E293884ADEC11B8BFC692@LV8P220MB1914.NAMP220.PROD.OUTLOOK.COM> <LV8P220MB19145828E2D9DD886F582569FC692@LV8P220MB1914.NAMP220.PROD.OUTLOOK.COM> <DS0PR08MB913865A87A2B6D6F0555EB5A91762@DS0PR08MB9138.namprd08.prod.outlook.com> <CAMoPOhm9wv=J-V5rKfsXiWN0HaovwEUxYVYjKmYEHHCgJ9=DRg@mail.gmail.com> <SA3PR11MB3470614607B45899817C346220DE7D2@SA3PR11MB347061.namprd11.prod.outlook.com> <CAMoPOhn_wnZaHUZ4qYvhD009ZLTchOVo0rwaq8=rYqMrjEFb6A@mail.gmail.com> <CAMoPOhmHNCQeUD0yp4+68GSfhdk+G=xnkAiBce1_sEMqFocn9Q@mail.gmail.com> <CH3PR11MB941921F717CEA45434431BDAC7DE7B2@CH3PR11MB941921.namprd11.prod.outlook.com> <CA+YzgTtn2OMV5-wuzSmQwOrjTNYNq6DRYWC+1w5mv1ZjsNmnqw@mail.gmail.com> <CA+b+ERn6LKXrNLaAPzLyaxk1MQVRGYGFJsCEL+qCGxb+qHOZeA@mail.gmail.com> <CAMoPOhkvixJjxnkuxZcsKWiHG3y2pRybhqWtE4TL74pHrhc8LA@mail.gmail.com> <CA+b+ERm+_k=Tsm-osDGXO9W5XCzxY8B0O-3nch1wrr7Bi+KQgw@mail.gmail.com> <DM4PR84MB2238360AE66B804D1941CAB48C7B2@DM4PR84MB2238.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To: <DM4PR84MB2238360AE66B804D1941CAB48C7B2@DM4PR84MB2238.NAMPRD84.PROD.OUTLOOK.COM>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 17 Nov 2026 20:40:19 +0100
X-Gm-Features: Aa3M54ot25XHLUnbalmL-oobp_jhF7Ewz8vUa_IwJud9A8M2OeUWRkoYT4E72Gg
Message-ID: <CAOj+MMF_mUvLo2DY=va7F90Xh4b5V4oQA-8uLh7mPqMb3spZZw@mail.gmail.com>
To: "Hegde, Shraddha" <shraddha.hegde@hpe.com>
Content-Type: multipart/alternative; boundary="0000000000002ab9c806607e112a"
X-Spamd-Bar: ----------------
Message-ID-Hash: TZWW3HY5BA7YVZXN2P4BFJNCYE5P2HBY
X-Message-ID-Hash: TZWW3HY5BA7YVZXN2P4BFJNCYE5P2HBY
X-MailFrom: robert@raszuk.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-teas.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Robert Raszuk <rraszuk@gmail.com>, Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com>, Vishnu Pavan Beeram <vishnupavan@gmail.com>, "Zafar Ali (zali)" <zali@cisco.com>, "Andrew Stone (Nokia)" <andrew.stone@nokia.com>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "draft-beeram-mpls-rsvp-sr@ietf.org" <draft-beeram-mpls-rsvp-sr@ietf.org>, spring <spring@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>, spring Chairs <spring-chairs@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Teas] Re: [spring] Re: [mpls] Re: Comments during Spring session - Re: Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/BB0JWBQg8QQOxVmQDqhclCRGZgc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>
Hi Shraddha, Yes I am aware of SRGB and SRLB. Are you sure that RSVP-TE BSIDs would always be allocated from SRLB ? That requires strict chaining and fails pretty badly upon link or node failure repair. But my point was different ... You know in practice today each protocol get allocated a range of the block by the SID block manager. It is never one by one. And I do sincerely hope that if for nothing else then for easy troubleshooting operator should be able to easily find out by looking at the packet at least if this is native SR or RSVP-TE/SR packet. Recall today's preso by OpenAI how important it is to wisely select semantics of the uN SIDs :) Regards, Robert On Tue, Nov 17, 2026 at 8:33 PM Hegde, Shraddha <shraddha.hegde= 40hpe.com@dmarc.ietf.org> wrote: > Hi Robert, > > You raise very important aspects of the SR architecture that probably > needs clarification in the > SR Distributed bandwidth management architecture draft. > > SR architecture has the SRGB and SRLB concept. > The BSID allocated by RSVP will come from the SRLB space. > > There isn't per protocol ownership of the SID space defined in SR > architecture and it is not needed for the proposed solution. > > > > Rgds > Shraddha > ------------------------------ > *From:* Robert Raszuk <rraszuk@gmail.com> > *Sent:* 17 November 2026 11:10 > *To:* Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com> > *Cc:* Vishnu Pavan Beeram <vishnupavan@gmail.com>; Zafar Ali (zali) < > zali@cisco.com>; Andrew Stone (Nokia) <andrew.stone@nokia.com>; > mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org <mpls-chairs@ietf.org>; > draft-beeram-mpls-rsvp-sr@ietf.org <draft-beeram-mpls-rsvp-sr@ietf.org>; > spring <spring@ietf.org>; TEAS WG (teas@ietf.org) <teas@ietf.org>; spring > Chairs <spring-chairs@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org> > *Subject:* [spring] Re: [mpls] Re: Comments during Spring session - Re: > Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17) > > Hi Pavan, > > Ok so you have confirmed that each transit node performing the delegation > will now need to allocate a unique BSID per group of paths sharing the very > same hop by hop (or rather egress by egress) path destination or next > delegation node. > > It is worth highlighting that now the owner of that BSID will be RSVP > protocol and not IGP. So it becomes necessary to introduce the concept of > SID spaces/blocks per protocol. > > Clearly this does not follow the promise that RSVP-SR is just a control > plane signalling chain in the proposal. Now it is clear that BSIDs > allocated by RSVP need to be installed into the data plane and that now > zooming out to the domain we now will have SIDs allocated by different > protocols to deal with. > > Btw in your RSVP RESV could you carry a mix of SIDs and uSIDs for a given > TE path ? > > Kind regards, > Robert > > > > > > On Tue, Nov 17, 2026 at 7:26 PM Vishnu Pavan Beeram < > vishnupavan.ietf@gmail.com> wrote: > > Hi Robert, > > Thanks for the question. Delegation works the same way as in RFC 8577, > with the delegation label replaced by a Binding SID (RFC 8402). > > - What is in the packet? Nothing special. The ingress pushes the > delegation hop's BSID as an ordinary label in its stack. When the packet > arrives at the delegation hop with that label active, the node matches it > against a local entry and replaces it with the labels that the BSID stands > for. A node acts only on a BSID that it allocated. > - How the BSID is signaled? Only in RSVP-TE. The delegation hop owns > and allocates the BSID, as for any Binding SID (RFC 8402), and records it > in the RRO with the Delegation Label flag (0x04) from RFC 8577. The ingress > learns it from the Resv and puts it in its stack. The draft assumes no IGP > advertisement of these BSIDs. > - How a BSID is tied to an LSP? By the RSVP session. The BSID is > learned in the Resv of that LSP, and the delegation hop's entry stands for > the downstream path segment of that LSP. LSPs that take the same downstream > segment can share it. > - Chains of delegation. Each delegation hop does the same. Which > labels a BSID stands for follows the stacking approach in RFC 8577 Section > 5, and the draft refers to it. > > Regards, > -Pavan > > On Tue, Nov 17, 2026 at 8:34 AM Robert Raszuk <rraszuk@gmail.com> wrote: > > Hi Pavan, > > I am not sure if this was covered during the presentation but I have one > question which I hope you could answer. > > In the case of delegation or chain of delegations and in the case of > shared SIDs between protocols what in the packet will indicate the need > that this specific set of packets will be subject for transit node imposing > a new stack of SIDs on it ? > > With RFC8577 it works well as the delegation label is specifically > signalled by RSVP-TE by the node doing delegation. Are you also assuming > that in SR-MPLS or SRv6 the new SID (technically a Binding SID) will be > allocated and now carried only with RSVP-TE extensions to indicate the need > for a specific transit node doing specific delegation imposition ? Or since > in your draft you are making a reference to RFC8402 are you assuming IGP > will carry it ? Is the latter how would you tight binding SID carried by > IGP with specific set of REVP-TE signalled SR Paths/LSPs ? > > Many thx, > Robert > > > > On Tue, Nov 17, 2026 at 5:01 PM Vishnu Pavan Beeram <vishnupavan@gmail.com> > wrote: > > Hi Zafar, all, > > Thank you for summarizing your comments. Most of them were covered in > earlier replies on the MPLS thread, and -02 now has text for several of > them. Briefly: > > - Protection (6.2, 6.3). These are open items that the draft > identifies, and we will elaborate them in a later revision. For 6.2, the > draft requires that the advertisement extension be backward compatible with > existing SR-MPLS deployments, in particular nodes that use TI-LFA to > protect Adj-SIDs. The extension would be a separate document, and its > encoding will be discussed where it is defined. For 6.3, the procedures > still to be specified (how a protection request is considered satisfied by > TI-LFA, and how the primary RSVP state and the Adj-SID forwarding state are > maintained through local repair) are listed in the draft. Node protection > is out of scope. > - Adj-SID ownership and coexistence. The Adj-SIDs remain owned, > allocated and advertised by the IGP. The draft doesn't change their > forwarding semantics. An RSVP-TE ingress is one more headend that imposes > them. Section 7.1 (new in -02) covers coexistence: > - The recommended deployment is that the selected Adj-SIDs carry > only RSVP-signaled traffic. > - Where SR-native traffic shares them, the measurement-based > options of RFC 8426 do not apply and static partitioning does. > - An operator may dedicate an additional Adj-SID by local policy. > - Section 10 notes that an Adj-SID label on the wire can belong to > an SR-native path or to an RSVP-TE tunnel, so tools that attribute traffic > by label can't assume it belongs only to an SR-native path. > - On lifecycle, persistent Adj-SIDs are recommended (Section 3.1). > If a label changes, the re-signaled Resv carries the new value and the > ingress updates its stack, with a disruption comparable to any RSVP-TE > label change. > - State. Each hop carries RSVP session state, which is what provides > distributed admission control and preemption. The forwarding plane carries > no per-LSP state, and the signaling state is the same kind that RFC 8577 > already carries. Where delegation is used, a delegation hop holds one > forwarding entry per downstream path segment, not one per tunnel. > - Process. Thank you for pointing to > draft-hegde-spring-sr-distributed-bw. We welcome SPRING's review of it and > any architecture discussion. As authors of this draft, our view is that the > signaling work can proceed in parallel, since it doesn't change the > semantics of the SR-MPLS forwarding plane. How the work is sequenced across > the WGs is the chairs' decision, and we will follow their guidance. > > Regards, > -Pavan > > On Tue, Nov 17, 2026 at 7:28 AM Zafar Ali (zali) <zali= > 40cisco.com@dmarc.ietf.org> wrote: > > Dear WG > > As per the request from the Spring WG chairs, I am summarizing my comments > in the Spring working group when this draft was presented. > > The question on RSVP-TE signaled facility backup for protected adj-SIDs > remains unanswered and undocumented. The draft says a new advertisement > extension is needed for RSVP facility backup of a protected Adj-SID but > defers that work. Until its encoding and processing rules are specified, it > is unknown that it will induce any Spring change or it will be backward > compatible. > > The question on RSVP-TE LSP protection using TI-LFA also remains > unanswered and undocumented. The draft does not specify how an RSVP > protection request is deemed satisfied by TI-LFA, or how the primary RSVP > signaling and reservation state, and the forwarding state for the Adj-SIDs > used by that LSP, are handled during local repair, throughout the failure > interval, and after the primary path is restored. Those TI-LFA integration > procedures are still necessary to assess the proposal and the TI-LFA for SR > was done in RTGWG. > > Node protection unspecified and hence the architecture implications on > RTGWG/ Spring. > > The adjacency SID labels are owned by IGP. Hijacking Adj sids own by a > different protocol for the use of RSVP-TE brings many Spring architectural > concerns – can the IGP adjacency SIDs be shared? For example, it breaks > traffic accounting for IGP and hence many features that are deployed using > that traffic accounting. If the same Adj-SID carries SR-native traffic, > RSVP admission control does not account for that traffic, and transit > forwarding cannot distinguish it from RSVP traffic. Impact of this change > on RFC 8426 that uses “dark bandwidth” is already highlighted and is among > these architectural concerns. Also, what happens when IGP changes the > adjacency SID labels. Other details on how traffic is restored, how long > the traffic is impacted, etc. The Spring WG should resolve this resource > ownership, sharing, lifecycle, and coexistence questions before defining > RSVP protocol extensions. This is a major architectural change! > > As mentioned earlier, the draft requires per-LSP RSVP state at every > transit node. SPRING should assess this against SR’s ingress-state > architectural goal and the intended scale. > > Thanks to authors of > https://datatracker.ietf.org/doc/draft-hegde-spring-sr-distributed-bw/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-hegde-spring-sr-distributed-bw/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H5aqYzQm$> > to start a draft in Spring. I suggest Spring review such draft(s) and agree > on an architecture and requirements document covering the use cases before > the protocol changes are adopted in relevant working groups. > > Thanks > > Regards … Zafar > > *From: *Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com> > *Date: *Sunday, November 15, 2026 at 7:42 PM > *To: *Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org> > *Cc: *Andrew Stone (Nokia) <andrew.stone@nokia.com>; Tarek Saad < > tsaad.net@gmail.com>; mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org > <mpls-chairs@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org>; spring <spring@ietf.org>; TEAS WG ( > teas@ietf.org) <teas@ietf.org>; spring Chairs <spring-chairs@ietf.org>; > TEAS WG Chairs <teas-chairs@ietf.org>; Zafar Ali (zali) <zali@cisco.com> > *Subject: *Re: [spring] Re: Call for adoption: > draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17) > > Hi all, > > Thank you for the reviews and the discussion. I have posted > draft-beeram-mpls-rsvp-sr-02 to address several of the comments raised > during the call: > > https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5HxuKUnLN$> > Diff against -01: > https://author-tools.ietf.org/iddiff?url1=draft-beeram-mpls-rsvp-sr-01&url2=draft-beeram-mpls-rsvp-sr-02 > <https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url1=draft-beeram-mpls-rsvp-sr-01&url2=draft-beeram-mpls-rsvp-sr-02__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5HzswJH42$> > > Notes: > - Coexistence with SR-native traffic (new Section 7.1): Explains how the > RFC 8426 options apply when SR-native traffic shares the Adj-SIDs, the > recommended deployment, and the separation of controller-based and > distributed bandwidth management. > - Operational considerations (new Section 10): Covers non-TE traffic and > per-LSP policing. > - Benefits (Sections 1): The benefits over RFC 8577 are reworded. > - Protection (Sections 6.2 and 6.3): Unchanged and will be elaborated in a > later revision. > > Regards, > -Pavan > > > On Sun, Nov 15, 2026 at 2:34 PM Vishnu Pavan Beeram < > vishnupavan.ietf@gmail.com> wrote: > > Subject: Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 > (Ends 2026-11-17) > > Hi Zafar, > > Thank you for the review. Several of your points were addressed on other > branches of the thread, so I've pulled them together here. > > 1. State and RFC 8402. Each hop carries RSVP session state, which is what > provides distributed admission control and preemption. The forwarding plane > is SR-MPLS and carries no per-LSP state ( > https://mailarchive.ietf.org/arch/msg/mpls/cFAOpoO3IktTu275JOVqqUTeK2g/ > <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/mpls/cFAOpoO3IktTu275JOVqqUTeK2g/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H_Bc0MuX$>). > This is the same signaling state RFC 8577 already carries. Where delegation > is used, a delegation hop holds one forwarding entry per downstream path > segment, shared by all tunnels that take the same downstream path, not one > per tunnel. > > 2. Why not per-LSP labels (RFC 3209). This work is for operators who run, > or are moving to, an SR-MPLS forwarding plane and want distributed > bandwidth management on it. Operators who stay on a traditional MPLS > forwarding plane can keep using RFC 3209 per-LSP labels (those deployments > are well served today), and this draft does not change that. Operators who > want a shared MPLS forwarding plane without Segment Routing are already > served by RFC 8577, which moved RSVP-TE to a shared per-adjacency label ( > https://mailarchive.ietf.org/arch/msg/mpls/iPVCfZhGI6OuuMg2jYWWIeM-i7w/ > <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/mpls/iPVCfZhGI6OuuMg2jYWWIeM-i7w/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H8pWo6Vz$>). > A shared forwarding plane does give up granular per-LSP transit statistics; > that trade-off comes with RFC 8577 and is not introduced by this draft. > What this draft changes is the source of the label: the Adj-SIDs the IGP > already advertises, instead of a second label allocation scheme. The value > is no separate TE-label allocator, optional persistence via the Adj-SID > P-flag, and a label stack identical to what an SR Policy headend would > impose. We will drop the wording about label exhaustion and fragmentation, > which are not the main driver on current platforms. > > 3. RFC 8426. As a co-author of RFC 8426, I'd like to be more precise about > what I said earlier. What I meant is that RFC 8426 treats SR load as > unreserved bandwidth to be measured around RSVP-TE (the Introduction, and > the measurement approach in Section 3.5). Its premise is networks that > already run RSVP-TE LSPs, with their transit state (Abstract, requirement > 5), and I don't find a stateless-fabric assumption in it. The > measurement-based options (Sections 3.3 and 3.5) need the transit node to > separate SR-native load from RSVP-TE load, so they do not apply if > SR-native traffic shares the selected Adj-SIDs. The recommended deployment > is that the selected Adj-SIDs carry only RSVP-signaled traffic. Where > SR-native traffic shares them, static partitioning (Section 3.1) applies ( > https://mailarchive.ietf.org/arch/msg/mpls/BV65VA5h-C6eREZ4U2L47KFzUeQ/ > <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/mpls/BV65VA5h-C6eREZ4U2L47KFzUeQ/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H_yqLkpw$>), > and a dedicated or marked Adj-SID would be a separate IGP document if the > WG wants it. We will state this scope in the next version. > > 4. Protection (6.2, 6.3). Agreed that these sections are incomplete; 6.1, > the RFC 8577 link protection procedure, is specified. 6.2 and 6.3 will be > elaborated in a subsequent version, and the IGP extension for 6.2 would be > a separate document. Additional protected Adj-SIDs per link scale with the > topology, not with the number of LSPs. I don't believe the open items > should hold up adoption. > > Regards, > -Pavan > > On Sun, Nov 15, 2026 at 9:32 AM Zafar Ali (zali) <zali= > 40cisco.com@dmarc.ietf.org> wrote: > > Hi > > I shared concerns from Andrew on RFC 8426 conflict. > > The statement that in "RFC 8426, SR traffic was assumed to be unreserved, > and distributed bandwidth engineering was not envisioned as an SR function" > is not correct. > What is correct is that RFC 8426 correctly assumes a stateless fabric. The > draft is bringing in states to the SR fabric and hence conflicts with > RFC8426 and RFC8402. > > Thanks > > Regards … Zafar > > *From: *Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com> > *Date: *Friday, November 6, 2026 at 6:29 PM > *To: *Andrew Stone (Nokia) <andrew.stone@nokia.com> > *Cc: *Tarek Saad <tsaad.net@gmail.com>; mpls@ietf.org <mpls@ietf.org>; > mpls-chairs@ietf.org <mpls-chairs@ietf.org>; > draft-beeram-mpls-rsvp-sr@ietf.org <draft-beeram-mpls-rsvp-sr@ietf.org>; > spring <spring@ietf.org>; TEAS WG (teas@ietf.org) <teas@ietf.org>; spring > Chairs <spring-chairs@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org> > *Subject: *[spring] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 > (Ends 2026-11-17) > > Hi Andrew, all, > > Thank you for the review and the questions. They help clarify the scope > and the value of the draft. Responses below. > > > *1. Bandwidth management / RFC 8426 * > Your analysis of the shared Adj-SID is correct for a deployment where > SR-native traffic is also steered over the same Adj-SIDs: the transit node > cannot separate the two, so measurement-based options such as RFC 8426 > Section 3.3 and Section 3.5 do not apply. This deserves explicit treatment > in the document, and we will add it. > > When we wrote RFC 8426, SR traffic was assumed to be unreserved, and > distributed bandwidth engineering was not envisioned as an SR function. The > RFC therefore treats SR load as something to be measured around RSVP-TE. > This document addresses the different case where distributed bandwidth > engineering is provided by RSVP-TE over an SR-MPLS data plane. > > The deployment model this version targets is the one RFC 8577 is > positioned for: SR-MPLS is the forwarding plane for RSVP-TE-signaled > tunnels, which provide distributed bandwidth engineering, and no SR-native > traffic is steered over the Adj-SIDs selected by this specification. In > that model: > > - the traffic on those Adj-SIDs is the traffic admitted by RSVP-TE, so > a per-label counter reflects RSVP-TE usage, as with RFC 8577 TE link labels; > - other traffic on the link is not reflected in RSVP-TE reservations. > Prefix/node-SID shortest-path traffic uses different labels, and transient > traffic such as TI-LFA repair paths is short-lived. This is accounted for > as unengineered background traffic through reservable-bandwidth headroom, > exactly as IGP and LDP traffic is today. > > In the next version we will state this scope explicitly in Section 1 and > Section 7, and say that where SR-native traffic is steered over the same > Adj-SIDs, the coexistence problem described in RFC 8426 arises and is not > addressed by this document. > > For deployments that want to run SR-native engineered traffic alongside, a > natural extension is an IGP-advertised Adj-SID carrying a marker that it is > reserved for RSVP-TE bandwidth engineering. That restores per-label > separation and would be defined in a separate IGP extension document, as we > already anticipate for the protection extension in Section 6.2. > > > *2. Section 1 benefits * > The motivation is operators who run SR-MPLS as their forwarding plane and > need distributed, bandwidth-aware TE. This lets them do so using the > Adj-SIDs that the IGP already advertises for each adjacency, without > introducing a separate label allocation scheme for RSVP-TE. We will sharpen > the benefits in a subsequent version: > > - Operational simplicity (single label allocation): The value is no > separate TE-label allocator for these tunnels, optional persistence via the > Adj-SID P-flag, and a label stack identical to what an SR Policy headend > would impose. We will drop the wording about label exhaustion and > fragmentation, which are not the main driver on current platforms. > - IGP-native discovery: You are right that signaling still has to > complete and that the RRO remains authoritative (Section 4.1). We will > reword the benefit accordingly. Because the Adj-SIDs are in the IGP-learned > TED, the ingress's own path computation can determine the label stack, > check MSD/ETLD feasibility, identify any delegation hops and, where needed, > constrain Adj-SID selection with ERO Label sub-objects before signaling, > and can cross-check the RRO against the result. The same applies if an > external path computation engine computes the path. > - Interoperability: We will reframe this benefit as reuse of existing > SR-MPLS capabilities and drop the data-plane-conflict wording. The tunnels > use Adj-SIDs that nodes already allocate and advertise, and can leverage SR > OAM. > > These are clarifications to the text and scope of the document; none of > them changes the signaling procedures or protocol extensions in the draft. > We will handle them in the next version. > > Thanks again for the thorough review; it will make the document better. > > Regards, > -Pavan > > On Fri, Nov 6, 2026 at 12:24 PM Andrew Stone (Nokia) <andrew.stone= > 40nokia.com@dmarc.ietf.org> wrote: > > Hi all, authors, > > I have some concerns with some aspects of this draft, with comments and > questions split into two categories. Any clarification appreciated. > > > 1. Bandwidth management - coexistence problem > > Section 7: I don't follow how bandwidth admission control will function. > Unless I'm missing something, the same Adj-SIDs will carry SR-native > traffic pushed from any ingress, and that load never appears in RSVP-TE > reservations, which only account for the signalled LSPs. RSVP-TE would > therefore be reserving bandwidth on links whose actual load it cannot see > or control. > > This looks to be the RSVP-TE and SR coexistence problem described in RFC > 8426 but the shared label makes it harder. > > For example, the options in RFC 8426 Sections 3.3 and 3.5 depend on > measuring SR utilization on each interface, but a transit node can no > longer separate SR traffic from RSVP-TE traffic when both use the same > Adj-SID. The SR traffic measured will contain none, some, or all of the > RSVP-TE signalled traffic on that Adj-SID. Any RSVP-TE traffic counted as > SR utilization reduces RSVP-TE's available bandwidth, creating a feedback > loop. The RSVP-TE related bandwidth may be counted twice. > > The other RFC 8426 options don't help either: static partitioning (RFC > 8426 Section 3.1) gives up shared bandwidth, and centralized management > (RFC 8426 Section 3.2), removes a goal for this draft. > > Section 7 of this document does not seem to address RFC 8426 within > context, which feels light given that Section 1 presents bandwidth > admission control as what RSVP-TE continues to provide. In the context of > bandwidth admission control, I don't see the gains this brings over RFC8577 > or classic RSVP-TE. > > > > 2. Benefits listed in Section 1 > > These benefits don't seem significant to me: > > - Single label allocation: I don't think local label exhaustion is a risk, > since this saves one label per TE link compared to RFC8577. What is the > concern with allocation fragmentation? It also doesn't help general RSVP-TE > scaling, since the per-LSP RSVP-TE state on each node is still there. > > - IGP-native discovery: Agreed, IGP flooding is useful, but Section 1 says > the ingress doesn't need to wait for Resv processing, while Section 4.1 > says it must still use the labels from the RRO, so it waits anyway. Is the > faster pre-computation really that significant? > > - Interoperability: I agree the same labels serve all data-plane traffic > in this proposal, but given the bandwidth concern in point 1, I'm not sure > this is actually a benefit. For the comment about data-plane conflict: what > data-plane conflict does this avoid, when it is all MPLS forwarding anyway? > > Thanks > Andrew > > > > > *From: *Tarek Saad <tsaad.net@gmail.com> > *Date: *Tuesday, November 3, 2026 at 1:06 PM > *To: *mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org < > mpls-chairs@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org>; spring <spring@ietf.org>; TEAS WG ( > teas@ietf.org) <teas@ietf.org> > *Cc: *spring Chairs <spring-chairs@ietf.org>; TEAS WG Chairs < > teas-chairs@ietf.org> > *Subject: *[spring] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 > (Ends 2026-11-17) > > > *CAUTION:* This is an external email. Please be very careful when > clicking links or opening attachments. See the URL nok.it/ext > <https://urldefense.com/v3/__http://nok.it/ext__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5Hwp2yk1r$> > for additional information. > > > Also adding TEAS WG for relevance to RSVP-TE protocol. > > Regards, > > *From: *Tarek Saad <tsaad.net@gmail.com> > *Date: *Tuesday, November 3, 2026 at 10:03 AM > *To: *mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org < > mpls-chairs@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org>; spring <spring@ietf.org> > *Cc: *spring Chairs <spring-chairs@ietf.org> > *Subject: *Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends > 2026-11-17) > > Adding the SPRING WG to this thread due to the document's relevance to > Segment Routing. > > Regards, > Tarek (as MPLS WG chair) > > *From: *Tarek Saad via Datatracker <noreply@ietf.org> > *Date: *Sunday, November 1, 2026 at 8:35 PM > *To: *mpls@ietf.org <mpls@ietf.org>; mpls-chairs@ietf.org < > mpls-chairs@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org < > draft-beeram-mpls-rsvp-sr@ietf.org> > *Subject: *Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends > 2026-11-17) > > This message starts a mpls WG Call for Adoption of: > draft-beeram-mpls-rsvp-sr-01 > > This Working Group Call for Adoption ends on 2026-11-17 > > Abstract: > RFC 8577 introduced the concept of signaling RSVP-TE tunnels on a > shared MPLS forwarding plane using preinstalled "TE link labels". > Those labels are functionally equivalent to Segment Routing (SR) > Adjacency Segment Identifiers (Adj-SIDs) but are allocated and > distributed solely via RSVP-TE signaling. > > This document extends RFC 8577 so that RSVP-TE tunnels can use > Segment Routing over MPLS (SR-MPLS) Adj-SIDs, as specified in RFC > 8402 and RFC 8660, in place of TE link labels. It restricts scope to > Adj-SIDs attached to a single unidirectional adjacency and defines > the signaling procedures and protocol extensions required to couple > the RSVP-TE control plane with the SR-MPLS data plane. > > Please reply to this message and indicate whether or not you support > adoption > of this Internet-Draft by the mpls WG. Comments to explain your preference > are greatly appreciated. Please reply to all recipients of this message and > include this message in your response. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the > provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H8toDpmL$> > [2] https://datatracker.ietf.org/doc/bcp79/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H9j59x7j$> > [3] https://datatracker.ietf.org/doc/rfc6701/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H31Qqb76$> > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/ > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5HxuKUnLN$> > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01 > <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5HwCNKFAq$> > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01 > <https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01__;!!NpxR!iz530AbJDkH6y1pSdj9HZW8ZUuBWnk_SirWn3NZJdkvkH0p5htazwrnv6oQMTOdLPxi-MlG5H6mUthOK$> > > _______________________________________________ > spring mailing list -- spring@ietf.org > To unsubscribe send an email to spring-leave@ietf.org > > _______________________________________________ > mpls mailing list -- mpls@ietf.org > To unsubscribe send an email to mpls-leave@ietf.org > > _______________________________________________ > spring mailing list -- spring@ietf.org > To unsubscribe send an email to spring-leave@ietf.org >
- [Teas] Re: [spring] Call for adoption: draft-beer… Acee Lindem
- [Teas] Re: [spring] Call for adoption: draft-beer… Vishnu Pavan Beeram
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Andrew Stone (Nokia)
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Andrew Stone (Nokia)
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Andrew Stone (Nokia)
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Zafar Ali (zali)
- [Teas] Re: [spring] Re: Call for adoption: draft-… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Vishnu Pavan Beeram
- [Teas] Comments during Spring session - Re: [spri… Zafar Ali (zali)
- [Teas] Re: [spring] Comments during Spring sessio… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Robert Raszuk
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Vishnu Pavan Beeram
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Robert Raszuk
- [Teas] Re: [mpls] Re: [spring] Comments during Sp… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Robert Raszuk
- [Teas] Re: [spring] Re: [mpls] Re: Comments durin… Vishnu Pavan Beeram
- [Teas] Re: [spring] Re: Call for adoption: draft-… Zafar Ali (zali)
- [Teas] Re: Call for adoption: draft-beeram-mpls-r… Tarek Saad
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Barth, Colby
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Robert Raszuk
- [Teas] Re: [mpls] Re: Call for adoption: draft-be… Greg Mirsky
- [Teas] Re: [spring] Re: [mpls] Re: Call for adopt… Robert Raszuk