IETF Logo Mail Archive

Re: [netconf] Upcoming updates to draft-ietf-netconf-udp-notif

Kent Watsen <kent@watsen.net> Thu, 22 July 2021 11:29 UTC

Return-Path: <0100017acdfa4846-8ddd1cdd-1d23-4c11-9916-646c90ac551b-000000@amazonses.watsen.net>
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 1129C3A42E5 for <netconf@ietfa.amsl.com>; Thu, 22 Jul 2021 04:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bo4sH6nIcIT6 for <netconf@ietfa.amsl.com>; Thu, 22 Jul 2021 04:29:31 -0700 (PDT)
Received: from a48-110.smtp-out.amazonses.com (a48-110.smtp-out.amazonses.com [54.240.48.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441063A42E3 for <netconf@ietf.org>; Thu, 22 Jul 2021 04:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1626953369; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=dHPUmbMAbEtTBeswF/psEtIv9mk4y1/oUiqzAymAnFk=; b=ZLmvdpEWxzFHts9zZzY3k8P9FOVbcH4O3BJFTLOgzHUn9oO9fM/880yYa4RRCB4m pqt7Y/8Ru/MR+c4EWLnQbhni5DIUv28AzOL5AzYXso0GIkcih5YyZQAEAPbCT3/y9YU TBvi2CUOS08Ai0iOHRXfdEXWoPFLaJMJC7kYCuOI=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100017acdfa4846-8ddd1cdd-1d23-4c11-9916-646c90ac551b-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3F8554A5-C4A7-4DE9-B856-D9A903F733BD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Thu, 22 Jul 2021 11:29:29 +0000
In-Reply-To: <CAFNmoOEntOdLkU0kvp6V-mTz9VZ7jDW5mnNmkj_-AqGdHtnVRQ@mail.gmail.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Pierre Francois <pierre.francois.ietf@gmail.com>
References: <CAFNmoOEntOdLkU0kvp6V-mTz9VZ7jDW5mnNmkj_-AqGdHtnVRQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.07.22-54.240.48.110
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gbE7vvUChheS7V27jfX645Fq0ks>
Subject: Re: [netconf] Upcoming updates to draft-ietf-netconf-udp-notif
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 22 Jul 2021 11:29:37 -0000

Thank you, Pierre.

All, -03 was posted 10 days ago.  Here’s the direct link:  https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif-03 <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif-03>.

More comments below.

K.


> On Jul 22, 2021, at 4:35 AM, Pierre Francois <pierre.francois.ietf@gmail.com> wrote:
> 
> 
> Hello everyone, 
> 
> The changes brought to -03 followed feedback received from the group:
> 
> -- Added a private encoding option to allow for more verbose private
> encoding description than what can be done in the ET Field.
> 
> -- Security section
> We say this transport is not secure and alternative solutions should be defined elsewhere so as to have a secure version of udp transport provided by the IETF. 
> Note: One option could be draft-unyte-udp-notif-dtls, but we are not mandating one particular solution in this draft. 
> 
> We are suggesting the following changes in a -04 to be submitted once the group agrees:
> 
> --IANA Section
> 
> Create IANA pools for Option type numbers and standard encoding type numbers, and request values for the types already listed in the draft.

There is a discussion going on in the "Capability-fetching mechanisms” thread regarding switching from using an IANA-defined registry to using YANG identities.  I would be good to understand the pros/cons of each.  Ultimately it comes down to 1) writing RFCs requesting IANA to create new entries vs. 2) writing an RFC (or perhaps not) defining a YANG module that defines an identity that derives off a base identity defined in some new module (called, e.g., "ietf-notif-transport-capabilites”).  
.
K.


> Once done, we could ping IANA to have an early allocation so that we could release the collector code using the right values, and the Wireshark dissector being developed could be merged into their main branch. 
> 
> -- Update yang model
> Adding segmentation configuration and maximum segment sizes.
> Currently, only fragmentation configuration is supported.
> 
> IMHO, the -04 will be the version to be last called, but let's see how it goes :)
> 
> Regards, 
> 
> Pierre. 
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email