Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

"Dongjie (Jimmy)" <> Mon, 17 May 2021 02:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DD7623A232D for <>; Sun, 16 May 2021 19:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wZGi99KLWm_r for <>; Sun, 16 May 2021 19:45:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 980883A232A for <>; Sun, 16 May 2021 19:45:10 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4Fk3H838lLz6W18J; Mon, 17 May 2021 10:39:00 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Mon, 17 May 2021 04:45:05 +0200
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 17 May 2021 10:45:04 +0800
Received: from ([]) by ([]) with mapi id 15.01.2176.012; Mon, 17 May 2021 10:45:03 +0800
From: "Dongjie (Jimmy)" <>
To: Gyan Mishra <>
CC: "" <>, "" <>
Thread-Topic: [spring] A new draft on Segment Routing for End-to-End IETF network slicing
Thread-Index: AddImA0It4733A5eRvyl5e+xCalORP//jdqA//9vaxCAAf78AP/8qU+Q
Date: Mon, 17 May 2021 02:45:03 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_a0bca22412814b2196d88c6a0a21e9fbhuaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 17 May 2021 02:45:16 -0000

Hi Gyan,

Thanks for your comments. Yes this document extends the single domain VTN mechanisms to multi-domain network scenarios, which could be used for the end-to-end IETF network slicing and further for 5G end-to-end network slicing.

This document proposes several optional types of VTN Binding SIDs (functions), each may be applicable in a particular case. Feedbacks on these BSID types are appreciated.

Best regards,

From: Gyan Mishra []
Sent: Saturday, May 15, 2021 3:09 PM
To: Dongjie (Jimmy) <>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

Hi Jimmy

I read the draft and support  the principles defined in instantiation of E2E network slice and method of mapping a VPN+ overlay to VTN underlay underpinning & resources provisioning via resource sid VTN ID across multiple domains E2E using a list of VTN BSIDs for per domain hop path steering.

This draft will be very useful for 5G E2E multi domain network slicing VTN provisioning and E2E concatenation of SR-TE BSID per domain hop BSID list E2E path instantiation.

Kind Regards


On Fri, May 14, 2021 at 10:45 AM Dongjie (Jimmy) <<>> wrote:
Hi Chongfeng,

Thanks for your valuable comments. The term “IETF network slice” was chosen by the network slicing design team in TEAS WG, after many discussion in both the design team and the WG.  This document tries to align with the terminology there.

I also agree that the terms in different SDOs needs to be aligned, or the relationship and mapping between different terms could be defined.

Best regards,

From:<> []
Sent: Friday, May 14, 2021 5:18 PM
To: Dongjie (Jimmy) <<>>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

I think this work is useful and support its progress in spring or other WGs. However, I have some concerns about the term of "IETF slicing”, from the perspective of operator, the terms of “IETF slicing” and “3GPP slicing” may be confusing, there should be a universal set of terms of slicing across different SDOs, even they may cover different sections or layers of the network system.  What’s your opinion?

Best regards

2021年5月14日 下午4:10,Dongjie (Jimmy) <<>> 写道:

Hi WG,

Recently we published a new draft on Segment Routing for End-to-End IETF Network Slicing:

It introduces the new SRv6 behaviors and SR-MPLS BSIDs to enable the mapping and concatenation of multi-domain IETF network slices. This document is aligned with the framework for end-to-end IETF network slicing as described in draft-li-teas-e2e-ietf-network-slicing.

Your review and comments are welcome.

Best regards,
spring mailing list<>

spring mailing list<>


Gyan Mishra

Network Solutions Architect


M 301 502-1347