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

Chongfeng Xie <chongfeng.xie@foxmail.com> Tue, 23 January 2024 03:33 UTC

Return-Path: <chongfeng.xie@foxmail.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 57780C14F6A4 for <lsr@ietfa.amsl.com>; Mon, 22 Jan 2024 19:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.837
X-Spam-Level:
X-Spam-Status: No, score=0.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 Hrl8m07S4LnA for <lsr@ietfa.amsl.com>; Mon, 22 Jan 2024 19:33:34 -0800 (PST)
Received: from out162-62-57-252.mail.qq.com (out162-62-57-252.mail.qq.com [162.62.57.252]) (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 A849FC14F61E for <lsr@ietf.org>; Mon, 22 Jan 2024 19:33:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1705980808; bh=HcguCIQX8BPCaXz2WAJX1GNTQq4KxwcY6J7aDwZa1Y0=; h=Date:From:To:Subject:References; b=GrDU0tdlTZuAaiCcuCyMPf7dnbCvbNVRTsLatIhH4krW+ajs0Va2pCbbqtKjE4vTM 7SXRCOIqTZUbKUGg9QEtt1VwSndO1ka+v8neFZ1Lejcp+/C5qLE9hh3aBXPK2SCdwg Uif/18zJK2QgAWnDHmOtUvUHFWnniI4IBA8fkiss=
Received: from DESKTOP-48H476U ([219.142.69.75]) by newxmesmtplogicsvrszc5-0.qq.com (NewEsmtp) with SMTP id 85A99CB5; Tue, 23 Jan 2024 11:33:26 +0800
X-QQ-mid: xmsmtpt1705980806t5ag332q8
Message-ID: <tencent_470E39B3BBD89BCAEB42877CC4EB28404207@qq.com>
X-QQ-XMAILINFO: OTISBJKPy/pkJACYzRUvBw9pzzdj3OSvmsSw8VdBSQQZQvIsWU8t8ouUm3ZTsG yzSLd2T8hjbOIgvwuhk3ru71qMRGTsFh2jGbP6QWHWtDUa0XJX4U9g7PuOHGjeSlpIPdrRHv4ENJ DcAO8JiXWYbPD0y+pIZr0s9sI6fHN4yRk4iouelK715nZL3OTlbNB9bVAG+YXZfB4i4gI07sY97Z aYB2HP4MQk0YLBwykVSb8aHky/PSkAnRR5YlMQZ4eC4vgCKP8Q6YMBKEvlAuC8SAKEFMG5hIGPsw Rqe7VvnSHdjrbvsz+/FBHihlY8iQ6xI5kdy4fshV5GKUThw5bHTW21Riv/NBJrQeXULGEtAuw6wV 2RWwufu9xAdU/Mzn4A57BT8WTfeNUUpYblArp/0XOxhOu3WKHrds8sbTb83NROCm5zFGSjkBjWe6 y9cBlVBOcHoa7mSeWS63Jqks+hDv1DZSjrPxt2BZ3O4vFxDUm2viy/wZp6Uqjfi//jWLIWY1KYqB KKXB6sUHcPiywsj0t9p3iR6b8s3We+lN/dc+gg0GSfJNygoxgvIdjB4fy3SbifYWUiVrATIZVE8x 8gHVQBKhbsogHvKLdrx/MPcG2/6DIvvFlNHMHKIXhVHgvsesnG9d8O/dG8nJoE8GzaMiD/jiLSja opxs5Usibvzq3JEJAz/+GR2pZng3Ti7orj/D8ksfGuClWReuPVnGc8dr8h7dwU4DxpHcaLVV4I/N RZUXm6pjfZqCZIUBN0u9h6XMaYqX+XvdNmuur5hAk5PwZAyGWMQ0hgPEUIUWLCJ2EMk3xd/EbUDw OhmZIp8uarO8c0NrIm5fktRktQN9d4wxFfXRaGn+VEjd2u4reKTn8qXbk5QrsFi2YZZf9UCu8k0R Svk3cTlrrFuFDy1y47VytWZ97IIU66gkX1l06CmI/E5lCyyMhHrNogwZ07phrMiQifwQYBgvMOvq A1sGIwERABKcVqlQ4i8KzuSHMIDe7jonFiIAAsExT9RJuNVtsUmUosfs81sKwM
X-QQ-XMRINFO: MPJ6Tf5t3I/ycC2BItcBVIA=
Date: Tue, 23 Jan 2024 11:33:27 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, Acee Lindem <acee.ietf@gmail.com>, lsr <lsr@ietf.org>
References: <C38046FD-E8BD-4309-8CA2-966F9FD50637@gmail.com>, <2088c16da01f407a91de90f171ef1a3f@huawei.com>
X-Priority: 3
X-GUID: E1BDADD5-285E-4B2A-849A-687F7A08A2FB
X-Has-Attach: no
X-Mailer: Foxmail 7.2.24.96[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202401231133270073483@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart744000231832_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/J41eImfrQAfhLqkk_ijGyxhyzRc>
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: Tue, 23 Jan 2024 03:33:38 -0000

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)
Date: 2024-01-11 18:37
To: Acee Lindem; Lsr
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>
> 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
> https://www.ietf.org/mailman/listinfo/lsr