Re: [mpls] SR-MPLS Service Programming usecase for Open DT Wed, 22 September 2021 02:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 54F743A1637 for <>; Tue, 21 Sep 2021 19:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 28-RLC9_wcfy for <>; Tue, 21 Sep 2021 19:07:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7D7713A1632 for <>; Tue, 21 Sep 2021 19:07:15 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 657B6648A0E37F5A1AD3 for <>; Wed, 22 Sep 2021 10:07:12 +0800 (CST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 4C15DDFD37B0CF680F0C; Wed, 22 Sep 2021 10:07:12 +0800 (CST)
Received: from ([]) by with SMTP id 18M26xeB009316; Wed, 22 Sep 2021 10:06:59 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Wed, 22 Sep 2021 10:06:58 +0800 (CST)
Date: Wed, 22 Sep 2021 10:06:58 +0800 (CST)
X-Zmail-TransId: 2afb614a8fc29fb8a782
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
From: <>
To: <>
Cc: <>
Content-Type: text/plain; charset="UTF-8"
X-MAIL: 18M26xeB009316
Archived-At: <>
Subject: Re: [mpls] =?utf-8?q?SR-MPLS_Service_Programming_usecase_for_Open_DT?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Sep 2021 02:07:21 -0000

Hi Haoyu,

I think there're some differences between the SR-MPLS SFC usecase and the network programming usecase.
The purpose and the content of the data carried after the BOS of these two usecases are not the same. 
The purpose of SR-MPLS SFC usecase is to achieve SFC by SR-MPLS instead of NSH. The data required to be carried after the BOS is metadata for SFC. A new extension header may be defined for it or maybe we reuse existing header like NSH or SRH or something else.
The purpose of network programming usecase is to support the equivalent of FUNC::ARG in SRv6.  And the content of the data carried after the BOS contains FUNC:ARGs, segment count and pointers as for my understanding.


日 期 :2021年09月20日 23:48
主 题 :RE: [mpls] SR-MPLS Service Programming usecase for Open DT
Hi Yao,
I think what you described has been covered in the "network programming" use case on the wiki page,, which is more akin to SRH in SR.
-----Original Message-----
From: mpls <> On Behalf Of
Sent: Thursday, September 16, 2021 1:40 AM
Subject: [mpls] SR-MPLS Service Programming usecase for Open DT
Hi DT,
Besides the requirement in NSH Based SFC usecase in the wiki to carry path ID and metadata by embedding NSH in EH.
There's also a need to carry metadata in SR service programming with SR-MPLS data plane.
The reference is draft-ietf-spring-sr-service-programming. SR service programming is a mechanism to achieve SFC in SR-MPLS and SRv6 networks without the use of NSH.
In this draft, there's a requirement to carry metadata in SR-MPLS data plane, some possible methods to carry metadata (e.g, defining an SRH-like header with only the mandatory fields required to carry metadata) and to indicate the presence of metadata(e.g, adding the indication in the semantic of the service SIDs, or introducing a protocol identifier in the MPLS packet) are proposed but not standardized.
As for the path ID, although not mentioned in this draft, I think there's a potential need for it to let the SFFs distinguish between different SFPs.
Maybe after discussion the solution for this usecase is similar to that for NSH Based SFC, but I think this usecase should be taken into consideration.