IETF Logo Mail Archive

Re: [netconf] draft-ietf-netconf-distributed-notif-07, draft-ietf-netconf-udp-notif-10

Mahesh Jethanandani <mjethanandani@gmail.com> Sun, 23 July 2023 22:54 UTC

Return-Path: <mjethanandani@gmail.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 4FBEBC151075 for <netconf@ietfa.amsl.com>; Sun, 23 Jul 2023 15:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level:
X-Spam-Status: No, score=-6.203 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 tXNJhP7w2kAk for <netconf@ietfa.amsl.com>; Sun, 23 Jul 2023 15:54:10 -0700 (PDT)
Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A47DC14EB1E for <netconf@ietf.org>; Sun, 23 Jul 2023 15:54:10 -0700 (PDT)
Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-1bb575a6ed3so599207fac.2 for <netconf@ietf.org>; Sun, 23 Jul 2023 15:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690152849; x=1690757649; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=GK+wbgWR8i/IESPmBj9y2WlawfDckYhm8K1Doou3aUI=; b=bYWWNNDIvj+asZs5/bNYxMG0K6M82tVvMlEr/fzsH6jxeBhxEHPChvfOt9chEtJ6U3 Lf7gdnLgK2G2kErB6AbF+Iy+7rLvyiQPLQgmW2xqPghm3tacv61RzUCTjjFoItWfTTL3 1CWv4yLhC/HQSm4/oiKYax1D79XdeBdNyn7pn40mpoEbVun/z5vK2y9JnHzR4j3AJXtN rwKudTq/2/gx20C5rMIvdfPQBXzkd+QIo/VpjCR7H/ZapY2Qko76rkt4eGvs0Xp419Em 7sLMaY6udd253yXzJLfgKdwl5U0QXMebjMVm3ptPwQUppSRzZF/LqznWAasrjqQeBank 5FvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690152849; x=1690757649; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=GK+wbgWR8i/IESPmBj9y2WlawfDckYhm8K1Doou3aUI=; b=Ev6Q8U25/PyfWrGQsjUrfvc+xopvGFX6WU5HyZ4w9+KwPGW3eRkYA3naRFMGVzqTyM +3QlNXnDIY0LXi2fkSsTve5xY+28i1lTDi7e95pfCjk34nIJp35fM/KdqcNsjC5GCYyM 49Uz5GOfq365WeKiC3UKOVLzKhk1ztduTozIZTJltZsRBhqIvR7nQ5xIbnUxtdZuN1nu GxFAkzVOwMpAljsP2/MlTJnkfs50pwEeFARvgZsB7f1QphAfe1+cKQERlnBK37mtxP5P Hrbx7MT/D5D/hoz71oc8lQQ2+phQPnW0mRJ3Vnqdso2xHPouG72LYe1Yo1Pv+ozEvR7p iTyA==
X-Gm-Message-State: ABy/qLY5UwA9vn4OoQVoeKDYES+YM6XWcaIQHl+bDo1Kmi29fyoa2Mwm aBgimnMFLtt4voDuBASngWBbO+p3XdM=
X-Google-Smtp-Source: APBJJlECmXA9iIAjAbvwCTCpT6FyzYGAQnWYXiW8azMuh+iSjMe5YBNAwSibtc3rvuBZlFm034NK2w==
X-Received: by 2002:a05:6870:d7a1:b0:1b3:b6c7:ab1a with SMTP id bd33-20020a056870d7a100b001b3b6c7ab1amr7002402oab.28.1690152849171; Sun, 23 Jul 2023 15:54:09 -0700 (PDT)
Received: from smtpclient.apple (dhcp-949b.meeting.ietf.org. [31.133.148.155]) by smtp.gmail.com with ESMTPSA id o11-20020a63a80b000000b005633778becasm6805854pgf.41.2023.07.23.15.54.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 23 Jul 2023 15:54:08 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-86719B01-26FE-4B29-916B-5D2A02977A08"
Content-Transfer-Encoding: 7bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 23 Jul 2023 15:53:57 -0700
Message-Id: <8E72430A-41E9-437F-B444-F7B0D83C41B6@gmail.com>
References: <41E432C7-7137-4553-ADA5-E5EB2263F897@insa-lyon.fr>
Cc: Thomas Graf <Thomas.Graf@swisscom.com>, netconf <netconf@ietf.org>, Paolo Lucente <paolo@pmacct.net>, Pierre Francois <pierre.francois@insa-lyon.fr>
In-Reply-To: <41E432C7-7137-4553-ADA5-E5EB2263F897@insa-lyon.fr>
To: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
X-Mailer: iPhone Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/aObf57rMHxBh6JJ66pqBNVxMwP0>
Subject: Re: [netconf] draft-ietf-netconf-distributed-notif-07, draft-ietf-netconf-udp-notif-10
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jul 2023 22:54:12 -0000

See inline. Speaking as a contributor. 

On Jul 23, 2023, at 1:54 PM, Alex Huang Feng <alex.huang-feng@insa-lyon.fr> wrote:

Hi Mahesh,

Please see inline,

On 23 Jul 2023, at 03:03, Mahesh Jethanandani <mjethanandani@gmail.com> wrote:

[Contributor hat on]

Hi Thomas/Alex,

The idea was to provide a “client-server” grouping much along the lines of draft-ietf-netconf-tcp-client-server. With that in mind:
I understand the idea of implementing generic and reusable groupings. However I am asking myself if this draft is the place to implement both client and server. The udp-client is used in the UDP-notif management yang model and therefore I am in favour of implementing it within the draft. On the other hand, the udp-server is not used within the draft and therefore it feels strange to me implementing a generic grouping that is not used within the same draft.

The suggestion by no means implying that it had to be within this draft. If anything, it would be better to move both the client and the server grouping in a draft of its own. 



- Is there a plan for udp-server-grouping?
The authors have not found a usecase within UDP-notif to use a udp-server-grouping and therefore were not planning on implementing one.
- I think you want the dtls container to be outside of the UDP client grouping. An end implementation may or may not want to use dtls.
The DTLS container is active if the feature “dtls13” exists. If the WG feels that 2 generic YANG modules (one with only “remote-address” and “remote-port” and another one using it with the DTLS container) is preferred, we will change that.

Think of it as three different groupings that can be used by themselves 

- UDP client grouping
- UDP server grouping 
- DTLS grouping 

Thanks 


Cheers,
Alex


Thanks.

On Jul 7, 2023, at 5:40 AM, <Thomas.Graf@swisscom.com> <Thomas.Graf@swisscom.com> wrote:

Dear netconf wg,
 
On behalf of the authors, I published draft-ietf-netconf-distributed-notif-07 and draft-ietf-netconf-udp-notif-10 containing the following changes:
 
  • Addressed feedback on udp-client-grouping in udp-notif from IETF 116
  • Added Implementation Status section in udp-notif and distributed-notif
  • Some editorial updates on udp-notif and distributed-notif
 
Looking forward to your review and feedback.
 
Best wishes
Thomas
 
 
draft-ietf-netconf-udp-notif-10
----
The IETF datatracker status page for this Internet-Draft is:
 
There is also an htmlized version available at:
 
A diff from the previous version is available at:
 
 
draft-ietf-netconf-distributed-notif-07
----
The IETF datatracker status page for this Internet-Draft is:
 
There is also an htmlized version available at:
 
A diff from the previous version is available at:
 
_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf" class="" rel="nofollow">https://www.ietf.org/mailman/listinfo/netconf


Mahesh Jethanandani






_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email