IETF Logo Mail Archive

[netconf] Re: Adoption call for notif-yang-04

Thomas.Graf@swisscom.com Sun, 19 May 2024 09:46 UTC

Return-Path: <Thomas.Graf@swisscom.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47130C14F6A7 for <netconf@ietfa.amsl.com>; Sun, 19 May 2024 02:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=swisscom.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQ6Lhmg6f5dd for <netconf@ietfa.amsl.com>; Sun, 19 May 2024 02:46:31 -0700 (PDT)
Received: from mail.swisscom.com (mailout120.swisscom.com [138.188.166.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8DC7C14F5E5 for <netconf@ietf.org>; Sun, 19 May 2024 02:46:29 -0700 (PDT)
Received: by mail.swisscom.com; Sun, 19 May 2024 11:46:16 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=swisscom.com; s=iscm; t=1716111977; bh=w/3W7/5kZXkhxMmt+wPahADmJRymjZlR7Xijpzzrd1A=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=EdQvIDs3BS2rvZjAm6itWOQWFYiD0MLeolYPy0Vslfqq5D6CmUWvP/UYvrpAFdOgD sf8B1BJSNe4YGBGsuoV1ckuIrC01dNBlhGJDkChbSZjL+EL0GpxZZEI9ZQzkc4zuRi ME0UM4veEv6BElU9igpyXi3RI06nNYmLfFjUE6Qp4fuSFFGcusp+nYd6nZST+c5Am+ cjVlo9ZDZajveOmnVAhzFFrA/zR2MIzkVkUJxrJLDqKy9/eDn/mAUQDmeZHCLSY5B2 qtlU740hMHysostqpkLw0g1UoEZMizGb2fOLlPEf10bRxLomA4W+R/N2ppcn9Spjc+ rBqQ+sm4/JZXA==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_245521_543301631.1716111976399"
X-Mailer: Totemo_TrustMail_(Notification)
From: Thomas.Graf@swisscom.com
To: kent+ietf@watsen.net, andy@yumaworks.com
Thread-Topic: [netconf] Adoption call for notif-yang-04
Thread-Index: AQHaiG/R3p/msZJOZkmEIn20P4DSh7Ft+tQAgABYjICABlPSgIABLAKAgBrkXpCAABk3AIAAUlsAgA1knNA=
Date: Sun, 19 May 2024 09:46:13 +0000
Message-ID: <0e02c89bdb8d445db0a3f83b30b01887@swisscom.com>
References: <0100018eb57a21d8-26b38f41-a625-4d44-9248-09b349fd4212-000000@email.amazonses.com> <DU2PR02MB10160110D4C72D682BA884802880E2@DU2PR02MB10160.eurprd02.prod.outlook.com> <CABCOCHT4Yy8gUKxmR9__ZcAEULiK8g-S7-B6EaLO8s0nk0FjTg@mail.gmail.com> <0100018f07521d0a-17e021b3-295a-4c50-8316-58632d7a7107-000000@email.amazonses.com> <CACvbXWGS_Er8bK0u4suNs0oHD7B6avObk8uu6bET_-7xWHcdbQ@mail.gmail.com> <355358f23f374b8dba8a20c00fea03f4@swisscom.com> <CABCOCHRVEQBocBAspUHJFE0vp8AkO1KCimPdUV9+H0kpg1TgYA@mail.gmail.com> <0100018f64a85d1c-f98eabaf-771e-473d-a1c3-40b8f9b51dc4-000000@email.amazonses.com>
In-Reply-To: <0100018f64a85d1c-f98eabaf-771e-473d-a1c3-40b8f9b51dc4-000000@email.amazonses.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_ActionId=43b248d3-dc92-4a54-97d7-22278ea9398c;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=2024-05-19T09:09:54Z;MSIP_Label_2e1fccfb-80ca-4fe1-a574-1516544edb53_SiteId=364e5b87-c1c7-420d-9bee-c35d19b557a1;
x-originating-ip: [138.188.161.184]
X-CFilter-Loop: Reflected
X-Trustmail: processed
Message-ID-Hash: FDAYAMKLA4WJZSXE4GPJHI5DCBDMD2NV
X-Message-ID-Hash: FDAYAMKLA4WJZSXE4GPJHI5DCBDMD2NV
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: netconf@ietf.org, pierre.francois@insa-lyon.fr
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Adoption call for notif-yang-04
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/cbuU4iG910_-DqGMPz6eYOMESts>
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 Kent,


  *   Code I’ve written in the past manually-validates the envelope and then, separately, validates the payload via the YANG “notification” definition.

I would phrase "manually-validates" differently. I think you have excluded from validation because it can't be validated. That’s what we have seen during IETF 117 hackathon when using yanglint.

To my best knowledge there is no IETF document where this is written. Correct?

I find reading that YANG-Push is based on notifications in https://datatracker.ietf.org/doc/html/rfc8639#section-1.4 and notifications can be encoded in JSON according to https://www.rfc-editor.org/rfc/rfc7951#section-1 for an implementer rather misleading. Would you agree?

Best wishes
Thomas

From: Kent Watsen <kent+ietf@watsen.net>
Sent: Saturday, May 11, 2024 12:38 AM
To: Andy Bierman <andy@yumaworks.com>
Cc: Graf Thomas, INI-NET-VNC-HCS <Thomas.Graf@swisscom.com>; Per Andersson <per.ietf@ionio.se>; BOUCADAIR Mohamed IMT/OLN <mohamed.boucadair@orange.com>; netconf@ietf.org; Alex Huang Feng <alex.huang-feng@insa-lyon.fr>; Benoit Claise <benoit.claise@huawei.com>; pierre.francois@insa-lyon.fr
Subject: Re: [netconf] Adoption call for notif-yang-04


Be aware: This is an external email.





On May 10, 2024, at 1:43 PM, Andy Bierman <andy@yumaworks.com<mailto:andy@yumaworks.com>> wrote:

It is quite rigid and XML-specific:

   <notification>
       <eventTime>...</eventTime>
       < **event element**  />
   </notification>

<snip/>
YANG is incapable of representing this XSD correctly (no SubstitutionGroup).

True, not even an “anydata” helps.  If the goal is to be able to validate the entire “notification” message, I don’t see how that’s possible.

Code I’ve written in the past manually-validates the envelope and then, separately, validates the payload via the YANG “notification” definition.

K.

v2.39.1 | Report a Bug | By Email | System Status