IETF Logo Mail Archive

[netconf] Re: [NMOP] New Version Notification for draft-netana-netconf-yp-transport-capabilities-00.txt

Kent Watsen <kent+ietf@watsen.net> Wed, 29 January 2025 17:23 UTC

Return-Path: <01000194b316f349-45dba822-2042-4b79-90e2-cdec6ce28c14-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 41C18C1840CB; Wed, 29 Jan 2025 09:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 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_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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 HcOtYQkYRtMz; Wed, 29 Jan 2025 09:23:34 -0800 (PST)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D9FEC169410; Wed, 29 Jan 2025 09:23:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1738171413; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=SZM/rqwyLGCTLmF7op+FZbFkv0ls+y6/TYZBQptHQVw=; b=HtoSXRHP+zicDz6A6x87P/Yr8bQuQW5+q8z+EidzlA4jEJUEsNj95igmoR8JZ+Fm BniML58vTD28GYA9+JQiNU1mVCOkadTRsVKi0ILv5xQUfmwRe/h+JWVHp1N15VEg204 CPR1amxijQszwDJXAdZkMzH2Wm8Eaiz01GIczm+A=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <01000194b316f349-45dba822-2042-4b79-90e2-cdec6ce28c14-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EA82A1DE-28AA-4214-8D0C-5AF99D51E708"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Wed, 29 Jan 2025 17:23:33 +0000
In-Reply-To: <CABCOCHQVPDd0rPgqrTYURLbTfsTEYTQCOvQAyYQhS7=FxK5JLw@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
References: <172917034955.1401018.6866481846942967268@dt-datatracker-78dc5ccf94-w8wgc> <6af696264f06484e8ae82f4ea394acb8@swisscom.com> <01000193bbb548e5-9619d8ee-92a5-4d65-8b8e-07219797b8f5-000000@email.amazonses.com> <9967d4393be241a68bd757770b36ec62@huawei.com> <01000193c0a97670-129c6dbd-bbd9-43ef-b22f-80190a36bf87-000000@email.amazonses.com> <fc2551fb04934e79b56009a33b770a4a@swisscom.com> <01000193dfccb260-269d6697-a33a-4792-aae9-047f0d5cb25e-000000@email.amazonses.com> <e20ad9f5e6c94c03abe2d23aee7ff19b@swisscom.com> <BB86B0B9-EC74-40BD-8FDF-3179242964EF@watsen.net> <0100019494ec650b-037db71e-ceeb-40d6-9f89-b338821df6df-000000@email.amazonses.com> <CABCOCHQVPDd0rPgqrTYURLbTfsTEYTQCOvQAyYQhS7=FxK5JLw@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2025.01.29-54.240.8.83
Message-ID-Hash: L62EO7Z4JGHBDJXFJ7T5WNPFHZPQ2PD4
X-Message-ID-Hash: L62EO7Z4JGHBDJXFJ7T5WNPFHZPQ2PD4
X-MailFrom: 01000194b316f349-45dba822-2042-4b79-90e2-cdec6ce28c14-000000@amazonses.watsen.net
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: Thomas.Graf@swisscom.com, "maqiufang (A)" <maqiufang1=40huawei.com@dmarc.ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, draft-netana-netconf-yp-transport-capabilities.authors@ietf.org, nmop@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: [NMOP] New Version Notification for draft-netana-netconf-yp-transport-capabilities-00.txt
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/fx0Ggk2uHVJ_D5BWDlmgayWvUOk>
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 Andy,

>> IMO, 8639 is DotW (dead in the water).  Let it go.  It doesn’t matter because no one is using it.
> 
> 
> RFC 8639 is in use by some vendors.
<snip/>

Options #3 and #4 apply a loose interpretation of the specs.  What it means is that 8639-producers need to be sure to always configure an encoding when using udp-notif.  I’m suggesting we make this choice because it seems less bad than forcing udp-notif to have a default encoding.  Nothing is being taken away, in case that was your concern.

> Why is a mandatory encoding required for UDP-Notif when it is not for RESTCONF?

Assuming s/RESTCONF/https-notif/, it is because the https-notif draft includes a discovery mechanism for the producer to determine the collector's supported encodings.

Kent // contributor

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