[RTG-DIR] Rtgdir last call review of draft-ietf-rtgwg-yang-rib-extend-16

Zhaohui Zhang via Datatracker <noreply@ietf.org> Mon, 01 May 2023 18:43 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 91082C151986; Mon, 1 May 2023 11:43:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zhaohui Zhang via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
Cc: draft-ietf-rtgwg-yang-rib-extend.all@ietf.org, last-call@ietf.org, rtgwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 10.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <168296662458.49135.11152971610183102502@ietfa.amsl.com>
Reply-To: Zhaohui Zhang <zzhang@juniper.net>
Date: Mon, 01 May 2023 11:43:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/Y-D0SJlg0i42ImkP5J9RqVROhG4>
Subject: [RTG-DIR] Rtgdir last call review of draft-ietf-rtgwg-yang-rib-extend-16
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: Mon, 01 May 2023 18:43:44 -0000

Reviewer: Zhaohui Zhang
Review result: Has Issues

I have the following one nit comment and one question:

  augment "/rt:routing/rt:ribs/rt:rib/"
    + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
    + "rt:next-hop-list/rt:next-hop-list/rt:next-hop"
  {
    description
      "Augment the multiple next hops with repair path.";
    uses repair-path;
  }

The description is slightly misleading. It is to agument a single next-hop in
the next-hop-list, not "multiple next hops".

Shouldn't the repair path be applicable to static routes as well?