IETF Logo Mail Archive

Re: [Netconf] Issue #2 for binary encoding: Should the new encoding include the Message layer?

Carsten Bormann <cabo@tzi.org> Fri, 29 June 2018 07:46 UTC

Return-Path: <cabo@tzi.org>
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 376E9124BE5; Fri, 29 Jun 2018 00:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 NvHPHr3tApPG; Fri, 29 Jun 2018 00:46:31 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 20522130EDA; Fri, 29 Jun 2018 00:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w5T7kRhj026048; Fri, 29 Jun 2018 09:46:27 +0200 (CEST)
Received: from [192.168.217.102] (p5DC7FF04.dip0.t-ipconnect.de [93.199.255.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 41H7xv54svzDXGc; Fri, 29 Jun 2018 09:46:27 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABCOCHQUDEiNAEj-NfBbpu8_RHuLk6U0HUNVFsTpHXBTuaDrgg@mail.gmail.com>
Date: Fri, 29 Jun 2018 09:46:27 +0200
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, draft-mahesh-netconf-binary-encoding@ietf.org, Netconf <netconf@ietf.org>
X-Mao-Original-Outgoing-Id: 551951185.211748-cbebd72507196784298295bfdb711868
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6BE7B96-0DC5-44E6-8A59-68A5B8DE274B@tzi.org>
References: <48161AFC-484C-4803-AFFF-4E9C0369A008@gmail.com> <20180321082546.pbsja53shgwlu6gv@elstar.local> <CABCOCHTZo-2=NSoHV+xNcmsOR1Ch+e-26pFz=oyMmGTS4C5QYw@mail.gmail.com> <E7646ADC-1F35-4CD9-8D32-E543AD5FCFE0@gmail.com> <CABCOCHQUDEiNAEj-NfBbpu8_RHuLk6U0HUNVFsTpHXBTuaDrgg@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/59RtdoGwz5zOBNQiVHjMm0znzNo>
Subject: Re: [Netconf] Issue #2 for binary encoding: Should the new encoding include the Message layer?
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, 29 Jun 2018 07:46:37 -0000

In Jun 26, 2018, at 03:46, Andy Bierman <andy@yumaworks.com> wrote:
> 
> CBOR does not support metadata at all.

I’m trying to follow this discussion, but I can’t process this sentence.

What is “metadata” here?  Or, maybe, what is “support”?
(You certainly can encode any kind of metadata in CBOR.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email