[Teas] FW: New Version Notification for draft-dong-teas-nrp-scalability-02.txt

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 17 May 2022 02:59 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 74901C20D671; Mon, 16 May 2022 19:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Q_piCyhudmQF; Mon, 16 May 2022 19:59:29 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB1ADC20D657; Mon, 16 May 2022 19:59:28 -0700 (PDT)
Received: from fraeml741-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4L2LS90KWQz6H7nW; Tue, 17 May 2022 10:59:21 +0800 (CST)
Received: from kwepemi500018.china.huawei.com ( by fraeml741-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 17 May 2022 04:59:25 +0200
Received: from kwepemi500017.china.huawei.com ( by kwepemi500018.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 17 May 2022 10:59:23 +0800
Received: from kwepemi500017.china.huawei.com ([]) by kwepemi500017.china.huawei.com ([]) with mapi id 15.01.2375.024; Tue, 17 May 2022 10:59:23 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: TEAS WG <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: New Version Notification for draft-dong-teas-nrp-scalability-02.txt
Thread-Index: AQHYaTBmlPuf+u6i/0GYJBMHtKm9T60iR9yA
Date: Tue, 17 May 2022 02:59:23 +0000
Message-ID: <66c2d7193f574de3997a4daef043fdc6@huawei.com>
References: <165271094082.62297.3802517131158728941@ietfa.amsl.com>
In-Reply-To: <165271094082.62297.3802517131158728941@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xLkIILzL6enLRcvjQbtWLWONqo8>
Subject: [Teas] FW: New Version Notification for draft-dong-teas-nrp-scalability-02.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 17 May 2022 02:59:33 -0000

Hi WG and Chairs, 

A new revision of draft-dong-teas-nrp-scalability has been submitted to solve the recent comments received on mail list and offline. The changes include:

- The text about general optimization mechanism is moved to the beginning of section 4. 
- In section 4.1.1, the figure and description of the examples are updated.
- Operational consideration section is added.
- Some editorial changes.

With this update, this document is in a good shape for the WG to take over, thus the authors would like to request WG Chairs to start the adoption call procedure. Thanks. 

Best regards,
Jie (on behalf of coauthors)

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, May 16, 2022 10:22 PM
To: Fengwei Qin <qinfengwei@chinamobile.com>; Guangming Yang <yangguangm@chinatelecom.cn>; Gyan Mishra <gyan.s.mishra@verizon.com>; James N Guichard <james.n.guichard@futurewei.com>; Dongjie (Jimmy) <jie.dong@huawei.com>; Jim Guichard <james.n.guichard@futurewei.com>; Liyan Gong <gongliyan@chinamobile.com>; Tarek Saad <tsaad@juniper.net>; Vishnu Beeram <vbeeram@juniper.net>; Vishnu Pavan Beeram <vbeeram@juniper.net>; Lizhenbin <lizhenbin@huawei.com>
Subject: New Version Notification for draft-dong-teas-nrp-scalability-02.txt

A new version of I-D, draft-dong-teas-nrp-scalability-02.txt
has been successfully submitted by Jie Dong and posted to the IETF repository.

Name:		draft-dong-teas-nrp-scalability
Revision:	02
Title:		Scalability Considerations for Network Resource Partition
Document date:	2022-05-16
Group:		Individual Submission
Pages:		18
URL:            https://www.ietf.org/archive/id/draft-dong-teas-nrp-scalability-02.txt
Status:         https://datatracker.ietf.org/doc/draft-dong-teas-nrp-scalability/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dong-teas-nrp-scalability
Diff:           https://www.ietf.org/rfcdiff?url2=draft-dong-teas-nrp-scalability-02

   The IETF Network Slice service aims to meet the connectivity demands
   of a network slice customer with specific Service Level Objectives
   (SLOs) and Service Level Expectations (SLEs) over a common underlay
   network.  A Network Resource Partition (NRP) is a set of network
   resources that are allocated from the underlay network to carry a
   specific set of network traffic and meet the required SLOs and SLEs.
   One or multiple IETF Network Slice services can be mapped to one NRP.

   As the demand for IETF Network Slice services increases, scalability
   would become an important factor for the large scale deployment of
   IETF Network Slices.  Although the scalability of IETF Network Slices
   can be improved by mapping a group of IETF Network Slices to one NRP,
   there are concerns about the scalability of NRPs.  This document
   describes the scalability considerations about NRPs in the network
   control plane and data plane, and some optimization mechanisms are

It seems the submission system cannot parse the document date correctly. Please help with this manual posting, thanks. 

The IETF Secretariat