Re: [Teas] A draft on the framework for end-to-end IETF network slicing

"Dongjie (Jimmy)" <> Mon, 17 May 2021 10:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF0243A316F for <>; Mon, 17 May 2021 03:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3w8VucXfclH7 for <>; Mon, 17 May 2021 03:03:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CEE5B3A3148 for <>; Mon, 17 May 2021 03:03:31 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4FkF0x5Gcwz6cw1F; Mon, 17 May 2021 17:57:21 +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 12:03:27 +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 18:03:26 +0800
Received: from ([]) by ([]) with mapi id 15.01.2176.012; Mon, 17 May 2021 18:03:25 +0800
From: "Dongjie (Jimmy)" <>
To: Daniele Ceccarelli <>, Jeff Tantsura <>, "" <>
Thread-Topic: [Teas] A draft on the framework for end-to-end IETF network slicing
Date: Mon, 17 May 2021 10:03:25 +0000
Message-ID: <>
References: <> <49ca2ff9-6530-44d7-888e-fa88b7e0a060@Spark> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_84a5b0dfbd2f4d37ae7bfb6dc6d9794ahuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] A draft on the framework for end-to-end IETF network slicing
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 17 May 2021 10:03:44 -0000

Hi Daniele,

Thanks for your suggestion.

This draft mainly describes the mapping of end-to-end IETF network slices and 5G end-to-end network slices to the multi-domain and intra-domain VTNs in the underlay, thus it is more about the “end-to-end” or multi-domain aspect of network slices. VPN+ and VTN are used to represent the realization of IETF network slice in the overlay and underlay respectively.

Agree further discussion about the term ACTN VN, VTN, Slice Aggregate, etc. is needed, once their relationship is resolved, the discussion on the solutions would be easier.

Best regards,

From: Daniele Ceccarelli []
Sent: Monday, May 17, 2021 3:37 PM
To: Jeff Tantsura <>;; Dongjie (Jimmy) <>
Subject: RE: [Teas] A draft on the framework for end-to-end IETF network slicing

I agree with Jeff, or even better, since there is a draft on the applicability of ACTN to network slicing, this one could be used to describe the applicability of VPN+/Enhanced VPN to Network slicing.

Don’t forget about the pending discussion on the relationship between ACTN VN and VTN, I still believe this duality can be easily resolved with an augmentation and have a single solution for network slicing instead of many.


From: Teas <<>> On Behalf Of Jeff Tantsura
Sent: den 14 maj 2021 23:14
To:<>; Dongjie (Jimmy) <<>>
Subject: Re: [Teas] A draft on the framework for end-to-end IETF network slicing


I think, it would have been more appropriate to have “vtn/vtn-id” in the draft name, rather than "e2e-ietf-network-slicing"

On May 12, 2021, 7:54 PM -0700, Dongjie (Jimmy) <<>>, wrote:
Hi WG,

Recently we published a draft on the framework for end-to-end IETF network slicing:

This document describes the scenarios of end-to-end network slicing, and the framework of network slice mapping between different network segments and network domains. Multiple network slice related identifiers are defined to covers different network scopes.

The network slice related identifiers of different network scopes can be instantiated with MPLS or IPv6 data plane, which are further described in the following drafts:

Your review and comments are welcome. (Comments on the specific data plane draft can go to the corresponding WG mail list).

Best regards,
Teas mailing list<>