IETF Logo Mail Archive

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

Benoit Claise <benoit.claise@huawei.com> Fri, 14 June 2024 09:26 UTC

Return-Path: <benoit.claise@huawei.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 AF711C14F6A7 for <netconf@ietfa.amsl.com>; Fri, 14 Jun 2024 02:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.425
X-Spam-Level:
X-Spam-Status: No, score=-7.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.521, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 BFqzm73WhCu9 for <netconf@ietfa.amsl.com>; Fri, 14 Jun 2024 02:26:53 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 305CCC14F681 for <netconf@ietf.org>; Fri, 14 Jun 2024 02:26:53 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4W0v1V26jvz6JB7j; Fri, 14 Jun 2024 17:22:06 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id B902714065C; Fri, 14 Jun 2024 17:26:49 +0800 (CST)
Received: from [10.81.84.182] (10.81.84.182) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 14 Jun 2024 11:26:47 +0200
Content-Type: multipart/alternative; boundary="------------hV2XjGp2oZEKgQyPmPRFSa3F"
Message-ID: <37ceeab1-c4ef-582b-571c-48959bbfb8c5@huawei.com>
Date: Fri, 14 Jun 2024 17:26:43 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Kent Watsen <kent+ietf@watsen.net>, Thomas.Graf@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> <0e02c89bdb8d445db0a3f83b30b01887@swisscom.com> <0100019012301ba8-cbf266f3-b215-4454-879e-193606dfd926-000000@email.amazonses.com>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <0100019012301ba8-cbf266f3-b215-4454-879e-193606dfd926-000000@email.amazonses.com>
X-Originating-IP: [10.81.84.182]
X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To frapeml500001.china.huawei.com (7.182.85.94)
Message-ID-Hash: 7LPIGJQ7PXJ2JYSFSSY6KGUNMZFF275H
X-Message-ID-Hash: 7LPIGJQ7PXJ2JYSFSSY6KGUNMZFF275H
X-MailFrom: benoit.claise@huawei.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" <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/fmo-_x_MJ8VJNdu_2DTYlJCG318>
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 Kent,

On 6/13/2024 11:21 PM, Kent Watsen wrote:
> Hi Thomas,
>
>> On May 19, 2024, at 5:46 AM, Thomas.Graf@swisscom.com wrote:
>>
>> Dear Kent,
>>
>> ...
>
>> To my best knowledge there is no IETF document where this is written. 
>> Correct?
>>
>
> This is possibly true.  I know that there has been discussion, with 
> regards to “anydata” statements, that the schema could be conveyed out 
> of band, which seems similar...
>
>
>> I find reading that YANG-Push is based on notifications in 
>> https://datatracker.ietf.org/doc/html/rfc8639#section-1.4and 
>> notifications can be encoded in JSON according to 
>> https://www.rfc-editor.org/rfc/rfc7951#section-1for an implementer 
>> rather misleading. Would you agree?
>>
>
> I don’t understand.  Can you say some more?  Also, what remediation do 
> you have in mind?
>
> Kent

With all respect, I find the timing of this reply disconcerting.
May 19th: Thomas asked you two key clarifying questions regarding the 
problem at stake
June 13th: you answered with "possibly true" and "I don't understand"... 
which begs for more discussion
June 13th: as WG chair, the call for adoption is unsuccessful

Maybe it doesn't matter in the end, as we should do a better job of 
explaining the problem statement...

Regards, Benoit

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