Re: [netconf] updates to client/server drafts

Kent Watsen <kent+ietf@watsen.net> Fri, 07 June 2019 22:30 UTC

Return-Path: <0100016b3410e34a-44c383cd-954a-46c4-b8a5-910dca096701-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 CCF49120154 for <netconf@ietfa.amsl.com>; Fri, 7 Jun 2019 15:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, 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 U2W5FDynYXPI for <netconf@ietfa.amsl.com>; Fri, 7 Jun 2019 15:30:51 -0700 (PDT)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A505512002E for <netconf@ietf.org>; Fri, 7 Jun 2019 15:30:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1559946650; h=From:Content-Type:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=KpTCVh7yswTvbCvdwyfWH0HKLI+iipTM5yG3SfMjMPs=; b=JI8Vr8uzKigRUQdo/eqRD7ndRJh6phRUjs+N6WwBQdII+/aIb3VTHizKRWkCJv5B DpJDq5LNe489ikEUaG3q7iQobziuDR9ZN+fBJN0JOnwsmxF/9ixjCZF9LyVrHm2yOnm 2qPc0dCkMbT9j7a1sE/w1hCbowN+0E2v4As7PCiU=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2DA2288F-94A7-4754-8576-6D6914716581"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 7 Jun 2019 22:30:50 +0000
References: <0100016b340e6eb9-e4442a9d-8d44-4f9e-af5c-14ae323a47e2-000000@email.amazonses.com>
To: "netconf@ietf.org" <netconf@ietf.org>
In-Reply-To: <0100016b340e6eb9-e4442a9d-8d44-4f9e-af5c-14ae323a47e2-000000@email.amazonses.com>
Message-ID: <0100016b3410e34a-44c383cd-954a-46c4-b8a5-910dca096701-000000@email.amazonses.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.06.07-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1qL1aAvMK0fq2sf3h4k8v7EknV0>
Subject: Re: [netconf] updates to client/server drafts
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: Fri, 07 Jun 2019 22:30:54 -0000

I misspoke, the restconf-client-server draft is adopted (I was thinking about the http-client-server draft).

K.

> On Jun 7, 2019, at 6:28 PM, Kent Watsen <kent+ietf@watsen.net>; wrote:
> 
> 
> The updates can be broadly described as thus:
> 
> 1) in crypto-types, replaced the 'action' statements with 'crypt-hash' like equivalents.  If folks don't like the "verbs", then we can simply remove them, having no solution for asking the device to generate a key or install a hidden key.
> 
> 2) in trust-anchors, renamed "trust-anchors" to "truststore"
> 
> 3) in both truststore and keystore, moved everything under a 'grouping' statement which is then used by a 'container'.  This is almost an editorial update.
> 
> 4) in tcp-client-server, added support for external NAT (we can remove is preferred)
> 
> 5) in restconf-client-server, added an 'http-listen' (not https-listen) choice, to support case when server is behind a TLS-terminator.  This draft isn't adopted yet, but this is driven by my needing to support this use case in a project I'm working on.  (ps: yes, I'm implementing the entire ietf-restconf-server model).
> 
> 6) also in restconf-client-server, refactored the server module to be more like other 'server' models.  If folks like it, I will also apply the same also to the client model, as well as to both the netconf client/server models.  Now the 'restconf-server-grouping' is just the RC-specific bits (i.e., the "demux" container minus the container), 'restconf-server-[listen|callhome]-stack-grouping' is the protocol stack for a single connection, and 'restconf-server-app-grouping' is effectively what was before (both listen+callhome for many inbound/outbound endpoints).
> 
> There are other smaller changes, please see the change logs and diffs for details.
> 
> 
> PS: the chairs are hoping to enter crypto-types, truststore, and keystore in Last Call in a couple weeks.   There may be another update to crypto-types draft before then pending on my Huawei co-authors.   The remainder of the drafts need more work before ready for Last Call.
> 
> Thanks,
> Kent // contributor
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf