[Lsr] 回复: draft-zhu-lsr-isis-sr-vtn-flexalgo-01

zhuyq8@chinatelecom.cn Fri, 09 October 2020 06:33 UTC

Return-Path: <zhuyq8@chinatelecom.cn>
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 950293A09CF for <lsr@ietfa.amsl.com>; Thu, 8 Oct 2020 23:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 K6qc9aSCThzo for <lsr@ietfa.amsl.com>; Thu, 8 Oct 2020 23:33:00 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.219]) by ietfa.amsl.com (Postfix) with ESMTP id 051A53A0846 for <lsr@ietf.org>; Thu, 8 Oct 2020 23:32:59 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:2168.1863574955
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-120.88.10.46?logid-55ad9888b1be4333bdfb83e70c742fdd (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 6DC5E2800A3; Fri, 9 Oct 2020 14:32:44 +0800 (CST)
X-189-SAVE-TO-SEND: 44031110@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id 55ad9888b1be4333bdfb83e70c742fdd for huaimo.chen@futurewei.com; Fri Oct 9 14:32:46 2020
X-Transaction-ID: 55ad9888b1be4333bdfb83e70c742fdd
X-filter-score: filter<0>
X-Real-From: zhuyq8@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: zhuyq8@chinatelecom.cn
From: zhuyq8@chinatelecom.cn
To: 'Huaimo Chen' <huaimo.chen@futurewei.com>, lsr@ietf.org
References: <160138654056.12980.329207214151594381@ietfa.amsl.com> <DM6PR05MB63482DBC001DD56BEF6F7311AE320@DM6PR05MB6348.namprd05.prod.outlook.com> <CAKz0y8w5VOf_=baG6UCP8Q9s=VLM2ghT2jhiF5FZNN4JXB23eA@mail.gmail.com> <DM6PR05MB63485389C261CA2E0C08DE50AE330@DM6PR05MB6348.namprd05.prod.outlook.com> <0f85212d-fac7-47ea-a608-4f53061cbf02@Spark> <DM6PR05MB63480E863599BBC810BF334AAE300@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV2+jhjAfxq5FzaukdhCOqXvGCkv75xYWcStN=SCrpni4Q@mail.gmail.com> <f4fdff8b-fe11-cb75-3cd7-7766baedf730@cisco.com> <CB2F6A55-B231-4A2D-821C-D3F2ABE6649E@futurewei.com> <cfae6af4-23d0-44b0-8bb3-f5e631b4c805@Spark> <CABNhwV3MmJeVMhGHqyGzwshSYVijquGsxaNFaryu5mF3j8n_zA@mail.gmail.com> <047be764-8203-ca46-7ee1-6f84f7bf2356@cisco.com> <CABNhwV3MMpMBQL_PXVFmX3RMkKXJVV0PTn4PvB0ctyHfRAMbuA@mail.gmail.com> <e5c2621e-fd94-5cf3-32bc-e7ccd7215714@cisco.com>, <CABNhwV0Y5qT7M3yDfK=PE2sk9BKLxuUNmXb3LV0Ws_hz=8vuYA@mail.gmail.com> <MN2PR13MB3117442307E6038B3F15F248F20D0@MN2PR13MB311 7.namprd13.pro d.outlook.com>
In-Reply-To: <MN2PR13MB3117442307E6038B3F15F248F20D0@MN2PR13MB3117.namprd13.prod.outlook.com>
Date: Fri, 09 Oct 2020 14:32:44 +0800
Message-ID: <002501d69e06$01084580$0318d080$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01D69E49.0F3F82B0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGKD7LFtv7e4JvKKSLeoBEBPZfcqAF3GgshAhtpkQ0CZ2c23QJFk5K4AiG0AhkBayX8DwEyA2XiAsh2sogBxUNl4QKQWbEGAt9qosQBTy1ERgEQ2QqnAgWoeQkCXt015ak5553A
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/Jb_17Ys5XPB9SCifsrLzKw6Lv5M>
Subject: [Lsr] 回复: draft-zhu-lsr-isis-sr-vtn-flexalgo-01
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 09 Oct 2020 06:33:03 -0000

Hi Huaimo, 

 

Thanks for your review comments, please see some replies inline with [YQ]:

 

 

发件人: Lsr <lsr-bounces@ietf.org> 代表 Huaimo Chen
发送时间: 2020年10月7日 5:57
收件人: lsr@ietf.org
主题: [Lsr] draft-zhu-lsr-isis-sr-vtn-flexalgo-01

 

Hi Authors,

 

    I have the following comments/questions on the draft.

 

    In section 2 "Advertisement of SR VTN Topology Attribute", 

for the last sentence "..., the Flex-Algo identifier could be reused 

as the identifier of the VTN in control plane.",

 

How do you reuse the Flex-Algo identifier?

[YQ] The “reuse” here means to make use of the existing Flex-Algo
identifier to represent VTN, rather than defining a new identifier. 

    Does every VTN have a Flex-Algo identifier?

    If so, where does the Flex-Algo identifier of every VTN come from?

[YQ] Yes, every VTN needs to be represented with a unique Flex-Algo
identifier. The Flex-Algo identifier comes from network planning. 

    In section 3 "Advertisement of SR VTN Resource Attribute", 

    is new flag "V" (Virtual) defined in this draft as an extension to RFC
8668?

[YQ] Yes, this is an extension to RFC 8668. 

    If so, should an IANA request/action in section "IANA Considerations" 

be added for this extension?

[YQ] Currently there is no IANA registry for the flags of L2 Bundle Member
Attributes TLV defined in RFC 8668, thus this new flag is described in the
text only. While a new registry may be created if the WG believe it is
helpful. 

    If not (i.e., it is defined in another draft), 

it is better to remove the definition of flag "V" from 

this draft and add a reference to another draft.

    In this case, it seems that there is no IANA request from this draft. 

It would be better to change the intended status of the draft from 

the standards track to informational. 

[YQ] As explained above, a new flag is proposed in this document, thus it is
appropriate to make it standard track.

Some nits: 

In section 2, the second sentence of the last paragraph,

should "to used" be changed to "to use"?

 

In section 3, the first sentence of the second paragraph,

should "was defined to advertise" be changed to 

"defines the advertisement of"?

  [YQ] Thanks for catching the nits, we will fix them in next revision. 

 

Best regards,

Yongqing Zhu

  

Best Regards,

Huaimo