IETF Logo Mail Archive

Re: [Netconf] activate-configured-subecription - WGLC subscribed-notifications-16

Qin Wu <bill.wu@huawei.com> Wed, 19 September 2018 03:06 UTC

Return-Path: <bill.wu@huawei.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 DDD36130E29 for <netconf@ietfa.amsl.com>; Tue, 18 Sep 2018 20:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3FgbNPRBN0LO for <netconf@ietfa.amsl.com>; Tue, 18 Sep 2018 20:06:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFADF130DFD for <netconf@ietf.org>; Tue, 18 Sep 2018 20:06:53 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [10.201.108.46]) by Forcepoint Email with ESMTP id 7B019676A5F3A for <netconf@ietf.org>; Wed, 19 Sep 2018 04:06:49 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.399.0; Wed, 19 Sep 2018 04:06:50 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.200]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0399.000; Wed, 19 Sep 2018 11:06:45 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Eric Voit (evoit)" <evoit=40cisco.com@dmarc.ietf.org>, Douglas Hubler <douglas@hubler.us>, Martin Bjorklund <mbj@tail-f.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] activate-configured-subecription - WGLC subscribed-notifications-16
Thread-Index: AQHUSpBgBUFGD5oy2kmpOilc7/EuyqTuKlmAgACurwCAAAD1gIAFUEkAgAG9NoCAAAwnAIAAICCAgAATFYCAAM5uAA==
Date: Wed, 19 Sep 2018 03:06:45 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9B04B16C@nkgeml513-mbx.china.huawei.com>
References: <20180914071445.ywfnizh4rnzbrs4f@anna.jacobs.jacobs-university.de> <CABCOCHRes7CLrdtyyTz1whmuuU_rMMVTHGh8vM32H+jukEf1LQ@mail.gmail.com> <CALAkb6emOEv0Zo6mss5wjp7NaO4pLbjZxGbNc2Bodt_PuZFu6A@mail.gmail.com> <20180918.214022.2268667197465086195.mbj@tail-f.com> <CALAkb6cfiFugMpSdU+FUhu9zRsWkXttGRZq80VQtD9kM+wM4bg@mail.gmail.com> <48e4aac958d142669f4032737cdc4373@XCH-RTP-013.cisco.com>
In-Reply-To: <48e4aac958d142669f4032737cdc4373@XCH-RTP-013.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.244]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9B04B16Cnkgeml513mbxchi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/X2Hc9Fw54uoO4qpXz7-SwbDB1kg>
Subject: Re: [Netconf] activate-configured-subecription - WGLC subscribed-notifications-16
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Configuration WG mailing 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, 19 Sep 2018 03:06:56 -0000

发件人: Netconf [mailto:netconf-bounces@ietf.org] 代表 Eric Voit (evoit)
发送时间: 2018年9月19日 6:44
收件人: Douglas Hubler; Martin Bjorklund
抄送: netconf@ietf.org
主题: Re: [Netconf] activate-configured-subecription - WGLC subscribed-notifications-16

Hi Douglas,

From: Douglas Hubler, September 18, 2018 5:35 PM

On Tue, Sep 18, 2018 at 3:40 PM Martin Bjorklund <mbj@tail-f.com<mailto:mbj@tail-f.com>> wrote:
So it seems you support my point to make this draft use SSE.  Then if
you use HTTP/2 you (the client) can simply create one HTTP/2 stream per
notification stream.  This just falls out for free with HTTP/2.

yes, with caveat that I haven't attempted actual implementation yet.

<Eric> Agree that SSE over HTTP2 should work.  However to me using SSE here seems redundant as HTTP2 provides the necessary mechanisms.  But I won’t get in the way if people really do want to go in this direction.

[Qin]: HTTP2 provides Server Push mechanism however there are lots of drawbacks, typical one is Server Push may be blocked, therefore HTTP1.1+ SSE is favored.

v2.23.0 | Report a Bug | By Email