Re: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology (MT) for Segment Routing based Network Resource Partition (NRP)" - draft-ietf-lsr-isis-sr-vtn-mt-06

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Thu, 01 February 2024 07:29 UTC

Return-Path: <gengxuesong@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D6BC14F5FD for <lsr@ietfa.amsl.com>; Wed, 31 Jan 2024 23:29:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=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_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 NzNc30PF70uw for <lsr@ietfa.amsl.com>; Wed, 31 Jan 2024 23:29:48 -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 811C5C14F5E4 for <lsr@ietf.org>; Wed, 31 Jan 2024 23:29:48 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TQVpF70ksz6K5dl; Thu, 1 Feb 2024 15:26:45 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id 8EABD1400D5; Thu, 1 Feb 2024 15:29:44 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 1 Feb 2024 07:29:39 +0000
Received: from canpemm500010.china.huawei.com (7.192.105.118) by canpemm100008.china.huawei.com (7.192.104.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 1 Feb 2024 15:29:37 +0800
Received: from canpemm500010.china.huawei.com ([7.192.105.118]) by canpemm500010.china.huawei.com ([7.192.105.118]) with mapi id 15.01.2507.035; Thu, 1 Feb 2024 15:29:37 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>, Acee Lindem <acee.ietf@gmail.com>, lsr <lsr@ietf.org>
Thread-Topic: RE: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology (MT) for Segment Routing based Network Resource Partition (NRP)" - draft-ietf-lsr-isis-sr-vtn-mt-06
Thread-Index: AQHaQoVUbwrv9UZ7UU6xwHYcHlApqrDUZZhAgBJvbcCADmYpEA==
Date: Thu, 01 Feb 2024 07:29:36 +0000
Message-ID: <5b54f057aa1c45838af36078ddf254ae@huawei.com>
References: <C38046FD-E8BD-4309-8CA2-966F9FD50637@gmail.com>, <2088c16da01f407a91de90f171ef1a3f@huawei.com> <tencent_470E39B3BBD89BCAEB42877CC4EB28404207@qq.com>
In-Reply-To: <tencent_470E39B3BBD89BCAEB42877CC4EB28404207@qq.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.43]
Content-Type: multipart/alternative; boundary="_000_5b54f057aa1c45838af36078ddf254aehuaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/jvXfUj6Im1LKOwGxItE1QHozrqU>
Subject: Re: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology (MT) for Segment Routing based Network Resource Partition (NRP)" - draft-ietf-lsr-isis-sr-vtn-mt-06
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2024 07:29:52 -0000

Hi Chongfeng,

Thanks for updating the document and the new version looks good to me.

Best
Xuesong

From: Chongfeng Xie [mailto:chongfeng.xie@foxmail.com]
Sent: Tuesday, January 23, 2024 11:33 AM
To: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Acee Lindem <acee.ietf@gmail.com>; lsr <lsr@ietf.org>
Subject: Re: RE: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology (MT) for Segment Routing based Network Resource Partition (NRP)" - draft-ietf-lsr-isis-sr-vtn-mt-06


Hi Xuesong,

Thanks for your support and review comments. We are working on a new revision which will take your comments into consideration.

As for your suggestion to add reference to the more scalable solution, according to the comments from Acee, we would not mention the specific solution in this draft, but we have referred to the NRP scalability document for more information on the scalability discussion.  Hope that would be OK to you.

Best regards,
Chongfeng

From: Gengxuesong (Geng Xuesong)<mailto:gengxuesong@huawei.com>
Date: 2024-01-11 18:37
To: Acee Lindem<mailto:acee.ietf@gmail.com>; Lsr<mailto:lsr@ietf.org>
Subject: RE: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology (MT) for Segment Routing based Network Resource Partition (NRP)" - draft-ietf-lsr-isis-sr-vtn-mt-06
Hi WG,

I support the publication of this document. I think this is a reasonable method of network slicing implementation which could reuse the existing mechanism.
Some editing comments for authors' reference.

Best
Xuesong

--

1.  Introduction
...
This document describes a
   simplified mechanism to build SR based NRPs in those scenarios.  The
   resource-aware segments can be used with this approach to provide
   resource guaranteed SR based NRPs, while the normal SR segments may
   also be used to provide SR based NRPs with shared network resources
   in the forwarding plane.

   The proposed approach is to use IS-IS Multi-Topology [RFC5120] with
   segment routing [RFC8667] to define the independent network topology
   of each NRP.  The network resources and other TE attributes of an NRP
   can be advertised using IS-IS MT with the Traffic Engineering (TE)
   extensions defined in [RFC5305] and [RFC8570].

[Xuesong] I recommend to swap the position of these two sentences. It will be easier for readers' understanding: show what is the proposal firstly and then describe this could be used with resource-aware segments to provide resource guaranteed SR based NRPs

2.  Advertisement of Topology Attribute for SR based NRP

[Xuesong] It will be helpful if there is a summary about what Topology Attribute for SR based NRP is requested before introducing what could be reused in different existing RFCs.

3.  Advertisement of Resource Attribute for SR based NRP

   In order to perform constraint based path computation for each NRP on
   the network controller or on the ingress nodes, the network resource
   attributes and other attributes associated with each NRP need to be
   advertised.

[Xuesong] It could be considered to add some explanation for whether this is just for this proposal or also could be used to other resource guaranteed SR based NRPs


5.  Scalability Considerations
  The
   mechanism described in this document is considered useful for network
   scenarios in which the required number of NRP is small, as no control
   protocol extension is required.  For network scenarios where the
   number of required NRP is large, more scalable solution would be
   needed, which may require further protocol extensions and
   enhancements.

[Xuesong] This is helpful to add some reference for example of more scalable solutions.


> -----Original Message-----
> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Acee Lindem
> Sent: Tuesday, January 9, 2024 6:50 AM
> To: Lsr <lsr@ietf.org<mailto:lsr@ietf.org>>
> Subject: [Lsr] Working Group Last Call for "Applicability of IS-IS Multi-Topology
> (MT) for Segment Routing based Network Resource Partition (NRP)" -
> draft-ietf-lsr-isis-sr-vtn-mt-06
>
> This begins a two week LSR Working Group last call for the “Applicability of IS-IS
> Multi-Topology (MT) for Segment Routing based Network Resource Partition
> (NRP)”. Please express your support or objection prior to Tuesday, January 23rd,
> 2024.
>
> Thanks,
> Acee
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org<mailto:Lsr@ietf.org>
> https://www.ietf.org/mailman/listinfo/lsr