[netconf] Re: draft-ietf-netconf-yp-transport-capabilities-05 ietf last call Tsvart review
Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 10 November 2025 22:03 UTC
Return-Path: <mjethanandani@gmail.com>
X-Original-To: netconf@mail2.ietf.org
Delivered-To: netconf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 27E4987290A0 for <netconf@mail2.ietf.org>; Mon, 10 Nov 2025 14:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hq9gMPUf_e3W for <netconf@mail2.ietf.org>; Mon, 10 Nov 2025 14:03:10 -0800 (PST)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D4FB68729010 for <netconf@ietf.org>; Mon, 10 Nov 2025 14:03:10 -0800 (PST)
Received: by mail-pg1-x536.google.com with SMTP id 41be03b00d2f7-ba488b064cbso2448707a12.1 for <netconf@ietf.org>; Mon, 10 Nov 2025 14:03:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762812184; x=1763416984; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=PDbiXaNnTIb8lUUSTXURtrVL+erOa/K+u60wUfPpYvM=; b=Vxy+hHGEYatELOKJ0d9OvbNI3XNW5f9je/mr8lqOYQoMbXKL0ESYQh5TNsNJKAMjlr UXHWpADrkeEMuAzcYXTVKUzMuRIJoGF4YqMwtcAsmTxDUwQN6dZgCC53F3Rmi43E057W jfM9pSewA2X9Y1UIYwuOU8rZgqj4URxtUDqQK/XyYr9IJX3LJzoSlHK8LD0P0AhhQyei jqbBpYVnPawnDdrHmaro47Fv/7vjeFw1ixtgglgehZVHnrV5NhkljaSvtb8+fXTXI9yN wDuOU7ttrJwVwwzTjyYG7u5xV905iztYxhnRmyTEsRrNjtK4OTCr5E+xZ48RWY4SQ5XL 0tFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762812184; x=1763416984; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PDbiXaNnTIb8lUUSTXURtrVL+erOa/K+u60wUfPpYvM=; b=lFmjcMjpHJjg1HjQGZLQBiG3rTop8xCIOog8A0Fqab6PBziRPXhrk5z0LPDWa30SRU RyEjIhxEA6Ooj0H8IQ2PAKGupp0mmW7XxvI7iqRJ8bC8/qQJvm964KRRrmu/IOW0cUBM Y3TPvSkSBF6+ca9v67AqbSWdo0mNV2PtZiXOltNcpPBcdfq5j8k9tgGne1C8JyBMtVo5 +h8U03QG1heSwsK6f/addB9riIEcQV1i0KnNkTe63Yb5xIV8GliMjOusuAgrR21EB49T kQYEwTvPLmNEgtvEtUIJezfiiITkvgg+foM7Z1lumQgJ0GtptVTFhJvGIyQiMgOlboS2 THfQ==
X-Forwarded-Encrypted: i=1; AJvYcCXA19Za6Xf4S9/4UewRG7sSYlMh62FcusdykPmgb4BssJ8pUcH/mMyhJGEZzHtpjtOHHl8+bbY5@ietf.org
X-Gm-Message-State: AOJu0YwE+vde4t1QEn3xpv7ZZZobCd/qd9UXUxT9nPL3XkleHzVQ8/fs bgW25VneIuMDk5InhQRjvglcfitdUD2hg2REZU8qFaMOZUVjZEqQ+fLH
X-Gm-Gg: ASbGncsWdG/9ahy+tY5TSrZTTn3d/PLn1Hiy7c3r1kE+Ir+6vjRUaumqtoSRVKzkOwA je/Um0yc633HuM3Dl9W276uxTJiwqYoZw8kYLz/v5BDS1Ffzl+7MQA/tPPto3ONpKv+mVoP5LSy GvNE2jtcA2h2SO1H0uVKWhT+Art82++3KzDcnKEjnwZ9oVTCuGQqv7N6EUIC/o8nUsgQIni1hDJ WNfZFiasaDm7SptfjTa4gBtU7fW5kduze0o/IkM19eANKs8iWIGqIJ7ZWpAF2qXTdA5/iaIpYfH SbfgiTcrqKdBWHL79dqqI9YmkIy8idxOTFjxZXhBkwPw8yuwQZPB0avEqe8+woVlwu/wIGrcDRX WDvbtE12vCz1Ys61o81jaLk2xpQ04ROcIf3Rh4FNSAsCiMCHUrAlKpfiItWjnfQspAlzNyuU05o oGW3FlTkdr1u7IDjdaOvoW
X-Google-Smtp-Source: AGHT+IH2LMnkw+NXEx/O+wmx+kovjXDxuKEJ4Mu2cgjSWHyqyobW2/0AB8Sg95mr095hbx4uerxJaA==
X-Received: by 2002:a17:902:c94b:b0:294:9813:4512 with SMTP id d9443c01a7336-297e540dd6fmr131820255ad.3.1762812183386; Mon, 10 Nov 2025 14:03:03 -0800 (PST)
Received: from smtpclient.apple ([38.99.102.194]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-29650c5ce87sm155763265ad.29.2025.11.10.14.02.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Nov 2025 14:03:02 -0800 (PST)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <61E34D8E-C4E3-40CC-9F32-04E8A95BCB7A@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D96BE7F8-F622-45C1-BEF1-CE40CAD3EA1D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
Date: Mon, 10 Nov 2025 14:02:55 -0800
In-Reply-To: <ZR1P278MB1170BDD779F7A756D09FC87A89FAA@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
To: Thomas.Graf@swisscom.com
References: <176005210101.918.11444865489939710929@dt-datatracker-84f8f646b-tg6mn> <ZR1P278MB1170BDD779F7A756D09FC87A89FAA@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Message-ID-Hash: LJEGHOWNBKSAURXIHVHV6YOLK3T2HPXZ
X-Message-ID-Hash: LJEGHOWNBKSAURXIHVHV6YOLK3T2HPXZ
X-MailFrom: mjethanandani@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Tommy Pauly <tpauly@apple.com>, tsv-art@ietf.org, draft-ietf-netconf-yp-transport-capabilities.all@ietf.org, last-call@ietf.org, NETCONF WG <netconf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: draft-ietf-netconf-yp-transport-capabilities-05 ietf last call Tsvart review
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/c2w8Xi9ySgGrh0MYYxhK0kZzM4U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>
Hi Thomas, Thanks for responding to Tommy’s Tsvart review. Some follow-up comments to what Tommy brings up. > On Oct 29, 2025, at 3:48 AM, Thomas.Graf@swisscom.com wrote: > > Dear Tommy, > > On behalf of the authors. Thanks a lot for the review and apologies for the late reply. Inline the feedback. > > I hope the explanations bring clarity and I am looking forward to suggestion to improve the document. Please don't hesitate to suggest improvements beyond the document scope, perhaps on YANG-Push (RFC 8639, 8641) itself. Since we are working on https://datatracker.ietf.org/doc/html/draft-wilton-netconf-yang-push-lite, this could be incorporated in YANG-Push Lite perhaps. > > Best wishes > Thomas > > -----Original Message----- > From: Tommy Pauly via Datatracker <noreply@ietf.org> > Sent: Thursday, October 9, 2025 7:22 PM > To: tsv-art@ietf.org > Cc: draft-ietf-netconf-yp-transport-capabilities.all@ietf.org; last-call@ietf.org; netconf@ietf.org > Subject: draft-ietf-netconf-yp-transport-capabilities-05 ietf last call Tsvart review > > > Be aware: This is an external email. > > > > Document: draft-ietf-netconf-yp-transport-capabilities > Title: YANG Notification Transport Capabilities > Reviewer: Tommy Pauly > Review result: Ready with Issues > > This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. > > When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@ietf.org if you reply to or forward this review. > > Thanks to the authors for this document. I want to preface my review by making it clear that I'm not a YANG expert; the majority of this document is the YANG definition itself. > > However, from a transport perspective, I do find aspects of this structuring potentially confusing. Having definitions that have names as broad as "transport protocol", "security protocol", etc, raise questions. Are there concrete and finite definitions of the values that can go in these fields? Or is this something relatively freeform and expandable? The current two examples of "transport protocol" are UDP and HTTPS. In an enumeration of transport protocols in another context, this would be a surprising list. While HTTP is used as a mechanism for transport in some contexts, one would most often expect a list like this to be TCP, UDP, QUIC, etc. My assumption is that this is really an enumeration of the specifically defined YANG notification substrates. > Having the name be notify-transport, notify-substrate, or similar, might be clearer. > > TG> As you already understood the document doesn't define transport or security protocols nor encodings for YANG-Push configured subscriptions (https://datatracker.ietf.org/doc/html/rfc8639#section-2.5) YANG metrics can be subscribed in YANG-Push dynamically (https://datatracker.ietf.org/doc/html/rfc8639#section-2.4) or with configuration. Where dynamically the data collector establishes a as a netconf/restconf client a netconf/restconf session to the netconf/restconf server of a network node. Once session is established, it subscribes to the pre-established session the YANG metrics. In this case the transport, security and encoding is inherited/implied from the previously established netconf/restconf session. Dynamic subscriptions are addressing the network operators needs to temporary subscribe to a set of YANG metrics for instance for troubleshooting an issue or verifying a maintenance window. Once the netconf/restconf session is teared down, the YANG-Push subscription is being removed. Where in configured subscription the principle is the same but instead of the previously established netconf/restconf session, the YANG metrics are now published through a separate session and remains configured even after netconf/restconf session teardown or network node reboot. YANG-Push configured subscriptions are used by network operators to maintain a so called digital twin from the network node. Obtaining the inventory (components installed) and its current state and state changes and statistical metrics. Tommy brings up a good point around use of “transport protocol”, “security protocol” in this document. Those have very specific meanings in all IETF documents and are understood to be different from how they are used in this document. I think it would make sense to make definitions in this document for things such as transport or security to be more specific to how they are used in this document. In that sense, having definitions such as ’notify-transport-protocol’ and ’notify-security-protocol’ would make it clear that these are transport or security protocols for notification purposes. > > RFC> RFC 8639 resp. 8641 defines the base mechanics how transport and security protocols and its encryption should be defined during the subscription phase and examples with https://datatracker.ietf.org/doc/html/rfc8639#appendix-A how ietf-subscribed-notifications@2019-09-09.yang should be augmented for YANG-Push configured transport protocols. The Netconf working group has two documents defining transport protocols for YANG-Push configured subscriptions: https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif, https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif. You might find https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/123/Hackathon/ietf-123-hackathon-validate-yang-push-publisher.pdf, https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/123/Hackathon/ipf-zbl1327-r-daisy-91_cisco_iosxr_20250718_115020-IOSXR2541/udp_notif_capture.pcap and https://github.com/network-analytics/udp-notif-dissector useful. It describes the YANG-Push IETF 123 hackathin activities, a pcap of 1 out of 4 example implementations and a Wireshark dissector. > > TG> RFC 9196 addresses one of the most important, yet simple, problems of today's network operator when subscribing YANG metrics: What can I subscribe. However in case of subscription it misses the aspect in YANG-Push configured subscription with which transport protocol and security protocol and with which encoding. This is what this document is covering. > > What is the process for expanding the list of possible values? Since you have "security transports" as an orthogonal concept to the "transport protocols", how do you capture the ways those protocols compose and interact? For example, if you're using HTTP/3, which is over QUIC, you cannot select TLS 1.2. I can imagine that this will get more complex going forward. Perhaps a way out of this is to focus on an enumeration of known profiles for how the notifications are handled (DTLS 1.3 + UDP as a set) rather than having combinations be expressed that may not make sense. > > TG> The process of expanding YANG-Push configured subscriptions is described in https://datatracker.ietf.org/doc/html/rfc8639#appendix-A. Currently defined transport protocols/security protocols are https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif, https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif. True. If the only defined “transport” is HTTP and UDP, it beehoves us to define the nodes in the model in a way that is specific to these two types of transport, and not the generic transport protocol, which are widely known as TCP, UDP and now QUIC. In other words, we are talking about a notif specific transport, with its own set of security protocols/(D)TLS versions. Thanks. > > I'll note that the HTTPDIR review [1] of the HTTPS "notification transport" > document also referred to using HTTP as a "substrate" more than a "transport". > That might be a helpful direction for the terminology. > > [1] > https://datatracker.ietf.org/doc/review-ietf-netconf-https-notif-15-httpdir-telechat-nottingham-2024-02-02/ > Mahesh Jethanandani mjethanandani@gmail.com
- [netconf] draft-ietf-netconf-yp-transport-capabil… Tommy Pauly via Datatracker
- [netconf] Re: draft-ietf-netconf-yp-transport-cap… Thomas.Graf
- [netconf] Re: draft-ietf-netconf-yp-transport-cap… Mahesh Jethanandani
- [netconf] Re: draft-ietf-netconf-yp-transport-cap… Thomas.Graf
- [netconf] Re: draft-ietf-netconf-yp-transport-cap… Thomas.Graf
- [netconf] Re: [Tsv-art] draft-ietf-netconf-yp-tra… Mahesh Jethanandani
- [netconf] Re: [Tsv-art] draft-ietf-netconf-yp-tra… Thomas.Graf
- [netconf] Re: [Tsv-art] draft-ietf-netconf-yp-tra… Mahesh Jethanandani