IETF Logo Mail Archive

Re: [netconf] Results of "Adoption Call for draft-mahesh-netconf-https-notif-00"

Kent Watsen <kent@watsen.net> Wed, 11 September 2019 05:06 UTC

Return-Path: <0100016d1eb7a7c3-6db38fa6-1c81-45ae-a907-dadb52a5bf78-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 B15C3120168 for <netconf@ietfa.amsl.com>; Tue, 10 Sep 2019 22:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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] 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 Ta3ZU7BILi-O for <netconf@ietfa.amsl.com>; Tue, 10 Sep 2019 22:06:57 -0700 (PDT)
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 01F72120020 for <netconf@ietf.org>; Tue, 10 Sep 2019 22:06:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1568178415; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=Ihv/BgIyZ+WhKQjfEI6A5Egv7TBVmE4uvmTGurK67qU=; b=SV5dpXpepit+4Ep7TC53kYlMVrcmC1Q1rMQR5eNfChzZbzlbb66IUfsiKT4m7F2M 7dX4w8pPAiULMM5RQZDay8W131eNbbJ6w9Zacky8N0puFcK2Fd0Jzze3Z4oqoq41Nz+ sO+8bxu46vlWcmqtCVq/loTjvjZPJsI7SDJMtCpw=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016d1eb7a7c3-6db38fa6-1c81-45ae-a907-dadb52a5bf78-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_09154D71-1D08-44B7-B4D9-A2E58B4654C1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 11 Sep 2019 05:06:55 +0000
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA92F7029@dggeml511-mbx.china.huawei.com>
Cc: Warren Kumari <warren@kumari.net>, "netconf@ietf.org" <netconf@ietf.org>, Ignas Bagdonas <ibagdona.ietf@gmail.com>, Alissa Cooper <alissa@cooperw.in>
To: Qin Wu <bill.wu@huawei.com>
References: <B8F9A780D330094D99AF023C5877DABAA92F7029@dggeml511-mbx.china.huawei.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.09.11-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/BxEtW0gO4V8bYMGgtu9p-Od6jFA>
Subject: Re: [netconf] Results of "Adoption Call for draft-mahesh-netconf-https-notif-00"
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: Wed, 11 Sep 2019 05:06:59 -0000

Hi Qin,

> Agree with Warren's suggestion. I also believe this work can be progressed in parallel with client server model draft, at least TCP client server , TLS client server model draft. 
> The model defined in these documents can be further reused in NETCONF client server model draft and RESTCONF client server model draft. 
> What is tricky is where does ietf-http-client come from? It seems to me it come from draft-kwatsen-netconf-http-client-server-03, which is still an individual draft.

If you recall, we tried to adopt http-client-server at the same time as tcp-client-server, but the HTTPBIS chairs were troubled (the NETCONF chairs reached out to them as a curtesy).  We didn't have the energy at the time to walk them thru it, and the adoption didn't have to happen *immediately* (i.e., it's not one of the first three drafts NETCONF is trying to bring to Last Call).  All this to explain why it is still an I-D.   I think that this having both the https-notif and restconf-client-server drafts depending on http-client-server draft will help the HTTPBIS chairs understand the scope, specifically that it is minimal, which is what they wanted. 

Kent

v2.23.0 | Report a Bug | By Email