[RTG-DIR]Re: Rtgdir early review of draft-ietf-idr-cpr-02

"Dongjie (Jimmy)" <jie.dong@huawei.com> Sun, 02 June 2024 14:27 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F982C14F6A9; Sun, 2 Jun 2024 07:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 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, URIBL_DBL_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 gMsOU9qq7KEB; Sun, 2 Jun 2024 07:27:43 -0700 (PDT)
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 B4571C14F699; Sun, 2 Jun 2024 07:27:42 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VsfGT0WNYz67Cnd; Sun, 2 Jun 2024 22:23:13 +0800 (CST)
Received: from lhrpeml500001.china.huawei.com (unknown [7.191.163.213]) by mail.maildlp.com (Postfix) with ESMTPS id C15E51400E7; Sun, 2 Jun 2024 22:27:39 +0800 (CST)
Received: from dggpemf500008.china.huawei.com (7.185.36.156) by lhrpeml500001.china.huawei.com (7.191.163.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Sun, 2 Jun 2024 15:27:38 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by dggpemf500008.china.huawei.com (7.185.36.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Sun, 2 Jun 2024 22:27:36 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.011; Sun, 2 Jun 2024 22:27:36 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
Thread-Topic: Rtgdir early review of draft-ietf-idr-cpr-02
Thread-Index: AQHas4uYIIkOJASgDUqvvJE/TDUykbG0WbFA
Date: Sun, 02 Jun 2024 14:27:36 +0000
Message-ID: <b59bc394bff149b4bdb5567db8cc4d9f@huawei.com>
References: <171718149894.52742.12055748151491642436@ietfa.amsl.com>
In-Reply-To: <171718149894.52742.12055748151491642436@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.216.48.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: 7YHTDNFROEDOOZ2LMGMMBYRR2HOTCID5
X-Message-ID-Hash: 7YHTDNFROEDOOZ2LMGMMBYRR2HOTCID5
X-MailFrom: jie.dong@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-dir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "draft-ietf-idr-cpr.all@ietf.org" <draft-ietf-idr-cpr.all@ietf.org>, "idr@ietf.org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [RTG-DIR]Re: Rtgdir early review of draft-ietf-idr-cpr-02
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/hBbW9ypscI3HOpokJ-vh-Q4mnIc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-dir-owner@ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Subscribe: <mailto:rtg-dir-join@ietf.org>
List-Unsubscribe: <mailto:rtg-dir-leave@ietf.org>

Hi Yingzhen, 

Thanks for the review and comments, we will prepare a new revision to address them. 

And please see some replies inline:

> -----Original Message-----
> From: Yingzhen Qu via Datatracker <noreply@ietf.org>
> Sent: Friday, May 31, 2024 9:52 PM
> To: rtg-dir@ietf.org
> Cc: draft-ietf-idr-cpr.all@ietf.org; idr@ietf.org
> Subject: Rtgdir early review of draft-ietf-idr-cpr-02
> 
> Reviewer: Yingzhen Qu
> Review result: Has Nits
> 
> This is an Early Review, requested by the WG chair.
> 
> Document: draft-ietf-idr-cpr-02
> Reviewer: Yingzhen Qu
> Review Date: May 31, 2024
> Intended Status: Informational
> 
> Summary:
> This draft proposes inter-domain intent-aware routing based on existing
> mechanisms to advertise IPv6 Colored Prefixes: BGP IPv6 Unicast Address Family
> and color extended community.
> 
> Comments and nits:
> 
> The Abstract is a bit long, the authors may consider moving some content from
> the abstract to the introduction.

OK, will reduce the text in the abstract. 

> 
> 
> 233    While in some special cases, one intent may be represented as
> 234    different color value in different domains, then the Color Extended
> 235    Community in the CPR routes may be updated at the border nodes of
> the
> 236    domains based on the color-mapping policy.
> 
> [Q]: why "may be updated" instead of "SHOULD be updated"?
> [comments]: Please consider adding an example of one intent with different
> colors in different domains.

Whether the color needs to be updated or not depends on the color-mapping policy between the adjacent domains. We will add some text to clarify this. 

> 
> 323    forwarding process using H.Insert.Red behavior is shown as below:
> 
> [comments]: Please add a reference for H.Insert.Red .

OK.

> 
> 334    The packet encapsulation and forwarding process using H.Encaps.Red
> 335    behavior is shown as below:
> 
> [comments]: Please add a reference for H.Encaps.Red.

OK. 

> 
> 420    There may be multiple inter-domain links between network domains,. A
> 
> nits: extra ","

Thanks for catching the nit, will fix it in next revision. 

Best regards,
Jie