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

Thomas.Graf@swisscom.com Thu, 28 May 2026 04:18 UTC

Return-Path: <Thomas.Graf@swisscom.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 2FCF0F66BCF5; Wed, 27 May 2026 21:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779941886; bh=jbGGtCxnFjkmRe79O8IhnGLQqcwiCKOU7LbCi/yp+Es=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=EaOoF24h2ji8T1LvFGtZ2gBCw41fd9x+R/V7rbnaycZzWt56+WoQjCshlX9K1lgDE pwuU5AXXTs+FsHrhaxQIH99FYaa+KMmvkZOp/I7BlTWfPKyMAu7kwmnxtEaYm+GYKA DJpyA24rO3Gb2hBOgSBwuVrRJ4ExZ7e52HF8Ck20=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=swisscom.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 CY7GqAbP_nCo; Wed, 27 May 2026 21:18:05 -0700 (PDT)
Received: from mail.swisscom.com (mailout110.swisscom.com [138.188.166.110]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E1569F66BCE5; Wed, 27 May 2026 21:18:04 -0700 (PDT)
Received: by mail.swisscom.com; Thu, 28 May 2026 06:17:52 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=swisscom.com; s=iscm; t=1779941873; bh=Z+WfInyb9qDZInW7fix3xmRnpzmfzXI/EEas/cwQcEY=; h=MIME-Version:Content-Type:From:To:CC:Subject:Date:Message-ID: References:In-Reply-To; b=b4xTE+VuarkSobjC70h9ZF67uxUQ0FOv2dRc3SP1/8QLOIOvTRyG6k7+lylggSPBO zl5mKng7bh0pO3dDPE8xRk7hkbJUkFkmFzgDWVaAqUttc03VMXYSEAVIaooxAod+Rg yF0FEQE0Nss7NXmpvHXP9PMtg1LvJVXKUUzwSA5n4YKyc/VPNbqs+rBSMBocgjf3ZW q+ojmJ3OE4wpSWdMmtxmzMTXHQ9YhJyVuR5BjmFYAyWkF64Cd58DNdFEeqvv9iZZ19 ryZq7898Rc4wsGlz7fBHe/5KaB+PIowYkyPsIvAkHrpHov2c2UH6RKpA9J5LRaRWSQ TqK/FwwVwv1Tw==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_754490_1076064208.1779941872046"
X-Mailer: Totemo_TrustMail_(Notification)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=x/s8M6U1vALx1Y3QRn4vDAtJAP9cuNGy2Q6fimB63R4xktbCwSzsPXgAD/YzMLgy0Djd0rzaYF38p9Tf5xB+N8uC9HwQz1YWu1ssKl1zkvfpQlLgOlrRXBm/QOmke99wGAyIOuA/7xw87ZH01UO3cQSXVqxws8xQZCyxZVSDFdaRn2XdiiFTsZ+d35p0whSHFzxG86R5Ow6uh1d34kzlhtZKHJ9lmhJypVGWUlExJC7i6tNITqXLx6c0/5/sQxswcdyrEpaN2SAzjb8+7PG8OZIObmGA98RR0ans4dtb5AFySANtKGale1ig5ITe+St/eoHFq5XVycBNjjNzCxk25g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=d1LTU7qKhhukKH8KpsuTQt21UNdwA9Repddg8GgFY1M=; b=vKzUQxZFkl4NX3ge4G9JUr5jVusRE1VgZkdRKccFBjr04FiaCCY7ierE3IPT21RtTyfJj9ufup2aYujdzeGOhDv54WwNBaFSnIwiuskeyvUfZ7G4D4Zqx6DxT7uuegVc57PJKFZN4WR42M/jzd+ntJ2LG6OuhypAVqm0I2EhDdxyG4hUMHkL96+OwDi23H5OrFtTSLyVJjeccCCDYkemaSDODhBVg5q+fBEkto+B3CorY3O+IY98CBAtQ+iIfwG+JiIvT6QeSof5mVwTi9dn2vwyV15eK1Z5fp+kb4D24THMMLnjjB7EKddEUhpPA6uHBiSaum+jwYF8EYzeQ5DJOw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=swisscom.com; dmarc=pass action=none header.from=swisscom.com; dkim=pass header.d=swisscom.com; arc=none
From: Thomas.Graf@swisscom.com
To: andy@yumaworks.com
Thread-Topic: [netconf] Re: [Technical Errata Reported] RFC8639 (8073)
Thread-Index: AQHc7FKiCwOZh0Nr+Um5oowLWgX0rrYe4syAgAALRtCAAJ/ugIAA2sCAgADmf3CAAL9OAIAAykwg
Date: Thu, 28 May 2026 04:17:46 +0000
Message-ID: <ZR1P278MB11705A271127E199C96D0E0B89092@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.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>
In-Reply-To: <CABCOCHS=mpJGU5kV_mo+vPcgGc0nh5yDkaSADx2OvA5+0EEVGQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=b4354c4d-3b5b-4812-9b2c-79188348a5f2;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ContentBits=0;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Enabled=true;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Method=Standard;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Name=C2 Internal;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SetDate=2026-05-28T04:16:24Z;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_Tag=10, 3, 0, 1;
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=swisscom.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: ZR1P278MB1170:EE_|ZR4P278MB1786:EE_
x-ms-office365-filtering-correlation-id: 08bb8602-544d-4359-e823-08debc701242
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|4022899009|376014|366016|1800799024|7416014|13003099007|8096899003|38070700021|6133799003|3023799007|4133799003|18002099003|22082099003|56012099006|4143699003|11063799006;
x-microsoft-antispam-message-info: BoBq6kOgP1dKW3rd7lDFroU6absi0VJkaU17gQb1WOjnWTBCqfI36smRh51c0aFxZN+VRRrWW9IMEObaMud7fNt3vODRxOjf3gQZg19iEFypfK8f86d3WMjRvTkrcpdexSIx5tNH6oaXh5UVYvnSR7mAHvQTJ60f2xlBvfbjbhiETEIS7l3b/8WbSWFgS9/CJ5l+4P+uJkz9Ld+ZVAusbbq4P+g8G5gEPI7kH7f4aPMyyxanh7iur5G2kpu3ga13rNnjjr+fkmnSwcvXwZkIZygCwRn75CFTevelKZmbGlj/+nZFOT7PE0wSs/Ot75KBFEaJHDSOPc5z5SlOkasIvaQezaDO6WZHxLDpubflkbAni15r5Q0Mosm4sxzp1YrOwUWv0cktgyNXafi0+TKvNQgAOBGMwqH67AF3QPoFnUXak68GsLFX1YGiFhRLH1kUSWLI0heqTbWL8zRGtIhwoLQtIl331pCjXO+twSQSf6qedpt2UFwZr1fbgxGqvM4CJW6hLtssSeJpbTwb6+kEfOMrNwpiee7FMJUoWEpo/XCqsRG6N1WEKkmDQzmUXiUXFXCVQ6C7QVamG2dDbmmz6RbBTez5fGr5tJRp8rSDxbKFVxjTuwQzqfnUMqTRu0cCpo0TRG1jBaIbiRaWlCD36xBmIG7fy+Dye/1ikbG6qc7Q0kl33Y8nF1QWwmqki/4+
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(4022899009)(376014)(366016)(1800799024)(7416014)(13003099007)(8096899003)(38070700021)(6133799003)(3023799007)(4133799003)(18002099003)(22082099003)(56012099006)(4143699003)(11063799006);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: QPT73pBujDODS7PYpqBiIw5T+BJZ5gdSIz2wu2txDaeukxQkLjlZqoOE1iAHKyWSQA+wDDDeZlmPcAktR7OelSbIaw6phkxwtvd/2GtKogWZvrWW2bkuxLDHYeXiCpV20Qq35ebBHfmgFR8syaMfVxXzGLEMZOeIojNBzceDmUFGu7jArg0sQcZYIWiMN06jP5Gdq5P3k87BSYlaQKFiXRd3rzkDHcfzXkBRcwXLlaApp7t5kkQxtccdgS3KPNxZiojh5jL3UTdqGyBAqFso1Yo+Yf2wcNGYRauwqNpkutYs05B3N7lAXvl29bSJKcUCST0PpFyRNuUBrZosUvWnJhdETXHD8ieLAkLSCLn+u+uNbwdgZqughs8U03An0DTUaBvDTTFa6bZxiHv3qTupnFrcbwz6U7Hu+19/IzCm7B8PRkFhePB0BrEukEBFDrvCQlC3x2GdPEJ46s9GG+lwcvoYLcXX2S0gZhV/7whATOFxX42RAm6P9aS7HRsxddnVyiKQV1enLU9bcZP8esRwvxyrdTH48lQPtcBo+a2PJO3Wen4FO95khbX5gxvIWcs8fg0LLZTkU3fsa63JnZDQfI2rwfbd1+Sfqzm2mNDnYJOI8zm3Hx0QLxNFrE1wtv8/I6SLzPKqIPV3lkeW11wkIttAK4GpCfDGODjuACq+eaKqp1sQ83cEO1pwRRlwp+m9PjPsYsmhYsIQs8AxtiyI6KDnEvCbYL7+RNkutJODmXBrlU8e3PE3+WTzif7qdAHb+8V0rE0J+rLMnBhLx+8Cnjx1PgENn+dGEWf02lN3EEPcMefd5nLkXhwFt8t+Pe6O/Q2GvVx6pfybPpvm270/sjw59AWP/iMWTDJAu0qQWZuiotrADUag3FGv6oqoYadRznOT0GPX6rrxV09L0jryuzGknfzXtUm02CH1TvuXjzvqabA2OkRDV+UiX4nsrlOSZKPqruhsdkufgrCIDJ6ZK4417zUDy6Zlxkq6zhHpRyVtkjdF0BIFzyQTOGHoiywiMDi22V2boAiIynicsonJlPlDoMD6zl/v30A7SvhPVHBwMKggBkOU4sgK0rGChlrZZgaDUm//akqbMB3ZuBzXKy3nJs+Hg9AgZheR84KXS89sTv88FYuNfFnBCs0JVs9jlKkvlbcbS2R86N91JUbDtwhyOJTlQsxJfHjKC6AEWiyB3ICELDUnOkM/Dm3BKdmCjnc6RdMKbO1Z5ItEN11j0UxExjo5cP35LxBy7z7stQbguURTTspqBY2p3KQaMTNweBr9G2HNiLv0eg/MMUJAjrxb34r1/kZ/fBb/oqqWR+s7bzMBVi5ricJZycUskSbnAblwloAAHqQcMoGbCPlL0aOB29XQhFhICefvfTiMNG0xRAJLdNLCD7cq5QpXLvK/HKtDUSSq56vvpITszErhK1T8NvGdYEoZ4CeyHzc5Lz2sQ6OopkWxNTbRdT7XwY3otz/vu0jyVf1kCJW23a6etnF5AXOrRGnALIS9FywalcBwEVM2fq4sAPWkcb6oEP0brqWm6FuaAJvBU7Zehu1uH4ZKWRPNF4FqI8lXOc/VIU1+IWKouMIGj8SpL5xJI07BPJKaYFtKi2R8CqLjZINAKCVaYccHyv3c+NGeLMqRggvMaRwevKjdJ5ejPNs1h4a/hE/hSFC68pfwxnhKk2v5JUBceNWoqT8CESC4H3Cf7aH3yYYY5mzKYfxa534ZeX3u6DkfvfN9csIBFZjUkNTMbQ==
X-Exchange-RoutingPolicyChecked: J988VY9E1wi5iHUIbki9Csdt1YiEdRuvPGdTDkucuRUdMXPNdzrt16jaJaK+C+sq65KzCDdto4Al+uPAgIsWoXgaTMCiUeMzn4WbCVKnvTgIS8ts9oXBD64XZoZwiIdLahaAU1ClNkWlBIWRwNBJ10Zjo9HBJvx0kp3BTiDeZxBJD8bLu/Joini90nGuWzhkecSK4oBKiZ5DxF0JdATwx0w40b5vS5wZvquZ6iEbSjW7JRl2OJNFHShKgzE6JM000rJ4ddI/9LsVQTJ7jFnK6ESv1OcilkdbZuT9zquogIixs7+MHa24jBqHm9qtkAScjNdTdEcTiiVd1w3EnQNNHA==
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 08bb8602-544d-4359-e823-08debc701242
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2026 04:17:46.1800 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 364e5b87-c1c7-420d-9bee-c35d19b557a1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: wfzCVeqOsjvF3FHjdHvSi3f7Q7yJtuzBcgPukIYIoowOe7sFUWXvQOVyweCSxuxdyx2OHq7KkCyDh4+Jg8ZmSRnbJIp7KC/xs+7HBt1B4U8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ZR4P278MB1786
X-OriginatorOrg: swisscom.com
X-CFilter-Loop: Reflected
X-Trustmail: processed
Message-ID-Hash: QNFEM2FGDRKPSLTSATXSQT6FFOQIRWSP
X-Message-ID-Hash: QNFEM2FGDRKPSLTSATXSQT6FFOQIRWSP
X-MailFrom: Thomas.Graf@swisscom.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: 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/i4ecnxUEHVjPoSgPbsx2r5NuMsI>
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,

Exactly. Thats what I had in mind. Probably is the most easiest fix. Since it is an example, the change is not normative and can be done in an errata.

Best wishes
Thomas

From: Andy Bierman <andy@yumaworks.com>
Sent: Wednesday, May 27, 2026 6:12 PM
To: Graf Thomas, SCS-INI-NET-VNC-E2E <Thomas.Graf@swisscom.com>
Cc: maqiufang1=40huawei.com@dmarc.ietf.org; 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; netconf@ietf.org
Subject: Re: [netconf] Re: [Technical Errata Reported] RFC8639 (8073)

Be aware: This is an external email.



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 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.

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 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<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>