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

Kent Watsen <kent+ietf@watsen.net> Thu, 07 November 2019 17:24 UTC

Return-Path: <0100016e46e53383-ec073c86-f9d4-4358-9d78-b337f9cd9a58-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 DF4FD12093A; Thu, 7 Nov 2019 09:24:19 -0800 (PST)
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 XKSDL6shkNcr; Thu, 7 Nov 2019 09:24:18 -0800 (PST)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEEA912093E; Thu, 7 Nov 2019 09:24:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1573147456; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=jzeD5+fsMQBVMYgqO6+C2IglewIsy6cH1B/ShR1wqjI=; b=Y+khX6gYG3oD5pBpcTBY7iar7ycHkmTlBItZMfUgze1eU8Xr4YbCkL8s7vT9nP5M VCV4T0Aa+48TY47lzQxKqM89ETwgq+xAqFX8jLpdzNj5dcqimnolVnnafIvRUrrkvDs JUrMt+bH4BbZGuXAb6syDwEmOgacrJBC8FqNCfQA=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016e46e53383-ec073c86-f9d4-4358-9d78-b337f9cd9a58-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_26E16379-4213-4045-AED7-6AF8C2B9D7A9"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 7 Nov 2019 17:24:16 +0000
In-Reply-To: <20191107153342.gqtgyseqyvsppcul@anna.jacobs.jacobs-university.de>
Cc: "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
To: Juergen Schoenwaelder <J.Schoenwaelder@jacobs-university.de>
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>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.11.07-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IeIeu2S2PO07gZnXs0OAMOvBV3Q>
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: Thu, 07 Nov 2019 17:24:20 -0000

>>>> 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 <https://datatracker.ietf.org/meeting/106/materials/agenda-106-httpbis-01.html>

Kent