[RTG-DIR]Rtgdir early review of draft-ietf-idr-cpr-02
Yingzhen Qu via Datatracker <noreply@ietf.org> Fri, 31 May 2024 18:51 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: rtg-dir@ietf.org
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EAFEFC1D4A7E; Fri, 31 May 2024 11:51:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yingzhen Qu via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171718149894.52742.12055748151491642436@ietfa.amsl.com>
Date: Fri, 31 May 2024 11:51:38 -0700
Message-ID-Hash: FEM2XAW4CLVZQGY3UT74GN47PIKYT3WD
X-Message-ID-Hash: FEM2XAW4CLVZQGY3UT74GN47PIKYT3WD
X-MailFrom: noreply@ietf.org
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, idr@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Yingzhen Qu <yingzhen.ietf@gmail.com>
Subject: [RTG-DIR]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/aZV1NyBMuQR3tY0lALXItAzPG8c>
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>
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. 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. 323 forwarding process using H.Insert.Red behavior is shown as below: [comments]: Please add a reference for H.Insert.Red . 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. 420 There may be multiple inter-domain links between network domains,. A nits: extra ","
- [RTG-DIR]Rtgdir early review of draft-ietf-idr-cp… Yingzhen Qu via Datatracker
- [RTG-DIR]Re: Rtgdir early review of draft-ietf-id… Dongjie (Jimmy)