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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Mon, 11 November 2019 14:22 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 2049D120289; Mon, 11 Nov 2019 06:22:42 -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=j8mdUdRz; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=FPfdZ2fY
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 Uh7VFpXXAKbU; Mon, 11 Nov 2019 06:22:39 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 662F512009C; Mon, 11 Nov 2019 06:22:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10058; q=dns/txt; s=iport; t=1573482159; x=1574691759; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dX4Yiz6Qj90bp3LyLbEfbyU+f0q9VCfiPO4pvHn3xfY=; b=j8mdUdRz00h5nhuGphidE5ON5+mk4HXT56aVsvD5QxZsJYNC/9HidEaY jbl2kYHIWBRYtj/CvpU0IU5gASQw5R5exBo4xpThJ9zaSxdi/inuwZMH9 0G+LbvPXlJJqxlc3UWf6Z2zsu8L1SXQzbibn/S41Cjab1o85Rq3QYH1ud Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3Aoaf+7hGIG47WbzrjSWXxRJ1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+eeT1bigmG8JqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAAB4bcld/51dJa1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF+gRwvKScFbFggBAsqCodlA4pqgl6THoRiglI?= =?us-ascii?q?DVAkBAQEMAQElCAIBAYRAAoQUJDgTAgMLAQEEAQEBAgEFBG2FNwyFUQEBAQE?= =?us-ascii?q?DEgsQEwEBKQ4BDwIBCBABBAEBKAcyFAkIAgQBDQUIEweDAYF5TQMuAQIMoV4?= =?us-ascii?q?CgTiIYIIngn4BAQWBNAEDBINNGIIXAwaBNowUGIFAP4FXgkw+gmICAQKBSBg?= =?us-ascii?q?MHwmDDIIslU8kmCEKgiWHF45ImXmCDIQMiC+INpFAAgQCBAUCDgEBBYFpIoF?= =?us-ascii?q?YcBU7gjgBM1ARFJA2DBeBBAEIgkOFFIU/dAGBJ4xaAYEOAQE?=
X-IronPort-AV: E=Sophos;i="5.68,293,1569283200"; d="scan'208,217";a="377649165"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Nov 2019 14:22:38 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id xABEMbPG015517 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Nov 2019 14:22:37 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 08:22:37 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 09:22:36 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 11 Nov 2019 09:22:36 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AoqGVkJHnBFyDR+iMjYFre/W5ShPUCxjX2vPEOGmicGzp5n16qDicP4tT1NTPIIBP22bs9Y78vy6lYUf4KohpW3mnKKsDTRo4JS64HzTxly1Tu/vxNBGodS8xE2qMhCE8rvoz4pRGehPKHCLorPtCsOfkyK9NFVad+w7YVs4Ql31wHTGe9hvWHqACW+9cUSa9iZaJ+AGaES4ZaNHuhGUAuNcSq2P9CGj4543O1JxhMu0f6VWheIOQvTN9esipLlpH33bzoA4FLEl6h6NVR+/ksv5JgNjZsK8h2b13t7Bk+aJq8FSKv0KWFUF92tF6pE41lC7VdyDAU8oTh17g+5QQg==
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=fApCWX5h1Iml5+YIZaJdUxq5xS/1EB9q6v9tPELbimw=; b=gdlobzwJk0NsZpkDnfI5Hw9raaHnkW78N/jIKtCCtYIMJx2jxe+v15B/gffcg8rubs0fZxBIeNQ/STGLTwfZNRpteykuZDx1idJaumgPLVW36/j9FmMI78mHZPbc6yH7Bb1/6OfcLXpFq2fBwcnQDlR06nftO8n/p0H2iKIAjfLJbv0vmNrwdVsLIoaQPelNLN+RhuVuup5s7qLgJuU/UipujAmvPgBj7ayNXkFuweennipRhLMeR5DxkfdkG4twBL/hA0JiJ4NZfmrZSHXO+QDMqlagtfmZZbbZM1d5tEGLlv8CM4tH8bmx44yiZTN3TUKYJwBRbKdsn4nYqp8pAw==
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=fApCWX5h1Iml5+YIZaJdUxq5xS/1EB9q6v9tPELbimw=; b=FPfdZ2fYj+GKgC2jUowhlRZe2OsBhMjl566s98U1+Xu5KpxWzQtD2u+Ijmv69E8hZdEz/xNXCw+6+r5LfRHWLt+4HHfzrX8qjNFqtjD/Lc1EGzF46EwyveByM0B5ToE/z9VKZIS4ZoYYdzPMakYLFNu/xFZ9vC7Re7/04m8O4fQ=
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:22:35 +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:22:35 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Kent Watsen <kent+ietf@watsen.net>, Juergen Schoenwaelder <J.Schoenwaelder@jacobs-university.de>
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: AQHViGJKiGFhsDrRSkSDDSpVvqe78Kd6xJGAgAQocICAAH7EAIAAfoCAgAAGb4CAAB7jAIAGFkxw
Date: Mon, 11 Nov 2019 14:22:35 +0000
Message-ID: <MN2PR11MB43665D4C44574150432EA1BDB5740@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <704A1489-3BC0-4EFF-A5B0-7D664EA05970@gmail.com> <20191104.093427.842126049822749848.mbj@tail-f.com> <0100016e432d004b-32e62ef2-4e6c-48f6-8fa4-092c55778ea8-000000@email.amazonses.com> <20191107073755.kw6xqp5uqruiask6@anna.jacobs.jacobs-university.de> <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>
In-Reply-To: <0100016e46e53383-ec073c86-f9d4-4358-9d78-b337f9cd9a58-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: 5eea4993-384e-4811-d25a-08d766b298ef
x-ms-traffictypediagnostic: MN2PR11MB4335:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB433579C011CB5B248D2FD17BB5740@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)(396003)(39860400002)(136003)(346002)(366004)(376002)(199004)(189003)(9326002)(66066001)(81166006)(8676002)(110136005)(81156014)(476003)(8936002)(71190400001)(99286004)(71200400001)(486006)(14444005)(256004)(446003)(11346002)(102836004)(7736002)(2906002)(21615005)(54906003)(26005)(316002)(76176011)(186003)(74316002)(7696005)(86362001)(53546011)(6506007)(33656002)(790700001)(14454004)(6436002)(52536014)(966005)(478600001)(5660300002)(606006)(6116002)(3846002)(9686003)(54896002)(6306002)(66446008)(64756008)(66476007)(66946007)(66556008)(236005)(55016002)(76116006)(4326008)(25786009)(229853002)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4335; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: lq2Oak5DbfawLwnbIWzrKEq8H0B0F5lIKFzGkaB4Dnp9EwuCfRM5nZL8oWPebgS8cLlD9HSpVEk3WLMFJvyRE57QXxu6xUT/gCoYy2UQtrVSNTjRZnLDXFb6yuk0kV0fJmNXtFBjmjGhzQ5AWZ9t6hS/Xo2362dO2C5Si+FbokEhyNAjTNaSg9nPCrh/f0coGbNttf1lwOcrJTnqSoKbjuwxFtgw0ZNcvpIv2N2/JEvEtxh0SHtyDW2JHWPlOkbpcA+yCUPaMh8i0Z3sbnHcMCYwbSHlviv6GScJyMsFZHRjUB1ZnSzBALwOzgn+9bTrapHgB3IVx3wsrj4N6DAfhexbaKgXrfX6O/Jl1Tv/6J1tchsfphIUnjHPh8EImftyoLETuPVKuV47uVG9yBQhpdmjqlnn7qHDKbeZjBnBLm1wZehw7TghFqLp8M3t1W6TrB91kuPOzzuNeRpgKoqRKQ+BoJ1Nr2AF8Q+zXnHfy5o=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43665D4C44574150432EA1BDB5740MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5eea4993-384e-4811-d25a-08d766b298ef
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2019 14:22:35.1600 (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: fxUXeykpWLfjG9PPLCSUos+Tm+rNGGA+OyW6KST8g5My3e1CJ8GW25OEE0/scCJesTzt5AxMKZwwC0xy1BWD+g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4335
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/i40e5iGQkeDyj48n_rdpz41Wdu0>
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:22:42 -0000

Hi Kent,

According to https://datatracker.ietf.org/wg/httpbis/charter/, it looks like the list address is: ietf-http-wg@w3.org<mailto:ietf-http-wg@w3.org>

Thanks,
Rob


From: netconf <netconf-bounces@ietf.org> On Behalf Of Kent Watsen
Sent: 07 November 2019 17:24
To: Juergen Schoenwaelder <J.Schoenwaelder@jacobs-university.de>
Cc: httpbis-chairs@ietf.org; netconf@ietf.org
Subject: Re: [netconf] Adoption call for draft-kwatsen-netconf-http-client-server-04


Noteworthily, the HTTP experts additionally said that they would have no issue if the module were called something else (ietf-restful-http-client/server?) as then it wouldn't appear to intending to be an all-encompassing HTTP definition and it would no longer require involvement of the HTTP experts to ensure correctness.

Changing the module name to ietf-restful-http-client/server makes any
reuse of the definitions look back.

Can you clarify what you mean by "look back"?

The name just looks odd: Do I want to import something that is labeled
as a restconf specific grouping? The HTTP people do not want us to
define something that may look generic but do we want to define
something that looks like a solution just for restconf? Well, perhaps
we should just put the -restconf- thing in the name and future will
tell us whether people reuse this or attempt to roll their own.

I see, but note that I wrote "restfull" (not "restconf"), which is important since the "https-notif" draft is NOT using RESTCONF (just HTTP).

That said, I don't see why we shouldn't proceed with "http", as that is what the protocol layer is called.   At one point the HTTP chairs said that, if we wanted to use "http", then we should involve the httpbis WG, which makes sense, but shouldn't (in my mind) block an adoption.   I suggest that we take the draft to the httpbis list and (maybe) present it in the httpbis session.

A couple days ago I looked for the httpbis list, but couldn't find it.  Their agenda [1] looks packed, so probably too late for a new request, but if the HTTP chairs are reading this and think we could squeeze in a quick preso, that would be great, otherwise, pointers to the httpbis list would be appreciated.

[1] https://datatracker.ietf.org/meeting/106/materials/agenda-106-httpbis-01.html

Kent