[netconf] Re: Default statements on udp-client-server groupings

Kent Watsen <kent@watsen.net> Tue, 10 September 2024 16:29 UTC

Return-Path: <01000191dcc4509d-0c99ab29-a02e-4a3e-b68b-3b1d58a87f27-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 0E427C14F6E9; Tue, 10 Sep 2024 09:29:01 -0700 (PDT)
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_NONE=-0.0001, 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] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4qousYhPnGI; Tue, 10 Sep 2024 09:29:00 -0700 (PDT)
Received: from a48-92.smtp-out.amazonses.com (a48-92.smtp-out.amazonses.com [54.240.48.92]) (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 295E7C14F5EF; Tue, 10 Sep 2024 09:28:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1725985739; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=xiCM3RiiETJt/eO4bVgr3tgcwPb4dH9RtxLxsLj8cyY=; b=Aw7M5bJC0/0Hm1GL0mrHPnmckhkS/cAJj9xCojxDXdCDZCFY5AZjYKpEz97i8fCt /AkTWvloJkVnugm6NKzyvXKOHKVo/LYjm62S8azPOg5079u3vzP26R/jhmD7iiUAZKQ KtsoWY29SNbvmgCyqyDRKArRTzlnVwKfJBFfAKuY=
From: Kent Watsen <kent@watsen.net>
Message-ID: <01000191dcc4509d-0c99ab29-a02e-4a3e-b68b-3b1d58a87f27-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5E1769C9-22B2-48FA-90E0-80A4E8E7F50D"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Tue, 10 Sep 2024 16:28:58 +0000
In-Reply-To: <CABCOCHRYQmo+XDZMGuTwNJ+OW2F1ZbRDcjMst40Z0GXpFD86-w@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
References: <EAA84133-F9D5-4380-994D-297993F13675@insa-lyon.fr> <01000191dc9a8080-119f64d0-f1d7-4549-9789-ba05daa87609-000000@email.amazonses.com> <CABCOCHRYQmo+XDZMGuTwNJ+OW2F1ZbRDcjMst40Z0GXpFD86-w@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.09.10-54.240.48.92
Message-ID-Hash: D5QLKAEADXY6IYVZKDA5P4PDDYN3JQLG
X-Message-ID-Hash: D5QLKAEADXY6IYVZKDA5P4PDDYN3JQLG
X-MailFrom: 01000191dcc4509d-0c99ab29-a02e-4a3e-b68b-3b1d58a87f27-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: "netconf@ietf.org" <netconf@ietf.org>, draft-ietf-netconf-udp-client-server.authors@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Default statements on udp-client-server groupings
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gbbpFQ1xYQZb4O53CnfQzupKcDI>
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>

> How is this any different than Call Home, which has default port assignments?

Exactly, it seems that UDP-notif should have a port assignment.


> The grouping should not have a default port, but the uses-stmt for the udp-notif service should add one.

The configuration data model for Call Home is in the NC/RC-client-server drafts.  Yes, they “refine” the default as expected.  Here’s an example:

             uses tcpc:tcp-client-grouping {
               refine "remote-port" {
                 default "4336";
                 description
                   "The RESTCONF server will attempt to
                    connect to the IANA-assigned well-known
                    port for 'restconf-ch-tls' (4336) if no
                    value is specified.";
               }
             }

	Note that this grouping does NOT refine the “local-port” from
	the tcp-client-grouping, since its default value is fine.


And here is the “base” grouping:

     leaf remote-port {
       type inet:port-number;
       default "0”;                          <--  THIS IS THE LINE BEING CONTESTED 
       description                                    ^— it seems 50/50 if useful, but it doesn’t harm either, does it?
         "The IP port number for the remote peer to establish a
          connection with.  An invalid default value is used
          so that importing modules may 'refine' it with the
          appropriate default port number value.";
     }
     leaf local-port {
       if-feature "local-binding-supported";
       type inet:port-number;
       default "0";                          <—  AND THIS LINE ALSO
       description                                    ^— this seems like a *good* value for all services, e.g., universal behavior
         "The local IP port number to bind to for when connecting
          to the remote peer.  The port number '0', which is the
          default value, indicates that any available local port
          number may be used.";
     }



Kent // contributor