[Idr] Re: Opsdir early review of draft-ietf-idr-cpr-02

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 05 June 2024 17:08 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A669C180B6A; Wed, 5 Jun 2024 10:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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 Ne8WAyS-l-8u; Wed, 5 Jun 2024 10:08:29 -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 9AF82C1E7250; Wed, 5 Jun 2024 10:08:29 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VvYhR0mNfz6K6q6; Thu, 6 Jun 2024 01:03:51 +0800 (CST)
Received: from lhrpeml100003.china.huawei.com (unknown [7.191.160.210]) by mail.maildlp.com (Postfix) with ESMTPS id B36411408F9; Thu, 6 Jun 2024 01:08:27 +0800 (CST)
Received: from dggpemf200009.china.huawei.com (7.185.36.246) 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.39; Wed, 5 Jun 2024 18:08:26 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by dggpemf200009.china.huawei.com (7.185.36.246) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 6 Jun 2024 01:08:24 +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; Thu, 6 Jun 2024 01:08:23 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Dan Romascanu <dromasca@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Thread-Topic: Opsdir early review of draft-ietf-idr-cpr-02
Thread-Index: AQHas43b+eyfkUEdFkK+GBomwskiGbG5QXTA
Date: Wed, 05 Jun 2024 17:08:23 +0000
Message-ID: <6b2117e7341243498d0334fcac8e9b11@huawei.com>
References: <171718247206.34624.2098415723570266398@ietfa.amsl.com>
In-Reply-To: <171718247206.34624.2098415723570266398@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: OM7HZ2VA6RL5O4LU6TMKWRDY7XMMMZOA
X-Message-ID-Hash: OM7HZ2VA6RL5O4LU6TMKWRDY7XMMMZOA
X-MailFrom: jie.dong@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.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: [Idr] Re: Opsdir early review of draft-ietf-idr-cpr-02
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4MF-jvGDJkYk7cIYkRhxRbE6tBk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi Dan, 

Thanks a lot for your review and comments, please see some replies inline: 

> -----Original Message-----
> From: Dan Romascanu via Datatracker <noreply@ietf.org>
> Sent: Friday, May 31, 2024 10:08 PM
> To: ops-dir@ietf.org
> Cc: draft-ietf-idr-cpr.all@ietf.org; idr@ietf.org; dromasca@gmail.com
> Subject: Opsdir early review of draft-ietf-idr-cpr-02
> 
> Reviewer: Dan Romascanu
> Review result: Has Issues
> 
> Thus is an early OPS-DIR review of draft-ietf-idr-cpr-02.
> 
> The document aims Informational Status.It describes a mechanism to advertise
> IPv6 prefixes in BGP which are associated with Color Extended Communities to
> establish end-to-end intent-aware paths for SRv6 services. Such IPv6 prefixes are
> called "Colored Prefixes", and this mechanism is called Colored Prefix Routing
> (CPR).
> 
> Operators that have under their responsibility multi-services networks running
> BGP should be familiar with this document.
> 
> From and Operational and Manageability point of view this document is Almost
> Ready. I found two issues that require clarifications.
> 
> Operational Considerations are described in Section 4. I found two places where
> clarifications are needed:
> 
> 1. The first paragraph is unclear to me. What does the sentence 'While an
> operator may prefer a BGP-based solution for the reasons described there.'
> mean? I guess that this is related to the previous statement (' ... the inter-domain
> intent-aware routing may be achieved with SR Policy across multiple domains,
> and services with specific intent can be steered to SR Policy at the ingress domain
> based on Color') with the intention of defining an exception, but the grammatical
> inconsistency makes the statement vague.
> Clarification is needed.

Sorry for the confusion caused by this text. Actually "the reasons described there" means the reasons described in [I-D.hr-spring-intentaware-routing-using-color], which is referred to in the first half of this sentence. 

We can break this into shorter sentences to make this clearer. 

> 
> 2. The following paragraph reads:
> 
> > There may be multiple inter-domain links between network domains,. A
>    border node may receive CPR routes from multiple peering border
>    nodes.  Then the border node may take the attributes of the inter-
>    domain links and/or the attributes of the received CPR routes into
>    consideration to select the best path for specific Colored Prefixes
>    to better meet the intent.  The detailed mechanism is up to the
>    operator's policy.
> 
> The first sentence seems incomplete. Moreover, what if the network domains
> belong to different operators with different policies? Operator's policies need to
> be somehow synchronized. How?

Thanks for catching this nit. Either the comma in the first sentence should be removed, or the period is removed and an "and” is added to the beginning of the next sentence. 

The operator's policy here refers to the mechanism used to select the best path from multiple received CPR routes. Yes the policy used in different domains needs to be consistent. Some coordination between the domains is needed, this is similar to the coordination of the color-mapping policy. We can add some text to make it clear.

Best regards,
Jie