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

Tianran Zhou <> Wed, 11 September 2019 09:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE51F120845 for <>; Wed, 11 Sep 2019 02:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id D0gPdZVROrX4 for <>; Wed, 11 Sep 2019 02:33:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6E7E6120844 for <>; Wed, 11 Sep 2019 02:33:49 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 683AA9B2F7F514603358 for <>; Wed, 11 Sep 2019 10:33:47 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 11 Sep 2019 10:33:46 +0100
Received: from ([fe80::a54a:89d2:c471:ff]) by ([]) with mapi id 14.03.0439.000; Wed, 11 Sep 2019 17:33:43 +0800
From: Tianran Zhou <>
To: Kent Watsen <>, "" <>
Thread-Topic: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
Thread-Index: AQHVXFoPOUn3XT57XkG9BuZUaItVxKcmTP+Q
Date: Wed, 11 Sep 2019 09:33:43 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_BBA82579FD347748BEADC4C445EA0F21BEFB1420NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Sep 2019 09:33:52 -0000

Hi Kent,

Considering the multiple stream originator case, I would suggest this https-notif to add a channel level configuration.

            +--here put the http client server configurations

This is compatible with the single originator case with only one channel configuration.

If you do not like this, I think existing https-notif model also works.
i.e. each receiver configuration stands for one channel.
But this is not clear IMO.


From: netconf [] On Behalf Of Kent Watsen
Sent: Tuesday, August 27, 2019 6:02 AM
Subject: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00

This email begins a 2-week adoption poll for:
In-room support for this draft was noted but, as always, it is necessary to confirm WG consensus on the list.  If interested in the WG defining an HTTPS-based solution for *configured subscriptions* (for which there are none to date), please voice your support for this draft's adoption.  If objecting, please state your reasons.

PS: Authors, please additionally respond to as if there is any IPR to disclose.

Kent and Mahesh // as chairs