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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Fri, 29 June 2018 08:16 UTC

Return-Path: <j.schoenwaelder@jacobs-university.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 3D8E2130E79; Fri, 29 Jun 2018 01:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 hnx6bHTKjSC1; Fri, 29 Jun 2018 01:16:18 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8F8130EAB; Fri, 29 Jun 2018 01:16:18 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 5E72822B9048; Fri, 29 Jun 2018 10:16:17 +0200 (CEST)
Date: Fri, 29 Jun 2018 10:16:17 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: Andy Bierman <andy@yumaworks.com>, draft-mahesh-netconf-binary-encoding@ietf.org, Netconf <netconf@ietf.org>
Message-ID: <20180629081617.tm6yjszyiyaje4wg@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Carsten Bormann <cabo@tzi.org>, Andy Bierman <andy@yumaworks.com>, draft-mahesh-netconf-binary-encoding@ietf.org, Netconf <netconf@ietf.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> <A6BE7B96-0DC5-44E6-8A59-68A5B8DE274B@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A6BE7B96-0DC5-44E6-8A59-68A5B8DE274B@tzi.org>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/G4ObimUv7AuHWblVXr_rRoHzI-8>
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 08:16:30 -0000

On Fri, Jun 29, 2018 at 09:46:27AM +0200, Carsten Bormann wrote:
> 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.)
>

Carsten,

YANG definitions translate to values of XML elements. We in addition
use XML attributes to carry metadata, for example following RFC 7952.
See section 5 of RFC 7952 for details how this works with the XML and
JSON encodings.

Note that what we call meanwhile metadata did exist before 7952 came
along: the NETCONF protocol operations use XML attributes to control
how the edit is carried out, see section 7.2 of RFC 6241. Hence, in
order to run NETCONF over a different encoding, we need a convention
to carry metadata along with the data.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>