Re: [core] Éric Vyncke's No Objection on draft-ietf-core-yang-cbor-16: (with COMMENT)

Carsten Bormann <cabo@tzi.org> Mon, 07 March 2022 22:44 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 336173A1189; Mon, 7 Mar 2022 14:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 RreXnyTSPmga; Mon, 7 Mar 2022 14:44:12 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62D43A1113; Mon, 7 Mar 2022 14:44:11 -0800 (PST)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KCD605lT9zDCdf; Mon, 7 Mar 2022 23:44:08 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <162625700369.11227.18056605126082947991@ietfa.amsl.com>
Date: Mon, 07 Mar 2022 23:44:08 +0100
Cc: The IESG <iesg@ietf.org>, draft-ietf-core-yang-cbor@ietf.org, core-chairs@ietf.org, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>, Marco Tiloca <marco.tiloca@ri.se>
X-Mao-Original-Outgoing-Id: 668385848.139425-8b1001c490edae73a09daef4c9655da7
Content-Transfer-Encoding: quoted-printable
Message-Id: <15D47BED-3340-43F3-B29E-A6E4B760ED4D@tzi.org>
References: <162625700369.11227.18056605126082947991@ietfa.amsl.com>
To: Éric Vyncke <evyncke@cisco.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ScaUSnSP7ZcFx7yByBrtuWwsles>
Subject: Re: [core] Éric Vyncke's No Objection on draft-ietf-core-yang-cbor-16: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2022 22:44:24 -0000

Hi Éric,

a little blast from the past, as we haven’t replied to all the COMMENTs yet:

> On 2021-07-14, at 12:03, Éric Vyncke via Datatracker <noreply@ietf.org> wrote:
> 
> Éric Vyncke has entered the following ballot position for
> draft-ietf-core-yang-cbor-16: No Objection
> […]
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thank you for the work put into this document.
> 
> Special thanks to Marco Tiloca for his shepherd's write-up, which contains a
> good summary of the WG consensus and the doc reviews.
> 
> Please find below 2 non-blocking COMMENT points.
> 
> I hope that this helps to improve the document,
> 
> Regards,
> 
> -éric
> 
> == COMMENTS ==
> 
> A generic comment about the operational issue of supporting TWO ways to encode
> a data node: either normal string or the SID. This means that either there is a
> 2-way negotiation mechanism or that all CORE nodes must support both encoding
> and have agreed on a common SID mappings. Section 7 only briefly touches this
> issue with "Content-Type" but not with "Accept".

Section 7 actually uses the term Content-Type as the combination of a media-type name and optional parameters, as it is used in RFC 9193-to-be (which is waiting for HTTP to be published).
So I don’t see a need to mention Accept here; readers versed in content-types (media types) should already see the connection.

> 
> -- Section 4.2.1 & 4.4.1 --
> BTW, I like the idea of encoding a container with sequential SID and the delta
> CBOR encoding ;-)

Thank you!

Grüße, Carsten