Re: [Teas] I-D Action: draft-ietf-teas-nrp-scalability-04.txt
"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 07 March 2024 02:44 UTC
Return-Path: <jie.dong@huawei.com>
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 7FB08C14F617; Wed, 6 Mar 2024 18:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.204
X-Spam-Level:
X-Spam-Status: No, score=-4.204 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzoiaQ14hPSF; Wed, 6 Mar 2024 18:44:08 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAC33C14E515; Wed, 6 Mar 2024 18:44:07 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Tqtst6BcCz6J9Tw; Thu, 7 Mar 2024 10:44:02 +0800 (CST)
Received: from lhrpeml100003.china.huawei.com (unknown [7.191.160.210]) by mail.maildlp.com (Postfix) with ESMTPS id A30EF140736; Thu, 7 Mar 2024 10:44:04 +0800 (CST)
Received: from dggpemm500005.china.huawei.com (7.185.36.74) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 7 Mar 2024 02:44:03 +0000
Received: from kwepemd100004.china.huawei.com (7.221.188.31) by dggpemm500005.china.huawei.com (7.185.36.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 7 Mar 2024 10:44:01 +0800
Received: from kwepemd100004.china.huawei.com ([7.221.188.31]) by kwepemd100004.china.huawei.com ([7.221.188.31]) with mapi id 15.02.1258.028; Thu, 7 Mar 2024 10:44:01 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "teas@ietf.org" <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>, "draft-ietf-teas-nrp-scalability@ietf.org" <draft-ietf-teas-nrp-scalability@ietf.org>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-nrp-scalability-04.txt
Thread-Index: AQHabiFH4rVPyuI1Zki7NHeyEm6ajrErkN7A
Date: Thu, 07 Mar 2024 02:44:00 +0000
Message-ID: <1983e4941fba49a8ae2bda119dfa971b@huawei.com>
References: <170954912828.65165.16467977058605138679@ietfa.amsl.com>
In-Reply-To: <170954912828.65165.16467977058605138679@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/dWt22-AuJQQgxPnq_Ne3pe2qr7E>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-nrp-scalability-04.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 07 Mar 2024 02:44:10 -0000
Dear all, A new revision of the nrp scalability draft has been uploaded before the cut-off. Here are the major changes: - Some of the scalability design principles are rephrased based on the comments received both online and offline. - Added a suggestion that network slicing protocol specifications also include considerations of scalability. - Some example of network slice realizations are listed in an Appendix (thanks to Adrian for the contribution and discussion), and the possible scalability issues with each of them are discussed. - The author list is adjusted to comply to the rules of 5-authors (thanks to Fengwei for all your contributions to this work). - Some editorial changes. As always review and comments are welcome. Best regards, Jie (on-behalf of the authors) > -----Original Message----- > From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > Sent: Monday, March 4, 2024 6:45 PM > To: i-d-announce@ietf.org > Cc: teas@ietf.org > Subject: [Teas] I-D Action: draft-ietf-teas-nrp-scalability-04.txt > > Internet-Draft draft-ietf-teas-nrp-scalability-04.txt is now available. It is a > work item of the Traffic Engineering Architecture and Signaling (TEAS) WG of > the IETF. > > Title: Scalability Considerations for Network Resource Partition > Authors: Jie Dong > Zhenbin Li > Liyan Gong > Guangming Yang > Gyan Mishra > Name: draft-ietf-teas-nrp-scalability-04.txt > Pages: 25 > Dates: 2024-03-04 > > Abstract: > > A network slice offers connectivity services to a network slice > customer with specific Service Level Objectives (SLOs) and Service > Level Expectations (SLEs) over a common underlay network. > > RFC XXXX describes a framework for network slices built using > networks that use IETF technologies. As part of that framework, the > Network Resource Partition (NRP) is introduced as a set of network > resources that are allocated from the underlay network to carry a > specific set of network slice service traffic and meet specific SLOs > and SLEs. > > As the demand for network slices increases, scalability becomes an > important factor. Although the scalability of network slices can be > improved by mapping a group of network slices to a single NRP, that > design may not be suitable or possible for all deployments, thus > there are concerns about the scalability of NRPs themselves. > > This document discusses some considerations for NRP scalability in > the control and data planes. It also investigates a set of > optimization mechanisms. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-teas-nrp-scalability/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-teas-nrp-scalability-04 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-teas-nrp-scalability-04 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > Teas mailing list > Teas@ietf.org > https://www.ietf.org/mailman/listinfo/teas
- [Teas] I-D Action: draft-ietf-teas-nrp-scalabilit… internet-drafts
- Re: [Teas] I-D Action: draft-ietf-teas-nrp-scalab… Dongjie (Jimmy)