[netconf] Re: [Technical Errata Reported] RFC8639 (8073)

Alex Huang Feng <alex.huang-feng@insa-lyon.fr> Mon, 01 June 2026 11:13 UTC

Return-Path: <alex.huang-feng@insa-lyon.fr>
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 65950F89E1F2; Mon, 1 Jun 2026 04:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780312395; bh=gP8TbqyLynDhnwk8H2vltfminYD2S6ENeyjeuPmEPnk=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=LCU6grHN7kdGgWApTYl8UKyoPQ8JUnmRZG6qqXLREDgTS+7C2xOXvrXF+VJMLybGr TBStnGXz4crzF9QPXOv1dvb2hEVvIsEoLhxE1JKF5Ix7OXjxHt0N7UVbcE7ckSk4va gUWEkwD0zZuIKBjQzKPKwDIhPONtHHv3i4lk3Cm0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.427
X-Spam-Level:
X-Spam-Status: No, score=-0.427 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, HTML_MESSAGE=0.001, RCVD_HELO_IP_MISMATCH=2.368, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=insa-lyon.fr
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 ZQGTqm_zPg5L; Mon, 1 Jun 2026 04:13:14 -0700 (PDT)
Received: from smtpout02-ext4.partage.renater.fr (smtpout02-ext4.partage.renater.fr [194.254.241.31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BAF2AF89E1E1; Mon, 1 Jun 2026 04:13:13 -0700 (PDT)
Received: from zmtaauth02.partage.renater.fr (zmtaauth02.partage.renater.fr [194.254.241.25]) by smtpout20.partage.renater.fr (Postfix) with ESMTP id CC768BFA96; Mon, 1 Jun 2026 13:12:54 +0200 (CEST)
Received: from zmtaauth02.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTPS id B4144A0DF9; Mon, 1 Jun 2026 13:12:54 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTP id 9E9DDA0E2B; Mon, 1 Jun 2026 13:12:54 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zmtaauth02.partage.renater.fr 9E9DDA0E2B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=insa-lyon.fr; s=CB289C06-95B8-49FE-9C4B-D197C6D2E7CB; t=1780312374; bh=fp0SoqGhYSQXz+x8fwS3bw6zGDDQhKIiMazIsCTL3Zg=; h=From:Message-Id:Mime-Version:Date:To; b=ahoDCKvX3/oeOgstgdlHarane0lIoZnk9LlKYFYJTJZOo7p/jCLpbcZyhiF5Iukin AyOh40oZEjfPBAjUxSP5ZPs/AEv9ouBboEM0PlPVdwquttEFPTyXF6aEVxx/1TMt7k sPQziSCoMrvB8SJIoRfs0Uwj7BlWRFO3n7ead2E8OEPHB3MnU+KlaGQSyZoDZ67Z2Z ZxHi8dpHRLkeJREmFkascrMfOELvYKAM2lkIxPh2qGHT3kmbhoQ9yjoNOdAr0at7hL cyPVUI7tfaCrkWmsmjwsJUOoi9ZWTEROwZcFfGSLmCbU+Wu0Hs3a7M3VUmICN7oraZ zCm/1oyhpA5sQ==
Received: from zmtaauth02.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth02.partage.renater.fr [127.0.0.1]) (amavis, port 10026) with ESMTP id xvCJAgpwrwUS; Mon, 1 Jun 2026 13:12:54 +0200 (CEST)
Received: from 91.243.136.145 (unknown [194.254.241.246]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTPA id 07D9BA0DF9; Mon, 1 Jun 2026 13:12:54 +0200 (CEST)
From: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
Message-Id: <6E46E090-04B8-4A67-881C-1485810B333D@insa-lyon.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2824B2DB-F5B6-4174-BB24-71E8F71C594A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\))
Date: Mon, 01 Jun 2026 13:12:43 +0200
In-Reply-To: <CABCOCHS=mpJGU5kV_mo+vPcgGc0nh5yDkaSADx2OvA5+0EEVGQ@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.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> <CABCOCHSDz8fA5YKVrzhsxczrapeSvC6BO-1k5FDS893QPpwiwA@mail.gmail.com> <ZR1P278MB11709348B2B463803B2D0D1689082@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM> <CABCOCHS=mpJGU5kV_mo+vPcgGc0nh5yDkaSADx2OvA5+0EEVGQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3826.700.81.1.4)
X-Virus-Scanned: clamav-milter 0.103.12 at clamav03
X-Virus-Status: Clean
Message-ID-Hash: JOE6N23LV5R4WCBWHU4YHRUZTROZDXFC
X-Message-ID-Hash: JOE6N23LV5R4WCBWHU4YHRUZTROZDXFC
X-MailFrom: alex.huang-feng@insa-lyon.fr
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, maqiufang1=40huawei.com@dmarc.ietf.org, Roman.Janota=40cesnet.cz@dmarc.ietf.org, rfc-editor@rfc-editor.org, ludwig@clemm.org, alberto.gonzalez@microsoft.com, warren@kumari.net, kent+ietf@watsen.net, draft-ietf-netconf-https-notif.authors@ietf.org, 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/hQg35jHgFSUfGv_kGENODXGKjlc>
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>

Dear Andy, NETCONF,

I support implementing this proposal from Andy.
This will help authors to not make the mistake again for new transports.

Regards,
Alex

> On 27 May 2026, at 18:12, Andy Bierman <andy@yumaworks.com> wrote:
> 
> 
> 
> On Tue, May 26, 2026 at 10:15 PM <Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com>> wrote:
>> Dear Andy and Qiufang,
>> 
>>  
>> 
>> AB> Are there any examples of transport protocols suitable for YANG in which the encoding is hard-wired?
>> 
>>  
>> 
>> For dynamic subscriptions yes. For configured subscriptions the encoding the transport usually supports more than one encoding. I am not aware of any which doesn't. I think that’s one of the advantages over dynamic subscriptions.
>> 
>>  
>> 
>> QM> 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.
>> 
>>  
>> 
>> It is acceptable in terms that the example is working. But you agree with me that it didn't prevent that there are transport specifications which support configurable encoding but missing base sn:configurable-encoding.
>> 
>>  
>> 
>> Looking at
>> 
>>  
>> 
>> https://datatracker.ietf.org/doc/html/rfc8639#appendix-A
>> 
>> For more on the overall objectives behind configuring transport connectivity for a configured subscription, see  Section 2.5.7 <https://datatracker.ietf.org/doc/html/rfc8639#section-2.5.7>.
>> 
>>  
>> 
>> Reading https://datatracker.ietf.org/doc/html/rfc8639#section-2.5.7 and also reading through the rest of the document, nowhere is described how configurable-encoding is being used. I believe adding a descriptive sentence or/and adding configurable-encoding in the code example would help an implementer to understand that if multiple encodings are supported (which is the normal case) configurable-encoding identity should be used.
>> 
>>  
>> 
>> Or in other words, the example or section 2.5.7 is not wrong, but it misses configurable-encoding option.
>> 
>>  
>> 
>> Would you agree it would help if added?
>> 
> 
> 
> How about:
> 
> Appendix A:
> 
> OLD:
>      identity foo {
>        base sn:transport;
>        description
>          "Transport type 'foo' is available for use as a configured
>           subscription's transport protocol for subscribed
>           notifications.";
>      }
> 
> NEW:
>      identity foo {
>        base sn:transport;
>        base sn:configurable-encoding;
>        description
>          "Transport type 'foo' is available for use as a configured
>           subscription's transport protocol for subscribed
>           notifications. Configurable encoding is supported.";
>      }
> 
>  
>>  
>> 
>> Best wishes
>> 
>> Thoma
>> 
> 
> 
> Andy
>  
>>  
>> 
>> From: Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>>
>> Sent: Tuesday, May 26, 2026 5:03 PM
>> To: maqiufang (A) <maqiufang1=40huawei.com@dmarc.ietf.org <mailto:40huawei.com@dmarc.ietf.org>>
>> Cc: Graf Thomas, SCS-INI-NET-VNC-E2E <Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com>>; Roman.Janota=40cesnet.cz@dmarc.ietf.org <mailto:40cesnet.cz@dmarc.ietf.org>; rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>; evoit@cisco.com <mailto:evoit@cisco.com>; ludwig@clemm.org <mailto:ludwig@clemm.org>; alberto.gonzalez@microsoft.com <mailto:alberto.gonzalez@microsoft.com>; einarnn@cisco.com <mailto:einarnn@cisco.com>; ambtripa@cisco.com <mailto:ambtripa@cisco.com>; warren@kumari.net <mailto:warren@kumari.net>; mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>; kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>; per.ietf@ionio.se <mailto:per.ietf@ionio.se>; draft-ietf-netconf-https-notif.authors@ietf.org <mailto:draft-ietf-netconf-https-notif.authors@ietf.org>; netconf@ietf.org <mailto:netconf@ietf.org>
>> Subject: Re: [netconf] Re: [Technical Errata Reported] RFC8639 (8073)
>> 
>>  
>> 
>> Be aware: This is an external email.
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> On Mon, May 25, 2026 at 7:00 PM maqiufang (A) <maqiufang1=40huawei.com@dmarc.ietf.org <mailto:40huawei.com@dmarc.ietf.org>> 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 tohttps://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.
>> 
>>  
>> 
>> I agree with Thomas.
>> 
>> This is built into the YANG module, not server implementation capabilities.
>> 
>> Are there any examples of transport protocols suitable for YANG in which the encoding is hard-wired?
>> 
>> The when-stmt=false implies that the concept of 'encoding' does not even exist for this transport.
>> 
>> It cannot be configured or reported with <get-data>. 
>> 
>>  
>> 
>> It was not intuitive at all that the udp-notif identity needed an extra base added so a different leaf could be used.
>> 
>>  
>> 
>> Best Regards,
>> Qiufang
>> 
>>  
>> 
>> Andy
>> 
>>  
>> 
>> -----Original Message-----
>> From: Thomas.Graf@swisscom.com <mailto:Thomas.Graf@swisscom.com> [mailto: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 <mailto:40cesnet.cz@dmarc.ietf.org>; rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>; evoit@cisco.com <mailto:evoit@cisco.com>; ludwig@clemm.org <mailto:ludwig@clemm.org>; alberto.gonzalez@microsoft.com <mailto:alberto.gonzalez@microsoft.com>; einarnn@cisco.com <mailto:einarnn@cisco.com>; ambtripa@cisco.com <mailto:ambtripa@cisco.com>; warren@kumari.net <mailto:warren@kumari.net>; mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>; kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>; per.ietf@ionio.se <mailto:per.ietf@ionio.se>; draft-ietf-netconf-https-notif.authors@ietf.org <mailto:draft-ietf-netconf-https-notif.authors@ietf.org>
>> Cc: netconf@ietf.org <mailto: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 tohttps://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 <mailto:40cesnet.cz@dmarc.ietf.org>>; RFC Errata System <rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>>; evoit@cisco.com <mailto:evoit@cisco.com>; ludwig@clemm.org <mailto:ludwig@clemm.org>; alberto.gonzalez@microsoft.com <mailto:alberto.gonzalez@microsoft.com>; einarnn@cisco.com <mailto:einarnn@cisco.com>; ambtripa@cisco.com <mailto:ambtripa@cisco.com>; warren@kumari.net <mailto:warren@kumari.net>; mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>; kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>; per.ietf@ionio.se <mailto:per.ietf@ionio.se>
>> Cc: netconf@ietf.org <mailto: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 <mailto:40cesnet.cz@dmarc.ietf.org>>
>> Sent: Monday, May 25, 2026 4:26 PM
>> To: RFC Errata System <rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>>; evoit@cisco.com <mailto:evoit@cisco.com>; ludwig@clemm.org <mailto:ludwig@clemm.org>; alberto.gonzalez@microsoft.com <mailto:alberto.gonzalez@microsoft.com>; einarnn@cisco.com <mailto:einarnn@cisco.com>; ambtripa@cisco.com <mailto:ambtripa@cisco.com>; warren@kumari.net <mailto:warren@kumari.net>; mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>; kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>; per.ietf@ionio.se <mailto:per.ietf@ionio.se>
>> Cc: netconf@ietf.org <mailto: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 <https://www/>.
>> > rfc-editor.org <http://rfc-editor.org/>%2Ferrata%2Feid8073&data=05%7C02%7CThomas.Graf%40swissco
>> > m.com <http://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 <mailto: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 <mailto:netconf@ietf.org> To unsubscribe send an email
>> > to netconf-leave@ietf.org <mailto:netconf-leave@ietf.org>
>> 
>> _______________________________________________
>> netconf mailing list -- netconf@ietf.org <mailto:netconf@ietf.org>
>> To unsubscribe send an email to netconf-leave@ietf.org <mailto:netconf-leave@ietf.org>_______________________________________________
> netconf mailing list -- netconf@ietf.org
> To unsubscribe send an email to netconf-leave@ietf.org