[Teas] draft-ietf-teas-yang-path-computation-28 early Rtgdir review

Sue Hares via Datatracker <noreply@ietf.org> Thu, 20 August 2026 12:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@mail2.ietf.org
Received: from [10.244.9.159] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 2664912CDA8FB; Thu, 20 Aug 2026 05:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787229681; bh=+meVBH+UE0AT/UNZnAm5eMOoHcAC598J/MkrL62gICI=; h=From:To:Cc:Subject:Reply-To:Date; b=iba0cmk4XzrmYAIxsciN9lVY4ZIS42RPUvwxzfY5ktptXKW5EnkFK3+DWRDFtyA0r Uw5QQ3I4r01a8d5lT5vQ4vOpBPcd/WrlJm3jxuQjZwEiMaiHxjeH0/6LwTGwHllbSQ IRs3+Ga//tozSZJibg3QNoDunSmpl80xOW4n4WHE=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sue Hares via Datatracker <noreply@ietf.org>
To: rtg-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.71.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178722968088.741621.9099393863357291916@dt-datatracker-7c6ddbc678-lb5nk>
Date: Thu, 20 Aug 2026 05:41:20 -0700
Message-ID-Hash: GRCGORTKQCKRF3OFCD7RT4EFHHT22NI3
X-Message-ID-Hash: GRCGORTKQCKRF3OFCD7RT4EFHHT22NI3
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; 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, teas@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Sue Hares <shares@ndzh.com>
Subject: [Teas] draft-ietf-teas-yang-path-computation-28 early Rtgdir review
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/PMfYdrK0LKFJK-xEkBIwgOv1VRI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Document: draft-ietf-teas-yang-path-computation
Title: A YANG Data Model for requesting path computation
Reviewer: Sue Hares
Review result: Has Nits

This is an early review for draft-ietf-teas-yang-path-computation-28.txt.
Reviewer: Susan Hares 
Caveat: I am not a yang doctor. I have not implemented or operated 
code that uses this model. 

Summary: Ready with NITS 
Excellent technical work that is logically consistent with previous work. 
Thank you to authors for excellent work! 

What is covered in this early review: Technical concepts, logical consistency, and yang concept
What is not covered in this review:
1) detailed editorial review of sentence grammar - tools 
2) detailed yang grammar - hopefully the Yang tools 

I did note two things editorial in passing: 
section 1.2 - PCE definition phrase "on an out-of-network-server, etc"
seems to be confusing.  Please check against PCE RFCs. 

Yang text: Does not seem to have complete sentences with periods in all descriptions. 

NITS: 
issue 1:  section 5.3, tunnel attribute list, binary type for 2 variables 

why are are these two variables binary? It is unclear from the text why these
two variables are binary.  A sentence on why these are binary would be helpful. 
I suspect it is to indicate wheter you are using source and destination - respectively. 

+--src-tunnel-tp-id  binary 
+--dst-tunnel-tp-id  binary

Issue 2: use of choice path-role in Yang statement 

It is not clear why you are using the yang form 
"choice path-role {
    When 'not (./source) and (.destination)'{
	
I think it is because you tried to do something in section 5.3. 
This tries to implement the constraint you are placing in the 
description in issue 1.  I'm just not sure if this is logically correct or 
incorrect.  Please add text explaining it for issue 1. 
Plesae double check this yang "when" statement. 

Issue 3: Augmentation of RPC filter types 

The augmentation of: 

Augment "/te: tunnels-actions/te:input/te:tunnel-info/" + "te:filter-ty pe"

uses a when statement of 
"when "derived-from-or-self"(../te:action-info:/te:action,"
     +"'tunnel-acitonm-path-comput-delete"

I think you are trying to add a path-delete function to the path-compute-delete group. 
I do not know if this correct. 

Issue 4: Security section 

It is not clear if you should be specifying some additional NACM handling and 
datastorage for the information you have identified as sensitivie. 
Is sensitive equivalent to network "critical information?"