IETF Logo Mail Archive

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

wangzitao <wangzitao@huawei.com> Tue, 17 September 2019 03:28 UTC

Return-Path: <wangzitao@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 4A4EF12006E for <netconf@ietfa.amsl.com>; Mon, 16 Sep 2019 20:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtwlvnftGBfX for <netconf@ietfa.amsl.com>; Mon, 16 Sep 2019 20:28:52 -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 7E5CB12006D for <netconf@ietf.org>; Mon, 16 Sep 2019 20:28:52 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5E6F6E3FEB7C2C7AE6FC for <netconf@ietf.org>; Tue, 17 Sep 2019 04:28:50 +0100 (IST)
Received: from lhreml727-chm.china.huawei.com (10.201.108.78) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 17 Sep 2019 04:28:50 +0100
Received: from lhreml727-chm.china.huawei.com (10.201.108.78) by lhreml727-chm.china.huawei.com (10.201.108.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 17 Sep 2019 04:28:49 +0100
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml727-chm.china.huawei.com (10.201.108.78) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Tue, 17 Sep 2019 04:28:49 +0100
Received: from DGGEMM527-MBX.china.huawei.com ([169.254.6.177]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0439.000; Tue, 17 Sep 2019 11:28:45 +0800
From: wangzitao <wangzitao@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
Thread-Index: AdVtB/z6FCRUy5flRC6mfDV5ok21pQ==
Date: Tue, 17 Sep 2019 03:28:44 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2DAFF493@DGGEMM527-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.142.117]
Content-Type: multipart/alternative; boundary="_000_E6BC9BBCBCACC246846FC685F9FF41EA2DAFF493DGGEMM527MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4jQtK2q81l98KYFDqsQuItyUck8>
Subject: Re: [netconf] 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: Tue, 17 Sep 2019 03:28:55 -0000

Hi Kent,

See my reply inline.

B.R.
-Michael

发件人: Kent Watsen [mailto:kent+ietf@watsen.net]
发送时间: 2019年9月17日 0:01
收件人: wangzitao <wangzitao@huawei.com>
抄送: netconf@ietf.org
主题: Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00

Hi Michael,


I am trying to understand the relationship and usage of this draft and a set of netconf drafts:
This model present the receiver's information (such as IP, port, etc) and it augment the ietf-subscription-notification model that the user can specify multiple subscription receivers.
And the user also need to configure the server to specify receiver's port and IP (via ietf-client-server?).

What is " ietf-client-server" ?
Sorry, it should be “NETCONF Client and Server Models”.

That the server can call home to the receivers.
Is my understanding correct? If yes, I suggest that a brief description of the workflow should be present in the draft.

This is a good suggestion.  We will add a section showing context.

Cool.


Kent





Best Regards!
-Michael

v2.23.0 | Report a Bug | By Email