[Gen-art] draft-ietf-teas-yang-path-computation-28 ietf last call Genart review

Linda Dunbar via Datatracker <noreply@ietf.org> Wed, 02 September 2026 23:00 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@mail2.ietf.org
Received: from [10.244.8.80] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 61DF313449355; Wed, 2 Sep 2026 16:00:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788390045; bh=4+NgpRrYkGlDbeo8S33CEG00RByfcAZU8H3RZHFqyL4=; h=From:To:Cc:Subject:Reply-To:Date; b=VZsxKgSSjakha3VTZPiHzTFDZoWp637BqK0p/Ngh+QUhVnC8+DEzV4JSir86jfg8Z WL4asJ3jxJ+FZoaIOiPI6JD4tsOjCxcDAQHpYfV7UYQ4wjZlroTsdWgBp/aCu7PpTR R4gzc401WN/dC0qcwS8Dl+vXsnzeeQVQ5PiZhv14=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178839004523.602369.6363596062009916946@dt-datatracker-6669c7b496-s9mrn>
Date: Wed, 02 Sep 2026 16:00:45 -0700
Message-ID-Hash: AD67IES6SCUVQI2WTSNAT5VTTL4XHKZR
X-Message-ID-Hash: AD67IES6SCUVQI2WTSNAT5VTTL4XHKZR
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-gen-art.ietf.org-0; header-match-gen-art.ietf.org-1; header-match-gen-art.ietf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-teas-yang-path-computation.all@ietf.org, last-call@ietf.org, teas@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Subject: [Gen-art] draft-ietf-teas-yang-path-computation-28 ietf last call Genart review
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Cq5OZt2E5iPVOMArfGuyhBuCO08>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Owner: <mailto:gen-art-owner@ietf.org>
List-Post: <mailto:gen-art@ietf.org>
List-Subscribe: <mailto:gen-art-join@ietf.org>
List-Unsubscribe: <mailto:gen-art-leave@ietf.org>

Document: draft-ietf-teas-yang-path-computation
Title: A YANG Data Model for requesting path computation
Reviewer: Linda Dunbar
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-teas-yang-path-computation-28
Reviewer: Linda Dunbar
Review Date: 2026-09-02
IETF LC End Date: 2026-09-09
IESG Telechat date: Not scheduled for a telechat

Summary:
This document defines a YANG data model to request TE path computation by
augmenting the TE tunnel RPCs. Major issues: None Minor issues:

- The document explains three related approaches: stateless path computation
RPC, optional transient state in the operational datastore, and compute-only TE
tunnel paths. The discussion is useful, but it is spread across Section 3.3 and
Section 3.3.1. A short comparison table or summary paragraph would help clarify
when each mechanism should be used. For example:
  The RPC is intended for stateless on-demand computation. The transient-state
  option is used when the client may later request setup of the same computed
  path. Compute-only tunnels are used when persistent tracking of the computed
  path is required.

- Section 3.3 says that path verification is always necessary because the path
set up later may not be exactly the same as the path previously computed. Does
this document defines any verification mechanism, or only requires/assumes that
verification is done by other mechanisms?

Nits/editorial comments:

- Section 1.1:
   s/“RFC number fpr”/“RFC number for”/
- Section 2:
   s/“The presented uses cases”/“The presented use cases”/

- Section 2.2:
   s/“inter-domains links”/“inter-domain links”/

- Section 3.3:
   s/“it is possible repeat the whole process”/“it is possible to repeat the
   whole process”/

- Section 3.3.1:
   s/“multi-domain path computation scenario scenarios”/“multi-domain path
   computation scenarios”/

- Section 4:
   s/“there could multiple choices”/“there could be multiple choices”/

- Section 5.3:
   s/“These attributes includes”/“These attributes include”/

- Section 5.4:
   s/“The models supports”/“The model supports”/

- YANG module description:
   s/“exiting te-tunnel”/“existing te-tunnel”/

- Security Considerations:
   s/“also applies to the use of this RPC”/“also apply to the use of this RPC”/

Best Regards,
Linda Dunbar