[netconf] Last Call on Re: Today's update to client-server drafts

tom petch <ietfc@btconnect.com> Fri, 12 June 2020 16:30 UTC

Return-Path: <ietfc@btconnect.com>
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 144293A07BA for <netconf@ietfa.amsl.com>; Fri, 12 Jun 2020 09:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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=btconnect.onmicrosoft.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 AY_2TRLxrfpR for <netconf@ietfa.amsl.com>; Fri, 12 Jun 2020 09:30:56 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70092.outbound.protection.outlook.com [40.107.7.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 863533A089B for <netconf@ietf.org>; Fri, 12 Jun 2020 09:30:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OnLJCabkB+V80LAqX35YG6eDHa2hKPKLs9PA6sRsGvuDmFF1rdQHKo6xxMJAZqwKt9vEzXA/pFUh0XqGT+/KE2qe/yl8ZvSVdymuPeelCn2ZyC/I9PvOkyy0oQkOysxp/S1t78GcEmQFoeUzmY9Be07NKcSxehxFB8TnSrhDV9xKXw2PxKNhmjnaJzqH1Gf8khZF7OV+y0jzhjzy+V7HCiIxwpICYmkD1R2zU+v60eOonTGJ05sHKKVuckWUcFDdiOZ9behxcFVH1VxfwVk6tmrZumzP/10YDjaH5wc6DiVdeZLie8p9/KK9e4o3Ikew+kDlWCGxKIBsncAtLgh2Gw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Pc6zIcB3NfTim/ysSSD/DQiu5tiECdBr1xfd2QjvFJ4=; b=Hxzbnb2lmE6aZSZUkFs8fbkUlDGQ1lzsoOffnDZlJfK6vQ+0SszwWxysNMqVPs3hyiAudGPUfzoDwJn1aA3Sc1QdyLI0uTcznpSpwWs05hldQKZgunbJwcLmMsz17tb2Zy01XkaA+PA/mwyWoIzzrPO+E+3tt7sJdqKIzALWLx1G0CuUBKQYcRHAfqwCkA+ZujiSeI5LqdMqKnd9q4sJmFfzgYPdq/Z8R6QtGx3dHQEFkwY+f9pSz2+XjvUWUCLD91KB3e4mvBLV8Q46Zctn5Aanu0ULqbbinU9X94Ih2H0nIVzgBu/irGsgjmngsNvAq/D/eIb3Wwr86oPGQl9cxw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Pc6zIcB3NfTim/ysSSD/DQiu5tiECdBr1xfd2QjvFJ4=; b=LkUegswr+kuGk0tgrNtIIZfZJHpmvebv+MQk5M1tkcLe+OwiA/seAXp2ggLbfCM/z8v4oIcWtITH84R01k0gVpJxNKAGNMe/pnVB0yoMVoXiYLpvpk1BUSac7OjQ9wl0jOLzYQoHhZwbAcd0y7JLctZckleZksm2+N4QJfxoaak=
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com (2603:10a6:10:198::14) by DB6PR07MB3301.eurprd07.prod.outlook.com (2603:10a6:6:22::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.7; Fri, 12 Jun 2020 16:30:52 +0000
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::592c:285:6786:bc65]) by DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::592c:285:6786:bc65%7]) with mapi id 15.20.3109.012; Fri, 12 Jun 2020 16:30:52 +0000
From: tom petch <ietfc@btconnect.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Kent Watsen <kent+ietf@watsen.net>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Last Call on Re: [netconf] Today's update to client-server drafts
Thread-Index: AQHWLu3jaU/uAQvClUC0xIr2aQT0pKizkcMAgCG8O+M=
Date: Fri, 12 Jun 2020 16:30:52 +0000
Message-ID: <DBAPR07MB701671D1E66A7C53FB559072A0810@DBAPR07MB7016.eurprd07.prod.outlook.com>
References: <0100017233fe7ff7-8e22b4b1-aa03-4c8e-bf9d-fdbc7d3e41fd-000000@email.amazonses.com>, <85A8ECA9-8875-45FA-839B-50CE35F6C8BA@gmail.com>
In-Reply-To: <85A8ECA9-8875-45FA-839B-50CE35F6C8BA@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.139.211.47]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c038dfe5-fd3f-4d73-088a-08d80eedf95e
x-ms-traffictypediagnostic: DB6PR07MB3301:
x-microsoft-antispam-prvs: <DB6PR07MB3301E3100E4ECC2964C4813AA0810@DB6PR07MB3301.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0432A04947
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6T4mVPU0Ahs/j8QuVfrAYkUMAUA3P6bsxfr+jchYJ+TiyIrrS+3Kye9ptNUhNX5uqxi/ZT1OMEmVQ6xYwBuFWGYSLD1ZTNHORWscdx71mbrq00WIMvycCgFQPESUNEoJ2uUiOLASmNmjx+PWjjR1WeWNErhY9KJLQNbbfIW9k8LAl+sF2AndAnlfD49dajJsVeGhcDC6jgLQOWtuUTr8kyR3vYWOM16IjeJUh49R2IRlzUeJNhDFBWboNbuYptcIL++FmOA0jyMxrghDZCmWpXadchclh6mIELrh8+ZJdIbOMXfOCbgwfEL9ELEMmH1NpFAUd+4NDqDBqj07JKAxvrJ7m2Hmx3/gvyswiQ4wN10Sbl3Lbp+op9Pw7zDfRkdxLQdQZC8oK0xKHV49Y3ZOTQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DBAPR07MB7016.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(376002)(366004)(346002)(136003)(39860400002)(396003)(86362001)(55016002)(33656002)(52536014)(8936002)(8676002)(9686003)(478600001)(83380400001)(966005)(5660300002)(15650500001)(186003)(4326008)(66446008)(66476007)(26005)(2906002)(6506007)(7696005)(316002)(91956017)(64756008)(66556008)(66946007)(76116006)(110136005)(53546011)(71200400001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: FLrYRovVxEAaMzmTLiDxnbMEHDOOIYPRHmjNbxgwFCBu93EfBSVvxo+eYM+e+dJfsNE20VMhaRC2Wl1IuRuxnkEM+4MpT0+Xz2wfjmmzKhg/Njkum+vesP/f9uUQpMJCz/xbHu1Brs3tumHLxXNoYqeiZ1NUgwhb6Td/bGjpK8cNmTbQcM7inQKlQmkIwiYUBVEVHWLH0bHB/sQRssmJufbTc4n2Ld7AVrrxl4BmCFXAw707TdOhY4HfuXjNViyrMI60uPLCxqdSDVsSBGpPYFg4cNmqqi6Xm1jF/xE/AjGG3AvgrK9pNoWKUdcLHc15R6OUbfoYX+o3glMpshwkAM9uO3c9Je52VojK9SH4JYfbc8iqy91HcU0ZtAPSsje810IMBCOXATLaDRw9f8R91t0vrr8GalrGHh8qmSq9SzkXDSclJbGOEEJlr8iJsffIBO05U3d9xhnAWCzX6TMWqG6b76nJLISuGWE9T2pxdSI=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c038dfe5-fd3f-4d73-088a-08d80eedf95e
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2020 16:30:52.5144 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cS6XpVK8QMiD6aAvdqVrQxbuiizLnQDCNQ5RoAkPri4DnUhm3rUAqTy33J/HQ9sbKSAXYd4AUi7kpxUjL7idmg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR07MB3301
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/sR5u1WZ6oCNm7y_sPhKToMH1mpQ>
Subject: [netconf] Last Call on Re: Today's update 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, 12 Jun 2020 16:30:58 -0000

From: netconf <netconf-bounces@ietf.org> on behalf of Mahesh Jethanandani <mjethanandani@gmail.com>
Sent: 22 May 2020 06:14

<tp>
I am sure I saw a Last Call but cannot now find it.

I wonder if there is anyone in the IETF who is familiar with this work and with RFC8635;  would these I-D meet the needs of RFC8635 which I have always seen as one of the two use cases for this work?

In passing, trust anchors registers prefix ta; logical except that the I-D uses ts

Tom Petch

What would it take to get the remaining drafts into WGLC?

> On May 20, 2020, at 2:30 PM, Kent Watsen <kent+ietf@watsen.net> wrote:
>
>
> The entire suite of drafts were updated today.
> The first three drafts are ready for WGLC.
> All of the other drafts are almost ready for WGLC.
> Below is the Change Log entry for each draft.
>
> K.
>
>
> For all drafts:
>
>   o  Added a "Note to Reviewers" note to first page.
>
>
> For crypto-types:
>
>   o  Removed the IANA-maintained registries for symmetric, asymmetric,
>       and hash algorithms.
>
>   o  Removed the "generate-symmetric-key" and "generate-asymmetric-key"
>       RPCs.
>
>   o  Removed the "algorithm" node in the various symmetric and
>       asymmetric key groupings.
>
>   o  Added 'typedef csr' and 'feature certificate-signing-request-
>      generation'.
>
>   o  Refined a usage of "end-entity-cert-grouping" to make the "cert"
>       node mandatory true.
>
>
> For trust-anchors:
>
>   o  Removed "algorithm" node from examples.
>
>   o  Removed the no longer used statements supporting the old "ssh-
>       public-key" and "raw-public-key" nodes.
>
>
> For keystore:
>
>   o  Removed augments to the "generate-symmetric-key" and "generate-
>       asymmetric-key" groupings.
>
>   o  Removed "generate-symmetric-key" and "generate-asymmetric-key"
>       examples.
>
>   o  Removed the "algorithm" nodes from remaining examples.
>
>   o  Renamed/updated the "Support for Built-in Keys" section.
>
>   o  Added new section "Encrypting Keys in Configuration".
>
>
> For tcp-client-server:
>
>   o  Removed commented out "grouping tcp-system-grouping" statement
>       kept for reviewers.
>
>
> For ssh-client-server:
>
>   o  Updated the "keepalives" containers to address Michal Vasko's
>       request to align with RFC 8071
>
>   o  Removed algorithm-mapping tables from the "SSH Common Model"
>       section
>
>   o  Removed 'algorithm' node from examples.
>
>   o  Added feature "client-identity-publickey"
>
>   o  Removed "choice auth-type", as auth-types aren't exclusive.
>
>   o  Renamed both "client-certs" and "server-certs" to "ee-certs"
>
>   o  Switch "must" to assert the public-key-format is "subject-public-
>       key-info-format" when certificates are used.
>
>
> For tls-client-server:
>
>   o  Updated the "keepalives" containers in part to address Michal
>       Vasko's request to align with RFC 8071 and in part to better align to RFC 6520
>
>   o  Removed algorithm-mapping tables from the "TLS Common Model"
>       section
>
>   o  Removed the 'algorithm' node from the examples.
>
>   o  Renamed both "client-certs" and "server-certs" to "ee-certs"
>
>
> For http-client-server:
>
>   o  Removed "protocol-versions" from ietf-http-server based on HTTP WG
>       feedback.
>
>   o  Slightly restructured the "proxy-server" definition in ietf-http-
>       client.
>
>   o  Added http-client example show proxy server use.
>
>
> For netconf-client-server:
>
>   o  Updated examples to remove the 'algorithm' nodes.
>
>   o  Updated examples to reflect the new TLS keepalives structure.
>
>   o  Added keepalives to the tcp-client-parameters section in the
>       netconf-server SSH-based call-home example.
>
>   o  Added a TLS-based call-home example to the netconf-client example.
>
>
> For restonf-client-server:
>
>   o  Updated examples to remove the 'algorithm' nodes.
>
>   o  Updated examples to reflect the new TLS keepalives structure.
>
>   o  Removed the 'protocol-versions' node from the restconf-server
>       examples.
>
>
>
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

Mahesh Jethanandani (as co-chair)
mjethanandani@gmail.com



_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf