IETF Logo Mail Archive

Re: [Netconf] netconf-binary-encoding comments

Henk Birkholz <henk.birkholz@sit.fraunhofer.de> Fri, 06 July 2018 17:47 UTC

Return-Path: <henk.birkholz@sit.fraunhofer.de>
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 DF8D3130E76 for <netconf@ietfa.amsl.com>; Fri, 6 Jul 2018 10:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 9kj_vorN6vl3 for <netconf@ietfa.amsl.com>; Fri, 6 Jul 2018 10:47:14 -0700 (PDT)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (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 3F688130E6C for <netconf@ietf.org>; Fri, 6 Jul 2018 10:47:14 -0700 (PDT)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w66HlBOs014431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <netconf@ietf.org>; Fri, 6 Jul 2018 19:47:12 +0200
Received: from [134.102.163.216] (134.102.163.216) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.399.0; Fri, 6 Jul 2018 19:47:06 +0200
To: netconf@ietf.org
References: <14395e68-eb71-7766-d4d2-4de0ea67681f@ericsson.com> <CABCOCHRJM5vTgTXcNircjcn6DCqK5fzW3E2rjMM6sb3A3Edz_g@mail.gmail.com> <79d3af9b-dd0c-833b-491f-a25a54a38559@cisco.com> <CABCOCHQfwND7uezS_ykQ4G-v_JPNqTx0Pw3hJVqTVB83XqJgzw@mail.gmail.com> <d6109edb-d54d-2e58-d830-6410f1a22013@cisco.com> <20180706172308.5ro5cjv3x7ujopsx@anna.jacobs.jacobs-university.de>
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Message-ID: <438643a4-8669-7e4b-fd8a-8ecabe9271e3@sit.fraunhofer.de>
Date: Fri, 06 Jul 2018 19:41:31 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180706172308.5ro5cjv3x7ujopsx@anna.jacobs.jacobs-university.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [134.102.163.216]
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/HAEwXPrBnVX695wxMGwgkSJJO5E>
Subject: Re: [Netconf] netconf-binary-encoding comments
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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, 06 Jul 2018 17:47:18 -0000

Hi all,

I cannot speak for NETCONF or RESTCONF, but there is a CoMI Hackathon 
project in Montreal. The champion is Alexander Pelov.

https://trac.ietf.org/trac/ietf/meeting/wiki/102hackathon

If you have the time, expertise or simply are curious, I am certain that 
every contribution or comment is welcome.

Viele Grüße,

Henk


On 07/06/2018 07:23 PM, Juergen Schoenwaelder wrote:
> On Fri, Jul 06, 2018 at 05:38:28PM +0100, Robert Wilton wrote:
>>
>> My consideration was more: where should the NETCONF WG be spending its
>> effort?
>>
> 
> So is there running code? Who is doing binary NETCONF and who is doing
> binary RESTCONF? What are the _measured_ (not expected) savings with
> binary NETCONF and binary RESTCONF? If all the running code moving
> binary values is neither NETCONF nor RESTCONF, why would we spent
> effort to extend NETCONF so that it can support multiple encodings?
> Are people eager to migrate from what they use to this new solution?
> 
> /js
>

v2.23.0 | Report a Bug | By Email