[Netconf] Need Multi-Replies extention in Netconf?-//FW: New Version Notification for draft-liu-netconf-multiple-replies-01.txt

"Liubing (Leo)" <leo.liubing@huawei.com> Fri, 10 July 2015 07:28 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49FD01A8915 for <netconf@ietfa.amsl.com>; Fri, 10 Jul 2015 00:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4tMXYahVSyUC for <netconf@ietfa.amsl.com>; Fri, 10 Jul 2015 00:28:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9EF41A8906 for <netconf@ietf.org>; Fri, 10 Jul 2015 00:28:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BYP25602; Fri, 10 Jul 2015 07:28:32 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jul 2015 08:28:00 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.135]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Fri, 10 Jul 2015 15:27:56 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: netconf <netconf@ietf.org>
Thread-Topic: Need Multi-Replies extention in Netconf?-//FW: New Version Notification for draft-liu-netconf-multiple-replies-01.txt
Thread-Index: AQHQuuHwMIR1YssWZkyzc//CtRLhdw==
Date: Fri, 10 Jul 2015 07:27:56 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C21E6F76@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.117]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/netconf/9cysd5CH6aeISZYBTRYDwnHzE2c>
Subject: [Netconf] Need Multi-Replies extention in Netconf?-//FW: New Version Notification for draft-liu-netconf-multiple-replies-01.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 10 Jul 2015 07:28:38 -0000

Hi Dear all,

We've uploaded a new version of draft-liu-netconf-multiple-replies-01. This draft was briefly presented in Dallas.

Excuse my iteration, the main idea of the draft is that in some scenarios, multiple replies for a single request might be needed. These scenarios listed in the draft are:
- Bulk reply
  The reply message is huge, needs multiple fragments
- Persistent reply
  Some operations such as Pinging, Tracert need continuous replies for the request.
- Long time reply
  Some operations might take a long time to perform, might need responses returns monitoring progress till the final result
- Datastore push updates (newly added in the 01 version)
  This is regarding to the the i2rs requirements using Subscribing to datastore push updates, which will be discussed in the upcoming meeting.
  The datastore push problem is a comprehensive issue that needs considerations in Content, Operations and Messages layer in Netconf. 
  In our draft, we only cares about the Messages layer. draft-clemm-netconf-yang-push-00 proposed to extend the Notification messaging to fulfill the requirements. This draft proposes multi-replies messaging might also cover the requirements (it needs more discussion though). 

So, with these scenarios, do you think the Netconf need to be extended at the Messages layer to support multi-replies?
(Btw, this draft also briefly discusses two solution alternatives.)

Looking forward to your comments. Thank you.

Best regards,
Bing


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 06, 2015 9:32 PM
To: Zhengguangying; Mahesh Jethanandani; Liubing (Leo); Kent Watsen; Kent Watsen; Zhengguangying; Mahesh Jethanandani; Liubing (Leo)
Subject: New Version Notification for draft-liu-netconf-multiple-replies-01.txt


A new version of I-D, draft-liu-netconf-multiple-replies-01.txt
has been successfully submitted by Bing Liu and posted to the IETF repository.

Name:		draft-liu-netconf-multiple-replies
Revision:	01
Title:		Processing Multiple Replies for One Request in NETCONF
Document date:	2015-07-06
Group:		Individual Submission
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-liu-netconf-multiple-replies-01.txt
Status:         https://datatracker.ietf.org/doc/draft-liu-netconf-multiple-replies/
Htmlized:       https://tools.ietf.org/html/draft-liu-netconf-multiple-replies-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-liu-netconf-multiple-replies-01

Abstract:
   This document discusses several scenarios that multiple replies for a
   single request are needed, with the ability to terminate the replies
   at any time.  Such scenarios are not well supported by current
   NETCONF (Network Configuration) protocol.  An extention at the
   NETCONF messaging layer is needed to fulfill the requirement.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat