Re: [Netconf] LC on netconf-event-notifications-08

Qin Wu <bill.wu@huawei.com> Sat, 17 March 2018 06:23 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 9E195127023 for <netconf@ietfa.amsl.com>; Fri, 16 Mar 2018 23:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 dSipMi7LBPZ4 for <netconf@ietfa.amsl.com>; Fri, 16 Mar 2018 23:23:45 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 BE954120227 for <netconf@ietf.org>; Fri, 16 Mar 2018 23:23:45 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A8089B6615F7D for <netconf@ietf.org>; Sat, 17 Mar 2018 06:23:42 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.382.0; Sat, 17 Mar 2018 06:23:43 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Sat, 17 Mar 2018 14:23:40 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Eric Voit (evoit)" <evoit@cisco.com>, Kent Watsen <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] LC on netconf-event-notifications-08
Thread-Index: AdO9uEKe0+yE8tKpSim7DF0SpuNKrA==
Date: Sat, 17 Mar 2018 06:23:39 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AD89B30@nkgeml513-mbs.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.45.62.55]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GJUmpzMXrT-BhtyDZxq16AZLcOU>
Subject: Re: [Netconf] LC on netconf-event-notifications-08
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 17 Mar 2018 06:23:48 -0000

-----邮件原件-----
发件人: Eric Voit (evoit) [mailto:evoit@cisco.com] 
发送时间: 2018年3月17日 6:28
收件人: Qin Wu <bill.wu@huawei.com>; Kent Watsen <kwatsen@juniper.net>; netconf@ietf.org
主题: RE: [Netconf] LC on netconf-event-notifications-08

Hi Qin,

Thanks for the comments.  Thoughts in-line...

> Qin Wu, March 16, 2018 3:25 PM
> 
> One followup comment.
> Section 4, 1st paragraph said:
> "
> A publisher is allowed to concurrently support both
>    [I-D.draft-ietf-netconf-subscribed-notifications] and [RFC5277]'s
>    "create-subscription" RPC,
> "
> There is no "create-subscription" RPC in 
> [I-D.draft-ietf-netconf-subscribed-
> notifications]? Is "create-subscription" RPC  referred to as 
> “establish- subscription” defined in in [I-D.draft-ietf-netconf-subscribed-notifications]?

No.  The create-subscription RPC is actually in RFC-5277.    The subscribed-notifications draft provides establish-subscription as an evolved version of that older RPC.    Nevertheless, a publisher might wish to support both the older and the newer specifications

[Qin]: Would it be great to make this clear in the text. Thanks.

> How is “establish-subscription” Compatibility with RFC-5277's create- 
> subscription? “establish-subscription”  and “create-subscription” can 
> not be used in the same NETCONF session?

Correct.  They cannot be used in the same session.

 
> Section 6.2 configured subscription
> Why draft-ietf-netconf-netconf-event-notifications-08
> Is a separate draft instead of part of 
> draft-ietf-netconf-subscribed-notifications-
> 10 since the state machine for a configured subscription is mainly 
> defined in draft-ietf-netconf-subscribed-notifications-10?

The subscribed-notifications draft is transport independent.     netconf-event-notifications provides details on how allow subscriptions over NETCONF.  Another draft not currently in last call (draft-ietf-netconf-restconf-notif) describes how to allow subscriptions over RESTCONF or HTTTP.    Other transport binding drafts exist for UDP.  Some are being written up for CBOR.


To get an idea of the interplay between many of the different drafts, read:
draft-voit-netconf-subscription-and-notif-overview 

[Qin]: Good, thanks for your clarification.

Eric
 
> -Qin
> -----邮件原件-----
> 发件人: Netconf [mailto:netconf-bounces@ietf.org] 代表 Qin Wu
> 发送时间: 2018年3月7日 9:47
> 收件人: Kent Watsen <kwatsen@juniper.net>; netconf@ietf.org
> 主题: Re: [Netconf] LC on netconf-event-notifications-08
> 
> Support for LC.
> 
> -Qin
> > -----Original Message-----
> > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent 
> > Watsen
> > Sent: Wednesday, February 28, 2018 6:11 PM
> > To: netconf@ietf.org
> > Subject: [Netconf] LC on netconf-event-notifications-08
> >
> > WG,
> >
> > The authors of netconf-event-notifications have indicated privately 
> > that they believe this document is now ready for Last Call.
> >
> > This starts a 2.5-week Last Call on 
> > draft-ietf-netconf-netconf-event-
> > notifications-08 [1] The LC will end on March 17, or when active 
> > threads peter out.
> >
> > Please send your comments on this thread. Reviews of the document, 
> > and statement of support, are particularly helpful to the authors.  
> > If you have concerns about the document, please state those too.
> >
> > Authors please indicate if you are aware of any IPR on the document.
> >
> >
> > [1]
> > https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notific
> > at
> > ions-08
> >
> >
> > Kent & Mahesh
> >
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf