IETF Logo Mail Archive

[netconf] Re: WGLC for udp-client-server

Benoit Claise <benoit.claise@huawei.com> Wed, 12 February 2025 08:49 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 10951C1D52E1 for <netconf@ietfa.amsl.com>; Wed, 12 Feb 2025 00:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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_BLOCKED=0.001, 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 jg_oIvmQvw_e for <netconf@ietfa.amsl.com>; Wed, 12 Feb 2025 00:49:12 -0800 (PST)
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 B6ACDC1D3DEB for <netconf@ietf.org>; Wed, 12 Feb 2025 00:49:12 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4YtBjt3WSGz6L5YH; Wed, 12 Feb 2025 16:46:10 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id EEEE5140CF4; Wed, 12 Feb 2025 16:49:09 +0800 (CST)
Received: from [10.48.153.78] (10.48.153.78) 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; Wed, 12 Feb 2025 09:49:07 +0100
Message-ID: <d37c7ced-1d11-4a66-b4a5-58b66eabfe5c@huawei.com>
Date: Wed, 12 Feb 2025 09:49:02 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Thomas.Graf@swisscom.com, per.ietf@ionio.se, netconf@ietf.org
References: <CACvbXWHPpF8KxOmScJNTeo5ghOCDiLWKyKCKLSM+DBeaeS7T=Q@mail.gmail.com> <ZR1P278MB11702D20500AB9B64D6DA51789FC2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
Content-Language: en-US
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <ZR1P278MB11702D20500AB9B64D6DA51789FC2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.48.153.78]
X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To frapeml500001.china.huawei.com (7.182.85.94)
Message-ID-Hash: M57LMND2XA7TIYIRI3POGHPDMJUNZYKG
X-Message-ID-Hash: M57LMND2XA7TIYIRI3POGHPDMJUNZYKG
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: WGLC for udp-client-server
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/CNfSZmhCkNiVbHQIEB3aU7b8gJk>
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 all,

I believe that this document is ready.


There is no reference to NMDA compliance in this doc., which is typical 
statement for YANG modules.
I don't know whether this is (still) imposed by the YANG doctors and AD.
Now, this document only contains grouping, so it's a special one.
I took a recent example "YANG Groupings for TCP Clients and TCP 
servers". 
https://www.rfc-editor.org/rfc/rfc9643.html#name-adherence-to-the-nmda
Consistency might be a plus.

Regards, Benoit


On 2/12/2025 7:17 AM, Thomas.Graf@swisscom.com wrote:
> Dear NETCONF wg and udp-client-server authors,
>
> Thanks a lot. I reviewed the document and have not found anything to comment on.
>
> The document is in perfect shape ready to move forward to IESG.
>
> I volunteer to do the document shepherding.
>
> Best wishes
> Thomas
>
> -----Original Message-----
> From: Per Andersson <per.ietf@ionio.se>
> Sent: Thursday, February 6, 2025 4:39 PM
> To: netconf@ietf.org
> Subject: [netconf] WGLC for udp-client-server
>
>
> Be aware: This is an external email.
>
>
>
> Hi!
>
> This email begins a two-week WGLC on:
>
> YANG Groupings for UDP Clients and UDP Servers
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-client-server-05
>
> Please take time to review this draft and post comments by February 20. Favorable comments are especially welcomed.
>
> None of the authors or contributors have declared IPR:
>
> https://mailarchive.ietf.org/arch/msg/netconf/NncA8JHqZH14wCptMhktgGcngyM/
>
>
> --
> Per, co-chair
>
> _______________________________________________
> netconf mailing list -- netconf@ietf.org To unsubscribe send an email to netconf-leave@ietf.org
>
> _______________________________________________
> netconf mailing list -- netconf@ietf.org
> To unsubscribe send an email to netconf-leave@ietf.org

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