IETF Logo Mail Archive

[netconf] http and RC client-server updates

Kent Watsen <kent+ietf@watsen.net> Tue, 09 July 2024 01:39 UTC

Return-Path: <010001909524f397-3c195919-3b71-4178-b8c5-dcd3f4db7a16-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 61C63C1E7245 for <netconf@ietfa.amsl.com>; Mon, 8 Jul 2024 18:39:07 -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 ln98g2PcANpu for <netconf@ietfa.amsl.com>; Mon, 8 Jul 2024 18:39:06 -0700 (PDT)
Received: from a48-90.smtp-out.amazonses.com (a48-90.smtp-out.amazonses.com [54.240.48.90]) (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 84B87C1E7242 for <netconf@ietf.org>; Mon, 8 Jul 2024 18:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1720489145; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:To:Feedback-ID; bh=9RnIEV3Isrf8UcWPZgj8VP4XRV3RHh4nSIqbHf6CbBQ=; b=ZChz3r8V2yOASSLlLhxIHjNkgYwHDVwaeMJSeXyo7DOflukXbkcPpwppG4HkRDrq I1EdT04XaQjpxVqw8SxrR61q/GWud6z9CEvjrcJOhnnYyvSf9baWdDgMMycpI99fqrK UxKlvIIs7rO8IojYkO8X1F7f9Trn8RZDvwOjxLZQ=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F9F0F604-AAF2-4E9A-90ED-942E75DA0956"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Message-ID: <010001909524f397-3c195919-3b71-4178-b8c5-dcd3f4db7a16-000000@email.amazonses.com>
Date: Tue, 09 Jul 2024 01:39:05 +0000
To: "netconf@ietf.org" <netconf@ietf.org>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.07.09-54.240.48.90
Message-ID-Hash: EPXW2ERHOBFI547HMKBPDQIMIX3YV4AI
X-Message-ID-Hash: EPXW2ERHOBFI547HMKBPDQIMIX3YV4AI
X-MailFrom: 010001909524f397-3c195919-3b71-4178-b8c5-dcd3f4db7a16-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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] http and RC client-server updates
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/qob5xg46ACuHytB59MkFd65rvZ0>
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>

I posted updates for the following drafts:

	- http-client-server
	- restconf-client-server

The updates are as follows:

For the http-client-server draft, the update is rather big.  After discussing with HTTP chairs and other experts, it was noted that our configuration for the HTTP-client was not expected.   What was stated was that the URI itself should be sufficient.  The update only affects the “client” groupings.  Now the client groupings have a “uri” leaf that is expected to encode transport details.

For the restconf-client-server draft, the update is only to adjust the examples to reflect the changes in the http-client-server draft.

Best,
K

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