IETF Logo Mail Archive

Re: [netconf] Current activities on RESTCONF/NETCONF to support paging

Qin Wu <bill.wu@huawei.com> Mon, 18 March 2019 01:39 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 276D7130F28 for <netconf@ietfa.amsl.com>; Sun, 17 Mar 2019 18:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Gqh1tCKfeSEz for <netconf@ietfa.amsl.com>; Sun, 17 Mar 2019 18:39:55 -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 F2220130F20 for <netconf@ietf.org>; Sun, 17 Mar 2019 18:39:54 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C4A4B303C66F4366D210 for <netconf@ietf.org>; Mon, 18 Mar 2019 01:39:52 +0000 (GMT)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Mar 2019 01:39:52 +0000
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 18 Mar 2019 01:39:52 +0000
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Mon, 18 Mar 2019 01:39:52 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.81]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Mon, 18 Mar 2019 09:39:42 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Wisotzky, Sven (Nokia - DE/Stuttgart)" <sven.wisotzky@nokia.com>, wangzitao <wangzitao@huawei.com>, Douglas Hubler <douglas@hubler.us>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Current activities on RESTCONF/NETCONF to support paging
Thread-Index: AdTdKqjdB7vGGWJfR4qgcU5/Okn5Fg==
Date: Mon, 18 Mar 2019 01:39:41 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9B2F075B@nkgeml513-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.31.203]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/2IURSKECm_rrLZgzciPP5ga-9gg>
Subject: Re: [netconf] Current activities on RESTCONF/NETCONF to support paging
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: Mon, 18 Mar 2019 01:39:57 -0000

-----邮件原件-----
发件人: netconf [mailto:netconf-bounces@ietf.org] 代表 Wisotzky, Sven (Nokia - DE/Stuttgart)
发送时间: 2019年3月15日 16:48
收件人: wangzitao <wangzitao@huawei.com>; Douglas Hubler <douglas@hubler.us>
抄送: netconf@ietf.org
主题: Re: [netconf] Current activities on RESTCONF/NETCONF to support paging

> Actually, there are some discussions in this WG. And there is an https://datatracker.ietf.org/drafts/draft-ietf-netconf-restconf-collection draft that try to address these issues (https://tools.ietf.org/html/draft-ietf-netconf-restconf-collection-00). IMO, these problems also exist in NETCONF, therefore, a common solution is required. 
 
It should have been clear from my initial ask. Yes, I am actually interested in a solution which serves both NETCONF and RESTCONF. The problem might be seen more important for RESTCONF - as this is considered protocol of choice for network controllers, talking about a larger scale of objects and traditionally used for communication between WebUI and back-end.

The bigger challenge regarding NETCONF is, that networking devices are often more restricted regarding management plane footprint (CPU/Memory). So whatever solution we come up with, it must be easy to implement without requiring large server-side footprint.

[Qin]: Agree, there is another relevant draft https://tools.ietf.org/html/draft-zheng-netconf-fragmentation-00
which try to address this issue. But the big challenge is large size data handling, whether it should be stateless or stateful. How much state does both side need to keep?

Sven 

_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email