Re: [netconf] Adoption call for draft-kwatsen-netconf-http-client-server-04

"Rob Wilton (rwilton)" <rwilton@cisco.com> Mon, 11 November 2019 14:26 UTC

Return-Path: <rwilton@cisco.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 B5A9F12009C; Mon, 11 Nov 2019 06:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=XXeTteZM; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fK/UVu4h
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 Hlkek8AjA2Sr; Mon, 11 Nov 2019 06:26:21 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F198512007C; Mon, 11 Nov 2019 06:26:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10980; q=dns/txt; s=iport; t=1573482381; x=1574691981; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Bbm5ADH+ehPeFb/mMUhjDyJ42xrCxsndb6mnfYjUsx0=; b=XXeTteZMCmKh09XwYkfZSMSjjYzGcsH8Pe5mHoEdfesG1+780HT3gZyE YPbgGrZul5dCyJMyRKKV6wqkHMK0dWUm/m1SqauLrIDNyRp0m3sZceQ6t +jjnWx99GsFnM5oNZkVeRLqKV7jnY4UWJr/4zmIDXWTWycR3imRwqJowJ E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AHirMlxzpeywJhCjXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZufFkz/MPnsRyc7B89FElRi+iLzPA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DfAQDZbsld/51dJa1lGwEBAQEBAQE?= =?us-ascii?q?FAQEBEQEBAwMBAQGBfoEcLyknBWxYIAQLKgqHZQOKa4Jekx6EYoJSA1QJAQE?= =?us-ascii?q?BDAEBLQIBAYRAAoQUJDgTAgMLAQEEAQEBAgEFBG2FNwyFUQEBAQEDEgsQEwE?= =?us-ascii?q?BNwEPAgEIEQQBAS8yHQgCBAENBQgagwGBeU0DLgECoWgCgTiIYIIngn4BAQW?= =?us-ascii?q?FDBiCFwmBNopRgUMYgUA/gVeCTD6ELxiDQIIslU8kmCEKgiWVX5l5ggyEDIg?= =?us-ascii?q?vmXYCBAIEBQIOAQEFgWkigVhwFYMnUBEUkDaBJwEJgkKKU3SBKIxaAYEOAQE?=
X-IronPort-AV: E=Sophos;i="5.68,293,1569283200"; d="scan'208,217";a="370352132"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Nov 2019 14:26:19 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id xABEQJGD020368 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Nov 2019 14:26:19 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 08:26:18 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 08:26:18 -0600
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 11 Nov 2019 08:26:18 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=euYCsDcRNb67GRzwIA9pPVbdd7jK5wP2ZjvBvVU/I7nktBIrr0bRCkMYcthZcaxLYhBJqfExk5D5TBfHXTjn5ju4ycfqhKEzngUP3jwXimrghxAshXNn1a9ttyIg9TNDTklB+abM9A4ZdQmQTT8VTRXbY4l0GlcCX7I2XqnOmvOC3hdxRNsy087Gp4SxtJB/FV5Hy3TWPeKqFA+axAayMurPmbcJb1+D7Yc8I0tu7h+W3RmzwlEWDn5K8jQLsEUHFQU5gxyZAdP/G4PlRupUC4PJGEzdkT53ras17MeVPm4DYmeUh4LwN4Tb/MioHNSTIrEdHmaT3PWq45oFfVw1jg==
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=FfsjOayPz0Q8iPQCZqRAQS+S5ZUzU4i63cLijlWGhbY=; b=T9A+Qx599P747WomSEehrbYJT2CHfeIUHX2B93EotbQdk5S2PZjAlScgoVpV1zn8li7ms2GdLQj5SkXwOT5qiLzjp6/D76si9d/zlrLzA7sqYQomIqTHuvUoZQDKk7A5nRWxNL+cLPu1mHVlhAJp3Xo18NBFVaDMxM6l9gidox4pxthNtfkoLsAWRxJhV6n+V8Np9gnEPtXaMhi5bfiB1ker6lAv2OXyF3bajEkdjdLSgvUEO8/6nt2zsPWSwpSjf9bl6iGa9RD3/G9Djd3v0e6KR8gOBcE/rWakX9nofIX5REuD501XdGHfHRN6HkZ8Cx3tCIB80WF2alCUW80rfA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FfsjOayPz0Q8iPQCZqRAQS+S5ZUzU4i63cLijlWGhbY=; b=fK/UVu4h9oTRbiMNSjDYQmp4cIKoQJIh4WiWFRUCRkIvuv05pl4tjT2aTcf0ZI1IWbcIYcaM4kNGMv1R2EH9waNOIhjcKC2Ij+EE+AgU1idER23RVzBXuIXHrQvXEWx4XW2vTn7m0tksquAk8p59kZjKbk+IiQVTd17dapN+Jj0=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB4335.namprd11.prod.outlook.com (52.135.38.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.25; Mon, 11 Nov 2019 14:26:17 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::49b6:bc5c:bd3e:203c]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::49b6:bc5c:bd3e:203c%5]) with mapi id 15.20.2430.027; Mon, 11 Nov 2019 14:26:17 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Kent Watsen <kent+ietf@watsen.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Adoption call for draft-kwatsen-netconf-http-client-server-04
Thread-Index: AQHViGJKiGFhsDrRSkSDDSpVvqe78Kd6xJGAgAQocICAAH7EAIAAfoCAgAAGb4CAAB7jAIAAKPyAgABi0oCABYgvMA==
Date: Mon, 11 Nov 2019 14:26:17 +0000
Message-ID: <MN2PR11MB4366C48AAC796F456FC0205FB5740@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <0100016e466ae626-e9821117-8286-4f26-bc91-284d7dcaa453-000000@email.amazonses.com> <20191107153342.gqtgyseqyvsppcul@anna.jacobs.jacobs-university.de> <0100016e46e53383-ec073c86-f9d4-4358-9d78-b337f9cd9a58-000000@email.amazonses.com> <20191107.205057.1889050828820990344.mbj@tail-f.com> <0100016e48af524e-96c5b2d0-6b19-4e26-b3b6-8bb8021851d8-000000@email.amazonses.com>
In-Reply-To: <0100016e48af524e-96c5b2d0-6b19-4e26-b3b6-8bb8021851d8-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.60]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6c1cbef6-41a0-4400-e814-08d766b31d99
x-ms-traffictypediagnostic: MN2PR11MB4335:
x-microsoft-antispam-prvs: <MN2PR11MB4335163E7EBAA47F43783643B5740@MN2PR11MB4335.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(136003)(396003)(376002)(39860400002)(51444003)(189003)(199004)(5660300002)(6116002)(14454004)(790700001)(478600001)(6436002)(52536014)(229853002)(25786009)(4326008)(6246003)(9686003)(3846002)(66946007)(66476007)(66556008)(64756008)(66446008)(6306002)(54896002)(76116006)(55016002)(486006)(256004)(14444005)(99286004)(71190400001)(71200400001)(446003)(11346002)(9326002)(66066001)(81166006)(476003)(8936002)(8676002)(81156014)(110136005)(186003)(74316002)(7696005)(76176011)(6506007)(53546011)(33656002)(86362001)(2906002)(7736002)(102836004)(316002)(54906003)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4335; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hUt15GTiIUAgU4MJUylqLR80yz23c4lon1tsuPZ7jBvtXhAyRrQYQX2aTs7UE4+KGj2vrI9AWteE17yIdpwA/dGxf6kiZ/VQLmzkz/I1w3h+rZ5USSrqsYhbYIDeHmowpWfSFzWDTLGzS1K8Q7yBup5S8vlXFtsw6MK809jKi+sXwR0PscrVcnqZh8AsE3rJgmErVp6bphpJcm7iL3QdyLwfZAAJa8a2oz4qA71yePoWw/COGrhNuW6SJCzLFQZQYzcWSaNgl9lxnCe0x00h2DGBYR23OM0SFQLfxsl6D56Wbvo/k5IfmhbuHqaEFoN06XQrEu9MC8cUnL9dcL0G4hap9bXsSK6YroLO2rmyBpBcu6+Dxg3KN1YzhV2b5ljwowrT6twr97g32vbPd+uOrMfjIaLaHUVxJ0H+32Sj3ViM7i0EgQkcZTzbw+x7WsoI
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4366C48AAC796F456FC0205FB5740MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6c1cbef6-41a0-4400-e814-08d766b31d99
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2019 14:26:17.7669 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TFqgr6G1kDkjAtreEI4T/PlWVVy0UGxd1i6a9U3Y4uN/e2nomcdMBWJGSNEGzagkuJaOnsOqiMAC9QSrt6qFnQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4335
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/G820498z5ArZtOs0WM_kyJEUDiM>
Subject: Re: [netconf] Adoption call for draft-kwatsen-netconf-http-client-server-04
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: Mon, 11 Nov 2019 14:26:23 -0000

Hi Kent,

I broadly agree with Martin here, in that I think that we want to get all of the "Client-Server" drafts finished.

Defining groupings in one place is probably beneficial and I as such as support the adoption of this draft, but not if it going to cause the other drafts that depend on these modules to end up being blocked for another 8 months, or a year.

Can we quickly find a name for these modules that is good enough for us, and would also be acceptable to the httpbis WG?

Perhaps "http-rest" instead of "http" or "restful"?

Thanks,
Rob


From: netconf <netconf-bounces@ietf.org> On Behalf Of Kent Watsen
Sent: 08 November 2019 01:45
To: Martin Bjorklund <mbj@tail-f.com>
Cc: httpbis-chairs@ietf.org; netconf@ietf.org
Subject: Re: [netconf] Adoption call for draft-kwatsen-netconf-http-client-server-04

Hi Martin,

I think it is quite clear that the WG doesn't want more delays.

Is it?   I only know that Balazs K. wishes to have the first three drafts (crypto-types, truststore, and keystore) completed soon.  The Nokia/BBF folks were interested in netconf-server, but forked long ago.  Otherwise, I'm unaware of anyone stating a preference.   For myself, I only hope to achieve a good result.



So I think that either we simply don't add this grouping *at this point*,
and define the necessary nodes in the higher-level modules, even
though it is not perfect; or we define the "restful" module with these
groupings, even though that is also perhaps not perfect.

ietf-restful-client and ietf-restful-server sound nice, but not so much in a stack:

    tcp-server-parameters : { ... },
    tls-server-parameters : { ... },
    restful-server-parameters : { .... },        <---- end-user says "what's that?"
    restconf-server-parameters : { ... }

or (for https-notif)

    tcp-client-parameters : { ... },
    tls-client-parameters : { ... },
    restful-client-parameters : { .... }    <---- end-user says "what's that?"


Actually, the above is purposely inaccurate.   If you recall, we switched to having container-less groupings, thus the consuming module can name the container whatever it wants, so the net-net is no impact other than changing the import and uses statements.   Though I still don't know why we should do even this, given the lack of any response to my Oct 30th message.


Kent // contributor