[RTG-DIR] Rtgdir last call review of draft-ietf-isis-sr-yang-17

Shuping Peng via Datatracker <noreply@ietf.org> Fri, 24 November 2023 08:37 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 7896CC19849A; Fri, 24 Nov 2023 00:37:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shuping Peng via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: draft-ietf-isis-sr-yang.all@ietf.org, last-call@ietf.org, lsr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 11.15.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170081504148.43244.1820947622791098734@ietfa.amsl.com>
Reply-To: Shuping Peng <pengshuping@huawei.com>
Date: Fri, 24 Nov 2023 00:37:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/PYhXI5gv5ucP_g9xUABk4xxzcTA>
Subject: [RTG-DIR] Rtgdir last call review of draft-ietf-isis-sr-yang-17
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Nov 2023 08:37:21 -0000

Reviewer: Shuping Peng
Review result: Has Issues


I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.

Document: draft-ietf-isis-sr-yang
Reviewer: Shuping Peng
Review Date: 2023-11-24
IETF LC End Date: 2023-11-30
Intended Status: Standards

I have some minor concerns about this document that I think should be resolved
before publication.

Major Issues:
 "No major issues found."

Minor Issues:
1. Page 3, when configure adjacency-sid, do we need to indicate the neighbor's
systemid or IP in order to differentiate the different neighbors in the case of
having multiple neighbors?

augment /rt:routing/rt:control-plane-protocols
    +--rw segment-routing
       +--rw adjacency-sid
          +--rw adj-sids* [value]
          |  +--rw value-type?   enumeration
          |  +--rw value         uint32
          |  +--rw protected?    boolean

2. Page 4, since LFA, RLFA and TI-LFA are the three algorithm for computing
backup paths, why they are not in sibling relationship?

  augment /rt:routing/rt:control-plane-protocols
    +--rw ti-lfa {ti-lfa}?
       +--rw enable?   boolean
  augment /rt:routing/rt:control-plane-protocols
    +--rw use-segment-routing-path?   boolean {remote-lfa-sr}?

3. Page 4, the keys of the global-block and local-block are not clear.

  augment /rt:routing/rt:control-plane-protocols
    +--ro sr-capability
    |  +--ro sr-capability
    |  |  +--ro sr-capability-bits*   identityref
    |  +--ro global-blocks
    |     +--ro global-block* []
    |        +--ro range-size?    uint32
    |        +--ro sid-sub-tlv
    |           +--ro sid?   uint32
    +--ro sr-algorithms
    |  +--ro sr-algorithm*   uint8
    +--ro local-blocks
    |  +--ro local-block* []
    |     +--ro range-size?    uint32
    |     +--ro sid-sub-tlv
    |        +--ro sid?   uint32
    +--ro srms-preference
       +--ro preference?   uint8

4. Currently there is no configuration node for the micro loop avoidance
any thoughts or plan on it?