[Teas] Fw:New Version Notification for draft-peng-teas-network-slicing-04.txt

peng.shaofu@zte.com.cn Wed, 21 October 2020 02:26 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFBC3A0A4F for <teas@ietfa.amsl.com>; Tue, 20 Oct 2020 19:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6JbMmf6g8KQy for <teas@ietfa.amsl.com>; Tue, 20 Oct 2020 19:26:13 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04AF53A0A49 for <teas@ietf.org>; Tue, 20 Oct 2020 19:26:07 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id C111177467D75524FF50 for <teas@ietf.org>; Wed, 21 Oct 2020 10:26:05 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id A33ED672844C39ACDE12 for <teas@ietf.org>; Wed, 21 Oct 2020 10:26:05 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl2.zte.com.cn with SMTP id 09L2Q497086554 for <teas@ietf.org>; Wed, 21 Oct 2020 10:26:04 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid201; Wed, 21 Oct 2020 10:26:04 +0800 (CST)
Date: Wed, 21 Oct 2020 10:26:04 +0800 (CST)
X-Zmail-TransId: 2afc5f8f9c3c51139b4a
X-Mailer: Zmail v1.0
Message-ID: <202010211026044982098@zte.com.cn>
References: 160319772087.22661.15912191333989550597@ietfa.amsl.com
Mime-Version: 1.0
From: <peng.shaofu@zte.com.cn>
To: <teas@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 09L2Q497086554
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/IjW0WRGB3sxDBCWQiBJRUfQBjcA>
Subject: [Teas] =?utf-8?q?Fw=3ANew_Version_Notification_for_draft-peng-te?= =?utf-8?q?as-network-slicing-04=2Etxt?=
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 02:26:16 -0000

Hi WG,






We have updated a new version to discuss how to realize IETF network slice based on a new virtual network identifier introduced in the underlay network.


The contents of this document mainly includes:


1) Why introduce the new virtual network identifer (we now call it AII) according to the requirements that we understand, instead of using the existing identifiers.


2) How to use AII to represent E2E TN-slice with guaranteed resource, especially inter-domain resource. Also, a simple variant without control extensions is described.


3) Different Slice Type is defined, each has different endogenous characteristics, such as dealy, igp-metric, te-metric, etc, that will provide a flexible and simple way to deploy service which does not need to define multiple sets of constraints, and no need to occupy many SR-TE instances.


4) Other considerations of interworking with other mechanism.






We hope to get your suggestions, and any comments are welcome.







Regards,


PSF









原始邮件



发件人:internet-drafts@ietf.org
收件人:彭少富10053815;Gregory Mirsky;Greg Mirsky;陈然00080434;Fengwei Qin;
日 期 :2020年10月20日 20:42
主 题 :New Version Notification for draft-peng-teas-network-slicing-04.txt



A new version of I-D, draft-peng-teas-network-slicing-04.txt
has been successfully submitted by Shaofu Peng and posted to the
IETF repository.

Name:        draft-peng-teas-network-slicing
Revision:    04
Title:        Packet Network Slicing using Segment Routing
Document date:    2020-10-20
Group:        Individual Submission
Pages:        28
URL:            https://www.ietf.org/archive/id/draft-peng-teas-network-slicing-04.txt
Status:         https://datatracker.ietf.org/doc/draft-peng-teas-network-slicing/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-peng-teas-network-slicing
Htmlized:       https://tools.ietf.org/html/draft-peng-teas-network-slicing-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-peng-teas-network-slicing-04

Abstract:
   This document presents a mechanism aimed at providing a solution for
   network slicing in the transport network for 5G services.  The
   proposed mechanism uses a unified administrative instance identifier
   to distinguish different virtual network resources for both intra-
   domain and inter-domain network slicing scenarios.  Combined with the
   segment routing technology, the mechanism could be used for both
   best-effort and traffic engineered services for tenants.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat