Re: [Netconf] New Version Notification for draft-mahesh-netconf-binary-encoding-00.txt
Qin Wu <bill.wu@huawei.com> Sun, 18 March 2018 08:43 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 247FF1200FC for <netconf@ietfa.amsl.com>; Sun, 18 Mar 2018 01:43:54 -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, HTML_MESSAGE=0.001, 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] 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 tgmJPxeNxMZD for <netconf@ietfa.amsl.com>; Sun, 18 Mar 2018 01:43:51 -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 37F7F12D7F0 for <netconf@ietf.org>; Sun, 18 Mar 2018 01:43:48 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 01093CAD4E502 for <netconf@ietf.org>; Sun, 18 Mar 2018 08:43:44 +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; Sun, 18 Mar 2018 08:43:44 +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; Sun, 18 Mar 2018 16:43:37 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Robert Wilton <rwilton@cisco.com>
CC: Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] New Version Notification for draft-mahesh-netconf-binary-encoding-00.txt
Thread-Index: AdO+kpHmJIQoi/2vS2mysfGm2uI78A==
Date: Sun, 18 Mar 2018 08:43:37 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AD8D18A@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.47.83.100]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AD8D18Ankgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/axgoDJRVYjGDT6XaaGUKpP3K8xc>
Subject: Re: [Netconf] New Version Notification for draft-mahesh-netconf-binary-encoding-00.txt
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: Sun, 18 Mar 2018 08:43:54 -0000
7) There is no encoding of metadata in CBOR, it might be useful if that was also considered, probably that would end up being a separate draft. 7b) Related to 7, how would the <edit-config> operations (merge, create, remove, etc) be encoded. 7c) Would errors also be reported using a binary encoding, or would they stay in XML? [Qin]: Interesting case, how do we deal with XML encoding and Binary encoding coexisting case? Juergen had a similar question. After discussing with him, we will clarify in the next version of the document that the encoding will be for everything above the Messages layer per Figure 1 of RFC 6241. So the answer to 7c is that it will stay in XML. For 7b, and example conversion of a XML to JSON encoding would look like this: In XML: <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get-config> <source> <running/> </source> <filter type="subtree"> <interface-configurations xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg"> <interface-configuration> <active>act</active> <interface-name>GigabitEthernet0/0/0/0</interface-name> </interface-configuration> </interface-configurations> </filter> </get-config> </rpc> After switching to JSON encoding the same request would look something like (just noticed that type=“subtree” got dropped) <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> { "ietf-netconf:get-config": { "source": { "running": null }, "filter": { "interface-configurations": { “xmlns":"http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg", "interface-configuration": { "active": "act", "interface-name": "GigabitEthernet0/0/0/0" } } } } } </rpc> [Qin]: I believe Conversion from XML to JSON has already been support internal YANG tool. But I am not sure we have tool to convert XML encoding to binary encoding. Maybe CBOR has already done this. 8) Does there need to be any comment/considerations regarding YANG push and friends. Yes, there are considerations for YANG push and friends drafts. Eric tells me that there is an ability in subscribed notifications to change the encoding mid-stream. But in general, I'm supportive of IETF allowing binary encodings to be used in NETCONF/RESTCONF for devices that want to use them. They seem to be particularly relevant to streaming telemetry related applications. Agree. Thanks, Rob On 22/02/2018 02:29, Mahesh Jethanandani wrote: This short draft proposes a mechanism for NETCONF clients and servers to negotiate an alternate form of encoding, e.g. binary encoding. Cheers. Begin forwarded message: From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> Subject: New Version Notification for draft-mahesh-netconf-binary-encoding-00.txt Date: February 21, 2018 at 6:18:45 PM PST To: "Jason Lam" <lamj@cisco.com<mailto:lamj@cisco.com>>, "Alfred Leung" <alfleung@cisco.com<mailto:alfleung@cisco.com>>, "Mahesh Jethanandani" <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>> A new version of I-D, draft-mahesh-netconf-binary-encoding-00.txt has been successfully submitted by Mahesh Jethanandani and posted to the IETF repository. Name: draft-mahesh-netconf-binary-encoding Revision: 00 Title: Binary Encoding for NETCONF Document date: 2018-02-23 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-mahesh-netconf-binary-encoding-00.txt Status: https://datatracker.ietf.org/doc/draft-mahesh-netconf-binary-encoding/ Htmlized: https://tools.ietf.org/html/draft-mahesh-netconf-binary-encoding-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-mahesh-netconf-binary-encoding-00 Abstract: This document describes a method by which a NETCONF [RFC6241] client and server can negotiate an alternate form of encoding. This document updates RFC 6241. 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<http://tools.ietf.org/>. The IETF Secretariat Mahesh Jethanandani mjethanandani@gmail.com<mailto:mjethanandani@gmail.com> _______________________________________________ Netconf mailing list Netconf@ietf.org<mailto:Netconf@ietf.org> https://www.ietf.org/mailman/listinfo/netconf Mahesh Jethanandani mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>
- [Netconf] Fwd: New Version Notification for draft… Mahesh Jethanandani
- Re: [Netconf] Fwd: New Version Notification for d… Robert Wilton
- Re: [Netconf] New Version Notification for draft-… Mahesh Jethanandani
- Re: [Netconf] New Version Notification for draft-… Qin Wu
- Re: [Netconf] New Version Notification for draft-… Martin Bjorklund
- Re: [Netconf] New Version Notification for draft-… Andy Bierman