[netconf] Re: [Technical Errata Reported] RFC8639 (8073)
Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 26 May 2026 05:04 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 33742F4F04D9 for <netconf@mail2.ietf.org>; Mon, 25 May 2026 22:04:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779771893; bh=rSCL7AMd8iFx0nUxICN01oo8OfVdfx9DAH7PDNlMgio=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=QcLdh0fKcpCeSx+HbJBhSW42d0tIae9Chnzst86SJ9GiEArKXfrA3CBGumLs5NEAB PE8XJ0tCS+9wYSOba8JrFPwqa7Ekp+kuhanpdHC8nas6G6ca+iYHxGmZJW/+MXFAy9 OGm9e8k2KXprF96QM1SBIJZF2UNuwZkwUuXiZmZI=
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 lFHv_zwBmKGx for <netconf@mail2.ietf.org>; Mon, 25 May 2026 22:04:51 -0700 (PDT)
Received: from mail-dy1-x1335.google.com (mail-dy1-x1335.google.com [IPv6:2607:f8b0:4864:20::1335]) (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 D1DE4F4F04BE for <netconf@ietf.org>; Mon, 25 May 2026 22:04:51 -0700 (PDT)
Received: by mail-dy1-x1335.google.com with SMTP id 5a478bee46e88-3042a388168so2985061eec.1 for <netconf@ietf.org>; Mon, 25 May 2026 22:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1779771891; x=1780376691; 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=OOcXIt5BGykcrAjZp4Ap/qEvvVeU1IX0jBwBVOPxDvk=; b=huacUflVXFUW7CVWT6po4I8c44pre+Cy5mDz+RT7ITyCg0MvZMM89Lq8KmG/PDTXDs QYEShaDfTo/wvB6ekP9ap58LiKpBNxJAYdXxrmjtTFph2wO97MO2zSKtPFL49E+fBIzk swKT+TEIgqFJCpnrn5f1givFLLkyvTFekrayMzreWF6cpjNr8rvRRociIGlWHUTgEl+p o315v/SObvFTd5htxTYUmQmw1vA3LJSPwCka64dc8HUbVwk5pWf6fH+VKR7U+B327HO8 Ibo1bc8fxe+TfHJUVfl1BdWmdunZKn+K2qwnftHmj42DCS2oXvcg+tVNbHrwJPDwf/IW Wvig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779771891; x=1780376691; 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=OOcXIt5BGykcrAjZp4Ap/qEvvVeU1IX0jBwBVOPxDvk=; b=CDDGlBQ6CGt4KGf5H/+58QKk4Bwk42MbO4iI/4UuCT6AQdkZBl8gGJLlpNnJemk7P5 aM2mUf4PQbe36hG4zV9W2TbvQSOXLu1IZJ8HVYMhrg2gEu9BYLCXCTQU8rEqU8H2aNjY vU5PwnF8FHHuJwyajA7y3idc3W7HLC+XDfj4TefjNwGn71Bi97c77mN3BGSWtrDmH9v9 y5FgGldL71JazqWq5oNgtabgRiO9wPTHFTubs4NQ1ZBG65kKRERoKgLJkA4BGUXhQBBX 8V7WEjw6Ho4G3ekQpdTTvXSI3tXkPxDy1eKGF55ASGGmIyFoayRiGigYCfN0Rr1YRwV0 2DQw==
X-Forwarded-Encrypted: i=1; AFNElJ8ttAa1tzqCic1C6dFVR9MOFVCFg9RYO2p8G/rQ3A8np4UNfD+YbI093DZn2GPSouvM+THX2g8i@ietf.org
X-Gm-Message-State: AOJu0YzVps+o23A0VTMPGTPgy28AJZTMybrdM+RWcYCUFuJeQIyE4y6L WuvXTvdGXfEyuMCyV7Cq0i18O3FawW219wN4SFjwqWzAgf4MmCAf21Dh
X-Gm-Gg: Acq92OHChPZgGCNTxF3PFkEg+Tbi+vk0cw9y0KQHER6qS/9vrohVKqyWyDiPQyJDF02 a+a6s8QoygXZmG72UAky1AKOYGNclUIb4QWdpmPcAq16/m/GHRdtBDCY0jld7rrLR2SlRUvBqiW CZXtD6nJGGGXxnT5tBPMaLPyUPoOWiMqoUydeqfFlewakDNDujZP5fBU8y3nBD0GPJVVrbmrCUn XqASnvsH2a+FroEp6ZyJNC9AUPEkxd482LskB1qNMPGkGbPrqGSB7J5SEeNbyjIpErFO/WWr582 f1arFM3prLplPsr7409BkHKi+9QQ1Sesr6cAVKUTHs6/2PQaWp19KeVL6dtyqtL9UqRBhS4hZ4H cw2JgiZfIroEzUimVik6lqlxPFhfDtBckRp+wHt8hHgERtEMd9s+eeKjGnkj8zcijQrDFgSuqbp H+jL43C/A72DBtj6nIbIKqr+5E5DeIpJdyvp5qGebj3YIIGcij7ZWEOENJNIwn6DHzeB9xWAyVq dJJLxc=
X-Received: by 2002:a05:7300:6d07:b0:2ef:e4:c912 with SMTP id 5a478bee46e88-30430633524mr8759252eec.9.1779771890687; Mon, 25 May 2026 22:04:50 -0700 (PDT)
Received: from smtpclient.apple (c-67-180-189-3.hsd1.ca.comcast.net. [67.180.189.3]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-3045225b7b6sm13057316eec.25.2026.05.25.22.04.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 May 2026 22:04:50 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <41C761F2-3026-4B76-BC62-EFB35CC18C41@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_56B65E63-F5EE-416A-9BDB-E4C01783A6AD"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.21\))
Date: Mon, 25 May 2026 22:04:38 -0700
In-Reply-To: <9fd388d9415e421a8011bdf4a21320ec@huawei.com>
To: "maqiufang (A)" <maqiufang1@huawei.com>
References: <20240811004051.B09C33B873@rfcpa.rfc-editor.org> <c8794873-2dc1-481d-8e46-a52030b88397@cesnet.cz> <ZR1P278MB1170E675E4EB427821107D6D890A2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM> <ZR1P278MB1170C4CA77BE2AB9F674B478890A2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM> <9fd388d9415e421a8011bdf4a21320ec@huawei.com>
X-Mailer: Apple Mail (2.3731.700.6.1.21)
Message-ID-Hash: KOIVURHNFKG4TECMD2PCPY3GGSUMODZT
X-Message-ID-Hash: KOIVURHNFKG4TECMD2PCPY3GGSUMODZT
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: "Thomas.Graf@swisscom.com" <Thomas.Graf@swisscom.com>, "Roman.Janota=40cesnet.cz@dmarc.ietf.org" <Roman.Janota=40cesnet.cz@dmarc.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>, Alexander Clemm <ludwig@clemm.org>, "alberto.gonzalez@microsoft.com" <alberto.gonzalez@microsoft.com>, Warren Kumari <warren@kumari.net>, Kent Watsen <kent+ietf@watsen.net>, "draft-ietf-netconf-https-notif.authors@ietf.org" <draft-ietf-netconf-https-notif.authors@ietf.org>, NETCONF WG <netconf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: [Technical Errata Reported] RFC8639 (8073)
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/kofCj8tQsmuXdpdrjzX1dS7tEx0>
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>
I tend to agree with Qiufang and others that the errata should be rejected. The configurable-encoding identity is intentionally designed as a capability marker (mixin), not a subtype of transport. Transport identities that support configurable encodings should derive from both transport and configurable-encoding. The when condition on the encoding leaf functions correctly with this design. Appendix A demonstrates the valid case of a transport that does not support configurable encodings. Adding base transport; to configurable-encoding would change the semantics by making any identity derived from it transitively a transport, which is not the intent. Unless I hear otherwise, that is what I will do. Separately, Kent and I can decide to update the https-notif transport draft. Cheers. > On May 25, 2026, at 6:59 PM, maqiufang (A) <maqiufang1@huawei.com> wrote: > > Hi, Thomas, all, > > I agree that this errata should be rejected. > > Regarding the suggestion that: >> "base sn:configurable-encoding;" should be added to the transport protocol identities and an errata to https://datatracker.ietf.org/doc/html/rfc8639#appendix-A should be filed. > > I think the existing example in appendix-A is acceptable. The transport identity foo does not use "sn:configurable-encoding" as its base, so the when statement for the encoding leaf is false. This means that it does not support configurable encodings, i.e., it uses a default encoding for an underlying transport foo. > > In short, it is not an error if a transport does not support the configuration of encodings. That said, I fully agree that for the http-notif transport, it makes a lot of sense to support configurable encodings. > > Best Regards, > Qiufang > > -----Original Message----- > From: Thomas.Graf@swisscom.com [mailto:Thomas.Graf@swisscom.com] > Sent: Tuesday, May 26, 2026 12:37 AM > To: Roman.Janota=40cesnet.cz@dmarc.ietf.org; rfc-editor@rfc-editor.org; evoit@cisco.com; ludwig@clemm.org; alberto.gonzalez@microsoft.com; einarnn@cisco.com; ambtripa@cisco.com; warren@kumari.net; mjethanandani@gmail.com; kent+ietf@watsen.net; per.ietf@ionio.se; draft-ietf-netconf-https-notif.authors@ietf.org > Cc: netconf@ietf.org > Subject: [netconf] Re: [Technical Errata Reported] RFC8639 (8073) > > Dear Roman, Kent, Andy and Mahesh, > > Apologies. I was wrong. Andy is correct. "base sn:configurable-encoding;" should be added to the transport protocol identities and an errata to https://datatracker.ietf.org/doc/html/rfc8639#appendix-A should be filed. Errata 8073 should be rejected. > > See: https://mailarchive.ietf.org/arch/msg/netconf/BRzA6DoJKgQd1twikAalC8TNqzE/ > > Reviewing > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif#section-6.2 > identity https { > base sn:transport; > description > "HTTPS transport for notifications."; > } > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif#section-7.2 > identity udp-notif { > base sn:transport; > base sn:configurable-encoding; > description > "UDP-Notif is used as transport for notification messages > and state change notifications."; > } > > It appears that draft-ietf-netconf-https-notif is missing the update. > > Best wishes > Thomas > > -----Original Message----- > From: Graf Thomas, SCS-INI-NET-VNC-E2E > Sent: Monday, May 25, 2026 5:58 PM > To: 'Roman Janota' <Roman.Janota=40cesnet.cz@dmarc.ietf.org>; RFC Errata System <rfc-editor@rfc-editor.org>; evoit@cisco.com; ludwig@clemm.org; alberto.gonzalez@microsoft.com; einarnn@cisco.com; ambtripa@cisco.com; warren@kumari.net; mjethanandani@gmail.com; kent+ietf@watsen.net; per.ietf@ionio.se > Cc: netconf@ietf.org > Subject: RE: [netconf] Re: [Technical Errata Reported] RFC8639 (8073) > > Dear Roman, > > errata EID 8073 is valid and should be implemented accordingly. Doublechecking 4 YANG-Push implementations from https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/125/Hackathon/ietf-125-hackathon-validate-e2e-yp-message-broker.pdf, it appears that the implementors haven't following up on the errata yet. Will take it as an action item. Thanks for following up and reminding. > > Best wishes > Thomas > > -----Original Message----- > From: Roman Janota <Roman.Janota=40cesnet.cz@dmarc.ietf.org> > Sent: Monday, May 25, 2026 4:26 PM > To: RFC Errata System <rfc-editor@rfc-editor.org>; evoit@cisco.com; ludwig@clemm.org; alberto.gonzalez@microsoft.com; einarnn@cisco.com; ambtripa@cisco.com; warren@kumari.net; mjethanandani@gmail.com; kent+ietf@watsen.net; per.ietf@ionio.se > Cc: netconf@ietf.org > Subject: [netconf] Re: [Technical Errata Reported] RFC8639 (8073) > > > Be aware: This is an external email. > > > > Hi all, > > Following up on this older errata (EID 8073), we agree with the correction and have already incorporated it into our ietf-subscribed-notifications YANG module. > > Does anyone disagree with this fix? > > Regards, > > Roman Janota > > On 8/11/24 2:40 AM, RFC Errata System wrote: >> The following errata report has been submitted for RFC8639, >> "Subscription to YANG Notifications". >> >> -------------------------------------- >> You may review the report below and at: >> https://che01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >> rfc-editor.org%2Ferrata%2Feid8073&data=05%7C02%7CThomas.Graf%40swissco >> m.com%7C513312e77ce24663ec6708deba69bb94%7C364e5b87c1c7420d9beec35d19b >> 557a1%7C0%7C0%7C639153160575816994%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1 >> hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=MlMWPTVBBJ3NNz0Kz9Kwd1095DTYmkIDaT6Qy3d >> Flwg%3D&reserved=0 >> >> -------------------------------------- >> Type: Technical >> Reported by: Andy Bierman <andy@yumaworks.com> >> >> Section: 4 >> >> Original Text >> ------------- >> identity configurable-encoding { >> description >> "If a transport identity derives from this identity, it means >> that it supports configurable encodings. An example of a >> configurable encoding might be a new identity such as >> >> Corrected Text >> -------------- >> identity configurable-encoding { >> base transport; >> description >> "If a transport identity derives from this identity, it means >> that it supports configurable encodings. An example of a >> configurable encoding might be a new identity such as >> >> Notes >> ----- >> This identity is incorrectly located in the section 'identities for encodings' >> It is actually an identity for the 'transport' leaf. >> The base is missing making it incorrect (page 44) >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". (If it is spam, it >> will be removed shortly by the RFC Production Center.) Please use >> "Reply All" to discuss whether it should be verified or rejected. When >> a decision is reached, the verifying party will log in to change the >> status and edit the report, if necessary. >> >> -------------------------------------- >> RFC8639 (draft-ietf-netconf-subscribed-notifications-26) >> -------------------------------------- >> Title : Subscription to YANG Notifications >> Publication Date : September 2019 >> Author(s) : E. Voit, A. Clemm, A. Gonzalez Prieto, E. Nilsen-Nygaard, A. Tripathy >> Category : PROPOSED STANDARD >> Source : Network Configuration >> Stream : IETF >> Verifying Party : IESG >> >> _______________________________________________ >> netconf mailing list -- netconf@ietf.org To unsubscribe send an email >> to netconf-leave@ietf.org Mahesh Jethanandani mjethanandani@gmail.com
- [netconf] [Technical Errata Reported] RFC8639 (80… RFC Errata System
- [netconf] Re: [Technical Errata Reported] RFC8639… Roman Janota
- [netconf] Re: [Technical Errata Reported] RFC8639… Thomas.Graf
- [netconf] Re: [Technical Errata Reported] RFC8639… Thomas.Graf
- [netconf] Re: [Technical Errata Reported] RFC8639… maqiufang (A)
- [netconf] Re: [Technical Errata Reported] RFC8639… Mahesh Jethanandani
- [netconf] Re: [Technical Errata Reported] RFC8639… Andy Bierman
- [netconf] Re: [Technical Errata Reported] RFC8639… Thomas.Graf
- [netconf] Re: [Technical Errata Reported] RFC8639… Andy Bierman
- [netconf] Re: [Technical Errata Reported] RFC8639… Andy Bierman
- [netconf] Re: [Technical Errata Reported] RFC8639… Thomas.Graf
- [netconf] Re: [Technical Errata Reported] RFC8639… Alex Huang Feng
- [netconf] Re: [Technical Errata Reported] RFC8639… Andy Bierman
- [netconf] Re: [Technical Errata Reported] RFC8639… Kent Watsen