
From nobody Fri Apr  2 16:49:21 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE6A3A0E5D for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 16:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5MOfRD8FMDXh for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 16:49:18 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 132683A0E5C for <cbor@ietf.org>; Fri,  2 Apr 2021 16:49:17 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id nh5so1113097pjb.5 for <cbor@ietf.org>; Fri, 02 Apr 2021 16:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=dOUdoH9gVylWBnV4X3jcSdvCXSTsE3u7ushAZuq/0nk=; b=T0y4nRdfJAzpiNN2LQtxHkw7EZeYJB8pJ7OljBs1VOB6d+BGgBz90ED5JgQ2+UBM9U MFVmR34t8bsfQlIar2W44DSUeoQhV1IHc00iieTaLm4qO75iGU4MKojuQpSYKTjeSI2Z rxS77+5qo2SWtisIbJbbyCk3Ij0PnAZ+sv4NkA41529bHvlDDwtpH9OggmKg8PdP3l6y n26CY0RKJlOl36k0Ccl3ywDPmHeidoOZrB+g+b/NVRJUPtO2qEPSZ1g1Y8SS15diyIHV Baxe+lx2LCFpZa/9r/iyFqthwJzV2B/gmdsf8/RcnB6ZvlgQLDqypMhlt7KbcIC0BJ8S x4rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dOUdoH9gVylWBnV4X3jcSdvCXSTsE3u7ushAZuq/0nk=; b=JGJRxn2p1ILVpqPU/Z51ENQ2PESckMyzRsYkNwYn10yAuoHMAkj1WmsEgN/2ox/aFj jMGH+N4WlSbqDRymmU40XqnFToM4L4Nhzv7/CBGIXGTSOv89CJjSHsxyGdmqkwqU/ips rVSvHLfcBOgFuPs2Ov0WrMDpk9jbrNWiNzk2/30zIymOcOCNNE5dArNhwa1L+rsxglcm zUmrGbp1H6cUWbctWV0eaaXLmzW4ep1S34R8jHVf+jrQrHzdx3MydovbUsfYTAEhdyMr PX6tYSldrcT7vPFvOBZvx6tgJi6+x2IblNY00gj42ahFRQM3Y7JjJVQDjbrohZZwP5UM tIBQ==
X-Gm-Message-State: AOAM532cTM9Dgbg62GlB/o7Kr5f21EeTsXuKF56G5AfPmBOSq32Z7vSq tweLPePK6hlIQtkDaK5vIH3BizJcnbdltplM9/1zU5UCiXMDEg==
X-Google-Smtp-Source: ABdhPJwEVj0eHBLok4LJsLryRF4D8JT2VNQVlg4ca8PnWIN9ndHvKgwlu66mXkXL/M9jHrQw4KZ/ruPtsGf2fIo9uIQ=
X-Received: by 2002:a17:90a:5898:: with SMTP id j24mr15742576pji.110.1617407356368;  Fri, 02 Apr 2021 16:49:16 -0700 (PDT)
MIME-Version: 1.0
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Fri, 2 Apr 2021 20:49:05 -0300
Message-ID: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com>
To: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000eef87305bf05fedd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/pV9HEGZOQ4zvhEquv8NzLJLHBKU>
Subject: [Cbor] Paywalled IEEE standards referenced in draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2021 23:49:20 -0000

--000000000000eef87305bf05fedd
Content-Type: text/plain; charset="UTF-8"

The IETF draft for cbor tags 1001 thru 1003 reference the IEEE1588-2008
standard for the clock quality keys.

Are there no other public domain or open-source standards that would serve
the same purpose as IEEE1588-2008 for the clock quality keys? I ask that
without any expertise on the subject, but merely as a C++ CBOR library
implementer who wants to support these CBOR tags (they are better for
transmitting std::chrono::time_point values losslessly).

At the very least, can the descriptions be more explicit about the data
types needed for the clock quality keys? ClockClass and ClockAccuracy
specify "one-byte integer", but it's not clear if it's signed or unsigned.
Also, "octet" would be a better word than "byte", since there are
architectures (such as DSPs) where a byte is 16 bits.

The OffsetScaledLogVariance key does not mention the value's data type(s)
or its physical units.

My motivation is to create an intermediate extended_time struct in my C++
library that contains all the possible fields of a CBOR extended time. If
an application wants to deserialize it into a std::chrono::time_point, my
library would discard the clock quality stuff. If some sort of scientific
application really wants the clock quality information, then they just
deserialize into an extended_time destination object and my library copies
all the available information.

It would be preferable if the numeric clock quality fields in my
extended_time struct were of a known static type, such as a double. But
since I don't have access to IEEE1588, I don't know if double is of
sufficient accuracy. I would appreciate it if an expert could illuminate me
on the required numeric precision, or point me in the right direction for
my own research on the subject.

Cheers,
Emile Cormier

--000000000000eef87305bf05fedd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The IETF draft for cbor tags 1001 thru 1003 reference=
 the IEEE1588-2008 standard for the clock quality keys.</div><div><div clas=
s=3D"gmail-comment gmail-js-suggested-changes-container">
  <div class=3D"gmail-comment-body gmail-markdown-body gmail-js-preview-bod=
y" style=3D"min-height:396px"><p>Are
 there no other public domain or open-source standards that would serve=20
the same purpose as IEEE1588-2008 for the clock quality keys? I ask that
 without any expertise on the subject, but merely as a C++ CBOR library=20
implementer who wants to support these CBOR tags (they are better for=20
transmitting <code>std::chrono::time_point</code> values losslessly).</p>
<p>At the very least, can the descriptions be more explicit about the data =
types needed for the clock quality keys? <code>ClockClass</code> and <code>=
ClockAccuracy</code>
 specify &quot;one-byte integer&quot;, but it&#39;s not clear if it&#39;s s=
igned or=20
unsigned. Also, &quot;octet&quot; would be a better word than &quot;byte&qu=
ot;, since there=20
are architectures (such as DSPs) where a byte is 16 bits.</p>
<p>The <code>OffsetScaledLogVariance</code> key does not mention the value&=
#39;s data type(s) or its physical units.</p>
<p>My motivation is to create an intermediate <code>extended_time</code>
 struct in my C++ library that contains all the possible fields of a=20
CBOR extended time. If an application wants to deserialize it into a <code>=
std::chrono::time_point</code>,
 my library would discard the clock quality stuff. If some sort of=20
scientific application really wants the clock quality information, then=20
they just deserialize into an <code>extended_time</code> destination object=
 and my library copies all the available information.</p>
<p>It would be preferable if the numeric clock quality fields in my <code>e=
xtended_time</code> struct were of a known static type, such as a <code>dou=
ble</code>. But since I don&#39;t have access to IEEE1588, I don&#39;t know=
 if <code>double</code> is of sufficient accuracy. I would appreciate it if=
 an expert could illuminate me on the required numeric precision, or point =
me in the right direction for my own research on the subject.</p><p>Cheers,=
<br>Emile Cormier<br></p></div>
</div></div></div>

--000000000000eef87305bf05fedd--


From nobody Fri Apr  2 18:39:28 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F713A13F4 for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 18:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 RWs8UGPKAaXR for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 18:39:22 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 872123A13F1 for <cbor@ietf.org>; Fri,  2 Apr 2021 18:39:22 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id x26so4596498pfn.0 for <cbor@ietf.org>; Fri, 02 Apr 2021 18:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=bx6rRaZuuzo6I57O9UhWRzk3WIQBpbiXHQKBP3Oigvo=; b=S9fsymS3mxvrMyt3WpRbUWkr/HzdGspM8yaoTq2QTHVXXbc3Lj6lgWTXEkPtDvjzJx Tfrjyeum4FgxsLLPpODOZTrAvBxAuay6nu6OODduO0rrIZ9my/2KswNMFCCr0mNGgLji AxZj7loAznqrKb+7sCD5BdndEyLS303tRPizBLp+HDw05HqUh7QjdI7oe3AYhC5hfVon eXKvuV+TIXaHL1+r8sS/ZTgrNtQJAqT/vFidCNVF+1/ywulBN5/sVRdrFWRtnuiNnV5+ R6POsea8QqCOLR9b5KchtC+MJ6KgD9AVZwvep6yiQ4CDJQEFEik4mP6RKQpEgc+T4F0f yOPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bx6rRaZuuzo6I57O9UhWRzk3WIQBpbiXHQKBP3Oigvo=; b=VeGRqoZ1CrHh5t7avBQJKBOc4OVgFULOsBGJsWlfKzRbNKGctSCXzi0MwX7/M7GedD EI4louNlBMH6cTpb47DIfCeZL7g8HRU5FU6ZBKBeQlNi9FBHjfSU1UwpRorgjncfcqGw 59bMPdKyb1ZTOztOx/qdJQoz5u/WrxCCORMttJI8K9Lnedhel+sM38Dvw6tgGyDmbNGz xJrxJlsL+XRgYek/n/gSirm1AERx0R0aClfG1AgHd4EA6bux97+iiqEH3gABwvsHSobz DQj40UaOEvXXSJpCiGJtDJz2g5FUO6iDbyOnGAtLdPLtj9UW/V0DFS9KsHDA9jWT0gt3 NR7g==
X-Gm-Message-State: AOAM530WjLI8NrfO7rh1ktQ5MpWG5vs/LtrTG6EofwuhFaVpc0vn/pMK xnSWMO0T/aqS3KqcoYWzhuraZb2xWR297GmC0YVDgXU0KyraPA==
X-Google-Smtp-Source: ABdhPJz2U0AjkBz+FEqc7czdySshYKHjyUctla0uooOJaY0ciQxI/9nqekmnHM42vm3GboGBY0RWqQBWQ5wkEyH+AE4=
X-Received: by 2002:a63:fa41:: with SMTP id g1mr5560584pgk.143.1617413961494;  Fri, 02 Apr 2021 18:39:21 -0700 (PDT)
MIME-Version: 1.0
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Fri, 2 Apr 2021 22:39:10 -0300
Message-ID: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com>
To: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a1366105bf078861"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/PgsVIL__QNDIxyJ7YuOqmtm19IY>
Subject: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 01:39:27 -0000

--000000000000a1366105bf078861
Content-Type: text/plain; charset="UTF-8"

I'd like to be able to encode any arbitrary C++ std::chrono::time_point (
https://en.cppreference.com/w/cpp/chrono/time_point) into CBOR in a
lossless manner. A C++ time_point basically contains three values: a
numerator and denominator to express a ratio in seconds, plus a multiplier
(aka "count"). For example, to store the number of weeks since the epoch,
one could use:

using weeks = std::period<uint64_t, std::ratio<604800, 1>>;
std::chrono::time_point<std::chrono::system_time, weeks> when(123);

In order words, 123 * (604800 / 1) seconds.

I could of course convert 123 weeks to seconds before encoding to CBOR, but
for large numbers of weeks, I would risk arithmetic overflow.

std::ratio<604800, 1> in my example is a compile-time constant, but it
would have to be encoded as a run-time pair of integers over CBOR. Note
that the ratio is arbitrary in C++. Nothing prevents a C++ programmer from
storing a "micro-fortnite" as a std::ratio<14*86400, 1000000>.

To allow the encoding any arbitrary time ratios, I propose a new CBOR tag
wrapping an array of 1 to 3 values:

[Count, Numerator, Denominator]

where Count is an integral or floating point number, and Numerator and
Denominator are integers representing the ratio in seconds.The Numerator
and Denominator would default to 1 if absent.

CBOR tags 1001-1003 would be extended to allow this new CBOR tag as the
value key. This would allow me to encode additional metadata on the
std::chrono::time_point clock type (POSIX, UTC, TAI, GPS).

I can write-up a draft proposal for this new tag on my Github, but I'd like
to hear your thoughts first.

Cheers,
Emile Cormier

--000000000000a1366105bf078861
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;d like to be able to encode any arbitrary C++ s=
td::chrono::time_point (<a href=3D"https://en.cppreference.com/w/cpp/chrono=
/time_point">https://en.cppreference.com/w/cpp/chrono/time_point</a>) into =
CBOR in a lossless manner. A C++ time_point basically contains three values=
: a numerator and denominator to express a ratio in seconds, plus a multipl=
ier (aka &quot;count&quot;). For example, to store the number of weeks sinc=
e the epoch, one could use:<br><br></div><div>using weeks =3D std::period&l=
t;uint64_t, std::ratio&lt;604800<span class=3D"gmail-t-c"><span class=3D"gm=
ail-mw-geshi gmail-cpp gmail-source-cpp"><span class=3D"gmail-nu0"></span><=
span class=3D"gmail-sy1">, 1</span></span></span>&gt;&gt;;<br>std::chrono::=
time_point&lt;std::chrono::system_time, weeks&gt; when(123);<br><br></div><=
div>In order words, 123 * (604800 / 1) seconds.</div><div><br></div><div>I =
could of course convert 123 weeks to seconds before encoding to CBOR, but f=
or large numbers of weeks, I would risk arithmetic overflow.</div><div><br>=
</div><div>std::ratio&lt;604800<span class=3D"gmail-t-c"><span class=3D"gma=
il-mw-geshi gmail-cpp gmail-source-cpp"><span class=3D"gmail-sy1">, 1</span=
></span></span>&gt; in my example is a compile-time constant, but it would =
have to be encoded as a run-time pair of integers over CBOR. Note that the =
ratio is arbitrary in C++. Nothing prevents a C++ programmer from storing a=
 &quot;micro-fortnite&quot; as a std::ratio&lt;14*86400, 1000000&gt;.</div>=
<div><br></div><div>To allow the encoding any arbitrary time ratios, I prop=
ose a new CBOR tag wrapping an array of 1 to 3 values:<br></div><div><br></=
div><div>[Count, Numerator, Denominator]<br></div><div><br></div><div>where=
 Count is an integral or floating point number, and Numerator and Denominat=
or are integers representing the ratio in seconds.The Numerator and Denomin=
ator would default to 1 if absent.<br><br></div><div>CBOR tags 1001-1003 wo=
uld be extended to allow this new CBOR tag as the value key. This would all=
ow me to encode additional metadata on the std::chrono::time_point clock ty=
pe (POSIX, UTC, TAI, GPS).<br><br></div><div>I can write-up a draft proposa=
l for this new tag on my Github, but I&#39;d like to hear your thoughts fir=
st.</div><div><br></div><div>Cheers,</div><div>Emile Cormier<br></div></div=
>

--000000000000a1366105bf078861--


From nobody Fri Apr  2 19:00:37 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E64C3A14DA for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 19:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dMxQkjLELQt3 for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 19:00:31 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 690633A14D4 for <cbor@ietf.org>; Fri,  2 Apr 2021 19:00:31 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id a22-20020a17090aa516b02900c1215e9b33so5296043pjq.5 for <cbor@ietf.org>; Fri, 02 Apr 2021 19:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=hAIhaN3wF9HBkMw96KNISbhRnfGpZqksWMxXTnUhjSw=; b=d6keGUNynwa3A4Hh4A6uQno3EAYydqkHE9Ih28RZEYOFtjQ5RXOEdpBicPiH5rT4F+ lKJ4OamcPNMqBQFTHiEFT8WYzAE+3bRt3C3wPYlKfxKZdap0XMYvI/Fn+urzkuYEWnND gq3y/kQ+wwKdMHwTIW4DTCE847tPNlWQ+IofY/U8CpAGXP1ZU5L1gVxr6b/UVVhFG3A7 LzN+8UENJFsFhkQEXvmIUpUy5xrk9mbOivyueEnUBx1MNV9zSJCiAL8cxEwLMYMrqFhx uQwE9c1HjaRcpFM5VJuUF0cb3/wCFI+5lljb3W9+l9eEf1seTazQq4PY51hnjaJY7Nu3 O7Aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hAIhaN3wF9HBkMw96KNISbhRnfGpZqksWMxXTnUhjSw=; b=rHooCK7jjuWke0lHXWnp9A51zaq4NUh+shm0ff4Y813d7JSVhoX7ogRQyTMmxEzArX E250YnSv9V/NBf6OP2Nhk+AqtnQKdHToER5jPj30xk6+aF9zNUVbWcHvsrC5m3L6IJCt K6cOXzvLkjZsK/BxNJjDp5cUucK23dE3CQ8xyg2mTgQPxLIUG58U9/dNogapuvvwSKIw eNyHOdKnXUEmJBcD3EkS387e1KJKmG7XUoH9CUMAl/a4F3wHE9igsyu4Rrxs/K+8LIjz Jxd42Xk3ghoWYvnqdXhbppZAUby+al4+KbADlxgB19dkTJHSXQPNhFOzzr4OSVcQ29G/ R81Q==
X-Gm-Message-State: AOAM530+SB198OjFAFB+b5pTgr8NC8aCjapRRCn/4tQXNLht6gVCkFzZ zt40SdYXJhbZ5A9+g1L6z8VPuh9InrI/SXYP7n2sdxG42EK4jA==
X-Google-Smtp-Source: ABdhPJwY2kOPmlD6LIsulnVniii6ktlRMhqxnSW4JfMCaVH9j6S8WxWUKRv9GXps0568YTyg+Y/4Cq7PuXyO6cJ3ksU=
X-Received: by 2002:a17:90b:16cd:: with SMTP id iy13mr16708428pjb.46.1617415229756;  Fri, 02 Apr 2021 19:00:29 -0700 (PDT)
MIME-Version: 1.0
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Fri, 2 Apr 2021 23:00:19 -0300
Message-ID: <CAM70yxBO8Rr4Fd2GBD4-K=8DY7oCefYLL=61_piLwJ8Wj=Dxww@mail.gmail.com>
To: cbor@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003957d405bf07d47a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1dHOOsJgv_7lDyU8hOBEtsUMjTQ>
Subject: [Cbor] draft-bormann-cbor-time-tag: POSIX and UTC are not the same
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 02:00:36 -0000

--0000000000003957d405bf07d47a
Content-Type: text/plain; charset="UTF-8"

In draft-bormann-cbor-time-tag (tags 1001-1003), UTC and POSIX are
confounded together under the same value of 0, under section 3.4. Key -1:
Time Scale.

UTC and POSIX are not the same! Per https://en.wikipedia.org/wiki/Unix_time:

... leap seconds are ignored, with a leap second having the same Unix time
> as the second before it, and every day is treated as if it contains exactly
> 86400 seconds. Due to this treatment Unix time is not a true representation
> of UTC.
>

This is reinforced by the fact that C++ has distinct clocks for system time
and UTC:

https://en.cppreference.com/w/cpp/chrono/system_clock
https://en.cppreference.com/w/cpp/chrono/utc_clock

There should therefore be distinct values for POSIX and UTC.

Cheers,
Emile Cormier

--0000000000003957d405bf07d47a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>In draft-bormann-cbor-time-tag (tags 1001-1003), UTC =
and POSIX are confounded together under the same value of 0, under section =
3.4. Key -1: Time Scale.</div><div><br></div><div>UTC and POSIX are not the=
 same! Per <a href=3D"https://en.wikipedia.org/wiki/Unix_time">https://en.w=
ikipedia.org/wiki/Unix_time</a>:</div><div><br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div>... leap seconds are ignored, with a leap =
second having the same Unix time as the second before it, and every day is =
treated as if it contains exactly 86400 seconds. Due to this treatment Unix=
 time is not a true representation of UTC.</div></blockquote><div><br></div=
><div>This is reinforced by the fact that C++ has distinct clocks for syste=
m time and UTC:</div><div><br></div><div><a href=3D"https://en.cppreference=
.com/w/cpp/chrono/system_clock">https://en.cppreference.com/w/cpp/chrono/sy=
stem_clock</a></div><div><a href=3D"https://en.cppreference.com/w/cpp/chron=
o/utc_clock">https://en.cppreference.com/w/cpp/chrono/utc_clock</a></div><d=
iv><br></div><div>There should therefore be distinct values for POSIX and U=
TC.<br></div><div><br></div><div>Cheers,</div><div>Emile Cormier<br> </div>=
</div>

--0000000000003957d405bf07d47a--


From nobody Fri Apr  2 23:21:27 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57CB3A089A for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 23:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 3dIXBmNUXl-Q for <cbor@ietfa.amsl.com>; Fri,  2 Apr 2021 23:21:22 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC86A3A0898 for <cbor@ietf.org>; Fri,  2 Apr 2021 23:21:22 -0700 (PDT)
Received: from [192.168.217.152] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FC6J00WcBzydl; Sat,  3 Apr 2021 08:21:20 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com>
Date: Sat, 3 Apr 2021 08:21:19 +0200
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A293EEDA-CD66-4BE8-B2EC-0B5CCA65948A@tzi.org>
References: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/udhHEJ_tY9kl_gXQQttLbk5skk4>
Subject: [Cbor] Octets (was: Re: Paywalled IEEE standards referenced in draft-bormann-cbor-time-tag)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 06:21:26 -0000

Hi Emile,

I=E2=80=99ll get to your very useful input later, as it requires some =
study, but I can react to this editorial one now:

> On 3. Apr 2021, at 01:49, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
> Also, "octet" would be a better word than "byte", since there are =
architectures (such as DSPs) where a byte is 16 bits.

Actually, no. =20
The term =E2=80=9Coctet=E2=80=9D stopped to be useful approximately =
1983, when the last architectures that had non-8-bit bytes ran out of =
steam.

Its continued usage over the decades is a symptom of a stilted style =
that values the superficial appearance of precision over the usefulness =
of the resulting documents.
It may be a small instance of the many symptoms of this kind in =
standards documents, but it is worth stamping out with a vengeance.

(Note that this is about the English language =E2=80=94 octet of course =
is the right word in French and other languages.)

If a technical document today uses the term =E2=80=9Cbyte=E2=80=9D for =
something else than 8 bits, somebody is trying to appear very smart by =
regressing to the time when that actually still was an option.  =
Technical documentation should never be made misleading just to appear =
that kind of smart.  I actually haven=E2=80=99t run into misuse of the =
term =E2=80=9Cbyte=E2=80=9D for a long, long time =E2=80=94 can you =
point to an example from this century?

Oh, and to get rid of the residual argument that =E2=80=9Cbyte=E2=80=9D =
might be perceived to be less accurate: since RFC 7049, many =
documents=E2=80=99 terminology sections include the sentence:

   The term "byte" is used in its now-customary sense as a synonym for
   "octet".

Just checked the time-tag document:=20
It does so explicitly as well (many other documents just include the =
terminology of RFC 7049/8949 and so do that only implicitly).

But now back to your excellent technical input...

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sat Apr  3 00:11:21 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B293A0FF1 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 00:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 XJxTh9t5Nis0 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 00:11:16 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F763A0FEF for <cbor@ietf.org>; Sat,  3 Apr 2021 00:11:16 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FC7PZ19fSzyPY; Sat,  3 Apr 2021 09:11:14 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com>
Date: Sat, 3 Apr 2021 09:11:13 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 639126673.3501281-f4f5e493810fdd372949b644777715f2
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFCD8747-717A-47CA-851A-E803163E782C@tzi.org>
References: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/N6tZUVrrLUrwzBS-Nj-JJowiX9s>
Subject: Re: [Cbor] Paywalled IEEE standards referenced in draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 07:11:20 -0000

On 2021-04-03, at 01:49, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
> The IETF draft for cbor tags 1001 thru 1003 reference the =
IEEE1588-2008 standard for the clock quality keys.
> Are there no other public domain or open-source standards that would =
serve the same purpose as IEEE1588-2008 for the clock quality keys?

I=E2=80=99m not aware of any other places where this material has been =
written up (note that RFC 8575 also simply references IEEE1588).

> I ask that without any expertise on the subject, but merely as a C++ =
CBOR library implementer who wants to support these CBOR tags (they are =
better for transmitting std::chrono::time_point values losslessly).
>=20
> At the very least, can the descriptions be more explicit about the =
data types needed for the clock quality keys? ClockClass and =
ClockAccuracy specify "one-byte integer", but it's not clear if it's =
signed or unsigned.

Well, it is clear from the CDDL above, but I have fixed the textual =
description of the rationale to include =E2=80=9Cunsigned=E2=80=9D in =
the editor copy [1].

[1]: https://github.com/cbor-wg/time-tag/commit/8ce40c3

> Also, "octet" would be a better word than "byte", since there are =
architectures (such as DSPs) where a byte is 16 bits.

(See previous mail.)

> The OffsetScaledLogVariance key does not mention the value's data =
type(s) or its physical units.

That is because it is really weird, and you won=E2=80=99t be able to =
make heads or tails of it unless you read IEEE1588.  Maybe we can have a =
summary of it in the next version, but rephrasing all the details =
won=E2=80=99t work.

> My motivation is to create an intermediate extended_time struct in my =
C++ library that contains all the possible fields of a CBOR extended =
time. If an application wants to deserialize it into a =
std::chrono::time_point, my library would discard the clock quality =
stuff. If some sort of scientific application really wants the clock =
quality information, then they just deserialize into an extended_time =
destination object and my library copies all the available information.
>=20
> It would be preferable if the numeric clock quality fields in my =
extended_time struct were of a known static type, such as a double. But =
since I don't have access to IEEE1588, I don't know if double is of =
sufficient accuracy. I would appreciate it if an expert could illuminate =
me on the required numeric precision, or point me in the right direction =
for my own research on the subject.

If you are talking about uncertainty (-7) and guarantee (-8), it is =
unclear to me what your precision requirements would be.  If the =
uncertainty is 1e-8 s, you could represent this in a double, but there =
of course is no exact representation of 1e-8 in IEEE 754 binary floating =
point.  The uncertainty of the uncertainty is going to be large enough =
that this is entirely inconsequential.  (The range of double is =
definitely sufficient.)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sat Apr  3 00:34:20 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5263A1125 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 00:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 eHiT7uEW0PvA for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 00:34:14 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29D6F3A1123 for <cbor@ietf.org>; Sat,  3 Apr 2021 00:34:14 -0700 (PDT)
Received: from [192.168.217.152] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FC7w42XF6zyPY; Sat,  3 Apr 2021 09:34:12 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_076C62BD-F6E1-40F7-8341-AD9BBA51E324"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxBO8Rr4Fd2GBD4-K=8DY7oCefYLL=61_piLwJ8Wj=Dxww@mail.gmail.com>
Date: Sat, 3 Apr 2021 09:34:11 +0200
Cc: cbor@ietf.org
Message-Id: <DDDC5DCF-A757-43BB-BD0C-E38617320601@tzi.org>
References: <CAM70yxBO8Rr4Fd2GBD4-K=8DY7oCefYLL=61_piLwJ8Wj=Dxww@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/tKxzQqpbHbEJjOunT8YHr_Q90yg>
Subject: Re: [Cbor] draft-bormann-cbor-time-tag: POSIX and UTC are not the same
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 07:34:19 -0000

--Apple-Mail=_076C62BD-F6E1-40F7-8341-AD9BBA51E324
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On 3. Apr 2021, at 04:00, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
> In draft-bormann-cbor-time-tag (tags 1001-1003), UTC and POSIX are =
confounded together under the same value of 0, under section 3.4. Key =
-1: Time Scale.
>=20
> UTC and POSIX are not the same! Per =
https://en.wikipedia.org/wiki/Unix_time =
<https://en.wikipedia.org/wiki/Unix_time>:
>=20
> ... leap seconds are ignored, with a leap second having the same Unix =
time as the second before it, and every day is treated as if it contains =
exactly 86400 seconds. Due to this treatment Unix time is not a true =
representation of UTC.

Well, that text is slightly confused, as it is a true representation of =
UTC, except it can=E2=80=99t represent the 27 leap seconds we have had =
so far or any of the future ones.

> This is reinforced by the fact that C++ has distinct clocks for system =
time and UTC:
>=20
> https://en.cppreference.com/w/cpp/chrono/system_clock =
<https://en.cppreference.com/w/cpp/chrono/system_clock>
> https://en.cppreference.com/w/cpp/chrono/utc_clock =
<https://en.cppreference.com/w/cpp/chrono/utc_clock>
>=20
> There should therefore be distinct values for POSIX and UTC.

POSIX and UTC (and thus NTP) are shifted by leap seconds (which is =
sometimes called =E2=80=9Cignoring leap seconds=E2=80=9D, a term that =
should never be used; cppreference says =E2=80=9Cnot counting leap =
seconds=E2=80=9D, which means that you have to be aware of leap seconds =
to actively not count them).

TAI, GPS are true monotonic time scales.  Leap seconds have no influence =
on them (what cppreference calls =E2=80=9Cincluding leap seconds=E2=80=9D)=
.
As C++ utc_clock "includes leap seconds=E2=80=9D, it appears to be a TAI =
referenced time scale (with a constant offset of 10 seconds from TAI).

I=E2=80=99m sorry, I didn=E2=80=99t invent this, I=E2=80=99m just the =
messenger :-)

Maybe adding an appendix on platform time representations would be worth =
it=E2=80=A6
(We could also add more lines to figure 1, pointing out that C++ =
utc_clock is TAI minus 10 seconds.)

Gr=C3=BC=C3=9Fe, Carsten


--Apple-Mail=_076C62BD-F6E1-40F7-8341-AD9BBA51E324
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
3. Apr 2021, at 04:00, Emile Cormier &lt;<a =
href=3D"mailto:emile.cormier.jr@gmail.com" =
class=3D"">emile.cormier.jr@gmail.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"">In draft-bormann-cbor-time-tag (tags =
1001-1003), UTC and POSIX are confounded together under the same value =
of 0, under section 3.4. Key -1: Time Scale.</div><div class=3D""><br =
class=3D""></div><div class=3D"">UTC and POSIX are not the same! Per <a =
href=3D"https://en.wikipedia.org/wiki/Unix_time" =
class=3D"">https://en.wikipedia.org/wiki/Unix_time</a>:</div><div =
class=3D""><br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div class=3D"">... leap seconds are =
ignored, with a leap second having the same Unix time as the second =
before it, and every day is treated as if it contains exactly 86400 =
seconds. Due to this treatment Unix time is not a true representation of =
UTC.</div></blockquote></div></div></blockquote><div><br =
class=3D""></div>Well, that text is slightly confused, as it is a true =
representation of UTC, except it can=E2=80=99t represent the 27 leap =
seconds we have had so far or any of the future ones.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">This is reinforced by the fact =
that C++ has distinct clocks for system time and UTC:</div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://en.cppreference.com/w/cpp/chrono/system_clock" =
class=3D"">https://en.cppreference.com/w/cpp/chrono/system_clock</a></div>=
<div class=3D""><a =
href=3D"https://en.cppreference.com/w/cpp/chrono/utc_clock" =
class=3D"">https://en.cppreference.com/w/cpp/chrono/utc_clock</a></div><di=
v class=3D""><br class=3D""></div><div class=3D"">There should therefore =
be distinct values for POSIX and UTC.</div></div></div></blockquote><br =
class=3D""></div><div>POSIX and UTC (and thus NTP) are shifted by leap =
seconds (which is sometimes called =E2=80=9Cignoring leap seconds=E2=80=9D=
, a term that should never be used; cppreference says =E2=80=9Cnot =
counting leap seconds=E2=80=9D, which means that you have to be aware of =
leap seconds to actively not count them).</div><div><br =
class=3D""></div><div>TAI, GPS are true monotonic time scales. =
&nbsp;Leap seconds have no influence on them =
(what&nbsp;cppreference&nbsp;calls =E2=80=9Cincluding leap =
seconds=E2=80=9D).</div><div>As C++ utc_clock "includes leap seconds=E2=80=
=9D, it appears to be a TAI referenced time scale (with a constant =
offset of 10 seconds from TAI).</div><div><br class=3D""></div><div>I=E2=80=
=99m sorry, I didn=E2=80=99t invent this, I=E2=80=99m just the messenger =
:-)</div><div><br class=3D""></div><div>Maybe adding an appendix on =
platform time representations would be worth it=E2=80=A6</div><div>(We =
could also add more lines to figure 1, pointing out that C++ utc_clock =
is TAI minus 10 seconds.)</div><div><br =
class=3D""></div><div><div>Gr=C3=BC=C3=9Fe, Carsten</div><div =
class=3D""><br class=3D""></div></div></body></html>=

--Apple-Mail=_076C62BD-F6E1-40F7-8341-AD9BBA51E324--


From nobody Sat Apr  3 01:03:39 2021
Return-Path: <henk.birkholz@sit.fraunhofer.de>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26733A1252 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 01:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fraunhofer.onmicrosoft.com
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 vGCKWwBVYaoA for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 01:03:33 -0700 (PDT)
Received: from mail-edgeDD24.fraunhofer.de (mail-edgeDD24.fraunhofer.de [192.102.167.24]) (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 62CE03A124E for <cbor@ietf.org>; Sat,  3 Apr 2021 01:03:30 -0700 (PDT)
IronPort-PHdr: =?us-ascii?q?9a23=3A2qRs3B/HsggaL/9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+7ZhSN5PhxghnOR4qIo/5Hiu+DtafmVCRA5Juaq3kNfdRKUA?= =?us-ascii?q?NNksQZmQEsQavnQU32JfLndWo2ScJFUlI2/nynPw5SAsmtL1HXq2e5uDgVHB?= =?us-ascii?q?i3PAFpJ+PzT4jVicn/1+2795DJJQtSgz/oerJuahuspBjXts4YjJEkJqtixw?= =?us-ascii?q?=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FvBwBkpYde/xoBYJlmHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgWoEAQELAYFTUAVsA1UdPAqEEYNGAQGFOYdcCCWJbo4wglIDSgo?= =?us-ascii?q?KAQEBAQEBAQEBBgEBGAsKAgQBAYNEgQACNYISJDcGDgIQAQEGAQEBAQEFBAI?= =?us-ascii?q?CaYVWDIZGAQEBAwEBEBEPAQUIAQEsCwEPCQIOCgICIwMCAiEGCxQRBgEMAQU?= =?us-ascii?q?CAQEegwQBgksDLQIDC5M/kGcCgTmIYnWBMoJ/AQEFgkWCeA0LV4E1AwYJAYE?= =?us-ascii?q?EKgGMMA+BTD+BEScMA4JaPoIeSQEBA4R0gl6wT0cHgUl3fASGb4p7hDUjjzU?= =?us-ascii?q?FjEaLO4N3iSOCPJA+AgQCBAUCDgEBBYFoJIFXTSRPgmlQGA2OHYNzhRSFQ3I?= =?us-ascii?q?CgSeNGQGBDwEB?=
X-IPAS-Result: =?us-ascii?q?A2FvBwBkpYde/xoBYJlmHAEBAQEBBwEBEQEEBAEBgWoEA?= =?us-ascii?q?QELAYFTUAVsA1UdPAqEEYNGAQGFOYdcCCWJbo4wglIDSgoKAQEBAQEBAQEBB?= =?us-ascii?q?gEBGAsKAgQBAYNEgQACNYISJDcGDgIQAQEGAQEBAQEFBAICaYVWDIZGAQEBA?= =?us-ascii?q?wEBEBEPAQUIAQEsCwEPCQIOCgICIwMCAiEGCxQRBgEMAQUCAQEegwQBgksDL?= =?us-ascii?q?QIDC5M/kGcCgTmIYnWBMoJ/AQEFgkWCeA0LV4E1AwYJAYEEKgGMMA+BTD+BE?= =?us-ascii?q?ScMA4JaPoIeSQEBA4R0gl6wT0cHgUl3fASGb4p7hDUjjzUFjEaLO4N3iSOCP?= =?us-ascii?q?JA+AgQCBAUCDgEBBYFoJIFXTSRPgmlQGA2OHYNzhRSFQ3ICgSeNGQGBDwEB?=
X-URL-LookUp-ScanningError: 1
X-IronPort-AV: E=Sophos;i="5.72,341,1580770800"; d="scan'208";a="41511344"
Received: from mail-mtaka26.fraunhofer.de ([153.96.1.26]) by mail-edgeDD24.fraunhofer.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Apr 2021 10:03:27 +0200
IronPort-PHdr: =?us-ascii?q?A9a23=3ABbIv3RdD3JRZOp9tMNSnoRZclGM/S4qcDmYuw?= =?us-ascii?q?pM6l7JDdLii9J3+PUvZoO9gl0LNQZ6zw/NJl+SQtLrvCiQM4peE5XYFdpEEF?= =?us-ascii?q?xoIkt4fkAFoBsmZQVb6I/jnY21ffoxCWVZp8mv9PR1TH8DzNFzfvnP06iQdS?= =?us-ascii?q?V3zMANvLbHzHYjfx828y+G1/cjVZANFzDqwaL9/NlO4twLU49IXnc1sMK8sz?= =?us-ascii?q?BvOrHZSPehblgtV?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3ALNXpHazPQLpQImNdlBjWKrPw5b1zdoIgy1?= =?us-ascii?q?knxilNYDZSddGVkN3roe8S0gX6hC1UdHYrn92BP6foewK+ybde544NMbC+GD?= =?us-ascii?q?T3oWfAFuFfxKbr3jGIIUfD38FH06MIScVDIfnRKXQ/ssrg+gm/FL8boeWv1K?= =?us-ascii?q?yzn+/RwzNMYGhRBJ1I1AtyBgaFHkAefmAvbqYRLoaW5cZMulObF0g/U8LTPB?= =?us-ascii?q?U4Y9Q=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAQAlIGhg/z6wYZlaGgEBAQEBAQE?= =?us-ascii?q?BAQEDAQEBARIBAQEBAgIBAQEBQAmBOAIBAQEBCwGBUlEHTCtaZwqEOINJAQG?= =?us-ascii?q?FOYgeCCg5AYlyjwuCUwNUCwEDAQEBAQEHAQEdCwoCBAEBg1F/AjWBRgImNwY?= =?us-ascii?q?OAhEBAQUBAQECAQYEcROFUA2GRQEBAQMBASEPAQUIAQEUGAsBDwkCDgoCAiM?= =?us-ascii?q?DAgIhBgsHDREGAQwBBQIBAYJtAYJVAy4CAwuPMpBtAoofd4EygQGCBAEBBoJ?= =?us-ascii?q?Mgk8NC1iBOwMGCQGBBSoBgnWFHIFGg3I2gVVCgRInDAOCZj6CHkIBAQOEcoJ?= =?us-ascii?q?ggy4EQxBbELtxLywHgXKBG4EeBQuIMY1ehSsFCh+UJAaQQyuPUIUXi2iDFpQ?= =?us-ascii?q?jAgQCBAUCDgEBBoFqJIFZTSRPgmlQFwIOjh+DcIUUhUdxAjYCBgEJAQEDCXy?= =?us-ascii?q?MMwGBDgEB?=
X-IronPort-AV: E=Sophos;i="5.81,302,1610406000"; d="scan'208";a="110098864"
Received: from 153-97-176-62.vm.c.fraunhofer.de (HELO XCH-HYBRID-02.ads.fraunhofer.de) ([153.97.176.62]) by mail-mtaKA26.fraunhofer.de with ESMTP; 03 Apr 2021 10:03:24 +0200
Received: from XCH-HYBRID-02.ads.fraunhofer.de (10.225.8.59) by XCH-HYBRID-02.ads.fraunhofer.de (10.225.8.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.721.2;  Sat, 3 Apr 2021 10:03:23 +0200
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (10.225.8.41) by XCH-HYBRID-02.ads.fraunhofer.de (10.225.8.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.721.2 via Frontend Transport; Sat, 3 Apr 2021 10:03:23 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MpheabqxaKT1LsUOzk8zbDZxlCteaGhLgjG6wwTtPVWCgwX8MDXSjRjUYrARXuqk3illBpeQVpZrQDdniYX6K5cje/OUjBQdNl1y0AXIZCXzXrB7cc21p1yVEM6apOnaMR7a6DcDoYuYikcWErbiX6hO7XAAdkglTMO31H6IvbA23+kEbUIHLY4WChG7+fVdb+322ik4rE14GrT+PdhY2ABx0+aKXdR+IjiCfuzaLLR7sIKjN7Vlz36DinUMefyaj40B+TBfrfA4Zb6KqBDekwKcxYURaZnj/pHlJWIG9Tk6Etho+mfsngmmjxxMhOs16zwi8OKwfTocYLO8v12/gw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4jhG3VYC0BFEo4f2yvOb9bQzRpXEK+f9gwGO3esCd8o=; b=ZgigYFGgJ40mcb/UD1Gf04rGbUrPAFMZOpOJTtp+doXl3geQ9x5z0mt7l22zJySjGgUiowixQU4jbbF/WoSYO58jGFveH90Xz3jp3sTjEXGlbB5bqJRJgAJ+AGylsPZ+Sxlx4u58Ure3CQfsdsjOzFWLRnDxKj1Ph/oXT0TM15NUQtCy5NWZvp+KpS4A24ha7NSDFUAxU1tT8UsxRT/Lrv4+yj7nZ07BF4AXTs6OqNccpjr6ZM0DMpdC4f1xfmqPtTrXxcXLR93mZ5uCbtw/qxiwiDzarpSalLxsnCC0Fx7UPEgQwxXSx7i470/BxGdbgrAj6RdyC9zk3TBHx4HDXw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sit.fraunhofer.de; dmarc=pass action=none header.from=sit.fraunhofer.de; dkim=pass header.d=sit.fraunhofer.de; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fraunhofer.onmicrosoft.com; s=selector2-fraunhofer-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4jhG3VYC0BFEo4f2yvOb9bQzRpXEK+f9gwGO3esCd8o=; b=RDXhXWpjlv+eAzgsj6i1p8W11Pf5WFsCU0IUV9HuXIGDRoaPNentiieTt3J0jucekVWIVzSDXMzE3IcwuO41tkPHx15leJiERZhZLF0PeRQvZ8Fu8AeJEGgcjwshiGCS19zzA9UKABGGFqk6qhDiFUZAFViryqcuiyW9ACB9d1g=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none; ietf.org; dmarc=none action=none header.from=sit.fraunhofer.de; 
Received: from AM9P194MB1316.EURP194.PROD.OUTLOOK.COM (2603:10a6:20b:3aa::19) by AM9P194MB1441.EURP194.PROD.OUTLOOK.COM (2603:10a6:20b:3a3::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3999.27; Sat, 3 Apr 2021 08:03:22 +0000
Received: from AM9P194MB1316.EURP194.PROD.OUTLOOK.COM ([fe80::f190:c3b1:4213:d69f]) by AM9P194MB1316.EURP194.PROD.OUTLOOK.COM ([fe80::f190:c3b1:4213:d69f%7]) with mapi id 15.20.3999.032; Sat, 3 Apr 2021 08:03:22 +0000
To: Carsten Bormann <cabo@tzi.org>, Emile Cormier <emile.cormier.jr@gmail.com>
CC: <cbor@ietf.org>
References: <CAM70yxBO8Rr4Fd2GBD4-K=8DY7oCefYLL=61_piLwJ8Wj=Dxww@mail.gmail.com> <DDDC5DCF-A757-43BB-BD0C-E38617320601@tzi.org>
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Message-ID: <33cdb7a5-4504-1ce5-7cc8-4933565466a6@sit.fraunhofer.de>
Date: Sat, 3 Apr 2021 10:03:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
In-Reply-To: <DDDC5DCF-A757-43BB-BD0C-E38617320601@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [79.234.119.37]
X-ClientProxiedBy: PR0P264CA0151.FRAP264.PROD.OUTLOOK.COM (2603:10a6:100:1b::19) To AM9P194MB1316.EURP194.PROD.OUTLOOK.COM (2603:10a6:20b:3aa::19)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.16.50] (79.234.119.37) by PR0P264CA0151.FRAP264.PROD.OUTLOOK.COM (2603:10a6:100:1b::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3999.26 via Frontend Transport; Sat, 3 Apr 2021 08:03:21 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 82d5a686-bd87-4047-6286-08d8f676f308
X-MS-TrafficTypeDiagnostic: AM9P194MB1441:
X-Microsoft-Antispam-PRVS: <AM9P194MB1441DA1454BCC48A0E8B6A23A8799@AM9P194MB1441.EURP194.PROD.OUTLOOK.COM>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 23xzPLxTRI4Px9C+iPdhge/0lh42rTZHzmj+I0zsvj6qDTRsdthBDcCeSRMGNLXQEDu/TOcp99DpJW6R+11nkutv9M95vuI5Pgyh9eP/7tzOTnb0TxEuMma+SgEQGT0jmq9EH29AvF0AYm/PzKmSEMHzPdGOU77Fo5v7v3lDu36ymxjpcK62Qdd87/HAE5slPdAcby4TiNJGjdLXMc+Y64gCCtCR0HM/Yr4C1WbA83UKVlxJ6qACgjs89akEia4hX+ZsYQKlwiq9+t/SO8e9x4VMGsL8ZQGMWM09SFhjAqQTDWa76X+VmSbHolEyS1JruIFbBdQg/O5K1D7ybtg1JIzndf7xmadrpkGPirqytc11ZdXi9is6ouQJGoH69rMBaRVMBdWxT78gzDl1egMRDGtOxz+81cwqgNgyIICqP/VpDqjL1//2ZhLa9OEUlYIyLf/T/piYLpj5m+AIt0AIHE3VrmxHStbdTVCvu1KcHqihVOwvLObmoPdcCWryYr/x51KsQBwBD7zg4ylj609PRhKgNlSbq3yC1x71P7mw4+qFlUG7Q3rzoDEGpAvGT3B8tZOa8nu+ovvsXNCV30mcEF6nIlLAxLYLJ1+cNb1qleoycUK60rs3aJjMIKIxIchxnlPkh5nQWvpKgMjSqGOqs7NeUqUD87oeOOZnl71BvisfltLh5HskdG9Vfs7WT2d0yIqZAigbWDmeLgT7ObSqboYqL5+4cLMBoxmxbT3yPRYhscI5gs+Xfm/mesgY1Kl6LvRuVOX23krcstXQUhmGgZbeRgg34vAI/7h++JHjkvg=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM9P194MB1316.EURP194.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(4636009)(39840400004)(376002)(366004)(396003)(136003)(346002)(16576012)(83380400001)(53546011)(8936002)(44832011)(478600001)(6486002)(956004)(966005)(110136005)(31686004)(38100700001)(16526019)(52116002)(2616005)(31696002)(316002)(5660300002)(26005)(66556008)(66476007)(2906002)(4326008)(66946007)(86362001)(8676002)(186003)(45980500001)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?YTJZYUl2Tk9NaFFjZnV1NXlzN09QK3dEZy82eXdSRklHa0g5Rkxra1dxQkND?= =?utf-8?B?YnRPWXk3Q1FnY05rTjJkQWlxWk1Pcmh0TitkVXFZMlBJQWVrdjVRVm80WDdB?= =?utf-8?B?djNVNjlwajNOS1NBMVhkNzI5MEt4YlNlUFIxVEhsaFR0eFJnQ2hMRzc5anc1?= =?utf-8?B?OVZWTW5OTlQzSGxPOHRDeFZPemh3VjR5ZVhjVWhKRFM5K2ErTFd0VkdBRERE?= =?utf-8?B?aHI4YzlSdU4vOWpqQzJQN2ZpWDBvdWZ0RGNUVlZOaVFaZmVVSFh0dDdGMXJy?= =?utf-8?B?WW9pWXJ6Um51WnFON2tMNkNxbDdaT0x3NXkzdjBZUTNOQUY1eEV3NkJGQXp0?= =?utf-8?B?U0VQTGZlSWJ4N1h2MGxBQjExZWtXWlZ1Z3g1Rkx6WXFmTVhDQ2lVMzRjRS92?= =?utf-8?B?WFRBeG44YlRBV29tSmgzSHBsOGNFWkI0ZkVXVkNSN2dPYWlLMFVDb2RjaHk3?= =?utf-8?B?WjZoSWFQNXdnRHZUZnNiOWxjd1R5VlA2aWgwbUc2V0Z3S1lGQ0ROVFF2SmxB?= =?utf-8?B?TmxNcXg4cTZjRmFzRXM2OGs3dnlzSEhKMlhsREFLTUp2d1dPN0RmNlozSzhK?= =?utf-8?B?ak9adVkwTmJ0ZzlnUkw0QVJJNktMaWxZb0VCRGE4aWhNcDkrNEdja0ZJeGhC?= =?utf-8?B?Q25ZMEdNcFFaY3FhUG82TnVtUkZHWEt2aEtiZmpIRnJ3aGpTZ3NyNmxld1JX?= =?utf-8?B?VVZBcHkzZkF3b1RuQ3BnaXpCSnVEOFhEVE1tbHZXckNVaTNtd1pVWHBvOFAw?= =?utf-8?B?dEZvRTVQdkpidkNNc2RkM2haT1FxcWwxb2FIc2xXcncrYU1PU1dDSEl5YUov?= =?utf-8?B?bDdnTVYzU3Bwc0E2MlhPV1VOTnA4OC9uUDQxaU1aclNhVEVOaUUzWmZoU2ZV?= =?utf-8?B?T2M3b3JiRHNuWmYxRktLOFFxVUFVTzg4Zm1wT3FocktVaTk4MzVzcjBPOU5k?= =?utf-8?B?cEZLVjVyVUp0eHEwY2dNcGJPRGFBb1Jqa1Y5WHlFTGZmSlkrd3JkRFZZVDk5?= =?utf-8?B?VklWSmdXZEVtV0lSMCtaOE4xSVVTbjNJMzNMYzB2OStJbVlZQjdSSVAxTmZ5?= =?utf-8?B?Rkd3WTBmbGpTMjMyWXlaZVd0U1BNRkhuQkdXd2tZU3I5Rlg2a0lOYWFkR1V4?= =?utf-8?B?NlJaMlhzSlJKd1BmN0h2UW5veDA5cklCeVMzbkc2eWJ6TnRQckpTaTlsWDRQ?= =?utf-8?B?MjMrc3JuVTZ1aU9yODgzYjZmbTBXNEpwMUdKeml4WFo2bXhjekM3aWh1U0NW?= =?utf-8?B?MThELy9hcWE3M2tCWHpPUGFKZ2Y1OFlXVzg4Q2tkNVdPZnVpN21zTFh0K3Az?= =?utf-8?B?UlZRODZQbXk5cXJCRzQxWlo0TCtSa3hnT28xM1NjUGFTaW5KQ0FXTHJ2dktz?= =?utf-8?B?MGZvaEtNRWRZUTBESlFnVnJmZGhJMlNHTSt4cXd2R1dEOUJqMnFyRy9NZTIz?= =?utf-8?B?REFSZXVkWm12NS9CK1JrTHVFaTROc3JwUHQvNkVWMWM0UHA0eWVCemdLMjhN?= =?utf-8?B?VzlvOHJDNkwwWUpQL1JjdzJMNGpRQ2w4RkppU0ZXRC9TR24zNVNzVHZuUGN6?= =?utf-8?B?TEE2OHlFZUdCVVk3VHJ4STNnQmkwYUxHSUM0cHIvaE1UQytHZXl3OEtzaW1S?= =?utf-8?B?U01NQVd6NWhxN0M2Mis2L2JlRnd2T2JHVzlnMUxncVQvbGMxWDNOb3dqbXRn?= =?utf-8?B?RXZvb3lDSU1TaXZGcEN4YnArM0p6K2hEdzA5bk5PczZPY0ZCTW1uRENvUlY3?= =?utf-8?Q?4Xy4klBiCYkiBRabIXcNVV9sByhlLQWHJ+SfQ38?=
X-MS-Exchange-CrossTenant-Network-Message-Id: 82d5a686-bd87-4047-6286-08d8f676f308
X-MS-Exchange-CrossTenant-AuthSource: AM9P194MB1316.EURP194.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Apr 2021 08:03:21.8694 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: f930300c-c97d-4019-be03-add650a171c4
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 0qC03ADGRSm8fnhGvmrZ4Sqocr11mqEZEYsFR/IVyIoT5V6SiPVB76O2icQBssQgEG8J/rK5SJ9eZCrBB8DYogQUCXjBSN5JYROdpedWoAo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM9P194MB1441
X-OriginatorOrg: sit.fraunhofer.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Nxrqw6lq5liwrNxS2RKjr3df6LI>
Subject: Re: [Cbor] draft-bormann-cbor-time-tag: POSIX and UTC are not the same
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 08:03:38 -0000

+1 on adding some references and expositional text in an Appendix. While 
this document most certainly is also "only the message of the 
messenger", the underlying principles result in confusion, occasionally. 
I think it is a good idea to mitigate some of these occasions, pro-actively.

On 03.04.21 09:34, Carsten Bormann wrote:
> On 3. Apr 2021, at 04:00, Emile Cormier <emile.cormier.jr@gmail.com 
> <mailto:emile.cormier.jr@gmail.com>> wrote:
>>
>> In draft-bormann-cbor-time-tag (tags 1001-1003), UTC and POSIX are 
>> confounded together under the same value of 0, under section 3.4. Key 
>> -1: Time Scale.
>>
>> UTC and POSIX are not the same! Per 
>> https://en.wikipedia.org/wiki/Unix_time:
>>
>>     ... leap seconds are ignored, with a leap second having the same
>>     Unix time as the second before it, and every day is treated as if
>>     it contains exactly 86400 seconds. Due to this treatment Unix time
>>     is not a true representation of UTC.
> 
> Well, that text is slightly confused, as it is a true representation of 
> UTC, except it can’t represent the 27 leap seconds we have had so far or 
> any of the future ones.
> 
>> This is reinforced by the fact that C++ has distinct clocks for system 
>> time and UTC:
>>
>> https://en.cppreference.com/w/cpp/chrono/system_clock
>> https://en.cppreference.com/w/cpp/chrono/utc_clock
>>
>> There should therefore be distinct values for POSIX and UTC.
> 
> POSIX and UTC (and thus NTP) are shifted by leap seconds (which is 
> sometimes called “ignoring leap seconds”, a term that should never be 
> used; cppreference says “not counting leap seconds”, which means that 
> you have to be aware of leap seconds to actively not count them).
> 
> TAI, GPS are true monotonic time scales.  Leap seconds have no influence 
> on them (what cppreference calls “including leap seconds”).
> As C++ utc_clock "includes leap seconds”, it appears to be a TAI 
> referenced time scale (with a constant offset of 10 seconds from TAI).
> 
> I’m sorry, I didn’t invent this, I’m just the messenger :-)
> 
> Maybe adding an appendix on platform time representations would be worth it…
> (We could also add more lines to figure 1, pointing out that C++ 
> utc_clock is TAI minus 10 seconds.)
> 
> Grüße, Carsten
> 
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor
> 


From nobody Sat Apr  3 06:00:20 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC3273A0AD4 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 06:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 9_RNL2RCT0iM for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 06:00:16 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 597A83A0AB8 for <cbor@ietf.org>; Sat,  3 Apr 2021 06:00:15 -0700 (PDT)
Received: from client-0137.vpn.uni-bremen.de (client-0137.vpn.uni-bremen.de [134.102.107.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FCH8D1mlRzyRk; Sat,  3 Apr 2021 15:00:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com>
Date: Sat, 3 Apr 2021 15:00:11 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 639147611.6453789-078ad5bf2a282cd6df5f427166ac610a
Content-Transfer-Encoding: quoted-printable
Message-Id: <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/0VjeXh-qW9ka1nczxyz_5gJGhMU>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 13:00:19 -0000

On 2021-04-03, at 03:39, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
> To allow the encoding any arbitrary time ratios, I propose a new CBOR =
tag wrapping an array of 1 to 3 values:
>=20
> [Count, Numerator, Denominator]

Right.  We already have tag 30 for rational numbers of form n/d.
So this would be c*n/d.
I=E2=80=99d imagine that in many applications, n/d would be a =
=E2=80=9Cconstant=E2=80=9D (i.e., available from the application=E2=80=99s=
 context); prefix packing or simply a convention could handle this.

> where Count is an integral or floating point number, and Numerator and =
Denominator are integers representing the ratio in seconds.The Numerator =
and Denominator would default to 1 if absent.

Only the trailing elements really can be =E2=80=9Cabsent=E2=80=9D (they =
could be null as well, but why not simply encode the 1 then).  Not sure =
that the denominator is likely to be the one that one would leave out.

> CBOR tags 1001-1003 would be extended to allow this new CBOR tag as =
the value key. This would allow me to encode additional metadata on the =
std::chrono::time_point clock type (POSIX, UTC, TAI, GPS).

Right, similar to the way we already handle 4 and 5 (and probably should =
add 30).
Alternatively, there could be separate keys for numerator and =
denominator, so these could be freely left out and/or combined.

I=E2=80=99m not so familiar with the use cases of this except for a =
scale factor of 86400 (i.e., days).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sat Apr  3 11:34:57 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4DB3A0AB2 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 11:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hgi_PuOhi0rt for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 11:34:51 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70443A0AB4 for <cbor@ietf.org>; Sat,  3 Apr 2021 11:34:51 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id nh5so1914423pjb.5 for <cbor@ietf.org>; Sat, 03 Apr 2021 11:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rNBDV5UHBK338hdb1pNW8tlLdBu5JCV2EpbGoLBXE4o=; b=jExAizCVfteSZm2SlzEanPFHmmf+JIqKvviBqhWIgx6k8W9SCdF68GHX98HH7mxUyb IXSU4hdQ1lmLT+sn8sqEMQ41BXfogVyXyJ815hCvbWPOwEQC7Yfwiv5/schl4suHe8Bi fIOcIEimFG8xdLXJKX5rijEz0KkAT9u9p6MP1hzvETuIKFdDEloK43o2pjStRXiDuonE xZ2gK/Uww7frhqaKtxBOKaSjWvND9um1jZ91zVbWfKZpoobHY+UB7JSjRFHJYB5WHlnx eUYerAG+nRFygXYgpIpMzSYEgX/qQn5/WWHEUX6V3FeTdQqrV9xcIyoyMWhcDziIHb8W kCpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rNBDV5UHBK338hdb1pNW8tlLdBu5JCV2EpbGoLBXE4o=; b=nRu84mvF03Bda7Or98siOYkqK/iEFV0VopCARAb5QWiHvMPTqO4vAA4AFqnvQJNTa5 BRX1XWlLbcRteRDsNfXS01CJvROT8sq84nfdBfCme0N+h9RG6izTC5V4jHh1DYjIqwei O6k1RuA6+vi6ILlaC0HfwOVD75u1pq2sJbfeOVe67BzppOmWv5v0qsogIGj2Yy4rHpyz h1pTLzbx/Cvo6fDUlcLH+ggIGhGtaqB5ZstaEl3JPDe4FdJ6cIhuxDZ0F9GJxg+zkyOi M0mnojsI3NJzanT/Qo3HguBXq33/Myc3a1Aygh1jub9m98uzbNz/MS1V9oNSP2xo7Us4 Vzzw==
X-Gm-Message-State: AOAM531ZHOvfSyMcCT8ghAzkJ7ZGYt4W+4FSUAygEL4lkh+60zbYm5f1 E8ZQPaczKeLmHg5lsF6Ju1FrHxvsgEW2WIlvUsI=
X-Google-Smtp-Source: ABdhPJykJz4DPT43sLi77WC60i76DzpaTDxE4wHjXItjw4TUXlaQPy2gcSWcyuChCegJhnrhM1xZh/QJ/3Glug46ZFY=
X-Received: by 2002:a17:90b:16cd:: with SMTP id iy13mr19677331pjb.46.1617474889540;  Sat, 03 Apr 2021 11:34:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxDK4d2NOUYbzXfYBqnCWCBjO+1JQ1tfWBSTC0bNKF5MyQ@mail.gmail.com> <EFCD8747-717A-47CA-851A-E803163E782C@tzi.org>
In-Reply-To: <EFCD8747-717A-47CA-851A-E803163E782C@tzi.org>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Sat, 3 Apr 2021 15:34:38 -0300
Message-ID: <CAM70yxDAbKuOJkSJmaBMZi=1_RdO4_AfnRhhh3C6TZ51h=7oeQ@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="00000000000039685605bf15b8aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/pS1xFAg6oguPxRtEWJIoQn5wTDU>
Subject: Re: [Cbor] Paywalled IEEE standards referenced in draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 18:34:56 -0000

--00000000000039685605bf15b8aa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 3, 2021 at 4:11 AM Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-04-03, at 01:49, Emile Cormier <emile.cormier.jr@gmail.com> wrote=
:
> >
> > The IETF draft for cbor tags 1001 thru 1003 reference the IEEE1588-2008
> standard for the clock quality keys.
> > Are there no other public domain or open-source standards that would
> serve the same purpose as IEEE1588-2008 for the clock quality keys?
>
> I=E2=80=99m not aware of any other places where this material has been wr=
itten up
> (note that RFC 8575 also simply references IEEE1588).
>
> > I ask that without any expertise on the subject, but merely as a C++
> CBOR library implementer who wants to support these CBOR tags (they are
> better for transmitting std::chrono::time_point values losslessly).
> >
> > At the very least, can the descriptions be more explicit about the data
> types needed for the clock quality keys? ClockClass and ClockAccuracy
> specify "one-byte integer", but it's not clear if it's signed or unsigned=
.
>
> Well, it is clear from the CDDL above, but I have fixed the textual
> description of the rationale to include =E2=80=9Cunsigned=E2=80=9D in the=
 editor copy [1].
>

Thanks! It did not occur to me to check the CDDL. I'll pay more attention
to that the next time the data type is not clear in the descriptive text.


>
> [1]: https://github.com/cbor-wg/time-tag/commit/8ce40c3
>
> > Also, "octet" would be a better word than "byte", since there are
> architectures (such as DSPs) where a byte is 16 bits.
>
> (See previous mail.)
>

If "byte" is already well understood to be 8 bits in these sorts of
internet standards, then I don't want to belabor the point.


>
> > The OffsetScaledLogVariance key does not mention the value's data
> type(s) or its physical units.
>
> That is because it is really weird, and you won=E2=80=99t be able to make=
 heads or
> tails of it unless you read IEEE1588.  Maybe we can have a summary of it =
in
> the next version, but rephrasing all the details won=E2=80=99t work.
>

I don't really need to understand it. I just need to pass it on to the
application if requested. I now see it defined as a 16-bit unsigned integer
in the CDDL.


>
> > My motivation is to create an intermediate extended_time struct in my
> C++ library that contains all the possible fields of a CBOR extended time=
.
> If an application wants to deserialize it into a std::chrono::time_point,
> my library would discard the clock quality stuff. If some sort of
> scientific application really wants the clock quality information, then
> they just deserialize into an extended_time destination object and my
> library copies all the available information.
> >
> > It would be preferable if the numeric clock quality fields in my
> extended_time struct were of a known static type, such as a double. But
> since I don't have access to IEEE1588, I don't know if double is of
> sufficient accuracy. I would appreciate it if an expert could illuminate =
me
> on the required numeric precision, or point me in the right direction for
> my own research on the subject.
>
> If you are talking about uncertainty (-7) and guarantee (-8), it is
> unclear to me what your precision requirements would be.  If the
> uncertainty is 1e-8 s, you could represent this in a double, but there of
> course is no exact representation of 1e-8 in IEEE 754 binary floating
> point.  The uncertainty of the uncertainty is going to be large enough th=
at
> this is entirely inconsequential.  (The range of double is definitely
> sufficient.)
>

Thank you, this helps. I'll probably just pass those items to the
application (if requested) as double-precision floats, then.

Thank you for your time and patience.


>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

--00000000000039685605bf15b8aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Sat, Apr 3, 2021 at 4:11 AM Carsten Bormann &lt;<a href=3D"mailto=
:cabo@tzi.org">cabo@tzi.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">On 2021-04-03, at 01:49, Emile Cormier &lt;<a hr=
ef=3D"mailto:emile.cormier.jr@gmail.com" target=3D"_blank">emile.cormier.jr=
@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; The IETF draft for cbor tags 1001 thru 1003 reference the IEEE1588-200=
8 standard for the clock quality keys.<br>
&gt; Are there no other public domain or open-source standards that would s=
erve the same purpose as IEEE1588-2008 for the clock quality keys?<br>
<br>
I=E2=80=99m not aware of any other places where this material has been writ=
ten up (note that RFC 8575 also simply references IEEE1588).<br>
<br>
&gt; I ask that without any expertise on the subject, but merely as a C++ C=
BOR library implementer who wants to support these CBOR tags (they are bett=
er for transmitting std::chrono::time_point values losslessly).<br>
&gt; <br>
&gt; At the very least, can the descriptions be more explicit about the dat=
a types needed for the clock quality keys? ClockClass and ClockAccuracy spe=
cify &quot;one-byte integer&quot;, but it&#39;s not clear if it&#39;s signe=
d or unsigned.<br>
<br>
Well, it is clear from the CDDL above, but I have fixed the textual descrip=
tion of the rationale to include =E2=80=9Cunsigned=E2=80=9D in the editor c=
opy [1].<br></blockquote><div><br></div><div>Thanks! It did not occur to me=
 to check the CDDL. I&#39;ll pay more attention to that the next time the d=
ata type is not clear in the descriptive text.<br></div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">
<br>
[1]: <a href=3D"https://github.com/cbor-wg/time-tag/commit/8ce40c3" rel=3D"=
noreferrer" target=3D"_blank">https://github.com/cbor-wg/time-tag/commit/8c=
e40c3</a><br>
<br>
&gt; Also, &quot;octet&quot; would be a better word than &quot;byte&quot;, =
since there are architectures (such as DSPs) where a byte is 16 bits.<br>
<br>
(See previous mail.)<br></blockquote><div><br></div><div>If &quot;byte&quot=
; is already well understood to be 8 bits in these sorts of internet standa=
rds, then I don&#39;t want to belabor the point.<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
&gt; The OffsetScaledLogVariance key does not mention the value&#39;s data =
type(s) or its physical units.<br>
<br>
That is because it is really weird, and you won=E2=80=99t be able to make h=
eads or tails of it unless you read IEEE1588.=C2=A0 Maybe we can have a sum=
mary of it in the next version, but rephrasing all the details won=E2=80=99=
t work.<br></blockquote><div><br></div><div>I don&#39;t really need to unde=
rstand it. I just need to pass it on to the application if requested. I now=
 see it defined as a 16-bit unsigned integer in the CDDL.<br></div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
&gt; My motivation is to create an intermediate extended_time struct in my =
C++ library that contains all the possible fields of a CBOR extended time. =
If an application wants to deserialize it into a std::chrono::time_point, m=
y library would discard the clock quality stuff. If some sort of scientific=
 application really wants the clock quality information, then they just des=
erialize into an extended_time destination object and my library copies all=
 the available information.<br>
&gt; <br>
&gt; It would be preferable if the numeric clock quality fields in my exten=
ded_time struct were of a known static type, such as a double. But since I =
don&#39;t have access to IEEE1588, I don&#39;t know if double is of suffici=
ent accuracy. I would appreciate it if an expert could illuminate me on the=
 required numeric precision, or point me in the right direction for my own =
research on the subject.<br>
<br>
If you are talking about uncertainty (-7) and guarantee (-8), it is unclear=
 to me what your precision requirements would be.=C2=A0 If the uncertainty =
is 1e-8 s, you could represent this in a double, but there of course is no =
exact representation of 1e-8 in IEEE 754 binary floating point.=C2=A0 The u=
ncertainty of the uncertainty is going to be large enough that this is enti=
rely inconsequential.=C2=A0 (The range of double is definitely sufficient.)=
<br></blockquote><div><br></div><div>Thank you, this helps. I&#39;ll probab=
ly just pass those items to the application (if requested) as double-precis=
ion floats, then.<br></div><div><br></div><div>Thank you for your time and =
patience.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
</blockquote></div></div>

--00000000000039685605bf15b8aa--


From nobody Sat Apr  3 12:16:39 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A30C63A10AA for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 12:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hYQPyQVkFI_R for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 12:16:27 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 619823A10B7 for <cbor@ietf.org>; Sat,  3 Apr 2021 12:16:25 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id s21so4169908pjq.1 for <cbor@ietf.org>; Sat, 03 Apr 2021 12:16:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LwzLjCUxAn/lr6Mt3trSO24RBsysaVFFHMsRU+eC7yY=; b=iTTc68ZiY13nyjaAyu0rSAxHyvS1PTMXsGE/K3U76MJxrK60SwqL/sNdamAr5k1jXp A/v7uG5YgVixl6TkKawdZ1MTHZsdAmAnazMvb56szngi3SYr1zUCs9+asCYiuIV1gPtk EdFGVsqh62aJd3iafW3/26ciJc0aOeOKJKOBvu/U3JcitwfT8pGN9/Q0BkcgoPvHCsem vHrsdpRoaB0EdSVrFC5zNEa1U6Fzhgz/xitg/CdnVoqsS1XevJWxfHIe5FbuWi1cJe1T qbZvYVU3nP8SH9I7lqkwLAbJAxPQLONzWqsy2iGuhjO3UPIYSgkI/nU+bwOGyepyy5TD Itzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LwzLjCUxAn/lr6Mt3trSO24RBsysaVFFHMsRU+eC7yY=; b=o1cPeZjK+KWF6oIfGZvrvdUNiHdu51B0RkSHu3HVvF77FIpm42nt7uEWwcsFghB7VC 0QLGxCkyqnlseEv7l8VIzizBgBcnhiRKORHVVCi0w3h7O0EAs40xt/KwkpRa8LyvACQP 5kyU+tP8nyBcpHwK9Yhin9Ec9W3uVs8nsLrZqb1hMFNNz2hMdjPUatmXC2jryE51uBKf JpdayqeG6g1d6GYMZIR9b41JAS9Yt7b7aXTx5PuxRdAnv/jyeYWQyQkcAb/7ZrkUe3vo A1lR9XNrxLQpBHfM1a+2RL4kX8PYrV6GZFNpDe0nxh8A/VHv3sFpzxKQA/1Wj0C4cokb E9Ww==
X-Gm-Message-State: AOAM532b2dH0tuJHtXSnNvAY+jxzEfUSOOgeiq5bQaUUFGX1YkRBKQKF UTsxfxgcRMU7EC24S5fwhMONAOmkXlOi95/gQrVme3GwdoSMvA==
X-Google-Smtp-Source: ABdhPJwT92FcvkfjTeCzAssrIcSwIRs0meUXvMuGKI9SBv1+NNAEhOmJaw3v+2HrPYsc+qcyAK1jJ+aocZgCMaZAgUM=
X-Received: by 2002:a17:902:c104:b029:e7:3268:6eb9 with SMTP id 4-20020a170902c104b02900e732686eb9mr17832033pli.32.1617477384021; Sat, 03 Apr 2021 12:16:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBO8Rr4Fd2GBD4-K=8DY7oCefYLL=61_piLwJ8Wj=Dxww@mail.gmail.com> <DDDC5DCF-A757-43BB-BD0C-E38617320601@tzi.org>
In-Reply-To: <DDDC5DCF-A757-43BB-BD0C-E38617320601@tzi.org>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Sat, 3 Apr 2021 16:16:13 -0300
Message-ID: <CAM70yxA80BBGDR=Rf_rrLPNEvX9BsjhKvp2JZPE-J_aGY54c_w@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e828ae05bf164c78"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/yHVIbI22D2twB85mfZ_Zv5sFTbw>
Subject: Re: [Cbor] draft-bormann-cbor-time-tag: POSIX and UTC are not the same
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 19:16:38 -0000

--000000000000e828ae05bf164c78
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 3, 2021 at 4:34 AM Carsten Bormann <cabo@tzi.org> wrote:

>
> TAI, GPS are true monotonic time scales.  Leap seconds have no influence
> on them (what cppreference calls =E2=80=9Cincluding leap seconds=E2=80=9D=
).
> As C++ utc_clock "includes leap seconds=E2=80=9D, it appears to be a TAI
> referenced time scale (with a constant offset of 10 seconds from TAI).
>
>
Ah yes, the C++ utc_clock having a constant offset from TAI makes sense to
me now. This was the piece of the puzzle that my brain was missing. :-)

The C++ tai_clock ticks do indeed have a constant 10 second offset from
utc_clock ticks (ignoring epoch starting moments) as shown here:
https://github.com/HowardHinnant/date/blob/77bd6b92a4f7f6a1bbbc44952e6502a3=
448376b0/include/date/tz.h#L2084

Note that HowardHinnant/date was the incubator project that lead to the
enhanced date/time facilities in C++20.

Thank you bearing with me as I grappled to understand this.

--000000000000e828ae05bf164c78
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Apr 3, =
2021 at 4:34 AM Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tz=
i.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div style=3D"overflow-wrap: break-word;"><div><br></div><div>TAI, GPS=
 are true monotonic time scales.=C2=A0 Leap seconds have no influence on th=
em (what=C2=A0cppreference=C2=A0calls =E2=80=9Cincluding leap seconds=E2=80=
=9D).</div><div>As C++ utc_clock &quot;includes leap seconds=E2=80=9D, it a=
ppears to be a TAI referenced time scale (with a constant offset of 10 seco=
nds from TAI).</div><div><br></div></div></blockquote><div><br></div>Ah yes=
, the C++ utc_clock having a constant offset from TAI makes sense to me now=
. This was the piece of the puzzle that my brain was missing. :-)</div><div=
><br></div><div>The C++ tai_clock ticks do indeed have a constant 10 second=
 offset from utc_clock ticks (ignoring epoch starting moments) as shown her=
e: <a href=3D"https://github.com/HowardHinnant/date/blob/77bd6b92a4f7f6a1bb=
bc44952e6502a3448376b0/include/date/tz.h#L2084">https://github.com/HowardHi=
nnant/date/blob/77bd6b92a4f7f6a1bbbc44952e6502a3448376b0/include/date/tz.h#=
L2084</a></div><div><br></div><div>Note that HowardHinnant/date was the inc=
ubator project that lead to the enhanced date/time facilities in C++20.<br>=
</div><div class=3D"gmail_quote"><div><br></div><div>Thank you bearing with=
 me as I grappled to understand this.<br></div></div></div>

--000000000000e828ae05bf164c78--


From nobody Sat Apr  3 12:59:02 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AF13A1269 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 12:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 EANAtCIzHMVf for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 12:58:56 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C67D3A1267 for <cbor@ietf.org>; Sat,  3 Apr 2021 12:58:56 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id t23so957716pjy.3 for <cbor@ietf.org>; Sat, 03 Apr 2021 12:58:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Dwsvfa1ysyCWglVZWpx44T/wwnV0H6jm3LatFmE2XkQ=; b=dunyBqxFW6+esjZv0lWmM4I7bKuHGiO5hbTnrsIC834ytsBqLKFqRyF65fSsK0r3OP DfHfunfWNPhnXYkE/vgsDUX3ROKcJ3CxaKTXl89M6QqHyNJtkSaSNKuJ2EVYVUeD9TqR 6ipQhZCvW1TfZM174Wl3056EqjjYtLseXtosiyzIZJxX6Mk9dVeDNZZhjQupTQQIULI4 B39FsDA+FYEeJqes8VXpXDk0vrdpL/DDLQTkh9+E3iYIyknH6lQfP/oSpDoZi27jiRNb 03DDDmI4gwHZnnDS0G6EoIX8/8bgxCboQSd7WtLtsCi3ZAS65ZE84T8scUJWrPeE2kdu OUoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Dwsvfa1ysyCWglVZWpx44T/wwnV0H6jm3LatFmE2XkQ=; b=GpvWV+8HqU3ouVPLN2AxCw+PM1uzRh8HilODJBIXNW+zwwI1PqNE8ef8AxxfuR0NW6 YbmpZIH50KVgNp6c74AjVSD19/+ucp5G3/8BwPIa6qUprgSDCxot2hSA7CV/5bcuK1Kl 6QsualirQva/VmmZ24eb99uLZowvFSZ9E/GGgYVvnsOdU0TbV+FnDAb82Dr4vKJdijCB a8WdLe3dePHNuR9zBHOIJoEZTgRt36W3rU7+61OcGWyx7vHlP12FUEx6EuVORPxfeqgO NzYkIKqPhLt7o2l3SHAGVWUkHOK4WwAsbXo6Vab+Rrx/3+gm/2XJHc6fBaM22bkV2WNG UJjw==
X-Gm-Message-State: AOAM530Aj3BBAVkPfhRVC20Z2PbvxE+JWwxu7t1XNmyoG+eubvvjSOn6 cfMzoDrpQm5rimlldgbEW9BKcTmX481v/56OHgI=
X-Google-Smtp-Source: ABdhPJyEv5mbYq+iSEQ1pzt0G9drglaF9zdtLaTZfxeOgDf9cNB4Vo1v01UpxJM8Iu3rIYU6nrZ1CiIPTQ6DSsBi++g=
X-Received: by 2002:a17:90b:310e:: with SMTP id gc14mr4241283pjb.198.1617479935018;  Sat, 03 Apr 2021 12:58:55 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org>
In-Reply-To: <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Sat, 3 Apr 2021 16:58:44 -0300
Message-ID: <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f54b9305bf16e4ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/IN0KVhHwmZFPZX_gAYWxZHz2b0g>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2021 19:59:01 -0000

--000000000000f54b9305bf16e4ce
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 3, 2021 at 10:00 AM Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-04-03, at 03:39, Emile Cormier <emile.cormier.jr@gmail.com> wrote=
:
> >
> > To allow the encoding any arbitrary time ratios, I propose a new CBOR
> tag wrapping an array of 1 to 3 values:
> >
> > [Count, Numerator, Denominator]
>
> Right.  We already have tag 30 for rational numbers of form n/d.
> So this would be c*n/d.
> I=E2=80=99d imagine that in many applications, n/d would be a =E2=80=9Cco=
nstant=E2=80=9D (i.e.,
> available from the application=E2=80=99s context); prefix packing or simp=
ly a
> convention could handle this.
>
> > where Count is an integral or floating point number, and Numerator and
> Denominator are integers representing the ratio in seconds.The Numerator
> and Denominator would default to 1 if absent.
>
> Only the trailing elements really can be =E2=80=9Cabsent=E2=80=9D (they c=
ould be null as
> well, but why not simply encode the 1 then).  Not sure that the denominat=
or
> is likely to be the one that one would leave out.
>

'null' could be the magic value that represents "ratio according to the
application context".

I've just had another idea... a denominator of zero (or possibly null)
could be a magic value used to indicate that the numerator is a base 10
exponent. This could allow a more compact representation when the ratio is
milliseconds, nanoseconds etc. Eg [123, -9, 0] instead of [123, 1,
1000000000] for expressing 123ns.

I'm also unsure about the denominator being more likely to be left out. I
think applications are more likely to transmit times as fractions of
seconds (e.g. Javascript Date in milliseconds, C++ std::chrono::sys_time in
nanoseconds), therefore it might be the numerator that's more likely left
out.


>
> > CBOR tags 1001-1003 would be extended to allow this new CBOR tag as the
> value key. This would allow me to encode additional metadata on the
> std::chrono::time_point clock type (POSIX, UTC, TAI, GPS).
>
> Right, similar to the way we already handle 4 and 5 (and probably should
> add 30).
> Alternatively, there could be separate keys for numerator and denominator=
,
> so these could be freely left out and/or combined.
>

I prefer having a dedicated tag for time expressed as C*N/D so that I can
have a more compact representation when the clock is assumed to be POSIX
and the clock accuracy doesn't matter. This new tag could then be handled
in CBOR extended time the same way it handles tag 4 and 5 (as you hinted).

I'm wondering if a new C*N/D tag could be useful in application domains
outside of timekeeping. It could be called something like "scaled ratio".


>
> I=E2=80=99m not so familiar with the use cases of this except for a scale=
 factor
> of 86400 (i.e., days).
>
>
Time points based on the 86400/1 ratio now have their own type alias in
C++: std::chrono::sys_date. They are now the recommended way to store and
compute dates in an efficient manner. Breaking them down into
year/month/day components is only recommended for display or data exchange
purposes.

Many thanks for the feedback!

Cheers,
Emile

--000000000000f54b9305bf16e4ce
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Apr 3, 2021 at 10:00 AM Carst=
en Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2021-04-03, a=
t 03:39, Emile Cormier &lt;<a href=3D"mailto:emile.cormier.jr@gmail.com" ta=
rget=3D"_blank">emile.cormier.jr@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; To allow the encoding any arbitrary time ratios, I propose a new CBOR =
tag wrapping an array of 1 to 3 values:<br>
&gt; <br>
&gt; [Count, Numerator, Denominator]<br>
<br>
Right.=C2=A0 We already have tag 30 for rational numbers of form n/d.<br>
So this would be c*n/d.<br>
I=E2=80=99d imagine that in many applications, n/d would be a =E2=80=9Ccons=
tant=E2=80=9D (i.e., available from the application=E2=80=99s context); pre=
fix packing or simply a convention could handle this.<br>
<br>
&gt; where Count is an integral or floating point number, and Numerator and=
 Denominator are integers representing the ratio in seconds.The Numerator a=
nd Denominator would default to 1 if absent.<br>
<br>
Only the trailing elements really can be =E2=80=9Cabsent=E2=80=9D (they cou=
ld be null as well, but why not simply encode the 1 then).=C2=A0 Not sure t=
hat the denominator is likely to be the one that one would leave out.<br></=
blockquote><div><br></div><div>&#39;null&#39; could be the magic value that=
 represents &quot;ratio according to the application context&quot;.</div><d=
iv><br></div><div>I&#39;ve just had another idea... a denominator of zero (=
or possibly null) could be a magic value used to indicate that the numerato=
r is a base 10 exponent. This could allow a more compact representation whe=
n the ratio is milliseconds, nanoseconds etc. Eg [123, -9, 0] instead of [1=
23, 1, 1000000000] for expressing 123ns.<br></div><div><br></div><div>I&#39=
;m also unsure about the denominator being more likely to be left out. I th=
ink applications are more likely to transmit times as fractions of seconds =
(e.g. Javascript Date in milliseconds, C++ std::chrono::sys_time in nanosec=
onds), therefore it might be the numerator that&#39;s more likely left out.=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
&gt; CBOR tags 1001-1003 would be extended to allow this new CBOR tag as th=
e value key. This would allow me to encode additional metadata on the std::=
chrono::time_point clock type (POSIX, UTC, TAI, GPS).<br>
<br>
Right, similar to the way we already handle 4 and 5 (and probably should ad=
d 30).<br>
Alternatively, there could be separate keys for numerator and denominator, =
so these could be freely left out and/or combined.<br></blockquote><div><br=
></div><div>I prefer having a dedicated tag for time expressed as C*N/D so =
that I can have a more compact representation when the clock is assumed to =
be POSIX and the clock accuracy doesn&#39;t matter. This new tag could then=
 be handled in CBOR extended time the same way it handles tag 4 and 5 (as y=
ou hinted).<br><br></div><div>I&#39;m wondering if a new C*N/D tag could be=
 useful in application domains outside of timekeeping. It could be called s=
omething like &quot;scaled ratio&quot;.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
<br>
I=E2=80=99m not so familiar with the use cases of this except for a scale f=
actor of 86400 (i.e., days).<br>
<br></blockquote><div><br></div><div>Time points based on the 86400/1 ratio=
 now have their own type alias in C++: std::chrono::sys_date. They are now =
the recommended way to store and compute dates in an efficient manner. Brea=
king them down into year/month/day components is only recommended for displ=
ay or data exchange purposes.<br></div><div><br></div><div>Many thanks for =
the feedback!<br></div><div><br></div><div>Cheers,</div><div>Emile<br></div=
></div></div>

--000000000000f54b9305bf16e4ce--


From nobody Sat Apr  3 20:00:11 2021
Return-Path: <lgl@island-resort.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF2E3A1083 for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 20:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=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 7N1fN0jUdrjm for <cbor@ietfa.amsl.com>; Sat,  3 Apr 2021 20:00:05 -0700 (PDT)
Received: from p3plsmtpa07-06.prod.phx3.secureserver.net (p3plsmtpa07-06.prod.phx3.secureserver.net [173.201.192.235]) (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 AF1243A1081 for <cbor@ietf.org>; Sat,  3 Apr 2021 20:00:05 -0700 (PDT)
Received: from [192.168.1.49] ([76.167.193.86]) by :SMTPAUTH: with ESMTPSA id SszblmoCAbSa5SszblYWQJ; Sat, 03 Apr 2021 20:00:04 -0700
X-CMAE-Analysis: v=2.4 cv=OIDiYQWB c=1 sm=1 tr=0 ts=60692bb4 a=t2DvPg6iSvRzsOFYbaV4uQ==:117 a=t2DvPg6iSvRzsOFYbaV4uQ==:17 a=1MSDjx2PAAAA:20 a=pGLkceISAAAA:8 a=gKmFwSsBAAAA:8 a=48vgC7mUAAAA:8 a=8wvRfdDZSjcQj26y3oYA:9 a=QEXdDO2ut3YA:10 a=xshDYo_HSl4r5RLtWnoA:9 a=T4gXUGBNC9afoNAl:21 a=_W_S_7VecoQA:10 a=nnPW6aIcBuj1ljLj_o6Q:22 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: lgl@island-resort.com
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <45AF20FB-886E-4BB7-9565-FC02E6BD694D@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD4ED031-EF87-42FF-B6ED-878D8487179F"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Sat, 3 Apr 2021 20:00:03 -0700
In-Reply-To: <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, cbor@ietf.org
To: Emile Cormier <emile.cormier.jr@gmail.com>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-CMAE-Envelope: MS4xfNm6YqNzrw36eB4uGsM7y2PifaTs674q/prkz+VWnxvBCtmTTh3nc3CR2XcQZ98iU9kRK5B6PKlWRpdeUbu2OqvxUt3igf9aXwlSkBSKR2AY35hgZMbb cAOxg9PKfrAsQTN3wTV5lo8hgcB6F3dTnENPe4cTpqbBfkmv7YAOK2vuHl2PLKct+lAeA2mzmy3YWdiyqXLVS5wY6o30jUJIs0HdTJnGU1BcqweLAJXbmeD4 2DvPJQXJXE6WdhhFbmv7bg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/HE2KbzcbhBmm455jFo3SbBlsymE>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2021 03:00:10 -0000

--Apple-Mail=_DD4ED031-EF87-42FF-B6ED-878D8487179F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Here=E2=80=99s a CBOR time FAQ that I wrote a few years ago: =
https://github.com/laurencelundblade/QCBOR/blob/master/doc/TimeTag1FAQ.md

If designing a protocol that=E2=80=99s to be implemented by lots of =
folks in many programming languages, then tag 1 epoch time seems like it =
covers most of the use cases to me. I think it is even good to exclude =
float from tag 1 because it doesn=E2=80=99t add much above a 64-bit =
epoch time value for human activity (see FAQ).=20

It would be good for the C++ CBOR encoder/decoder to translate from tag =
1 epoch time to/from C++ time points since tag 1 epoch is what you=E2=80=99=
ll find in most CBOR-based protocols.

What you propose seems useful in use cases of one C++ talking to another =
when the protocol is not intended for broad use.

LL


> On Apr 3, 2021, at 12:58 PM, Emile Cormier =
<emile.cormier.jr@gmail.com> wrote:
>=20
>=20
>=20
> On Sat, Apr 3, 2021 at 10:00 AM Carsten Bormann <cabo@tzi.org =
<mailto:cabo@tzi.org>> wrote:
> On 2021-04-03, at 03:39, Emile Cormier <emile.cormier.jr@gmail.com =
<mailto:emile.cormier.jr@gmail.com>> wrote:
> >=20
> > To allow the encoding any arbitrary time ratios, I propose a new =
CBOR tag wrapping an array of 1 to 3 values:
> >=20
> > [Count, Numerator, Denominator]
>=20
> Right.  We already have tag 30 for rational numbers of form n/d.
> So this would be c*n/d.
> I=E2=80=99d imagine that in many applications, n/d would be a =
=E2=80=9Cconstant=E2=80=9D (i.e., available from the application=E2=80=99s=
 context); prefix packing or simply a convention could handle this.
>=20
> > where Count is an integral or floating point number, and Numerator =
and Denominator are integers representing the ratio in seconds.The =
Numerator and Denominator would default to 1 if absent.
>=20
> Only the trailing elements really can be =E2=80=9Cabsent=E2=80=9D =
(they could be null as well, but why not simply encode the 1 then).  Not =
sure that the denominator is likely to be the one that one would leave =
out.
>=20
> 'null' could be the magic value that represents "ratio according to =
the application context".
>=20
> I've just had another idea... a denominator of zero (or possibly null) =
could be a magic value used to indicate that the numerator is a base 10 =
exponent. This could allow a more compact representation when the ratio =
is milliseconds, nanoseconds etc. Eg [123, -9, 0] instead of [123, 1, =
1000000000] for expressing 123ns.
>=20
> I'm also unsure about the denominator being more likely to be left =
out. I think applications are more likely to transmit times as fractions =
of seconds (e.g. Javascript Date in milliseconds, C++ =
std::chrono::sys_time in nanoseconds), therefore it might be the =
numerator that's more likely left out.
> =20
>=20
> > CBOR tags 1001-1003 would be extended to allow this new CBOR tag as =
the value key. This would allow me to encode additional metadata on the =
std::chrono::time_point clock type (POSIX, UTC, TAI, GPS).
>=20
> Right, similar to the way we already handle 4 and 5 (and probably =
should add 30).
> Alternatively, there could be separate keys for numerator and =
denominator, so these could be freely left out and/or combined.
>=20
> I prefer having a dedicated tag for time expressed as C*N/D so that I =
can have a more compact representation when the clock is assumed to be =
POSIX and the clock accuracy doesn't matter. This new tag could then be =
handled in CBOR extended time the same way it handles tag 4 and 5 (as =
you hinted).
>=20
> I'm wondering if a new C*N/D tag could be useful in application =
domains outside of timekeeping. It could be called something like =
"scaled ratio".
> =20
>=20
> I=E2=80=99m not so familiar with the use cases of this except for a =
scale factor of 86400 (i.e., days).
>=20
>=20
> Time points based on the 86400/1 ratio now have their own type alias =
in C++: std::chrono::sys_date. They are now the recommended way to store =
and compute dates in an efficient manner. Breaking them down into =
year/month/day components is only recommended for display or data =
exchange purposes.
>=20
> Many thanks for the feedback!
>=20
> Cheers,
> Emile
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org <mailto:CBOR@ietf.org>
> https://www.ietf.org/mailman/listinfo/cbor =
<https://www.ietf.org/mailman/listinfo/cbor>

--Apple-Mail=_DD4ED031-EF87-42FF-B6ED-878D8487179F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Here=E2=80=99s a CBOR time FAQ that I wrote a few years =
ago:&nbsp;<a =
href=3D"https://github.com/laurencelundblade/QCBOR/blob/master/doc/TimeTag=
1FAQ.md" =
class=3D"">https://github.com/laurencelundblade/QCBOR/blob/master/doc/Time=
Tag1FAQ.md</a><div class=3D""><br class=3D""></div><div class=3D"">If =
designing a protocol that=E2=80=99s to be implemented by lots of folks =
in many programming languages, then tag 1 epoch time seems like it =
covers most of the use cases to me. I think it is even good to exclude =
float from tag 1 because it doesn=E2=80=99t add much above a 64-bit =
epoch time value for human activity (see FAQ).&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D"">It would be good for the =
C++ CBOR encoder/decoder to translate from tag 1 epoch time to/from C++ =
time points since tag 1 epoch is what you=E2=80=99ll find in most =
CBOR-based protocols.</div><div class=3D""><br class=3D""></div><div =
class=3D"">What you propose seems useful in use cases of one C++ talking =
to another when the protocol is not intended for broad use.</div><div =
class=3D""><br class=3D""></div><div class=3D"">LL</div><div =
class=3D""><br class=3D""></div><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Apr =
3, 2021, at 12:58 PM, Emile Cormier &lt;<a =
href=3D"mailto:emile.cormier.jr@gmail.com" =
class=3D"">emile.cormier.jr@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"Apple-interchange-newline"><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Apr =
3, 2021 at 10:00 AM Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" =
class=3D"">cabo@tzi.org</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;">On 2021-04-03, at 03:39, Emile =
Cormier &lt;<a href=3D"mailto:emile.cormier.jr@gmail.com" =
target=3D"_blank" class=3D"">emile.cormier.jr@gmail.com</a>&gt; =
wrote:<br class=3D"">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">&gt; To =
allow the encoding any arbitrary time ratios, I propose a new CBOR tag =
wrapping an array of 1 to 3 values:<br class=3D"">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">&gt; [Count, =
Numerator, Denominator]<br class=3D""><br class=3D"">Right.&nbsp; We =
already have tag 30 for rational numbers of form n/d.<br class=3D"">So =
this would be c*n/d.<br class=3D"">I=E2=80=99d imagine that in many =
applications, n/d would be a =E2=80=9Cconstant=E2=80=9D (i.e., available =
from the application=E2=80=99s context); prefix packing or simply a =
convention could handle this.<br class=3D""><br class=3D"">&gt; where =
Count is an integral or floating point number, and Numerator and =
Denominator are integers representing the ratio in seconds.The Numerator =
and Denominator would default to 1 if absent.<br class=3D""><br =
class=3D"">Only the trailing elements really can be =E2=80=9Cabsent=E2=80=9D=
 (they could be null as well, but why not simply encode the 1 =
then).&nbsp; Not sure that the denominator is likely to be the one that =
one would leave out.<br class=3D""></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">'null' could be the magic value that =
represents "ratio according to the application context".</div><div =
class=3D""><br class=3D""></div><div class=3D"">I've just had another =
idea... a denominator of zero (or possibly null) could be a magic value =
used to indicate that the numerator is a base 10 exponent. This could =
allow a more compact representation when the ratio is milliseconds, =
nanoseconds etc. Eg [123, -9, 0] instead of [123, 1, 1000000000] for =
expressing 123ns.<br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">I'm also unsure about the denominator =
being more likely to be left out. I think applications are more likely =
to transmit times as fractions of seconds (e.g. Javascript Date in =
milliseconds, C++ std::chrono::sys_time in nanoseconds), therefore it =
might be the numerator that's more likely left out.</div><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br =
class=3D"">&gt; CBOR tags 1001-1003 would be extended to allow this new =
CBOR tag as the value key. This would allow me to encode additional =
metadata on the std::chrono::time_point clock type (POSIX, UTC, TAI, =
GPS).<br class=3D""><br class=3D"">Right, similar to the way we already =
handle 4 and 5 (and probably should add 30).<br class=3D"">Alternatively, =
there could be separate keys for numerator and denominator, so these =
could be freely left out and/or combined.<br class=3D""></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">I prefer having a =
dedicated tag for time expressed as C*N/D so that I can have a more =
compact representation when the clock is assumed to be POSIX and the =
clock accuracy doesn't matter. This new tag could then be handled in =
CBOR extended time the same way it handles tag 4 and 5 (as you =
hinted).<br class=3D""><br class=3D""></div><div class=3D"">I'm =
wondering if a new C*N/D tag could be useful in application domains =
outside of timekeeping. It could be called something like "scaled =
ratio".<br class=3D""></div><div class=3D"">&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;"><br class=3D"">I=E2=80=99m not =
so familiar with the use cases of this except for a scale factor of =
86400 (i.e., days).<br class=3D""><br class=3D""></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">Time points based on the =
86400/1 ratio now have their own type alias in C++: =
std::chrono::sys_date. They are now the recommended way to store and =
compute dates in an efficient manner. Breaking them down into =
year/month/day components is only recommended for display or data =
exchange purposes.<br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Many thanks for the feedback!<br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">Cheers,</div><div class=3D"">Emile<br =
class=3D""></div></div></div><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">CBOR mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:CBOR@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">CBOR@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/cbor" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/cbor</a></div></blockquot=
e></div><br class=3D""></div></body></html>=

--Apple-Mail=_DD4ED031-EF87-42FF-B6ED-878D8487179F--


From nobody Sun Apr  4 01:38:09 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99533A1D37 for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 01:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 XT6cy0MIcWmx for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 01:38:04 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705EC3A1D36 for <cbor@ietf.org>; Sun,  4 Apr 2021 01:38:04 -0700 (PDT)
Received: from [192.168.217.152] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FCnHF3JLfzyX0; Sun,  4 Apr 2021 10:38:01 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A04D340E-49FE-497F-A123-1C10C20337A1"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com>
Date: Sun, 4 Apr 2021 10:38:00 +0200
Cc: cbor@ietf.org
Message-Id: <C354E68B-0B1A-4644-AB38-67453F8A52C3@tzi.org>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/WWrOutzcWJXEfaEXBLgvUmNcPsE>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2021 08:38:08 -0000

--Apple-Mail=_A04D340E-49FE-497F-A123-1C10C20337A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>=20
> I've just had another idea... a denominator of zero (or possibly null) =
could be a magic value used to indicate that the numerator is a base 10 =
exponent. This could allow a more compact representation when the ratio =
is milliseconds, nanoseconds etc. Eg [123, -9, 0] instead of [123, 1, =
1000000000] for expressing 123ns.

We already have decimal fractions (tag 4), so this is covered.
There is also key -9 etc. for tag 1001, if you want to separate the =
seconds and their fractional parts.
(I=E2=80=99m not a big fan of encoding magic values in the data items =
themselves, either.)

> I'm wondering if a new C*N/D tag could be useful in application =
domains outside of timekeeping. It could be called something like =
"scaled ratio".

Probably.
Making it amenable to cbor-packed suffix (or circumfix!) compression =
would make this a quite versatile tool.

> I=E2=80=99m not so familiar with the use cases of this except for a =
scale factor of 86400 (i.e., days).
>=20
>=20
> Time points based on the 86400/1 ratio now have their own type alias =
in C++: std::chrono::sys_date. They are now the recommended way to store =
and compute dates in an efficient manner. Breaking them down into =
year/month/day components is only recommended for display or data =
exchange purposes.

Right, so seconds (and their decimal fractions) and days are the most =
important scaling factors.

Gr=C3=BC=C3=9Fe, Carsten


--Apple-Mail=_A04D340E-49FE-497F-A123-1C10C20337A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><div class=3D"gmail_quote"><div class=3D""><br =
class=3D""></div><div class=3D"">I've just had another idea... a =
denominator of zero (or possibly null) could be a magic value used to =
indicate that the numerator is a base 10 exponent. This could allow a =
more compact representation when the ratio is milliseconds, nanoseconds =
etc. Eg [123, -9, 0] instead of [123, 1, 1000000000] for expressing =
123ns.<br class=3D""></div></div></div></div></blockquote><div><br =
class=3D""></div>We already have decimal fractions (tag 4), so this is =
covered.</div><div>There is also key -9 etc. for tag 1001, if you want =
to separate the seconds and their fractional parts.</div><div>(I=E2=80=99m=
 not a big fan of encoding magic values in the data items themselves, =
either.)</div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div class=3D"gmail_quote"><div =
class=3D"">I'm wondering if a new C*N/D tag could be useful in =
application domains outside of timekeeping. It could be called something =
like "scaled ratio".<br =
class=3D""></div></div></div></div></blockquote><div><br =
class=3D""></div>Probably.</div><div>Making it amenable to cbor-packed =
suffix (or circumfix!) compression would make this a quite versatile =
tool.</div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;">I=E2=80=99m not so familiar with =
the use cases of this except for a scale factor of 86400 (i.e., =
days).<br class=3D""><br class=3D""></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">Time points based on the 86400/1 ratio =
now have their own type alias in C++: std::chrono::sys_date. They are =
now the recommended way to store and compute dates in an efficient =
manner. Breaking them down into year/month/day components is only =
recommended for display or data exchange =
purposes.</div></div></div></div></blockquote><br =
class=3D""></div><div>Right, so seconds (and their decimal fractions) =
and days are the most important scaling factors.</div><br class=3D""><div =
class=3D""><div class=3D"">Gr=C3=BC=C3=9Fe, Carsten</div></div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_A04D340E-49FE-497F-A123-1C10C20337A1--


From nobody Sun Apr  4 10:06:07 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43FB83A10E9 for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 10:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GkjxIRpPmKUw for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 10:06:00 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 687183A10E8 for <cbor@ietf.org>; Sun,  4 Apr 2021 10:06:00 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id lr1-20020a17090b4b81b02900ea0a3f38c1so7503635pjb.0 for <cbor@ietf.org>; Sun, 04 Apr 2021 10:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J23yLcfYAy1ou0Ub+Iu2WMz2LZdcbMYzhxOEcVR1KqM=; b=aMXP+O9YTaPG0a1C1CNeF1ekzhoDAI2L5HftV+8Wvxh1lVVqA1oAcvGpiU1qR2nODm ui7vmq93GxWLVjQGofN2VcMUhlehhR3TuwTZ7LzLOUbyX8TY47WLQUfK77X5fAq9xC0g zqEzoRPwQEJe14Zi1ZuhYSvhSVpTbOdD9qUCOBAsFvifk90OSJSs7Kd+9uwu2/wbPg86 jIXF7PXyCC6pRnYcm3lAjX4wQ0ht1uzpEk0MD33GwteK3juyuPl6kL8jFBmo1ZhiT21o pc5KgExIyEyF8RoigXdrvqyDO1PxkMfps+NU3ZomAZ06QNalz6+I278ePe+rMhZBDE54 1+CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J23yLcfYAy1ou0Ub+Iu2WMz2LZdcbMYzhxOEcVR1KqM=; b=jOW7v10tuDIsboQOB3/CEm9gUiVtbJ9XCybzMkz1gPlYeizu5VxoiHq/oq6DVv8+Aw ncpwOhvbjqyqRQmsPyFh0s1Z6Mbmtq3f8B4uMR+mUY88wwoCWPNzEKTxKkMOO4NwFxHJ rovGmb2KRKK1CJiVGqnwg8z0mIk/+QLh0uQc3B/DLX1gI3FPnxA0mqkJN5MCylS626xG VsMRuhIrzH/TWtzJ60Faphfa4ndXdArKftj5X+YmYfR+Xo1GgKrz9LXq3yTbioq3EERR mst+jPpms7Vi/h+Vbb9M+nfOfpzyN0TY7MC6hHT+Ie994o0WnIQQ+3+7VV0/LQvURVYd epcw==
X-Gm-Message-State: AOAM5336Hr5Mjm5MH8NDRiiXj/sEISQJnqK99of9/On55fnBcbckqtg3 +2h6E7ExetzDE/oULPPzzORL5oTB5kStoLhJ+sU=
X-Google-Smtp-Source: ABdhPJw4ppDWp/tahvbXQKlM1d7YKcXbABRsQIsIuJhhiEsKI5846PnX5nzdHO0uSg/v+OeXG4skvf4puVfILrmPn18=
X-Received: by 2002:a17:90b:16cd:: with SMTP id iy13mr23373833pjb.46.1617555959108;  Sun, 04 Apr 2021 10:05:59 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com> <C354E68B-0B1A-4644-AB38-67453F8A52C3@tzi.org>
In-Reply-To: <C354E68B-0B1A-4644-AB38-67453F8A52C3@tzi.org>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Sun, 4 Apr 2021 14:05:48 -0300
Message-ID: <CAM70yxCZ2OJwUEbu1ARUCG4FPZKjZ4f4LG0QPnJ8tOFKfUu-Ag@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="00000000000058d85505bf289835"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/zvuE3drIR5bwGhWicxc09n5hTaA>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2021 17:06:05 -0000

--00000000000058d85505bf289835
Content-Type: text/plain; charset="UTF-8"

On Sun, Apr 4, 2021 at 5:38 AM Carsten Bormann <cabo@tzi.org> wrote:

>
> I've just had another idea... a denominator of zero (or possibly null)
> could be a magic value used to indicate that the numerator is a base 10
> exponent. This could allow a more compact representation when the ratio is
> milliseconds, nanoseconds etc. Eg [123, -9, 0] instead of [123, 1,
> 1000000000] for expressing 123ns.
>
>
> We already have decimal fractions (tag 4), so this is covered.
>

I overlooked tag 4 for that purpose. Thanks for reminding me.


> I'm wondering if a new C*N/D tag could be useful in application domains
> outside of timekeeping. It could be called something like "scaled ratio".
>
>
> Probably.
> Making it amenable to cbor-packed suffix (or circumfix!) compression would
> make this a quite versatile tool.
>
>
Are you referring to https://tools.ietf.org/html/draft-ietf-cbor-packed-02
? I wasn't aware of its existence before this.

--00000000000058d85505bf289835
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Sun, Apr 4, 2021 at 5:38 AM Carsten Bormann &lt;<a href=3D"mailto=
:cabo@tzi.org">cabo@tzi.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div><=
blockquote type=3D"cite"><div><div dir=3D"ltr" style=3D"font-family:Helveti=
ca;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:no=
rmal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;text-decoration:none"><div class=
=3D"gmail_quote"><div><br></div><div>I&#39;ve just had another idea... a de=
nominator of zero (or possibly null) could be a magic value used to indicat=
e that the numerator is a base 10 exponent. This could allow a more compact=
 representation when the ratio is milliseconds, nanoseconds etc. Eg [123, -=
9, 0] instead of [123, 1, 1000000000] for expressing 123ns.<br></div></div>=
</div></div></blockquote><div><br></div>We already have decimal fractions (=
tag 4), so this is covered.</div></div></blockquote><div><br></div><div>I o=
verlooked tag 4 for that purpose. Thanks for reminding me.<br></div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D=
"overflow-wrap: break-word;"><div><blockquote type=3D"cite"><div><div dir=
=3D"ltr" style=3D"font-family:Helvetica;font-size:12px;font-style:normal;fo=
nt-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px;text-decoration:none"><div class=3D"gmail_quote"><div>I&#39;m wondering =
if a new C*N/D tag could be useful in application domains outside of timeke=
eping. It could be called something like &quot;scaled ratio&quot;.<br></div=
></div></div></div></blockquote><div><br></div>Probably.</div><div>Making i=
t amenable to cbor-packed suffix (or circumfix!) compression would make thi=
s a quite versatile tool.</div><div><br></div></div></blockquote><div><br><=
/div><div>Are you referring to <a href=3D"https://tools.ietf.org/html/draft=
-ietf-cbor-packed-02">https://tools.ietf.org/html/draft-ietf-cbor-packed-02=
</a> ? I wasn&#39;t aware of its existence before this.<br></div><div>=C2=
=A0</div></div></div>

--00000000000058d85505bf289835--


From nobody Sun Apr  4 11:02:41 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF3F3A1324 for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 11:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 xw8oKPbZ8eb4 for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 11:02:36 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD3753A1323 for <cbor@ietf.org>; Sun,  4 Apr 2021 11:02:36 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FD1pd6JrFzyWV; Sun,  4 Apr 2021 20:02:33 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxCZ2OJwUEbu1ARUCG4FPZKjZ4f4LG0QPnJ8tOFKfUu-Ag@mail.gmail.com>
Date: Sun, 4 Apr 2021 20:02:33 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 639252153.215874-7460e84abfa4958848036c75091c6ef8
Content-Transfer-Encoding: quoted-printable
Message-Id: <12E37C16-1B62-4A68-8E11-ED779089A90C@tzi.org>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <A96FD12B-2F8B-495B-83F1-4A0F50DAA12C@tzi.org> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com> <C354E68B-0B1A-4644-AB38-67453F8A52C3@tzi.org> <CAM70yxCZ2OJwUEbu1ARUCG4FPZKjZ4f4LG0QPnJ8tOFKfUu-Ag@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/sXXXaIzbgIar7S2XsUZt9C9uwi4>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2021 18:02:41 -0000

On 2021-04-04, at 19:05, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
>> I'm wondering if a new C*N/D tag could be useful in application =
domains outside of timekeeping. It could be called something like =
"scaled ratio".
>=20
> Probably.
> Making it amenable to cbor-packed suffix (or circumfix!) compression =
would make this a quite versatile tool.
>=20
>=20
> Are you referring to =
https://tools.ietf.org/html/draft-ietf-cbor-packed-02 ? I wasn't aware =
of its existence before this.

Indeed.  This doesn=E2=80=99t mean we should design tags with the =
assumption that we will always have packing available, but we also can =
assume if there is a strong reason to be very frugal with encoding =
space, cbor-packed will be available as an alternative to touching every =
single detail to make it more compact.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Apr  4 11:24:33 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53EBB3A13FD for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 11:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 c6qWSfN3Hrv3 for <cbor@ietfa.amsl.com>; Sun,  4 Apr 2021 11:24:28 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F113A13FC for <cbor@ietf.org>; Sun,  4 Apr 2021 11:24:28 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FD2Hs2tGbzyXW; Sun,  4 Apr 2021 20:24:25 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxA7iCKHRxHqvAt404xYU5f69Grun4rpTBD98+1HzZWc=w@mail.gmail.com>
Date: Sun, 4 Apr 2021 20:24:24 +0200
X-Mao-Original-Outgoing-Id: 639253464.724172-43074722d08bc447e393401aa15c17cc
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA70F7DF-AC91-46FF-86B3-99A186BFCD8D@tzi.org>
References: <CAM70yxC7o3CNz67Yx3-yLt3tPQaTRaezOO99Ssa-3ppu-NwD=Q@mail.gmail.com> <d9790cc20ed6ef267e656ab7b4f8492f@mothers-arms.co.uk> <CAM70yxBifhSvsmRu3bq3ayrqqMecp2q1LORUvGcK28jujZrOfg@mail.gmail.com> <CAM70yxB+iDW_11p+AHWc7Njcb-jpBS99OJU+70xBw9Pe+20U1g@mail.gmail.com> <CAM70yxA7iCKHRxHqvAt404xYU5f69Grun4rpTBD98+1HzZWc=w@mail.gmail.com>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/30g_AAbAKyZ4CGT3k0qm33FcrOY>
Subject: Re: [Cbor] Consolidated set of tags for map-like entities
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2021 18:24:32 -0000

We sat down and combined Emile=E2=80=99s consolidated CBOR tags draft =
with some ideas about how to handle these tags in CDDL.

=
https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-map-like-data-00.h=
tml

This does not have Emile=E2=80=99s =E2=80=9Cwith-list=E2=80=9D =
additions, which are probably a good idea to look at.

This also doesn=E2=80=99t address earlier discussions we have had about =
alternative formats (at the representation level) for ordered multimaps, =
as summarized for instance in:

<https://mailarchive.ietf.org/arch/msg/cbor/5MuDSyPivZ7JfPhsfwCaW2usFHQ>

So some discussion will be required.

I=E2=80=99m nominating this draft for a slot at Wednesday=E2=80=99s =
interim=E2=80=A6

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Apr  5 08:58:03 2021
Return-Path: <thiago.macieira@intel.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA83F3A1F2D for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 08:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=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 ei3JKZgF-SLr for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 08:57:50 -0700 (PDT)
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (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 AE9293A1E06 for <cbor@ietf.org>; Mon,  5 Apr 2021 08:57:34 -0700 (PDT)
IronPort-SDR: gKGnFw8ENNcYfCaOMx2RkzzlE6s3vq/8TKatoa9YaYPuW0cmAi6sfOKdw/8snjNmODbBfgDyF8 5t6AWpqtuUwQ==
X-IronPort-AV: E=McAfee;i="6000,8403,9945"; a="172338050"
X-IronPort-AV: E=Sophos;i="5.81,307,1610438400"; d="scan'208";a="172338050"
Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2021 08:57:33 -0700
IronPort-SDR: UV50OnJIA9kTzukk3DHdH79l3c8mxMVjQLYusMPbbevox0337koDvo5KXlidNPKdAuITZT8sii J+ZgjrWHUOPA==
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.81,307,1610438400"; d="scan'208";a="440545262"
Received: from irsmsx605.ger.corp.intel.com ([163.33.146.138]) by fmsmga004.fm.intel.com with ESMTP; 05 Apr 2021 08:57:32 -0700
Received: from tjmaciei-mobl1.localnet (10.251.24.87) by IRSMSX605.ger.corp.intel.com (163.33.146.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 5 Apr 2021 16:57:31 +0100
From: Thiago Macieira <thiago.macieira@intel.com>
To: <cbor@ietf.org>
Date: Mon, 5 Apr 2021 08:57:28 -0700
Message-ID: <2403465.MzrCfxQRY8@tjmaciei-mobl1>
Organization: Intel Corporation
In-Reply-To: <45AF20FB-886E-4BB7-9565-FC02E6BD694D@island-resort.com>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com> <45AF20FB-886E-4BB7-9565-FC02E6BD694D@island-resort.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Originating-IP: [10.251.24.87]
X-ClientProxiedBy: orsmsx603.amr.corp.intel.com (10.22.229.16) To IRSMSX605.ger.corp.intel.com (163.33.146.138)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/mZ4X4Kwu61UCevJEcBSrzpHokWk>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 15:58:02 -0000

On Saturday, 3 April 2021 20:00:03 PDT Laurence Lundblade wrote:
> What you propose seems useful in use cases of one C++ talking to another
> when the protocol is not intended for broad use.
> 
> LL

Not really,. it's not. It's only useful if both sides already know what the 
other will send, otherwise you can't find a std::chrono::time_point 
specialisation to match the type. Note that the std::ratio specialisations 
that time_point are constructed on are compile-time constants. You can't match 
them unless you know before hand you may need to.

For example, ii I sent a time point specifying a ratio of 14609700 : 864, I 
REALLY do not expect the receiver to find a matching type (that's an average 
century with 36524 and one quarter days). Another "useful" ratio is 1296 : 
1000, the microfortnight.

So, no, let's be very clear that code meant to be interoperable should never 
use one of those. If we think it's useful to allow protocols to specify their 
own time points, sure, make it possible to encode them in a specific tag. I 
don't think it is.

I would say only decimal powers of the second with values 0, -3, -6 and -9 are 
meant to be used in interoperable protocols and therefore we should optimise 
for size for those and only those.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering




From nobody Mon Apr  5 15:09:58 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB753A29FE for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 15:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WQBJQSu_xFXG for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 15:09:50 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5ACF3A29F8 for <cbor@ietf.org>; Mon,  5 Apr 2021 15:09:50 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id i190so764187pfc.12 for <cbor@ietf.org>; Mon, 05 Apr 2021 15:09:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S8v7I1qccgzISytOgG4lGGWuPq4v/srFr2TnZn1rpr8=; b=dWxzDbBDBiwicaRQJxnDcTJHhywabtJFldiBigSQeJY5vn422GuqAvqs56U8PFgR+k PTXipClkjELZJrUdsi6wYokkPMcDAhNleKinEArbDgL2/3m9vu32iDcjnP9RyZ8pCy4l tPvthQyRvCAktO6QwOosGVZMtptnfM7xA2wr14O3LjUcaq6z5Npn4eipL6wnGYmHFCOz b45lYMtmnTKfaWVspU6A1m7vIVPs13g5J6Gyz6sfoLlP/oUXGkV7L78/IplSiLzRVMza SHrZuiob1TeBzVRewoT82W5wkUdzPGeQe35UROe66HCCDojRb79BoeB74N1PmaSMkiNQ zkCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S8v7I1qccgzISytOgG4lGGWuPq4v/srFr2TnZn1rpr8=; b=cDkDSsuPF4PZgXf+jgIpTonf/5LIhk3gADMXnSVNxl/Kzy/oGuEgz6bhsDtKvW9XaS FJk5bCgkSbi7EOFr4r5Fb1DN1LTMsCdyVsDBulsfZ3LTxnPEx1e/d1i4Q9shsBYYO+hN ctnukxYlxpSwDs9LFdG2sWxa6WJTxejd12uLdkK8uqcruqXrdQOIdnyk4Ae2CmZR+2or rpsOrA5miADgPQZblqFFrXzcWpQUW5LSud3gXbN/mDO+M4SYeIx1E695AUBf/LUuCziD E/1eHtArCqdROqNzFjP+vuZeJG3jHj2AaBMsJkam2h7C9cvhOWapcezMth1UskizLt9u eb5Q==
X-Gm-Message-State: AOAM532XI18NkIIAEBJLRM36mNE09rW1viD7ikVUlqkyN6kcVkP+fvNB hsmimfqxY+2Mzv2YANtJPYT8JwPhlVK8GEhO+mY=
X-Google-Smtp-Source: ABdhPJxsySCgNTv26zMKSyfXignONSb/KGF4QYJoDqw3MdLlU10+XVLKZ6UhVS+rk2bA0ja99nadEWjFqiz4JD3e2NI=
X-Received: by 2002:a63:fa41:: with SMTP id g1mr16346345pgk.143.1617660589133;  Mon, 05 Apr 2021 15:09:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <CAM70yxCaOps1n7pLo_BPR0_ggZ_QbJnY-jsNPw2NYPfP=psihg@mail.gmail.com> <45AF20FB-886E-4BB7-9565-FC02E6BD694D@island-resort.com> <2403465.MzrCfxQRY8@tjmaciei-mobl1>
In-Reply-To: <2403465.MzrCfxQRY8@tjmaciei-mobl1>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Mon, 5 Apr 2021 19:09:37 -0300
Message-ID: <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com>
To: Thiago Macieira <thiago.macieira@intel.com>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c8527705bf40f487"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/W2lynGwL3TH6h7_mgT8VCmbX3Ys>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 22:09:57 -0000

--000000000000c8527705bf40f487
Content-Type: text/plain; charset="UTF-8"

On Mon, Apr 5, 2021 at 12:59 PM Thiago Macieira <thiago.macieira@intel.com>
wrote:

> On Saturday, 3 April 2021 20:00:03 PDT Laurence Lundblade wrote:
> > What you propose seems useful in use cases of one C++ talking to another
> > when the protocol is not intended for broad use.
> >
> > LL
>
> Not really,. it's not. It's only useful if both sides already know what
> the
> other will send, otherwise you can't find a std::chrono::time_point
> specialisation to match the type. Note that the std::ratio specialisations
> that time_point are constructed on are compile-time constants. You can't
> match
> them unless you know before hand you may need to.
>

You are indeed correct that std::ratio is compile-time. But passing along
the ratio via CBOR allows the decoder to compute the values needed to store
it under a different compile-time std::ratio used by the receiving
application (as well as detecting overflow). If the destination ratio
happens to be the same, the decoder can bypass all the intermediate
calculations.


>
> For example, ii I sent a time point specifying a ratio of 14609700 : 864,
> I
> REALLY do not expect the receiver to find a matching type (that's an
> average
> century with 36524 and one quarter days). Another "useful" ratio is 1296 :
> 1000, the microfortnight.
>
>
Now, now, no need to get snarky. ;-)  I concede that ratios other than
86400:1 (days) or 1:10^3N are contrived examples and probably have no
practical use over an interoperable protocol.


> So, no, let's be very clear that code meant to be interoperable should
> never
> use one of those. If we think it's useful to allow protocols to specify
> their
> own time points, sure, make it possible to encode them in a specific tag.
> I
> don't think it is.
>
> I would say only decimal powers of the second with values 0, -3, -6 and -9
> are
> meant to be used in interoperable protocols and therefore we should
> optimise
> for size for those and only those.
>
>
I think dates expressed as a number of days since the epoch would also be
useful. Tag 0 (date/time string) has a numeric counterpart under tag 1. I
think tag 1004 (date string) should also have a numeric counterpart under
one form or another.

If tag 30 (rational number) were allowed to express time in seconds, it
could be used to represent integral days with a range of +/-2^61 / 86400 =
+/-26687997791825 days, which corresponds to +/-73069256156.73 years.
That's 5.3 times the age of the universe.

Of course, seconds since epoch (tag 1) could also be used to exchange a
date as days*86400, but the semantics of the value (a date) would be lost.

How about just a new tag for a date expressed as the number of days since
the epoch? This would definitely be useful (and efficient) in C++ when both
ends use std::chrono::sys_date. Decoders for other languages could simply
multiply the value by 86400 and handle it the same way as tag 1.

--000000000000c8527705bf40f487
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Mon, Apr 5, 2021 at 12:59 PM Thiago Macieira &lt;<a href=3D"mailt=
o:thiago.macieira@intel.com">thiago.macieira@intel.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">On Saturday, 3 April =
2021 20:00:03 PDT Laurence Lundblade wrote:<br>
&gt; What you propose seems useful in use cases of one C++ talking to anoth=
er<br>
&gt; when the protocol is not intended for broad use.<br>
&gt; <br>
&gt; LL<br>
<br>
Not really,. it&#39;s not. It&#39;s only useful if both sides already know =
what the <br>
other will send, otherwise you can&#39;t find a std::chrono::time_point <br=
>
specialisation to match the type. Note that the std::ratio specialisations =
<br>
that time_point are constructed on are compile-time constants. You can&#39;=
t match <br>
them unless you know before hand you may need to.<br></blockquote><div><br>=
</div><div>You are indeed correct that std::ratio is compile-time. But pass=
ing along the ratio via CBOR allows the decoder to compute the values neede=
d to store it under a different compile-time std::ratio used by the receivi=
ng application (as well as detecting overflow). If the destination ratio ha=
ppens to be the same, the decoder can bypass all the intermediate calculati=
ons.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">
<br>
For example, ii I sent a time point specifying a ratio of 14609700 : 864, I=
 <br>
REALLY do not expect the receiver to find a matching type (that&#39;s an av=
erage <br>
century with 36524 and one quarter days). Another &quot;useful&quot; ratio =
is 1296 : <br>
1000, the microfortnight.<br>
<br></blockquote><div><br></div><div>Now, now, no need to get snarky. ;-)=
=C2=A0 I concede that ratios other than 86400:1 (days) or 1:10^3N are contr=
ived examples and probably have no practical use over an interoperable prot=
ocol.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">
So, no, let&#39;s be very clear that code meant to be interoperable should =
never <br>
use one of those. If we think it&#39;s useful to allow protocols to specify=
 their <br>
own time points, sure, make it possible to encode them in a specific tag. I=
 <br>
don&#39;t think it is.<br>
<br>
I would say only decimal powers of the second with values 0, -3, -6 and -9 =
are <br>
meant to be used in interoperable protocols and therefore we should optimis=
e <br>
for size for those and only those.<br>
<br></blockquote><div><br></div><div>I think dates expressed as a number of=
 days since the epoch would also be useful. Tag 0 (date/time string) has a =
numeric counterpart under tag 1. I think tag 1004 (date string) should also=
 have a numeric counterpart under one form or another.</div><div><br></div>=
<div>If tag 30 (rational number) were allowed to express time in seconds, i=
t could be used to represent integral days with a range of +/-2^61 / 86400 =
=3D +/-26687997791825 days, which corresponds to +/-73069256156.73 years. T=
hat&#39;s 5.3 times the age of the universe.</div><div><br></div><div>Of co=
urse, seconds since epoch (tag 1) could also be used to exchange a date as =
days*86400, but the semantics of the value (a date) would be lost.</div><di=
v><br></div><div>How about just a new tag for a date expressed as the numbe=
r of days since the epoch? This would definitely be useful (and efficient) =
in C++ when both ends use std::chrono::sys_date. Decoders for other languag=
es could simply multiply the value by 86400 and handle it the same way as t=
ag 1.<br></div></div></div>

--000000000000c8527705bf40f487--


From nobody Mon Apr  5 15:29:07 2021
Return-Path: <thiago.macieira@intel.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC7D33A2A9D for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 15:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 BhgVF1kTl_Q5 for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 15:29:01 -0700 (PDT)
Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) (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 A2B423A2A9C for <cbor@ietf.org>; Mon,  5 Apr 2021 15:28:59 -0700 (PDT)
IronPort-SDR: sS6pKOD7nLhwA2riDMutZjhI9lIl4UwMui4YuvWGMmUphDm8H5FNQZXgGcxhvZ4VbuTdogGytL qw03bg+rxanw==
X-IronPort-AV: E=McAfee;i="6000,8403,9945"; a="173008362"
X-IronPort-AV: E=Sophos;i="5.81,307,1610438400"; d="scan'208";a="173008362"
Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2021 15:28:58 -0700
IronPort-SDR: IF574O2kNmVO2okmPKa/XMPn9GuwGlb7eU0HITGMWn3W5EcG3PBGJfGkwqaJskSGVTP1eyB/bs Ky9zIgxhiLUw==
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.81,307,1610438400"; d="scan'208";a="420917702"
Received: from irsmsx605.ger.corp.intel.com ([163.33.146.138]) by orsmga008.jf.intel.com with ESMTP; 05 Apr 2021 15:28:57 -0700
Received: from tjmaciei-mobl1.localnet (10.251.24.87) by IRSMSX605.ger.corp.intel.com (163.33.146.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 5 Apr 2021 23:28:56 +0100
From: Thiago Macieira <thiago.macieira@intel.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
CC: <cbor@ietf.org>
Date: Mon, 5 Apr 2021 15:28:52 -0700
Message-ID: <2096114.vpHZ4K6Zy5@tjmaciei-mobl1>
Organization: Intel Corporation
In-Reply-To: <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <2403465.MzrCfxQRY8@tjmaciei-mobl1> <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Originating-IP: [10.251.24.87]
X-ClientProxiedBy: orsmsx603.amr.corp.intel.com (10.22.229.16) To IRSMSX605.ger.corp.intel.com (163.33.146.138)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/K6PUoCE-lVnV5CiGPD9dE_FhpAg>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 22:29:06 -0000

On Monday, 5 April 2021 15:09:37 PDT Emile Cormier wrote:
> Now, now, no need to get snarky. ;-)  I concede that ratios other than
> 86400:1 (days) or 1:10^3N are contrived examples and probably have no
> practical use over an interoperable protocol.
> 
[cut]
> I think dates expressed as a number of days since the epoch would also be
> useful. Tag 0 (date/time string) has a numeric counterpart under tag 1. I
> think tag 1004 (date string) should also have a numeric counterpart under
> one form or another.

I can accept indicating the number of days. I don't find that a particularly 
useful encoding, since it does little to save space, but does add complexity. 
I don't find saving 2 bytes because we can encode the whole number of days 
until June 2149 a compelling value.

> If tag 30 (rational number) were allowed to express time in seconds, it
> could be used to represent integral days with a range of +/-2^61 / 86400 =
> +/-26687997791825 days, which corresponds to +/-73069256156.73 years.
> That's 5.3 times the age of the universe.

Please don't require rational numbers or BigFloat to represent time. The only 
valid encodings should be integers and floating point, and maybe not even the 
latter.

> Of course, seconds since epoch (tag 1) could also be used to exchange a date
> as days*86400, but the semantics of the value (a date) would be lost.
>
> How about just a new tag for a date expressed as the number of days since
> the epoch? 

Semantically indicating a date without time would be far more valuable, 
regardless of how it gets encoded. Simply expressing a time point that happens 
to be midnight UTC on a particular date is not that. So I support this idea.

Similarly, it would be useful to have just a time within a day.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering




From nobody Mon Apr  5 16:37:34 2021
Return-Path: <lgl@island-resort.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B42613A2CA9 for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=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 RQxeechEjCrf for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:37:28 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) (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 3CBF53A2CA7 for <cbor@ietf.org>; Mon,  5 Apr 2021 16:37:28 -0700 (PDT)
Received: from [192.168.1.81] ([76.167.193.86]) by :SMTPAUTH: with ESMTPA id TYmclN7A1ukyLTYmdlE4Ks; Mon, 05 Apr 2021 16:37:27 -0700
X-CMAE-Analysis: v=2.4 cv=Od9dsjfY c=1 sm=1 tr=0 ts=606b9f37 a=t2DvPg6iSvRzsOFYbaV4uQ==:117 a=t2DvPg6iSvRzsOFYbaV4uQ==:17 a=QyXUC8HyAAAA:8 a=48vgC7mUAAAA:8 a=53xPHaCqQ9RSo-jqpZQA:9 a=QEXdDO2ut3YA:10 a=Vpng8tuhqNti8GUUIpgA:9 a=MCRB6UTkycLNzvnJ:21 a=_W_S_7VecoQA:10 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: lgl@island-resort.com
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <F01F4733-E2B3-471A-AD9C-A3C4CD34446F@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1C39E431-AC0D-4DD8-B673-6896B186ADC7"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Mon, 5 Apr 2021 16:37:26 -0700
In-Reply-To: <2096114.vpHZ4K6Zy5@tjmaciei-mobl1>
Cc: Emile Cormier <emile.cormier.jr@gmail.com>, cbor@ietf.org
To: Thiago Macieira <thiago.macieira@intel.com>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <2403465.MzrCfxQRY8@tjmaciei-mobl1> <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com> <2096114.vpHZ4K6Zy5@tjmaciei-mobl1>
X-Mailer: Apple Mail (2.3445.104.17)
X-CMAE-Envelope: MS4xfLLHW8umYk2aJhYoHYptpCtb1E7giLe0EjWdgkGGyLNPP2A86fd2wUItI5VjIhs2AROdk67Qtph/4332fAkm2sEQXog0AhkBYSqlHeweneTBt37h0MhZ HREKSaqkv93NeYTydRk4RF+eRqHR4QezsLQArP1lOWC0Fn8ZshKxdPV9uqZGYcY/Y3i8nLhk+aoXB1Ek11uuGJodXhjG2mmXtlP9Ycy8jEksuiCDJZdCuyBr S4VIiGknk2DT4wZGRc6b0ySdt0dDDKjXREn+DXjjZPY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/HVZ-H4WnOUBsmHeIRJ-4qZPW4Zc>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 23:37:33 -0000

--Apple-Mail=_1C39E431-AC0D-4DD8-B673-6896B186ADC7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 5, 2021, at 3:28 PM, Thiago Macieira =
<thiago.macieira@intel.com> wrote:
>=20
>> How about just a new tag for a date expressed as the number of days =
since
>> the epoch?=20
>=20
> Semantically indicating a date without time would be far more =
valuable,=20
> regardless of how it gets encoded. Simply expressing a time point that =
happens=20
> to be midnight UTC on a particular date is not that. So I support this =
idea.

It=E2=80=99s been done.:-)  https://tools.ietf.org/html/rfc8943

LL=

--Apple-Mail=_1C39E431-AC0D-4DD8-B673-6896B186ADC7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 5, 2021, at 3:28 PM, Thiago Macieira &lt;<a =
href=3D"mailto:thiago.macieira@intel.com" =
class=3D"">thiago.macieira@intel.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">How =
about just a new tag for a date expressed as the number of days since<br =
class=3D"">the epoch?<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Semantically indicating a date without time would be far more =
valuable,<span class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">regardless of how it gets =
encoded. Simply expressing a time point that happens<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">to be midnight UTC on a =
particular date is not that. So I support this =
idea.</span></div></div></blockquote></div><br class=3D""><div =
class=3D"">It=E2=80=99s been done.:-) &nbsp;<a =
href=3D"https://tools.ietf.org/html/rfc8943" =
class=3D"">https://tools.ietf.org/html/rfc8943</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">LL</div></body></html>=

--Apple-Mail=_1C39E431-AC0D-4DD8-B673-6896B186ADC7--


From nobody Mon Apr  5 16:39:48 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A203A2C88 for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tqE9JWmMjwNv for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:39:41 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD3943A2CB4 for <cbor@ietf.org>; Mon,  5 Apr 2021 16:39:41 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id e10so2091349pls.6 for <cbor@ietf.org>; Mon, 05 Apr 2021 16:39:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oadwWZdctqL+XMt6RI50G4+XPbcvCUzWjVxDAm2PsSQ=; b=KubB+92x8b2VEUnJul99DBuvbvfdSzkJd588958rgc07JeNLOBGptubT4jap924GKR WX9V/ovYiEmxvRgEoC5/xBOAEwWfNV2zcSL47lR2RnV+th3eZeR362pmPCNJVnRc0qmt xzMBm8MPHoQuBCCh+0W7El0JPf1TsWLEqoogioNa3pQKNrSrGew9mYA6nJQbpROYgH8F P6/E/2QQDCJT4kFSrfZMdb3Qc4KrPa39E3HmURd3UQPtBVNbXQrXK+rF8W1HzVYxtQNS P4m/Z/MJjZjfEuKXAN5QL5sJbF88a/ItlQ5vjTpIzYtiQjC7hLEBnvkyR86lmyNebSNF kp5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oadwWZdctqL+XMt6RI50G4+XPbcvCUzWjVxDAm2PsSQ=; b=CkcUdltPHL3nqVhueXgO6ZQBn8tiUCtEavLlkJ6wp6JhoCRqAkuN1N5CpGzYf7FXW8 6Ir1czqpRmL/CI7Tqn1WunBP14MYpBQB1XF63xyWevKiGgfauxJ7VH9kB3OFXL3XlpWP oNLEU4uoEPixrV7YiEy6RpOyOg6UBvjd/52XfnpnrFsjjZi2oXNMm8/oEdKV3M1ubRYK K7QIsVADQez6D8wbzQgGQ2dRn98Pjewg/9UiEd0fRnIZQ51fsxT1L0fN48akR7VknqLL zF+tiK50cnZnK6Z+5P4KT/tyUaaDs+2pRfUoCWYoVJEOUn4+BMiaNJgrVZy418fj0Tez X+GA==
X-Gm-Message-State: AOAM530DNvNwuuaq78O9JIrMlfyxP3BLjBfeDsQFJsmHpvXYU33pSNLU +/pirFptn4TWpAGS+l0dpuR4eHen9AyHVDaY5H8=
X-Google-Smtp-Source: ABdhPJzy198gT39yYrLjwfuccV9smeCs/Js5t+Y1k6I2v59txPgjUbVY67Vm+4o/yCJy3DFdhlRErJ4xGHxXFxtvT5Q=
X-Received: by 2002:a17:90a:5898:: with SMTP id j24mr1521926pji.110.1617665979530;  Mon, 05 Apr 2021 16:39:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <2403465.MzrCfxQRY8@tjmaciei-mobl1> <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com> <2096114.vpHZ4K6Zy5@tjmaciei-mobl1>
In-Reply-To: <2096114.vpHZ4K6Zy5@tjmaciei-mobl1>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Mon, 5 Apr 2021 20:39:28 -0300
Message-ID: <CAM70yxBJe32LT3dZ-NEC+-On1BEg0Sgbsa7A-1h+V0Q-jFe-Gg@mail.gmail.com>
To: Thiago Macieira <thiago.macieira@intel.com>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="00000000000013439405bf4236f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/WdM2I_a5J2poLL3EZ6CkC5t6feo>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 23:39:46 -0000

--00000000000013439405bf4236f4
Content-Type: text/plain; charset="UTF-8"

On Mon, Apr 5, 2021 at 7:28 PM Thiago Macieira <thiago.macieira@intel.com>
wrote:


> I can accept indicating the number of days. I don't find that a
> particularly
> useful encoding, since it does little to save space, but does add
> complexity.
> I don't find saving 2 bytes because we can encode the whole number of days
> until June 2149 a compelling value.
>

My main motivation is not to save space. It's to save the computational
cost of an intermediate ISO8601 date string when both ends simply want to
exchange a std::chrono::sys_date (while preserving the date semantic). It's
the same motivation (presumably) as for tag 1. Not only is the Y/M/D to
days computation complex, you also have to check for invalid dates (e.g.
January 32nd, February 29 on a non-leap-year, etc).


> Please don't require rational numbers or BigFloat to represent time. The
> only
> valid encodings should be integers and floating point, and maybe not even
> the
> latter.
>

I can support that (no rational nor BigFloat), as long as there's a
mechanism to exchange dates as the number days since epoch without losing
the 'date' semantic.

I'm afraid the ship has already sailed regarding floating point
representation of time in the existing CBOR time tags. Javascript
'natively' handles time as floating point milliseconds. In Python, it's
floating point seconds.

We _could_ constrain a new, proposed "numeric date" tag to have an
integer-only data item, but it would not be consistent with the other
existing time tags which support both integer and floating point.
Javascript folks might complain about the lack of floating point.


> Semantically indicating a date without time would be far more valuable,
> regardless of how it gets encoded. Simply expressing a time point that
> happens
> to be midnight UTC on a particular date is not that. So I support this
> idea.
>

I'm also not fond of expressing dates as time-date values that coincide
with midnight.

I'm glad to hear about support for a numeric date tag in the same spirit as
tag 1. I'm happy to drop my "scaled ratio" idea if I can at least
efficiently transfer a std::chrono::sys_date without performing Gregorian
calendar conversions. All other likely use cases for
std::chrono::time_point (in seconds, ms, us, or ns) can be handled by the
existing tags.

Similarly, it would be useful to have just a time within a day.
>

That could be expressed with the CBOR duration tag (1002) as the duration
since midnight. Of course, the application would have to know to interpret
this duration as the time of day. std::chrono::duration is the recommended
way to store the time of day efficiently in C++. The new
std::chrono::hh_mm_ss in C++20 is intended more for display purposes.

Perhaps a key could be added in tag 1002 to indicate that the duration
represents a time of day?

Cheers,
Emile Cormier

--00000000000013439405bf4236f4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Mon, Apr 5, 2021 at 7:28 PM Thiago Macieira &lt;<a href=3D"mailto=
:thiago.macieira@intel.com">thiago.macieira@intel.com</a>&gt; wrote:<br></d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I can=
 accept indicating the number of days. I don&#39;t find that a particularly=
 <br>
useful encoding, since it does little to save space, but does add complexit=
y. <br>
I don&#39;t find saving 2 bytes because we can encode the whole number of d=
ays <br>
until June 2149 a compelling value.<br></blockquote><div><br></div><div>My =
main motivation is not to save space. It&#39;s to save the computational co=
st of an intermediate ISO8601 date string when both ends simply want to exc=
hange a std::chrono::sys_date (while preserving the date semantic). It&#39;=
s the same motivation (presumably) as for tag 1. Not only is the Y/M/D to d=
ays computation complex, you also have to check for invalid dates (e.g. Jan=
uary 32nd, February 29 on a non-leap-year, etc).<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">

Please don&#39;t require rational numbers or BigFloat to represent time. Th=
e only <br>
valid encodings should be integers and floating point, and maybe not even t=
he <br>
latter.<br></blockquote><div><br></div><div>I can support that (no rational=
 nor BigFloat), as long as there&#39;s a mechanism to exchange dates as the=
 number days since epoch without losing the &#39;date&#39; semantic.</div><=
div><br></div><div>I&#39;m afraid the ship has already sailed regarding flo=
ating point representation of time in the existing CBOR time tags. Javascri=
pt &#39;natively&#39; handles time as floating point milliseconds. In Pytho=
n, it&#39;s floating point seconds.</div><div><br></div><div>We _could_ con=
strain a new, proposed &quot;numeric date&quot; tag to have an integer-only=
 data item, but it would not be consistent with the other existing time tag=
s which support both integer and floating point. Javascript folks might com=
plain about the lack of floating point.<br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Semantically indicating a date without time would be far more valuable, <br=
>
regardless of how it gets encoded. Simply expressing a time point that happ=
ens <br>
to be midnight UTC on a particular date is not that. So I support this idea=
.<br></blockquote><div><br></div><div>I&#39;m also not fond of expressing d=
ates as time-date values that coincide with midnight.</div><div><br></div><=
div>I&#39;m glad to hear about support for a numeric date tag in the same s=
pirit as tag 1. I&#39;m happy to drop my &quot;scaled ratio&quot; idea if I=
 can at least efficiently transfer a std::chrono::sys_date without performi=
ng Gregorian calendar conversions. All other likely use cases for std::chro=
no::time_point (in seconds, ms, us, or ns) can be handled by the existing t=
ags.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div>

Similarly, it would be useful to have just a time within a day.</div></bloc=
kquote><div><br></div><div>That could be expressed with the CBOR duration t=
ag (1002) as the duration since midnight. Of course, the application would =
have to know to interpret this duration as the time of day. std::chrono::du=
ration is the recommended way to store the time of day efficiently in C++. =
The new std::chrono::hh_mm_ss in C++20 is intended more for display purpose=
s.<br></div><div><br></div><div>Perhaps a key could be added in tag 1002 to=
 indicate that the duration represents a time of day?<br></div><div><br></d=
iv><div>Cheers,</div><div>Emile Cormier<br></div></div></div>

--00000000000013439405bf4236f4--


From nobody Mon Apr  5 16:49:00 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0178E3A2D09 for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 q4l-FWmZEJel for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:48:53 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61E653A2D06 for <cbor@ietf.org>; Mon,  5 Apr 2021 16:48:53 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id a12so9158993pfc.7 for <cbor@ietf.org>; Mon, 05 Apr 2021 16:48:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ecu474aFqMa1JV82rriMY0MUYAKgq5FJHoC5F6bcElg=; b=XO+nBtB80ai5wjtX9ar+Ls2mBCcvRXKJJPW0BFwB7PqxXxhxFFDruBnZNtS/vbaKID KX/gmutwhyOTiVE0HL585ndVQXnYcXbfBjT3Xa/suoR8Z6HFXAAmaUK1TCh8S1lwbAhp eI629SQHYzKGTQRGGumNI2uxMqlX6IVeAdp3kXiQqBxCrWlyAnrCxqJxM40wRSsZPOq3 qR6q8WsDVgy/rBkQMRyiRFL8jTXayOSbjHZgYCuQCuy5qR/YNWLjvsprLp19xu1TnzKo FmQgHhSUuNVXBEWZqGfMeT18Z1arNaxRhyWPXv/85qLidlFIm7fE3mumvPiITgm8q05c Rxpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ecu474aFqMa1JV82rriMY0MUYAKgq5FJHoC5F6bcElg=; b=nz1jmF64b1L3NLdWF55N/ag+4FXZ9qAHO8POlcEL8EH95n3Kdu90GS3nFWInA9vS9R czlSrYQC88DKz2dRd4hdpFe7hcZcRiaUBJodEeixgJAjheqAsJmTWOJUGZP9dne6BtSL 3fJ9et+E1ZlNoqHQnpVe070HEixEjvVuPZxeg+EH5KVfQGaesYaSv9cYygFno4wR5Qdr fFqLskJpM0QjLKi3tqDUdtx8kvxRTlGTrAqjdQgvETYQZJ92LZunNHxzZHT6Gmc5/ymD FSqzslljoIaZTZEQcmvKCUE9UYMudoJqZp7B292qtxyiTAr2U+E34CXhysj/XXwdGwDK fJFw==
X-Gm-Message-State: AOAM531xJFuymvmoRnkupE2tDVHOaQB7q2F2+HLfoCmvFzHqBdOEAyr+ 369kxEZMpeaq2ofWnCkO1AtzinOPT/S7iKxaNKI=
X-Google-Smtp-Source: ABdhPJwMQ/0nuYy5JsNtbW92qCLgdupkvdNUFPwwZLSXZPKiKpSOClfzupP2egBcz/djwCgUOe1tfjrNc0Z5XMGM55c=
X-Received: by 2002:a62:3246:0:b029:224:6c6f:b3f2 with SMTP id y67-20020a6232460000b02902246c6fb3f2mr25066392pfy.68.1617666532211; Mon, 05 Apr 2021 16:48:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <2403465.MzrCfxQRY8@tjmaciei-mobl1> <CAM70yxAvoZmURMZHNY3-pKceU0mPbny=-QRAEeEzM2P0pcYrAg@mail.gmail.com> <2096114.vpHZ4K6Zy5@tjmaciei-mobl1> <F01F4733-E2B3-471A-AD9C-A3C4CD34446F@island-resort.com>
In-Reply-To: <F01F4733-E2B3-471A-AD9C-A3C4CD34446F@island-resort.com>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Mon, 5 Apr 2021 20:48:41 -0300
Message-ID: <CAM70yxDAQ9RQ3PS=6doomp4X7-MozVusEnfKVq2Co8JWPZ-Ocg@mail.gmail.com>
To: Laurence Lundblade <lgl@island-resort.com>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000047f0105bf425790"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/qAje5s5Q24khLpMKFOtIQpJ8lXg>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 23:48:58 -0000

--000000000000047f0105bf425790
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 5, 2021 at 8:37 PM Laurence Lundblade <lgl@island-resort.com>
wrote:

>
> It=E2=80=99s been done.:-)  https://tools.ietf.org/html/rfc8943
>

Darn, I missed tag 100 in the CBOR tags list! I would have expected
something like that to be adjacent to tag 1004. I guess the intent was to
save an extra byte.

Tag 100 is "Unsigned or negative integer", no floating point. I can
certainly live with that.

Alright I'd like to drop my original "scaled ratio" idea, as it doesn't
seem that it will gain much traction. At least one thing that came out of
this discussion (from Thago) is there's currently no way to explicitly
express a "time of day" semantic.

Thank you all for indulging me in this "out-of-the-box" idea. :-)

Cheers,
Emile Cormier

--000000000000047f0105bf425790
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Mon, Apr 5, 2021 at 8:37 PM Laurence Lundblade &lt;<a href=3D"mai=
lto:lgl@island-resort.com">lgl@island-resort.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap=
: break-word;"><br><div>It=E2=80=99s been done.:-) =C2=A0<a href=3D"https:/=
/tools.ietf.org/html/rfc8943" target=3D"_blank">https://tools.ietf.org/html=
/rfc8943</a></div></div></blockquote><div><br></div><div>Darn, I missed tag=
 100 in the CBOR tags list! I would have expected something like that to be=
 adjacent to tag 1004. I guess the intent was to save an extra byte.<br></d=
iv><div><br></div><div>Tag 100 is &quot;Unsigned or negative integer&quot;,=
 no floating point. I can certainly live with that.<br><br></div><div>Alrig=
ht I&#39;d like to drop my original &quot;scaled ratio&quot; idea, as it do=
esn&#39;t seem that it will gain much traction. At least one thing that cam=
e out of this discussion (from Thago) is there&#39;s currently no way to ex=
plicitly express a &quot;time of day&quot; semantic.<br></div><div><br></di=
v><div>Thank you all for indulging me in this &quot;out-of-the-box&quot; id=
ea. :-)</div><div><br></div><div>Cheers,</div><div>Emile Cormier<br></div><=
/div></div>

--000000000000047f0105bf425790--


From nobody Mon Apr  5 16:49:07 2021
Return-Path: <thiago.macieira@intel.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD9143A2D0B for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 sBUDIOFg9CKB for <cbor@ietfa.amsl.com>; Mon,  5 Apr 2021 16:49:01 -0700 (PDT)
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (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 784113A2D19 for <cbor@ietf.org>; Mon,  5 Apr 2021 16:49:00 -0700 (PDT)
IronPort-SDR: 4NYKTozZ3ymc0QNSxVQvqlQuJSdGBN374Ev6qN/NWvpuFOXnyFplHQNwJp+fjozz6I3UVRbW1c wjMtdycdvKfg==
X-IronPort-AV: E=McAfee;i="6000,8403,9945"; a="254281422"
X-IronPort-AV: E=Sophos;i="5.81,308,1610438400"; d="scan'208";a="254281422"
Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2021 16:48:59 -0700
IronPort-SDR: XhNNxtmQkaa3m9ZmRh1CtC8XXTCsd9sryLsBf9Zp0Yo4KpsDg0hN1a82QWkojscQbFr1ikoBwz xxKnj8GWe53Q==
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.81,308,1610438400"; d="scan'208";a="420940092"
Received: from irsmsx605.ger.corp.intel.com ([163.33.146.138]) by orsmga008.jf.intel.com with ESMTP; 05 Apr 2021 16:48:58 -0700
Received: from tjmaciei-mobl1.localnet (10.251.24.87) by IRSMSX605.ger.corp.intel.com (163.33.146.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 6 Apr 2021 00:48:57 +0100
From: Thiago Macieira <thiago.macieira@intel.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
CC: <cbor@ietf.org>
Date: Mon, 5 Apr 2021 16:48:51 -0700
Message-ID: <7356438.btiWBhuGgt@tjmaciei-mobl1>
Organization: Intel Corporation
In-Reply-To: <CAM70yxBJe32LT3dZ-NEC+-On1BEg0Sgbsa7A-1h+V0Q-jFe-Gg@mail.gmail.com>
References: <CAM70yxBF2XeewhsXOGv06kTVitz1kNHkYLHGqm3gX0Vyc2c2YA@mail.gmail.com> <2096114.vpHZ4K6Zy5@tjmaciei-mobl1> <CAM70yxBJe32LT3dZ-NEC+-On1BEg0Sgbsa7A-1h+V0Q-jFe-Gg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Originating-IP: [10.251.24.87]
X-ClientProxiedBy: orsmsx603.amr.corp.intel.com (10.22.229.16) To IRSMSX605.ger.corp.intel.com (163.33.146.138)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/GssDSkSjIjiJn7fd_HoFzian37U>
Subject: Re: [Cbor] Encoding Arbitrary Time Ratios
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2021 23:49:06 -0000

On Monday, 5 April 2021 16:39:28 PDT Emile Cormier wrote:
> Perhaps a key could be added in tag 1002 to indicate that the duration
> represents a time of day?

My motivation here is to represent the QTime class, which is a component of 
QDateTime, but not a very important motivation for me. We've been asked more 
than once to extend it to allow any duration, not just intra-day.

I'm happy with transferring QDateTime and QDate over a network.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering




From nobody Tue Apr  6 03:19:07 2021
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3311B3A1A51; Tue,  6 Apr 2021 03:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 6rcOv3b-Rc7L; Tue,  6 Apr 2021 03:19:01 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40048.outbound.protection.outlook.com [40.107.4.48]) (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 BDD9C3A1A50; Tue,  6 Apr 2021 03:19:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OChojg68xKP7k5Nt2UqaVPu6JI1Ea6+FJGWi9Y1DC5tOlvrM/vOved7s8XIdZWezKDBvWEuGX11Ea7Ckp0fgqubntCTkv45VuLSlEbQCB91pLBfNtHg22i7o9okUhRHRhipHUJhZsNgnja1AAqyUnp57QGdAvxMBKCi0+fvtQZo1duEyZxKDYpX+FRjt2QdPUzJjz+AqICjECgCVTTt7+HY49MEwJTl58KrZBD3M17ImJDnuAtH1wBjElvAonLkNjLHUL5NOoewk3QE3KXiMtqk0Ql7PN3LCaErRsQYftoOeD9ZmfUMh/5/ASuwOm9GaC5ETzu7Nn+5zVRODSBm8RQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GMLHvy8SMMhYSQewmvG69wSX0wJhuokwJHl4pXOTvKc=; b=fifJ+Ey6aW9LscA0UpdS7InsWez4vVrAkV4VRGLjBvRxpoSpnOKLP2ztt74FDlWLW1BAMCqxlLEkhjd5r+qOm3ziS5GiVYndSS8kc8jQ0yXiB7Qm3f85r5Cfvq7Q4GFY/HeI3PlHXkmOTgNfIHzwU/IIV3IFzx0lN1Ya1frBK9blzt1Vt5u5TUKthJqOa12kObvndBu44G7xr7NlBcDY96Dfn/oPzeAucCpSZcSOVXRwz9LsTr5WvjRSaR3D9JXHutmNpOz6cfV+Llt8MIzNc/4f49fBKCdrSCBGM1T5et/4pJiQVkCRpuc+C0EQnWxIsrTsMtxisBxL3bHO5bGzAA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GMLHvy8SMMhYSQewmvG69wSX0wJhuokwJHl4pXOTvKc=; b=F6aBsely5L0O+alwRDlJ8MSv5OJ+Y7hFXwzOoGTy7uPGK2DnUwrOHhEIavYMq+O4ekWlBU3E69Bp4oIN2lDxIJapQiHhPoyOmGavn1RdcmBTwU0A14G1g4L+qNu8CqX2oKUCmFsux97p9txqhYfoislLCB75kAplzyczlDwMPwk=
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) by HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.13; Tue, 6 Apr 2021 10:18:56 +0000
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b]) by HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b%5]) with mapi id 15.20.4020.015; Tue, 6 Apr 2021 10:18:56 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: "cbor@ietf.org" <cbor@ietf.org>
CC: "draft-ietf-acme-star-delegation@ietf.org" <draft-ietf-acme-star-delegation@ietf.org>
Thread-Topic: CDDL in draft-ietf-acme-star-delegation-07
Thread-Index: AQHXKs5A6DJmChB+p0eu+dqXQrw/7Q==
Date: Tue, 6 Apr 2021 10:18:55 +0000
Message-ID: <215725D8-7589-4121-A209-5E8802291955@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.47.21031401
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [62.63.203.117]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 092fb96b-b3d0-4125-1f31-08d8f8e562cb
x-ms-traffictypediagnostic: HE1PR07MB4217:
x-microsoft-antispam-prvs: <HE1PR07MB42171CA35C9A0C9193A54D1798769@HE1PR07MB4217.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: R5RFmA26/UpE6M1xRwcaOBow95e8GpUBrYbiT2mgc77ddSP83eN8uCK95ANAj024xF5laR+BSLb6eh10LMco6dYnBeeQbMZ4lueNefm0GebwBShXte4WsAYz0Z3kNJcSAml8A3rBnnseObEr49isSuodZpJfDuTxSM1nu8tI+FFfzEfw6Ke8lk+WZHpgs5zNLIBLXWJRhQ4yYnTEQJJSnDosOl0vV+xttGNOldi/rRHnMtHJzqeHFICuX2Odgv2Fiwrf3pLVDuZcX1tnO+zL5FXeKGEJME7lXjBHKosG3ra6uMCxdCmvPFq0ca5ugC2ejYWdrUiitfRdjlDkuAtsYQlLNEzJ0j/+qwHZZ4/3Y6lwj4xOxDthEt2JxOU87ZnOX6d3saC8CyceoRrlg+6PbvfqBCv2rZV3moKA0H99J9973i5aMBLJ2i9CBUdHoKeXtJmn7uLFK1bpCHfpMpR+Zk2aZPqAaHJT4CfBr5YWj8LhVTKpt3wCLh3X6ngYldD/4OzmMmNAAZQdCHeUCWrPfNfabzuD7ERi2nG2mhR9bMemXfct/HVkDy5Yd5Z5AE3P/qrBOkZOqwH6UG0TVcXNNUiiIrmhCBccCWSov3haTcGm1lqXin+rx7MdpZgUC3aR8rIMa5FgxRRd2V5ceYO1dMWDK4i/Mx1krgVcRoeIppRrFFcIT7+wSUsLYpRE7oYln4V2sl9LH5x2trFAvSjZjoHZICqmUh2RsfzGyLQOztfpOvSZueSC+zdtuh70Gm4CCm1P1ySAJKicJUJUnDaN/A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4217.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(366004)(39860400002)(396003)(136003)(376002)(44832011)(83380400001)(2906002)(36756003)(6512007)(4326008)(6486002)(38100700001)(6506007)(2616005)(478600001)(450100002)(186003)(316002)(5660300002)(966005)(4744005)(8676002)(66446008)(64756008)(66556008)(66476007)(33656002)(66946007)(76116006)(86362001)(91956017)(71200400001)(8936002)(6916009)(26005)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?RXRLVGlzWTIza2VpRytRNmY5T0xVV1RxNUFWd1E3RHptbFFURi93Wmt4VnBz?= =?utf-8?B?eUhsYWZZQ1NTV1FqaHV1M29RRDNpY3pUcjNmakZncUVoQnpBdHp4NjZPT0RV?= =?utf-8?B?Tm9HS2N1SDBvWEthWXB0K2NIQ0Z0Z3RMT0tVY0tNUXFubmVYT0VFOGRvdFQr?= =?utf-8?B?WEMwQW1KWHZZT1ZxdFFIbXF5OGhjR3FWNlBDTG1sQVdoYkxiMEpBaHEwV05p?= =?utf-8?B?OXFQRGdOZEdhdU9Yd0tZU3hQV0JoV3JaNENBZjVNMlh0eWJCUkovK2w2WU01?= =?utf-8?B?R29hbHlBT1NEVE5GTUpEUTNFNHh3eXBLSGlaWi9ZbXVtbjZoTldMcXAwWGFU?= =?utf-8?B?VHAvaUYwV3JLcXpMN29sbXpjODBHUlFUVjI1V1A2WlBWazFPVzcxWlJ1LytY?= =?utf-8?B?WGFtcGZhNjA4a0crVld0RWVPa04ydHVaZ1hidk5HeW1XUmdiRXhmSG5JWUFo?= =?utf-8?B?REliZm1kM09qWG1OMU1IV2tnUzd4QzNVSXd2S3pJZmIycHhhcXdhZjJJQk9z?= =?utf-8?B?eEJpZ2VGenVmWEEraEJ3OFlkZ1R6VndZeE5vb3V0TmFNNElzRy9JWmdPV2x4?= =?utf-8?B?MmVIUm5kaVgxSk9FM01xWHBqVStiRXUrVzhWQ25wbDBJenNSK2JINTZQdFp5?= =?utf-8?B?N1Y1dTR2LzJFYXM2cmVwWlowanBPQnY2VnlLYnVJblVnRy93UWtieFQ3QW5l?= =?utf-8?B?Vjd3OUtCSTlzM1hRUS9CMEttQlYvMjRyNFlzeHRsNjVpSmtIREhVaG1lTmxv?= =?utf-8?B?T283Y3orUCtlamVJUi9QejFoM3U1c2pkUXR1TEtXU2FHUkFlTDdoT2ZtUWJU?= =?utf-8?B?OHhxZWFTNmRWbXZwTVlnR1BBRmtqRUNySGVUaFNURzhBNDV5d1NGUSt0UVdt?= =?utf-8?B?b21GWjM4Ryt6b01rU3dlcGZidFJQNzhmUWdrZVU2bVU5N2JJZTBJdkkrWXYy?= =?utf-8?B?TFJiVXNYcUhBdG9KdTdRbE13UTVmcU9McW5ibTBHVFZaQjg1eGhHM0dnd1pG?= =?utf-8?B?eThvRlZQbTN3Q05TWEY0MjFxbVF4ZUZJcHQvOUIwUkJQRDBybS95QldEQytX?= =?utf-8?B?Yjd1b0RYdDI3UkNHNzNFbmtQVDc0U2NiVm9wQzBmQnVKOXV6SytKWkY3RlhN?= =?utf-8?B?akdIYkhLV0ZzUGZBcGFoRXgyS0hMZW1qcU5lY3JOcmlKN0oxS1FOcUR0UjNp?= =?utf-8?B?bHFGcTIzamdyV0QvTFVBdmdBaHQyK3prcmpkR3lKM1JhQzR4T0dvVTVEYS9H?= =?utf-8?B?ZjFFNUg0cnYydUVrMVg1cmZJUWxKVTZXQm1NcVc4WGRmVUNCdTVjWFRmUVFO?= =?utf-8?B?bHlSaGlHOHRhQjRpYlJwdGtvcTBnTitHWkpSRWw3alJ4UHlMK2JLMEdjcjU3?= =?utf-8?B?aGV0cEtXTTJ0cm95ek1tck5STFVFWkdBaGMycGxHcG5HRnBRTElHZVBZT0Vm?= =?utf-8?B?K1pqd0QvRlBiSDZGbmMwejNjTUlzZFNuZGloNnlJa2RLRzNuQ29uc0FuTEor?= =?utf-8?B?SFpqOHJWdVBOZklVSWY1aHhodEpBaDhydFNmQ2RUY255a2dRbksyREY4WHFQ?= =?utf-8?B?ajhWWE9jb1l2YWMxS0NITFVIWkU0TVNtU0VZaU51eVVtTGZMZ2REV3U0eXBY?= =?utf-8?B?T21HMFNwUDhIckZXbEpyOFYyMHIvbDhQK2RmclAvekw3ejBmZWgvQkNtMlBT?= =?utf-8?B?dmk0QnZCODNJV0lnT0Nza1lIYndJZDBmK3ZSMlo5V3EzR0d5ck9lTVpBUWh6?= =?utf-8?Q?T/QLK+PxarJmG3gFkysUgwsIx2LLOvo+UgxR1zb?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <ED4951E837DD9144BADB87167AB7810F@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4217.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 092fb96b-b3d0-4125-1f31-08d8f8e562cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2021 10:18:56.0374 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qz9UmZ78hb/gKLg7dlZlQ5o+gPUVxni6BAbIXb4sXNZ1U9IYLOx6Wg6qEyldMXkpI4m5SJ7rsk59oyuBikjsV8U78AcENtKRX7KGM2r4J/YfbCGVz9XrimDEky5JeYdF
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4217
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/2oBRCUTzvjiaW7qblm209iRlXW4>
Subject: [Cbor] CDDL in draft-ietf-acme-star-delegation-07
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 10:19:06 -0000

Q0RETCBleHBlcnRzLA0KDQpJIGFtIHJlYWNoaW5nIG91dCBiZWNhdXNlIGRyYWZ0LWlldGYtYWNt
ZS1zdGFyLWRlbGVnYXRpb24tMDcgaXMgaW4gSUVTRyByZXZpZXcsIGFuZCBpdCBjb250YWlucyBz
b21lIG5vcm1hdGl2ZSBDRERMLCBhY2NvbXBhbmllZCBieSBub24tbm9ybWF0aXZlIEpTT04gc2No
ZW1hIGFsdGVybmF0aXZlLCB3aGljaCBJIGRvbid0IHRoaW5rIGdvdCBhbnkgcmV2aWV3cyBmcm9t
IChvdGhlciB0aGFuIGF1dGhvcnMpIENEREwgZm9sa3MuIEkgaGF2ZSBwZXJzb25hbGx5IGNoZWNr
ZWQgdGhlIENEREwgdmlhIHRvb2xzLCBidXQgYW5vdGhlciBzZXQgb2YgZXllcyBsb29raW5nIHdv
dWxkIGJlIGdyZWF0Lg0KDQpJZiB5b3UgaGF2ZSBhIHNlY29uZCB0byB0YWtlIGEgbG9vayBhdCBp
dCwgYWQgc2VuZCBhbnkgZmVlZGJhY2sgYmVmb3JlIHRvbW9ycm93LCBJIHdvdWxkIGJlIHZlcnkg
Z3JhdGVmdWw6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtaWV0
Zi1hY21lLXN0YXItZGVsZWdhdGlvbi0wNyNhcHBlbmRpeC1CIA0KDQooWWVzLCB0aGlzIHdpbGwg
YmVjb21lIHBhcnQgb2YgdGhlIEFSVCBBcmVhIFJldmlldyBUZWFtIGFyZWEgb2YgY29tcGV0ZW5j
ZSwgYW5kIHlvdSBhcmUgdmVyeSB3ZWxjb21lIHRvIHRha2UgcGFydCBpbiB0aGF0IGRpc2N1c3Np
b24gaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9hcnQvbFpEOG9tbVpBeHFT
VEo0M1laLVJLN2JMNE13LyApDQoNClRoYW5rcywNCkZyYW5jZXNjYQ0KDQo=


From nobody Tue Apr  6 05:54:33 2021
Return-Path: <lars@eggert.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 981393A223F; Tue,  6 Apr 2021 05:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 cZe9zMMRevlM; Tue,  6 Apr 2021 05:54:17 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01A23A2248; Tue,  6 Apr 2021 05:53:11 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:68eb:fc77:3b2:d84e] (unknown [IPv6:2a00:ac00:4000:400:68eb:fc77:3b2:d84e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 34C0A600314; Tue,  6 Apr 2021 15:53:01 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1617713581; bh=8W3cC92tKJY75/Qt0obH72Cx1FGIHmABwQ54qxepPBY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=O9Kd75GKSvAmU6ltCHzltEqZWfaZtlTCW9tQb8UhJyE4pYbtmvggMlihXL0FaRG4O rPBVn9Dqqv0Icb4owSD4jN2lscCMJ7GgYqFKvarOLZRzcLjA4JQdzZbKKcelk1TbX5 61GiL2H4k6nqEnqvLzE4Un35Q8O3p9lCwUSC8B3Q=
From: Lars Eggert <lars@eggert.org>
Message-Id: <A6D0AF65-2086-4192-88F5-53E608B6F768@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_8F1724E7-1128-465A-8DA5-8E6E080F8A9C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 6 Apr 2021 15:53:01 +0300
In-Reply-To: <161626675022.26882.5439240460167296841@ietfa.amsl.com>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-cbor-tags-oid.all@ietf.org, cbor@ietf.org, last-call@ietf.org
To: Gyan Mishra <hayabusagsm@gmail.com>
References: <161626675022.26882.5439240460167296841@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-MailScanner-ID: 34C0A600314.A0291
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/EPpa2cUXZCiI7rlJiltebPNzf2U>
Subject: Re: [Cbor] [Last-Call] Genart last call review of draft-ietf-cbor-tags-oid-05
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 12:54:26 -0000

--Apple-Mail=_8F1724E7-1128-465A-8DA5-8E6E080F8A9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Gyan, thank you for your review. I have entered a No Objection ballot =
for this document.

Lars


> On 2021-3-20, at 20:59, Gyan Mishra via Datatracker <noreply@ietf.org> =
wrote:
>=20
> Reviewer: Gyan Mishra
> Review result: Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-cbor-tags-oid-??
> Reviewer: Gyan Mishra
> Review Date: 2021-03-20
> IETF LC End Date: 2021-03-24
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary:
> Document is ready for publication
> Major issues:
> None
>=20
> Minor issues:
> None
> Nits/editorial comments:
> None
>=20
>=20
>=20
> --
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call


--Apple-Mail=_8F1724E7-1128-465A-8DA5-8E6E080F8A9C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAmBsWa0ACgkQVLXDCb9w
wVfwOA//Zd+6Kn1AZTcGsOWyFEyvPryRbxtPU7XNMeDLQF/QRh9zvN5NjqsRWJx+
jUm2+bH9qDJ/HEhpd76FPvv5MNC6EoURc1o5CEcAHAH8f1DCYlnJMiJpBE6J+l26
mNdGTSWB566MxFOkoV8MBkchOUUSWcK7qlUOcQYi59YlXeanihbzndJunLlPTiO1
jbLmRpAaPzZmL7sZSciDnKdMH4v+10uPSojM1rTcRaBDysQivyF7AxhyGmmWyROv
O66c1sKSOqt8A2ByoZgSTWpiHCLsfLAu2TLhs1ASinYSUzRBHLapj0m+O11khizJ
4DlIJr0QkqmGRGzNkKptr36EUgiTZ95WkCvvzlfkgY7ZV5OUK+53ZOZEflaUBCS4
Nrm1vZwhSnly3Vb4NEjXoJaUH8Z4pssRmnY01tp9XP+7wjlxCJHVU6XwLh+Fq718
M77MTbQiwmu6Eega33RsHheqo6leE6rU591IHXYMRlbfYlWgxDo9aplWQrsVN4Db
92Qq4SjvYV86AzF4mdtBuUWjty4RSt57kldVnaJZufkHIAkcHksGkkDcSZ0px2JZ
Qh+WQRm2HOlSWlFUVt+rl387aGqGpiZiQvLHsw/+vT1f8X2K6ZcLafc9zn/UQoRA
peE4oHfb05IXi28SpVwc/IlR4KaftzGNe52Ix3yDiw5j87TEnqY=
=wElz
-----END PGP SIGNATURE-----

--Apple-Mail=_8F1724E7-1128-465A-8DA5-8E6E080F8A9C--


From nobody Tue Apr  6 08:46:24 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBDF3A2654; Tue,  6 Apr 2021 08:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZpNB6A5bQGiS; Tue,  6 Apr 2021 08:46:15 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFBA43A2618; Tue,  6 Apr 2021 08:46:14 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FFBhN2DpLzyR4; Tue,  6 Apr 2021 17:46:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <215725D8-7589-4121-A209-5E8802291955@ericsson.com>
Date: Tue, 6 Apr 2021 17:46:11 +0200
Cc: "cbor@ietf.org" <cbor@ietf.org>, "draft-ietf-acme-star-delegation@ietf.org" <draft-ietf-acme-star-delegation@ietf.org>
X-Mao-Original-Outgoing-Id: 639416771.594656-415d36642fb40dcd4f76fe3c62702e57
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E353DC2-E9E5-4BDE-9522-024A080093BB@tzi.org>
References: <215725D8-7589-4121-A209-5E8802291955@ericsson.com>
To: Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/23A-PFhRY-pdkg2-Kgcd4jqySVo>
Subject: Re: [Cbor] CDDL in draft-ietf-acme-star-delegation-07
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 15:46:23 -0000

Hi Francesca,

here are a few comments.

(1)
The json-schema.org definition uses oneOf, which should never be used =
(anyOf is usually what is actually meant; this is a well-known problem =
in the json-schema.org vocabulary).

(2)
keytypes is missing a minItems=3D1.

(3)
The regexp for =E2=80=9Coid=E2=80=9D (in both JSO and CDDL) is quite =
permissive with respect to leading zeros.  It is rather unusual to have =
leading zeroes (except for arc zero itself) in OID strings, so there =
might be some interop issues with that.

(4) the intro to the CDDL should probably mention that the multipleOf=3D8 =
on the RSA key size is not reflected in the CDDL, nor are the format=3Dxxx=
 keywords (which are not terribly well-defined in JSO either).

(5) subjectAltName.DNS items allow =E2=80=9C*=E2=80=9D and =E2=80=9C**=E2=80=
=9D in the CDDL form but might not in the JSO form (format=3Dhostname).

CDDL Style nits:

(a)
rsaKeySize =3D int .ge 2048
=3D>
rsaKeySize =3D uint .ge 2048
While these mean the same in CDDL, converters such as CDDL-YANG =
converters could put in different underlying built-in data types, and =
uint is actually the basic type for a size in bits.

(b)
There are a number of =E2=80=9C1*=E2=80=9D occurrence qualifiers that =
might be slightly more readable as =E2=80=9C+=E2=80=9D.=20

(c)
regtext-or-wildcard could be simplified by making use of prioritized =
choice (Appendix A of RFC 8610).  Of course, the current form is easier =
to translate into other specification formats (which actually wasn=E2=80=99=
t done for the JSO form), so this is just a note. =20

(d)
The non-empty object requirement (JSO: minProperties=3D1) could be =
stated in CDDL as

({=E2=80=A6=E2=80=A6}) .and ({ + any =3D> any })

To reduce noise, a generic could be defined:

non-empty<M> =3D (M) .and ({ + any =3D> any })

=E2=80=A6and used:

distinguishedName =3D non-empty<{
  ? country: regtext-or-wildcard
...
}>

There is not a lot of tool support for .and, so I am not going to push =
for this, but it sure works for me.

Gr=C3=BC=C3=9Fe, Carsten



> On 2021-04-06, at 12:18, Francesca Palombini =
<francesca.palombini=3D40ericsson.com@dmarc.ietf.org> wrote:
>=20
> CDDL experts,
>=20
> I am reaching out because draft-ietf-acme-star-delegation-07 is in =
IESG review, and it contains some normative CDDL, accompanied by =
non-normative JSON schema alternative, which I don't think got any =
reviews from (other than authors) CDDL folks. I have personally checked =
the CDDL via tools, but another set of eyes looking would be great.
>=20
> If you have a second to take a look at it, ad send any feedback before =
tomorrow, I would be very grateful: =
https://datatracker.ietf.org/doc/html/draft-ietf-acme-star-delegation-07#a=
ppendix-B=20
>=20
> (Yes, this will become part of the ART Area Review Team area of =
competence, and you are very welcome to take part in that discussion =
https://mailarchive.ietf.org/arch/msg/art/lZD8ommZAxqSTJ43YZ-RK7bL4Mw/ )
>=20
> Thanks,
> Francesca
>=20
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor


From nobody Tue Apr  6 09:21:13 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5B6B3A274D; Tue,  6 Apr 2021 09:21:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles via Datatracker <noreply@ietf.org>
To: <iot-directorate@ietf.org>
Cc: cbor@ietf.org, draft-ietf-cbor-tags-oid.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161772606961.13833.6830636143413776698@ietfa.amsl.com>
Reply-To: Ines Robles <mariainesrobles@googlemail.com>
Date: Tue, 06 Apr 2021 09:21:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/xtXQBYMB0UDnFV5rLFHebeda-tw>
Subject: [Cbor] Iotdir telechat review of draft-ietf-cbor-tags-oid-06
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 16:21:10 -0000

Reviewer: Ines Robles
Review result: Ready with Nits

Summary:

The document defines CBOR tags for object identifiers (OIDs).  The document is
well written.

Few minor questions/comments.

Major Issues: None

Minor Issues: None

Nits:

- It would be nice to expand SDNV in section 1.1 instead of Section 2.

- Section 3.2 - Figure 4-MIB relative object identifier in CBOR:

0b010_01001 should be 0b010_00011 ? for major type 2, additional information 3
bytes

- Section 7.1:

 -- In order to mention the registry, maybe smth like

  to assign the CBOR tags --> to assign in the CBOR tags registry the following
  tags....

 -- It would be nice to have the table with the same structure as the registry
 table (add reference column like in Section 7.2), I think template column does
 not apply here.

- Section 7.2:

-- In order to mention the registry, maybe smth similar as Section 7.1?

Thank you for this document,

Ines.



From nobody Tue Apr  6 09:57:04 2021
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1193A1E86; Tue,  6 Apr 2021 09:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 IXNETIACkQRf; Tue,  6 Apr 2021 09:56:57 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2040.outbound.protection.outlook.com [40.107.20.40]) (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 2705F3A28D5; Tue,  6 Apr 2021 09:56:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NBIfou9KcavYAceUYaEquWxuYj2G5rCP9N0kVWWcHKoW4PDUbGX/JKI5vF9fZiwOIaqvmFzkfbMJJaGcKUmBErGjvrxw0UmtbScxh7H9l2mvozxrDbU2GzJ1NXYZvuoE4CY+BR16XTL1020MTKZnppd2TfphUfvLIix7edGPRUbdH5bIT3fd0sdbmTWJEYAc7HScZqaW/0GKS1p3QOZr7tMDe/IFpUpz/8BJVDE+GBu5ThYxPs4VyBHC1OwerqUcni94GQeMxe9JDRb45l4Gd9GgBpNHyPMltTL2F5w9Pp2Uj/kdqTUBNBvtThkSrQg4pHr4533mJ0sJOcGuNwBkFg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oob48xe49DvxojKJ+kdehNkQ+xfrpe11xnC+aLLliKQ=; b=aP2wtOwZhe6LnFy3SzNf4LdgoXJJhVxoo3XTNLEyi7rAg/e7aWQ5K0Qtvbj4PgVBalIjh0QOw9inx9gzBebPntfaEzhsbB1xpdT5L34cCqRetHNx0H1ps14RCTe3OmaDJhXMmL6I7DnzvsOxAwnHnOI8d5J4a77Ixpd7I35hE3wO3GmckvRzoyqMT2Pe2CIirr/HhP0l+pfRt1QIncS2QiiTjUYJin+xjUYwJhlkG0OfXmie7No9Yf0OQJ3SL3pSjGg2sgvFoUWaCvYdS67m7ol1pkQRA8p5GZL8YUPDxEk61qr0hEz4I0/APK5lrG4w/lRIDC6YeyfdiMy1h8WtNw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oob48xe49DvxojKJ+kdehNkQ+xfrpe11xnC+aLLliKQ=; b=ZeBOtxb8j9nPGDD06Ibo4mFZRXQEVHQqZuZOZ3LwkOPiDDy20qZuk8Yee5hN23rhCNjSZRXuzJ/xDlP6GO2fZyVKrLUz0neMCyn9VEwqnMb60OJgkABUNyi/taHhKIQBCKHYp+ttjj+1T6cVTWWFsdcj2SzWTg3tP9BKkd9lcHc=
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) by HE1PR0701MB2345.eurprd07.prod.outlook.com (2603:10a6:3:6c::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.8; Tue, 6 Apr 2021 16:56:54 +0000
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b]) by HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b%5]) with mapi id 15.20.4020.015; Tue, 6 Apr 2021 16:56:53 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>
CC: "cbor@ietf.org" <cbor@ietf.org>, "draft-ietf-acme-star-delegation@ietf.org" <draft-ietf-acme-star-delegation@ietf.org>
Thread-Topic: [Cbor] CDDL in draft-ietf-acme-star-delegation-07
Thread-Index: AQHXKs5A6DJmChB+p0eu+dqXQrw/7aqnolKAgAA1SIA=
Date: Tue, 6 Apr 2021 16:56:53 +0000
Message-ID: <10C08C5D-016D-422F-ACA9-23E492CA5E93@ericsson.com>
References: <215725D8-7589-4121-A209-5E8802291955@ericsson.com> <6E353DC2-E9E5-4BDE-9522-024A080093BB@tzi.org>
In-Reply-To: <6E353DC2-E9E5-4BDE-9522-024A080093BB@tzi.org>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.47.21031401
authentication-results: tzi.org; dkim=none (message not signed) header.d=none;tzi.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [62.63.203.117]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 623170cc-bb73-460d-1f36-08d8f91cfb09
x-ms-traffictypediagnostic: HE1PR0701MB2345:
x-microsoft-antispam-prvs: <HE1PR0701MB2345CB4CB1A3D278B15089AB98769@HE1PR0701MB2345.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: zCzO4Vbw8RdfzwpQOQGPAdNSVFFl9k0ZyGeladtsrxM6TQnIEcJhD2nSV+qjE8RZxdMxsjZiHAIDuy6G/6DbtobQLij2ge5DeZXDbQ6TXiz65lSJDdZ+QNCgvqSvy95oY64BnL4Jt++aJ9EGDwYQ13SI/3KVQvh+he2iTYfQK5wUtNKAxrOhzTv07oTEyT6w90Cr6wNT5vHDBp89qxSZrkkTY/wGESJrtBYGBOzwLD1Zre9G6Y/SZTMpbbYZbXzmQR58XEoEzmAWRufpqp7sqepZlhPbSERVcX+m5XaCPmIU/+Sp5cY2xiFWgHdKRjGgKP48avIAnKBQckwKxyiHufXD3n7SKXtxJCjG3tsepI5AjVzRpQO8o9n90BzC8/8V6E+KtNggVlfYLaQCjv/jvDnn+36tcSexZsNrUsIn/zRXcwh8k+lwqJJpnMM0zcN/G4EvF6g8rOM7ZyQUeWH1CL3NH+nYuNCI0H3zus4F74SMACETfwTnTP4pPZm6e/lcnp0BiJ5NVg23iDFlYBvs6ex2p2k0YKfl+gWTHTKSHvsxyinNKEywCqrW2tqKO+ECAXN64wS+5LKseBunjeGghkcSRlT+FlzS8ogCFnIvGIqS8gvenGp488YsvKYtshjEKEKC9bsUnZtaN2FxElOqAQfnuWZWFG8u5BhBATWvaEwvsTU2Mo3pPZ0fvJlcO7q+KYU+AD1E1ED0r3rs4kYDH0Uyje6Tag2QF3DH1RZhCztASjzlUAX7SNutzLk/tICgy5UKEO3nq8h7uIvEZABgniQgy8C49XdUGzQRadjFH/4=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4217.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(376002)(366004)(136003)(346002)(396003)(6512007)(71200400001)(2906002)(26005)(4326008)(83380400001)(186003)(478600001)(53546011)(966005)(6486002)(6916009)(86362001)(76116006)(36756003)(38100700001)(8676002)(8936002)(6506007)(66476007)(54906003)(66556008)(64756008)(66446008)(66946007)(5660300002)(2616005)(316002)(44832011)(33656002)(21314003)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?dVFpVkNuKzNYSXFTenRsajRJQjcvNFFDb2w1OWtlc3M3ZkJCRmtDUHR1VnNS?= =?utf-8?B?cUI1MTFKYTY4eEpsZE12ZWJHWUxaN0FrUEpnUnoyS1dENTNBbXVDN21BQVU1?= =?utf-8?B?d3BBSGtpREtHWlB2Z1EwNHNqd2Z0QytsbGZsQ1p6UlZuY1FTOHlhNUlxVW1W?= =?utf-8?B?ZldvSnl4Rm9YNitEelNKQUM5eDY2dXFRRUpsT2pwdGIxckVqTTdIN0ZvNVI0?= =?utf-8?B?VkozcDZDM09EMlhpeUlrWUlDSzgzUjZweWtLdFowUXk5WmdHSEtsaFpPclVk?= =?utf-8?B?LzAxemJSWkYzUjh2NWpZaWpreVczM3h5d081aldrY0Z1WWd6UUdpT016UTk3?= =?utf-8?B?NnppNklKeUNUS1hKei9UbFZVVWFTMTFZUzRYTTJpNDBpNEFtazVleHJoeWFm?= =?utf-8?B?aWY1MTBTZ1BLWnNQWmxpVnl5cVJrSnQ3MGlYRHNiK2gxUVZmSG4wM3NEa0Fx?= =?utf-8?B?NjAvc2VjZXhvS3B1emhNTTRoT2x2WkRvMExIVkowaWRwS1o4TlQvdlFZbHMz?= =?utf-8?B?d2hRRFBhV3hDWDNORkNHWTlna2NuOUJuN3k0L1NQMDB6MEU1U2VhQ0JjaWph?= =?utf-8?B?SFl3MlJRaFFhU0p2ZiswbFVDcjhVdER0M1kxSFhONUdoZ3FPVHpidnBHYVVD?= =?utf-8?B?VzZZYjJ0aUs5WjVGVk11d2kySjBEMGxrMUFJTGJ5NUtTb3NMVDdZS3VLL0Jp?= =?utf-8?B?OU9FRHVIeDFMZXZSdHFsbzM2TnVxU3A5MURKWG4rZ0JCTHEyZ3A0d0N2YjBV?= =?utf-8?B?STRsVkVUM0VaL01hdERicjhnMTdkOTUzKytKekYzb0JYdnN4MUkrUmgxUWor?= =?utf-8?B?OFZRUFhsbCt3NWJaK3JLY2VRSEVDT3RQQnZEemF2YVVHaU5tY3V0Wk9qSzkx?= =?utf-8?B?cXpaVVN6aWVHZjJyV2xvZDd2Y0RBbUQxV3F4eFhaV2tneFdUZHFjaHlXVFN0?= =?utf-8?B?MU96cU9WMzB3dno3Y0w2OWEzbXZNd2xoTVJreDA1RjdEeFFFZ1ZTbG1EdXRK?= =?utf-8?B?Q0NiRWJEKzkxNVFkQ01GOU5ybVZnMStXQWw4Mys1amRYTkhrSHl3ekxaWFlV?= =?utf-8?B?S1NRT21JcHNtYU1hMDlsQWVmYkZyUVdreCt4ZU9IZGcrbTEvemU3TGdSSkV1?= =?utf-8?B?d3JYMXNJOVc2SnVvZndTek1yQUE1M1VJZkhtMG0vY3d5T0crNnhZeElVbnlL?= =?utf-8?B?cWtJNzN0b1U1WmlPWFhuMHRkV0hmRWxFcWFWSkpQMkswVVVIdThBY053Wlhr?= =?utf-8?B?UzM4cTJtZjBZTHV1Q2xLWHVVRXA4bUxUa3JMVndtY1FNRlhQcnRqUjF6Z2pi?= =?utf-8?B?dEVxYTRIdmdwU0loSXZsQ0dibktwTlBRVWtkSFBVY3FwZWQxQ1NRekVKNUdB?= =?utf-8?B?ejY1OXh5YjljUExVQmk3bmg0NWVoM1hyL3NQVHl2NGRyTCt0cUphUFZoQlhu?= =?utf-8?B?NUpwY0F4a1U0TlVPOEFnSXpUdnNvb28wUUtNelpPeldsZGlEZVYzRzUvbnVp?= =?utf-8?B?enNIT1FSRUhEcXg2WnBBMnVSanp4bTlDS2lTZ3J2TTA0QWdtSVE2Yk93L0pa?= =?utf-8?B?WUtSdGFTWFdEQUh0cmpNY3U5U3dJQjQyeU5OWW04WEhYeHhRVWRZWFdNK0x3?= =?utf-8?B?SGFuU0hPN1AycDhJY2xRbmEzRlJtTHdDOUJ1WkZzZ250dld4dnU2UGIxdGZy?= =?utf-8?B?Q014Z20wWnhwcnBzMG8rWUlhZFRFS09TbHRGVnMzK2VERDh4T3NvbktUMFhW?= =?utf-8?B?U2ZKaEtYL0JDeXdGNUwrdXNvNnY2V25GN0V0TjFKYm0zaGlTaHZqckNwd0FO?= =?utf-8?B?QmlEK1UzMXV3N1VXWHR3Zz09?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <F9841A4BA6FFBF4790C3EBFF26732DFB@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4217.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 623170cc-bb73-460d-1f36-08d8f91cfb09
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2021 16:56:53.7535 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2tantvqYO1zwgJwrjoh996QoygpmWaK4AzZOekQ3l7Xw3fBJYLA/7mbFHJ2cSAemkCGclKcU5fjTMXACyPB4MNYFWlmjhChKPrJ2AhmqY6srj8UAcXLvnShLwwh4NpBL
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2345
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/J7MCWo71XkcwzGnJP1KMMIwbJN0>
Subject: Re: [Cbor] CDDL in draft-ietf-acme-star-delegation-07
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 16:57:03 -0000

VGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgdGhlIHN1cGVyIHF1aWNrIGFuZCByaWdvcm91cyByZXZp
ZXcgQ2Fyc3RlbiEgVGhpcyBpcyBleHRyZW1lbHkgaGVscGZ1bCwgSSB3aWxsIHBvaW50IHRvIHlv
dXIgY29tbWVudHMgaW50byBteSBiYWxsb3QuDQoNCkZyYW5jZXNjYQ0KDQrvu79PbiAwNi8wNC8y
MDIxLCAxNzo0NiwgIkNCT1Igb24gYmVoYWxmIG9mIENhcnN0ZW4gQm9ybWFubiIgPGNib3ItYm91
bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgY2Fib0B0emkub3JnPiB3cm90ZToNCg0KICAgIEhp
IEZyYW5jZXNjYSwNCg0KICAgIGhlcmUgYXJlIGEgZmV3IGNvbW1lbnRzLg0KDQogICAgKDEpDQog
ICAgVGhlIGpzb24tc2NoZW1hLm9yZyBkZWZpbml0aW9uIHVzZXMgb25lT2YsIHdoaWNoIHNob3Vs
ZCBuZXZlciBiZSB1c2VkIChhbnlPZiBpcyB1c3VhbGx5IHdoYXQgaXMgYWN0dWFsbHkgbWVhbnQ7
IHRoaXMgaXMgYSB3ZWxsLWtub3duIHByb2JsZW0gaW4gdGhlIGpzb24tc2NoZW1hLm9yZyB2b2Nh
YnVsYXJ5KS4NCg0KICAgICgyKQ0KICAgIGtleXR5cGVzIGlzIG1pc3NpbmcgYSBtaW5JdGVtcz0x
Lg0KDQogICAgKDMpDQogICAgVGhlIHJlZ2V4cCBmb3Ig4oCcb2lk4oCdIChpbiBib3RoIEpTTyBh
bmQgQ0RETCkgaXMgcXVpdGUgcGVybWlzc2l2ZSB3aXRoIHJlc3BlY3QgdG8gbGVhZGluZyB6ZXJv
cy4gIEl0IGlzIHJhdGhlciB1bnVzdWFsIHRvIGhhdmUgbGVhZGluZyB6ZXJvZXMgKGV4Y2VwdCBm
b3IgYXJjIHplcm8gaXRzZWxmKSBpbiBPSUQgc3RyaW5ncywgc28gdGhlcmUgbWlnaHQgYmUgc29t
ZSBpbnRlcm9wIGlzc3VlcyB3aXRoIHRoYXQuDQoNCiAgICAoNCkgdGhlIGludHJvIHRvIHRoZSBD
RERMIHNob3VsZCBwcm9iYWJseSBtZW50aW9uIHRoYXQgdGhlIG11bHRpcGxlT2Y9OCBvbiB0aGUg
UlNBIGtleSBzaXplIGlzIG5vdCByZWZsZWN0ZWQgaW4gdGhlIENEREwsIG5vciBhcmUgdGhlIGZv
cm1hdD14eHgga2V5d29yZHMgKHdoaWNoIGFyZSBub3QgdGVycmlibHkgd2VsbC1kZWZpbmVkIGlu
IEpTTyBlaXRoZXIpLg0KDQogICAgKDUpIHN1YmplY3RBbHROYW1lLkROUyBpdGVtcyBhbGxvdyDi
gJwq4oCdIGFuZCDigJwqKuKAnSBpbiB0aGUgQ0RETCBmb3JtIGJ1dCBtaWdodCBub3QgaW4gdGhl
IEpTTyBmb3JtIChmb3JtYXQ9aG9zdG5hbWUpLg0KDQogICAgQ0RETCBTdHlsZSBuaXRzOg0KDQog
ICAgKGEpDQogICAgcnNhS2V5U2l6ZSA9IGludCAuZ2UgMjA0OA0KICAgID0+DQogICAgcnNhS2V5
U2l6ZSA9IHVpbnQgLmdlIDIwNDgNCiAgICBXaGlsZSB0aGVzZSBtZWFuIHRoZSBzYW1lIGluIENE
REwsIGNvbnZlcnRlcnMgc3VjaCBhcyBDRERMLVlBTkcgY29udmVydGVycyBjb3VsZCBwdXQgaW4g
ZGlmZmVyZW50IHVuZGVybHlpbmcgYnVpbHQtaW4gZGF0YSB0eXBlcywgYW5kIHVpbnQgaXMgYWN0
dWFsbHkgdGhlIGJhc2ljIHR5cGUgZm9yIGEgc2l6ZSBpbiBiaXRzLg0KDQogICAgKGIpDQogICAg
VGhlcmUgYXJlIGEgbnVtYmVyIG9mIOKAnDEq4oCdIG9jY3VycmVuY2UgcXVhbGlmaWVycyB0aGF0
IG1pZ2h0IGJlIHNsaWdodGx5IG1vcmUgcmVhZGFibGUgYXMg4oCcK+KAnS4gDQoNCiAgICAoYykN
CiAgICByZWd0ZXh0LW9yLXdpbGRjYXJkIGNvdWxkIGJlIHNpbXBsaWZpZWQgYnkgbWFraW5nIHVz
ZSBvZiBwcmlvcml0aXplZCBjaG9pY2UgKEFwcGVuZGl4IEEgb2YgUkZDIDg2MTApLiAgT2YgY291
cnNlLCB0aGUgY3VycmVudCBmb3JtIGlzIGVhc2llciB0byB0cmFuc2xhdGUgaW50byBvdGhlciBz
cGVjaWZpY2F0aW9uIGZvcm1hdHMgKHdoaWNoIGFjdHVhbGx5IHdhc27igJl0IGRvbmUgZm9yIHRo
ZSBKU08gZm9ybSksIHNvIHRoaXMgaXMganVzdCBhIG5vdGUuICANCg0KICAgIChkKQ0KICAgIFRo
ZSBub24tZW1wdHkgb2JqZWN0IHJlcXVpcmVtZW50IChKU086IG1pblByb3BlcnRpZXM9MSkgY291
bGQgYmUgc3RhdGVkIGluIENEREwgYXMNCg0KICAgICh74oCm4oCmfSkgLmFuZCAoeyArIGFueSA9
PiBhbnkgfSkNCg0KICAgIFRvIHJlZHVjZSBub2lzZSwgYSBnZW5lcmljIGNvdWxkIGJlIGRlZmlu
ZWQ6DQoNCiAgICBub24tZW1wdHk8TT4gPSAoTSkgLmFuZCAoeyArIGFueSA9PiBhbnkgfSkNCg0K
ICAgIOKApmFuZCB1c2VkOg0KDQogICAgZGlzdGluZ3Vpc2hlZE5hbWUgPSBub24tZW1wdHk8ew0K
ICAgICAgPyBjb3VudHJ5OiByZWd0ZXh0LW9yLXdpbGRjYXJkDQogICAgLi4uDQogICAgfT4NCg0K
ICAgIFRoZXJlIGlzIG5vdCBhIGxvdCBvZiB0b29sIHN1cHBvcnQgZm9yIC5hbmQsIHNvIEkgYW0g
bm90IGdvaW5nIHRvIHB1c2ggZm9yIHRoaXMsIGJ1dCBpdCBzdXJlIHdvcmtzIGZvciBtZS4NCg0K
ICAgIEdyw7zDn2UsIENhcnN0ZW4NCg0KDQoNCiAgICA+IE9uIDIwMjEtMDQtMDYsIGF0IDEyOjE4
LCBGcmFuY2VzY2EgUGFsb21iaW5pIDxmcmFuY2VzY2EucGFsb21iaW5pPTQwZXJpY3Nzb24uY29t
QGRtYXJjLmlldGYub3JnPiB3cm90ZToNCiAgICA+IA0KICAgID4gQ0RETCBleHBlcnRzLA0KICAg
ID4gDQogICAgPiBJIGFtIHJlYWNoaW5nIG91dCBiZWNhdXNlIGRyYWZ0LWlldGYtYWNtZS1zdGFy
LWRlbGVnYXRpb24tMDcgaXMgaW4gSUVTRyByZXZpZXcsIGFuZCBpdCBjb250YWlucyBzb21lIG5v
cm1hdGl2ZSBDRERMLCBhY2NvbXBhbmllZCBieSBub24tbm9ybWF0aXZlIEpTT04gc2NoZW1hIGFs
dGVybmF0aXZlLCB3aGljaCBJIGRvbid0IHRoaW5rIGdvdCBhbnkgcmV2aWV3cyBmcm9tIChvdGhl
ciB0aGFuIGF1dGhvcnMpIENEREwgZm9sa3MuIEkgaGF2ZSBwZXJzb25hbGx5IGNoZWNrZWQgdGhl
IENEREwgdmlhIHRvb2xzLCBidXQgYW5vdGhlciBzZXQgb2YgZXllcyBsb29raW5nIHdvdWxkIGJl
IGdyZWF0Lg0KICAgID4gDQogICAgPiBJZiB5b3UgaGF2ZSBhIHNlY29uZCB0byB0YWtlIGEgbG9v
ayBhdCBpdCwgYWQgc2VuZCBhbnkgZmVlZGJhY2sgYmVmb3JlIHRvbW9ycm93LCBJIHdvdWxkIGJl
IHZlcnkgZ3JhdGVmdWw6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJh
ZnQtaWV0Zi1hY21lLXN0YXItZGVsZWdhdGlvbi0wNyNhcHBlbmRpeC1CIA0KICAgID4gDQogICAg
PiAoWWVzLCB0aGlzIHdpbGwgYmVjb21lIHBhcnQgb2YgdGhlIEFSVCBBcmVhIFJldmlldyBUZWFt
IGFyZWEgb2YgY29tcGV0ZW5jZSwgYW5kIHlvdSBhcmUgdmVyeSB3ZWxjb21lIHRvIHRha2UgcGFy
dCBpbiB0aGF0IGRpc2N1c3Npb24gaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21z
Zy9hcnQvbFpEOG9tbVpBeHFTVEo0M1laLVJLN2JMNE13LyApDQogICAgPiANCiAgICA+IFRoYW5r
cywNCiAgICA+IEZyYW5jZXNjYQ0KICAgID4gDQogICAgPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgID4gQ0JPUiBtYWlsaW5nIGxpc3QNCiAgICA+
IENCT1JAaWV0Zi5vcmcNCiAgICA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vY2Jvcg0KDQogICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCiAgICBDQk9SIG1haWxpbmcgbGlzdA0KICAgIENCT1JAaWV0Zi5vcmcNCiAgICBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Nib3INCg0K


From nobody Tue Apr  6 09:59:46 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1823A28FE; Tue,  6 Apr 2021 09:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 hGVVzkn-X3Up; Tue,  6 Apr 2021 09:59:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FCE63A28FC; Tue,  6 Apr 2021 09:59:39 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FFDK53QBDzySH; Tue,  6 Apr 2021 18:59:37 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <161772606961.13833.6830636143413776698@ietfa.amsl.com>
Date: Tue, 6 Apr 2021 18:59:36 +0200
Cc: IETF IoT Directorate <iot-directorate@ietf.org>, cbor@ietf.org, draft-ietf-cbor-tags-oid.all@ietf.org, last-call@ietf.org
X-Mao-Original-Outgoing-Id: 639421175.7483799-db4fa40fb476595ae1f1b8a6e667078a
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3A61CA0-2197-4885-BBD6-CE12D70B7AD8@tzi.org>
References: <161772606961.13833.6830636143413776698@ietfa.amsl.com>
To: Ines Robles <mariainesrobles@googlemail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/2x4slE0Ery_BS1AySM-Qwtsr9AY>
Subject: Re: [Cbor] Iotdir telechat review of draft-ietf-cbor-tags-oid-06
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 16:59:44 -0000

Hi Ines,

thank you for these comments!

Good catch with the 0b010_01001! =20
I should know better (made the same kind of mistake in RFC 7049).

I actually kept in a second expansion of SDNV in Section 2; possibly the =
RFC editor will strike that, but I find it useful.

All the below are now in =
https://github.com/cbor-wg/cbor-oid/commit/9c90d8d

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-04-06, at 18:21, Ines Robles via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Ines Robles
> Review result: Ready with Nits
>=20
> Summary:
>=20
> The document defines CBOR tags for object identifiers (OIDs).  The =
document is
> well written.
>=20
> Few minor questions/comments.
>=20
> Major Issues: None
>=20
> Minor Issues: None
>=20
> Nits:
>=20
> - It would be nice to expand SDNV in section 1.1 instead of Section 2.
>=20
> - Section 3.2 - Figure 4-MIB relative object identifier in CBOR:
>=20
> 0b010_01001 should be 0b010_00011 ? for major type 2, additional =
information 3
> bytes
>=20
> - Section 7.1:
>=20
> -- In order to mention the registry, maybe smth like
>=20
>  to assign the CBOR tags --> to assign in the CBOR tags registry the =
following
>  tags....
>=20
> -- It would be nice to have the table with the same structure as the =
registry
> table (add reference column like in Section 7.2), I think template =
column does
> not apply here.
>=20
> - Section 7.2:
>=20
> -- In order to mention the registry, maybe smth similar as Section =
7.1?
>=20
> Thank you for this document,
>=20
> Ines.
>=20
>=20


From nobody Tue Apr  6 10:19:58 2021
Return-Path: <kio@mothers-arms.co.uk>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 402853A2997 for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 10:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 YUF6cjg3i7cg for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 10:19:54 -0700 (PDT)
Received: from authenticated.a-painless.mh.aa.net.uk (painless-a.thn.aa.net.uk [IPv6:2001:8b0:62::26]) (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 94D133A2994 for <cbor@ietf.org>; Tue,  6 Apr 2021 10:19:54 -0700 (PDT)
Received: from cpc105076-sgyl40-2-0-cust233.18-2.cable.virginm.net ([82.4.24.234] helo=Galaxy-S10e.lan) by painless-a.thn.aa.net.uk with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <kio@mothers-arms.co.uk>) id 1lTpMl-0002kH-Pn; Tue, 06 Apr 2021 18:19:52 +0100
Date: Tue, 06 Apr 2021 18:19:47 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <CAM70yxDJ8fNBPWLtheiWKvvpKUayw0ueuNtAbnd8BsVWV8gKMg@mail.gmail.com>
References: <CAM70yxDJ8fNBPWLtheiWKvvpKUayw0ueuNtAbnd8BsVWV8gKMg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----FVD6AO01LXUP2U03ARXMNCWNC9SZEE"
Content-Transfer-Encoding: 7bit
To: cbor@ietf.org,Emile Cormier <emile.cormier.jr@gmail.com>
From: Kio Smallwood <kio@mothers-arms.co.uk>
Message-ID: <161ED597-9822-41BC-9B1B-311DBBD26BE6@mothers-arms.co.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/2-XFOFo0dyyj8eSrCWJfuGbLelE>
Subject: Re: [Cbor] Consolidated set of tags for containers
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 17:19:56 -0000

------FVD6AO01LXUP2U03ARXMNCWNC9SZEE
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

I'm quite happy with this=2E Especially the use of abstract data types=2E=
=20

I would like to add that Sets already have a tag of 258

Would it be worth considering how to handle multiple tags that fulfil the =
same role e=2Eg=2E tag 258 and 144?

Cheers=2E=20
Kio



On 19 March 2021 00:27:53 GMT, Emile Cormier <emile=2Ecormier=2Ejr@gmail=
=2Ecom> wrote:
>I branched my consolidated map tags proposal to include tags for
>list-like
>containers=2E This now lives on the "with-lists" branch on my GitHub
>repo=2E
>With the addition of list-like containers, the proposal now contains
>tags
>for representing containers like lists, sets and bags=2E
>
>https://github=2Ecom/ecorm/cbor-map-like/blob/with-lists/README=2Emd
>
>Summary of changes:
>
>* Added "Category" column for either "Dictionary" or "Collection"
>
>* Added dictionaries with arbitrary keys and uniform values to make
>decoding the traits less insane=2E This increases the total number of
>tags
>from 20 to 24=2E
>
>* Removed programming languages section in favor of abstract data types
>that model each tag=2E Much less maintenance this way=2E
>
>I await your comments, critiques, and questions=2E

--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
------FVD6AO01LXUP2U03ARXMNCWNC9SZEE
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>I'm quite happy with this=2E Especially the use of=
 abstract data types=2E <br><br>I would like to add that Sets already have =
a tag of 258<br><br>Would it be worth considering how to handle multiple ta=
gs that fulfil the same role e=2Eg=2E tag 258 and 144?<br><br>Cheers=2E <br=
>Kio<br><br><br><br><div class=3D"gmail_quote">On 19 March 2021 00:27:53 GM=
T, Emile Cormier &lt;emile=2Ecormier=2Ejr@gmail=2Ecom&gt; wrote:<blockquote=
 class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-left: 1=
px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir=3D"ltr"><div>I branched my consolidated map tags proposal to incl=
ude tags for list-like containers=2E This now lives on the "with-lists" bra=
nch on my GitHub repo=2E With the addition of list-like containers, the pro=
posal now contains tags for representing containers like lists, sets and ba=
gs=2E</div><div><br></div><div><a href=3D"https://github=2Ecom/ecorm/cbor-m=
ap-like/blob/with-lists/README=2Emd">https://github=2Ecom/ecorm/cbor-map-li=
ke/blob/with-lists/README=2Emd</a></div><div><br></div><div>Summary of chan=
ges:</div><div><br></div><div>* Added "Category" column for either "Diction=
ary" or "Collection"</div><div><br></div><div>* Added dictionaries with arb=
itrary keys and uniform values to make decoding the traits less insane=2E T=
his increases the total number of tags from 20 to 24=2E</div><div><br></div=
><div>* Removed programming languages section in favor of abstract data typ=
es that model each tag=2E Much less maintenance this way=2E</div><div><br><=
/div><div>I await your comments, critiques, and questions=2E<br></div></div=
>
</blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail=2E=
 Please excuse my brevity=2E</body></html>
------FVD6AO01LXUP2U03ARXMNCWNC9SZEE--


From nobody Tue Apr  6 12:07:57 2021
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E4F3A2CC3; Tue,  6 Apr 2021 12:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com
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 Gf0JtiSEthOc; Tue,  6 Apr 2021 12:07:49 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FDBA3A2CC0; Tue,  6 Apr 2021 12:07:48 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id u29so8364036vsi.12; Tue, 06 Apr 2021 12:07:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M3mj9xUE92ahhN0CMAruJtgy63J9af6uqFvZ9hyEnh4=; b=otnwfQNAq85zoUfBfRV+pOiXvppdVhTdST/w0MFnjMOOBw7qY9daOir7oF384uaxEk llSyES6OymCSA0slQyh1Bn49psT3mXcXHnymzkl4Fya7wKvo4g1ffVRqgdlKHVcbRdUR tFK5kk1exT6K4oWbn6JayD207rPpJnMC0hJaPiQsjB60g5eVm+QoyZyfasa/cTS4mrr7 p4e+CeG26vQ93S2XXzrJgcm36h4jVlTtVMDHjNKjarVh9B1vNwvqLDAaUivrjIv7oPHG FSu5Rz7pP7oIfsQrtptRIo5+9i83xdb1AiCWNZ/ZiNcp7cv2ii6KkbuURrJlS5RYYJBo xiXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M3mj9xUE92ahhN0CMAruJtgy63J9af6uqFvZ9hyEnh4=; b=dYcU1dtA7MAwoRfDYzkU3F13/WI60OSaKLni5Rrsy6F6luIv8B82CDqeHuDQbwq8kr xgf8n2pv/cOtpV7COUDb5PCASGQJ2ePJCHloFG1ftSX+bi1JgXhInTNmiEcRPA05nOrY eaknJ4IpAufmoWuh5vIhBr2orrQHhghhGEvazeaBfDkdpn61ajFESTU7Mney4uXyKd0g t5fXrvl430olk89Ad9EQrTv8HnWwP3lL7FIJKmB/vz0ErqGFg0aCiP/9ufzqibXPlgdY SZgjI/Gc0uteR8YGl/knu9BNYXg01SzhzIDmja7FPUQ00VN59b8DuSMGxjD1cjw+PI8z 6JMA==
X-Gm-Message-State: AOAM530KEOpFT/vwdRDJfvD0sXA/wjGoV19atKWdyWlnMeQY3Z9GJ6lN oJq6AFdt6NjwAP2GSdxg81pF1DSmJHYxcAKcEUKcc4wdoUWhOw==
X-Google-Smtp-Source: ABdhPJx4q0msMVjzIVYEYRv05BvHYxZLLWy46Ookgigs1LD9XD9d+AYkro294xsAM+/zo2WqwkUpHLBqU090JEjPSIg=
X-Received: by 2002:a67:ef0d:: with SMTP id j13mr19210861vsr.3.1617736067231;  Tue, 06 Apr 2021 12:07:47 -0700 (PDT)
MIME-Version: 1.0
References: <161772606961.13833.6830636143413776698@ietfa.amsl.com> <D3A61CA0-2197-4885-BBD6-CE12D70B7AD8@tzi.org>
In-Reply-To: <D3A61CA0-2197-4885-BBD6-CE12D70B7AD8@tzi.org>
From: Ines  Robles <mariainesrobles@googlemail.com>
Date: Tue, 6 Apr 2021 22:07:11 +0300
Message-ID: <CAP+sJUe4MWhzGtfwpy-qUW3OPHv_1KLGaqC3-sj_Kzo8Yq7mFw@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: IETF IoT Directorate <iot-directorate@ietf.org>, cbor@ietf.org,  draft-ietf-cbor-tags-oid.all@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a0b49805bf5287ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/REAtH0T7dkP02s7LBKssOJn19QA>
Subject: Re: [Cbor] Iotdir telechat review of draft-ietf-cbor-tags-oid-06
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 19:07:55 -0000

--000000000000a0b49805bf5287ea
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you very much Carsten for addressing my comments

Liebe Gr=C3=BC=C3=9Fe,

Ines

On Tue, Apr 6, 2021 at 7:59 PM Carsten Bormann <cabo@tzi.org> wrote:

> Hi Ines,
>
> thank you for these comments!
>
> Good catch with the 0b010_01001!
> I should know better (made the same kind of mistake in RFC 7049).
>
> I actually kept in a second expansion of SDNV in Section 2; possibly the
> RFC editor will strike that, but I find it useful.
>
> All the below are now in
> https://github.com/cbor-wg/cbor-oid/commit/9c90d8d
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
> > On 2021-04-06, at 18:21, Ines Robles via Datatracker <noreply@ietf.org>
> wrote:
> >
> > Reviewer: Ines Robles
> > Review result: Ready with Nits
> >
> > Summary:
> >
> > The document defines CBOR tags for object identifiers (OIDs).  The
> document is
> > well written.
> >
> > Few minor questions/comments.
> >
> > Major Issues: None
> >
> > Minor Issues: None
> >
> > Nits:
> >
> > - It would be nice to expand SDNV in section 1.1 instead of Section 2.
> >
> > - Section 3.2 - Figure 4-MIB relative object identifier in CBOR:
> >
> > 0b010_01001 should be 0b010_00011 ? for major type 2, additional
> information 3
> > bytes
> >
> > - Section 7.1:
> >
> > -- In order to mention the registry, maybe smth like
> >
> >  to assign the CBOR tags --> to assign in the CBOR tags registry the
> following
> >  tags....
> >
> > -- It would be nice to have the table with the same structure as the
> registry
> > table (add reference column like in Section 7.2), I think template
> column does
> > not apply here.
> >
> > - Section 7.2:
> >
> > -- In order to mention the registry, maybe smth similar as Section 7.1?
> >
> > Thank you for this document,
> >
> > Ines.
> >
> >
>
>

--000000000000a0b49805bf5287ea
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you very much Carsten for addressing my comments<div=
><br></div><div>Liebe Gr=C3=BC=C3=9Fe,</div><div><br></div><div>Ines</div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Tue, Apr 6, 2021 at 7:59 PM Carsten Bormann &lt;<a href=3D"mailto:cabo@tz=
i.org">cabo@tzi.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">Hi Ines,<br>
<br>
thank you for these comments!<br>
<br>
Good catch with the 0b010_01001!=C2=A0 <br>
I should know better (made the same kind of mistake in RFC 7049).<br>
<br>
I actually kept in a second expansion of SDNV in Section 2; possibly the RF=
C editor will strike that, but I find it useful.<br>
<br>
All the below are now in <a href=3D"https://github.com/cbor-wg/cbor-oid/com=
mit/9c90d8d" rel=3D"noreferrer" target=3D"_blank">https://github.com/cbor-w=
g/cbor-oid/commit/9c90d8d</a><br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
<br>
&gt; On 2021-04-06, at 18:21, Ines Robles via Datatracker &lt;<a href=3D"ma=
ilto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&gt; wrote:<br=
>
&gt; <br>
&gt; Reviewer: Ines Robles<br>
&gt; Review result: Ready with Nits<br>
&gt; <br>
&gt; Summary:<br>
&gt; <br>
&gt; The document defines CBOR tags for object identifiers (OIDs).=C2=A0 Th=
e document is<br>
&gt; well written.<br>
&gt; <br>
&gt; Few minor questions/comments.<br>
&gt; <br>
&gt; Major Issues: None<br>
&gt; <br>
&gt; Minor Issues: None<br>
&gt; <br>
&gt; Nits:<br>
&gt; <br>
&gt; - It would be nice to expand SDNV in section 1.1 instead of Section 2.=
<br>
&gt; <br>
&gt; - Section 3.2 - Figure 4-MIB relative object identifier in CBOR:<br>
&gt; <br>
&gt; 0b010_01001 should be 0b010_00011 ? for major type 2, additional infor=
mation 3<br>
&gt; bytes<br>
&gt; <br>
&gt; - Section 7.1:<br>
&gt; <br>
&gt; -- In order to mention the registry, maybe smth like<br>
&gt; <br>
&gt;=C2=A0 to assign the CBOR tags --&gt; to assign in the CBOR tags regist=
ry the following<br>
&gt;=C2=A0 tags....<br>
&gt; <br>
&gt; -- It would be nice to have the table with the same structure as the r=
egistry<br>
&gt; table (add reference column like in Section 7.2), I think template col=
umn does<br>
&gt; not apply here.<br>
&gt; <br>
&gt; - Section 7.2:<br>
&gt; <br>
&gt; -- In order to mention the registry, maybe smth similar as Section 7.1=
?<br>
&gt; <br>
&gt; Thank you for this document,<br>
&gt; <br>
&gt; Ines.<br>
&gt; <br>
&gt; <br>
<br>
</blockquote></div>

--000000000000a0b49805bf5287ea--


From nobody Tue Apr  6 13:35:34 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0B93A2FAE for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 13:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ETFRUBvEQkPh for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 13:35:29 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F56D3A2FAD for <cbor@ietf.org>; Tue,  6 Apr 2021 13:35:29 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id ep1-20020a17090ae641b029014d48811e37so69489pjb.4 for <cbor@ietf.org>; Tue, 06 Apr 2021 13:35:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=8vqogTDrHkXxCNfrbrnrgXU7JGkULFt3j3C1Kgt/fKc=; b=h0/GBYozQB0ek04OCOHNlhIiUnpieqvtdebL3v27/XRXHjD/OKpTBKH23vmRNLwzya xLhAUHLQ6rmkJCCEOaTz3K0khe0HLB1QDagu6eT0YsoKLpAzPgCsEWklmP3HGFi51FeB R09JT8Z/y8sQKFrIF95h1T1Y0GaEHjnWYYHV7bpeJTBTjSdEe8nkDEY66urbHwPLxdpv hdccFn60bcMw60Fs+uDXke9DkE7B/WA0fYmCZGgnAeo7LLH7kcgM6enNSpw6l/aSxgrb voCDLb5Gn0qDdxnaYht1svmZbGj0lJGdhu65OCeBe1VktZM2BERLMJuUwg0dlGPioSVN UJkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8vqogTDrHkXxCNfrbrnrgXU7JGkULFt3j3C1Kgt/fKc=; b=YeBTlOWO+89/VcsTL3kVoHeXGrzeeJIcZjGVEskUdbuyxpO/ZDeu9zhoV07MGcK5uH q04/kNk8WB9uzSe5YsA96CejiK3Z8pY0c2JtSprB+zBTiaoKE8YCb61vx8FGmXVjslnx GMXD2aTuY80ePFZBhgRrrmj1x4w4R0fHUI5fzpTbFc8iWx/ue5/0DDf8z4UYXY9XtLnZ cYxGyXFUA0SqoVfEO6pEHvjDvygDtgy9gzlfY/bM0CuDQs+R1AG3VTiUdsXQGflZsaGs m3jQMU9hsCDdm6x1hUQE4R6l88dlfgJh3yWrFSPeXIQwtD6fYJwvC/GVqNEqjsRLnz+K FTMg==
X-Gm-Message-State: AOAM531E0Rk7f63DPsKNNfMyWW4kLsBP/Trtc0seCHDNytBNeQfxT6oM A8sTQMLGhc8OC4n9n2P5NSMN3k6vdSYZ6mpWaMxAt5iVTETXXg==
X-Google-Smtp-Source: ABdhPJyfsA7/O9aQfLVdmgYRxkMtdIatfOMWq6TdeCLw3C4OLnMQ+f5hqHPWhd2j+JYyu2SZ6O2ZPwPrY0IsfLgf0I0=
X-Received: by 2002:a17:902:59da:b029:e9:3064:7e02 with SMTP id d26-20020a17090259dab02900e930647e02mr7152726plj.9.1617741327783; Tue, 06 Apr 2021 13:35:27 -0700 (PDT)
MIME-Version: 1.0
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Tue, 6 Apr 2021 17:35:17 -0300
Message-ID: <CAM70yxBEvhN9VqbRpMedPMaSjnRf_GQcUAYcfna0kA5=7gRcdw@mail.gmail.com>
To: cbor@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002e5b4305bf53c10e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/lxN8zxiFV2mNKLlbDYw8Ff1eFI0>
Subject: [Cbor] Multiple ways of expressing the same time via draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 20:35:34 -0000

--0000000000002e5b4305bf53c10e
Content-Type: text/plain; charset="UTF-8"

I'm implementing tags 1001 and 1002 in my C++ library to exchange time
points and durations (refer to
https://www.ietf.org/archive/id/draft-bormann-cbor-time-tag-04.html).

I'm in the situation where I''m not sure which is the "expected" way to
encode time as nanoseconds since the Unix epoch. I'm specifically referring
to std::chrono::system_clock::time_point, which is a 64 bit integer. There
are currently three ways I could encode such a value.

1. The whole number of seconds under Key 1, with the remaining nanoseconds
under Key -9.

2. The total number of nanoseconds under Key -9, with a value of zero under
Key 1.

3. The total number of nanoseconds expressed as a Decimal Fraction under
Key 4.

Option #2 is the easiest and most efficient because it doesn't involve a
division/subtraction calculation. However, a receiver that discards Key -9
will end up with zero seconds. At least with option #1, the receiver will
know the number of whole seconds if Key -9 is ignored.

Option #3 requires that the sender and receiver understand Tag 4 (Decimal
Fraction), or at least the concept of decimal fractions within the context
of tags 1001-1003.

I'm guessing that option #1 is the "canonical" way, but I'm not entirely
sure. Some guidance would be appreciated. Perhaps a few words concerning
this should be added to the standard's text?

On the receiving side, my library would ideally handle all three scenarios.
It's on the sending side I'm more concerned about when I need to
interoperate with CBOR decoders other than mine.

I apologize if this has already been discussed before. I'm a bit late to
the CBOR party. :-)

Cheers,
Emile Cormier

--0000000000002e5b4305bf53c10e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;m implementing tags 1001 and 1002 in my C++ lib=
rary to exchange time points and durations (refer to <a href=3D"https://www=
.ietf.org/archive/id/draft-bormann-cbor-time-tag-04.html">https://www.ietf.=
org/archive/id/draft-bormann-cbor-time-tag-04.html</a>).</div><div><br></di=
v><div>I&#39;m in the situation where I&#39;&#39;m not sure which is the &q=
uot;expected&quot; way to encode time as nanoseconds since the Unix epoch. =
I&#39;m specifically referring to std::chrono::system_clock::time_point, wh=
ich is a 64 bit integer. There are currently three ways I could encode such=
 a value.<br></div><div><br></div><div>1. The whole number of seconds under=
 Key 1, with the remaining nanoseconds under Key -9.</div><div><br></div><d=
iv>2. The total number of nanoseconds under Key -9, with a value of zero un=
der Key 1.</div><div><br></div><div>3. The total number of nanoseconds expr=
essed as a Decimal Fraction under Key 4.</div><div><br></div><div>Option #2=
 is the easiest and most efficient because it doesn&#39;t involve a divisio=
n/subtraction calculation. However, a receiver that discards Key -9 will en=
d up with zero seconds. At least with option #1, the receiver will know the=
 number of whole seconds if Key -9 is ignored.</div><div><br></div><div>Opt=
ion #3 requires that the sender and receiver understand Tag 4 (Decimal Frac=
tion), or at least the concept of decimal fractions within the context of t=
ags 1001-1003.</div><div><br></div><div>I&#39;m guessing that option #1 is =
the &quot;canonical&quot; way, but I&#39;m not entirely sure. Some guidance=
 would be appreciated. Perhaps a few words concerning this should be added =
to the standard&#39;s text?</div><div><br></div><div>On the receiving side,=
 my library would ideally handle all three scenarios. It&#39;s on the sendi=
ng side I&#39;m more concerned about when I need to interoperate with CBOR =
decoders other than mine.</div><div><br></div><div>I apologize if this has =
already been discussed before. I&#39;m a bit late to the CBOR party. :-)<br=
></div><div><br></div><div>Cheers,</div><div>Emile Cormier<br></div></div>

--0000000000002e5b4305bf53c10e--


From nobody Tue Apr  6 14:02:22 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9543A30BB for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 14:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 p_TMXzlMO7iS for <cbor@ietfa.amsl.com>; Tue,  6 Apr 2021 14:02:16 -0700 (PDT)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 730B13A30B9 for <cbor@ietf.org>; Tue,  6 Apr 2021 14:02:16 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id ot17-20020a17090b3b51b0290109c9ac3c34so75997pjb.4 for <cbor@ietf.org>; Tue, 06 Apr 2021 14:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=esUDwr7M5RMxtZlIyh+bNfUDkQTLbGt4SrMTwNTZrdg=; b=koDFGqtoYeDWMtVBrksvON69Gn/kHNdRuMWVkjKFCO+t6K+eWaKO8OQUDHzvDVJtzK e30PpI+ebcQk5F6uSTuZJHREAULpxBFVwII7Mtply1qrsjfc/zfLrxrARopyrn3JY0qz tZvu3dzcPttAIt94GWxeitFeGKRgfde+BYtcMpLgbS+3BDczv6B2voOZRA1qhzYGpdw5 JLV/77y0+R9VATiwwYTb5FUa+m1p2P7ZN9mpjmo9TdyxtP2/3ArxB/uVwadlONcxHtXp T94DeGMEfm1HYlsDvfz07p7PNVOHsk+/zU6SurAtNUDBUQoh3Cd+YFuHefD56mMLvXH+ s0CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=esUDwr7M5RMxtZlIyh+bNfUDkQTLbGt4SrMTwNTZrdg=; b=n/50MYgChPy5gqcIZSwuWMW4jHGCcDh7U/A5kgyZlPwGjYf/TndXPg6yvKEdqaUkU6 95O4JUSOlWU7Fx3BkSIJ+qKgW/dM7iJDJjL3M2wI7DVltLuwYcmUQXFXK/W0b/oMSFhn Rf6npoIx0lq9gtLl+zJRJGrS0GQEKiV0xhdz301XMTH9YKKr4UVWVnGqK/CYHO+lWbSA aT3KHtCGv761148u6P2zAEl88xgvvpeSamMf/bd2/6Ag9fiAUVxgr89pATDJzenJA7Ss akiyrLW34x1bY7a7YKoYfolVtSgopi9MFm6Y1Q4DvV0cWqscBLYB0W22hLEEhjCqEebZ ozBQ==
X-Gm-Message-State: AOAM531bvPA1qPdXv54wBjhF3BzYmB3SxQGvj0PJ6um5MmK3nav+1caQ Yo2cbIkSKCzxsBJG0PweDHXcnWhpAS+GSP3/rLFdtItCkq2ugA==
X-Google-Smtp-Source: ABdhPJxdBdKgTA/bJ9BOs/h1Piegz9e+R4vZFs2TdnfgNwqz89o9hHvUjzx+baBVjGghpPnSAxO5cr2JXPvTXWtetnY=
X-Received: by 2002:a17:902:263:b029:e7:35d8:4554 with SMTP id 90-20020a1709020263b02900e735d84554mr106670plc.83.1617742935313; Tue, 06 Apr 2021 14:02:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxDJ8fNBPWLtheiWKvvpKUayw0ueuNtAbnd8BsVWV8gKMg@mail.gmail.com> <161ED597-9822-41BC-9B1B-311DBBD26BE6@mothers-arms.co.uk>
In-Reply-To: <161ED597-9822-41BC-9B1B-311DBBD26BE6@mothers-arms.co.uk>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Tue, 6 Apr 2021 18:02:04 -0300
Message-ID: <CAM70yxBfcSCEwDr1OxWM40G+C7BaxFhyFm0C2PAQ_H3N1dboGA@mail.gmail.com>
To: Kio Smallwood <kio@mothers-arms.co.uk>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ff51fe05bf5420d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/P5qmcg7hGTt7zc0l8894kVQeWx8>
Subject: Re: [Cbor] Consolidated set of tags for containers
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 21:02:21 -0000

--000000000000ff51fe05bf5420d2
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 6, 2021 at 2:19 PM Kio Smallwood <kio@mothers-arms.co.uk> wrote:

> I'm quite happy with this. Especially the use of abstract data types.
>
> I would like to add that Sets already have a tag of 258
>

Thanks! I've added a reference to tag 258 to my draft.
https://github.com/ecorm/cbor-map-like/blob/with-lists/README.md

Would it be worth considering how to handle multiple tags that fulfil the
> same role e.g. tag 258 and 144?
>

I'd say that a decoder should treat them as being synonymous.

One thing that should be considered is removing the tags for uniform keys
and arbitrary values. That would reduce the number of allotted tags from 24
to 20 (in my "with-lists" variant, that is). However, the logic for
decoding each trait would become more complex, as it would no longer be
"one-hot" bit encoding (in EE parlance). A small lookup table could take
care of associating traits with tag values. Such a table would only be 20
bytes if traits are packed into bits.

Cheers,
Emile Cormier

--000000000000ff51fe05bf5420d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Tue, Apr 6, 2021 at 2:19 PM Kio Smallwood &lt;<a href=3D"mailto:k=
io@mothers-arms.co.uk">kio@mothers-arms.co.uk</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><div>I&#39;m quite happy with =
this. Especially the use of abstract data types. <br><br>I would like to ad=
d that Sets already have a tag of 258<br></div></blockquote><div><br></div>=
<div>Thanks! I&#39;ve added a reference to tag 258 to my draft. <a href=3D"=
https://github.com/ecorm/cbor-map-like/blob/with-lists/README.md">https://g=
ithub.com/ecorm/cbor-map-like/blob/with-lists/README.md</a></div><div> <br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Would it be wo=
rth considering how to handle multiple tags that fulfil the same role e.g. =
tag 258 and 144?<br></div></blockquote><div><br></div><div>I&#39;d say that=
 a decoder should treat them as being synonymous.</div><div><br></div><div>=
One thing that should be considered is removing the tags for uniform keys a=
nd arbitrary values. That would reduce the number of allotted tags from 24 =
to 20 (in my &quot;with-lists&quot; variant, that is). However, the logic f=
or decoding each trait would become more complex, as it would no longer be =
&quot;one-hot&quot; bit encoding (in EE parlance). A small lookup table cou=
ld take care of associating traits with tag values. Such a table would only=
 be 20 bytes if traits are packed into bits.<br></div><div><br></div><div>C=
heers,</div><div>Emile Cormier</div></div></div>

--000000000000ff51fe05bf5420d2--


From nobody Wed Apr  7 01:20:36 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A69073A109D; Wed,  7 Apr 2021 01:20:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-tags-oid@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com, christian@amsuess.com, mariainesrobles@googlemail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <161778363066.21259.2439157676104887014@ietfa.amsl.com>
Date: Wed, 07 Apr 2021 01:20:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/KfBb8JVc5Krz9CE2stXIQwFr5mE>
Subject: [Cbor] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-cbor-tags-oid-06=3A_=28with_COMMENT=29?=
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 08:20:31 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-cbor-tags-oid-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put in this document.

Thank you also for your reply to Ines Robles' review for the IoT directorate:
https://datatracker.ietf.org/doc/review-ietf-cbor-tags-oid-06-iotdir-telechat-robles-2021-04-06/

Regards

-éric




From nobody Wed Apr  7 01:21:41 2021
Return-Path: <evyncke@cisco.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD0C3A10A3; Wed,  7 Apr 2021 01:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.616
X-Spam-Level: 
X-Spam-Status: No, score=-9.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=kFtCNP2K; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=s/KLSrtG
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 dqIFWANP2kvD; Wed,  7 Apr 2021 01:21:29 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFFB53A10A0; Wed,  7 Apr 2021 01:21:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11677; q=dns/txt; s=iport; t=1617783688; x=1618993288; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=wT0ssSenh+wvpBA4h2UPchQWcZ8IhcphQTXWUQHjEYg=; b=kFtCNP2Kwe9bk4ccLEYIVI0KsOWD6a8VwJO5VTnGfpq58ZViLzfLF0IU CuE22ocVK9e1fO2CgbIH86qoDmu5ukiuwlbVghM36OLrvOUil22y02uyO wXU6rbNod9CIbT8bETHOuFTk1fgft1J8sa5foN5+ol99XbfOOThpCMN/W w=;
IronPort-PHdr: =?us-ascii?q?A9a23=3AGIlhZxRZnqZH0WxWKZTYiDQ6vNpso0HLVj590?= =?us-ascii?q?bIulq5Of6K//p/rIE3Y47B3gUTUWZnAg9pIjuPMuObhVHAOp5GbvyNKfJ9NU?= =?us-ascii?q?koDjsMb10wlDdWeAEL2ZPjtc2QhHctEWVMkmhPzMUVcFMvkIVGHpHq04G0eH?= =?us-ascii?q?xzlPkx0K/j7XInIgJf/2+W74ZaGZQJOiXK0aq9zKxPjqwLXu4EWjIJuJ7x3x?= =?us-ascii?q?AHOpy5Dev9dwiVjIlfA9ys=3D?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3AyWS5T6Mq6d5SUMBcT4Px55DYdL4zR+YMi2?= =?us-ascii?q?QD/3taDTRIb82VkN2vlvwH1RnyzA0cQm0khMroAsi9aFvm39pQ7ZMKNbmvGD?= =?us-ascii?q?PntmyhMZ144eLZrQHIMxbVstRQ3aIIScdDIfX7B1RikILe6A63D94vzLC8gd?= =?us-ascii?q?+VrM31pk0dKj1CQadm8gt/F0K/Gkp5WAFJCfMCZeShz+BAoCetfmlSU9SjCh?= =?us-ascii?q?A+Lqn+jvDotLajWx4JABY79BKD5AnJ1JfWGwWVty1uKA9n7qwl9QH+4mnEz4?= =?us-ascii?q?Wl98q20xrNk1LUhq4m5OfJ7vtmKIiyhtMOKjPq4zzYJLhJf7GZpjg6rKWOxT?= =?us-ascii?q?8R4aPxiiwtNchy9H/dF1vdyXCGtmWQs0dN11bYxVCVmnflq8DiLQhKdvZpv5?= =?us-ascii?q?5TcRfS9iMbzbdB+Z9LxG6Qut52Ch7NjU3GlqD1fixqjUa9rD4el/cShRVkIP?= =?us-ascii?q?IjQYJWxLZvmH99IdMlJmbX+YonGO5hAIX3//BNa26XaHjfoy1G3MGsdm5bJG?= =?us-ascii?q?bEfmEy/uiulxRGlnFwyEUVgOYFmG0byZ47Q55Yo8zZL6VTkq1URMN+V9M+OM?= =?us-ascii?q?4xBe+MTkDdSxPFN2yfZX79ErscBn7Lo5nrpJI4+f+tY55N6JcpgpzOXBd5uA?= =?us-ascii?q?cJCgfTIPzL+KcO3gHGQW27Uzio4NpZ/YJFtrr1Q6euPjaETFwojsu8s/QSCs?= =?us-ascii?q?DWQJ+ISdVrKs6mCVGrNZdC3gX4VZUXA2IZStcpttEyXE/Los+jEPytisXrNN?= =?us-ascii?q?LoYJb9GzctXW3yRlEZWiLoGclG5ke3HnvxgB3bXWLxalXylKgASZTyzqw28s?= =?us-ascii?q?wgJ4dMug8ahRCS/ceQMwBPtaQwYQ95O7PokqSyoGGs5mbW52B1Oh5QZ3wlpI?= =?us-ascii?q?nIYjdvn0snIkn0ebEMt5G0YmZJxkaKIRd5UofLCgJFvk92/qi2NpSUwignB7?= =?us-ascii?q?ucQzqnpkpWgEjPY4YXm6WF68ugR4gxCYw+XrdtUS/REQZupApsoGBfSQMNS0?= =?us-ascii?q?PFDAnygaG9gJF8PpCFS/BMxCOQZe9dszb2qFiVr8BHfAprYxeeFeqsxTsIax?= =?us-ascii?q?URrFtr6KMbiKeHgl+UWBsCqdV9FkZNZmSRCK9BFyKfauxv6+rWUTA1a3uWjj?= =?us-ascii?q?qHjBx2XWzm+ywp9zDcBBzRX+3XCVxAvX0d6ILWyRdfc2WQeF8YUAEmjaR0CX?= =?us-ascii?q?nGtnFv0eWCe6q01C+LZkEfx/wGWQu1Ewc6Phlj3JS+2hKThV+5ZAYb74RrMe?= =?us-ascii?q?rHALs5dbbPnnurNY2TjKkDW+RZ5ZB/KbnVw6M2ePPafw+eNzXjDew1nwSTu3?= =?us-ascii?q?Y+ISFxwUNU28/AyVng7GKi2mQ4DueXKFN6R6sDK9XZ62T/Xf6H3NF4it0y1N?= =?us-ascii?q?HAf1nZe5qDyavNaSREJQ6WqWmqT/swoZQRpLksrtJIbtDmeCqN0GsC0AQ1Lc?= =?us-ascii?q?/ymk9bSKNn4KrZMosqe8AJYSpW8lcgidznFjpljiXmRuslOV09hX7SON2Ep6?= =?us-ascii?q?DFrrciGUWNrgr9M1v3yVwXw97VGy+YkbIKAaM5JmpbLFUm4HN55eWYasneDh?= =?us-ascii?q?6pe+wrxiv1DlatNLtGDK6LFrUbokwkv5WGn+qLezH53w6Vtz1hOa5K+3umR8?= =?us-ascii?q?T3AA/kI58+z/WqfVCXxq2t64qviT2yTz2xYUERn5dEekwddd4rsEhrsKQnli?= =?us-ascii?q?ypDrXqqUckmUZE6T5pllTxypGriV2raX1uIEncmNFKRjFdPXiDkNTd/eWZ3H?= =?us-ascii?q?r75iJZ2ZOrLjYnQvheX94KTob2KC9yKc8f+L6wlpBf9xh+XA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BkAQAHa21g/4kNJK1aHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQGCAQQBAQsBgSIwUQd3WjYxhEKDSAOFOYgrJQOURYR2glMDVAs?= =?us-ascii?q?BAQENAQEoCgIEAQGEUAIXgWACJTcGDgIDAQEMAQEFAQEBAgEGBHEThVANhkQ?= =?us-ascii?q?BAQEBAgEjBBkBATcBBAsCAQYCEQMBAgEnAwICAjAUCQgCBAENBYJxAYF+VwM?= =?us-ascii?q?OIQEOkFOQbQKKH3d/M4EBggQBAQaBMwGDahiCEwMGgTkBgnWEBwEBhk4nHIF?= =?us-ascii?q?JQoETJwwQgl8+gmACAoF+DQmCYTWCK4FYgVYEGCsQIg1QXwUUChGUa4dpjHi?= =?us-ascii?q?QVoELCoMLiWOHHYZIhTQEH6RxlRWLapc/AgQCBAUCDgEBBoFqJIFZcBVlAYI?= =?us-ascii?q?+UBcCDo4fCQMWg06KWXMCNgIGAQkBAQMJfIwVAQE?=
X-IronPort-AV: E=Sophos;i="5.82,203,1613433600";  d="scan'208,217";a="881119358"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Apr 2021 08:21:27 +0000
Received: from mail.cisco.com (xbe-rcd-001.cisco.com [173.37.102.16]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 1378LR8D009995 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Wed, 7 Apr 2021 08:21:27 GMT
Received: from xfe-aln-001.cisco.com (173.37.135.121) by xbe-rcd-001.cisco.com (173.37.102.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.3; Wed, 7 Apr 2021 03:21:27 -0500
Received: from xfe-aln-002.cisco.com (173.37.135.122) by xfe-aln-001.cisco.com (173.37.135.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.3; Wed, 7 Apr 2021 03:21:26 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (173.37.151.57) by xfe-aln-002.cisco.com (173.37.135.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.3 via Frontend Transport; Wed, 7 Apr 2021 03:21:26 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XQzc5UXrQidhhYnzsk72PYTxfunneVOYiLGF6vaqeIVQAf4Nyj2tn5der/LrdIvgHYplwE/QXh5Uf4vzOz94PKEtJLKW+9AL1cUI75nthdXnzExhDjiI/jGLOPlipKMS1yTABtV24Tp2yJI93bWi4kJHYUgQuZaG3PTnmDOqhNNROcW9SCeLfVuMzi5mLiXvUKWA7dfnljX42DidGLjrVufS3Uftm5F6f8xhsia9N3kPq4g6VZ0w5jN+plxm0Ofn2vTWXGgNQ5vYAWfy1APaSafMWSPd0Z2OPFA3teC2qLSHjpPXfTwMAB9G78Zr541H3dY1hCWxCKR6oWsPNl+raQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wT0ssSenh+wvpBA4h2UPchQWcZ8IhcphQTXWUQHjEYg=; b=CiTMIpD+c832dMnM8+OgRgImurOWwc2VQDnh/5PLAQGYVMdNvKKC3CY7aXZOR6n4qTmaGtHUSHQup346GhjkdkZEAUK6r5f+FCVBW8CSp4DMtCbcMFav9t38l99SWVzHh4raTG57fn/dt2QUzkW/r5ZsxLCONKz5g7lEYh5H3BSXRldu5t8hRSYBGzOT+QyTEIDJ6WN+jdDBO9NuOOit17FidUOHqG1nAfGLYrJcpvUTQiySQHJoLH113/f/Ll3lw6ZAzD4+Klge2fHd3Bh0kcGLpaAt2eSsMFV462uFrZEbdR53uZ/SJKDXjUmXX54Df3rmu7ZJfpLTMOOat5v6SA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wT0ssSenh+wvpBA4h2UPchQWcZ8IhcphQTXWUQHjEYg=; b=s/KLSrtG1x0y4cuG7T6dBICF4rATsI3CVXiqQBTk/cyfrwHgLzM5GbW0Gy6tepTfkNpyJTf2/JyccSRZOdkHUkueiNO3fS+eoalCIhheiMTCnxCYCnLBcQvzIBiNDqNCn6neTEkaGISG0fuDWkDeUauZvGnruTacmnvDQT08/DQ=
Received: from PH0PR11MB4966.namprd11.prod.outlook.com (2603:10b6:510:42::21) by PH0PR11MB4872.namprd11.prod.outlook.com (2603:10b6:510:32::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.16; Wed, 7 Apr 2021 08:21:25 +0000
Received: from PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::dcdf:3910:b85d:6eba]) by PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::dcdf:3910:b85d:6eba%7]) with mapi id 15.20.4020.017; Wed, 7 Apr 2021 08:21:25 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Ines Robles <mariainesrobles=40googlemail.com@dmarc.ietf.org>, "Carsten Bormann" <cabo@tzi.org>
CC: "draft-ietf-cbor-tags-oid.all@ietf.org" <draft-ietf-cbor-tags-oid.all@ietf.org>, IETF IoT Directorate <iot-directorate@ietf.org>, "cbor@ietf.org" <cbor@ietf.org>
Thread-Topic: [Iot-directorate] Iotdir telechat review of draft-ietf-cbor-tags-oid-06
Thread-Index: AQHXKwDm229bqHD1f0GXdx5hjM5lNqqntnAAgAAjpoCAAP9tAA==
Date: Wed, 7 Apr 2021 08:21:25 +0000
Message-ID: <BAF905D0-999D-4849-8234-757BF252983B@cisco.com>
References: <161772606961.13833.6830636143413776698@ietfa.amsl.com> <D3A61CA0-2197-4885-BBD6-CE12D70B7AD8@tzi.org> <CAP+sJUe4MWhzGtfwpy-qUW3OPHv_1KLGaqC3-sj_Kzo8Yq7mFw@mail.gmail.com>
In-Reply-To: <CAP+sJUe4MWhzGtfwpy-qUW3OPHv_1KLGaqC3-sj_Kzo8Yq7mFw@mail.gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.47.21031401
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:c0c1:36:38fd:a599:79b8:71b4]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a3cc7990-4041-4932-a981-08d8f99e22be
x-ms-traffictypediagnostic: PH0PR11MB4872:
x-microsoft-antispam-prvs: <PH0PR11MB48721BAEC792F9FEBBD898CEA9759@PH0PR11MB4872.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8UgBUBWpD+s/6DSNOIlOhVy6OdoMXdMI4dNmNyP1cTuXRzxMh4NWyg31GDuBfK4iELcpIgcaY8ZYBxUIiWBM79j5TwnFSA2B+FDlU9NT2y6S9JCEo5D9NNpOjazlxYI0vFI4v3UPsEznOBMFpS0yFJbKw6AMwyGxOtESVxNW3pb98CasDqoYyPU6DBbURoJD1C8uEmayo5R+lx197e8T6t3JqDK92g/zCajF+ACkuOo4Q1KU6gHi9eVC9i4inHsjtWukjfOWZkTWzJiC5G3KoXyHQabUEhHZnT+HUK9yjOkHt6p9vQgIru95xZ7Sc6qW6bW1mOp67rDLghI1OE2E1i4VVBhm1j5egrd1qUldhHN8635gYHlIaXv07mCYox95DqWfj51BIcx6Wwrugv6GvF6Tw5/gxPKZRlvxD6Q79dbK5+h5M6cOM9JBGvgMf8d1CujETxMlzvZtCwxgRzv6N5WQR+iN2ehHnEXYz7hN7qKpbPsQgomkESUHOFHY52z9ZQoWgMUc2IN/mA1T6BpNxH9lLUCl7jVDUsuF37mKVFH+lLboUZcqlaAgEYgLgIYWxtlmvgRo7agGbMtUYEKir7pqw414qF8QF1CK1krV+oU5uhWiWxnXju3T20mJmcL2Aj28E8KsTICBRX3aJ3h6tb5y9TqgSLPFvahIZWhjY25CHRmt6e2YJWnwzaykMnCjmRJtrbkkbsm4xLLjXn6rqF48KDaS9NzZTm30xskorGsZ6oqqvUAobhLCbl6IZpF4qT3ZK15W+4esqIYd+ItwpQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:PH0PR11MB4966.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(346002)(376002)(136003)(39860400002)(396003)(6512007)(2616005)(2906002)(36756003)(86362001)(33656002)(186003)(83380400001)(166002)(71200400001)(6506007)(53546011)(66556008)(64756008)(38100700001)(110136005)(91956017)(5660300002)(66476007)(478600001)(54906003)(4326008)(8936002)(6486002)(8676002)(76116006)(66446008)(66946007)(966005)(316002)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?ZUhoRWZKS1d1K0VRYTJldHZud0dNbmFwN1JMcjBnZjdrVWdrRGFLcXpkN1BW?= =?utf-8?B?QnNSb20zcmlOK2pKL2ZZRWlGNENkQzFrazdJcnNRM3poZmZ0SEtvSVpIOUk2?= =?utf-8?B?MG1ZQXdmWTZxMzE2VW5wVXU5RHdEUVVldWdSeEFNT1ZiYWNYcVkzaVJ6VGVS?= =?utf-8?B?WHIva1dVTFJNdVlIODk1blRTNE12UmFpeUlxdHZMS3hoTnI5aGN4Qm9JYThj?= =?utf-8?B?RDZvZldtVkFyYTNZSWlrMDhBNmRhY3hEdUhRTWZqTEt2c1FublNnQTdBRWtt?= =?utf-8?B?YVFRWDhUYWhTNmdIbldtVkNOWndVSkVlcG5GVkVZa3lvZCtCSEtDSmZxaVh0?= =?utf-8?B?Q0JWdEVVWWRxR2ZKK0h3S1FTZlpKQWlRUmFTbnJIWW9HeUxvclNqUFM5bDhw?= =?utf-8?B?NVBmR1lUZWhWaUh5VEJ6ZlF5WmFFOVpxVDVSSzZWQldxTnZIU0U3L0ZpVjBO?= =?utf-8?B?bmsvMk4zRGxWRnIwZi9CMzlHdHRXeEQ5bllpN2FvMXFQN2swb1dUOEpLczBz?= =?utf-8?B?dVNsOEp4a3diMG0weTY3SmxLSWUzb0lMbUhjNTdYaW5LS0lnWUZmaUppbU5y?= =?utf-8?B?YmZkTGp0MmIvVk1XRzNKS1BkREFDQ21rMU9VcDY1QUw1YTB5VXp0dmV2YXhh?= =?utf-8?B?VURHbkEzYnhxb2R5Q3QvbHFYME9oTi95MmpuazVDMWNNTU1HZlBSOTZoQThU?= =?utf-8?B?L3BTVW1jM1pOYnJBaGxRWkI4T1VLUEpQWXpjSVB5Z21SN1pNeDd3YnR2RXgv?= =?utf-8?B?WFhTRDhhVkJsUVMrN0tBTXJrWWhYb080WDJZTStoY1NOVC9wYWZVc3dGTWZU?= =?utf-8?B?T3NTaHBCbS9OQmxLYjQ0dWZzTTFTcHVQclBVNTVaWTlPZ25RZjNkNDJQRnJ6?= =?utf-8?B?eElkN2xKYzNxbG1seEs5TlZJSUdKMTdMSUVVWW04dURvbHhCZ0xZY1FQMU1H?= =?utf-8?B?YUFSYjN2QlBOZkNSeEk4YjhqZkdHL0FWMnVMWmNUK1lRRDJ4YmNGK004L0FT?= =?utf-8?B?SE9VOTZFQUVKMXdjRGRScXVzeWRjVzNjRmIxSUNuamN3ZExqckZpcnM4V284?= =?utf-8?B?WXFmQXNwTTdxRkNMVG5kMjB1NkZaL2Rnb21xSTFiY3Zoek01YzIrZUdTUjBG?= =?utf-8?B?L1U4NEtVU1Bmb1FrNy8rTXJ6SUxwa0p4cGVrQXJneU5zTk56dndnZWNzeGxO?= =?utf-8?B?ZmxZM3puaUlwNzZwUVFUMjBaSmRiV2FkbzZid3NQR0NxVE5TanhaWEMzcmwy?= =?utf-8?B?VkhmT1p5cGtzQThGejlWdkNLZ3JGLzRDYlF0dk5KdzNRUmt3YloyZDgwbUsx?= =?utf-8?B?U3BFM1pJUTEwVG5zWjRaUldjQXFEVkpZK09OLzFqUVM2ZGFQcGx5bElNNVJB?= =?utf-8?B?VHVmaXNPdGcrSjR5Y1NlY0RDcXA0SmhWQ25mQXJIa1ZqOFRaL29qNnFqdW1w?= =?utf-8?B?Nm5UTTB0K1NqUk0yWXFZSjRyRlQvSkg4dmxaMVNBclJCb1duUXNneTdXblo2?= =?utf-8?B?WFNFV2NjbmNKVFF5aktkQ3VWTU5mUGxvQUt3RHhOOFlhaDlhUFF1MXBWRTd4?= =?utf-8?B?U3BkT2lXNFJXWmNyUkIvc1hyWXorUGduQXhjRzUycE0xM0pEY0lmeXZpdzgr?= =?utf-8?B?bGpkREFhV2UrSUszUlMvVUJWSU5kdjhrSjYrNDE3S0NmOFhVSDNIb3dMdU1Q?= =?utf-8?B?UUh2MUVBVm95bWN0SzdrZWZnckg0dFpjWjhLbmdPdFhyd2lmZmQwZVZFSE1M?= =?utf-8?B?azh6azJ4ZEQ4a3FoQ3NDZzQ5MEs1WkpVQkVpSUlhUzg4ekhHNVBReWdhcWh1?= =?utf-8?B?WDlnVHhudm1IZ0FIclRWOTJtRGF6ZmdjeTdzWmpqS0hXNzNWNlFWQUNYT1B2?= =?utf-8?Q?1IOYahNiwYfs2?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BAF905D0999D48498234757BF252983Bciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB4966.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a3cc7990-4041-4932-a981-08d8f99e22be
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2021 08:21:25.4561 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jlxh5wEwhpYqHn2njU16m/Tly3hm2UZ2uhgCcR6qlL6Jjh+rVW/l3BB12yFWlkhs8S143N6uVzYQYp/bjPk8rw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB4872
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xbe-rcd-001.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Z5JXjfshnTbMB7UaLjrQa5XZXgs>
Subject: Re: [Cbor] [Iot-directorate] Iotdir telechat review of draft-ietf-cbor-tags-oid-06
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 08:21:35 -0000

--_000_BAF905D0999D48498234757BF252983Bciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmsgeW91IEluZXMgZm9yIHlvdXIgcmV2aWV3IGFuZCBDYXJzdGVuIGZvciB5b3VyIHByb21w
dCByZXBseS4NCg0KSSBqdXN0IGJhbGxvdGVkIGEg4oCYbm8gb2JqZWN0aW9u4oCZIGV2YWx1YXRp
b24uDQoNClJlZ2FyZHMNCg0KLcOpcmljDQoNCkZyb206IElvdC1kaXJlY3RvcmF0ZSA8aW90LWRp
cmVjdG9yYXRlLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBJbmVzIFJvYmxlcyA8bWFy
aWFpbmVzcm9ibGVzPTQwZ29vZ2xlbWFpbC5jb21AZG1hcmMuaWV0Zi5vcmc+DQpEYXRlOiBUdWVz
ZGF5LCA2IEFwcmlsIDIwMjEgYXQgMjE6MDgNClRvOiBDYXJzdGVuIEJvcm1hbm4gPGNhYm9AdHpp
Lm9yZz4NCkNjOiAiZHJhZnQtaWV0Zi1jYm9yLXRhZ3Mtb2lkLmFsbEBpZXRmLm9yZyIgPGRyYWZ0
LWlldGYtY2Jvci10YWdzLW9pZC5hbGxAaWV0Zi5vcmc+LCBJRVRGIElvVCBEaXJlY3RvcmF0ZSA8
aW90LWRpcmVjdG9yYXRlQGlldGYub3JnPiwgImxhc3QtY2FsbEBpZXRmLm9yZyIgPGxhc3QtY2Fs
bEBpZXRmLm9yZz4sICJjYm9yQGlldGYub3JnIiA8Y2JvckBpZXRmLm9yZz4NClN1YmplY3Q6IFJl
OiBbSW90LWRpcmVjdG9yYXRlXSBJb3RkaXIgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYt
Y2Jvci10YWdzLW9pZC0wNg0KDQpUaGFuayB5b3UgdmVyeSBtdWNoIENhcnN0ZW4gZm9yIGFkZHJl
c3NpbmcgbXkgY29tbWVudHMNCg0KTGllYmUgR3LDvMOfZSwNCg0KSW5lcw0KDQpPbiBUdWUsIEFw
ciA2LCAyMDIxIGF0IDc6NTkgUE0gQ2Fyc3RlbiBCb3JtYW5uIDxjYWJvQHR6aS5vcmc8bWFpbHRv
OmNhYm9AdHppLm9yZz4+IHdyb3RlOg0KSGkgSW5lcywNCg0KdGhhbmsgeW91IGZvciB0aGVzZSBj
b21tZW50cyENCg0KR29vZCBjYXRjaCB3aXRoIHRoZSAwYjAxMF8wMTAwMSENCkkgc2hvdWxkIGtu
b3cgYmV0dGVyIChtYWRlIHRoZSBzYW1lIGtpbmQgb2YgbWlzdGFrZSBpbiBSRkMgNzA0OSkuDQoN
CkkgYWN0dWFsbHkga2VwdCBpbiBhIHNlY29uZCBleHBhbnNpb24gb2YgU0ROViBpbiBTZWN0aW9u
IDI7IHBvc3NpYmx5IHRoZSBSRkMgZWRpdG9yIHdpbGwgc3RyaWtlIHRoYXQsIGJ1dCBJIGZpbmQg
aXQgdXNlZnVsLg0KDQpBbGwgdGhlIGJlbG93IGFyZSBub3cgaW4gaHR0cHM6Ly9naXRodWIuY29t
L2Nib3Itd2cvY2Jvci1vaWQvY29tbWl0LzljOTBkOGQNCg0KR3LDvMOfZSwgQ2Fyc3Rlbg0KDQoN
Cj4gT24gMjAyMS0wNC0wNiwgYXQgMTg6MjEsIEluZXMgUm9ibGVzIHZpYSBEYXRhdHJhY2tlciA8
bm9yZXBseUBpZXRmLm9yZzxtYWlsdG86bm9yZXBseUBpZXRmLm9yZz4+IHdyb3RlOg0KPg0KPiBS
ZXZpZXdlcjogSW5lcyBSb2JsZXMNCj4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzDQo+
DQo+IFN1bW1hcnk6DQo+DQo+IFRoZSBkb2N1bWVudCBkZWZpbmVzIENCT1IgdGFncyBmb3Igb2Jq
ZWN0IGlkZW50aWZpZXJzIChPSURzKS4gIFRoZSBkb2N1bWVudCBpcw0KPiB3ZWxsIHdyaXR0ZW4u
DQo+DQo+IEZldyBtaW5vciBxdWVzdGlvbnMvY29tbWVudHMuDQo+DQo+IE1ham9yIElzc3Vlczog
Tm9uZQ0KPg0KPiBNaW5vciBJc3N1ZXM6IE5vbmUNCj4NCj4gTml0czoNCj4NCj4gLSBJdCB3b3Vs
ZCBiZSBuaWNlIHRvIGV4cGFuZCBTRE5WIGluIHNlY3Rpb24gMS4xIGluc3RlYWQgb2YgU2VjdGlv
biAyLg0KPg0KPiAtIFNlY3Rpb24gMy4yIC0gRmlndXJlIDQtTUlCIHJlbGF0aXZlIG9iamVjdCBp
ZGVudGlmaWVyIGluIENCT1I6DQo+DQo+IDBiMDEwXzAxMDAxIHNob3VsZCBiZSAwYjAxMF8wMDAx
MSA/IGZvciBtYWpvciB0eXBlIDIsIGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gMw0KPiBieXRlcw0K
Pg0KPiAtIFNlY3Rpb24gNy4xOg0KPg0KPiAtLSBJbiBvcmRlciB0byBtZW50aW9uIHRoZSByZWdp
c3RyeSwgbWF5YmUgc210aCBsaWtlDQo+DQo+ICB0byBhc3NpZ24gdGhlIENCT1IgdGFncyAtLT4g
dG8gYXNzaWduIGluIHRoZSBDQk9SIHRhZ3MgcmVnaXN0cnkgdGhlIGZvbGxvd2luZw0KPiAgdGFn
cy4uLi4NCj4NCj4gLS0gSXQgd291bGQgYmUgbmljZSB0byBoYXZlIHRoZSB0YWJsZSB3aXRoIHRo
ZSBzYW1lIHN0cnVjdHVyZSBhcyB0aGUgcmVnaXN0cnkNCj4gdGFibGUgKGFkZCByZWZlcmVuY2Ug
Y29sdW1uIGxpa2UgaW4gU2VjdGlvbiA3LjIpLCBJIHRoaW5rIHRlbXBsYXRlIGNvbHVtbiBkb2Vz
DQo+IG5vdCBhcHBseSBoZXJlLg0KPg0KPiAtIFNlY3Rpb24gNy4yOg0KPg0KPiAtLSBJbiBvcmRl
ciB0byBtZW50aW9uIHRoZSByZWdpc3RyeSwgbWF5YmUgc210aCBzaW1pbGFyIGFzIFNlY3Rpb24g
Ny4xPw0KPg0KPiBUaGFuayB5b3UgZm9yIHRoaXMgZG9jdW1lbnQsDQo+DQo+IEluZXMuDQo+DQo+
DQo=

--_000_BAF905D0999D48498234757BF252983Bciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <57D226D0BC3AC549A9E50BE26C9129F4@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCWZvbnQtc2l6
ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBz
cGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcy
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJlbi1CRSIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSIgc3R5bGU9IndvcmQtd3JhcDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+VGhhbmsgeW91IElu
ZXMgZm9yIHlvdXIgcmV2aWV3IGFuZCBDYXJzdGVuIGZvciB5b3VyIHByb21wdCByZXBseS48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPkkganVzdCBiYWxsb3RlZCBhIOKAmG5vIG9iamVjdGlvbuKAmSBldmFs
dWF0aW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+UmVnYXJkczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+LcOp
cmljPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNC
NUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPklvdC1kaXJlY3RvcmF0ZSAmbHQ7aW90LWRpcmVjdG9y
YXRlLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBJbmVzIFJvYmxlcyAmbHQ7bWFy
aWFpbmVzcm9ibGVzPTQwZ29vZ2xlbWFpbC5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+
RGF0ZTogPC9iPlR1ZXNkYXksIDYgQXByaWwgMjAyMSBhdCAyMTowODxicj4NCjxiPlRvOiA8L2I+
Q2Fyc3RlbiBCb3JtYW5uICZsdDtjYWJvQHR6aS5vcmcmZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVv
dDtkcmFmdC1pZXRmLWNib3ItdGFncy1vaWQuYWxsQGlldGYub3JnJnF1b3Q7ICZsdDtkcmFmdC1p
ZXRmLWNib3ItdGFncy1vaWQuYWxsQGlldGYub3JnJmd0OywgSUVURiBJb1QgRGlyZWN0b3JhdGUg
Jmx0O2lvdC1kaXJlY3RvcmF0ZUBpZXRmLm9yZyZndDssICZxdW90O2xhc3QtY2FsbEBpZXRmLm9y
ZyZxdW90OyAmbHQ7bGFzdC1jYWxsQGlldGYub3JnJmd0OywgJnF1b3Q7Y2JvckBpZXRmLm9yZyZx
dW90OyAmbHQ7Y2JvckBpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFtJb3Qt
ZGlyZWN0b3JhdGVdIElvdGRpciB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jYm9yLXRh
Z3Mtb2lkLTA2PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6MzYuMHB0Ij5UaGFuayB5b3UgdmVyeSBtdWNoIENhcnN0ZW4gZm9yIGFkZHJlc3NpbmcgbXkg
Y29tbWVudHM8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPkxpZWJl
IEdyw7zDn2UsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4w
cHQiPkluZXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBw
dCI+T24gVHVlLCBBcHIgNiwgMjAyMSBhdCA3OjU5IFBNIENhcnN0ZW4gQm9ybWFubiAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmNhYm9AdHppLm9yZyI+Y2Fib0B0emkub3JnPC9hPiZndDsgd3JvdGU6PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFy
Z2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBjbTttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0
b206MTIuMHB0O21hcmdpbi1sZWZ0OjM2LjBwdCI+DQpIaSBJbmVzLDxicj4NCjxicj4NCnRoYW5r
IHlvdSBmb3IgdGhlc2UgY29tbWVudHMhPGJyPg0KPGJyPg0KR29vZCBjYXRjaCB3aXRoIHRoZSAw
YjAxMF8wMTAwMSEmbmJzcDsgPGJyPg0KSSBzaG91bGQga25vdyBiZXR0ZXIgKG1hZGUgdGhlIHNh
bWUga2luZCBvZiBtaXN0YWtlIGluIFJGQyA3MDQ5KS48YnI+DQo8YnI+DQpJIGFjdHVhbGx5IGtl
cHQgaW4gYSBzZWNvbmQgZXhwYW5zaW9uIG9mIFNETlYgaW4gU2VjdGlvbiAyOyBwb3NzaWJseSB0
aGUgUkZDIGVkaXRvciB3aWxsIHN0cmlrZSB0aGF0LCBidXQgSSBmaW5kIGl0IHVzZWZ1bC48YnI+
DQo8YnI+DQpBbGwgdGhlIGJlbG93IGFyZSBub3cgaW4gPGEgaHJlZj0iaHR0cHM6Ly9naXRodWIu
Y29tL2Nib3Itd2cvY2Jvci1vaWQvY29tbWl0LzljOTBkOGQiIHRhcmdldD0iX2JsYW5rIj4NCmh0
dHBzOi8vZ2l0aHViLmNvbS9jYm9yLXdnL2Nib3Itb2lkL2NvbW1pdC85YzkwZDhkPC9hPjxicj4N
Cjxicj4NCkdyw7zDn2UsIENhcnN0ZW48YnI+DQo8YnI+DQo8YnI+DQomZ3Q7IE9uIDIwMjEtMDQt
MDYsIGF0IDE4OjIxLCBJbmVzIFJvYmxlcyB2aWEgRGF0YXRyYWNrZXIgJmx0OzxhIGhyZWY9Im1h
aWx0bzpub3JlcGx5QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bm9yZXBseUBpZXRmLm9yZzwv
YT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsgPGJyPg0KJmd0OyBSZXZpZXdlcjogSW5lcyBSb2JsZXM8
YnI+DQomZ3Q7IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggTml0czxicj4NCiZndDsgPGJyPg0K
Jmd0OyBTdW1tYXJ5Ojxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGUgZG9jdW1lbnQgZGVmaW5lcyBD
Qk9SIHRhZ3MgZm9yIG9iamVjdCBpZGVudGlmaWVycyAoT0lEcykuJm5ic3A7IFRoZSBkb2N1bWVu
dCBpczxicj4NCiZndDsgd2VsbCB3cml0dGVuLjxicj4NCiZndDsgPGJyPg0KJmd0OyBGZXcgbWlu
b3IgcXVlc3Rpb25zL2NvbW1lbnRzLjxicj4NCiZndDsgPGJyPg0KJmd0OyBNYWpvciBJc3N1ZXM6
IE5vbmU8YnI+DQomZ3Q7IDxicj4NCiZndDsgTWlub3IgSXNzdWVzOiBOb25lPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IE5pdHM6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC0gSXQgd291bGQgYmUgbmljZSB0
byBleHBhbmQgU0ROViBpbiBzZWN0aW9uIDEuMSBpbnN0ZWFkIG9mIFNlY3Rpb24gMi48YnI+DQom
Z3Q7IDxicj4NCiZndDsgLSBTZWN0aW9uIDMuMiAtIEZpZ3VyZSA0LU1JQiByZWxhdGl2ZSBvYmpl
Y3QgaWRlbnRpZmllciBpbiBDQk9SOjxicj4NCiZndDsgPGJyPg0KJmd0OyAwYjAxMF8wMTAwMSBz
aG91bGQgYmUgMGIwMTBfMDAwMTEgPyBmb3IgbWFqb3IgdHlwZSAyLCBhZGRpdGlvbmFsIGluZm9y
bWF0aW9uIDM8YnI+DQomZ3Q7IGJ5dGVzPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC0gU2VjdGlvbiA3
LjE6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC0tIEluIG9yZGVyIHRvIG1lbnRpb24gdGhlIHJlZ2lz
dHJ5LCBtYXliZSBzbXRoIGxpa2U8YnI+DQomZ3Q7IDxicj4NCiZndDsmbmJzcDsgdG8gYXNzaWdu
IHRoZSBDQk9SIHRhZ3MgLS0mZ3Q7IHRvIGFzc2lnbiBpbiB0aGUgQ0JPUiB0YWdzIHJlZ2lzdHJ5
IHRoZSBmb2xsb3dpbmc8YnI+DQomZ3Q7Jm5ic3A7IHRhZ3MuLi4uPGJyPg0KJmd0OyA8YnI+DQom
Z3Q7IC0tIEl0IHdvdWxkIGJlIG5pY2UgdG8gaGF2ZSB0aGUgdGFibGUgd2l0aCB0aGUgc2FtZSBz
dHJ1Y3R1cmUgYXMgdGhlIHJlZ2lzdHJ5PGJyPg0KJmd0OyB0YWJsZSAoYWRkIHJlZmVyZW5jZSBj
b2x1bW4gbGlrZSBpbiBTZWN0aW9uIDcuMiksIEkgdGhpbmsgdGVtcGxhdGUgY29sdW1uIGRvZXM8
YnI+DQomZ3Q7IG5vdCBhcHBseSBoZXJlLjxicj4NCiZndDsgPGJyPg0KJmd0OyAtIFNlY3Rpb24g
Ny4yOjxicj4NCiZndDsgPGJyPg0KJmd0OyAtLSBJbiBvcmRlciB0byBtZW50aW9uIHRoZSByZWdp
c3RyeSwgbWF5YmUgc210aCBzaW1pbGFyIGFzIFNlY3Rpb24gNy4xPzxicj4NCiZndDsgPGJyPg0K
Jmd0OyBUaGFuayB5b3UgZm9yIHRoaXMgZG9jdW1lbnQsPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IElu
ZXMuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BAF905D0999D48498234757BF252983Bciscocom_--


From nobody Wed Apr  7 14:37:38 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDFA3A2AA2 for <cbor@ietfa.amsl.com>; Wed,  7 Apr 2021 14:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KK5GEXQwj9bf for <cbor@ietfa.amsl.com>; Wed,  7 Apr 2021 14:37:32 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45ABB3A2A9A for <cbor@ietf.org>; Wed,  7 Apr 2021 14:37:32 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id v8so10012108plz.10 for <cbor@ietf.org>; Wed, 07 Apr 2021 14:37:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Bpesor/mhmY/CKw/OFLHZaLf1jo9QiqESfsIM6/ApJw=; b=G4VHwbgGl+KHvrdHL3QT7Ste//3GuASEbrCpjbN+57/ALG8YWvII9qwHVlMQiU4xw5 XvUZUHanIUrElYeWPvaoiy9+IK4ALCpdKJ0Kphk/2ieSt2vOvn5zU1t5W7qXYZ+cN598 BL80riZQPeJ/u/FID1S8zyxqbLXkvJpGfUX2BMJnCjxdlhd907QQAFB4t83dtZOxfttq o5K3MHEbpgECmqfnqB6Cj54QQvazfnmHlW3gzPUshxe1B8MTvvyPKv/OE+Dz8n1VH/Yz hyhwID1cgayZdszmgN73CttqYxOYHxFKaCUb2b9awT9we9zjBiI+jjUhMVtcIcTSI63A pXzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Bpesor/mhmY/CKw/OFLHZaLf1jo9QiqESfsIM6/ApJw=; b=U5VaDMa3p52GJ7AS8cxsYUhZMnjwPXf01Ma514EA8PDYXSZeMxv8/w+FRJojeIZTrg 4KKReXYq0S29hL177lBL1TcjERkJBgMzZ/ET74OU4ZwzTKlCFw3s6VOPCqv5B7h3U+/g FAM44MfH14c6z58aaRYOf3vGXBrcEAGT+aFzIHEGqaN/44DEluZSuSRfrY6r5rHbA3+Z l4tJRlIKipxQ/HcSQOD6dcINdFgDV1ZPt7ZhjESIGBYWUcQIW8cX5C/YkFVpBvwUc4qR wAND6fa4z7EnkHFaOuH6JPoFFh+sbDArlAXo7tlAoi8nNhyfamFUegsgLFS/UsGVIA66 MeTA==
X-Gm-Message-State: AOAM530+bxjbLBXkIUWOOPcfa0tKtKL95H8czOOUFFKn+NyyQ7V4qIkE biZUE9GBYKkDuRXpqugSwkGven+7PZve4vQJP1g=
X-Google-Smtp-Source: ABdhPJyPRhSauH9HGbKu+BuNpOXhM93Pay9WUqA+6/C+5HHKwRy2VApikdu3ZgoBVAzSG0YPUOe3McPwukVq2nweM/g=
X-Received: by 2002:a17:90b:310e:: with SMTP id gc14mr5368058pjb.198.1617831450527;  Wed, 07 Apr 2021 14:37:30 -0700 (PDT)
MIME-Version: 1.0
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Wed, 7 Apr 2021 18:37:19 -0300
Message-ID: <CAM70yxC_6JnG+CbumDs+-maOcMYyRZXAD1QJgXJQsG2tYFVVdQ@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>, cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ea4add05bf68bcfb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/cbjF2VieyPxFriV0Rcl90Gxz73g>
Subject: Re: [Cbor] CBOR tag proposal for enumerated alternatives (tagged unions)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 21:37:37 -0000

--000000000000ea4add05bf68bcfb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 31, 2021 at 9:38 AM Carsten Bormann <cabo@tzi.org> wrote:

> I=E2=80=99m not sure we discussed this one yet in detail:
>
>
> https://docs.google.com/document/d/16aiDEBhJj3kipj_7PVppEhxAr5E6QhQreN61e=
CxvBjU/edit#
>
> This is a (cbor-tags) registration request, so the WG does not have to
> have an opinion, but the designated expert would be interested in it
> nonetheless.
> (I=E2=80=99m personally pretty convinced of the use case; this is more of=
 an issue
> of keeping tabs on available tag numbers and looking out for related use
> cases.)
>

As I had mentioned in the interim meeting, a related use case is
optional<T> (aka Nullable<T>). The meeting host (Christian?) was
questioning whether separate tags would be more appropriate to represent
the optional<T> semantic.

It would indeed be possible for the enumerated alternatives tags to be used
for representing an optional<T>. For instance, alternative 0 would
represent the "no value" state, followed by a null data item (0xF6),
whereas alternative 1 would represent the "has value" state followed by the
actual value. However, this is just an arbitrary convention and the
enumerated alternatives tags used in this fashion don't explicitly express
the "optional" semantic (it has to be assumed by the application). I
therefore agree that separate tags would be preferable for the optional<T>
use case.

I communicated with one of the co-authors of the enumerated alternatives
proposal about the possibility of including extra tags for the optional<T>
use case. They declined, not wanting to expand the scope of their proposal,
which is perfectly understandable.

My idea of tags for representing optional<T> might be overkill. One can
simply encode an optional value as either null (0xF6) or the actual value.
A contrived example where this would not work is encoding
optional<null_type> (i.e. "optional null").

Anyway, the idea of tags for optional values is out there for the
designated expert to consider. I cannot say if it's an idea actually worth
pursuing. I don't currently need them for encoding/decoding
std::optional<T> in my C++ work (I just check for null when deserializing
an optional value). However, I could definitely make use of the enumerated
alternatives tags for encoding/decoding std::variant<T0, T1, T2...>,
especially when the alternative types are ambiguous once converted to CBOR.

Cheers,
Emile Cormier

--000000000000ea4add05bf68bcfb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, Mar 31, 2021 at 9:38 AM Carsten Bormann &lt;<a href=3D"mailt=
o:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">I=E2=80=99m not sure we discu=
ssed this one yet in detail:<br>
<br>
<a href=3D"https://docs.google.com/document/d/16aiDEBhJj3kipj_7PVppEhxAr5E6=
QhQreN61eCxvBjU/edit#" rel=3D"noreferrer" target=3D"_blank">https://docs.go=
ogle.com/document/d/16aiDEBhJj3kipj_7PVppEhxAr5E6QhQreN61eCxvBjU/edit#</a><=
br>
<br>
This is a (cbor-tags) registration request, so the WG does not have to have=
 an opinion, but the designated expert would be interested in it nonetheles=
s.<br>
(I=E2=80=99m personally pretty convinced of the use case; this is more of a=
n issue of keeping tabs on available tag numbers and looking out for relate=
d use cases.)<br></blockquote><div><br></div><div>As I had mentioned in the=
 interim meeting, a related use case is optional&lt;T&gt; (aka Nullable&lt;=
T&gt;). The meeting host (Christian?) was questioning whether separate tags=
 would be more appropriate to represent the optional&lt;T&gt; semantic.</di=
v><div><br></div><div>It would indeed be possible for the enumerated altern=
atives tags to be used for representing an optional&lt;T&gt;. For instance,=
 alternative 0 would represent the &quot;no value&quot; state, followed by =
a null data item (0xF6), whereas alternative 1 would represent the &quot;ha=
s value&quot; state followed by the actual value. However, this is just an =
arbitrary convention and the enumerated alternatives tags used in this fash=
ion don&#39;t explicitly express the &quot;optional&quot; semantic (it has =
to be assumed by the application). I therefore agree that separate tags wou=
ld be preferable for the optional&lt;T&gt; use case.<br></div><div><br></di=
v><div>I communicated with one of the co-authors of the enumerated alternat=
ives proposal about the possibility of including extra tags for the optiona=
l&lt;T&gt; use case. They declined, not wanting to expand the scope of thei=
r proposal, which is perfectly understandable.</div><div><br></div><div>My =
idea of tags for representing optional&lt;T&gt; might be overkill. One can =
simply encode an optional value as either null (0xF6) or the actual value. =
A contrived example where this would not work is encoding optional&lt;null_=
type&gt; (i.e. &quot;optional null&quot;).<br></div><div><br></div><div>Any=
way, the idea of tags for optional values is out there for the designated e=
xpert to consider. I cannot say if it&#39;s an idea actually worth pursuing=
. I don&#39;t currently need them for encoding/decoding std::optional&lt;T&=
gt; in my C++ work (I just check for null when deserializing an optional va=
lue). However, I could definitely make use of the enumerated alternatives t=
ags for encoding/decoding std::variant&lt;T0, T1, T2...&gt;, especially whe=
n the alternative types are ambiguous once converted to CBOR.<br></div><div=
><br></div><div>Cheers,</div><div>Emile Cormier<br></div></div></div>

--000000000000ea4add05bf68bcfb--


From nobody Wed Apr  7 14:44:56 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75383A2AD3 for <cbor@ietfa.amsl.com>; Wed,  7 Apr 2021 14:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KAiFD4VcYWDx for <cbor@ietfa.amsl.com>; Wed,  7 Apr 2021 14:44:51 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1556A3A2AD1 for <cbor@ietf.org>; Wed,  7 Apr 2021 14:44:50 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id s11so313058pfm.1 for <cbor@ietf.org>; Wed, 07 Apr 2021 14:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2bx8y+0ueQvuXFLqZ2FX9tC1d5jIis8DUjq30yR3xJ8=; b=tUqwUnDKuoZKOSOeUe2Bq+EJJva03evNV5YLxRUn4Fav5lb7aUVH1Gvp+W7f91V3r8 fY1nTZngjNLhBSB0HwaW6gCIkVXlYQ+TFAgulbN/JAYiiwXfq2S81sj1K+lvCW1XQDn7 7wsgUroR7wUtgQ44a+5W6crwWJ4Cc1iR39bqZPJI6xl8EwexvBZPwDiRYNuoNZRq6cL6 8NhFHpUQ9oevyuWFGJpUDZtDK3pzj62k6gYDZbu7F1BXoB04J0+Su1Xd+ssGmBewk5Zw U4OLLtsnYW6ySvt4nWXKDthzEztEcvmewNkg7T7oUy73WMOWKfljYXA7xxWiC/yh11io FDew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2bx8y+0ueQvuXFLqZ2FX9tC1d5jIis8DUjq30yR3xJ8=; b=gRnO0x/OhUeAreh7KM2sFBGMWK348G+kQYjKRjoCqlCxwjaZg8XTJjQyvMy5rINkIz mtPe2BZ9vPrGOr19X05j0+KCmv9z8bQ5n0f29bBWaN1gjTjHKV94aJ0iy2THTc1r7PpL BUVgNAv5l7ZM7DsufjzfzaJOgwUxAmSrsgko2qU4dNtIruWryTxVWEALnR4ugcNxFuK4 ktY5OkFpWYYkvSbWPsvxt6ubYYtlY+//EMKdfW/I7un/3VMFG3OkBOtV43HSNeTatyxB 5HbEY5ucGWOc3mzS43093fslix+q9xyLf7RQ7eCIbwKUAtDmPxRLYcpmngX4xlqfBEKE Kfkg==
X-Gm-Message-State: AOAM531+O62hhotLUb+0vyaWS0fAI+kwor3xFXbHjiDjZNwykDOoTZT/ 3m/e6xkSBuoHl5lvB7ioeIba0Kzc7q9C6g65q8nrW3JSTyM=
X-Google-Smtp-Source: ABdhPJytfAWYUlbRd9+KH50BhuEsFrKW5yun9WZiuM9e+RPJ/cQ+ZSyFQvBhMfT8qAt7BonXqX3jbD3JHJ4E+xwxAuQ=
X-Received: by 2002:a63:3ec2:: with SMTP id l185mr5138499pga.45.1617831889762;  Wed, 07 Apr 2021 14:44:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxDJ8fNBPWLtheiWKvvpKUayw0ueuNtAbnd8BsVWV8gKMg@mail.gmail.com> <161ED597-9822-41BC-9B1B-311DBBD26BE6@mothers-arms.co.uk> <CAM70yxBfcSCEwDr1OxWM40G+C7BaxFhyFm0C2PAQ_H3N1dboGA@mail.gmail.com>
In-Reply-To: <CAM70yxBfcSCEwDr1OxWM40G+C7BaxFhyFm0C2PAQ_H3N1dboGA@mail.gmail.com>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Wed, 7 Apr 2021 18:44:39 -0300
Message-ID: <CAM70yxCso4Fu14G8UT8=Zk7NTVr2-vfQEUUrghZC6MbX=PeXTg@mail.gmail.com>
To: Kio Smallwood <kio@mothers-arms.co.uk>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000187a4105bf68d754"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/0HdGro2DAh8Cp82xoeUCdeA-lEs>
Subject: Re: [Cbor] Consolidated set of tags for containers
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 21:44:54 -0000

--000000000000187a4105bf68d754
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 6, 2021 at 6:02 PM Emile Cormier <emile.cormier.jr@gmail.com>
wrote:

One thing that should be considered is removing the tags for uniform keys
> and arbitrary values.
>

Sorry, I meant removing tags for arbitrary keys and uniform values, which I
believe would be a rare use case.

--000000000000187a4105bf68d754
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Tue, Apr 6, 2021 at 6:02 PM Emile Cormier &lt;<a href=3D"mailto:e=
mile.cormier.jr@gmail.com">emile.cormier.jr@gmail.com</a>&gt; wrote:</div><=
div dir=3D"ltr" class=3D"gmail_attr"><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote">One thing=
 that should be considered is removing the tags for uniform keys and arbitr=
ary values.</div></div></blockquote><div><br></div><div>Sorry, I meant remo=
ving tags for arbitrary keys and uniform values, which I believe would be a=
 rare use case. <br></div></div></div>

--000000000000187a4105bf68d754--


From nobody Wed Apr  7 15:23:03 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C15A3A2C29; Wed,  7 Apr 2021 15:22:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-tags-oid@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com, christian@amsuess.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <161783417685.27338.2878236772630764165@ietfa.amsl.com>
Date: Wed, 07 Apr 2021 15:22:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/wdsfWNzL2i1GvU9HQubAT4xyJ0Y>
Subject: [Cbor] Benjamin Kaduk's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2021 22:22:58 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-cbor-tags-oid-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I made a PR at https://github.com/cbor-wg/cbor-oid/pull/9 with an
editorial suggestion (it ended up being just one -- well done!).

Is there anything useful to say about how bstrs tagged in this way will
be (mis?)interpreted by implementations that don't understand these tag
values?

Section 2

   Tag TBD110: tags a byte string as the [X.690] encoding of a relative
   object identifier (also "relative OID").  Since the encoding of each
   number is the same as for [RFC6256] Self-Delimiting Numeric Values
   (SDNVs), this tag can also be used for tagging a byte string that
   contains a sequence of zero or more SDNVs.

I did not think that CBOR was prone to reusing tag values for types that
are semantically different but happen to have the same binary encoding
rules.  Should generic SDNVs get a dedicated tag?

Section 7.1

Please note which range (and encoded length?) the allocations should
come from.  Alternately, mentioning specific requested values here might
be wise (given that there are examples that assume specific values).

Section 8

We might mention something about how when tag factoring is in use you
have to be careful that the only bstrs being affected do contain OIDs,
and inadvertently tagging a compound structure that sometimes contains
non-OID bstrs (in the relevant places) can have unexpected effects.

Section 9.1

AFAICT RFC 6256 only needs to be normative because of the way the
control operators are defined, and we rely on BER for everything else.
(Also, it looks like BER has more strict requirements than SDNV for the
minimal-length encoding, though I did not investigate this very
thoroughly.)




From nobody Wed Apr  7 18:49:54 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C9E3A32EC; Wed,  7 Apr 2021 18:49:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-tags-oid@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com, christian@amsuess.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <161784658891.8883.7447256942679073873@ietfa.amsl.com>
Date: Wed, 07 Apr 2021 18:49:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/HTZLeCNunSRxS-enDoUP5eed_cQ>
Subject: [Cbor] John Scudder's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 01:49:49 -0000

John Scudder has entered the following ballot position for
draft-ietf-cbor-tags-oid-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

1. Section 2:

   Since the semantics of absolute and relative object identifiers
   differ, this specification defines two tags, collectively called the
   "OID tags" here:

Sure looks like three tags to me.

2. Section 5:

Since this is the first place you refer to CDDL, put your reference to RFC 8610 here instead of §6?




From nobody Wed Apr  7 22:47:29 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E93A3A3AB9; Wed,  7 Apr 2021 22:47:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-tags-oid@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <161786084703.14674.9412885551672611584@ietfa.amsl.com>
Date: Wed, 07 Apr 2021 22:47:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/siBPDUHTArZ7WIYgWuInT7-Iids>
Subject: [Cbor] Murray Kucherawy's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 05:47:28 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-cbor-tags-oid-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

For Zaheduzzaman: The downref was properly identified during the Last Call.




From nobody Wed Apr  7 23:14:01 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2AF3A3BA1; Wed,  7 Apr 2021 23:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 XOmdwQoAW7VE; Wed,  7 Apr 2021 23:13:52 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12F223A3B9F; Wed,  7 Apr 2021 23:13:51 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FG9v16DdSzybQ; Thu,  8 Apr 2021 08:13:49 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <161784658891.8883.7447256942679073873@ietfa.amsl.com>
Date: Thu, 8 Apr 2021 08:13:49 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-cbor-tags-oid@ietf.org, CBOR Working Group <cbor-chairs@ietf.org>, cbor@ietf.org, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mao-Original-Outgoing-Id: 639555228.020396-0a473edfb1ed1414e1b96e26732344e7
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC1A77CD-7114-4964-B0D1-6353CCCA4EAD@tzi.org>
References: <161784658891.8883.7447256942679073873@ietfa.amsl.com>
To: John Scudder <jgs@juniper.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/iXPHSfYUl3WIvyzNG9tJn7dD6fA>
Subject: Re: [Cbor] John Scudder's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 06:13:56 -0000

Hi John,

> On 2021-04-08, at 03:49, John Scudder via Datatracker =
<noreply@ietf.org> wrote:
>=20
> John Scudder has entered the following ballot position for
> draft-ietf-cbor-tags-oid-06: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> 1. Section 2:
>=20
>   Since the semantics of absolute and relative object identifiers
>   differ, this specification defines two tags, collectively called the
>   "OID tags" here:
>=20
> Sure looks like three tags to me.

Indeed.  Ben Kaduk (whose comments I=E2=80=99m otherwise still =
processing) had a PR for this, which I merged.

> 2. Section 5:
>=20
> Since this is the first place you refer to CDDL, put your reference to =
RFC 8610 here instead of =C2=A76?

Fixed (including expansion of abbreviation): =
https://github.com/cbor-wg/cbor-oid/commit/2d39560

Thank you!

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Apr  8 01:00:33 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 325DE3A3F3A; Thu,  8 Apr 2021 01:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 haFnJvl8IU4G; Thu,  8 Apr 2021 01:00:28 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 876AD3A3F39; Thu,  8 Apr 2021 01:00:27 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FGDG12hLwz17ZX; Thu,  8 Apr 2021 10:00:25 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <161783417685.27338.2878236772630764165@ietfa.amsl.com>
Date: Thu, 8 Apr 2021 10:00:24 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-cbor-tags-oid@ietf.org, CBOR Working Group <cbor-chairs@ietf.org>, cbor@ietf.org, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mao-Original-Outgoing-Id: 639561623.810825-2434c72920fc0d27d1076b22344eea4c
Content-Transfer-Encoding: quoted-printable
Message-Id: <F32E1CFE-D37B-438C-BABF-9139F926EDA9@tzi.org>
References: <161783417685.27338.2878236772630764165@ietfa.amsl.com>
To: Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/AkUML_UlWuASmmLGiiTobxM-iG0>
Subject: Re: [Cbor] Benjamin Kaduk's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 08:00:31 -0000

Hi Ben,

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> I made a PR at https://github.com/cbor-wg/cbor-oid/pull/9 with an
> editorial suggestion (it ended up being just one -- well done!).

Merged, thank you.

> Is there anything useful to say about how bstrs tagged in this way =
will
> be (mis?)interpreted by implementations that don't understand these =
tag
> values?

I don=E2=80=99t think there is anything specific beyond what is true for =
all tagged byte strings.

> Section 2
>=20
>   Tag TBD110: tags a byte string as the [X.690] encoding of a relative
>   object identifier (also "relative OID").  Since the encoding of each
>   number is the same as for [RFC6256] Self-Delimiting Numeric Values
>   (SDNVs), this tag can also be used for tagging a byte string that
>   contains a sequence of zero or more SDNVs.
>=20
> I did not think that CBOR was prone to reusing tag values for types =
that
> are semantically different but happen to have the same binary encoding
> rules.  Should generic SDNVs get a dedicated tag?

Relative OIDs by their nature need context to interpret them.
The same kind of context could say that they are really SDNV sequences =
outside the OID mechanism.
Saying =E2=80=9Cthis is an SDNV sequence but I won=E2=80=99t tell you =
how to use it=E2=80=9D isn=E2=80=99t particularly useful.
New tags could be allocated when specific non-OID SDNV usage patterns =
emerge.

> Section 7.1
>=20
> Please note which range (and encoded length?) the allocations should
> come from.  Alternately, mentioning specific requested values here =
might
> be wise (given that there are examples that assume specific values).

The request follows the pattern we have emerged of calling unassigned =
but suggested values TBD4711.  Examples of course may need to bind to =
specific values, which is where we used the suggested values.

Made the range explicit, a7b222f.

> Section 8
>=20
> We might mention something about how when tag factoring is in use you
> have to be careful that the only bstrs being affected do contain OIDs,
> and inadvertently tagging a compound structure that sometimes contains
> non-OID bstrs (in the relevant places) can have unexpected effects.

Added (9782c6e):

An attacker might trick an application into using a byte string inside
a tag-factored data item, where the byte string is not actually
intended to fall under one of the tags defined here.  This may cause
the application to emit data with semantics different from what was
intended.  Applications therefore need to be restrictive with respect
to what data items they apply tag factoring to.

> Section 9.1
>=20
> AFAICT RFC 6256 only needs to be normative because of the way the
> control operators are defined, and we rely on BER for everything else.

Yes.  Are you making this comment to state why this downref is =
relatively innocuous, or to say that we shouldn=E2=80=99t have the =
downref?

> (Also, it looks like BER has more strict requirements than SDNV for =
the
> minimal-length encoding, though I did not investigate this very
> thoroughly.)

Indeed.  However, this specification is more restrictive in not allowing =
leading zeroes except for an only byte.  E.g., Section 2.1 says:

>> Also, the first byte of each SDNV cannot be a
>> leading zero in SDNV's base-128 arithmetic, so it cannot take the
>> value 0x80 (bullet (c) in Section 8.1.2.4.2 of {{X.690}}).

To make this clear from the outset, I changed in the terminology section =
(dd312ff) :

-The term "SDNV" (Self-Delimiting Numeric Value) is used as defined in =
{{-sdnv}}.
+The term "SDNV" (Self-Delimiting Numeric Value) is used as defined in
+{{-sdnv}}, with the additional restriction detailed in {{reqts}}.

Thank you!

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Apr  8 05:06:14 2021
Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 959783A1458; Thu,  8 Apr 2021 05:06:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-tags-oid@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com, christian@amsuess.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <161788356811.31539.2139615008210880278@ietfa.amsl.com>
Date: Thu, 08 Apr 2021 05:06:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/PiF72eMCnERyUEqY-REDzCSzlcs>
Subject: [Cbor] Robert Wilton's Discuss on draft-ietf-cbor-tags-oid-06: (with DISCUSS and COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 12:06:09 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-cbor-tags-oid-06: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-cbor-tags-oid/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hi,

Hopefully not tricky to discuss/resolve, sorry for posting it close to the
telechat!

I would like to please see some more clarity or guidance about when TAG TBD112
should be used, given that there are two possible encodings of absolute OIDs
below "1.3.6.1.4.1".

Specifically, the questions that I have, that probably need to be clarified are:
 - is a CBOR encoder allowed to optimize a TBD110 tag into a TBD112 tag?
 - Should CBOR decoder clients always expect to be able to handle both TBD110
 and TBD112 tags? - Or, it the decision over whether to use TBD110 or TBD112
 down to the application and the application needs to agree which is use.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I found this document to be interesting because I knew from the title that it
was going to only be 4 pages long and say that OIDs are obviously encoded as a
tagged array, hence I was surprised to see that was not the solution and it
uses BER encoded OIDs instead.

The document explains, and I think that I understand why this has been done,
but I question whether the title of the document and name of the tags is right.
 Is it really a CBOR representation of OIDs, or is it actually a CBOR
representation of BER encoded OIDs?  I.e., it is plausible that there would
ever be a requirement for non BER encoded OIDs.  E.g., I'm not an ASN.1 expert,
but say if somewhat wanted to do a CBOR encoding of ASN.1, then it is not
obvious to me that they would use a BER encoding for OIDs.  Hence the
suggestion is to make the title, abstract, and name of the tags clear that it
is about the CBOR encoding or BER encoded OIDs.

In the introduction:
   Since the semantics of absolute and relative object identifiers
   differ, this specification defines two tags, collectively called the
   "OID tags" here:

I presume that this should be three tags?

In section 4.1.  Tag Factoring Example: X.500 Distinguished Name:

The diagram uses a mix of single letters (e.g. c for country), and a full name
"street".  Is this how the X.500 attributes are defined?  Otherwise it might be
clearer to always use their full names.

    The country and street RDNs are single-valued. The second and fourth RDNs
    are multi-valued.

Perhaps:  "The country (first) and street (third) RDNs are single-valued. The
second and fourth RDNs are multi-valued."

    h'550407': "Los Angeles", h'550408': "CA",

I think that the example would be more clear by splitting the city and county
onto separate lines.

Finally, the document contains these two sentences that seem to somewhat
conflict with each other:

"While these sequences can easily be represented in CBOR arrays of unsigned
integers, a more compact representation can often be achieved by adopting the
widely used representation of object identifiers defined in BER; this
representation may also be more amenable to processing by other software that
makes use of object identifiers."

compared to:

"Staying close to the way object identifiers are encoded in ASN.1 BER makes
back-and-forth translation easy; otherwise we would choose a more efficient
encoding."

Regards,
Rob




From nobody Thu Apr  8 12:45:01 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4B473A190F for <cbor@ietfa.amsl.com>; Thu,  8 Apr 2021 12:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 r_uxm67aMEJj for <cbor@ietfa.amsl.com>; Thu,  8 Apr 2021 12:44:56 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FFD63A190D for <cbor@ietf.org>; Thu,  8 Apr 2021 12:44:56 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FGWts4PTmzyXR; Thu,  8 Apr 2021 21:44:53 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <161788356811.31539.2139615008210880278@ietfa.amsl.com>
Date: Thu, 8 Apr 2021 21:44:52 +0200
X-Mao-Original-Outgoing-Id: 639603892.382916-7bdc8afc682da8387f573a62c190ce72
Content-Transfer-Encoding: quoted-printable
Message-Id: <74E0F02D-1AAB-444B-ABCA-82EACEF27B5F@tzi.org>
References: <161788356811.31539.2139615008210880278@ietfa.amsl.com>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/QoS55EJAFylmBR6vnNbdg2C-aGg>
Subject: [Cbor] OID representation (was: Re: Robert Wilton's Discuss on draft-ietf-cbor-tags-oid-06: (with DISCUSS and COMMENT))
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 19:45:00 -0000

CBOR WG,

in the IESG processing of draft-ietf-cbor-tags-oid, Rob Wilton raises =
some questions that I think the WG needs to consider before we reply.

I=E2=80=99ll include some excerpts from Rob=E2=80=99s message and try to =
translate this into questions to the WG.

## Question that needs to be decided by WG

> I would like to please see some more clarity or guidance about when =
TAG TBD112
> should be used, given that there are two possible encodings of =
absolute OIDs
> below "1.3.6.1.4.1".
>=20
> Specifically, the questions that I have, that probably need to be =
clarified are:
> - is a CBOR encoder allowed to optimize a TBD110 tag into a TBD112 =
tag?
> - Should CBOR decoder clients always expect to be able to handle both =
TBD110
> and TBD112 tags? - Or, it the decision over whether to use TBD110 or =
TBD112
> down to the application and the application needs to agree which is =
use.

This is indeed a good question (about TBD111 vs. TBD112, actually).
This can be seen as related to issues about preferred representations, =
or about minimizing interoperability problems by nailing down exactly =
one allowed representation.

So what we could propose as a WG is:

(1) Not establishing any stronger connection between TBD111 and TBD112, =
i.e. status quo.
(2) Declaring TBD112 as the preferred encoding of an absolute OID that =
starts with 1.3.6.1.4.1 (0x2b06010401), but still allowing the use of =
TBD111 as non-preferred.   This would mean a requirement on decoders =
implementing TBD111 to also implement TBD112.
(3) Outlawing any TBD111 starting with (0x2b06010401) and requiring the =
use of TBD112 in all such cases.  This would mean a requirement on both =
encoders and decoders.  It would also mean a slight complication in tag =
factoring: replace all naked byte strings that start with =
h=E2=80=992b06010401=E2=80=99 by TBD112(rest) (saving three bytes), =
unless *all* such byte strings start with h=E2=80=992b06010401=E2=80=99, =
in which case these prefixes would all be removed and an outer tag of =
TBD112 used.

(2a) would be (2) with a deterministic encoding requirement to use the =
shortest form (i.e., (3) in deterministic encoding only).

## Other responses, to be vetted by the WG

> I found this document to be interesting because I knew from the title =
that it
> was going to only be 4 pages long and say that OIDs are obviously =
encoded as a
> tagged array, hence I was surprised to see that was not the solution =
and it
> uses BER encoded OIDs instead.
>=20
> The document explains, and I think that I understand why this has been =
done,
> but I question whether the title of the document and name of the tags =
is right.
> Is it really a CBOR representation of OIDs, or is it actually a CBOR
> representation of BER encoded OIDs? =20

The first, using the technical approach named in the second.

> I.e., it is plausible that there would
> ever be a requirement for non BER encoded OIDs.  E.g., I'm not an =
ASN.1 expert,
> but say if somewhat wanted to do a CBOR encoding of ASN.1, then it is =
not
> obvious to me that they would use a BER encoding for OIDs. =20

One example for a CBOR encoding of something that previously has been =
encoded in ASN.1 is draft-mattsson-cose-cbor-cert-compress, which =
normatively references the tags-oid spec.  The certificate spec actually =
goes ahead and registers translation tables between likely OIDs and =
small integers.  But if the full range of OIDs is needed, the byte =
string derived from the BER content indeed is the representation chosen. =
 (As the C509 certificates are schema-driven, they do not need the =
actual tags defined here.)

> Hence the
> suggestion is to make the title, abstract, and name of the tags clear =
that it
> is about the CBOR encoding or BER encoded OIDs.

The specification proposes to use BER in a number of tags for binary =
encoding of OIDs.
The BERness is not a feature that the OIDs already need to have before =
these tags apply.
So a title "CBOR encoding of BER encoded OIDs=E2=80=9D (which is what I =
think Rob wanted to say) would be a restriction beyond what this spec is =
about.

## Answers that probably don=E2=80=99t need WG input

> In the introduction:
>   Since the semantics of absolute and relative object identifiers
>   differ, this specification defines two tags, collectively called the
>   "OID tags" here:
>=20
> I presume that this should be three tags?

(Fixed by Ben=E2=80=99s PR, https://github.com/cbor-wg/cbor-oid/pull/9 =
.)

> In section 4.1.  Tag Factoring Example: X.500 Distinguished Name:
>=20
> The diagram uses a mix of single letters (e.g. c for country), and a =
full name
> "street".  Is this how the X.500 attributes are defined? =20

This uses the naming defined e.g. in RFC 4519, section 2.2 and section =
2.34, which has been derived from X.520 and is quite ubiquitous, going =
back to Table 1 of RFC 1779.

>    The country and street RDNs are single-valued. The second and =
fourth RDNs
>    are multi-valued.
>=20
> Perhaps:  "The country (first) and street (third) RDNs are =
single-valued. The
> second and fourth RDNs are multi-valued."

Now in https://github.com/cbor-wg/cbor-oid/commit/3d0fd8b .

>    h'550407': "Los Angeles", h'550408': "CA",
>=20
> I think that the example would be more clear by splitting the city and =
county
> onto separate lines.

Now in https://github.com/cbor-wg/cbor-oid/commit/3d0fd8b .

> Finally, the document contains these two sentences that seem to =
somewhat
> conflict with each other:
>=20
> "While these sequences can easily be represented in CBOR arrays of =
unsigned
> integers, a more compact representation can often be achieved by =
adopting the
> widely used representation of object identifiers defined in BER; this
> representation may also be more amenable to processing by other =
software that
> makes use of object identifiers."
>=20
> compared to:
>=20
> "Staying close to the way object identifiers are encoded in ASN.1 BER =
makes
> back-and-forth translation easy; otherwise we would choose a more =
efficient
> encoding."


While the BER form is reasonably efficient, a more efficient =
representation of sequences of unsigned integers that roughly follow =
Zipf=E2=80=99s law in distribution has been described in  =
<https://mailarchive.ietf.org/arch/msg/cbor/9owRyOcXdsK7Ooc1S3D9-AImDdU>, =
which would for instance represent 1.3.6.1.4.1 as 0x136141 and does not =
need a special case to make absolute OIDs efficient.

The WG instead decided to follow the existing BER representation because =
it is so widely implemented and is compatible with SDNVs, which are used =
in additional applications and often have good platform support (e.g., =
Ruby pack/unpack(=E2=80=9Cw*=E2=80=9D)).
For OID-style applications, BER content is often still more compact than =
a CBOR array of unsigned integers.

Tagged (homogeneous) arrays of arcs don=E2=80=99t help as the OID arcs =
vary widely in their range; e.g., the common OID 1.2.840.113549.1.1.1 =
(*, 2+9 bytes in BER) would need to be an array of seven 32-bit integers =
(2tag+2head+28 bytes) instead of a basic CBOR array of unsigned integers =
of 14 bytes.

In general, I don=E2=80=99t think we need to discuss an extensive set of =
alternative approaches (paths not taken) in this specification.

Gr=C3=BC=C3=9Fe, Carsten

(*) {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) =
rsaEncryption(1)}


From nobody Thu Apr  8 15:49:16 2021
Return-Path: <kaduk@mit.edu>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445233A2015; Thu,  8 Apr 2021 15:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 MxIgKhcOC4ht; Thu,  8 Apr 2021 15:49:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 5A3043A2011; Thu,  8 Apr 2021 15:49:10 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 138Mn12j018121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 8 Apr 2021 18:49:06 -0400
Date: Thu, 8 Apr 2021 15:49:00 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Carsten Bormann <cabo@tzi.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-cbor-tags-oid@ietf.org, CBOR Working Group <cbor-chairs@ietf.org>, cbor@ietf.org, Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
Message-ID: <20210408224900.GA79563@kduck.mit.edu>
References: <161783417685.27338.2878236772630764165@ietfa.amsl.com> <F32E1CFE-D37B-438C-BABF-9139F926EDA9@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F32E1CFE-D37B-438C-BABF-9139F926EDA9@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/BAwn5o4rky7kDXzcsdfSADjDl40>
Subject: Re: [Cbor] Benjamin Kaduk's No Objection on draft-ietf-cbor-tags-oid-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2021 22:49:15 -0000

Hi Carsten,

On Thu, Apr 08, 2021 at 10:00:24AM +0200, Carsten Bormann wrote:
> Hi Ben,
> 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > I made a PR at https://github.com/cbor-wg/cbor-oid/pull/9 with an
> > editorial suggestion (it ended up being just one -- well done!).
> 
> Merged, thank you.
> 
> > Is there anything useful to say about how bstrs tagged in this way will
> > be (mis?)interpreted by implementations that don't understand these tag
> > values?
> 
> I don’t think there is anything specific beyond what is true for all tagged byte strings.
> 
> > Section 2
> > 
> >   Tag TBD110: tags a byte string as the [X.690] encoding of a relative
> >   object identifier (also "relative OID").  Since the encoding of each
> >   number is the same as for [RFC6256] Self-Delimiting Numeric Values
> >   (SDNVs), this tag can also be used for tagging a byte string that
> >   contains a sequence of zero or more SDNVs.
> > 
> > I did not think that CBOR was prone to reusing tag values for types that
> > are semantically different but happen to have the same binary encoding
> > rules.  Should generic SDNVs get a dedicated tag?
> 
> Relative OIDs by their nature need context to interpret them.
> The same kind of context could say that they are really SDNV sequences outside the OID mechanism.
> Saying “this is an SDNV sequence but I won’t tell you how to use it” isn’t particularly useful.
> New tags could be allocated when specific non-OID SDNV usage patterns emerge.

Okay, thanks for talking through it.

> > Section 7.1
> > 
> > Please note which range (and encoded length?) the allocations should
> > come from.  Alternately, mentioning specific requested values here might
> > be wise (given that there are examples that assume specific values).
> 
> The request follows the pattern we have emerged of calling unassigned but suggested values TBD4711.  Examples of course may need to bind to specific values, which is where we used the suggested values.
> 
> Made the range explicit, a7b222f.
> 
> > Section 8
> > 
> > We might mention something about how when tag factoring is in use you
> > have to be careful that the only bstrs being affected do contain OIDs,
> > and inadvertently tagging a compound structure that sometimes contains
> > non-OID bstrs (in the relevant places) can have unexpected effects.
> 
> Added (9782c6e):
> 
> An attacker might trick an application into using a byte string inside
> a tag-factored data item, where the byte string is not actually
> intended to fall under one of the tags defined here.  This may cause
> the application to emit data with semantics different from what was
> intended.  Applications therefore need to be restrictive with respect
> to what data items they apply tag factoring to.
> 
> > Section 9.1
> > 
> > AFAICT RFC 6256 only needs to be normative because of the way the
> > control operators are defined, and we rely on BER for everything else.
> 
> Yes.  Are you making this comment to state why this downref is relatively innocuous, or to say that we shouldn’t have the downref?

If I was holding the pen it wouldn't have the downref ... but it doesn't
actually matter.

> > (Also, it looks like BER has more strict requirements than SDNV for the
> > minimal-length encoding, though I did not investigate this very
> > thoroughly.)
> 
> Indeed.  However, this specification is more restrictive in not allowing leading zeroes except for an only byte.  E.g., Section 2.1 says:
> 
> >> Also, the first byte of each SDNV cannot be a
> >> leading zero in SDNV's base-128 arithmetic, so it cannot take the
> >> value 0x80 (bullet (c) in Section 8.1.2.4.2 of {{X.690}}).

Exactly, yes.

> To make this clear from the outset, I changed in the terminology section (dd312ff) :
> 
> -The term "SDNV" (Self-Delimiting Numeric Value) is used as defined in {{-sdnv}}.
> +The term "SDNV" (Self-Delimiting Numeric Value) is used as defined in
> +{{-sdnv}}, with the additional restriction detailed in {{reqts}}.
> 
> Thank you!

Thank you!

-Ben


From nobody Fri Apr  9 02:18:38 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA7A3A1987 for <cbor@ietfa.amsl.com>; Fri,  9 Apr 2021 02:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 Krl95tTU_5rj for <cbor@ietfa.amsl.com>; Fri,  9 Apr 2021 02:18:32 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D580D3A1983 for <cbor@ietf.org>; Fri,  9 Apr 2021 02:18:30 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FGsxc5hRjz16gP; Fri,  9 Apr 2021 11:18:28 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAM70yxBEvhN9VqbRpMedPMaSjnRf_GQcUAYcfna0kA5=7gRcdw@mail.gmail.com>
Date: Fri, 9 Apr 2021 11:18:28 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 639652708.164252-eeaa7bdc059d6bfc9dc8262e6721af6b
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1053C4F-11DB-474E-B73A-798D6FCE36AD@tzi.org>
References: <CAM70yxBEvhN9VqbRpMedPMaSjnRf_GQcUAYcfna0kA5=7gRcdw@mail.gmail.com>
To: Emile Cormier <emile.cormier.jr@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/50iTxjlP1kfcngMuDPrMIhQnx44>
Subject: Re: [Cbor] Multiple ways of expressing the same time via draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 09:18:36 -0000

Hi Emile,

On 2021-04-06, at 22:35, Emile Cormier <emile.cormier.jr@gmail.com> =
wrote:
>=20
> I'm implementing tags 1001 and 1002 in my C++ library to exchange time =
points and durations (refer to =
https://www.ietf.org/archive/id/draft-bormann-cbor-time-tag-04.html).
>=20
> I'm in the situation where I''m not sure which is the "expected" way =
to encode time as nanoseconds since the Unix epoch. I'm specifically =
referring to std::chrono::system_clock::time_point, which is a 64 bit =
integer. There are currently three ways I could encode such a value.
>=20
> 1. The whole number of seconds under Key 1, with the remaining =
nanoseconds under Key -9.
>=20
> 2. The total number of nanoseconds under Key -9, with a value of zero =
under Key 1.
>=20
> 3. The total number of nanoseconds expressed as a Decimal Fraction =
under Key 4.

Oh.  You are pointing out a deficiency of the current text.  The =
*intention* was that Key 1 is an integer and Key -3*n is supplying the =
fractional part.  E.g., like UNIX struct timeval for -6 (old) and struct =
timespec for -9 (new) do.
So that would be your Option 1.

But since you raise it, we probably should entertain the question.

The issue really is whether the onus is on the sender/encoder or the =
recipient/decoder.

Restricting the value for key -3*n to be less than 10**(3*n) places the =
onus on the sender, who would need to do a modulo if that is not the way =
the data is already represented on the sender=E2=80=99s platform.
Not adding this restriction places the onus on the recipient, who would =
then need to do the modulo in case the recipient=E2=80=99s platform =
representation is like one of the UNIX ones.

> Option #2 is the easiest and most efficient because it doesn't involve =
a division/subtraction calculation.

=E2=80=A6 for the sender.

> However, a receiver that discards Key -9 will end up with zero =
seconds. At least with option #1, the receiver will know the number of =
whole seconds if Key -9 is ignored.

Which indeed maybe also is a concern.

> Option #3 requires that the sender and receiver understand Tag 4 =
(Decimal Fraction), or at least the concept of decimal fractions within =
the context of tags 1001-1003.

That would seem to be the easier case; =E2=80=9Cunderstanding=E2=80=9D =
Tag 4 in this context is limited to being able to parse the 4([-6, =
microseconds]) arrangement, unless the sender=E2=80=99s code looks for =
trailing zeros and does stunts like 4([-5, tens-of-microseconds]) in =
these cases, which of course cannot be excluded.

> I'm guessing that option #1 is the "canonical" way, but I'm not =
entirely sure. Some guidance would be appreciated. Perhaps a few words =
concerning this should be added to the standard's text?

Definitely, either way.

I think I=E2=80=99m mildly in favor of placing the onus on the sender, =
i.e., Option 1.

etime =3D #6.1001({
  ...
  1: int,
  ? (
    -3: uint .lt 1000 //
    -6: uint .lt 1000000 //
    -9: uint .lt 1000000000 //
    -12: uint .lt 1000000000000 //
    -15: uint .lt 1000000000000000 //
    -18: uint .lt 1000000000000000000
  )
  ...
})

> On the receiving side, my library would ideally handle all three =
scenarios. It's on the sending side I'm more concerned about when I need =
to interoperate with CBOR decoders other than mine.

Right, be conservative=E2=80=A6liberal=E2=80=A6

Thanks for bringing this up!

One always learns a lot from implementation efforts.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Apr  9 12:13:59 2021
Return-Path: <emile.cormier.jr@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E769D3A2B80 for <cbor@ietfa.amsl.com>; Fri,  9 Apr 2021 12:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 a4sJetVArEFS for <cbor@ietfa.amsl.com>; Fri,  9 Apr 2021 12:13:53 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E69A3A2B82 for <cbor@ietf.org>; Fri,  9 Apr 2021 12:13:53 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id q10so4644402pgj.2 for <cbor@ietf.org>; Fri, 09 Apr 2021 12:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nx9rGM6jwN7bMRpDJCvQqMEKgRNj82Mcsm4KmVgjCuY=; b=s6PFxqSDzXsndv+OjacKeu/fszinWBLhwlUNDJc2L8GNx4zKNbIYSMNXJIPWuuGppq 8vD1sgN77C4D5KrEoQVpUpQP7GB/G0VRl1uQLe08k5ehnxKAxroSj9X1hcERHLxj68C/ lvKRnNzzoUG3csEH2kDW/SWd2j3PsMfw5bDw4JGT13L8yBzsOCctQ5RQ6g/J6KhWhoqG sS8H1vQIxRYpD5dIX7Nfqp9F81PxbTmgAPQbgDWuEaOwBiYWAESKNoTasBldDIGqEOQZ aD9K5JEbn2uWy4hjs2tIVpMDjiArmQcZZB59TBwGI++5RKiCdiredngq5UJVCXa+/XWN 8TVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nx9rGM6jwN7bMRpDJCvQqMEKgRNj82Mcsm4KmVgjCuY=; b=mf9iY328SMwExJOsv1UqWU1uX8aO6xFy6ymEEQi9m97bkd47vdvshWZkxiGfivHtnn 98u0XnMhcmudbc6EZ+DZBxME+/6flr0QGhRrPh94AU9K8/F5umHDeJd7ZqZhVSp7sgS0 p1BkNU6+AZDk9dXE9FImEzR7h9LwkAGVJkJG6bLzsHZQtUTNGXWUC5YH6rwfkmjqbSUd 3Dwjf/EcBCKo8tfKJRD6bLAaHCUJQje9kf2kKkbfHqgpO8ViwgIYFnVjwYITsAmjwqFs Iq3RYMMYwHcOPaGsVDa4SkzDysf96psH5nedE5RlvujwpQPE88quPYx4V9HBBRlAHAI/ A3Zw==
X-Gm-Message-State: AOAM533VBb8pO6CwD9NexPrYveBNA19xkr4xFLFctf7dF2FiZTODCx/I ODI+5gs95d6ytfOy7vlVhYALO+1cvvcLlIbTYsQ=
X-Google-Smtp-Source: ABdhPJyyLQjJVeQWgIk+6LL5XVYt8keblG9VtOZuMmiCxuVPs6RW0AuAAktlEOfUOhxSyCFHUq1htO97ACVguSg//Lw=
X-Received: by 2002:a63:3ec2:: with SMTP id l185mr14825144pga.45.1617995631187;  Fri, 09 Apr 2021 12:13:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAM70yxBEvhN9VqbRpMedPMaSjnRf_GQcUAYcfna0kA5=7gRcdw@mail.gmail.com> <A1053C4F-11DB-474E-B73A-798D6FCE36AD@tzi.org>
In-Reply-To: <A1053C4F-11DB-474E-B73A-798D6FCE36AD@tzi.org>
From: Emile Cormier <emile.cormier.jr@gmail.com>
Date: Fri, 9 Apr 2021 16:13:40 -0300
Message-ID: <CAM70yxBdtZRCwVCXPO7506X_j8PB3fvS6i1bzKrE4EfbtMNq7g@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d85b3205bf8ef64c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/PGibjDXfASBFTHpuIH3E7jnqZH8>
Subject: Re: [Cbor] Multiple ways of expressing the same time via draft-bormann-cbor-time-tag
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 19:13:58 -0000

--000000000000d85b3205bf8ef64c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Carsten,

As always, thank you for your invaluable insights. I'll proceed with my C++
implementation assuming that my option #1 is what's preferred for the
sender. I did indeed strike me that the POSIX timespec struct, with its
separate fields for seconds and nanoseconds, seemed to be the inspiration
behind the specification.

The "penalty" for the division/modulo operation, for sending a
std::chrono::time_point via tag 1001, is probably insignificant. I'm sure
it's orders of magnitude faster than converting it to ISO8601 text.

By the way, my "scaled arbitrary ratio" idea from before turned out to be
useful as an internal, intermediate representation between various
application time types (like std::chrono::time_point, time_t, timespec,
etc...) and the various JSON/CBOR-like codecs that my library supports.

Cheers,
Emile Cormier

On Fri, Apr 9, 2021 at 6:18 AM Carsten Bormann <cabo@tzi.org> wrote:

> Hi Emile,
>
> On 2021-04-06, at 22:35, Emile Cormier <emile.cormier.jr@gmail.com> wrote=
:
> >
> > I'm implementing tags 1001 and 1002 in my C++ library to exchange time
> points and durations (refer to
> https://www.ietf.org/archive/id/draft-bormann-cbor-time-tag-04.html).
> >
> > I'm in the situation where I''m not sure which is the "expected" way to
> encode time as nanoseconds since the Unix epoch. I'm specifically referri=
ng
> to std::chrono::system_clock::time_point, which is a 64 bit integer. Ther=
e
> are currently three ways I could encode such a value.
> >
> > 1. The whole number of seconds under Key 1, with the remaining
> nanoseconds under Key -9.
> >
> > 2. The total number of nanoseconds under Key -9, with a value of zero
> under Key 1.
> >
> > 3. The total number of nanoseconds expressed as a Decimal Fraction unde=
r
> Key 4.
>
> Oh.  You are pointing out a deficiency of the current text.  The
> *intention* was that Key 1 is an integer and Key -3*n is supplying the
> fractional part.  E.g., like UNIX struct timeval for -6 (old) and struct
> timespec for -9 (new) do.
> So that would be your Option 1.
>
> But since you raise it, we probably should entertain the question.
>
> The issue really is whether the onus is on the sender/encoder or the
> recipient/decoder.
>
> Restricting the value for key -3*n to be less than 10**(3*n) places the
> onus on the sender, who would need to do a modulo if that is not the way
> the data is already represented on the sender=E2=80=99s platform.
> Not adding this restriction places the onus on the recipient, who would
> then need to do the modulo in case the recipient=E2=80=99s platform repre=
sentation
> is like one of the UNIX ones.
>
> > Option #2 is the easiest and most efficient because it doesn't involve =
a
> division/subtraction calculation.
>
> =E2=80=A6 for the sender.
>
> > However, a receiver that discards Key -9 will end up with zero seconds.
> At least with option #1, the receiver will know the number of whole secon=
ds
> if Key -9 is ignored.
>
> Which indeed maybe also is a concern.
>
> > Option #3 requires that the sender and receiver understand Tag 4
> (Decimal Fraction), or at least the concept of decimal fractions within t=
he
> context of tags 1001-1003.
>
> That would seem to be the easier case; =E2=80=9Cunderstanding=E2=80=9D Ta=
g 4 in this
> context is limited to being able to parse the 4([-6, microseconds])
> arrangement, unless the sender=E2=80=99s code looks for trailing zeros an=
d does
> stunts like 4([-5, tens-of-microseconds]) in these cases, which of course
> cannot be excluded.
>
> > I'm guessing that option #1 is the "canonical" way, but I'm not entirel=
y
> sure. Some guidance would be appreciated. Perhaps a few words concerning
> this should be added to the standard's text?
>
> Definitely, either way.
>
> I think I=E2=80=99m mildly in favor of placing the onus on the sender, i.=
e.,
> Option 1.
>
> etime =3D #6.1001({
>   ...
>   1: int,
>   ? (
>     -3: uint .lt 1000 //
>     -6: uint .lt 1000000 //
>     -9: uint .lt 1000000000 //
>     -12: uint .lt 1000000000000 //
>     -15: uint .lt 1000000000000000 //
>     -18: uint .lt 1000000000000000000
>   )
>   ...
> })
>
> > On the receiving side, my library would ideally handle all three
> scenarios. It's on the sending side I'm more concerned about when I need =
to
> interoperate with CBOR decoders other than mine.
>
> Right, be conservative=E2=80=A6liberal=E2=80=A6
>
> Thanks for bringing this up!
>
> One always learns a lot from implementation efforts.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

--000000000000d85b3205bf8ef64c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Carsten,</div><div><br></div><div>As always, thank=
 you for your invaluable insights. I&#39;ll proceed with my C++ implementat=
ion assuming that my option #1 is what&#39;s preferred for the sender. I di=
d indeed strike me that the POSIX timespec struct, with its separate fields=
 for seconds and nanoseconds, seemed to be the inspiration behind the speci=
fication.</div><div><br></div><div>The &quot;penalty&quot; for the division=
/modulo operation, for sending a std::chrono::time_point via tag 1001, is p=
robably insignificant. I&#39;m sure it&#39;s orders of magnitude faster tha=
n converting it to ISO8601 text.</div><div><br></div><div>By the way, my &q=
uot;scaled arbitrary ratio&quot; idea from before turned out to be useful a=
s an internal, intermediate representation between various application time=
 types (like std::chrono::time_point, time_t, timespec, etc...) and the var=
ious JSON/CBOR-like codecs that my library supports.<br></div><div><br></di=
v><div>Cheers,</div><div>Emile Cormier<br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 9, 2021 at 6:18=
 AM Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Emil=
e,<br>
<br>
On 2021-04-06, at 22:35, Emile Cormier &lt;<a href=3D"mailto:emile.cormier.=
jr@gmail.com" target=3D"_blank">emile.cormier.jr@gmail.com</a>&gt; wrote:<b=
r>
&gt; <br>
&gt; I&#39;m implementing tags 1001 and 1002 in my C++ library to exchange =
time points and durations (refer to <a href=3D"https://www.ietf.org/archive=
/id/draft-bormann-cbor-time-tag-04.html" rel=3D"noreferrer" target=3D"_blan=
k">https://www.ietf.org/archive/id/draft-bormann-cbor-time-tag-04.html</a>)=
.<br>
&gt; <br>
&gt; I&#39;m in the situation where I&#39;&#39;m not sure which is the &quo=
t;expected&quot; way to encode time as nanoseconds since the Unix epoch. I&=
#39;m specifically referring to std::chrono::system_clock::time_point, whic=
h is a 64 bit integer. There are currently three ways I could encode such a=
 value.<br>
&gt; <br>
&gt; 1. The whole number of seconds under Key 1, with the remaining nanosec=
onds under Key -9.<br>
&gt; <br>
&gt; 2. The total number of nanoseconds under Key -9, with a value of zero =
under Key 1.<br>
&gt; <br>
&gt; 3. The total number of nanoseconds expressed as a Decimal Fraction und=
er Key 4.<br>
<br>
Oh.=C2=A0 You are pointing out a deficiency of the current text.=C2=A0 The =
*intention* was that Key 1 is an integer and Key -3*n is supplying the frac=
tional part.=C2=A0 E.g., like UNIX struct timeval for -6 (old) and struct t=
imespec for -9 (new) do.<br>
So that would be your Option 1.<br>
<br>
But since you raise it, we probably should entertain the question.<br>
<br>
The issue really is whether the onus is on the sender/encoder or the recipi=
ent/decoder.<br>
<br>
Restricting the value for key -3*n to be less than 10**(3*n) places the onu=
s on the sender, who would need to do a modulo if that is not the way the d=
ata is already represented on the sender=E2=80=99s platform.<br>
Not adding this restriction places the onus on the recipient, who would the=
n need to do the modulo in case the recipient=E2=80=99s platform representa=
tion is like one of the UNIX ones.<br>
<br>
&gt; Option #2 is the easiest and most efficient because it doesn&#39;t inv=
olve a division/subtraction calculation.<br>
<br>
=E2=80=A6 for the sender.<br>
<br>
&gt; However, a receiver that discards Key -9 will end up with zero seconds=
. At least with option #1, the receiver will know the number of whole secon=
ds if Key -9 is ignored.<br>
<br>
Which indeed maybe also is a concern.<br>
<br>
&gt; Option #3 requires that the sender and receiver understand Tag 4 (Deci=
mal Fraction), or at least the concept of decimal fractions within the cont=
ext of tags 1001-1003.<br>
<br>
That would seem to be the easier case; =E2=80=9Cunderstanding=E2=80=9D Tag =
4 in this context is limited to being able to parse the 4([-6, microseconds=
]) arrangement, unless the sender=E2=80=99s code looks for trailing zeros a=
nd does stunts like 4([-5, tens-of-microseconds]) in these cases, which of =
course cannot be excluded.<br>
<br>
&gt; I&#39;m guessing that option #1 is the &quot;canonical&quot; way, but =
I&#39;m not entirely sure. Some guidance would be appreciated. Perhaps a fe=
w words concerning this should be added to the standard&#39;s text?<br>
<br>
Definitely, either way.<br>
<br>
I think I=E2=80=99m mildly in favor of placing the onus on the sender, i.e.=
, Option 1.<br>
<br>
etime =3D #6.1001({<br>
=C2=A0 ...<br>
=C2=A0 1: int,<br>
=C2=A0 ? (<br>
=C2=A0 =C2=A0 -3: uint .lt 1000 //<br>
=C2=A0 =C2=A0 -6: uint .lt 1000000 //<br>
=C2=A0 =C2=A0 -9: uint .lt 1000000000 //<br>
=C2=A0 =C2=A0 -12: uint .lt 1000000000000 //<br>
=C2=A0 =C2=A0 -15: uint .lt 1000000000000000 //<br>
=C2=A0 =C2=A0 -18: uint .lt 1000000000000000000<br>
=C2=A0 )<br>
=C2=A0 ...<br>
})<br>
<br>
&gt; On the receiving side, my library would ideally handle all three scena=
rios. It&#39;s on the sending side I&#39;m more concerned about when I need=
 to interoperate with CBOR decoders other than mine.<br>
<br>
Right, be conservative=E2=80=A6liberal=E2=80=A6<br>
<br>
Thanks for bringing this up!<br>
<br>
One always learns a lot from implementation efforts.<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
</blockquote></div>

--000000000000d85b3205bf8ef64c--


From nobody Sun Apr 11 09:51:27 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C533A14B5 for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 EVYs5_tZPqxL for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:51:20 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E06C3A14B3 for <cbor@ietf.org>; Sun, 11 Apr 2021 09:51:20 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FJHv94fwxzydC; Sun, 11 Apr 2021 18:51:17 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210411161045.9648FF40799@rfc-editor.org>
Date: Sun, 11 Apr 2021 18:51:16 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, christoph.vigano@uni-bremen.de, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, Barry Leiba <barryleiba@computer.org>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mao-Original-Outgoing-Id: 639852676.652444-d6cfa777d0736a44fd295fd3a9a7f983
Content-Transfer-Encoding: quoted-printable
Message-Id: <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org>
References: <20210411161045.9648FF40799@rfc-editor.org>
To: cbor@ietf.org, smbarte2@illinois.edu
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/12YE-suaunQV5PnZ8KYeT7ZmzuA>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 16:51:25 -0000

Hi Sean,

thank you for submitting this errata report.

Without going into all the details here:

CDDL imports JSON syntax (Section 7 of RFC 8259) for text strings, and =
that has been somewhat simplified in the ABNF (which allows more than =
the RFC 8259 rules then actually allow).
However, there is one omission in the ABNF: the \u syntax, which is =
somewhat complicated in JSON because it is followed either by 4 hex =
digits that are not in the range d800 to dfff or by 4 hex digits in the =
range d800 to dbff, another \u, and four more hex digits dc00 to dfff.
Someone needs to sit down and write up the ABNF for that (or find some =
ABNF that already has done the work).

I=E2=80=99m not sure this update should all be put into an errata item; =
maybe we should pursue writing this up in a document that updates RFC =
8610 that could then also add a less unwieldy syntax for non-BMP code =
points such as the ubiquitous \u{=E2=80=A6}.

It seems people haven=E2=80=99t used a lot of \u notation with CDDL =
before: except for the C0 control characters not covered by JSON =
escapes, the literal character usually works well enough.

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-04-11, at 18:10, RFC Errata System <rfc-editor@rfc-editor.org> =
wrote:
>=20
> The following errata report has been submitted for RFC8610,
> "Concise Data Definition Language (CDDL): A Notational Convention to =
Express Concise Binary Object Representation (CBOR) and JSON Data =
Structures".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6527
>=20
> --------------------------------------
> Type: Technical
> Reported by: Sean Bartell <smbarte2@illinois.edu>
>=20
> Section: B
>=20
> Original Text
> -------------
>     SESC =3D "\" (%x20-7E / %x80-10FFFD)
>=20
> Corrected Text
> --------------
>     SESC =3D "\" (%x22 / %x27 / %x2F / %x5C / %x62 / %x66 / %x6E / =
%x72 / %x74 / %x75 4HEXDIG )
>=20
> Notes
> -----
> The ABNF rule for string escape codes should specify which escape =
codes are allowed, and also specify that "\u" must be followed by four =
hex digits. My suggested correction is based on JSON, but with the =
addition of "\'" (single quote) for use in text-based byte strings =
(section G.2). (Presumably, characters outside the BMP must be escaped =
using a surrogate pair, as in JSON.)
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC8610 (draft-ietf-cbor-cddl-08)
> --------------------------------------
> Title               : Concise Data Definition Language (CDDL): A =
Notational Convention to Express Concise Binary Object Representation =
(CBOR) and JSON Data Structures
> Publication Date    : June 2019
> Author(s)           : H. Birkholz, C. Vigano, C. Bormann
> Category            : PROPOSED STANDARD
> Source              : Concise Binary Object Representation Maintenance =
and Extensions
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG


From nobody Sun Apr 11 10:02:22 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC523A155E for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 10:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 Aa8l6W73jSvc for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 10:02:15 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FA183A155C for <cbor@ietf.org>; Sun, 11 Apr 2021 10:02:15 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FJJ7m19cRzyc6; Sun, 11 Apr 2021 19:02:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210411160226.2F39DF4078C@rfc-editor.org>
Date: Sun, 11 Apr 2021 19:02:11 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, christoph.vigano@uni-bremen.de, superuser@gmail.com, francesca.palombini@ericsson.com, barryleiba@computer.org, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, smbarte2@illinois.edu, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 639853331.217123-810f0af17392c1f56b50f770ec26424e
Content-Transfer-Encoding: quoted-printable
Message-Id: <6613947B-B585-402E-81AE-BC8D754BDC0A@tzi.org>
References: <20210411160226.2F39DF4078C@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/06oYYDrLbiW1sxd_cNLK56xiUFU>
Subject: Re: [Cbor] [Editorial Errata Reported] RFC8610 (6526)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 17:02:21 -0000

Hi Sean,

thank you for submitting this errata report.
Strangely, another backslash has been swallowed in the text that was =
mailed around below (it is correct at =
https://www.rfc-editor.org/errata/eid6526).

This report should be marked as verified, once it has been ascertained =
that the backslashes in the record survived.

(For those following along with the other errata report:
This one is about the appendix for CBOR EDN extended diagnostic =
notation, which has subtly different syntax from CDDL itself, and which =
is not defined in ABNF.)

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-04-11, at 18:02, RFC Errata System <rfc-editor@rfc-editor.org> =
wrote:
>=20
> The following errata report has been submitted for RFC8610,
> "Concise Data Definition Language (CDDL): A Notational Convention to =
Express Concise Binary Object Representation (CBOR) and JSON Data =
Structures".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6526
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Sean Bartell <smbarte2@illinois.edu>
>=20
> Section: G.2
>=20
> Original Text
> -------------
>   The escaping rules of JSON strings are applied equivalently for
>   text-based byte strings, e.g., "\" stands for a single backslash and
>   "'" stands for a single quote.  Whitespace is included literally,
>   i.e., the previous section does not apply to text-based byte =
strings.
>=20
> Corrected Text
> --------------
>   The escaping rules of JSON strings are applied equivalently for
>   text-based byte strings, e.g., "\" stands for a single backslash and
>   "\'" stands for a single quote.  Whitespace is included literally,
>   i.e., the previous section does not apply to text-based byte =
strings.
>=20
> Notes
> -----
> "\" and "'" need a backslash to escape them.
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC8610 (draft-ietf-cbor-cddl-08)
> --------------------------------------
> Title               : Concise Data Definition Language (CDDL): A =
Notational Convention to Express Concise Binary Object Representation =
(CBOR) and JSON Data Structures
> Publication Date    : June 2019
> Author(s)           : H. Birkholz, C. Vigano, C. Bormann
> Category            : PROPOSED STANDARD
> Source              : Concise Binary Object Representation Maintenance =
and Extensions
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG


From nobody Mon Apr 12 05:53:16 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921993A1CA6; Mon, 12 Apr 2021 05:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 6r2-EyWeumSd; Mon, 12 Apr 2021 05:53:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 025353A1CA9; Mon, 12 Apr 2021 05:53:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A36F9F40798; Mon, 12 Apr 2021 05:52:53 -0700 (PDT)
To: smbarte2@illinois.edu, henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210412125253.A36F9F40798@rfc-editor.org>
Date: Mon, 12 Apr 2021 05:52:53 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/UzZ5s50Ppq3X1ttm7XISAHV_0h8>
Subject: [Cbor] [Errata Verified] RFC8610 (6526)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Apr 2021 12:53:11 -0000

The following errata report has been verified for RFC8610,
"Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6526

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Sean Bartell <smbarte2@illinois.edu>
Date Reported: 2021-04-11
Verified by: Francesca Palombini (IESG)

Section: G.2

Original Text
-------------
   The escaping rules of JSON strings are applied equivalently for
   text-based byte strings, e.g., "\" stands for a single backslash and
   "'" stands for a single quote.  Whitespace is included literally,
   i.e., the previous section does not apply to text-based byte strings.

Corrected Text
--------------
   The escaping rules of JSON strings are applied equivalently for
   text-based byte strings, e.g., "\" stands for a single backslash and
   "\'" stands for a single quote.  Whitespace is included literally,
   i.e., the previous section does not apply to text-based byte strings.

Notes
-----
"\" and "'" need a backslash to escape them.

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Tue Apr 13 05:13:32 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801333A12C4 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 05:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 S2yPD9hHj13v for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 05:13:25 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10F5E3A12C2 for <cbor@ietf.org>; Tue, 13 Apr 2021 05:13:25 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FKPdZ4lPvzyd9; Tue, 13 Apr 2021 14:13:22 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org>
Date: Tue, 13 Apr 2021 14:13:22 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, christoph.vigano@uni-bremen.de, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, Barry Leiba <barryleiba@computer.org>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mao-Original-Outgoing-Id: 640008801.258806-38bca6a40634a21a7530fe845d4ee75e
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org>
To: cbor@ietf.org, smbarte2@illinois.edu
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/N1lb3N1tGBGbqg3puezb1L9f-xY>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 12:13:30 -0000

On 2021-04-11, at 18:51, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> However, there is one omission in the ABNF: the \u syntax, which is =
somewhat complicated in JSON because it is followed either by 4 hex =
digits that are not in the range d800 to dfff or by 4 hex digits in the =
range d800 to dbff, another \u, and four more hex digits dc00 to dfff.
> Someone needs to sit down and write up the ABNF for that (or find some =
ABNF that already has done the work).

I was too lazy to find some ABNF so I wrote my own.

76c76,84
< SESC =3D "\" (%x20-7E / %x80-10FFFD)
---
>=20
> SESC =3D "\" ( %x22 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 /
>              (%x75 hexchar) )
>=20
> hexchar =3D ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
>            ("D"
>             (( %x30-37 2HEXDIG ) /
>              (("8"/"9"/"A"/"B") 2HEXDIG "\" %x75 "D"
>               ("C"/"D"/"E"/"F") 2HEXDIG )))
79c87
< BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
---
> BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / "\'" / CRLF


The second change is necessary as SESC is now narrowly restricted to the =
escape combinations that JSON allows in text strings, and \' is not =
among those.

You can play with this changed grammar in cddlc version 0.0.3 (`gem =
update` if needed).

> I=E2=80=99m not sure this update should all be put into an errata =
item; maybe we should pursue writing this up in a document that updates =
RFC 8610 that could then also add a less unwieldy syntax for non-BMP =
code points such as the ubiquitous \u{=E2=80=A6}.

I=E2=80=99m still not entirely sure we want to handle this as a =
bog-standard errata item.
Opinions welcome.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 13 06:07:39 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFEE33A15C6 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 06:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 ATvjdBLcfVya for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 06:07:32 -0700 (PDT)
Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54A743A15C4 for <cbor@ietf.org>; Tue, 13 Apr 2021 06:07:32 -0700 (PDT)
Received: by mail-lj1-f179.google.com with SMTP id p23so15590159ljn.0 for <cbor@ietf.org>; Tue, 13 Apr 2021 06:07:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=jz7qYS84SUHenqu6C52hhMDfNpt6zFdVMuYTDpGhCuE=; b=EGRmbywt2ZdEWBT1RtLV45AkcdIETRNuZFnICRs0nKbaPOYVM45oxiCCM1Bq/hId9q rUnAM0g7GKoT1VTGlirF3rcq53B7k63qb15/W8YHksfdSydVZwM/8e93NQgLouU8B5D6 /AFGZJhGbdqdrglnux8sqtMNGUjMaCDGhGb107RicIV1jiUUXUKijMG+zZrm/fEIw8dx PdDE3YBgy/qNDRUSpkyQx2gVWymeY6OVyq0a1t1vvacsuyf9GHGONfKmLpNjfqNRBJcD JdJ9dpZTQHb+uoUDePay6OGshCqveA2UV0fRSa0ABUfYvP3cs7ox6D6hjw/af7KDlq1r UfGQ==
X-Gm-Message-State: AOAM5301R4v/YWlL6apEu8/x5OZ8ltXZPdk7O59epM7GpdU+hAAbeW3R yILHCMvGDbi/r4sPXLdToKVjtvmkT97K2g/nniw=
X-Google-Smtp-Source: ABdhPJwxAyQKx1hgaRFkG+aBZtZtQdaEEWF4CBmasIRmIV+HbaAlhE3z/ujJg45J9m2sV548+xF1l1Zk71FtojwYmq4=
X-Received: by 2002:a2e:a793:: with SMTP id c19mr16909900ljf.75.1618319249189;  Tue, 13 Apr 2021 06:07:29 -0700 (PDT)
MIME-Version: 1.0
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org>
In-Reply-To: <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 13 Apr 2021 09:07:18 -0400
Message-ID: <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org, smbarte2@illinois.edu,  Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, christoph.vigano@uni-bremen.de, "Murray S. Kucherawy" <superuser@gmail.com>,  Francesca Palombini <francesca.palombini@ericsson.com>,  =?UTF-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/OIzgCMSjPuTcjVu3mZQ7in7cXyg>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 13:07:37 -0000

Indeed, this one screams "Hold for Document Update" to me, as it's
something that rather more complex.  It's clear that this isn't just
an "oops" when we published, but, rather a (valid) rethinking that
needs broader review and consensus on the solution.

Barry

On Tue, Apr 13, 2021 at 8:13 AM Carsten Bormann <cabo@tzi.org> wrote:
>
> On 2021-04-11, at 18:51, Carsten Bormann <cabo@tzi.org> wrote:
> >
> > However, there is one omission in the ABNF: the \u syntax, which is som=
ewhat complicated in JSON because it is followed either by 4 hex digits tha=
t are not in the range d800 to dfff or by 4 hex digits in the range d800 to=
 dbff, another \u, and four more hex digits dc00 to dfff.
> > Someone needs to sit down and write up the ABNF for that (or find some =
ABNF that already has done the work).
>
> I was too lazy to find some ABNF so I wrote my own.
>
> 76c76,84
> < SESC =3D "\" (%x20-7E / %x80-10FFFD)
> ---
> >
> > SESC =3D "\" ( %x22 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 /
> >              (%x75 hexchar) )
> >
> > hexchar =3D ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
> >            ("D"
> >             (( %x30-37 2HEXDIG ) /
> >              (("8"/"9"/"A"/"B") 2HEXDIG "\" %x75 "D"
> >               ("C"/"D"/"E"/"F") 2HEXDIG )))
> 79c87
> < BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
> ---
> > BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / "\'" / CRLF
>
>
> The second change is necessary as SESC is now narrowly restricted to the =
escape combinations that JSON allows in text strings, and \' is not among t=
hose.
>
> You can play with this changed grammar in cddlc version 0.0.3 (`gem updat=
e` if needed).
>
> > I=E2=80=99m not sure this update should all be put into an errata item;=
 maybe we should pursue writing this up in a document that updates RFC 8610=
 that could then also add a less unwieldy syntax for non-BMP code points su=
ch as the ubiquitous \u{=E2=80=A6}.
>
> I=E2=80=99m still not entirely sure we want to handle this as a bog-stand=
ard errata item.
> Opinions welcome.
>
> Gr=C3=BC=C3=9Fe, Carsten
>


From nobody Tue Apr 13 06:30:01 2021
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 317713A16D9 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 06:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 NbTg24pe0dop for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 06:29:54 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70072.outbound.protection.outlook.com [40.107.7.72]) (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 D81903A16D7 for <cbor@ietf.org>; Tue, 13 Apr 2021 06:29:53 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PzGTnT/U2pVA9EzUms0Q8yE4l7jmMV/AauXkxpMvgplroVObp76A1LyLTe+ftFKX0PwqgeRoKg/86Nq8Is5VsMEfBzlyMKpc4eMikX15DfStrZWHeZmGMFNdwgxicvA7aZRQNlh6vDD8Rlbe+DNFDHZubwMShD/ZJSJsEpueoUqClExLNn1m+ZTjf4h72j8DaxkRzMeWtx2Vj1iJw7vb2K205s9BHn83tMG84jsLV7d8rU8BwMBmdv8xguLxTKIFf7Wm406pa+IfMz2gjWT7FWcgrgrm5VYu7PM1GB56uuj/ZI83E4c4y9kSL1NZNgJQpKzWNS/qNM8UMGpjHCaDcA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=00GyNK8y9EaHCA/yBp1Dk7yDDDSm9JHoqX/0xPHIlVg=; b=E5yla4b0wDgB9PJMGovpxgtikxmzjO39iNTEzIlqAjxEX0aTIP/2AI+y5NwUBrTSEbAOUkBtPvHm74ZghXRlc8coDTe4CgL45x9WxpK8XKqDdB22j9LDOu3z7nfr3TxHWBaY2DuNsxPmI1SYpa58412ZmNnwGUQzrA4v9LJyDI5YaJEb96/WjP3BA4ypJFFOVoOoZ6o3EIJS9exyqF41tDKtb5AoelIwDlx7umluxrcb51abLOa7RAqaEH/LiME8lDqxQlXo7uaT7FkOrTSiPyZuHHeHZzcoyQNJlGApBfYwbksilo5KfPVaQFMxFSfejJpwiC3pXK4ZPnk8c6dqyA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=00GyNK8y9EaHCA/yBp1Dk7yDDDSm9JHoqX/0xPHIlVg=; b=rnWRBYOBxjhZHmn0LFT8tD4etPlMP6xwN2aYajk1XcmcPOcWaDZwCKw43pQBEXLO1fdVwebX/ID8+lMquSohitxbkVof686yvSVvuRjUmE4Reb6ENpCLaY7cQII/5jRmYQpBv5te/vmqisk8Q43GA6yEQw0AtRinfKkbq0HeUd8=
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) by HE1PR07MB4219.eurprd07.prod.outlook.com (2603:10a6:7:9f::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.14; Tue, 13 Apr 2021 13:29:49 +0000
Received: from HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b]) by HE1PR07MB4217.eurprd07.prod.outlook.com ([fe80::593:f4fd:94e3:d90b%6]) with mapi id 15.20.4042.014; Tue, 13 Apr 2021 13:29:49 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: Barry Leiba <barryleiba@computer.org>, Carsten Bormann <cabo@tzi.org>
CC: "cbor@ietf.org" <cbor@ietf.org>, "smbarte2@illinois.edu" <smbarte2@illinois.edu>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "christoph.vigano@uni-bremen.de" <christoph.vigano@uni-bremen.de>, "Murray S. Kucherawy" <superuser@gmail.com>, =?utf-8?B?Q2hyaXN0aWFuIEFtc8O8c3M=?= <christian@amsuess.com>
Thread-Topic: [Cbor] [Technical Errata Reported] RFC8610 (6527)
Thread-Index: AQHXLu1MxZJ/y5yBPE6uvhEeaSsQdKqvh+sAgALXBQCAAA8SAIAAJ9AA
Date: Tue, 13 Apr 2021 13:29:49 +0000
Message-ID: <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com>
In-Reply-To: <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.47.21031401
authentication-results: computer.org; dkim=none (message not signed) header.d=none;computer.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:1ba8:147a:eb00:e040:6d47:6fe9:aa4]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e2a1fda6-8546-444d-dc97-08d8fe80365a
x-ms-traffictypediagnostic: HE1PR07MB4219:
x-microsoft-antispam-prvs: <HE1PR07MB421901E8E339F3FFFC6CE6DE984F9@HE1PR07MB4219.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 293iK9/y8bYB6PLit7KnNZSCXauf65C+ruYooC/+ol1b6xg3Lx3VQt26vt6QNo81mSC3icKOXPfrcpkl7Qh5yoPVY8UnYH219w9/SYBLgKP0xPvJpXjb2Zq8O2GpUbRJ9VZ3+DNij7buJaofjwjdt8tfx7bWc/BRBnbiiRA8S5LAcJXqiDlnOUKrIaCdjvMZBt4e3ggwXEl3iw4UeRJFQqi+sK9k6jw+D9Nh8unkWLoCnJdRekiEdNOlPLuqpMg59c1sRJiw6ZEOPXa6pNZCKO1cIDjPQ9A63R5d0ZZcZuPmX4ItakXkYPzgsULXanawzb1GBd0tiulQzy6c6jMztbvWbE9JgK04vpnpm1skFI+mI5MYp6x990iz7icWbtxjP+nBINlcD4So5tBSeSUCaafakCMmKVPx3z23aXhQVlwucMaFbHVvzF9dWMrrQhKsxZwnrSEgrLDArRQAYrnuWsMd8Qp1NuMEyVxoDVuuY02kjqQPmB3RKBfu505aSgWaagb723l7NhmoqbXf+P8FLVT4ww9HuBnpur9xBrKoREmOHcf04IstvDEr2JtXnp349KwHZUrUEW9PLk50/jaOIf/N9iG0kmXNlYbgYDvh9Vm6UBm8h8PnCAzTDt7l1lbm0ec48+1lZxeSHYcB444qF2tFbUVbfTmUM95vGMSLGAt5ShccgLVBB60pZNGT6BRkoCoRXnCQb4vClPX+XijfmMnTeEbYBwFUTS+IF4Ww7jSo+g4KXZYXZKeNIeI8sffY
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB4217.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(366004)(396003)(346002)(376002)(136003)(33656002)(4326008)(38100700002)(54906003)(71200400001)(83380400001)(86362001)(122000001)(8676002)(76116006)(8936002)(316002)(5660300002)(36756003)(2616005)(186003)(6486002)(66446008)(44832011)(478600001)(64756008)(6512007)(2906002)(966005)(66946007)(66556008)(66476007)(53546011)(6506007)(110136005)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?d3VUZjR1M0JsUWZORmpVQzZRanY4aks0Y1UzWnVIR1hkZHR1RzJCYU4vNXVW?= =?utf-8?B?d3lPczl4NHJmVXJ4SVU2NHZFR1hOZHc4S3NWNzhUaEJvejNkOUdId0dlQ3Rs?= =?utf-8?B?cDZtajhGc2JWZktoSmsvb0NvQzc1Y3E2RG55V0l2TUdGd3kxdlZXdU1hUFN1?= =?utf-8?B?WVNNZ0ZXWlJ3MGszQXhwUnFsS0xHaW52SDRQODdsOHc0WnBxWE1qMThKU25v?= =?utf-8?B?ZzFiK2lIYnNOY3BENUh6Ni9LSzkvalpoQ3JIK21JWlhYREN3RDl1SGNwMko3?= =?utf-8?B?SEl6SGxSNlA4aGExSXE5UHlvYTZ3bW0ya2laRFFmYjJKU2lObUU3VkxyUmxG?= =?utf-8?B?elpOWVp0dTFJWnNWUFZML3J0QmhWVnpuUUN2WjRpUDlzYmt1cWkzdHFuMlYr?= =?utf-8?B?SFFHMlpJcWZDbHc2ZS9KNHd0QS84bTg1YkxKWW8xRTFKcTducFliTEhyS2tB?= =?utf-8?B?MnBrMDA3MW1CVE9EYnYyWHpHS2lJVGp0cEh2UndKUlF4QVpjTjduQU1nU2di?= =?utf-8?B?bGxCS0pLUEN5amRHb29FRkRLWDJtVEowYWRtR3hwZFZvZVNBc1U0TFV2SkRl?= =?utf-8?B?NlRadllLc0Nkckx5THliVkdLb091N3FGcVJFK2tHbHpLaW9LcHhnZVlyQUlx?= =?utf-8?B?QWdlTDllRU5oUHoyV3FqWnB0clJ4cDVEUllvUm5GbFNUUXdCRE54T3V3Znc5?= =?utf-8?B?Nm1ENUd4SWMzMWdHMldPbmxGWkNrRGQzd1ZEVml0TWJZd05XeFRLakYzVzV2?= =?utf-8?B?N3NkdDNubEprOXY1MmhYdHRsUzlTUTZabXI2WWEzOVdPenFvcEFxMmlJL2lO?= =?utf-8?B?emdQQ3c5Y3RqRHBSVzNjYlhDNERKSHJRWC85ZlNMVklSeE5ZZWxsK3lRQmNV?= =?utf-8?B?WEpRZ1duSDdGYnhJcDdTMVVwN1RHeEo5RTRZaUgrdHdSTGF5TlN5bU5VSkVX?= =?utf-8?B?cHFBRHFwT2lmZDVkMjluRytQM3BrWDhPcnBVNVUwZ3ZiNElXVk1XL2pQTUFH?= =?utf-8?B?VGtTeXdFQlIySEh5aUNLSldER1B5N2lDdzlNaTIweG5IMEVrSGY1RE45MExq?= =?utf-8?B?ZmkwVElDQ1kvbnB6YXVaQVJSYmhUaWlOMkgwbmRzYitpandIRFFTbzJPSzNv?= =?utf-8?B?VmQ5dENPY1BoMnJLbnZXUGdWM3M0SzRCcWtZVXA1dU5XTjdabjQ3REFkZlZ1?= =?utf-8?B?NExIemVVcVpLd3lMZFk5bk9pa3VWbncvYmgxTWRkMDVoNFZndkMyUGFrcWxL?= =?utf-8?B?WDlSbWk3TDZSdzBDNTZBODR6QjcxbUJJdzlHZWxwNldZWDgwMHlSelBqbFl4?= =?utf-8?B?L29nSG9aQk1QY3N0NVFZNHpFaFQzNS95VFF3UHRKZnFaemtZM2hIWjJVRm50?= =?utf-8?B?NmFMSlE4c0h2K1NmaVFvV0RkeFJkZXpMbnlCZWxId2habHBNZ0x1eEg4Y3Ay?= =?utf-8?B?dzRoZFRyN1ZPQ1JId3ZwUUhGU2ZGM1RtN2ZuM2Viend3QWpiNjIrS2xLMUJU?= =?utf-8?B?blVqVGRjNjRQTHo4WVB6bUtvRFhsU1dVd3VoeW4xYzRNUWJDMWNObnFZUGVp?= =?utf-8?B?R3pCdlphbXFCd0E4VFhzeWd1K0REdTVaakxPcTdHcGI5R0R3TlM3OTNTaEN3?= =?utf-8?B?NmZVN3pMeUEzOCtjVUZDblNEV3FSRXJucVhiSnR1OGM5elRJV2FYa2JNaURh?= =?utf-8?B?amxNT0Z3Z3lRdmIzTFNLd20xWnY5bWVTYW9aZjB3c1JqU3Rtd2E3Z2FtNkhs?= =?utf-8?B?YU9BUVZ6NlBQM25HTWZvOENBQlFjMDFQd0x3TVZaYzQ4cllLaWxYbHBGVmpi?= =?utf-8?B?b0RXeUVtckFucFJVQnNLT1VXSklsN0lTcVFZcXdXYVk0dHhETmx4V2RYcm4w?= =?utf-8?B?V2o2d2dtYzEvV0dYb1g5R0xvcWc2NkUyN3BNc2VLUjVFM0E9PQ==?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <BA063BD948E02A4BB69916D9197F94DE@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB4217.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e2a1fda6-8546-444d-dc97-08d8fe80365a
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2021 13:29:49.3259 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ZJ3Vz9H9c0N/IP8O9ukV7oGBhDY9x/fKU1+AVvTuX3uqX07WZ6WWbwg9oADNfckaJMokITAkH4EbudwNkeBPjmgu9HzexsR1IQjq65heo4asXIP/U7BcX0ouLVZ1Cpx/
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4219
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Cnzu8TylnFYa5pqn3iVxCW3MyKM>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 13:29:59 -0000

SSBhZ3JlZSB3aXRoIEJhcnJ5IGluIHRoYXQgdGhpcyBzZWVtcyB0byByZXF1aXJlIG1vcmUgdGhp
bmtpbmcgYW5kIGJyb2FkZXIgcmV2aWV3IGFuZCBjb25zZW5zdXMuIENhcnN0ZW4sIHlvdSBzZWVt
IHRvIGltcGx5IHRoYXQgdGhpcyBzaG91bGQgaW5zdGVhZCBiZSByZWplY3RlZCwgd2l0aCB0aGUg
bW90aXZhdGlvbiB0aGF0IGl0IHdvdWxkIG5lZWQgYSBuZXcgZG9jdW1lbnQgKHVwZGF0aW5nIDg2
MTApLCBpcyB0aGF0IHJpZ2h0ID8NCg0KKEZvciBldmVyeWJvZHkgbm90IGZhbWlsaWFyIHdpdGgg
dGhlIGVycmF0YSBzdGF0dXMgZGVmaW5pdGlvbjogaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
ZXJyYXRhLWRlZmluaXRpb25zLw0KIEhvbGQgZm9yIGRvY3VtZW50IHVwZGF0ZTog4oCcVGhlIGVy
cmF0dW0gaXMgbm90IGEgbmVjZXNzYXJ5IHVwZGF0ZSB0byB0aGUgUkZDLiBIb3dldmVyLCBhbnkg
ZnV0dXJlIHVwZGF0ZSBvZiB0aGUgZG9jdW1lbnQgbWlnaHQgY29uc2lkZXIgdGhpcyBlcnJhdHVt
LCBhbmQgZGV0ZXJtaW5lIHdoZXRoZXIgaXQgaXMgY29ycmVjdCBhbmQgbWVyaXRzIGluY2x1ZGlu
ZyBpbiB0aGUgdXBkYXRlLuKAnQ0KUmVqZWN0ZWQ6IOKAnFRoZSBlcnJhdHVtIFsuLi5dIHByb3Bv
c2VzIGEgY2hhbmdlIHRvIHRoZSBSRkMgdGhhdCBzaG91bGQgYmUgZG9uZSBieSBwdWJsaXNoaW5n
IGEgbmV3IFJGQyB0aGF0IHJlcGxhY2VzIHRoZSBjdXJyZW50IFJGQy4gSW4gdGhlIGxhdHRlciBj
YXNlLCBpZiB0aGUgY2hhbmdlIGlzIHRvIGJlIGNvbnNpZGVyZWQgZm9yIGZ1dHVyZSB1cGRhdGVz
IG9mIHRoZSBkb2N1bWVudCwgaXQgc2hvdWxkIGJlIHByb3Bvc2VkIHVzaW5nIGNoYW5uZWxzIG90
aGVyIHRoYW4gdGhlIGVycmF0YSBwcm9jZXNzLCBzdWNoIGFzIGEgV0cgbWFpbGluZyBsaXN0LuKA
nSkNCg0KRnJhbmNlc2NhDQoNCu+7v09uIDEzLzA0LzIwMjEsIDE1OjA3LCAiQmFycnkgTGVpYmEi
IDxiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZz4gd3JvdGU6DQoNCiAgICBJbmRlZWQsIHRoaXMgb25l
IHNjcmVhbXMgIkhvbGQgZm9yIERvY3VtZW50IFVwZGF0ZSIgdG8gbWUsIGFzIGl0J3MNCiAgICBz
b21ldGhpbmcgdGhhdCByYXRoZXIgbW9yZSBjb21wbGV4LiAgSXQncyBjbGVhciB0aGF0IHRoaXMg
aXNuJ3QganVzdA0KICAgIGFuICJvb3BzIiB3aGVuIHdlIHB1Ymxpc2hlZCwgYnV0LCByYXRoZXIg
YSAodmFsaWQpIHJldGhpbmtpbmcgdGhhdA0KICAgIG5lZWRzIGJyb2FkZXIgcmV2aWV3IGFuZCBj
b25zZW5zdXMgb24gdGhlIHNvbHV0aW9uLg0KDQogICAgQmFycnkNCg0KICAgIE9uIFR1ZSwgQXBy
IDEzLCAyMDIxIGF0IDg6MTMgQU0gQ2Fyc3RlbiBCb3JtYW5uIDxjYWJvQHR6aS5vcmc+IHdyb3Rl
Og0KICAgID4NCiAgICA+IE9uIDIwMjEtMDQtMTEsIGF0IDE4OjUxLCBDYXJzdGVuIEJvcm1hbm4g
PGNhYm9AdHppLm9yZz4gd3JvdGU6DQogICAgPiA+DQogICAgPiA+IEhvd2V2ZXIsIHRoZXJlIGlz
IG9uZSBvbWlzc2lvbiBpbiB0aGUgQUJORjogdGhlIFx1IHN5bnRheCwgd2hpY2ggaXMgc29tZXdo
YXQgY29tcGxpY2F0ZWQgaW4gSlNPTiBiZWNhdXNlIGl0IGlzIGZvbGxvd2VkIGVpdGhlciBieSA0
IGhleCBkaWdpdHMgdGhhdCBhcmUgbm90IGluIHRoZSByYW5nZSBkODAwIHRvIGRmZmYgb3IgYnkg
NCBoZXggZGlnaXRzIGluIHRoZSByYW5nZSBkODAwIHRvIGRiZmYsIGFub3RoZXIgXHUsIGFuZCBm
b3VyIG1vcmUgaGV4IGRpZ2l0cyBkYzAwIHRvIGRmZmYuDQogICAgPiA+IFNvbWVvbmUgbmVlZHMg
dG8gc2l0IGRvd24gYW5kIHdyaXRlIHVwIHRoZSBBQk5GIGZvciB0aGF0IChvciBmaW5kIHNvbWUg
QUJORiB0aGF0IGFscmVhZHkgaGFzIGRvbmUgdGhlIHdvcmspLg0KICAgID4NCiAgICA+IEkgd2Fz
IHRvbyBsYXp5IHRvIGZpbmQgc29tZSBBQk5GIHNvIEkgd3JvdGUgbXkgb3duLg0KICAgID4NCiAg
ICA+IDc2Yzc2LDg0DQogICAgPiA8IFNFU0MgPSAiXCIgKCV4MjAtN0UgLyAleDgwLTEwRkZGRCkN
CiAgICA+IC0tLQ0KICAgID4gPg0KICAgID4gPiBTRVNDID0gIlwiICggJXgyMiAvICV4MkYgLyAl
eDVDIC8gJXg2MiAvICV4NjYgLyAleDZFIC8gJXg3MiAvICV4NzQgLw0KICAgID4gPiAgICAgICAg
ICAgICAgKCV4NzUgaGV4Y2hhcikgKQ0KICAgID4gPg0KICAgID4gPiBoZXhjaGFyID0gKChESUdJ
VCAvICJBIi8iQiIvIkMiIC8gIkUiLyJGIikgM0hFWERJRykgLw0KICAgID4gPiAgICAgICAgICAg
ICgiRCINCiAgICA+ID4gICAgICAgICAgICAgKCggJXgzMC0zNyAySEVYRElHICkgLw0KICAgID4g
PiAgICAgICAgICAgICAgKCgiOCIvIjkiLyJBIi8iQiIpIDJIRVhESUcgIlwiICV4NzUgIkQiDQog
ICAgPiA+ICAgICAgICAgICAgICAgKCJDIi8iRCIvIkUiLyJGIikgMkhFWERJRyApKSkNCiAgICA+
IDc5Yzg3DQogICAgPiA8IEJDSEFSID0gJXgyMC0yNiAvICV4MjgtNUIgLyAleDVELTEwRkZGRCAv
IFNFU0MgLyBDUkxGDQogICAgPiAtLS0NCiAgICA+ID4gQkNIQVIgPSAleDIwLTI2IC8gJXgyOC01
QiAvICV4NUQtMTBGRkZEIC8gU0VTQyAvICJcJyIgLyBDUkxGDQogICAgPg0KICAgID4NCiAgICA+
IFRoZSBzZWNvbmQgY2hhbmdlIGlzIG5lY2Vzc2FyeSBhcyBTRVNDIGlzIG5vdyBuYXJyb3dseSBy
ZXN0cmljdGVkIHRvIHRoZSBlc2NhcGUgY29tYmluYXRpb25zIHRoYXQgSlNPTiBhbGxvd3MgaW4g
dGV4dCBzdHJpbmdzLCBhbmQgXCcgaXMgbm90IGFtb25nIHRob3NlLg0KICAgID4NCiAgICA+IFlv
dSBjYW4gcGxheSB3aXRoIHRoaXMgY2hhbmdlZCBncmFtbWFyIGluIGNkZGxjIHZlcnNpb24gMC4w
LjMgKGBnZW0gdXBkYXRlYCBpZiBuZWVkZWQpLg0KICAgID4NCiAgICA+ID4gSeKAmW0gbm90IHN1
cmUgdGhpcyB1cGRhdGUgc2hvdWxkIGFsbCBiZSBwdXQgaW50byBhbiBlcnJhdGEgaXRlbTsgbWF5
YmUgd2Ugc2hvdWxkIHB1cnN1ZSB3cml0aW5nIHRoaXMgdXAgaW4gYSBkb2N1bWVudCB0aGF0IHVw
ZGF0ZXMgUkZDIDg2MTAgdGhhdCBjb3VsZCB0aGVuIGFsc28gYWRkIGEgbGVzcyB1bndpZWxkeSBz
eW50YXggZm9yIG5vbi1CTVAgY29kZSBwb2ludHMgc3VjaCBhcyB0aGUgdWJpcXVpdG91cyBcdXvi
gKZ9Lg0KICAgID4NCiAgICA+IEnigJltIHN0aWxsIG5vdCBlbnRpcmVseSBzdXJlIHdlIHdhbnQg
dG8gaGFuZGxlIHRoaXMgYXMgYSBib2ctc3RhbmRhcmQgZXJyYXRhIGl0ZW0uDQogICAgPiBPcGlu
aW9ucyB3ZWxjb21lLg0KICAgID4NCiAgICA+IEdyw7zDn2UsIENhcnN0ZW4NCiAgICA+DQoNCg==


From nobody Tue Apr 13 07:03:44 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03D63A1869 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 07:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 vUM7rIy6AIQf for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 07:03:35 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0684E3A185B for <cbor@ietf.org>; Tue, 13 Apr 2021 07:03:34 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FKS4h3J5wz16gW; Tue, 13 Apr 2021 16:03:32 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com>
Date: Tue, 13 Apr 2021 16:03:31 +0200
Cc: Barry Leiba <barryleiba@computer.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "smbarte2@illinois.edu" <smbarte2@illinois.edu>, "cbor@ietf.org" <cbor@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, "christoph.vigano@uni-bremen.de" <christoph.vigano@uni-bremen.de>
X-Mao-Original-Outgoing-Id: 640015410.918579-b669c03b34cf301f7491abee4101bd23
Content-Transfer-Encoding: quoted-printable
Message-Id: <46AD6448-751D-42BB-A7E9-655D5A98D9B9@tzi.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com>
To: Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/7-0jAM5C56Q89XVkCLqHWo2kMX0>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 14:03:43 -0000

Hi Francesca,

I must admit that I=E2=80=99m not really comfortable with the errata =
process.

This errata report points to a problem with the ABNF definition of CDDL =
that keeps it from upholding the promise in Section 3.1 (top of page =
16).
(Note that the note in the same paragraph is also about ABNF, but about =
how CDDL is different from ABNF, not about details of using the JSON =
string form and describing that in ABNF.  This stuff is all so meta...)

So is an update necessary?  The problem does not break existing =
specifications, as far as I know.  I would expect that implementers of =
CDDL will want to do something similar to what I did for the cddlc tool; =
the conflict between ABNF spec and text needs to be resolved in some way =
and a search for a minimal way to do so will come up with a solution =
similar to mine.
It is less clear that this minimal way is what we actually want to limit =
ourselves to.
But we *could* apply this hot fix and think about better ways to handle =
literals later, in CDDL 2.0 =E2=80=94 draft-bormann-cbor-cddl-freezer =
has a Section 3 about literal syntax.

On the other hand, a workaround for this gap will be available with =
.cat, which I think we will be moving forward even faster than the next =
CDDL version.  Having an errata report that is not just rejected but =
acknowledges the problem and possibly points to this workaround for now =
would be helpful to users.

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-04-13, at 15:29, Francesca Palombini =
<francesca.palombini=3D40ericsson.com@dmarc.ietf.org> wrote:
>=20
> I agree with Barry in that this seems to require more thinking and =
broader review and consensus. Carsten, you seem to imply that this =
should instead be rejected, with the motivation that it would need a new =
document (updating 8610), is that right ?
>=20
> (For everybody not familiar with the errata status definition: =
https://www.rfc-editor.org/errata-definitions/
> Hold for document update: =E2=80=9CThe erratum is not a necessary =
update to the RFC. However, any future update of the document might =
consider this erratum, and determine whether it is correct and merits =
including in the update.=E2=80=9D
> Rejected: =E2=80=9CThe erratum [...] proposes a change to the RFC that =
should be done by publishing a new RFC that replaces the current RFC. In =
the latter case, if the change is to be considered for future updates of =
the document, it should be proposed using channels other than the errata =
process, such as a WG mailing list.=E2=80=9D)
>=20
> Francesca
>=20
> =EF=BB=BFOn 13/04/2021, 15:07, "Barry Leiba" <barryleiba@computer.org> =
wrote:
>=20
>    Indeed, this one screams "Hold for Document Update" to me, as it's
>    something that rather more complex.  It's clear that this isn't =
just
>    an "oops" when we published, but, rather a (valid) rethinking that
>    needs broader review and consensus on the solution.
>=20
>    Barry
>=20
>    On Tue, Apr 13, 2021 at 8:13 AM Carsten Bormann <cabo@tzi.org> =
wrote:
>>=20
>> On 2021-04-11, at 18:51, Carsten Bormann <cabo@tzi.org> wrote:
>>>=20
>>> However, there is one omission in the ABNF: the \u syntax, which is =
somewhat complicated in JSON because it is followed either by 4 hex =
digits that are not in the range d800 to dfff or by 4 hex digits in the =
range d800 to dbff, another \u, and four more hex digits dc00 to dfff.
>>> Someone needs to sit down and write up the ABNF for that (or find =
some ABNF that already has done the work).
>>=20
>> I was too lazy to find some ABNF so I wrote my own.
>>=20
>> 76c76,84
>> < SESC =3D "\" (%x20-7E / %x80-10FFFD)
>> ---
>>>=20
>>> SESC =3D "\" ( %x22 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 =
/
>>>             (%x75 hexchar) )
>>>=20
>>> hexchar =3D ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
>>>           ("D"
>>>            (( %x30-37 2HEXDIG ) /
>>>             (("8"/"9"/"A"/"B") 2HEXDIG "\" %x75 "D"
>>>              ("C"/"D"/"E"/"F") 2HEXDIG )))
>> 79c87
>> < BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
>> ---
>>> BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / "\'" / CRLF
>>=20
>>=20
>> The second change is necessary as SESC is now narrowly restricted to =
the escape combinations that JSON allows in text strings, and \' is not =
among those.
>>=20
>> You can play with this changed grammar in cddlc version 0.0.3 (`gem =
update` if needed).
>>=20
>>> I=E2=80=99m not sure this update should all be put into an errata =
item; maybe we should pursue writing this up in a document that updates =
RFC 8610 that could then also add a less unwieldy syntax for non-BMP =
code points such as the ubiquitous \u{=E2=80=A6}.
>>=20
>> I=E2=80=99m still not entirely sure we want to handle this as a =
bog-standard errata item.
>> Opinions welcome.
>>=20
>> Gr=C3=BC=C3=9Fe, Carsten
>>=20
>=20
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor


From smbarte2@illinois.edu  Tue Apr 13 16:54:52 2021
Return-Path: <smbarte2@illinois.edu>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291A93A09B7 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 16:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=illinois.edu
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 aRooOrNaUBx0 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 16:54:46 -0700 (PDT)
Received: from mx0b-00007101.pphosted.com (mx0b-00007101.pphosted.com [148.163.139.28]) (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 8B9C13A09BB for <cbor@ietf.org>; Tue, 13 Apr 2021 16:54:46 -0700 (PDT)
Received: from pps.filterd (m0166260.ppops.net [127.0.0.1]) by mx0b-00007101.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 13DNqcKh032601; Tue, 13 Apr 2021 23:54:40 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=illinois.edu; h=message-id : in-reply-to : references : date : from : to : cc : subject : content-type : content-transfer-encoding : mime-version; s=campusrelays; bh=aPL9wR8iIf+ApbhhDbtkOtS2R/m8xBQmvnGA4YIqWeE=; b=Zat8Jg6GwCT5WAtBgitYhsAsmr50AsqDljSh3LLfHobuX3f/a9MfexMFrYThKbn5jTOi 2WsOXPmKeEzRWGGelOHEF08I9MpzcL3A1euvU2ICz+TgYZLm9rGn6YK5RNkfWqwO1QDw J9kmcW75H7V2A8Z7XcbkHYpbQxUpm3bAQ2i5E3ljSITd2n7tAhdwa5Od+QXqYSilhcGX iJ/6jlGxTxLNvj0/nhe7VjN7srb3EeBKv0JWxv37PRT3VfbfR5Ppv0KctXDFsIaybhtZ 3nI2znShZR3QKbTyaXpKZDxfCk0YM27Df5ISri8K7s6hGmjhjh5e624zNkWqwyZRDwpr pQ== 
Received: from nam04-dm6-obe.outbound.protection.outlook.com (mail-dm6nam08lp2047.outbound.protection.outlook.com [104.47.73.47]) by mx0b-00007101.pphosted.com with ESMTP id 37vu17q24n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 13 Apr 2021 23:54:40 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EigGvCOgzN2kwG6Bqr6lt8cbdKkIRYHXdRhaHCwlHr8ziWHHES6fAvBJvL6IoMHFAOBlpGr3PE7GsrLx+gwlN8klNC7irJhfVZJLTNyWsCv2fXBwsRRPDNHyQSo7EUlBfxuHA9+CT8qxEIAIH6lGQRouW40oYK1UcP201D74PM552/Udp/39tluH5pAg12slq+EqLhzmVMweqiFqH8Hg8RWPpFqfLRR6eoQQAMQtKk+ZY+qPFR5btxxtPSOMD4x8QsgZt8TNS2AWIgqyLi0e3fBdJkugy2RG8z+saK5WzeE90XdJ2PT68BRyypL5QV9s3Uc1aom4S8C/NnRDWfgyOQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aPL9wR8iIf+ApbhhDbtkOtS2R/m8xBQmvnGA4YIqWeE=; b=BhbdvRv0YcWMYyj2DXNKyz/6qlTErKzPQjrSMoy5sGwpvUQPXnC2y0KJiq9fZvSFwKVphH40fWSddjKBGeuosVg3Yx7s2mHdOQFq7o1LeQxjJCZyJaP+i2E4m2f3jadHrm0PUIHoL4FWBwjzmFPXx11M+Y0rMZ0Pw5iJ7WhNMM3uLhCfHgeU46++fePZ9Mq5eQmE4HeW2Mj10Z7tayfLkMQ12LZYaGrSluywKxffcY6VwNnDo/suBemwPLpUygJhVWSzNlpRF5LsFhoaeDaBV8JcypkOQxw80aIHJOb+qpMFst+C5jpviQhBfzG6XV/dVutOsFQmrH86zCyjzojhDw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=illinois.edu; dmarc=pass action=none header.from=illinois.edu; dkim=pass header.d=illinois.edu; arc=none
Authentication-Results: amsuess.com; dkim=none (message not signed) header.d=none;amsuess.com; dmarc=none action=none header.from=illinois.edu;
Received: from DM6PR11MB3834.namprd11.prod.outlook.com (2603:10b6:5:137::27) by DM5PR11MB0060.namprd11.prod.outlook.com (2603:10b6:4:63::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.27; Tue, 13 Apr 2021 23:54:39 +0000
Received: from DM6PR11MB3834.namprd11.prod.outlook.com ([fe80::345a:a90f:6d5f:fe3e]) by DM6PR11MB3834.namprd11.prod.outlook.com ([fe80::345a:a90f:6d5f:fe3e%7]) with mapi id 15.20.4020.022; Tue, 13 Apr 2021 23:54:39 +0000
X-ME-Sender: <xms:Oy92YF3j-iMsFfyuJ2FkSH-_6PpOQ-L7HFLbOrzRRCQizwSPiI11xA> <xme:Oy92YMF4ykElbqYCVgpzNN9aILGx-2y2QqRuuJWNtudRNqUow3QMUA7NuHwS2Fw51 retkCitqB61aODOHNs>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeltddgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfufgv rghnuceurghrthgvlhhlfdcuoehsmhgsrghrthgvvdesihhllhhinhhoihhsrdgvughuqe enucggtffrrghtthgvrhhnpeeikeffheethfffvdeikedtlefhieekhfejueetteejkeel tedvleevjedvgeefveenucffohhmrghinheprhhftgdqvgguihhtohhrrdhorhhgpdhurh hluggvfhgvnhhsvgdrtghomhdpihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepsggrrhhtvghllhdomhgvshhmthhprghuth hhphgvrhhsohhnrghlihhthidqleefheduvddvtddtqddvtdeileduleeikedqshhmsggr rhhtvgdvpeepihhllhhinhhoihhsrdgvughusehsvghnthdrtghomh
X-ME-Proxy: <xmx:Oy92YF4o_5KJ0BoLCaxb-YlBuRx5tKR5Xt76RCdU6_IDSSIp0bCG1A> <xmx:Oy92YC0QdNSYEQcEObTsYkZ1lJyrgUrpc9oyzNm_mBY_m7OcFok_Vw> <xmx:Oy92YIEVs-dg6mmvfMhjhx1fK5CHvm9uLgVtxiKEAAsgfKOyE4M-Lw> <xmx:PS92YNMZy1L6diNT2h3ctuR851kd-nFL6j85mfq5c_fxa7GRC_47r-myWKw>
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249
Message-Id: <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com>
In-Reply-To: <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com>
Date: Tue, 13 Apr 2021 18:54:15 -0500
From: "Sean Bartell" <smbarte2@illinois.edu>
To: "Carsten Bormann" <cabo@tzi.org>, "Francesca Palombini" <francesca.palombini=40ericsson.com@dmarc.ietf.org>
Cc: "Barry Leiba" <barryleiba@computer.org>, "Henk Birkholz" <henk.birkholz@sit.fraunhofer.de>, "cbor@ietf.org" <cbor@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>, =?UTF-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, "christoph.vigano@uni-bremen.de" <christoph.vigano@uni-bremen.de>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [66.111.4.227]
X-ClientProxiedBy: MN2PR16CA0042.namprd16.prod.outlook.com (2603:10b6:208:234::11) To DM6PR11MB3834.namprd11.prod.outlook.com (2603:10b6:5:137::27)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from auth1-smtp.messagingengine.com (66.111.4.227) by MN2PR16CA0042.namprd16.prod.outlook.com (2603:10b6:208:234::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.16 via Frontend Transport; Tue, 13 Apr 2021 23:54:38 +0000
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])	by mailauth.nyi.internal (Postfix) with ESMTP id 9F17427C0061; Tue, 13 Apr 2021 19:54:37 -0400 (EDT)
Received: from imap10 ([10.202.2.60])  by compute6.internal (MEProxy); Tue, 13 Apr 2021 19:54:37 -0400
Received: by mailuser.nyi.internal (Postfix, from userid 501)	id 8FF1E4E009D;  Tue, 13 Apr 2021 19:54:35 -0400 (EDT)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 363728a9-8138-46b7-918a-08d8fed77fbd
X-MS-TrafficTypeDiagnostic: DM5PR11MB0060:
X-Microsoft-Antispam-PRVS: <DM5PR11MB0060AE2B35808BD32C7E7D97F74F9@DM5PR11MB0060.namprd11.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: nqi2goGnSiBO08wxhW829cKnHd8Z+74E9jyCfJMf98M4TkVluqzkEEIaTutJJb0fIXGvnfPNY6PMzq7Ss+k8qRSI3OPhdCO0o+81EsPZQn/jvlF0F+XCFnP7iLHIcvvrkjykQ+npUAlutpe1swsedUgCx8X0dglvgcO7r2KVqiAU+xpNLBF/TfPgVW6WFxL2cYqelKDkfPeEM69ql3QOLVP8XpKhLolnjD9Y+AM+ph0PWVgi5rQUvR4/j/9OvAHagcgs/clk1CVwkI+XJXOAm3IydEibHOsWJR8C5E4HbWUXn887u7QK1HK/ob41d2AfzMVo2SCcNjAP6KyxwDY2Yc/XXE1z5QOWOGvTN5WwSKlN125Iq0u9aSDSEiKmVT/RDmBjDl+TV+vg1r0pCgdLzg+uYUvMqhIDN+QBpV8t8kdvHFy3Gki/HGNuY9RpoAeRMJVZmKqPbFlTUwtsut8Iz2ozoBi+E/S1+J4EvPeKkud3DyvBB/6T7rptaZhCB7MD9f6BU20kwDKQwoHTic43aUoVDzuJdUbC8Aw7GEeO2Z3I33kml1KohVWnE107mxz1crp7ENiuVwAl074S/re4eRfFXhcgxG3TZqeNtO1uNoGYGUxnE28edZmf84L1rmCc7MFpR92YmdJ1Yihie/BAjLt8N8YwFtYp657iAQd3dkDW3hU49sdIDDPn5gZ0XBiVvWZjyFMnbtww5fYs02Yhr6EKgk3JoP5RG3VTyJVYPp1//OGmbeXIxVqogGK3NMDjJ+mwJh2t3vs8JN6/olsBf/7tmcFl6cMaaQlhmyuHOLk=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB3834.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(39840400004)(396003)(136003)(366004)(376002)(8676002)(66946007)(75432002)(53546011)(9686003)(2906002)(66476007)(31696002)(786003)(66556008)(38350700002)(54906003)(52116002)(38100700002)(8936002)(83380400001)(6666004)(316002)(110136005)(478600001)(5660300002)(186003)(4326008)(26005)(6266002)(31686004)(42186006)(966005)(86362001)(40310500001)(40720500001); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?M0VJcmI5QjBwSzlaTVZodGM3OHV2dktPUkt1aDgvaHBJaHhUNGlwMy9ZZ3FL?= =?utf-8?B?MUZnQUNabkFrb0Q3ZUxNTFpaU0JxRUxCa2pWWG1tTkxxRFRFV0R2NXRNQ3p5?= =?utf-8?B?RWZ1RzNxZEhNKzZQUUp2WVV0UmhWR0FrYmJLdGJJc2dlT0k4ME4xd0FvTWJO?= =?utf-8?B?dDNjdTJ3QXVic0E5b0NsSjQxeGk0dXdaSTcvcmNpZjIzSzIrdUFtQ2RlTmps?= =?utf-8?B?U0ZqUWVzZWRwUGxOU1VzVTgzOWtadExubmwxRkNGQ2xyQzNrTlNSVHpxUkps?= =?utf-8?B?UVdSVEtkS0pnK1l1Y2l2N2RJOFRXdEE3SE03eFpJSXRYSkdDUjBpQ0VKMTdS?= =?utf-8?B?NTUyaytrZXBLY0tKUG9FSXE2UXQwb2srSnJQYXlHT0JMb0RZa1R4TmtOMXdM?= =?utf-8?B?YUVBNHRZWHNNcENlM2dBQ3RGZ2o4Z3ArUTlYVDhLQy9sM3RTSlZqSVR3YzMz?= =?utf-8?B?OExkZEExa3dWMERxSkhwMEJZS29xbTAycXVhbEdwSFFmKzg2cFRJb0FnNU0v?= =?utf-8?B?dDJ2OSs5ZHJ0QmlxZ2xhZ2Y0Zncyd1VmamJuTWFHSGRsekNVYW91Wk1jSFQy?= =?utf-8?B?bkpicDE3VUltdXdDZ1BmR1VlbTEzQ2FxK3Z5UEFZYkRhRXBkY3lid0lzOWxI?= =?utf-8?B?Qy8rN2w4SmVSSEVZd1VCaGRPMDNOcEk5ancvR2tiRGhIamxPMzIzanhzenhF?= =?utf-8?B?ZlhIVUF4OGcxQVNwQ2VnWnVsdW9FU0hVZERWbnpwQ2t4Z1VhUDhqZkVFMmc5?= =?utf-8?B?ck45RkowbXFzNTh1eGhsZFJVY2xUSmYrQ3FMbEg2OVZpY3FrS1Q4cHhEdCtK?= =?utf-8?B?Ykx1WnJ0N1VTRkhrU0xaRWxrMnZEQjZPOEtXNTBRd3BYc1p3U1l0bjcwVlhT?= =?utf-8?B?NW0wYWVVMllGVS9EekpqdUJyTERIMExEc1JYVHlqRzdhSmZibnN1TXVRcSt6?= =?utf-8?B?bm84ZjNaMTc2UmRwVkROOW5uVCsxS1BCTURrRVVqR0NsQW5RRHIyZkNMcGhz?= =?utf-8?B?Sk5xUGNIdk83UEN3VkgrVWo2cGMwbkgyTWtNM05nY1RLellaYkgrNDY2WGs0?= =?utf-8?B?K1BYZXgrVHVUaHEvTWhMbU5SSk9NVWF2ZmhiVHlRM1FxMURLQjg2SzI1cFFH?= =?utf-8?B?YW9ueXpYb1djSUV6WCtUc2ZCcjBQL2llbnJPN0E4Rzl6UDN6Z3BCeEdnTWE5?= =?utf-8?B?ajVSSGZ3dE43MmhPLzc2bzB3YVp2NmtvU3dZRkk1MzFGYjZSbndxQkxuN1pG?= =?utf-8?B?Q0hoK2NqQWRST2VTeGw0VVBJNHd0N2kyZFAzMktyT2gzZEk3RitXcnBnbXNU?= =?utf-8?B?SitYMG9YRnBFMW9MM2Z6b29xMHVjeERCYkFrK3JVcmFzMFhaTjNFTm8rMlVC?= =?utf-8?B?Vjc5UTBHUDNVVFhDM1Ryd2NNR1lNcDdFaWp4Sis1T1Ywa0dycUlZVHlJSENI?= =?utf-8?B?cVRvdDdPdEJrM2VQbUtheVlFQ2ZsMit1dDA4VXF2UGxHaXZ3b1dHM2sxYUJ4?= =?utf-8?B?K05rK1g3dTRERjRrZkQ3ZFF5RlFTU24vYitFRmZ2SmpqYVZkaHZuTnRlZGlk?= =?utf-8?B?d0R3NitydHI5bDVTRmMrelo1RTE1ajBqVGJzcXU1Z25oRTdvNzBhQzZUYytK?= =?utf-8?B?Rk5NRU9PSkQ4bksxNE5vZ2ZjSE1DeS9BR1J1M0FBLzFIOWtuVldyYTd3Sk9F?= =?utf-8?B?dEF4UDRKN3E0c1g3Zy9pR1dsMEtjZHQ5L05HSVJDeGk0SHlLNmpkNUEyK2g2?= =?utf-8?Q?rl+PUKwaWJCgnVN0xpfl1120HmS85DdhgVsCv/X?=
X-OriginatorOrg: illinois.edu
X-MS-Exchange-CrossTenant-Network-Message-Id: 363728a9-8138-46b7-918a-08d8fed77fbd
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB3834.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Apr 2021 23:54:38.9627 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 44467e6f-462c-4ea2-823f-7800de5434e3
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 8fjWPJkEB/TyuzdGxrHdWjFOTOEtcataNdy7wGyvtSQMtOi82p9l2DHpsnOjm0JZ0tb08imGSfxJeRjAmu9KJg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB0060
X-Proofpoint-GUID: 4sFyAzLKNTzePr5X6D8FgmWv8NlUE8gN
X-Proofpoint-ORIG-GUID: 4sFyAzLKNTzePr5X6D8FgmWv8NlUE8gN
X-Spam-Details: rule=cautious_plus_nq_notspam policy=cautious_plus_nq score=0 impostorscore=0 phishscore=0 spamscore=0 adultscore=0 mlxlogscore=999 malwarescore=0 lowpriorityscore=0 suspectscore=0 bulkscore=0 clxscore=1011 mlxscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104130156
X-Spam-OrigSender: smbarte2@illinois.edu
X-Spam-Bar: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/El5mbcWhL-LBvNXel-6-K_r4Bc4>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 00:25:25 -0000

> >    On Tue, Apr 13, 2021 at 8:13 AM Carsten Bormann <cabo@tzi.org> wrote=
:
> >>=20
> >> I was too lazy to find some ABNF so I wrote my own.
> >>=20
> >> 76c76,84
> >> < SESC =3D "\" (%x20-7E / %x80-10FFFD)
> >> ---
> >>>=20
> >>> SESC =3D "\" ( %x22 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 =
/
> >>>             (%x75 hexchar) )
> >>>=20
> >>> hexchar =3D ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
> >>>           ("D"
> >>>            (( %x30-37 2HEXDIG ) /
> >>>             (("8"/"9"/"A"/"B") 2HEXDIG "\" %x75 "D"
> >>>              ("C"/"D"/"E"/"F") 2HEXDIG )))
> >> 79c87
> >> < BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
> >> ---
> >>> BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / "\'" / CRLF
> >>=20
> >>=20
> >> The second change is necessary as SESC is now narrowly restricted to t=
he escape combinations that JSON allows in text strings, and \' is not amon=
g those.
> >>=20

This ABNF looks correct to me, but it obfuscates more than it clarifies. I =
would suggest following the example of the JSON RFC (https://www.rfc-editor=
.org/rfc/rfc8259.html#section-7). The ABNF there allows arbitrary hex digit=
s (%x75 4HEXDIG), but the text clarifies how non-BMP characters are handled=
. A similar situation already exists for base64 bytestrings, for which CDDL=
's ABNF allows invalid base64.

It's also not clear to me whether \' should be allowed in text strings, or =
whether \" should be allowed in byte strings. Allowing them would make both=
 types of strings consistent with each other, but prohibiting them would le=
t text strings use the exact same syntax as JSON. And one more issue: the A=
BNF currently allows CRLF in unprefixed byte strings, and I'm not sure whet=
her that's intentional.

> > On 2021-04-13, at 15:29, Francesca Palombini <francesca.palombini=3D40e=
ricsson.com@dmarc.ietf.org> wrote:
> >=20
> > I agree with Barry in that this seems to require more thinking and broa=
der review and consensus. Carsten, you seem to imply that this should inste=
ad be rejected, with the motivation that it would need a new document (upda=
ting 8610), is that right ?
> >=20
> > (For everybody not familiar with the errata status definition: https://=
urldefense.com/v3/__https://www.rfc-editor.org/errata-definitions/__;!!DZ3f=
jg!soSEF4XBhOUPRdN5wSzvAeVKOyu_4HkZe_d06IEV4huYgnyqgimjYJH9OeHL0LITxA8$=20
> > Hold for document update: =E2=80=9CThe erratum is not a necessary updat=
e to the RFC. However, any future update of the document might consider thi=
s erratum, and determine whether it is correct and merits including in the =
update.=E2=80=9D
> > Rejected: =E2=80=9CThe erratum [...] proposes a change to the RFC that =
should be done by publishing a new RFC that replaces the current RFC. In th=
e latter case, if the change is to be considered for future updates of the =
document, it should be proposed using channels other than the errata proces=
s, such as a WG mailing list.=E2=80=9D)

More guidance on the errata process (https://www.ietf.org/about/groups/iesg=
/statements/processing-rfc-errata/): "Changes that modify the working of a =
protocol to something that might be different from the intended consensus w=
hen the document was approved should be either Hold for Document Update or =
Rejected. Deciding between these two depends on judgment. Changes that are =
clearly modifications to the intended consensus, or involve large textual c=
hanges, should be Rejected. In unclear situations, small changes can be Hol=
d for Document Update."

As I interpret it, if this is a "small change", and there was no clear "int=
ended consensus" about which escape codes should be allowed, the erratum ca=
n be marked as "Hold for Document Update".

FWIW, I'm not actually using CDDL at the moment. I'm using the extended dia=
gnostic notation, and I was using the CDDL ABNF to narrow down my choice of=
 syntax.

Sean


From nobody Tue Apr 13 22:54:00 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1873A0AA7 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 22:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 dDDoLjyjexvA for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 22:53:54 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5F063A0A9F for <cbor@ietf.org>; Tue, 13 Apr 2021 22:53:53 -0700 (PDT)
Received: from [192.168.217.110] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FKs9C376nzyV2; Wed, 14 Apr 2021 07:53:51 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com>
Date: Wed, 14 Apr 2021 07:53:50 +0200
Cc: Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>, Barry Leiba <barryleiba@computer.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "cbor@ietf.org" <cbor@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, "christoph.vigano@uni-bremen.de" <christoph.vigano@uni-bremen.de>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com> <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com>
To: Sean Bartell <smbarte2@illinois.edu>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/bDVcl5zxrcqAw-4H-XqY9ap628Q>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 05:53:59 -0000

> This ABNF looks correct to me, but it obfuscates more than it =
clarifies.

I don=E2=80=99t agree =E2=80=94 it is a very clear statement of what is =
allowed.

> I would suggest following the example of the JSON RFC =
(https://www.rfc-editor.org/rfc/rfc8259.html#section-7). The ABNF there =
allows arbitrary hex digits (%x75 4HEXDIG), but the text clarifies how =
non-BMP characters are handled.

RFC 8259 is a product of a process that was more political than =
technical.  There was a lot of discussion of unpaired surrogates etc., =
spilling over from UTF-16 land.
There was always a danger of ECMA bursting out of the fragile agreement =
to align ECMA 404 and RFC 8259, and that precarious situation limited =
the amount of fixing that could be done between 7159 and 8259.
While RFC 8259 makes it clear that the JSON text itself needs to be =
UTF-8, it wasn't really possible to summon the courage to write text =
that explicitly disallows constructing invalid text from escapes in text =
string data items.

To summarize, RFC 8259 is in many ways not a good model for how to =
specify things.

As my ABNF proposal shows, it is easy to specify how surrogates can be =
used in the ABNF, and doing that saves a validation process step in the =
implementation.

> A similar situation already exists for base64 bytestrings, for which =
CDDL's ABNF allows invalid base64.

Yes, but it is much harder to do an ABNF that combines all the syntax =
for whitespace, comments, *and* that for base64.

> It's also not clear to me whether \' should be allowed in text =
strings,

The text in section 3.1 doesn=E2=80=99t support allowing that:

   o  Text strings are enclosed by double quotation '"' characters.
      They follow the conventions for strings as defined in Section 7 of
      [RFC8259].  [=E2=80=A6]

> or whether \" should be allowed in byte strings.

It is:

      If unprefixed, the string is
      interpreted as with a text string, except that single quotes must
      be escaped and that the resulting UTF-8 bytes are marked as a byte
      string (major type 2).

Note the absence of a statement like =E2=80=9Cdouble quotes must not be =
escaped=E2=80=9D.

> Allowing them would make both types of strings consistent with each =
other, but prohibiting them would let text strings use the exact same =
syntax as JSON.

JSON doesn=E2=80=99t have byte strings, but for text strings we indeed =
should have full alignment.

> And one more issue: the ABNF currently allows CRLF in unprefixed byte =
strings, and I'm not sure whether that's intentional.

It is.
(And that is important for draft-ietf-cbor-cddl-control.)

BTW:
> FWIW, I'm not actually using CDDL at the moment. I'm using the =
extended diagnostic notation, and I was using the CDDL ABNF to narrow =
down my choice of syntax.

Maybe providing ABNF for EDN would be a good idea, after all.
It *is* subtly different in a number of details from CDDL syntax.
One formal interpretation of EDN syntax (albeit not in ABNF form, as it =
predates the abnftt tool) can be found in =
https://github.com/cabo/cbor-diag/blob/master/lib/cbor-diag-parser.treetop=
 (and, yes, this contains the equivalent of the surrogate pair handling =
that is in the ABNF I proposed).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr 14 02:21:07 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1DC3A124C for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:02:42 -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, 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 icM4uQoe3y0a for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:02:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6F303A1241 for <cbor@ietf.org>; Sun, 11 Apr 2021 09:02:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2F39DF4078C; Sun, 11 Apr 2021 09:02:26 -0700 (PDT)
To: henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org, superuser@gmail.com, francesca.palombini@ericsson.com, barryleiba@computer.org, christian@amsuess.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: smbarte2@illinois.edu, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210411160226.2F39DF4078C@rfc-editor.org>
Date: Sun, 11 Apr 2021 09:02:26 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/3b3RVBGIBiVrb1C-cuec4gYKYPs>
X-Mailman-Approved-At: Wed, 14 Apr 2021 02:21:06 -0700
Subject: [Cbor] [Editorial Errata Reported] RFC8610 (6526)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 16:02:42 -0000

The following errata report has been submitted for RFC8610,
"Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6526

--------------------------------------
Type: Editorial
Reported by: Sean Bartell <smbarte2@illinois.edu>

Section: G.2

Original Text
-------------
   The escaping rules of JSON strings are applied equivalently for
   text-based byte strings, e.g., "\" stands for a single backslash and
   "'" stands for a single quote.  Whitespace is included literally,
   i.e., the previous section does not apply to text-based byte strings.

Corrected Text
--------------
   The escaping rules of JSON strings are applied equivalently for
   text-based byte strings, e.g., "\" stands for a single backslash and
   "\'" stands for a single quote.  Whitespace is included literally,
   i.e., the previous section does not apply to text-based byte strings.

Notes
-----
"\" and "'" need a backslash to escape them.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 14 02:21:11 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E483A12B3 for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:11:01 -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, 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 6Tm0hUynbYGA for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:10:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 272DD3A12AF for <cbor@ietf.org>; Sun, 11 Apr 2021 09:10:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9648FF40799; Sun, 11 Apr 2021 09:10:45 -0700 (PDT)
To: henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org, superuser@gmail.com, francesca.palombini@ericsson.com, barryleiba@computer.org, christian@amsuess.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: smbarte2@illinois.edu, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210411161045.9648FF40799@rfc-editor.org>
Date: Sun, 11 Apr 2021 09:10:45 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/WI3Lpora3FTZrAzOpKDMW55txwA>
X-Mailman-Approved-At: Wed, 14 Apr 2021 02:21:06 -0700
Subject: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 16:11:02 -0000

The following errata report has been submitted for RFC8610,
"Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6527

--------------------------------------
Type: Technical
Reported by: Sean Bartell <smbarte2@illinois.edu>

Section: B

Original Text
-------------
     SESC = "\" (%x20-7E / %x80-10FFFD)

Corrected Text
--------------
     SESC = "\" (%x22 / %x27 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 / %x75 4HEXDIG )

Notes
-----
The ABNF rule for string escape codes should specify which escape codes are allowed, and also specify that "\u" must be followed by four hex digits. My suggested correction is based on JSON, but with the addition of "\'" (single quote) for use in text-based byte strings (section G.2). (Presumably, characters outside the BMP must be escaped using a surrogate pair, as in JSON.)

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 14 02:21:15 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D3E3A0C59 for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 17:13:41 -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, 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 kEFzg25dQZax for <cbor@ietfa.amsl.com>; Tue, 13 Apr 2021 17:13:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0CBD3A0C4E for <cbor@ietf.org>; Tue, 13 Apr 2021 17:13:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EE85DF40791; Tue, 13 Apr 2021 17:13:22 -0700 (PDT)
To: henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org, superuser@gmail.com, francesca.palombini@ericsson.com, barryleiba@computer.org, christian@amsuess.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: smbarte2@illinois.edu, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210414001322.EE85DF40791@rfc-editor.org>
Date: Tue, 13 Apr 2021 17:13:22 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/t3RR6dbywM5KM7UeWtArJPFem3M>
X-Mailman-Approved-At: Wed, 14 Apr 2021 02:21:06 -0700
Subject: [Cbor] [Technical Errata Reported] RFC8610 (6543)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 00:13:42 -0000

The following errata report has been submitted for RFC8610,
"Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6543

--------------------------------------
Type: Technical
Reported by: Sean Bartell <smbarte2@illinois.edu>

Section: B

Original Text
-------------
     bytes = [bsqual] %x27 *BCHAR %x27
     BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF

Corrected Text
--------------
     bytes = %x27 *BCHAR %x27
           / bsqual %x27 *QCHAR %x27
     BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
     QCHAR = DIGIT / ALPHA / "+" / "/" / "-" / "_" / "=" / WS

Notes
-----
Section 3.1 states that comments are allowed in prefixed byte strings. This correction explicitly uses WS (which includes comments) in the rule for prefixed byte strings. Although the original ABNF would allow *most* comments, it would prohibit comments including a single quote, or comments with a backslash at the end of the line.

My correction allows prefixed byte strings to use every hex and base64 character. Alternatively, the ABNF could be narrowed down using separate rules for hex and base64, or it could be broadened to allow other characters. The ultimate effect would be the same regardless.

Note that both the original and corrected ABNF allow CRLF in unprefixed bytestrings.

(Note: Unlike my previous two errata, which affected unprefixed byte strings, this one affects prefixed byte strings.)

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 14 06:14:31 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5A053A0F02 for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 06:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 0DIE6qAt5_-I for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 06:14:23 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F14C3A0EF6 for <cbor@ietf.org>; Wed, 14 Apr 2021 06:14:23 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FL2xS2yGSz1058; Wed, 14 Apr 2021 15:14:20 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210414001322.EE85DF40791@rfc-editor.org>
Date: Wed, 14 Apr 2021 15:14:19 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, christoph.vigano@uni-bremen.de, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, Barry Leiba <barryleiba@computer.org>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, cbor@ietf.org, smbarte2@illinois.edu
X-Mao-Original-Outgoing-Id: 640098858.696261-1b6dda42fca8df7d5dbc06f9986f7a5c
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D880912-A489-4534-A05E-6B8129DB3614@tzi.org>
References: <20210414001322.EE85DF40791@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/ekFn8a4GbUQAk4nyhc-Il-ZRLZc>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6543)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 13:14:29 -0000

Hi Sean,

Thank you for submitting this report.

I don=E2=80=99t think bare single quotes are meant to be allowed in =
(comments in) qualified (h or b64 prefixed) byte string literals in =
CDDL.  The text doesn=E2=80=99t really say, and the grammar isn=E2=80=99t =
favorable.

The problem with =E2=80=9Cfixing=E2=80=9D this ABNF to allow that is =
that it would typically be implemented as a two-level (three-level?) =
grammar, first processing the string syntax (e.g., handling the \=E2=80=99=
 processing) and then applying the WS syntax (e.g., comments) for the =
bsqual cases, and then the b64/b16 decoding.
But the other implementation approach, handling everything at the first =
level, is also valid.
This will make it require extra effort to get interoperability out of =
embedded single quotes.

I think most CDDL specification writers will survive without single =
quotes in comments in qualified byte string literals, at least until we =
review and update this specification.
Details like this generally need some WG time to resolve.

I put some text about the two open errata reports into =
draft-bormann-cbor-cddl-freezer, which is a list of items to consider =
during the next review and update of RFC 8610; will post the updated I-D =
SOON.

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-04-14, at 02:13, RFC Errata System <rfc-editor@rfc-editor.org> =
wrote:
>=20
> The following errata report has been submitted for RFC8610,
> "Concise Data Definition Language (CDDL): A Notational Convention to =
Express Concise Binary Object Representation (CBOR) and JSON Data =
Structures".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6543
>=20
> --------------------------------------
> Type: Technical
> Reported by: Sean Bartell <smbarte2@illinois.edu>
>=20
> Section: B
>=20
> Original Text
> -------------
>     bytes =3D [bsqual] %x27 *BCHAR %x27
>     BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
>=20
> Corrected Text
> --------------
>     bytes =3D %x27 *BCHAR %x27
>           / bsqual %x27 *QCHAR %x27
>     BCHAR =3D %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
>     QCHAR =3D DIGIT / ALPHA / "+" / "/" / "-" / "_" / "=3D" / WS
>=20
> Notes
> -----
> Section 3.1 states that comments are allowed in prefixed byte strings. =
This correction explicitly uses WS (which includes comments) in the rule =
for prefixed byte strings. Although the original ABNF would allow *most* =
comments, it would prohibit comments including a single quote, or =
comments with a backslash at the end of the line.
>=20
> My correction allows prefixed byte strings to use every hex and base64 =
character. Alternatively, the ABNF could be narrowed down using separate =
rules for hex and base64, or it could be broadened to allow other =
characters. The ultimate effect would be the same regardless.
>=20
> Note that both the original and corrected ABNF allow CRLF in =
unprefixed bytestrings.
>=20
> (Note: Unlike my previous two errata, which affected unprefixed byte =
strings, this one affects prefixed byte strings.)
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC8610 (draft-ietf-cbor-cddl-08)
> --------------------------------------
> Title               : Concise Data Definition Language (CDDL): A =
Notational Convention to Express Concise Binary Object Representation =
(CBOR) and JSON Data Structures
> Publication Date    : June 2019
> Author(s)           : H. Birkholz, C. Vigano, C. Bormann
> Category            : PROPOSED STANDARD
> Source              : Concise Binary Object Representation Maintenance =
and Extensions
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>=20
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor


From nobody Wed Apr 14 07:25:44 2021
Return-Path: <doug@ewellic.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C20D3A0DB5 for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 BvbAMOT_7mmF for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:25:39 -0700 (PDT)
Received: from p3plsmtpa08-02.prod.phx3.secureserver.net (p3plsmtpa08-02.prod.phx3.secureserver.net [173.201.193.103]) (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 EA8C23A0DB0 for <cbor@ietf.org>; Wed, 14 Apr 2021 07:25:38 -0700 (PDT)
Received: from DESKTOPLPOB1E4 ([71.237.1.75]) by :SMTPAUTH: with ESMTPSA id WgSXlq9L1NBMaWgSXlHc3a; Wed, 14 Apr 2021 07:25:38 -0700
X-CMAE-Analysis: v=2.4 cv=VK8YI/DX c=1 sm=1 tr=0 ts=6076fb62 a=6nY1uNNCgC/8Ccg2lpAcFA==:117 a=6nY1uNNCgC/8Ccg2lpAcFA==:17 a=IkcTkHD0fZMA:10 a=nORFd0-XAAAA:8 a=j6Q8m6KLQMQEAyPOhxQA:9 a=QEXdDO2ut3YA:10 a=AYkXoqVYie-NGRFAsbO8:22
X-SECURESERVER-ACCT: doug@ewellic.org
From: "Doug Ewell" <doug@ewellic.org>
To: "'Carsten Bormann'" <cabo@tzi.org>, "'Sean Bartell'" <smbarte2@illinois.edu>
Cc: <christoph.vigano@uni-bremen.de>, "'Henk Birkholz'" <henk.birkholz@sit.fraunhofer.de>, "'Francesca Palombini'" <francesca.palombini=40ericsson.com@dmarc.ietf.org>, <cbor@ietf.org>, "'Murray S. Kucherawy'" <superuser@gmail.com>, =?utf-8?Q?'Christian_Ams=C3=BCss'?= <christian@amsuess.com>, "'Barry Leiba'" <barryleiba@computer.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com> <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com> <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org>
In-Reply-To: <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org>
Date: Wed, 14 Apr 2021 08:25:38 -0600
Message-ID: <000001d7313a$0b2e8020$218b8060$@ewellic.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEBA1vMKGz097JJaR0iVVtQal8dHwIFKGGgAqHA9PQA8MAZHwHad349Agap2QAB7Q+rvQJqLUFPq/Hr4lA=
Content-Language: en-us
X-CMAE-Envelope: MS4xfGB97JvplI3QO9YWBJW4gIHn2GdDj3aBDJKIzl3C3N/lBfApgQPoqq3p2DiTvvsaIWRTei/IyM84NG4vvMJ09cTsyKdkhju3KUpNqNrL7us349gTEIC7 ZQifv+KWXP9nvjrZi7xeh/LjSBKnwRzyJPRe0DDAGWsh3wpEPv8TtrHQJjYwLHjAZ+noB/1GD1WzujhjrXvCDNyTQBlyGzFef6MYTpAlMBXYyHmkqtLc4nL3 IDo16v2cTGfp1Eo9R9KruiqCb0tUkIQefJC9fR11vPoTupRexMLcno1WCmg08qCbDlZ1901OjhP+5TORfOT9RcALLSkF0r3YcQnbMOi+QFJHhkHR18vft+/V lZ15ObL51GMkOEfUOYEIAOsOb67IkvZwoU1Zz1EIiDIXZD4O4dqCiUTVQL5jvBjIzigmRLdLxjsGGWfNz1yxeo1LFXNC8I1qqiYz9arlI5Ye61M/9Gpnb7bN Y3I2CJfjoxTZCgzr
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/hTbmeHb8MeaOkEuLhr1X2Wbds5c>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 14:25:44 -0000

Carsten Bormann replied to Sean Bartell:

>> This ABNF looks correct to me, but it obfuscates more than it
>> clarifies.
>
> I don=E2=80=99t agree =E2=80=94 it is a very clear statement of what =
is allowed.

I'd like to see separate ABNF definitions for UNICODE_SCALAR_VALUE, =
HIGH_SURROGATE, and LOW_SURROGATE, and then see 'hexchar' defined in =
terms of those. I think that would make it clearer what is going on.

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org



From nobody Wed Apr 14 07:29:39 2021
Return-Path: <doug@ewellic.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9079F3A1043 for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 bIPW1q5TVkVb for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:29:27 -0700 (PDT)
Received: from p3plsmtpa08-02.prod.phx3.secureserver.net (p3plsmtpa08-02.prod.phx3.secureserver.net [173.201.193.103]) (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 4BAF73A0DF7 for <cbor@ietf.org>; Wed, 14 Apr 2021 07:29:27 -0700 (PDT)
Received: from DESKTOPLPOB1E4 ([71.237.1.75]) by :SMTPAUTH: with ESMTPSA id WgWDlqABYNBMaWgWElHcOU; Wed, 14 Apr 2021 07:29:26 -0700
X-CMAE-Analysis: v=2.4 cv=VK8YI/DX c=1 sm=1 tr=0 ts=6076fc46 a=6nY1uNNCgC/8Ccg2lpAcFA==:117 a=6nY1uNNCgC/8Ccg2lpAcFA==:17 a=IkcTkHD0fZMA:10 a=nORFd0-XAAAA:8 a=WNBxxPohtitCnqZiEOEA:9 a=QEXdDO2ut3YA:10 a=AYkXoqVYie-NGRFAsbO8:22
X-SECURESERVER-ACCT: doug@ewellic.org
From: "Doug Ewell" <doug@ewellic.org>
To: "'Carsten Bormann'" <cabo@tzi.org>, "'Sean Bartell'" <smbarte2@illinois.edu>
Cc: <christoph.vigano@uni-bremen.de>, "'Henk Birkholz'" <henk.birkholz@sit.fraunhofer.de>, "'Francesca Palombini'" <francesca.palombini=40ericsson.com@dmarc.ietf.org>, <cbor@ietf.org>, "'Murray S. Kucherawy'" <superuser@gmail.com>, =?utf-8?Q?'Christian_Ams=C3=BCss'?= <christian@amsuess.com>, "'Barry Leiba'" <barryleiba@computer.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com> <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com> <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org> 
In-Reply-To: 
Date: Wed, 14 Apr 2021 08:29:27 -0600
Message-ID: <000101d7313a$937e2160$ba7a6420$@ewellic.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEBA1vMKGz097JJaR0iVVtQal8dHwIFKGGgAqHA9PQA8MAZHwHad349Agap2QAB7Q+rvQJqLUFPq/Hr4lCAAAFwEA==
Content-Language: en-us
X-CMAE-Envelope: MS4xfDtUmyWi5P9DixAoXzOWhQXZn6HExT7zfzGygoMwdrc3mTBJBafj0pBOwtl+T/73Z5P6DEcaL+tfJmRmq8gESs7QiR4cY1LzyDbeixYyVDbWe7XCer96 /L72tjcfF4Dbvgjmnm7VfMEmugTprV41RtxNO1Gk9noW669D9EFbYz1DpvRfdSPdf/O2cjEgnI5kDo4usXOxckMiDe3OyKDG8lNeFY0RegAeJ+pdoWf5JHqz wqywft6UIFyDzdOAJNR+L5Ga64Th8bXLYUDqkw0FfN8eKLmAKow9CKtCKXFE8qUXAeA/z92spgiBFljRO5H7Gb7HQ+G0RZWzjxthUyYiAmeED9VdlWS1McE8 66m6MMytuvze0CozUTISUrMwaKeSSkm0Vy5cv2ZkOUz+EhaWCK2rPop12OgXy0olAh5NwwGKy1HRaG+6PFGv6Kn5wKtoA96MreLL8RJKX7AdckS26mhBkMSq WDcevs3itmFve/6A
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/mOpJbM_Rj5VDtlQFpqZZC_RR-Nw>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 14:29:39 -0000

I just wrote:

> I'd like to see separate ABNF definitions for UNICODE_SCALAR_VALUE,
> HIGH_SURROGATE, and LOW_SURROGATE, and then see 'hexchar' defined in
> terms of those. I think that would make it clearer what is going on.

Of course it can't be UNICODE_SCALAR_VALUE, but something like =
NONSURROGATE that conveys the meaning "any 4-digit hex value excluding =
surrogates."

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org




From nobody Wed Apr 14 07:54:05 2021
Return-Path: <smbarte2@illinois.edu>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2563A1133 for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=illinois.edu
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 vCWXhHVtAN0Q for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 07:53:58 -0700 (PDT)
Received: from mx0b-00007101.pphosted.com (mx0b-00007101.pphosted.com [148.163.139.28]) (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 AB6B23A1153 for <cbor@ietf.org>; Wed, 14 Apr 2021 07:53:38 -0700 (PDT)
Received: from pps.filterd (m0166259.ppops.net [127.0.0.1]) by mx0b-00007101.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 13EErJuC008292; Wed, 14 Apr 2021 14:53:30 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=illinois.edu; h=message-id : in-reply-to : references : date : from : to : cc : subject : content-type : mime-version; s=campusrelays; bh=G4BAvUGqvV3mreXEll7KvhBqwSGv6uaNU8jsRfzPrio=; b=GLgiVk7UJaX1mAJqh9tX1U6dTe1HrXQPpW3Wgw+C+bq5ieonLdpO/GGhTPzY56AuvhV7 3xWKApV2Kj1ies/OIG8qoeVLph4dhwWTml/xgsh0XkNjpSDKs5qAsuuzaS9+Q5qp3/gB ngxIlTa1971gH67+EPRPbKRh60lXe6+LB8ViRnCCyAhBLoTBVQkLW2HLVW5sa62goPn2 oypRSNLQDRMJvQoVeWuGBiHVrV5wrYgxooycG2gfO0VcpQlZWNATVXBX2iB10+0+69GJ TwPzFpbPFPfzemQjpIuKE99WdBg9wo3d2EQpKK00k2tR7a57iYIzlH/jrxPVgbeoRw6S 9g== 
Received: from nam11-dm6-obe.outbound.protection.outlook.com (mail-dm6nam11lp2173.outbound.protection.outlook.com [104.47.57.173]) by mx0b-00007101.pphosted.com with ESMTP id 37vv0bke37-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Apr 2021 14:53:29 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lgCpDUPwy5tJygsiWQ+keVd6pXMdkz3c3+F8ExntMqJQzVtgOUcylAahLR7xzd60uuZ9xFCSO4D7a0kh7xZ0cAZDfblyCe53dNFW8rwRXB9lBA5Pk7AdWqRa1heqXuFwWhpD0s4vlutMrVaOKyv4npFaYkVjrSo4hez91LZeKKQPYEaUbNN/YqrxRlgDEYUaoJloUYP0oxwau7/WPP9kvUq84LPNCUwwiiOxsSCxO6mYpwYkTX4OVcAiOhMKZqbkQAr/m2FCG89ffv1a3BmRZjjftpa8SXale3u4rFnh3PzdhfJZogKTNkUGunVtygDxssoziRae5Tx18CEN4I7Z8w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=G4BAvUGqvV3mreXEll7KvhBqwSGv6uaNU8jsRfzPrio=; b=HRjgDHiGr0GrvBbJfbk8UzZiL+9yQPiLxCdDwqGSuaN/xOF2ma4M/iEEaxeEhnxfLWzqQgc6vq1vMafTuj/9aF7cY1a7xsUIpxVbN0k/NHjoW538W6jW31ls722v3CoFMc5XGQHFJytwDm2qmmCXY2447J2qBT96bKmSCPyoBsRjSEyfDXgJzCkD9UjyyTuLG5uMZtF7+qG4ZXQNJj40t8f7wqMl7cvnQ4mSneqX32sTiPt2oauPJWqD2W/GEX50KfkNKgKUJQY8p06OTik60vzIFo/ArcfCauZmBp7WQYAxwuzOiGw0F5YyzDj35AKBptdW4MsIfEC/XB6DIHz3KQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=illinois.edu; dmarc=pass action=none header.from=illinois.edu; dkim=pass header.d=illinois.edu; arc=none
Authentication-Results: amsuess.com; dkim=none (message not signed) header.d=none;amsuess.com; dmarc=none action=none header.from=illinois.edu;
Received: from DM6PR11MB3834.namprd11.prod.outlook.com (2603:10b6:5:137::27) by DM4PR11MB5263.namprd11.prod.outlook.com (2603:10b6:5:38a::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4020.18; Wed, 14 Apr 2021 14:53:28 +0000
Received: from DM6PR11MB3834.namprd11.prod.outlook.com ([fe80::345a:a90f:6d5f:fe3e]) by DM6PR11MB3834.namprd11.prod.outlook.com ([fe80::345a:a90f:6d5f:fe3e%7]) with mapi id 15.20.4020.022; Wed, 14 Apr 2021 14:53:28 +0000
X-ME-Sender: <xms:4gF3YPdMALv6SmMjVm5Tk_KcCTKhhQl246bJXX3ivmBlva9ZPtzevA> <xme:4gF3YFPL8FFj9DoXeRMdGY8S-x2iOq-S78rhO8fwUMVqXM2kYzY1-Co_hi5fb2HAG 4q7xmLKvr0AZHrkMiM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeluddgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdfuvggr nhcuuegrrhhtvghllhdfuceoshhmsggrrhhtvgdvsehilhhlihhnohhishdrvgguuheqne cuggftrfgrthhtvghrnhepkeetgeethffftdelleethefgkefgudffgefgkeefgeelheek tdevkeeugfffjeelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepsggrrhhtvghllhdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidq leefheduvddvtddtqddvtdeileduleeikedqshhmsggrrhhtvgdvpeepihhllhhinhhoih hsrdgvughusehsvghnthdrtghomh
X-ME-Proxy: <xmx:4gF3YIh8F5wW671s465atic1KW_6xBaqUkGUELOtXfXBWst6_OimEw> <xmx:4gF3YA-iJZLPWj3hSg3VtpDzip0ymproH54wsbeoFUVjqUXcVeBRzA> <xmx:4gF3YLs-t614c7ryBu8utqlI27Pqamad0lpw3I9WSl_VNuTSOaXgxg> <xmx:5QF3YPjdBqcSXqEr3Xz67rxXJaADk5xwcLNF9kgBDuzGjYZ-Y8So3IqqwdQ>
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249
Message-Id: <0ecc0cac-e468-4d4d-94c5-2d670eed6904@www.fastmail.com>
In-Reply-To: <c46d6f4064f740eca0cf0a59abed211a@DM6PR11MB3834.namprd11.prod.outlook.com>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com> <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com> <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org> <c46d6f4064f740eca0cf0a59abed211a@DM6PR11MB3834.namprd11.prod.outlook.com>
Date: Wed, 14 Apr 2021 09:53:02 -0500
From: "Sean Bartell" <smbarte2@illinois.edu>
To: "Doug Ewell" <doug@ewellic.org>, "Carsten Bormann" <cabo@tzi.org>
Cc: "christoph.vigano@uni-bremen.de" <christoph.vigano@uni-bremen.de>, "Henk Birkholz" <henk.birkholz@sit.fraunhofer.de>, "Francesca Palombini" <francesca.palombini=40ericsson.com@dmarc.ietf.org>, "cbor@ietf.org" <cbor@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>, =?UTF-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, "Barry Leiba" <barryleiba@computer.org>
Content-Type: text/plain
X-Originating-IP: [66.111.4.228]
X-ClientProxiedBy: MN2PR06CA0010.namprd06.prod.outlook.com (2603:10b6:208:23d::15) To DM6PR11MB3834.namprd11.prod.outlook.com (2603:10b6:5:137::27)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from auth2-smtp.messagingengine.com (66.111.4.228) by MN2PR06CA0010.namprd06.prod.outlook.com (2603:10b6:208:23d::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.16 via Frontend Transport; Wed, 14 Apr 2021 14:53:27 +0000
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])	by mailauth.nyi.internal (Postfix) with ESMTP id 9D57F27C005A; Wed, 14 Apr 2021 10:53:25 -0400 (EDT)
Received: from imap10 ([10.202.2.60])  by compute6.internal (MEProxy); Wed, 14 Apr 2021 10:53:25 -0400
Received: by mailuser.nyi.internal (Postfix, from userid 501)	id C95AB4E009D;  Wed, 14 Apr 2021 10:53:22 -0400 (EDT)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4edc0f4f-2cad-4105-07ec-08d8ff551038
X-MS-TrafficTypeDiagnostic: DM4PR11MB5263:
X-Microsoft-Antispam-PRVS: <DM4PR11MB52634C3C083E1D5FAFF8D7EFF74E9@DM4PR11MB5263.namprd11.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 0cXwWIQhBxggepPomN1uKvWe4Udx9aH3eQiumTSpKyMHsP4ZQTFI9jcHt5sNodGc9FZ9khsV2OT0AMKUeUdEyk6aog09+ptP/yRLqXIqdnjJufcedaiDo41Z617u8PWamQ96nZ/bStfWd12MwSjBPO1tHdE0F4S86sdliB7nqM/HgGTsjZxv2zPY5XSVAZ5/SJM3JARFXftU0QZxVz0mYAIVKnZiOAdJV+67d9EeKPQ7jBCPQRst2sE0wgI39n1AJP7FE1niMo+Pkv5CaJtTHYfGQ4wuRAn5eBHEuIgtLQ+KWs+4bI69ku3ePSx50TAFGw9ZPK1FbvbeTas18GFZF0RXmc6jQVj/FkSwKAFRuL8e972muY2n8NnX06LIyjhEc5sJb8ztRI7iQpdsVtS8uC/4mXkI0Iyy02nWqHLEjlTX0PuaXx4Xzmkovd25nBCWwuUU2JvjFmLZYeXZRqzpy07rbzmvGMsfJ4fbFtuXNDB9hgpOjBYizIJvN9G4OjhmGuDzwwuxxyQCfVD3iJ2XwtXbatpL9F6CqMSozxfmwXFICVff3s81TM5C/1zg44eArQ8lAJxM6C/1iN14Q8Qpfb+SBZs6DL/wvWjv+By4OIaBPnrNSGLcwNtOUrI8cgu01z/JmvIoFy66v4fbDrQCt7rhypY4CXEHzP50lxQ6NjtAQQHmJAQcINSUxtvocq+uRT36uMUdWAe+itaW59M6F4J3JWs3imzOYCuEjakSjss=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR11MB3834.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(366004)(39860400002)(136003)(376002)(38350700002)(478600001)(86362001)(6266002)(4744005)(9686003)(2906002)(54906003)(6666004)(110136005)(38100700002)(4326008)(5660300002)(8936002)(186003)(26005)(66946007)(31696002)(66476007)(75432002)(31686004)(8676002)(52116002)(316002)(786003)(42186006)(66556008)(40310500001)(40720500001); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData: =?us-ascii?Q?rBbw2+p4TZ2MjlCSHlzxk+F/iHRGHpkDpDuroNHOHGCGjz8RQqL7rC8SKSyx?= =?us-ascii?Q?0DOYwmC2hZsXbRP17Ow5zrO7cPwYN4i8fRsp9YRNWzfqppY6ov1LVHORjjMs?= =?us-ascii?Q?A03/JDJepDfndTRPhzrbFcRDidjaEL1n/3Hs7NICIHRsK+YtBYg+4YZ2bB57?= =?us-ascii?Q?cYNiy/botQKKXMUqgH2BOOPIdZASWbsFyBXVa8QGnOvqjB7uw8eA8ZLQNZ/a?= =?us-ascii?Q?ViwYuf4y7p3ryOl6S04Cewye9aQXL2gwEDfZF9HvLS6/FMjx1j313R2eLdXy?= =?us-ascii?Q?DS9vpzjIXpHCUgkrM88OOhdEcwZi+++z8gVjed33sOlKwcRHdQRNelS2KAHc?= =?us-ascii?Q?02970IFRD9OkqNi04BGprlcHhaunnsNngH5+b8ZN2MfudeSrwccS1QqN4I95?= =?us-ascii?Q?xN0147XTPz77j03xzkBb6OUgiv0Ktw2hAZLLP89asGB0oUPLfgdIK1M/6As0?= =?us-ascii?Q?NMJMipkVWvT98HYgshFEHoP9kFjOhOFLVAFNH9vUvYPkc86fv6pahhnnNcBV?= =?us-ascii?Q?QmnM7vURgmyCaKSUzw9kfeLCAMIHkTV7fKOZhXkG7UoL72GpJm05Q5iXJNaZ?= =?us-ascii?Q?56qic38BgDr7nP7QsMlKGpSwMsI360JRjRrIhlnoMPDzrmPpjenxdxo3mTEc?= =?us-ascii?Q?Gyq4tscVB9/ZLMipthBR7ZarxjWIVcj2HDNlfNDVQOG5+3+OJT55C5X1LEEK?= =?us-ascii?Q?eSmwv51IHv9TWmpG/9euENQElmJuP7GsvDV/woaWEE34pH0bHEyUXlfJ/9bj?= =?us-ascii?Q?rxP6DPCmL65Raj0LkBbNZSmnpDgTeldqJcW0St9Bi3kKVQyH4TF7Oga+vXVD?= =?us-ascii?Q?LmlGd5t03beS1BMF0rZEWgmZC6d1HgYVNtvVU43CMS6rtCbzazaxG7ldqDPF?= =?us-ascii?Q?s0qPOzR0wcfRTpxxe7ntbEq6f2KBipX2RPrgg8M7qwQ5wt0WBjtOSZiQder9?= =?us-ascii?Q?3vFFuB03r9KP8oCrGAcPIih/r5viEdDUcn3wUYApguts/vm0+1dCcHFxu0Xq?= =?us-ascii?Q?Hh+MFdylLP/rIzcI6oK5qMoluaqFr6PbIp5z2++EPjdy77hYysK//L9p/bWs?= =?us-ascii?Q?OhCo4RtsmPBI7/VJWZFWm0kxoh7UYWQcZEXwegTAuGOhU7Bu00zrZT/dvqID?= =?us-ascii?Q?E9Mt/09MX9Gv6huJpC/QXiuMFkfpNXQnGYfILwaLcILrn0LoQpn/44Sc0WHy?= =?us-ascii?Q?yLKPLE78gyFoBE5rB/rvXuC7zSksQ0M9VwzoAONnHUrLuaxLZtYb8BdGsw9H?= =?us-ascii?Q?gkT92/Dt0ySm9r3kwD89NomaAFnKFnEM1aL2uL9RFrSsuiCllAi/lw4BvhzB?= =?us-ascii?Q?2vP0GJ7wl2JgINhWSkXhUmoy?=
X-OriginatorOrg: illinois.edu
X-MS-Exchange-CrossTenant-Network-Message-Id: 4edc0f4f-2cad-4105-07ec-08d8ff551038
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB3834.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Apr 2021 14:53:28.3774 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 44467e6f-462c-4ea2-823f-7800de5434e3
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 7KK7lyLq7WPPw0zQHBlMvc55Dx85yY6zfsKsvEIAnFoyz584PZdBbf4IHhM1NxSeBVxSInmIk9RIqgrGDAHDKQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR11MB5263
X-Proofpoint-ORIG-GUID: eYRimuVPX6-YtvXnM0hhrOCCwehCtl-a
X-Proofpoint-GUID: eYRimuVPX6-YtvXnM0hhrOCCwehCtl-a
X-Spam-Details: rule=cautious_plus_nq_notspam policy=cautious_plus_nq score=0 suspectscore=0 priorityscore=1501 lowpriorityscore=0 mlxlogscore=590 malwarescore=0 mlxscore=0 bulkscore=0 phishscore=0 spamscore=0 adultscore=0 impostorscore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104140102
X-Spam-OrigSender: smbarte2@illinois.edu
X-Spam-Bar: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/TwYqkEaG0sYUVhY-Bw9AC-Qiy34>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 14:54:03 -0000

On Wed, Apr 14, 2021, at 09:29, Doug Ewell wrote:
> I just wrote:
> 
> > I'd like to see separate ABNF definitions for UNICODE_SCALAR_VALUE,
> > HIGH_SURROGATE, and LOW_SURROGATE, and then see 'hexchar' defined in
> > terms of those. I think that would make it clearer what is going on.
> 
> Of course it can't be UNICODE_SCALAR_VALUE, but something like 
> NONSURROGATE that conveys the meaning "any 4-digit hex value excluding 
> surrogates."

I'd be happy with handling surrogate pairs this way; it's much clearer than putting everything in one rule. Other than that, I don't have any particular opinion about Carsten's proposals.


From nobody Wed Apr 14 09:18:34 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314C33A15D1 for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 09:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 wN4YfTt-_CxG for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 09:18:23 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D455E3A15EE for <cbor@ietf.org>; Wed, 14 Apr 2021 09:18:22 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FL71m2y65zybX; Wed, 14 Apr 2021 18:18:20 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <000101d7313a$937e2160$ba7a6420$@ewellic.org>
Date: Wed, 14 Apr 2021 18:18:19 +0200
Cc: Sean Bartell <smbarte2@illinois.edu>, christoph.vigano@uni-bremen.de, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>, cbor@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, Barry Leiba <barryleiba@computer.org>
X-Mao-Original-Outgoing-Id: 640109898.906027-501053973f087a1dfd93cd6ec236b745
Content-Transfer-Encoding: quoted-printable
Message-Id: <C81B921B-00A4-4DAB-95ED-4254DACB9366@tzi.org>
References: <20210411161045.9648FF40799@rfc-editor.org> <4986660B-EDCC-4D07-A74E-BBEBE698721D@tzi.org> <2E410DD1-D0E2-4137-B7E7-7FB18CF71971@tzi.org> <CALaySJJAzJgtQY9wuF1dgCQRfTSAz3Ofva-N-EwqcFGo_d6XEw@mail.gmail.com> <513F7F4F-E791-4B96-AF3E-42A7B1447EF7@ericsson.com> <73c7a676bea744e48390f9fdb2639843@DM6PR11MB3834.namprd11.prod.outlook.com> <5a2abb26-2a17-4b1b-b491-7bac8485e69a@www.fastmail.com> <DF1E72C2-D300-4561-A991-60D48F6EC027@tzi.org> <000101d7313a$937e2160$ba7a6420$@ewellic.org>
To: Doug Ewell <doug@ewellic.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/ljHAiw-WhNqoIKAzkjZa4WIf56Q>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 16:18:34 -0000

Nice!

hexchar =3D non-surrogate / (high-surrogate "\" %x75 low-surrogate)
non-surrogate =3D ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
                ("D" %x30-37 2HEXDIG )
high-surrogate =3D "D" ("8"/"9"/"A"/"B") 2HEXDIG
low-surrogate =3D "D" ("C"/"D"/"E"/"F") 2HEXDIG

Now in use in
https://github.com/cabo/cddlc/blob/master/lib/parser/cddl.abnf.orig

Gr=C3=BC=C3=9Fe, Carsten



> On 2021-04-14, at 16:29, Doug Ewell <doug@ewellic.org> wrote:
>=20
> I just wrote:
>=20
>> I'd like to see separate ABNF definitions for UNICODE_SCALAR_VALUE,
>> HIGH_SURROGATE, and LOW_SURROGATE, and then see 'hexchar' defined in
>> terms of those. I think that would make it clearer what is going on.
>=20
> Of course it can't be UNICODE_SCALAR_VALUE, but something like =
NONSURROGATE that conveys the meaning "any 4-digit hex value excluding =
surrogates."
>=20
> --
> Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
>=20
>=20
>=20


From nobody Wed Apr 14 09:59:43 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 075933A175D for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 09:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 L-k9BbRgyVtI for <cbor@ietfa.amsl.com>; Wed, 14 Apr 2021 09:59:37 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C5D03A1766 for <cbor@ietf.org>; Wed, 14 Apr 2021 09:59:37 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FL7xM49hpzyd0; Wed, 14 Apr 2021 18:59:35 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7D880912-A489-4534-A05E-6B8129DB3614@tzi.org>
Date: Wed, 14 Apr 2021 18:59:35 +0200
Cc: Barry Leiba <barryleiba@computer.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, smbarte2@illinois.edu, cbor@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>, =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>, christoph.vigano@uni-bremen.de, Francesca Palombini <francesca.palombini@ericsson.com>
X-Mao-Original-Outgoing-Id: 640112375.116266-73719ef51fc30f14970aef2fe3e6900c
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8572153-8BAC-4FF2-B53C-0897CDB2AC58@tzi.org>
References: <20210414001322.EE85DF40791@rfc-editor.org> <7D880912-A489-4534-A05E-6B8129DB3614@tzi.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/ez3iu80HCKAjAorOLiPt4w1g_70>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6543)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 16:59:42 -0000

> On 2021-04-14, at 15:14, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> SOON

=
https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-freezer-06.html#na=
me-clarifications

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 20 05:56:37 2021
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C0C3A2195 for <cbor@ietfa.amsl.com>; Tue, 20 Apr 2021 05:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 OYOql1rBR1W5 for <cbor@ietfa.amsl.com>; Tue, 20 Apr 2021 05:56:30 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60048.outbound.protection.outlook.com [40.107.6.48]) (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 D3F5D3A2193 for <cbor@ietf.org>; Tue, 20 Apr 2021 05:56:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MTI4vNeLjxOz3zkG0TuPyDl+Vd1OfqGSLEtCXI8ED6PfU2+NMwxI0YjFN4Ew/NkCGe6A2w21VUCPjg9Axmlg39500WWIB1elY6NRi+Ig+GIpKgNeBI6bnlVR5NHTVDl2iTF6Xn78xT2FN30Orim2O43yS7rC3m0dr/a/WEeSDGraIFH9XiP8vL0ayldMHJixwfdcWXeol/2Q1PGejI4CRwgC/4Y/OpQlN1p2hAwWtQUXhdLwddNraVTseZcik83k0EW8jmGV9HNOX+c3RvZo2lfZpgcUsZ6mZPvzjfyRNZfDnQ6wbn3HDi6+9L3SVlTlgaaxzkxAWGoP4ws/gDHkjw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5u7SIBxoR0SQ7qQEB7G6+O88ad9EwDlDWPXPwhPJxtU=; b=bTODzhrQ7sZmCiz1jBbOzsRgBzGELeKUrCDwNUROyhKNH6Uek5TzX7tOYfkKGG28x8SZ3WyRGt610RWnm47bJIsXpWr5aSXmiCShdy/yiJEmn9Z4JYdRBx3yHQK+chBey+4VHnvNmtsxxHez0Qrf9xY8LuWanR9vkk5Oz0BHmdk70jwmG2OENpWJl+3jymz+1WGcI938WHu6o5HSfug0bhosXdyqp2gV11HlFKEHWlU05V6zBRqpGf+TRXyrNS9Xq258SvVug/aeE8Mz5FrkjDygr2pDQfVsheb/7DSiYts2Wfh6uwhfPG1e4fQ54FOYmPDGO14RHyVvdt61aiEWXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5u7SIBxoR0SQ7qQEB7G6+O88ad9EwDlDWPXPwhPJxtU=; b=Utz/E2FG0HtQSjEJh3TTYgh1RenDdjY0CFg+epGmkctgeXGWwwuTPaDuHiJG5kt/vYmw4jG8Qj8CghuWdDFiSstFFv/49nHAFurZyTtpvhxcBt+ZRAj6ChxPwONQFWUym0F4S6S1k5MtdGO/BVWXTJ03Muuxc1iKmgVEH6HLG4U=
Received: from DB6PR07MB4213.eurprd07.prod.outlook.com (2603:10a6:6:49::32) by DBAPR07MB6885.eurprd07.prod.outlook.com (2603:10a6:10:198::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4065.6; Tue, 20 Apr 2021 12:56:26 +0000
Received: from DB6PR07MB4213.eurprd07.prod.outlook.com ([fe80::915f:ef9a:3028:5a63]) by DB6PR07MB4213.eurprd07.prod.outlook.com ([fe80::915f:ef9a:3028:5a63%3]) with mapi id 15.20.4065.019; Tue, 20 Apr 2021 12:56:25 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>, "cbor@ietf.org" <cbor@ietf.org>
Thread-Topic: [Cbor] OID representation (was: Re: Robert Wilton's Discuss on draft-ietf-cbor-tags-oid-06: (with DISCUSS and COMMENT))
Thread-Index: AQHXLK+zN/eW/KIUt0uDrkx0R09iTKq9kUuA
Date: Tue, 20 Apr 2021 12:56:25 +0000
Message-ID: <38A1215C-6CE1-45B5-9880-38FF8EA3DC60@ericsson.com>
References: <161788356811.31539.2139615008210880278@ietfa.amsl.com> <74E0F02D-1AAB-444B-ABCA-82EACEF27B5F@tzi.org>
In-Reply-To: <74E0F02D-1AAB-444B-ABCA-82EACEF27B5F@tzi.org>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.47.21031401
authentication-results: tzi.org; dkim=none (message not signed) header.d=none;tzi.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:1ba8:147a:eb00:2c0c:2164:d067:901e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 93419b50-aa47-4725-e84f-08d903fbb518
x-ms-traffictypediagnostic: DBAPR07MB6885:
x-microsoft-antispam-prvs: <DBAPR07MB68850AE6A064DE25EDDC438698489@DBAPR07MB6885.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IVeZeYA+wZnVvyeDBPezIRec1fPnYrBv9ql1aCzErp/sF9o0W8vhkZj4urxsTWGAFxnE35CxIga6C3hmm7U9K7NSawiw/tzl+w2WK7aeyuu7DZiwfQ3OgIhAXpu9WkubXRb0R9miwa2XA7UIH/L+wbzWQ305jh0m6KQNZtUMFhE/l2r5EW8F3InjPLSw9MTwIBy3wj9nUFYKETn0+2+VV9CTcPgnlHy1Y4NIGFe+e3GL+T7baW2vhSkCJNAvx7tB5iZKj8s9Vg/6+3efwtSCoFLVn/i8IAB4znuk27pg/M0qXbCsRbcCJ1A8DgUzXHQRwec8JGfNiAeU6l5TdVTvIT/ZtCYnDAP84kgH8T7thm7pfzR2UHrAlJk1HzBWTKwXiGn7jw7tTna2PN8hbq81vx3teEtm7GdM3z0LM1FcBE4LfRdeUV1jvphi+nas/EEqbQdkiw4hlyZhj+RlQUXogJZVnzNh0eC/Fr18BbNp3AP3qQAVMSaAsZFhPNf7UAeVNSCCUDdbc41rDQZZ6BlcVxOYnNJ+UYp6ReqFwP7kKItOV+Fa6BEqO0xeYutxcosrkiAn/77n/6f+OFzUn+5Ylok8xR0Bm+1v12iWD+zD8NKouef2qcBYZPS5MbXqlQrlxaMvE9R06xDXM8zELWmS/qqligrWDV8//ONAajRv0mLvGkQhv9oR0kr2Mw+/ZU7+rAaFN4OuEWZgQIILmKsD5NklSl4oEUwCxh3wUF1lhh8uJsjsP3UBF6TjO2uSKtba
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DB6PR07MB4213.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(376002)(366004)(346002)(396003)(39860400002)(6486002)(6506007)(966005)(186003)(110136005)(86362001)(316002)(2906002)(66476007)(6512007)(64756008)(66556008)(5660300002)(66946007)(66446008)(91956017)(8936002)(76116006)(33656002)(8676002)(478600001)(2616005)(38100700002)(83380400001)(71200400001)(44832011)(122000001)(36756003)(45980500001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?R0dpQ2hPNWx3OGV0blNadlI1T1QzcVFWcTFjUC90RGw1bHpOK3Bsa1dGNzFu?= =?utf-8?B?dU4zcmU1bDJoTmZKUlV6MmQwYWxxZHhvVHhpSXQxRDRHZmdWSGF1VnV4dUNG?= =?utf-8?B?UXBmMHp3dWJ5YzgzT0lUN3FQSTA2ZWUxeis2ZjVHeWxUMVBRd3JEcnNyMGdY?= =?utf-8?B?QUdybE04dlZpNkZ2T2tteC9kYjBxN0twSjJWTUFuK1VwZVlWdzdUN0RiRk52?= =?utf-8?B?ODBKRndreE54ZURWdTR5b1YwdEVaNHFJL0UzRjljV2pSUTE3aVFZUUFoRy8v?= =?utf-8?B?ckJFN1U5dy9wTGlOdnBDbVhselhzbGRzNGgyMmNkT2lYekErQzlEcXZtblND?= =?utf-8?B?M0dyT1JMUHVueE5LeVBIWk92THN3ZlpsRUlmN29XaDJPWUlQT21NTUZxaDBJ?= =?utf-8?B?S0s4MGg5ZkZkQW1HWXJGc2pVNURDaytZVkRoM2ltNWJON1NkdFpWcENRSFJJ?= =?utf-8?B?dnFTZkdKNnBKUWdKL3A3T3N4VjUwUTZ0OFphZWVnMkM1SnRSTHpNd3dYQ1lr?= =?utf-8?B?ak12KzZnWklUTkhjSnc5WDVjN3RHTndFdWV4bjd6ZHpXZEJuWHBBNG5DRXJC?= =?utf-8?B?NFBVZ0dITXlWOGNNdndkbVJvS3N6SVBzY3cyZmJCVnpCMzVQa01ESUhjUE5B?= =?utf-8?B?eXllY09CQUFFbFRYWVAxck9SNkdCTnEzeDdNRFp4bWt4SFpRY1ozYWFFVFdS?= =?utf-8?B?TThZb3BOeFhTQy9SYkh4R2UyR2ozOWE2UVA1TitOV0kwZ3hYeW9rQmQzMmRS?= =?utf-8?B?N3czQkVvTDJRL1piT2lqakxIUzRTdWpQWHVHd0JHYyt5RWlzVmtGclE1cEwz?= =?utf-8?B?dmhDdlo5K1FKdU5YWWQ2WEVZTDZwRlk1WVJucHpvZVBpT2pLQmpkZEt4OFZz?= =?utf-8?B?NVBHelc3REY1Nk83U2JKUHVYeFFYSWtORmdYYjlQTkFQNGtGSTA3Qk1aV3hB?= =?utf-8?B?SGhvV09FTVB1clNnSVZFN3pMdzNENWM0cnhFWlBQWXZQWk9NaWpDVHM3bUdv?= =?utf-8?B?Nm5QdUVjQTBxR0hqbk55NEE5VGtqenQveVpOTzllVTQ2VGVOUkpuRnU5S3M5?= =?utf-8?B?RXg3QlB0V2FPT3ZYQkZCcmxuWDUxd3MwWUhYL0lUYkgzczRCMzBYTlhxM2Rq?= =?utf-8?B?M2NSbWxTd2pNYlRxZFdLZW80c0JEbStoekdTdzhYaGxFbGlFU0ZQSXFrUkt4?= =?utf-8?B?OGF0U1Q5RmRXTGNtN2lkeGNnZEkxMXBQck9kNnFRb1NZTzFldWdqZVNaWTFK?= =?utf-8?B?aFBaN3Zpa2ZsSGNXSTVzZGRJNmVJN1F3VG41MGNvekxvY1lyUjQ3ZWZhUys5?= =?utf-8?B?QkJiWDhscGNqYndsREVCOC9xUWtUZFVsOVJWV1JOa0RmTTZpOVFCcFRBS3Jj?= =?utf-8?B?ZzB0ZzVURkFXOTFKOTdORG1RR0loUi96ak52NitMbWdhbzRiL3RjSzR0RXFW?= =?utf-8?B?dnh5OGt2UWRQNG9iTDM2SHduSHJlS0NUUkZ0Y21wRGR0dUxMaXNUdURDclhS?= =?utf-8?B?eWdteGhZTGdHQkNKaHdlU242SzJnYUt1YmlhOXhkdWlKbnA2SFd2UGZ5NXpS?= =?utf-8?B?VXo5eXU5YnJGWVBpZXNBcEsrNWJ3TmdoL1o1NDFIdUNQYUhwZkk3NW9lMTl3?= =?utf-8?B?aDBKQkpnbk9zN2JpQU8yeXRodk8xbjVJVkEweXE5cGJaejNFZFJvbExKQUpC?= =?utf-8?B?ZFFwOEt6d1lMTllQVkhFWXUzSlJMV2xEZEtCbGtIRmsyUXV3NENFMTZYbkpa?= =?utf-8?B?MWJIREZ2eXE1ZkdjT2VPdkdTUktxdW9rTkZGWXk5TjJwZEsxZXlDMEV5TTYz?= =?utf-8?B?TjB4aFdsNTd0czZUWE1wN1p3YzBvcWdZQS82bUg4c1YxNGNEUWRJTTB0aVlE?= =?utf-8?B?TGxyZEErVUNqY0tyenFRTWVvTDRRbjB5SWVuMnlBNWo3bHc9PQ==?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <B2F8E171B1CD3E4787131D81D3CB7E05@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB6PR07MB4213.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 93419b50-aa47-4725-e84f-08d903fbb518
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2021 12:56:25.8809 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: GXU1qK1FisKgZfWtZ1Wlk6QT25pBwWfM078+WMZAQhvrG7b1BGVlIvi6FAmFDEsivC+TE488zh1lP+dnzSks3LZbFlk7Bd4VkpepgvmMOVJMur5MrxiA6+wJtV65A+/w
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBAPR07MB6885
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/uUW8GQdbApQD3Ruu9HD7ypwgv18>
Subject: Re: [Cbor] OID representation (was: Re: Robert Wilton's Discuss on draft-ietf-cbor-tags-oid-06: (with DISCUSS and COMMENT))
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 12:56:35 -0000

SGkgYWxsLA0KDQpBbnkgb3BpbmlvbnMgb24gdGhpcz8gQ2hhaXJzLCBpdCBtaWdodCBiZSBnb29k
IHRvIGFkZCB0aGlzIHRvIHRoZSBhZ2VuZGEgdG9tb3Jyb3cuDQoNClRoYW5rcywNCkZyYW5jZXNj
YQ0KDQrvu79PbiAwOC8wNC8yMDIxLCAyMTo0NSwgIkNCT1Igb24gYmVoYWxmIG9mIENhcnN0ZW4g
Qm9ybWFubiIgPGNib3ItYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgY2Fib0B0emkub3Jn
PiB3cm90ZToNCg0KICAgIENCT1IgV0csDQoNCiAgICBpbiB0aGUgSUVTRyBwcm9jZXNzaW5nIG9m
IGRyYWZ0LWlldGYtY2Jvci10YWdzLW9pZCwgUm9iIFdpbHRvbiByYWlzZXMgc29tZSBxdWVzdGlv
bnMgdGhhdCBJIHRoaW5rIHRoZSBXRyBuZWVkcyB0byBjb25zaWRlciBiZWZvcmUgd2UgcmVwbHku
DQoNCiAgICBJ4oCZbGwgaW5jbHVkZSBzb21lIGV4Y2VycHRzIGZyb20gUm9i4oCZcyBtZXNzYWdl
IGFuZCB0cnkgdG8gdHJhbnNsYXRlIHRoaXMgaW50byBxdWVzdGlvbnMgdG8gdGhlIFdHLg0KDQog
ICAgIyMgUXVlc3Rpb24gdGhhdCBuZWVkcyB0byBiZSBkZWNpZGVkIGJ5IFdHDQoNCiAgICA+IEkg
d291bGQgbGlrZSB0byBwbGVhc2Ugc2VlIHNvbWUgbW9yZSBjbGFyaXR5IG9yIGd1aWRhbmNlIGFi
b3V0IHdoZW4gVEFHIFRCRDExMg0KICAgID4gc2hvdWxkIGJlIHVzZWQsIGdpdmVuIHRoYXQgdGhl
cmUgYXJlIHR3byBwb3NzaWJsZSBlbmNvZGluZ3Mgb2YgYWJzb2x1dGUgT0lEcw0KICAgID4gYmVs
b3cgIjEuMy42LjEuNC4xIi4NCiAgICA+IA0KICAgID4gU3BlY2lmaWNhbGx5LCB0aGUgcXVlc3Rp
b25zIHRoYXQgSSBoYXZlLCB0aGF0IHByb2JhYmx5IG5lZWQgdG8gYmUgY2xhcmlmaWVkIGFyZToN
CiAgICA+IC0gaXMgYSBDQk9SIGVuY29kZXIgYWxsb3dlZCB0byBvcHRpbWl6ZSBhIFRCRDExMCB0
YWcgaW50byBhIFRCRDExMiB0YWc/DQogICAgPiAtIFNob3VsZCBDQk9SIGRlY29kZXIgY2xpZW50
cyBhbHdheXMgZXhwZWN0IHRvIGJlIGFibGUgdG8gaGFuZGxlIGJvdGggVEJEMTEwDQogICAgPiBh
bmQgVEJEMTEyIHRhZ3M/IC0gT3IsIGl0IHRoZSBkZWNpc2lvbiBvdmVyIHdoZXRoZXIgdG8gdXNl
IFRCRDExMCBvciBUQkQxMTINCiAgICA+IGRvd24gdG8gdGhlIGFwcGxpY2F0aW9uIGFuZCB0aGUg
YXBwbGljYXRpb24gbmVlZHMgdG8gYWdyZWUgd2hpY2ggaXMgdXNlLg0KDQogICAgVGhpcyBpcyBp
bmRlZWQgYSBnb29kIHF1ZXN0aW9uIChhYm91dCBUQkQxMTEgdnMuIFRCRDExMiwgYWN0dWFsbHkp
Lg0KICAgIFRoaXMgY2FuIGJlIHNlZW4gYXMgcmVsYXRlZCB0byBpc3N1ZXMgYWJvdXQgcHJlZmVy
cmVkIHJlcHJlc2VudGF0aW9ucywgb3IgYWJvdXQgbWluaW1pemluZyBpbnRlcm9wZXJhYmlsaXR5
IHByb2JsZW1zIGJ5IG5haWxpbmcgZG93biBleGFjdGx5IG9uZSBhbGxvd2VkIHJlcHJlc2VudGF0
aW9uLg0KDQogICAgU28gd2hhdCB3ZSBjb3VsZCBwcm9wb3NlIGFzIGEgV0cgaXM6DQoNCiAgICAo
MSkgTm90IGVzdGFibGlzaGluZyBhbnkgc3Ryb25nZXIgY29ubmVjdGlvbiBiZXR3ZWVuIFRCRDEx
MSBhbmQgVEJEMTEyLCBpLmUuIHN0YXR1cyBxdW8uDQogICAgKDIpIERlY2xhcmluZyBUQkQxMTIg
YXMgdGhlIHByZWZlcnJlZCBlbmNvZGluZyBvZiBhbiBhYnNvbHV0ZSBPSUQgdGhhdCBzdGFydHMg
d2l0aCAxLjMuNi4xLjQuMSAoMHgyYjA2MDEwNDAxKSwgYnV0IHN0aWxsIGFsbG93aW5nIHRoZSB1
c2Ugb2YgVEJEMTExIGFzIG5vbi1wcmVmZXJyZWQuICAgVGhpcyB3b3VsZCBtZWFuIGEgcmVxdWly
ZW1lbnQgb24gZGVjb2RlcnMgaW1wbGVtZW50aW5nIFRCRDExMSB0byBhbHNvIGltcGxlbWVudCBU
QkQxMTIuDQogICAgKDMpIE91dGxhd2luZyBhbnkgVEJEMTExIHN0YXJ0aW5nIHdpdGggKDB4MmIw
NjAxMDQwMSkgYW5kIHJlcXVpcmluZyB0aGUgdXNlIG9mIFRCRDExMiBpbiBhbGwgc3VjaCBjYXNl
cy4gIFRoaXMgd291bGQgbWVhbiBhIHJlcXVpcmVtZW50IG9uIGJvdGggZW5jb2RlcnMgYW5kIGRl
Y29kZXJzLiAgSXQgd291bGQgYWxzbyBtZWFuIGEgc2xpZ2h0IGNvbXBsaWNhdGlvbiBpbiB0YWcg
ZmFjdG9yaW5nOiByZXBsYWNlIGFsbCBuYWtlZCBieXRlIHN0cmluZ3MgdGhhdCBzdGFydCB3aXRo
IGjigJkyYjA2MDEwNDAx4oCZIGJ5IFRCRDExMihyZXN0KSAoc2F2aW5nIHRocmVlIGJ5dGVzKSwg
dW5sZXNzICphbGwqIHN1Y2ggYnl0ZSBzdHJpbmdzIHN0YXJ0IHdpdGggaOKAmTJiMDYwMTA0MDHi
gJksIGluIHdoaWNoIGNhc2UgdGhlc2UgcHJlZml4ZXMgd291bGQgYWxsIGJlIHJlbW92ZWQgYW5k
IGFuIG91dGVyIHRhZyBvZiBUQkQxMTIgdXNlZC4NCg0KICAgICgyYSkgd291bGQgYmUgKDIpIHdp
dGggYSBkZXRlcm1pbmlzdGljIGVuY29kaW5nIHJlcXVpcmVtZW50IHRvIHVzZSB0aGUgc2hvcnRl
c3QgZm9ybSAoaS5lLiwgKDMpIGluIGRldGVybWluaXN0aWMgZW5jb2Rpbmcgb25seSkuDQoNCiAg
ICAjIyBPdGhlciByZXNwb25zZXMsIHRvIGJlIHZldHRlZCBieSB0aGUgV0cNCg0KICAgID4gSSBm
b3VuZCB0aGlzIGRvY3VtZW50IHRvIGJlIGludGVyZXN0aW5nIGJlY2F1c2UgSSBrbmV3IGZyb20g
dGhlIHRpdGxlIHRoYXQgaXQNCiAgICA+IHdhcyBnb2luZyB0byBvbmx5IGJlIDQgcGFnZXMgbG9u
ZyBhbmQgc2F5IHRoYXQgT0lEcyBhcmUgb2J2aW91c2x5IGVuY29kZWQgYXMgYQ0KICAgID4gdGFn
Z2VkIGFycmF5LCBoZW5jZSBJIHdhcyBzdXJwcmlzZWQgdG8gc2VlIHRoYXQgd2FzIG5vdCB0aGUg
c29sdXRpb24gYW5kIGl0DQogICAgPiB1c2VzIEJFUiBlbmNvZGVkIE9JRHMgaW5zdGVhZC4NCiAg
ICA+IA0KICAgID4gVGhlIGRvY3VtZW50IGV4cGxhaW5zLCBhbmQgSSB0aGluayB0aGF0IEkgdW5k
ZXJzdGFuZCB3aHkgdGhpcyBoYXMgYmVlbiBkb25lLA0KICAgID4gYnV0IEkgcXVlc3Rpb24gd2hl
dGhlciB0aGUgdGl0bGUgb2YgdGhlIGRvY3VtZW50IGFuZCBuYW1lIG9mIHRoZSB0YWdzIGlzIHJp
Z2h0Lg0KICAgID4gSXMgaXQgcmVhbGx5IGEgQ0JPUiByZXByZXNlbnRhdGlvbiBvZiBPSURzLCBv
ciBpcyBpdCBhY3R1YWxseSBhIENCT1INCiAgICA+IHJlcHJlc2VudGF0aW9uIG9mIEJFUiBlbmNv
ZGVkIE9JRHM/ICANCg0KICAgIFRoZSBmaXJzdCwgdXNpbmcgdGhlIHRlY2huaWNhbCBhcHByb2Fj
aCBuYW1lZCBpbiB0aGUgc2Vjb25kLg0KDQogICAgPiBJLmUuLCBpdCBpcyBwbGF1c2libGUgdGhh
dCB0aGVyZSB3b3VsZA0KICAgID4gZXZlciBiZSBhIHJlcXVpcmVtZW50IGZvciBub24gQkVSIGVu
Y29kZWQgT0lEcy4gIEUuZy4sIEknbSBub3QgYW4gQVNOLjEgZXhwZXJ0LA0KICAgID4gYnV0IHNh
eSBpZiBzb21ld2hhdCB3YW50ZWQgdG8gZG8gYSBDQk9SIGVuY29kaW5nIG9mIEFTTi4xLCB0aGVu
IGl0IGlzIG5vdA0KICAgID4gb2J2aW91cyB0byBtZSB0aGF0IHRoZXkgd291bGQgdXNlIGEgQkVS
IGVuY29kaW5nIGZvciBPSURzLiAgDQoNCiAgICBPbmUgZXhhbXBsZSBmb3IgYSBDQk9SIGVuY29k
aW5nIG9mIHNvbWV0aGluZyB0aGF0IHByZXZpb3VzbHkgaGFzIGJlZW4gZW5jb2RlZCBpbiBBU04u
MSBpcyBkcmFmdC1tYXR0c3Nvbi1jb3NlLWNib3ItY2VydC1jb21wcmVzcywgd2hpY2ggbm9ybWF0
aXZlbHkgcmVmZXJlbmNlcyB0aGUgdGFncy1vaWQgc3BlYy4gIFRoZSBjZXJ0aWZpY2F0ZSBzcGVj
IGFjdHVhbGx5IGdvZXMgYWhlYWQgYW5kIHJlZ2lzdGVycyB0cmFuc2xhdGlvbiB0YWJsZXMgYmV0
d2VlbiBsaWtlbHkgT0lEcyBhbmQgc21hbGwgaW50ZWdlcnMuICBCdXQgaWYgdGhlIGZ1bGwgcmFu
Z2Ugb2YgT0lEcyBpcyBuZWVkZWQsIHRoZSBieXRlIHN0cmluZyBkZXJpdmVkIGZyb20gdGhlIEJF
UiBjb250ZW50IGluZGVlZCBpcyB0aGUgcmVwcmVzZW50YXRpb24gY2hvc2VuLiAgKEFzIHRoZSBD
NTA5IGNlcnRpZmljYXRlcyBhcmUgc2NoZW1hLWRyaXZlbiwgdGhleSBkbyBub3QgbmVlZCB0aGUg
YWN0dWFsIHRhZ3MgZGVmaW5lZCBoZXJlLikNCg0KICAgID4gSGVuY2UgdGhlDQogICAgPiBzdWdn
ZXN0aW9uIGlzIHRvIG1ha2UgdGhlIHRpdGxlLCBhYnN0cmFjdCwgYW5kIG5hbWUgb2YgdGhlIHRh
Z3MgY2xlYXIgdGhhdCBpdA0KICAgID4gaXMgYWJvdXQgdGhlIENCT1IgZW5jb2Rpbmcgb3IgQkVS
IGVuY29kZWQgT0lEcy4NCg0KICAgIFRoZSBzcGVjaWZpY2F0aW9uIHByb3Bvc2VzIHRvIHVzZSBC
RVIgaW4gYSBudW1iZXIgb2YgdGFncyBmb3IgYmluYXJ5IGVuY29kaW5nIG9mIE9JRHMuDQogICAg
VGhlIEJFUm5lc3MgaXMgbm90IGEgZmVhdHVyZSB0aGF0IHRoZSBPSURzIGFscmVhZHkgbmVlZCB0
byBoYXZlIGJlZm9yZSB0aGVzZSB0YWdzIGFwcGx5Lg0KICAgIFNvIGEgdGl0bGUgIkNCT1IgZW5j
b2Rpbmcgb2YgQkVSIGVuY29kZWQgT0lEc+KAnSAod2hpY2ggaXMgd2hhdCBJIHRoaW5rIFJvYiB3
YW50ZWQgdG8gc2F5KSB3b3VsZCBiZSBhIHJlc3RyaWN0aW9uIGJleW9uZCB3aGF0IHRoaXMgc3Bl
YyBpcyBhYm91dC4NCg0KICAgICMjIEFuc3dlcnMgdGhhdCBwcm9iYWJseSBkb27igJl0IG5lZWQg
V0cgaW5wdXQNCg0KICAgID4gSW4gdGhlIGludHJvZHVjdGlvbjoNCiAgICA+ICAgU2luY2UgdGhl
IHNlbWFudGljcyBvZiBhYnNvbHV0ZSBhbmQgcmVsYXRpdmUgb2JqZWN0IGlkZW50aWZpZXJzDQog
ICAgPiAgIGRpZmZlciwgdGhpcyBzcGVjaWZpY2F0aW9uIGRlZmluZXMgdHdvIHRhZ3MsIGNvbGxl
Y3RpdmVseSBjYWxsZWQgdGhlDQogICAgPiAgICJPSUQgdGFncyIgaGVyZToNCiAgICA+IA0KICAg
ID4gSSBwcmVzdW1lIHRoYXQgdGhpcyBzaG91bGQgYmUgdGhyZWUgdGFncz8NCg0KICAgIChGaXhl
ZCBieSBCZW7igJlzIFBSLCBodHRwczovL3Byb3RlY3QyLmZpcmVleWUuY29tL3YxL3VybD9rPWJh
NmZjODUwLWU1ZjRmMTUwLWJhNmY4OGNiLTg2ZmM2ODEyYzM2MS0xM2E3ZGY0NzI4NjBmZGUxJnE9
MSZlPTBlN2ExNTlmLWU4NDgtNDg2OC1iYTgzLTc3YmQxNWJkNzEwOSZ1PWh0dHBzJTNBJTJGJTJG
Z2l0aHViLmNvbSUyRmNib3Itd2clMkZjYm9yLW9pZCUyRnB1bGwlMkY5IC4pDQoNCiAgICA+IElu
IHNlY3Rpb24gNC4xLiAgVGFnIEZhY3RvcmluZyBFeGFtcGxlOiBYLjUwMCBEaXN0aW5ndWlzaGVk
IE5hbWU6DQogICAgPiANCiAgICA+IFRoZSBkaWFncmFtIHVzZXMgYSBtaXggb2Ygc2luZ2xlIGxl
dHRlcnMgKGUuZy4gYyBmb3IgY291bnRyeSksIGFuZCBhIGZ1bGwgbmFtZQ0KICAgID4gInN0cmVl
dCIuICBJcyB0aGlzIGhvdyB0aGUgWC41MDAgYXR0cmlidXRlcyBhcmUgZGVmaW5lZD8gIA0KDQog
ICAgVGhpcyB1c2VzIHRoZSBuYW1pbmcgZGVmaW5lZCBlLmcuIGluIFJGQyA0NTE5LCBzZWN0aW9u
IDIuMiBhbmQgc2VjdGlvbiAyLjM0LCB3aGljaCBoYXMgYmVlbiBkZXJpdmVkIGZyb20gWC41MjAg
YW5kIGlzIHF1aXRlIHViaXF1aXRvdXMsIGdvaW5nIGJhY2sgdG8gVGFibGUgMSBvZiBSRkMgMTc3
OS4NCg0KICAgID4gICAgVGhlIGNvdW50cnkgYW5kIHN0cmVldCBSRE5zIGFyZSBzaW5nbGUtdmFs
dWVkLiBUaGUgc2Vjb25kIGFuZCBmb3VydGggUkROcw0KICAgID4gICAgYXJlIG11bHRpLXZhbHVl
ZC4NCiAgICA+IA0KICAgID4gUGVyaGFwczogICJUaGUgY291bnRyeSAoZmlyc3QpIGFuZCBzdHJl
ZXQgKHRoaXJkKSBSRE5zIGFyZSBzaW5nbGUtdmFsdWVkLiBUaGUNCiAgICA+IHNlY29uZCBhbmQg
Zm91cnRoIFJETnMgYXJlIG11bHRpLXZhbHVlZC4iDQoNCiAgICBOb3cgaW4gaHR0cHM6Ly9wcm90
ZWN0Mi5maXJlZXllLmNvbS92MS91cmw/az0wNjhiMDMwZi01OTEwM2EwZi0wNjhiNDM5NC04NmZj
NjgxMmMzNjEtMGI5YWY5NGI4Nzc2ZjVjZiZxPTEmZT0wZTdhMTU5Zi1lODQ4LTQ4NjgtYmE4My03
N2JkMTViZDcxMDkmdT1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20lMkZjYm9yLXdnJTJGY2Jvci1v
aWQlMkZjb21taXQlMkYzZDBmZDhiIC4NCg0KICAgID4gICAgaCc1NTA0MDcnOiAiTG9zIEFuZ2Vs
ZXMiLCBoJzU1MDQwOCc6ICJDQSIsDQogICAgPiANCiAgICA+IEkgdGhpbmsgdGhhdCB0aGUgZXhh
bXBsZSB3b3VsZCBiZSBtb3JlIGNsZWFyIGJ5IHNwbGl0dGluZyB0aGUgY2l0eSBhbmQgY291bnR5
DQogICAgPiBvbnRvIHNlcGFyYXRlIGxpbmVzLg0KDQogICAgTm93IGluIGh0dHBzOi8vcHJvdGVj
dDIuZmlyZWV5ZS5jb20vdjEvdXJsP2s9MTI1NmQyMzUtNGRjZGViMzUtMTI1NjkyYWUtODZmYzY4
MTJjMzYxLWM2OWZiODQzMjZjNTI2YzImcT0xJmU9MGU3YTE1OWYtZTg0OC00ODY4LWJhODMtNzdi
ZDE1YmQ3MTA5JnU9aHR0cHMlM0ElMkYlMkZnaXRodWIuY29tJTJGY2Jvci13ZyUyRmNib3Itb2lk
JTJGY29tbWl0JTJGM2QwZmQ4YiAuDQoNCiAgICA+IEZpbmFsbHksIHRoZSBkb2N1bWVudCBjb250
YWlucyB0aGVzZSB0d28gc2VudGVuY2VzIHRoYXQgc2VlbSB0byBzb21ld2hhdA0KICAgID4gY29u
ZmxpY3Qgd2l0aCBlYWNoIG90aGVyOg0KICAgID4gDQogICAgPiAiV2hpbGUgdGhlc2Ugc2VxdWVu
Y2VzIGNhbiBlYXNpbHkgYmUgcmVwcmVzZW50ZWQgaW4gQ0JPUiBhcnJheXMgb2YgdW5zaWduZWQN
CiAgICA+IGludGVnZXJzLCBhIG1vcmUgY29tcGFjdCByZXByZXNlbnRhdGlvbiBjYW4gb2Z0ZW4g
YmUgYWNoaWV2ZWQgYnkgYWRvcHRpbmcgdGhlDQogICAgPiB3aWRlbHkgdXNlZCByZXByZXNlbnRh
dGlvbiBvZiBvYmplY3QgaWRlbnRpZmllcnMgZGVmaW5lZCBpbiBCRVI7IHRoaXMNCiAgICA+IHJl
cHJlc2VudGF0aW9uIG1heSBhbHNvIGJlIG1vcmUgYW1lbmFibGUgdG8gcHJvY2Vzc2luZyBieSBv
dGhlciBzb2Z0d2FyZSB0aGF0DQogICAgPiBtYWtlcyB1c2Ugb2Ygb2JqZWN0IGlkZW50aWZpZXJz
LiINCiAgICA+IA0KICAgID4gY29tcGFyZWQgdG86DQogICAgPiANCiAgICA+ICJTdGF5aW5nIGNs
b3NlIHRvIHRoZSB3YXkgb2JqZWN0IGlkZW50aWZpZXJzIGFyZSBlbmNvZGVkIGluIEFTTi4xIEJF
UiBtYWtlcw0KICAgID4gYmFjay1hbmQtZm9ydGggdHJhbnNsYXRpb24gZWFzeTsgb3RoZXJ3aXNl
IHdlIHdvdWxkIGNob29zZSBhIG1vcmUgZWZmaWNpZW50DQogICAgPiBlbmNvZGluZy4iDQoNCg0K
ICAgIFdoaWxlIHRoZSBCRVIgZm9ybSBpcyByZWFzb25hYmx5IGVmZmljaWVudCwgYSBtb3JlIGVm
ZmljaWVudCByZXByZXNlbnRhdGlvbiBvZiBzZXF1ZW5jZXMgb2YgdW5zaWduZWQgaW50ZWdlcnMg
dGhhdCByb3VnaGx5IGZvbGxvdyBaaXBm4oCZcyBsYXcgaW4gZGlzdHJpYnV0aW9uIGhhcyBiZWVu
IGRlc2NyaWJlZCBpbiAgPGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvY2Jv
ci85b3dSeU9jWGRzSzdPb2MxUzNEOS1BSW1EZFU+LCB3aGljaCB3b3VsZCBmb3IgaW5zdGFuY2Ug
cmVwcmVzZW50IDEuMy42LjEuNC4xIGFzIDB4MTM2MTQxIGFuZCBkb2VzIG5vdCBuZWVkIGEgc3Bl
Y2lhbCBjYXNlIHRvIG1ha2UgYWJzb2x1dGUgT0lEcyBlZmZpY2llbnQuDQoNCiAgICBUaGUgV0cg
aW5zdGVhZCBkZWNpZGVkIHRvIGZvbGxvdyB0aGUgZXhpc3RpbmcgQkVSIHJlcHJlc2VudGF0aW9u
IGJlY2F1c2UgaXQgaXMgc28gd2lkZWx5IGltcGxlbWVudGVkIGFuZCBpcyBjb21wYXRpYmxlIHdp
dGggU0ROVnMsIHdoaWNoIGFyZSB1c2VkIGluIGFkZGl0aW9uYWwgYXBwbGljYXRpb25zIGFuZCBv
ZnRlbiBoYXZlIGdvb2QgcGxhdGZvcm0gc3VwcG9ydCAoZS5nLiwgUnVieSBwYWNrL3VucGFjayji
gJx3KuKAnSkpLg0KICAgIEZvciBPSUQtc3R5bGUgYXBwbGljYXRpb25zLCBCRVIgY29udGVudCBp
cyBvZnRlbiBzdGlsbCBtb3JlIGNvbXBhY3QgdGhhbiBhIENCT1IgYXJyYXkgb2YgdW5zaWduZWQg
aW50ZWdlcnMuDQoNCiAgICBUYWdnZWQgKGhvbW9nZW5lb3VzKSBhcnJheXMgb2YgYXJjcyBkb27i
gJl0IGhlbHAgYXMgdGhlIE9JRCBhcmNzIHZhcnkgd2lkZWx5IGluIHRoZWlyIHJhbmdlOyBlLmcu
LCB0aGUgY29tbW9uIE9JRCAxLjIuODQwLjExMzU0OS4xLjEuMSAoKiwgMis5IGJ5dGVzIGluIEJF
Uikgd291bGQgbmVlZCB0byBiZSBhbiBhcnJheSBvZiBzZXZlbiAzMi1iaXQgaW50ZWdlcnMgKDJ0
YWcrMmhlYWQrMjggYnl0ZXMpIGluc3RlYWQgb2YgYSBiYXNpYyBDQk9SIGFycmF5IG9mIHVuc2ln
bmVkIGludGVnZXJzIG9mIDE0IGJ5dGVzLg0KDQogICAgSW4gZ2VuZXJhbCwgSSBkb27igJl0IHRo
aW5rIHdlIG5lZWQgdG8gZGlzY3VzcyBhbiBleHRlbnNpdmUgc2V0IG9mIGFsdGVybmF0aXZlIGFw
cHJvYWNoZXMgKHBhdGhzIG5vdCB0YWtlbikgaW4gdGhpcyBzcGVjaWZpY2F0aW9uLg0KDQogICAg
R3LDvMOfZSwgQ2Fyc3Rlbg0KDQogICAgKCopIHtpc28oMSkgbWVtYmVyLWJvZHkoMikgdXMoODQw
KSByc2Fkc2koMTEzNTQ5KSBwa2NzKDEpIHBrY3MtMSgxKSByc2FFbmNyeXB0aW9uKDEpfQ0KDQog
ICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBD
Qk9SIG1haWxpbmcgbGlzdA0KICAgIENCT1JAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Nib3INCg0K


From nobody Tue Apr 20 09:03:31 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F7C3A294A for <cbor@ietfa.amsl.com>; Tue, 20 Apr 2021 09:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Ovayc8gH6aW3 for <cbor@ietfa.amsl.com>; Tue, 20 Apr 2021 09:03:25 -0700 (PDT)
Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235F53A2948 for <cbor@ietf.org>; Tue, 20 Apr 2021 09:03:25 -0700 (PDT)
Received: by mail-lf1-f43.google.com with SMTP id x20so31990806lfu.6 for <cbor@ietf.org>; Tue, 20 Apr 2021 09:03:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IdynlN2ix2DZfcYrY4vknDMgvEbb0Nw0DrAwU91RsRs=; b=QM+gjAP7K1+GsIdMTIrs7Kgel3HwPzPs6PZBennxkV55HhI2zPfOvDqoZOa1Zqilmm CHHFPC9IJK7hJVPHDzLHb4j1IhnibXkw/x75MRJhilR1b1q98M9FnKj47IaM4j+P1Ogo qMRz+QtoJuTaaOGlOmukADRe6LDpYndF070JEItXcrfR6iPxFTWnUrNqBXWG516nND09 mWhZY0V2qK/SeuWRV+/8lA13EI3G2VOgph+juR7i4hbwxnQXgciNG+87+BDxAL2Fhz9/ GniGVh6IhvWAU0FljZcOzrtGnbJXrQVWcKIBPIeOqpxL/XR/6UR76+PQ2WKRvWylJdoe wDFQ==
X-Gm-Message-State: AOAM531FLZTOkm2+d1KfJgRTYey+7XkImxvYqx0GpkxYhBbDCqiSqNFB 2s3T1E2vM9lwHJh1uLRevS6ktkLRWlcQwehRNwklukx/TVxKpw==
X-Google-Smtp-Source: ABdhPJxeG9oZ3VV7eNgpDv9uemiLm3tRTSfffM5GctGCqRtZqJX5GL1P/uDwpu3XD0Mhz2GWFlXvUPHRSqFqcbUmC50=
X-Received: by 2002:ac2:532e:: with SMTP id f14mr10509518lfh.292.1618934602745;  Tue, 20 Apr 2021 09:03:22 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Apr 2021 12:03:11 -0400
Message-ID: <CALaySJK+ciZRDrtyYb5PSfcG1s=uzEAXkAvdEPpnMaFUwMEb7A@mail.gmail.com>
To: cbor@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Oa21-DViWEmDKFm_Y9M6Yu0XwCE>
Subject: [Cbor] Reminder: bi-weekly CBOR conference call on 21 April
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 16:03:30 -0000

Hi, all,

We'll have our regular bi-weekly CBOR conference call on Wednesday, 21
April, at 1600 UTC.  Various pointers are here:
https://datatracker.ietf.org/meeting/interim-2021-cbor-07/session/cbor

In particular, see the agenda here:
https://codimd.ietf.org/notes-ietf-interim-2021-cbor-07-cbor?view

Meeting link: https://ietf.webex.com/ietf/j.php?MTID=m3ed3d0309a5f216c8a4d8463130b07cb
Meeting number: 178 745 7694
Password: VDkAMXjG443

-- 
Barry


From nobody Wed Apr 21 05:00:50 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5CE93A22F3 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 05:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 kp7qIPrKAP73 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 05:00:44 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62D0F3A22D3 for <cbor@ietf.org>; Wed, 21 Apr 2021 05:00:44 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FQJzF22Hgz14Nd; Wed, 21 Apr 2021 14:00:41 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CALaySJK+ciZRDrtyYb5PSfcG1s=uzEAXkAvdEPpnMaFUwMEb7A@mail.gmail.com>
Date: Wed, 21 Apr 2021 14:00:40 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 640699240.86577-72034df3f0fc9e6b75fc18bd5b537674
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BBC74D5-C39B-4FAF-A3C5-43B20430F7D2@tzi.org>
References: <CALaySJK+ciZRDrtyYb5PSfcG1s=uzEAXkAvdEPpnMaFUwMEb7A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/lJzldJfScL2VziMImWnGMAypDUE>
Subject: Re: [Cbor] Reminder: bi-weekly CBOR conference call on 21 April
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 12:00:49 -0000

Hi Barry,

On 2021-04-20, at 18:03, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> In particular, see the agenda here:
> https://codimd.ietf.org/notes-ietf-interim-2021-cbor-07-cbor?view

I think we want to discuss the errata reports 6527 and 6543.
I have written text for those in=20

=
https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-freezer-07.html#na=
me-clarifications

(Submitted a small editorial update today on the ABNF.)

We should check
* that we agree on the resolutions proposed;
* agree whether and how to handle this in the errata reporting process =
and/or somewhere else.

If the =E2=80=9Cclarifications=E2=80=9D part of the freezer document =
starts to grow, this might take up a role similar to that of =
draft-ietf-rohc-rtp-impl-guide which ultimately became RFC 4815 [1] =
(except that we probably want to rev 8610 instead).

Gr=C3=BC=C3=9Fe, Carsten

[1]: https://datatracker.ietf.org/doc/rfc4815/


From nobody Wed Apr 21 05:48:49 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC993A266E for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 05:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 NSWsZU4HsdYj for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 05:48:42 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDFC43A266D for <cbor@ietf.org>; Wed, 21 Apr 2021 05:48:42 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FQL2c2x87z14gg; Wed, 21 Apr 2021 14:48:40 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CALaySJK+ciZRDrtyYb5PSfcG1s=uzEAXkAvdEPpnMaFUwMEb7A@mail.gmail.com>
Date: Wed, 21 Apr 2021 14:48:39 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 640702119.873727-e5faadef84491120c27fcdae28711431
Content-Transfer-Encoding: quoted-printable
Message-Id: <64E90866-6888-4AA9-98C3-9665E94D2FA0@tzi.org>
References: <CALaySJK+ciZRDrtyYb5PSfcG1s=uzEAXkAvdEPpnMaFUwMEb7A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/qJYOxRoyrIisDfVU6T8o3PTv6yw>
Subject: Re: [Cbor] Reminder: bi-weekly CBOR conference call on 21 April
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 12:48:47 -0000

On 2021-04-20, at 18:03, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> In particular, see the agenda here:
> https://codimd.ietf.org/notes-ietf-interim-2021-cbor-07-cbor?view

The other item of unfinished business we can close today may be the CBOR =
tags for alternatives/unions.
=
https://docs.google.com/document/d/16aiDEBhJj3kipj_7PVppEhxAr5E6QhQreN61eC=
xvBjU/edit

At the last meeting, I was tasked with asking the authors about the =
relationship to Optional data structures (Maybe etc.).
The authors answered that they see this as a separate item that is best =
handled separately, so that the currently discussed set of tags can be =
cleanly focused on the specific use case.
(I forget to ask whether I can forward the reply to this list, hence my =
paraphrasing.)
I tend to agree with this position.

Unless there is some additional input today, I think that the designated =
expert for cbor-tags (yours truly) can approve this request.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Apr 21 07:41:28 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE903A2A7A; Wed, 21 Apr 2021 07:41:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: cbor@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: cbor@ietf.org
Message-ID: <161901608279.29074.10665077579538802999@ietfa.amsl.com>
Date: Wed, 21 Apr 2021 07:41:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/i4P_Eghz_z_SDTWnkvusXVMV-zo>
Subject: [Cbor] I-D Action: draft-ietf-cbor-file-magic-01.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 14:41:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Concise Binary Object Representation Maintenance and Extensions WG of the IETF.

        Title           : On storing CBOR encoded items on stable storage
        Author          : Michael Richardson
	Filename        : draft-ietf-cbor-file-magic-01.txt
	Pages           : 8
	Date            : 2021-04-21

Abstract:
   This document proposes an on-disk format for CBOR objects that is
   friendly to common on-disk recognition systems like the Unix file(1)
   command.

   This document is being discussed at: https://github.com/cbor-wg/cbor-
   magic-number


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-cbor-file-magic-01.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cbor-file-magic-01


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Apr 21 07:43:03 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105593A2A68 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 07:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 xqsPFH6iVjGt for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 07:42:57 -0700 (PDT)
Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F65A3A2A74 for <cbor@ietf.org>; Wed, 21 Apr 2021 07:42:45 -0700 (PDT)
Received: by mail-lf1-f50.google.com with SMTP id t14so10092917lfe.1 for <cbor@ietf.org>; Wed, 21 Apr 2021 07:42:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LYnoQyDZuB10CM3kqwBpUuLU6UJzjJWxHVCcQWcgyGY=; b=TDGCzVjdfhYwqnCiXHE1N46O3PSnFnMIn8nxGcMuza6xrZnGRgUKzeZUz8tOX0JI/O 3lnexzPAGoxdiom7ApmEqZabeAZVXpkK9CLow92xE2P3ydpw0IEdKy1J7jwGgul4sfAa /og8/G5KlyWhIMDWMzGSOLo+/DLe5EktgZOkLfx/naQ6SK06SgS/o6QeYuvndPwJ/Z+L a137o8KGoFxVhVfqmAlV6NpkS1L9TcuY5DSwjzZ9j/sq4tCkQQCHlSG5iB7BkGgGcEsH qCHEnfe1cBuPYzaxbHfn9syGDy0VR6WbnPG25u0M0LyhXEmNyfZIu4C9OiUtLe35KLRd kTrA==
X-Gm-Message-State: AOAM531F4h7grtr4kgRmQI3NRz0UQ43ttV3BVE/HA79tglCa4lV4m5WN mSZ9sAZcIDCenvXGZzlLTgto/RRh2+DsZD2+gu6lZQNIcxexeQ==
X-Google-Smtp-Source: ABdhPJwv7oJmmaGyleSZw9HNmsWQqyaX1YSWCbAVxIyJ9VO4N3DiAmsrO7r1tOXOrjfBhSbbQL5/lNOxOWzW1e9rPGw=
X-Received: by 2002:ac2:4d10:: with SMTP id r16mr19146156lfi.643.1619016163367;  Wed, 21 Apr 2021 07:42:43 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 21 Apr 2021 10:42:32 -0400
Message-ID: <CALaySJ+WVnnoSO4JuCb9OMi9kguXLjHZONKMXTt39sbrmGAVGA@mail.gmail.com>
To: cbor@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/sHBuA_5H5roXLpyGUd9ArhgaLzk>
Subject: [Cbor] Notes from bi-weekly CBOR conference call on 21 April
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 14:43:02 -0000

Notes from today's call are here:
https://codimd.ietf.org/notes-ietf-interim-2021-cbor-07-cbor?view

Thanks to those who attended, and to Christian for taking the notes.
The next conference call is on 5 May.  Meanwhile, everyone please
review the IESG comments on cbor-tags-oid, discuss on the list, and
let's get that document finished up.

Barry


From nobody Wed Apr 21 07:44:38 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208953A2AD0 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 07:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 cQiVBDw2HVGp for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 07:44:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B7423A2A99 for <cbor@ietf.org>; Wed, 21 Apr 2021 07:44:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8753739043 for <cbor@ietf.org>; Wed, 21 Apr 2021 10:52:06 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qFVsD21QeDU6 for <cbor@ietf.org>; Wed, 21 Apr 2021 10:52:02 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DB84338FD0 for <cbor@ietf.org>; Wed, 21 Apr 2021 10:52:02 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B2FB6653 for <cbor@ietf.org>; Wed, 21 Apr 2021 10:44:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cbor@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 21 Apr 2021 10:44:20 -0400
Message-ID: <26848.1619016260@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/8h2A9KfmUn_rW-_8EGeJmn1n_qY>
Subject: [Cbor] draft-ietf-cbor-file-magic
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 14:44:37 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/
version -01 has been posted today which reflects that IANA has allocated Tag
55800 to the CBOR Sequence.  (That happened a few weeks ago, but I had not =
reposted)

This version also includes some review from Carsten, sent as a pull request.
Many small nits: thank you for them.

My belief is that the document is done, and should proceed to WGLC.
A GENART review is probably in order.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCAOkQACgkQgItw+93Q
3WUGFgf/c4S/aP5PEMBzNb+lcO6yN6FGQMaEzbZolVLBULrlhAhviXY7hpPDVJbM
GX2IjqsIy/42C8jDp5jWfmyXIgKzKdIjXwBtiL8xM28jmKyPJQbfUZhx+YUYcFmm
QuJHRTC/9ZQVL/nANBTcHB4J9AThUMNzGvWH6r62K2sR76hP5+YwESoRKND+Xvb/
4C6uNmFbWNKahMIZrA0fvivLCLpZppXfJyCWrhfc15Q+e9Np3/LuQgSkBgfhTNSp
4gZeCsxeKrBaxEYDAxCJAAOtQh9a4Skb6IKRkFGVnfDJe6OiF03SylPGtLo+9idk
jb7W570B6Wsht6/IUkTgxc+O/MP5zg==
=K964
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 21 07:48:41 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BA43A2A93; Wed, 21 Apr 2021 07:48:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: cbor@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: cbor@ietf.org
Message-ID: <161901652070.21189.10766815933127378426@ietfa.amsl.com>
Date: Wed, 21 Apr 2021 07:48:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/U2zUeqLTDqM6x3SW8kqy-8gvxb4>
Subject: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 14:48:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Concise Binary Object Representation Maintenance and Extensions WG of the IETF.

        Title           : CBOR tags for IPv4 and IPv6 addresses and prefixes
        Author          : Michael Richardson
	Filename        : draft-ietf-cbor-network-addresses-04.txt
	Pages           : 6
	Date            : 2021-04-21

Abstract:
   This document describes two CBOR Tags to be used with IPv4 and IPv6
   addresses and prefixes.

   RFC-EDITOR-please remove: This work is tracked at https://github.com/
   cbor-wg/cbor-network-address


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cbor-network-addresses/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-cbor-network-addresses-04.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cbor-network-addresses-04


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Apr 21 07:52:58 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C79B73A2AB3; Wed, 21 Apr 2021 07:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 DkSr5Hin2EH4; Wed, 21 Apr 2021 07:52:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A4643A2ABA; Wed, 21 Apr 2021 07:52:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 27A35390B7; Wed, 21 Apr 2021 11:00:33 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZOwOgY7svQ2B; Wed, 21 Apr 2021 11:00:29 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8000A390B4; Wed, 21 Apr 2021 11:00:29 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 52A33653; Wed, 21 Apr 2021 10:52:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cbor@ietf.org, 6man@ietf.org
In-Reply-To: <161901652070.21189.10766815933127378426@ietfa.amsl.com>
References: <161901652070.21189.10766815933127378426@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 21 Apr 2021 10:52:47 -0400
Message-ID: <29493.1619016767@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/F924VlSPq8ouuaCFm4aawckbnAM>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 14:52:57 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


internet-drafts@ietf.org wrote:
    > Title           : CBOR tags for IPv4 and IPv6 addresses and prefixes
    > Author          : Michael Richardson
    > Filename        : draft-ietf-cbor-network-addresses-04.txt
    > Pages           : 6
    > Date            : 2021-04-21

...

    > A diff from the previous version is available at:
    > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cbor-network-addresses=
-04

The Designated Expert had already assigned the tags for -03, which was
published March 25.
Again, Carsten sent a few small edits, which are included in -04.

I am CC'ing 6man here, because perhaps someone there will have an opinion.

I believe that the document is done.
I have running code.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCAPD4ACgkQgItw+93Q
3WWvCAf/VqEbBPohwFWU2PoUJEdCBr43F9iMfUzW1ER0P0qHMUoPcltIYShw/+yo
jG/klmg6hbJQEryd8c03fGhzgha2wr/MblV+9lgApSe3GpQrROZY5a7u5V1NRfu7
0EfR4GeSjDDtbNIzfE4SbFsIx/iND+fv2/YhUuvvCZZACnGVmNalWq3s8+eD04wb
ljDk71MftKRXsQkNKwBNU7rAnkIXFxPyIdu2fInqbfsViXWLiNpRQmnNQQ5tjD/r
URKbHBgUVoI5eWX1y4sT5o8/G2OXfhnvNTip/lOiJGbbS15CgD+EwwMSeP/ALi6g
NCFnmqf0qVYeACpXCI/8GQfbLZiUyw==
=LY+w
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 21 08:15:45 2021
Return-Path: <christian@amsuess.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECD63A2B9B; Wed, 21 Apr 2021 08:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.793
X-Spam-Level: 
X-Spam-Status: No, score=-0.793 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOCALPART_IN_SUBJECT=1.107, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 o4uuGAyKk89O; Wed, 21 Apr 2021 08:15:40 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F4A3A2B9D; Wed, 21 Apr 2021 08:15:37 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id CBBB9407AD; Wed, 21 Apr 2021 17:15:29 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 52F66D3; Wed, 21 Apr 2021 17:15:28 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:9391:8308:15c5:2377]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 132C710A; Wed, 21 Apr 2021 17:15:28 +0200 (CEST)
Received: (nullmailer pid 1851879 invoked by uid 1000); Wed, 21 Apr 2021 15:15:27 -0000
Date: Wed, 21 Apr 2021 17:15:27 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: draft-ietf-cbor-file-magic@ietf.org
Cc: cbor@ietf.org
Message-ID: <YIBBjy5wuep9yd+M@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AMMwATS0tPVQvRIY"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/3ZyvYvoMiFbUC5uaOv75Q_CBlmo>
Subject: [Cbor] draft-ietf-cbor-file-magic: Processing recommendations
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 15:15:44 -0000

--AMMwATS0tPVQvRIY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Michael,

looking at cbor-file-magic from the "implementing generic tools" (static
CoAP file server, downloading CoAP client) point of view, I'm wondering
whether anything actionable for these cases.

I'm tempted to do crazy things, serving content formats from recognized
CBOR protocol tags, and possibly stripping the tagging once transferred
into a Content-Format option, or doing the inverse when downloading into
a file. Turning down the crazy, these things may make more sense in an
opt-in fashion both on the server and on the client side. Going only
half the way and serving the content-format while also sending the full
data stream probably makes no sense (if the data was really intended to
be application/octet-stream, the server is already lying about the
content format, and stealing the inital bytes just adds to the charges).

Is there any recommendation on that topic that you'd deem sensible,
either in-document or just on the "it's been discussed on the list"
record?

(On the mapping between content formats and tags I'll have to revisit
the discussion history; I was under the impression that at some point
this was tied to content format numbers, as in "registering 2**16 tags
at once", but seems I was mistaken here).

BR
c

PS. Is bcp really the intended category for that document?

--=20
Yesterday is history, tomorrow is a mystery, and today is a gift. That
is why it is called the present.
  -- ancient saying

--AMMwATS0tPVQvRIY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECM1tElX6OodcH7CWOY0REtOkveEFAmCAQYwACgkQOY0REtOk
veHbew/+JIL9t5Mwt/Xu6nUvq8Hn60WcmcCP418WH9R7VVgobS7kSNyaW+sOcfA7
i9TK/9EkKjuO4cCS6+Xb3kNwzYx/Ab1aLaJxFKDdmdKcyDq5DDtinvOeqPIt5UtE
Vbag7KGctgsr/WJtmdL1NoAH5HXI4mK8hq3ju7s2gBJibaJvBsmOrcod1cxOzn4x
uZi10avftyUKKARJ2MAZ0AXHPPpsNA4yIXYRe9laq3CkHcDqI0j/rx4RYyr/2Rqf
p7dD8IYTXCskXobn4CWxMbPQZ5tNhIF65olj5pDihQvs73VPGIkFWf/SUmDHIXGm
RQ0pCClzQFzSlWLevVkXsvvRcWTmfdkn/ofQYO2wwLNY6vxbxMr1BBxPHDoHMear
bYPwHWArDTttLRPs1I87bw4HVREu56le2l2F96HlWkJaw0/qBMH9uHHdsF0WcE5A
hKUX8agrxWZjEDGVdsqLSyBxbBAlZBHVtz2ahSghy+DEvVPOmhH99ZW80S/V72vC
xEZcy4S6pyURVq3gNoLkUI0wfHbWDiMQ64ihlYm0o5GOtAvO3uCItP61vRUu6htF
sbJtgGlsiTfsiAcfwPpOVENHtPcGhFZ5La2qy6lD2UlKZVOLbK1LgmzWLgOIFDh6
Bf0WwftaRakHJekMpoyVUeu96Bfctvac7QaGekFQntj41nXJdy8=
=UUGt
-----END PGP SIGNATURE-----

--AMMwATS0tPVQvRIY--


From nobody Wed Apr 21 08:27:46 2021
Return-Path: <christian@amsuess.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903833A26CB for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 08:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 0o2gCzYrAV3E for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 08:27:36 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C398C3A2C62 for <cbor@ietf.org>; Wed, 21 Apr 2021 08:27:08 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id C4818407AD; Wed, 21 Apr 2021 17:27:05 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 35B83D3; Wed, 21 Apr 2021 17:27:05 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:9391:8308:15c5:2377]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 02EE110A; Wed, 21 Apr 2021 17:27:05 +0200 (CEST)
Received: (nullmailer pid 1852588 invoked by uid 1000); Wed, 21 Apr 2021 15:27:04 -0000
Date: Wed, 21 Apr 2021 17:27:04 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Message-ID: <YIBESErn5JhXgtgq@hephaistos.amsuess.com>
References: <26848.1619016260@localhost>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="d6Mcw8CNXnFitQR0"
Content-Disposition: inline
In-Reply-To: <26848.1619016260@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/t4TFND_lkyC1X1fn9ZFlRNLsiaI>
Subject: Re: [Cbor] draft-ietf-cbor-file-magic
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 15:27:40 -0000

--d6Mcw8CNXnFitQR0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Carsten,

> This version also includes some review from Carsten, sent as a pull reque=
st.
> Many small nits: thank you for them.

that PR looks like you've been thoroughly over the document and found
mostly minor editorial things.

Can you upgrade that into an explicit review by adding your view on the
document's maturity and correctness?

Thanks
Christian

--=20
To use raw power is to make yourself infinitely vulnerable to greater power=
s.
  -- Bene Gesserit axiom

--d6Mcw8CNXnFitQR0
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECM1tElX6OodcH7CWOY0REtOkveEFAmCAREUACgkQOY0REtOk
veFs4BAAp7JzP30DvJxMp8KKAe/flCMLxIAxkAR68Vinzw7ixiEPqzhhTxfP0IKm
SUFGsRO8Tlz5CogaG8wYLP9JiY/tZEkI6dzXeL0Wy7Ecd2/Ya4Fmz9rqhTqwwVPJ
BIALpNYwwh2OwZdUFlfA0pDEI/14TyzSK2BJPxommG2uP305148brHWrtwJUe56D
/FsqFTrHm4Z2ppdI5UY7zjvb4oWjgOx0de8ZyRRZ3xkKOhz6aiTs+ych9ZK7Jh85
8OAFfEb8bGXrngJlP0U7qBi1sy1SQNQHrn2KeKbSxaPmWJ3ByJH6Grn4LmFMHK9a
JvyEklQez7npZiJlmlMEEvV31vxLXV/OD2vmk7IW8wuq7oA+uoOu3wDzJzETfpP6
ee73fFWAeG1iCJ8pyqPNkYZNVLITPpxsKDZ1+GwhaMdct04ySc3O5yIAZnw06Gvr
p4HiVUP2uqZiCFgCWYhRn9J4r8RyuFsBIAGQSSC0DeZGggbWejQ9j83vY7XlQ2p6
NoAuxxuVQjFWdZEjiDuYLX8i0wOXRjv/FJuwjLXOiMPE7lDgsWR3SkVaCoo5VzmG
MDq7j+FW59ghD1EsHLycvx6S6LSWe+jCNZEmBQLZ973696vlejqzbACHcUWPKAH2
McJ91vPZ9WG4qy8WK43SbhUOJNhQ6GP4syvhmqnNnUq3a1mUdcI=
=aEH+
-----END PGP SIGNATURE-----

--d6Mcw8CNXnFitQR0--


From nobody Wed Apr 21 08:46:16 2021
Return-Path: <christian@amsuess.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C01B13A2CC6 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 08:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 Ng3XTQOCa16S for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 08:46:10 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B59C3A2CED for <cbor@ietf.org>; Wed, 21 Apr 2021 08:46:10 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 553A9407AD; Wed, 21 Apr 2021 17:46:06 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 7F3D4D3; Wed, 21 Apr 2021 17:46:04 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:9391:8308:15c5:2377]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 3E93B10A; Wed, 21 Apr 2021 17:46:04 +0200 (CEST)
Received: (nullmailer pid 1853562 invoked by uid 1000); Wed, 21 Apr 2021 15:46:03 -0000
Date: Wed, 21 Apr 2021 17:46:03 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Ira McDonald <blueroofmusic@gmail.com>
Message-ID: <YIBIuxT7GclCpRx3@hephaistos.amsuess.com>
References: <161514460151.27711.5917503298881031512@ietfa.amsl.com> <BA5404FF-46D1-436C-BAC2-947504330DED@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="42J0uF/su6jcYxrQ"
Content-Disposition: inline
In-Reply-To: <BA5404FF-46D1-436C-BAC2-947504330DED@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/PfcvJK0vmb-_y2zDzqlxFfA6F_U>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-cddl-control-03.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 15:46:15 -0000

--42J0uF/su6jcYxrQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello CBOR group,

> https://datatracker.ietf.org/doc/draft-ietf-cbor-cddl-control/
>
> The intention is that -03, if we like it, would be the basis for
> potential pre-WGLC reviews and/or a WGLC.

I'd like to start a WGLC on this at the next interim, but this will need
review from the working group as well.

If you enjoy this document, please hit the like button and subscri...
oh, wait, wrong track: please write a review to enable the document's
progression towards publication.

Thanks
Christian

--=20
You don't use science to show that you're right, you use science to
become right.
  -- Randall Munroe

--42J0uF/su6jcYxrQ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECM1tElX6OodcH7CWOY0REtOkveEFAmCASLgACgkQOY0REtOk
veF1oA//W/dolciERQ6kYOL3UFSy+1HuxZRZjOwzr+hT72pmpMWDnS1fLIg0En90
Lgs82rkOHLMrJUjYznB5WCh4vJwYTQLwsfpRCD/zU7h6YaPcDN377qH8u98DRsi7
tKZPNAEPkIeiK+MAPBA81JT2O7PUm91WiMAXiwk6LZJY3TDOTajgh7+fu5T+zIul
AWN90jHf4rbH0C3zXZdFgx8z0F5MoHTAkBqejxY4vno5xpkcDLMQt7WPkpffy7+0
IjG3oqez35XIlngvyBOhCMFiYj4d/fLLXQbxoYlXj7pDDeM9p8D8zw0Koz2a+zab
5umhPxne5xWRsPxBnoP0Y85VL/QBTgiVyB27zjCaA5jJku0y67c5mfbLTtJ2AzjN
wSA0N/PGOXlBB43V4DlIzweC/ymUS2k4LZUDz8MgJFFvhwqNLpUzx69j1g6V3Fam
/Jo29VZzH7vof97LlscjQIVPu+8HAJCzJ92tP94Ll51tJ3ASIAuVNnIazP2ZM3pc
PjT3CvClmpFveZD/+dhshtcPLMgBDOcJbJsNRtRjhda/9P+h3453s+7odFYjZaWT
aVY2EBp8DbEX8kvrnzPCI7rNfGFN/N4eK9noYF7Y3livawP5ZkJXa5/6bGy65gTA
u0MbadprAabUvhwACWGjY1WVL37dcS7sMAl0erwoppNiMszOi3A=
=mksU
-----END PGP SIGNATURE-----

--42J0uF/su6jcYxrQ--


From nobody Wed Apr 21 12:00:29 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41433A3429 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 12:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 YGHsIvaMawj6 for <cbor@ietfa.amsl.com>; Wed, 21 Apr 2021 12:00:19 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F4D03A333E for <cbor@ietf.org>; Wed, 21 Apr 2021 12:00:12 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FQVHD5yrCzyTV; Wed, 21 Apr 2021 21:00:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <74E0F02D-1AAB-444B-ABCA-82EACEF27B5F@tzi.org>
Date: Wed, 21 Apr 2021 21:00:08 +0200
X-Mao-Original-Outgoing-Id: 640724408.284946-b0be74bc4512b7ad92d29f0dc39cd7ad
Content-Transfer-Encoding: quoted-printable
Message-Id: <97099EDD-49D2-45FC-A790-C7A986BFFACE@tzi.org>
References: <161788356811.31539.2139615008210880278@ietfa.amsl.com> <74E0F02D-1AAB-444B-ABCA-82EACEF27B5F@tzi.org>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/qzPhCGPr5liRJtfRK5c3qNzqz4w>
Subject: Re: [Cbor] OID representation (was: Re: Robert Wilton's Discuss on draft-ietf-cbor-tags-oid-06: (with DISCUSS and COMMENT))
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 19:00:28 -0000

On 2021-04-08, at 21:44, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> (1) Not establishing any stronger connection between TBD111 and =
TBD112, i.e. status quo.
> (2) Declaring TBD112 as the preferred encoding of an absolute OID that =
starts with 1.3.6.1.4.1 (0x2b06010401), but still allowing the use of =
TBD111 as non-preferred.   This would mean a requirement on decoders =
implementing TBD111 to also implement TBD112.
> (3) Outlawing any TBD111 starting with (0x2b06010401) and requiring =
the use of TBD112 in all such cases.  This would mean a requirement on =
both encoders and decoders.  It would also mean a slight complication in =
tag factoring: replace all naked byte strings that start with =
h=E2=80=992b06010401=E2=80=99 by TBD112(rest) (saving three bytes), =
unless *all* such byte strings start with h=E2=80=992b06010401=E2=80=99, =
in which case these prefixes would all be removed and an outer tag of =
TBD112 used.
>=20
> (2a) would be (2) with a deterministic encoding requirement to use the =
shortest form (i.e., (3) in deterministic encoding only).

At today=E2=80=99s interim meeting, we opted for (2a).

I have now added the text necessary for this in PR #10 [1].

Please send comments and reviews; I plan to bottle this up in a -04 and =
a response to Rob by the weekend.

Gr=C3=BC=C3=9Fe, Carsten


[1]: https://github.com/cbor-wg/cbor-oid/pull/10=


From nobody Wed Apr 21 12:37:15 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11DD23A3406; Wed, 21 Apr 2021 12:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 91l5dWesjKDs; Wed, 21 Apr 2021 12:37:08 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 002AF3A3402; Wed, 21 Apr 2021 12:37:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0269738E6B; Wed, 21 Apr 2021 15:44:47 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id isgZ2xzczLN0; Wed, 21 Apr 2021 15:44:45 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2C40638E38; Wed, 21 Apr 2021 15:44:45 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 3DA2A653; Wed, 21 Apr 2021 15:37:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian =?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FAms=3DFCss=3F=3D?= <christian@amsuess.com>
cc: draft-ietf-cbor-file-magic@ietf.org, cbor@ietf.org
In-Reply-To: <YIBBjy5wuep9yd+M@hephaistos.amsuess.com>
References: <YIBBjy5wuep9yd+M@hephaistos.amsuess.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 21 Apr 2021 15:37:02 -0400
Message-ID: <6496.1619033822@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/gxzQ2xfScMyZ53JX-4bpGPFmzW4>
Subject: Re: [Cbor] draft-ietf-cbor-file-magic: Processing recommendations
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 19:37:13 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Christian Ams=C3=BCss <christian@amsuess.com> wrote:
    > Hello Michael,

    > looking at cbor-file-magic from the "implementing generic tools" (sta=
tic
    > CoAP file server, downloading CoAP client) point of view, I'm wonderi=
ng
    > whether anything actionable for these cases.

My opinion is: not really.

    > I'm tempted to do crazy things, serving content formats from recogniz=
ed
    > CBOR protocol tags, and possibly stripping the tagging once transferr=
ed
    > into a Content-Format option, or doing the inverse when downloading i=
nto
    > a file.

I certainly think that storing the media type with the file is smart.
MacOS does it, and a number of non-/pre-Unix systems forced the file
extension.  It wasn't until Unix/CPM/DOS that had pseudo-relevant file
extensions, but didn't enforce any meaning on them that we things got
confusing.  But, that was because "it's all a stream of bytes" meant that y=
ou
could apply tools in a less regimented way.
In a world of XML,JSON,CBOR, being able to process records has started to
have some appeal again.

I think that deriving a media type (both for CoAP and HTTP) from the
cbor-file-magic makes sense.  Whether or not you want to strip off the
12-byte sequence-style prefix is another question to me.

    > Turning down the crazy, these things may make more sense in an
    > opt-in fashion both on the server and on the client side. Going only
    > half the way and serving the content-format while also sending the fu=
ll
    > data stream probably makes no sense (if the data was really intended =
to
    > be application/octet-stream, the server is already lying about the
    > content format, and stealing the inital bytes just adds to the charge=
s).

I agree.

    > Is there any recommendation on that topic that you'd deem sensible,
    > either in-document or just on the "it's been discussed on the list"
    > record?

I think that a place where it wins is forensics.
We know that we are going to embed trust anchors into systems.
The trust anchors are public keys with authorizations attached to them.
Marking each trust anchor with what it's intended to validate
is cheap and easily avoids confusion.
     ("Huh, so your refridgerator trusts the root DNSSEC key for software
       updates, and it can't do DNS if you turn on DNSSEC? How did that hap=
pen?")

The second place is where two possible CBOR encoded things can be sent over
some channel.  Or where a CBOR encode thing, or a legacy thing might be sen=
t,
and the legacy thing already has some kind of magic header.

    > PS. Is bcp really the intended category for that document?

Yes, because there really isn't any SHOULD/MUST here.
The 55800 tag, which we added for this document, is of general use.
The per-protocol tag is one which the user of this BCP obtains, so we aren't
specifying anything there.

We are just explaining a way to use existing mechanism to put things togeth=
er.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCAft0ACgkQgItw+93Q
3WUnuQf/Q6b4ws1Surr+TdKCEIMQGlJyplTHuM6OcxOR6hVP62VDa4gAgLF12IoI
Hm+TlOqw71cgJ/QT/LIS/Favg9Vi4fbLVHX2HSvPJ7AhLjNdjCtW1/0YSUHWlgG3
4ZG6tzwzxlL8gKbGCVlF2vK0/HBTHmZ32e4O4RNyw4YqsFJ+jUiczS34b+SZCbCB
mhr1HjKD3x5BpT2G/Ka6UbcI9ODbNkmb+MGfh1z+3NSC1erJsOo9kiPGCKZAkzAP
D2XdpVEek/FfxNkhpcxCXia8juWkMZ/vkOyun7I7I9ObvQv/1MNY8jdPg044E8YO
iW5ZRoM4z6qRksZPkvHJ9R1f/4jYSw==
=uzAM
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 21 13:23:56 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A20123A355E; Wed, 21 Apr 2021 13:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 PKe2Gd_2xgDF; Wed, 21 Apr 2021 13:23:51 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 261243A355B; Wed, 21 Apr 2021 13:23:51 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FQX7n02JQzyQG; Wed, 21 Apr 2021 22:23:48 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <YIBBjy5wuep9yd+M@hephaistos.amsuess.com>
Date: Wed, 21 Apr 2021 22:23:48 +0200
Cc: draft-ietf-cbor-file-magic@ietf.org, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 640729428.404537-7a71ee86b92ca41811508728aaabba45
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D11722B-D0A5-4439-9E78-A6FCD967FD55@tzi.org>
References: <YIBBjy5wuep9yd+M@hephaistos.amsuess.com>
To: =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/z1LSIXWY0XtFbzPYT6xP-Irns54>
Subject: Re: [Cbor] draft-ietf-cbor-file-magic: Processing recommendations
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 20:23:56 -0000

On 2021-04-21, at 17:15, Christian Ams=C3=BCss <christian@amsuess.com> =
wrote:
>=20
> (On the mapping between content formats and tags I'll have to revisit
> the discussion history; I was under the impression that at some point
> this was tied to content format numbers, as in "registering 2**16 tags
> at once", but seems I was mistaken here).

I still like the idea.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Apr 22 11:08:53 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7A23A11CF for <cbor@ietfa.amsl.com>; Thu, 22 Apr 2021 11:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 xDIeZMGHSZY3 for <cbor@ietfa.amsl.com>; Thu, 22 Apr 2021 11:08:48 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3AB3A11BF for <cbor@ietf.org>; Thu, 22 Apr 2021 11:08:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id B532D38EBB for <cbor@ietf.org>; Thu, 22 Apr 2021 14:16:32 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4gZwsfFoPzQx for <cbor@ietf.org>; Thu, 22 Apr 2021 14:16:32 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 29DCE38E32 for <cbor@ietf.org>; Thu, 22 Apr 2021 14:16:32 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AC22F63E for <cbor@ietf.org>; Thu, 22 Apr 2021 14:08:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cbor@ietf.org
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 22 Apr 2021 14:08:45 -0400
Message-ID: <27225.1619114925@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/KS9yPXoebHUyOCrX91yXzMuzhvQ>
Subject: Re: [Cbor] draft-ietf-cbor-file-magic (fwd) Christos Zoulas: Re: draft-ietf-cbor-file-magic
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Apr 2021 18:08:52 -0000

--==-=-=
Content-Type: multipart/mixed; boundary="=-=-="

--=-=-=
Content-Type: text/plain


Forwarding with permission.


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline; filename=43
Content-Description: forwarded message

Replied: Wed, 21 Apr 2021 15:40:30 -0400
Replied: "Christos Zoulas <christos@zoulas.com> christos@astron.com"
Return-Path: <christos@zoulas.com>
Received: from tuna.sandelman.ca [2607:f0b0:f:3::184]
	by localhost with IMAP (fetchmail-6.4.0.beta4)
	for <mcr@sandelman.ca> (single-drop); Wed, 21 Apr 2021 12:21:20 -0400 (EDT)
Received: from tuna.sandelman.ca ([unix socket])
	 by tuna (Cyrus 2.5.10-Debian-2.5.10-3+deb9u2) with LMTPA;
	 Wed, 21 Apr 2021 12:02:55 -0400
X-Sieve: CMU Sieve 2.4
Received: from localhost (localhost [127.0.0.1])
	by tuna.sandelman.ca (Postfix) with ESMTP id 6BFF3390F0
	for <mcr@sandelman.ca>; Wed, 21 Apr 2021 12:02:55 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1])
	by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id jtWnwA09m0Bh for <mcr@sandelman.ca>;
	Wed, 21 Apr 2021 12:02:51 -0400 (EDT)
Received: from rebar.astron.com (rebar.astron.com [IPv6:2620:106:3003:1f00:9e8e:99ff:fe15:cae4])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by tuna.sandelman.ca (Postfix) with ESMTPS id 7EB72390E4
	for <mcr@sandelman.ca>; Wed, 21 Apr 2021 12:02:51 -0400 (EDT)
Received: from 2603-7000-2640-0003-2cd5-6361-a714-8482.res6.spectrum.com (2603-7000-2640-0003-2cd5-6361-a714-8482.res6.spectrum.com [IPv6:2603:7000:2640:3:2cd5:6361:a714:8482])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by rebar.astron.com (Postfix) with ESMTPSA id 7A34F17FE0B;
	Wed, 21 Apr 2021 11:55:06 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=zoulas.com; s=201908;
	t=1619020506; bh=LSyYGQ0GX3/iDcRgJcVSuzsA1v7FC3PaQjWItPhV9Oo=;
	h=From:Subject:Date:In-Reply-To:Cc:To:References;
	b=kOjexBCVnVAXAyvp5o07MIp0osb7Yl5Zsts/cqQWod3V06jI0pE+c65vLwSZ7BP13
	 xk2jDmphYtUVwbnlK13kny4enmq9qi4s8g2FEhZ6GlZxsU9KHnyaXk0+TFnua55K4J
	 hGyAFemxU5EZIqjZhsVPFKV6DBAtd1XqI5itQEfeO2+HG1Co1So5XDzIbEVf4tFvrf
	 IuzhZ/3w9QxN38BXiZY4xiy08hzPIgx7dYQsZB0EsM8wNW1wh91AB7IF1MYnisdhfb
	 WDP4TL2TkE7TjMbwz9z6z2VLaRKerLeX8Joosxt/RptxrsDzTAeQSaCbFe2P8Bvk9S
	 03lLcUjBH/RBg==
From: Christos Zoulas <christos@zoulas.com>
Message-Id: <5E8907D4-61C4-4588-9893-B5307BD9F6EE@zoulas.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_F3BDA540-734D-4A83-83D0-4AD8E8859F25";
	protocol="application/pgp-signature";
	micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Subject: Re: [Cbor] draft-ietf-cbor-file-magic
Date: Wed, 21 Apr 2021 11:55:05 -0400
In-Reply-To: <27539.1619016403@localhost>
Cc: christos@astron.com
To: Michael Richardson <mcr@sandelman.ca>
References: <27539.1619016403@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.21)


--Apple-Mail=_F3BDA540-734D-4A83-83D0-4AD8E8859F25
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DC3B6F04-DD1B-4DA5-A8CC-E2E9DBB4E505"


--Apple-Mail=_DC3B6F04-DD1B-4DA5-A8CC-E2E9DBB4E505
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

LGTM, no comments :-) It has the right attributes:
- long magic
- starts binary (since it is binary data)
- magic number looks unique.

Best.

christos

> On Apr 21, 2021, at 10:46 AM, Michael Richardson <mcr@sandelman.ca> =
wrote:
>=20
>=20
> Hi Christos,
>=20
> I thought I'd give you a heads up on this document.
> You may have some comments.  Email cbor@ietf.org, or issue at:
>   https://github.com/cbor-wg/cbor-magic-number
>=20
> Thank you for file(1).
>=20
>=20
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> Subject: [Cbor] draft-ietf-cbor-file-magic
> Date: April 21, 2021 at 10:44:20 AM EDT
> To: cbor@ietf.org
>=20
>=20
>=20
> https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/
> version -01 has been posted today which reflects that IANA has =
allocated Tag
> 55800 to the CBOR Sequence.  (That happened a few weeks ago, but I had =
not reposted)
>=20
> This version also includes some review from Carsten, sent as a pull =
request.
> Many small nits: thank you for them.
>=20
> My belief is that the document is done, and should proceed to WGLC.
> A GENART review is probably in order.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T =
consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
>=20
>=20
>=20
>=20
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor
>=20
>=20


--Apple-Mail=_DC3B6F04-DD1B-4DA5-A8CC-E2E9DBB4E505
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">LGTM,=
 no comments :-) It has the right attributes:<div class=3D"">- long =
magic</div><div class=3D"">- starts binary (since it is binary =
data)</div><div class=3D"">- magic number looks unique.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Best.</div><div =
class=3D""><br class=3D""></div><div class=3D"">christos</div><div =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 21, 2021, at 10:46 AM, Michael Richardson &lt;<a =
href=3D"mailto:mcr@sandelman.ca" class=3D"">mcr@sandelman.ca</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><br =
class=3D"">Hi Christos,<br class=3D""><br class=3D"">I thought I'd give =
you a heads up on this document.<br class=3D"">You may have some =
comments. &nbsp;<a href=3D"mailto:cbor@ietf.org" class=3D"">Email =
cbor@ietf.org</a>, or issue at:<br class=3D""> &nbsp;&nbsp;<a =
href=3D"https://github.com/cbor-wg/cbor-magic-number" =
class=3D"">https://github.com/cbor-wg/cbor-magic-number</a><br =
class=3D""><br class=3D"">Thank you for file(1).<br class=3D""><br =
class=3D""><br class=3D""><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(127, 127, 127, 1.0);" class=3D""><b =
class=3D"">From: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" =
class=3D"">Michael Richardson &lt;<a href=3D"mailto:mcr+ietf@sandelman.ca"=
 class=3D"">mcr+ietf@sandelman.ca</a>&gt;<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(127, 127, 127, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">[Cbor] =
draft-ietf-cbor-file-magic</b><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(127, 127, 127, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">April 21, 2021 at 10:44:20 AM =
EDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(127, 127, 127, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a href=3D"mailto:cbor@ietf.org" =
class=3D"">cbor@ietf.org</a><br class=3D""></span></div><br class=3D""><br=
 class=3D""><br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-cbor-file-magic/</a=
><br class=3D"">version -01 has been posted today which reflects that =
IANA has allocated Tag<br class=3D"">55800 to the CBOR Sequence. =
&nbsp;(That happened a few weeks ago, but I had not reposted)<br =
class=3D""><br class=3D"">This version also includes some review from =
Carsten, sent as a pull request.<br class=3D"">Many small nits: thank =
you for them.<br class=3D""><br class=3D"">My belief is that the =
document is done, and should proceed to WGLC.<br class=3D"">A GENART =
review is probably in order.<br class=3D""><br class=3D"">--<br =
class=3D"">Michael Richardson &lt;mcr+IETF@sandelman.ca&gt; =
&nbsp;&nbsp;. o O ( IPv6 I=C3=B8T consulting )<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sandelman =
Software Works Inc, Ottawa and Worldwide<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">CBOR mailing list<br class=3D"">CBOR@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/cbor<br class=3D""><br =
class=3D""><br class=3D""></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_DC3B6F04-DD1B-4DA5-A8CC-E2E9DBB4E505--

--Apple-Mail=_F3BDA540-734D-4A83-83D0-4AD8E8859F25
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iF0EARECAB0WIQS+BJlbqPkO0MDBdsRxESqxbLM7OgUCYIBK2QAKCRBxESqxbLM7
OnhZAKCiY3RYqx8sjpO/gHltRmZGB3KKzwCfazeQDxSaRW6/PVHtTiMsXOsbfoE=
=CAm3
-----END PGP SIGNATURE-----

--Apple-Mail=_F3BDA540-734D-4A83-83D0-4AD8E8859F25--

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=--

--==-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCBu60ACgkQgItw+93Q
3WWd4QgAqZYvZyWN96DS15UuINB2vC0pN8gPSH+2O4AvvuatOwg0uqqs/XWBWOpB
zGe7whYiypXQzI1T1x1FpNH1fLNsHMOeW4dFPWMSLr8x+jPdsYr5FyY9IyO3g3q2
+BcxkhuSpGnXk7lDNAtl8s/39WUaer4/76e2gH/pDfvWFQedxQby75nu8WTe7pKx
i//hrKT4xzhrlkvZoDiyVbv2W9737WmolDnEmSRBK8QFxmc5A6fEr0rMtp8VVg83
KHbZopRbEmdGRaHYQ1QWlimOsocXV9Ti5znQpEK4bYkwcR06ZzhgcuxSE3TES0aM
7bNiBAzcg6e4wHBnsyl+7Fdo2UAKkg==
=ZYh7
-----END PGP SIGNATURE-----
--==-=-=--


From nobody Fri Apr 23 03:45:54 2021
Return-Path: <otroan@employees.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 607AA3A180D; Fri, 23 Apr 2021 03:45:52 -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, SPF_HELO_NONE=0.001, SPF_PASS=-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 vN2Rp9TvJypn; Fri, 23 Apr 2021 03:45:48 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51D193A180C; Fri, 23 Apr 2021 03:45:48 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [91.239.252.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id EA0804E11A43; Fri, 23 Apr 2021 10:45:45 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 0FE5356244B5; Fri, 23 Apr 2021 12:45:43 +0200 (CEST)
From: otroan@employees.org
Message-Id: <95B40318-7555-401E-9913-E1308723CB39@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_1F7E90BB-89C5-43B7-B24D-8BF8AA9F29C2"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Fri, 23 Apr 2021 12:45:41 +0200
In-Reply-To: <29493.1619016767@localhost>
Cc: cbor@ietf.org, 6man@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <161901652070.21189.10766815933127378426@ietfa.amsl.com> <29493.1619016767@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/VSSS8bvQeDtOgpadIZBIu8yXMCQ>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Apr 2021 10:45:52 -0000

--Apple-Mail=_1F7E90BB-89C5-43B7-B24D-8BF8AA9F29C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Do you want to say anthing about tag 261 or perhaps subsume tag 261 into =
this?

Why do you have "Trailing zero bytes MUST be omitted." as it seems the =
decoder would happily deal with trailing zeros?

Cheers,
Ole

> On 21 Apr 2021, at 16:52, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> Signed PGP part
>=20
> internet-drafts@ietf.org wrote:
>> Title           : CBOR tags for IPv4 and IPv6 addresses and prefixes
>> Author          : Michael Richardson
>> Filename        : draft-ietf-cbor-network-addresses-04.txt
>> Pages           : 6
>> Date            : 2021-04-21
>=20
> ...
>=20
>> A diff from the previous version is available at:
>> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cbor-network-addresses-04
>=20
> The Designated Expert had already assigned the tags for -03, which was
> published March 25.
> Again, Carsten sent a few small edits, which are included in -04.
>=20
> I am CC'ing 6man here, because perhaps someone there will have an =
opinion.
>=20
> I believe that the document is done.
> I have running code.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T =
consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
>=20
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_1F7E90BB-89C5-43B7-B24D-8BF8AA9F29C2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdu1h07DO3As4hPTA3JCvLd9yNkgFAmCCpVUACgkQ3JCvLd9y
Nkha8BAAiA/eunZPQREaGYQscx0vzYxcefEKlYklhN97ZEWGedCD/9r/P2CSsCwU
chExzg4WIjnQOXN1EWtwCJ2YZjky02qqhOTRu959nMOva8QRvHuj0YJTSBhHw+es
5p7qiOYnVTfv2BwWJOaD1xFXTV9ax/9ERT5/Y2T+UOd24gCdUHqFmYlHpT9JkRn8
V2/i3XvqATVQcLWLFeEKJNvPk59IdFNKFUXiBdErqKaamwEYSk13TRSixRawRiTz
vgIThYcNMB7JhD1lkXQLeC9gKBl/WMPqJO+Clo6t0A4lDR1XqLKux69V5lcwhkNC
SXcYUxpmDZjE5pEUl3MYkJxuYmGKc8m5SHyqOxZUrPMW9mfPRLWHDhkoZJLzRplD
cQGpomN7ugi7nnyZ8712SRFYyqKYLJe/ifwk5WSXejzjK5XPJ82Ns0wH42XO/gwE
LUKaaWhYFdupYj0/61X4WDyxWGYwoqgXbhGTIcvrxYTV40HFfPfoKBPZlSRD7f/C
6E5JQv3dTbkJfeu0AuH+0v1vQtsknUAtlLe8XZ0oYYJ5IgPCOjlB0ya2i+Ld4EIr
3WcX8zSqG5zFNJDnPmnhKG8P3fes/fPtBuUqShxo5hK4sT1OMEXGLR0yZ9LTqIC1
W2XaRYnGX3UaFEk1MhoZyFhtVTUI7oERbbV7IZpgRGDv/2d89/s=
=lW+T
-----END PGP SIGNATURE-----

--Apple-Mail=_1F7E90BB-89C5-43B7-B24D-8BF8AA9F29C2--


From nobody Fri Apr 23 08:29:23 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C433A123C; Fri, 23 Apr 2021 08:29:16 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 IlX4ADoMbAIe; Fri, 23 Apr 2021 08:29:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CE2A3A122E; Fri, 23 Apr 2021 08:29:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B0320F4078C; Fri, 23 Apr 2021 08:29:01 -0700 (PDT)
To: smbarte2@illinois.edu, henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210423152901.B0320F4078C@rfc-editor.org>
Date: Fri, 23 Apr 2021 08:29:01 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/i3M2clwl8023kSoJxsEhkAs692Q>
Subject: [Cbor] [Errata Held for Document Update] RFC8610 (6527)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Apr 2021 15:29:17 -0000

The following errata report has been held for document update 
for RFC8610, "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6527

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Sean Bartell <smbarte2@illinois.edu>
Date Reported: 2021-04-11
Held by: Francesca Palombini (IESG)

Section: B

Original Text
-------------
text = %x22 *SCHAR %x22
SCHAR = %x20-21 / %x23-5B / %x5D-7E / %x80-10FFFD / SESC
SESC = "\" (%x20-7E / %x80-10FFFD)

Corrected Text
--------------
SESC = "\" ( %x22 / "/" / "\" /                 ; \" \/ \
             %x62 / %x66 / %x6E / %x72 / %x74 / ; \b \f \n \r \t
             (%x75 hexchar) )                   ; \u
hexchar = non-surrogate / (high-surrogate "\" %x75 low-surrogate)
non-surrogate = ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
               ("D" %x30-37 2HEXDIG )
high-surrogate = "D" ("8"/"9"/"A"/"B") 2HEXDIG
low-surrogate = "D" ("C"/"D"/"E"/"F") 2HEXDIG

Notes
-----
As discussed during the CBOR interim 2021-04-21 and in the mailing list: https://mailarchive.ietf.org/arch/msg/cbor/ljHAiw-WhNqoIKAzkjZa4WIf56Q/ 
--
The ABNF used in [RFC8610] for the content of text string literals is rather permissive:

text = %x22 *SCHAR %x22
SCHAR = %x20-21 / %x23-5B / %x5D-7E / %x80-10FFFD / SESC
SESC = "\" (%x20-7E / %x80-10FFFD)

This allows almost any non-C0 character to be escaped by a backslash, but critically misses out on the \uXXXX and \uHHHH\uLLLL forms that JSON allows to specify characters in hex. Both can be solved by updating the SESC production to:

SESC = "\" ( %x22 / "/" / "\" /                 ; \" \/ \
             %x62 / %x66 / %x6E / %x72 / %x74 / ; \b \f \n \r \t
             (%x75 hexchar) )                   ; \u
hexchar = non-surrogate / (high-surrogate "\" %x75 low-surrogate)
non-surrogate = ((DIGIT / "A"/"B"/"C" / "E"/"F") 3HEXDIG) /
               ("D" %x30-37 2HEXDIG )
high-surrogate = "D" ("8"/"9"/"A"/"B") 2HEXDIG
low-surrogate = "D" ("C"/"D"/"E"/"F") 2HEXDIG

Now that SESC is more restrictively formulated, this also requires an update to the BCHAR production used in the ABNF syntax for byte string literals:

bytes = [bsqual] %x27 *BCHAR %x27
BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
bsqual = "h" / "b64"
The updated version explicit allows \', which is no longer allowed in the updated SESC:

BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / "\'" / CRLF


--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Apr 23 08:34:37 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50BFC3A12C3; Fri, 23 Apr 2021 08:34:35 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 wB4dqIkrT8kZ; Fri, 23 Apr 2021 08:34:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A2FF3A12BE; Fri, 23 Apr 2021 08:34:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 63018F4078C; Fri, 23 Apr 2021 08:34:23 -0700 (PDT)
To: smbarte2@illinois.edu, henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210423153423.63018F4078C@rfc-editor.org>
Date: Fri, 23 Apr 2021 08:34:23 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/j1w8lrBBEXlwXva74N9gYGB7jks>
Subject: [Cbor] [Errata Held for Document Update] RFC8610 (6543)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Apr 2021 15:34:35 -0000

The following errata report has been held for document update 
for RFC8610, "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6543

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Sean Bartell <smbarte2@illinois.edu>
Date Reported: 2021-04-13
Held by: Francesca Palombini (IESG)

Section: B

Original Text
-------------
     bytes = [bsqual] %x27 *BCHAR %x27
     BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF

Corrected Text
--------------
     bytes = %x27 *BCHAR %x27
           / bsqual %x27 *QCHAR %x27
     BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
     QCHAR = DIGIT / ALPHA / "+" / "/" / "-" / "_" / "=" / WS


Notes
-----
As discussed during the CBOR interim 2021-04-21 and in the mailing list: https://mailarchive.ietf.org/arch/msg/cbor/ekFn8a4GbUQAk4nyhc-Il-ZRLZc/
--

The ABNF used in [RFC8610] for the content of byte string literals lumps together byte strings notated as text with byte strings notated in base16 (hex) or base64 (but see also updated BCHAR production above):

bytes = [bsqual] %x27 *BCHAR %x27
BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF

Errata report 6543 proposes to handle the two cases in separate productions (where, with an updated SESC, BCHAR obviously needs to be updated as above):

bytes = %x27 *BCHAR %x27
      / bsqual %x27 *QCHAR %x27
BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF
QCHAR = DIGIT / ALPHA / "+" / "/" / "-" / "_" / "=" / WS

This potentially causes a subtle change, which is hidden in the WS production:

WS = SP / NL
SP = %x20
NL = COMMENT / CRLF
COMMENT = ";" *PCHAR CRLF
PCHAR = %x20-7E / %x80-10FFFD
CRLF = %x0A / %x0D.0A

This allows any non-C0 character in a comment, so this fragment becomes possible:

foo = h'
   43424F52 ; 'CBOR'
   0A       ; LF, but don't use CR!
'

The current text is not unambiguously saying whether the three apostrophes need to be escaped with a \ or not, as in:

foo = h'
   43424F52 ; \'CBOR\'
   0A       ; LF, but don\'t use CR!
'
... which would be supported by the existing ABNF in [RFC8610].

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG


From nobody Sun Apr 25 03:40:59 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C79C3A1542; Sun, 25 Apr 2021 03:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 nfLxSp1FGs29; Sun, 25 Apr 2021 03:40:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64DD23A1544; Sun, 25 Apr 2021 03:40:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 887BF38984; Sun, 25 Apr 2021 06:48:47 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ENl6H1a498nO; Sun, 25 Apr 2021 06:48:46 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 1A88C391E2; Fri, 23 Apr 2021 18:30:31 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 33A495E; Fri, 23 Apr 2021 18:22:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: otroan@employees.org
cc: cbor@ietf.org, 6man@ietf.org
In-Reply-To: <95B40318-7555-401E-9913-E1308723CB39@employees.org>
References: <161901652070.21189.10766815933127378426@ietfa.amsl.com> <29493.1619016767@localhost> <95B40318-7555-401E-9913-E1308723CB39@employees.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 23 Apr 2021 18:22:40 -0400
Message-ID: <12496.1619216560@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/hZWL__kN7h3RvqTRK3EzXKi3LQI>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2021 10:40:59 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


otroan@employees.org wrote:
    > Do you want to say anthing about tag 261 or perhaps subsume tag 261
    > into this?

Hi, I wasn't happy with tag 260/261.
In addition to not distinguishing between v4 and v6 explicitely, tag 260 al=
so
confused 6-byte ethernet into the definition, and did not accomodate 8-byte
ethernet.
Tag 261 (on prefixes), I did not understand, which is why I wrote the docum=
ent.

    > Why do you have "Trailing zero bytes MUST be omitted." as it seems the
    > decoder would happily deal with trailing zeros?

Yes, well Postel rule definitely applies here.

For prefixes, a concern was expressed that irrelvant bits could be included
and could form some kind of intentional convert channel.  Worse, they could
be a non-intentional leak of private information (a la Heartbleed).
So, it might be good to be able to make sure that encoders were more conser=
vative.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCDSK8ACgkQgItw+93Q
3WXhgwgAshD70Dgu76hwyZOBaCLWLB/P70a49BNb1D81/bTnCKGPGR5D7fiJZxWf
ILLRIxqfQHUY73iRwr71jLsbdDoTdptnZpbA1/ag8yreQ3jQWcTEMM0Ym43OWq2L
Hb8iop8y108H8fwSPCl6BjhQYhuX/A2ibBV5ucWYYzBnSS1CHAJF2rHbTgBoe3wh
7uTT7LBwP3KmhRmr3M32IxVLjyeR2+KhKePFPX8rjtu1JZRDcic6OVeEDo8NFNpn
Ws3fGTASn9dKJNTXgCW7aZkdVE4mvAeIikF277uzI7xk0sTm1oyF6EBuE9fUtdlG
W94D+LULkQy2yWhsTLoVTBNxW5eviQ==
=eo+Y
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Apr 25 04:06:18 2021
Return-Path: <otroan@employees.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD073A163E; Sun, 25 Apr 2021 04:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 lbIKFeHj6ls5; Sun, 25 Apr 2021 04:06:14 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76B643A163D; Sun, 25 Apr 2021 04:06:14 -0700 (PDT)
Received: from [192.168.10.78] (dhcp193287181.blix.com [193.28.7.181]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 5F4234E11D08; Sun, 25 Apr 2021 11:06:13 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Date: Sun, 25 Apr 2021 13:06:10 +0200
Message-Id: <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org>
References: <12496.1619216560@localhost>
Cc: cbor@ietf.org, 6man@ietf.org
In-Reply-To: <12496.1619216560@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPhone Mail (18D70)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Ru36HQXnrJeTawVv-OtVNhanypQ>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2021 11:06:17 -0000

Thanks Michael,

Top posting.=20
- for 261 I would at least include those arguments and make it clear when to=
 use or the other
- so you don=E2=80=99t want to support the commonly used shortcut of specify=
ing both and address and a prefix in one?
- in ip agnostic code I often find I just need an IP address instead of havi=
ng to care if it=E2=80=99s 4 or 6. It would therefore be nice with a general=
 IP address and ip prefix type too.=20

Cheers=20
Ole

> On 25 Apr 2021, at 12:40, Michael Richardson <mcr+ietf@sandelman.ca> wrote=
:
>=20
> =EF=BB=BF
> otroan@employees.org wrote:
>> Do you want to say anthing about tag 261 or perhaps subsume tag 261
>> into this?
>=20
> Hi, I wasn't happy with tag 260/261.
> In addition to not distinguishing between v4 and v6 explicitely, tag 260 a=
lso
> confused 6-byte ethernet into the definition, and did not accomodate 8-byt=
e
> ethernet.
> Tag 261 (on prefixes), I did not understand, which is why I wrote the docu=
ment.
>=20
>> Why do you have "Trailing zero bytes MUST be omitted." as it seems the
>> decoder would happily deal with trailing zeros?
>=20
> Yes, well Postel rule definitely applies here.
>=20
> For prefixes, a concern was expressed that irrelvant bits could be include=
d
> and could form some kind of intentional convert channel.  Worse, they coul=
d
> be a non-intentional leak of private information (a la Heartbleed).
> So, it might be good to be able to make sure that encoders were more conse=
rvative.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consult=
ing )
>           Sandelman Software Works Inc, Ottawa and Worldwide
>=20
>=20
>=20
>=20


From nobody Sun Apr 25 08:30:26 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2813A1701; Sun, 25 Apr 2021 08:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 2MfALRxTk84G; Sun, 25 Apr 2021 08:30:18 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C15163A16FF; Sun, 25 Apr 2021 08:30:16 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FSsR94zQfzySd; Sun, 25 Apr 2021 17:30:13 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org>
Date: Sun, 25 Apr 2021 17:30:13 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cbor@ietf.org, 6man@ietf.org
X-Mao-Original-Outgoing-Id: 641057413.204631-678098a5db77b1125362e352a981a0f8
Content-Transfer-Encoding: quoted-printable
Message-Id: <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Wl5B-7Q55ojgpQOPIhbehfgK3Dg>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2021 15:30:20 -0000

> - for 261 I would at least include those arguments and make it clear =
when to use or the other

Sounds good to me.

> - so you don=E2=80=99t want to support the commonly used shortcut of =
specifying both and address and a prefix in one?

That is a valid point.
But I think the data should indicate whether they are just a prefix or =
an address and a prefix.

> - in ip agnostic code I often find I just need an IP address instead =
of having to care if it=E2=80=99s 4 or 6. It would therefore be nice =
with a general IP address and ip prefix type too.=20

If I understand this right, we already have that.  One type with two =
different tags=E2=80=A6
(CBOR doesn=E2=80=99t have =E2=80=9Ctypes=E2=80=9D [except for the =
=E2=80=9Cmajor types=E2=80=9D on the representation level].  You are =
free to construct your own types in your implementation, e.g. construct =
a =E2=80=9CBoolean=E2=80=9D type from =E2=80=9Ctrue=E2=80=9D and =
=E2=80=9Cfalse=E2=80=9D.  In your case, the =E2=80=9CIP address and =
prefix=E2=80=9D type would include values with either tag 52 or 54.  We =
could define recommended CDDL types, like we did in Section 5 of RFC =
8746...)

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Apr 25 14:12:38 2021
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87A33A103C; Sun, 25 Apr 2021 14:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ITQ0kz8K57AC; Sun, 25 Apr 2021 14:12:32 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 771C83A103A; Sun, 25 Apr 2021 14:12:32 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id g16so10986869plq.3; Sun, 25 Apr 2021 14:12:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HJ0+l7gQn64dYW9XkdG1+2WkbNdYSAUovAqsre8/Ydg=; b=V0Jc7U8H6dkXLEWlLATjVUKgajJkqnESTrmANbGL61zi8rbKQrksc0sqbXnA43A1rq d5F9Lj2x+wuMDNbnRYEjey+uoSKwdxRb74AjuScapd6X9/N/QgsFWDerMD7mk4dUfkTH SJDJIUlDXIS2OLuxG+le6ksSB3HtWiIwhIZLlel3MEnPy75udZojPefMlvqlJF6lGfxf +Xc2+wTNd31MXd/hUmGZoXxnhFfgRksJYiqqKMb68s2Ia8B7fniQb8NMOVHDDXbZkzUC K2NTUkMXZ1AOYS0uOLHxxnfav17G25l5RLDAQE5lnkkmAAX2DpHR8FUqH13aWf/6TS9f 5H3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HJ0+l7gQn64dYW9XkdG1+2WkbNdYSAUovAqsre8/Ydg=; b=UCM222SMrFSj/qCco3A3IzEBMaHmf40zjzSwlwfgh8eMgXVUuBcMbX5ySexw3TmCZd tt49b2ieXVuYfXCfCsrsFMCIZBb7TTyUDl1NqDUFaiDL43XBL+gSI23Yp/uqGydhuxBL lfYo3fRMyI8GnaVq7MNBYLIH8yswyDAQ+HWs26Hs/BAKegitIdPmAmJ/2y3rxgwROJox VmhgNgXfwd3oE/m7ooxWSh7z/53YXu3KPiLMAnlkp86Ow1MQPxTBGn7wftUKpUBOZGSd w5b5sVY9FBlYyLS+AAHRGg9utI4XMH+Nv2U6wYrke8pe3xssFU1IMJ9jMAIozXXhHbHL nCcg==
X-Gm-Message-State: AOAM533RuOOmocqJ4dmw9lBh0yIUWW2rPvSEH5xa7w1xNFlZ++EEl5HN Cl3wvHIyYhWEHlNb08Tl2+dHC0AWMJkBXQ==
X-Google-Smtp-Source: ABdhPJxezWvecQjvb0mLTdgVDwjXkxl5s+/AUByH6bSbqdrHqm3sWyd5UtiSuYNj3wwsgf9CzFpx/g==
X-Received: by 2002:a17:902:7c17:b029:ec:bfde:23e2 with SMTP id x23-20020a1709027c17b02900ecbfde23e2mr15074008pll.33.1619385150828;  Sun, 25 Apr 2021 14:12:30 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.131.14]) by smtp.gmail.com with ESMTPSA id 23sm9533124pgo.53.2021.04.25.14.12.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Apr 2021 14:12:30 -0700 (PDT)
To: Carsten Bormann <cabo@tzi.org>, Ole Troan <otroan@employees.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, 6man@ietf.org, cbor@ietf.org
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <647a725f-69a8-43bd-0500-0e382dc50a5f@gmail.com>
Date: Mon, 26 Apr 2021 09:12:24 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/jvZ4aYRlamTsMA4kV1UTARzNzqc>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2021 21:12:37 -0000

On 26-Apr-21 03:30, Carsten Bormann wrote:
>> - for 261 I would at least include those arguments and make it clear w=
hen to use or the other
>=20
> Sounds good to me.
>=20
>> - so you don=E2=80=99t want to support the commonly used shortcut of s=
pecifying both and address and a prefix in one?
>=20
> That is a valid point.
> But I think the data should indicate whether they are just a prefix or =
an address and a prefix.
>=20
>> - in ip agnostic code I often find I just need an IP address instead o=
f having to care if it=E2=80=99s 4 or 6. It would therefore be nice with =
a general IP address and ip prefix type too.=20

This is very dependent on the context where you are using the address. So=
metimes you need to be address-family independent and sometimes not. It c=
an also be programming-language dependent. And it can be API dependent (w=
ho are you passing the address to?). So I think this will have to be hand=
led by the parser of the decoded CBOR, not by the CBOR tagging.
=20
> If I understand this right, we already have that.  One type with two di=
fferent tags=E2=80=A6

Yes, and how you cast it into a particular language's type(s) is not a CB=
OR issue.

> (CBOR doesn=E2=80=99t have =E2=80=9Ctypes=E2=80=9D [except for the =E2=80=
=9Cmajor types=E2=80=9D on the representation level].  You are free to co=
nstruct your own types in your implementation, e.g. construct a =E2=80=9C=
Boolean=E2=80=9D type from =E2=80=9Ctrue=E2=80=9D and =E2=80=9Cfalse=E2=80=
=9D.  In your case, the =E2=80=9CIP address and prefix=E2=80=9D type woul=
d include values with either tag 52 or 54.  We could define recommended C=
DDL types, like we did in Section 5 of RFC 8746...)

Sure. But in GRASP we ended up with=20
  ipv4-address =3D bytes .size 4
  ipv6-address =3D bytes .size 16
which wouldn't suit every case.=20

Regards
    Brian

>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Sun Apr 25 17:06:29 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 833C43A03FE; Sun, 25 Apr 2021 17:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 GTADX3Y8NcrX; Sun, 25 Apr 2021 17:06:22 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47CC33A03FB; Sun, 25 Apr 2021 17:06:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id BE01338BA6; Sun, 25 Apr 2021 20:14:18 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id y_JzY3eeUG41; Sun, 25 Apr 2021 20:14:18 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5411538BA5; Sun, 25 Apr 2021 20:14:18 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9D07D486; Sun, 25 Apr 2021 20:06:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ole Troan <otroan@employees.org>
cc: cbor@ietf.org, 6man@ietf.org
In-Reply-To: <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sun, 25 Apr 2021 20:06:19 -0400
Message-ID: <14010.1619395579@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/enqKNVdm1MOrHpk04Lue94HiIac>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 00:06:28 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Ole Troan <otroan@employees.org> wrote:
    > - for 261 I would at least include those arguments and make it clear
    > when to use or the other

I'm not sure it's fair to criticise 261.

    > - so you don=E2=80=99t want to support the commonly used shortcut of =
specifying
    > both and address and a prefix in one?

I don't understand your suggestion.
    X - address
[n,X] - prefix

    > - in ip agnostic code I often find I just need an IP address instead =
of
    > having to care if it=E2=80=99s 4 or 6. It would therefore be nice wit=
h a
    > general IP address and ip prefix type too.

So, I think that I've done this.

When you find that you need a v4 or a v6 in your schema, you would just wri=
te
"IPaddress", and then let the tag tell your decoder whether it was v4 or v6.

I used this CDDL in my use case:

IPaddress =3D #6.260(v6addr) / #6.261(v4addr)
IPsubnet  =3D #6.260([prefixlen, v6addr])
          / #6.261([prefixlen, v4addr])
prefixlen =3D uint
v6addr    =3D bytes .size 16
v4addr    =3D bytes .size 4

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCGA/oACgkQgItw+93Q
3WUNvwgAiFlQZSbhyrKQQfRA/XMggrJNpTqqtU2xS9F3EHJcfxXaWySFaPsy1pXZ
JFThq7k87qNmHPl38Ozvtt/KtKCJbk8b0HtE5QE1mjACv+AmfQtCeKYlVYNYj5v0
kfpjUK8Z9aOuFenQASI87DqXzkKgN272LSengXnZAyul1Ack23vWeDlahL+YD2Kb
0+wpEeHPz7mAWIL5BX51W9wB08MTKfFUsVBC1ZceGMIcSWE+hjS9SHqvd/EtWSbg
3L/ZYc0pom/SGw3DkFJW8XTKQRi/j/OwO03KjkzX+1IcKqanAO/4c+Nqpi1wnUAt
eSmKqfpitqhVyutDjKKKMy+sgHcpGA==
=VHVx
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Apr 25 17:47:34 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4A63A0B69; Sun, 25 Apr 2021 17:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 uY-DRnsVciiQ; Sun, 25 Apr 2021 17:47:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 076213A0B6C; Sun, 25 Apr 2021 17:47:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AA9A838BB6; Sun, 25 Apr 2021 20:55:21 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YDlGWCKEbNtn; Sun, 25 Apr 2021 20:55:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BBAC438BB5; Sun, 25 Apr 2021 20:55:19 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E82A2486; Sun, 25 Apr 2021 20:47:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
In-Reply-To: <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Sun, 25 Apr 2021 20:47:20 -0400
Message-ID: <26182.1619398040@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Ii_aasqpJYqSUXkt7uDMMJHVw4Y>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 00:47:29 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    >> - for 261 I would at least include those arguments and make it clear=
 when to use or the other

    > Sounds good to me.

What I'm hearing is that you'd like me to write something like below.
  https://github.com/cbor-wg/cbor-network-address/commit/c7962ed01ef0f63773=
cca70c97be54edc481bb78


# Introduction

{{RFC8949}} defines a number of CBOR Tags for common items.

Tag 260 and tag 261 was later defined through IANA.
These tags cover addresses (260), and prefixes (261).
Tag 260 distinguishes between IPv4, IPv6 and Ethernet through the length of=
 the byte string only.
Tag 261 was not documented well enough to be used.

The author wanted an explicit indication of IPv4 or IPv6, and the possibili=
ty to omit trailing zeroes.

This document provides a format for IPv6 and IPv4 addresses and prefixes.
Prefixes may omit trailing zeroes in the address.
Due to the complexity of testing the value of omitting trailing zeros for a=
ddresses was considered non-essential and support for that was removed in t=
his specification.

This document does not deal with 6 or 8-byte ethernet addressees.





=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCGDZgACgkQgItw+93Q
3WVX6gf/aNlxGB3/EkcYzR+T2EyXpqdQxP+xC9h5nu/ailPXPUGK4O88pdHGWhQF
WTw3+OkooBga9uZUw2AeNMioXBQjuUow9v37+5JEu2zvazH0AX/xT7GUhdnJ8smL
j17m6pY0q9OBg7bcfwJuzJyBCk306Fq0PPUdb31Ttal+HhTyo+PtxF3eRefxbYe3
yagPSrLP5k4+amcnG1vrfGS6IKSb9+ZZxoMnVWZxb7789pg6I3EOL28nfavhK7Za
C4SdrrWH6U7I69bWv0QaF0oGsPQSyNL2cbyufOto2oGvISn3SkMVz6AxTt6rd3w6
J9+tQtYiM9Hr8dSKe8TLqH9XdAYq3Q==
=ZvZJ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Apr 25 22:15:37 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 870323A1911; Sun, 25 Apr 2021 22:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 0nkJ2uOl7xDv; Sun, 25 Apr 2021 22:15:23 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC4333A190F; Sun, 25 Apr 2021 22:15:21 -0700 (PDT)
Received: from [192.168.217.112] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FTClB1j5FzyVP; Mon, 26 Apr 2021 07:15:18 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <14010.1619395579@localhost>
Date: Mon, 26 Apr 2021 07:15:17 +0200
Cc: Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <14010.1619395579@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/KHSDAZvVCiTdoFtx6ALN26hlp4E>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 05:15:28 -0000

On 26. Apr 2021, at 02:06, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
>> - so you don=E2=80=99t want to support the commonly used shortcut of =
specifying
>> both and address and a prefix in one?
>=20
> I don't understand your suggestion.
>    X - address
> [n,X] - prefix

Back in IPv4-land, we often said something like

=E2=80=9CConfigure the interface to 192.168.3.5/24=E2=80=9D

Which is a short-cut for

=E2=80=9CConfigure the interface to address 192.168.3.5, prefix =
192.168.3.0/24=E2=80=9D

Since address/prefix is structurally similar to a prefix (but uses a =
full 32-bit address), it could be expressed by adding a third case

>    A - address
> [n,P] - prefix
> [A,n] - address/prefix

Where A is a 4-byte byte-string, P is a 0-to-4-byte byte string, and n =
is an unsigned integer 0 to 32.

This construct is less common in IPv6-land, because n is usually 64, so =
sending the address suffices, but there are exceptions to that here, =
too.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sun Apr 25 22:18:46 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1FB3A192D; Sun, 25 Apr 2021 22:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 PFyPdDYhk6GI; Sun, 25 Apr 2021 22:18:40 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5B9F3A1929; Sun, 25 Apr 2021 22:18:39 -0700 (PDT)
Received: from [192.168.217.112] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FTCq22Jk3zyVc; Mon, 26 Apr 2021 07:18:38 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <26182.1619398040@localhost>
Date: Mon, 26 Apr 2021 07:18:37 +0200
Cc: Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <225FB2BC-4E10-40AA-9165-D098029B2AAD@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <5989D772-0104-4F12-A43B-AFBC77266C9C@tzi.org> <26182.1619398040@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/_iIVnFXD0GoIKCGerm1DGEMf4Cs>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 05:18:45 -0000

On 26. Apr 2021, at 02:47, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
>=20
> Carsten Bormann <cabo@tzi.org> wrote:
>>> - for 261 I would at least include those arguments and make it clear =
when to use or the other
>=20
>> Sounds good to me.
>=20
> What I'm hearing is that you'd like me to write something like below.
>  =
https://github.com/cbor-wg/cbor-network-address/commit/c7962ed01ef0f63773c=
ca70c97be54edc481bb78
>=20
>=20
> # Introduction
>=20
> {{RFC8949}} defines a number of CBOR Tags for common items.
>=20
> Tag 260 and tag 261 was later defined through IANA.
> These tags cover addresses (260), and prefixes (261).
> Tag 260 distinguishes between IPv4, IPv6 and Ethernet through the =
length of the byte string only.
> Tag 261 was not documented well enough to be used.
>=20
> The author wanted an explicit indication of IPv4 or IPv6, and the =
possibility to omit trailing zeroes.

s/The author wanted/The present specification achieves/ or some such.

> This document provides a format for IPv6 and IPv4 addresses and =
prefixes.
> Prefixes may omit trailing zeroes in the address.
> Due to the complexity of testing the value of omitting trailing zeros =
for addresses was considered non-essential and support for that was =
removed in this specification.

Need a comma after =E2=80=9Ctesting=E2=80=9D.
s/removed/not provided/

> This document does not deal with 6 or 8-byte ethernet addressees.

MAC addresses, more generally.

Gr=C3=BC=C3=9Fe, Carsten



From nobody Tue Apr 27 03:51:20 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14AA73A0E17; Tue, 27 Apr 2021 03:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 LJCNqgZu87LL; Tue, 27 Apr 2021 03:51:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 207AD3A0E15; Tue, 27 Apr 2021 03:51:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 60EBA3898E; Tue, 27 Apr 2021 06:59:14 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GhjZ2Bba0Mi1; Tue, 27 Apr 2021 06:59:13 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D624D389AF; Mon, 26 Apr 2021 14:31:06 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4B77B61B; Mon, 26 Apr 2021 14:23:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
In-Reply-To: <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <14010.1619395579@localhost> <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 26 Apr 2021 14:23:05 -0400
Message-ID: <22810.1619461385@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/mk4F9qq17jdCbtuw6zjLuXLmI_U>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 10:51:19 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    >>> both and address and a prefix in one?
    >>
    >> I don't understand your suggestion.
    >> X - address
    >> [n,X] - prefix

    > Back in IPv4-land, we often said something like

    > =E2=80=9CConfigure the interface to 192.168.3.5/24=E2=80=9D

Ah, oh yes.
Ole is this what you had in mind?

    > Which is a short-cut for

    > =E2=80=9CConfigure the interface to address 192.168.3.5, prefix 192.1=
68.3.0/24=E2=80=9D

    > Since address/prefix is structurally similar to a prefix (but uses a
    > full 32-bit address), it could be expressed by adding a third case

    <1> A - address
    <2> [n,P] - prefix
    <3> [A,n] - address/prefix

<3> is forced because case <2> demands that the trailing bits are zero, and
are ideally omitted.  If we didn't insist on that, then we could do it all
with one case.

I find the need for a third case a bit inelegant, but I can live with it.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCHBQgACgkQgItw+93Q
3WWzyQgAwHOWvvGZqxyyN4QCSvfNym4ilv+dYENITDSXqNvLtVjSwUOpXVxL6OZj
WuKAtFMURVJZX7so4UJToeAeDab9w987GGva7sYetyIZGvojccyKcYFS64VVDnEr
d8ms1At5Q74Rr/PfZEqmj1+Bf34lDbgxgAxGgvTTUgbZM88YLl+qKW5bmxazMmVb
4i0yYn9NxG88ieb0PKIkTpAOoDfoXYbiT8jBGT29rhboNMkxoXTcYW8fTI5dsQzv
VaaU644bSNWF0K61KpPEmi3GU7pKDLbb3882STTSW2Q4BVpLsdvJJ/4mbmxmVIZ8
LB19LbrX+dXVo+HjLmiffhoz7CcnHw==
=DelA
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 27 03:57:46 2021
Return-Path: <otroan@employees.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87873A0E66; Tue, 27 Apr 2021 03:57:40 -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, SPF_HELO_NONE=0.001, SPF_PASS=-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 71mJNuRZrCNd; Tue, 27 Apr 2021 03:57:38 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D63643A0E63; Tue, 27 Apr 2021 03:57:37 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [IPv6:2a01:799:151f:d300:3c01:554b:6ee1:b32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id E5CEE4E11AD9; Tue, 27 Apr 2021 10:57:32 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 0C38A573719A; Tue, 27 Apr 2021 12:57:30 +0200 (CEST)
From: otroan@employees.org
Message-Id: <32A35A7F-BC0D-44A9-B3F9-3B6FF026C841@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_AD7C635E-80F1-4FD4-823B-C58E141854AE"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 27 Apr 2021 12:57:29 +0200
In-Reply-To: <22810.1619461385@localhost>
Cc: Carsten Bormann <cabo@tzi.org>, cbor@ietf.org, 6man@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <14010.1619395579@localhost> <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org> <22810.1619461385@localhost>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/VCa-W8JDBBVfpQQH71EkaSj9uX0>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 10:57:41 -0000

--Apple-Mail=_AD7C635E-80F1-4FD4-823B-C58E141854AE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Michael,

>>>> both and address and a prefix in one?
>>>=20
>>> I don't understand your suggestion.
>>> X - address
>>> [n,X] - prefix
>=20
>> Back in IPv4-land, we often said something like
>=20
>> =E2=80=9CConfigure the interface to 192.168.3.5/24=E2=80=9D
>=20
> Ah, oh yes.
> Ole is this what you had in mind?

Yes. Although I think it equally applies to IPv6. An implementation =
should not and can not assume 64.

>> Which is a short-cut for
>=20
>> =E2=80=9CConfigure the interface to address 192.168.3.5, prefix =
192.168.3.0/24=E2=80=9D
>=20
>> Since address/prefix is structurally similar to a prefix (but uses a
>> full 32-bit address), it could be expressed by adding a third case
>=20
>    <1> A - address
>    <2> [n,P] - prefix
>    <3> [A,n] - address/prefix
>=20
> <3> is forced because case <2> demands that the trailing bits are =
zero, and
> are ideally omitted.  If we didn't insist on that, then we could do it =
all
> with one case.
>=20
> I find the need for a third case a bit inelegant, but I can live with =
it.

It has it's pros and cons.
Configuring the on-link prefix and configuring the address are two =
separate things indeed.
It is a short-cut.

If you choose not to support it, it might be worth having a little blurb =
stating how configured an address and connected prefix would look like.


Best regards,
Ole

--Apple-Mail=_AD7C635E-80F1-4FD4-823B-C58E141854AE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdu1h07DO3As4hPTA3JCvLd9yNkgFAmCH7hkACgkQ3JCvLd9y
Nkh35g/6AgrA9i7+p4Vzw1gJMJCZdz3TxSBCFvbwj9Sa0WsB+HUQH6spR0nIiH2q
nHZu8Fd6a2dCIXM4wl7yhwYgjlJ7plUpIMZAMMQJ+sL7z8wkv5tR1Ur3pYKH9OED
H18jpUmhgUeaedVDP6a2C7py72SxINOG/biHKX8f5wUnYzgC7fqmL6jy1Lu9QSDJ
55iBtoqJpfmsF+ssH0mo6DfatMRS/gk+r1ne1RC677W6wDSmvNn1LdcafrJjh6i+
VeXukIfSX4Tdh5Rl52oV+/i4SAxeoJyS6mQED3KQHORGqdQ1eUM8KRf1u9ntrktd
RGUwo8bRxGeVxCEsJbMyUqaht8EwMAPVOWJ8oiS2uyJiLFnKq39r9l/EJ8lW0sly
tEoAYE9CfSL8WaZMI5JST9PxT4ukSK570kOEIIrbBMvE3HgPPWdfhr22SNRy8L1O
QBxNQyPpsC9mrV6E7wZHMm1uIzldevvJsd1KG7S9Pvmfvi4FX2PenPCHrbQIPDNp
q7efSk0tDu/JNT/rO9KjT/nQgAvYj6TeJh0+KtIipTQ/sUHYC4HdrCegFfXBrPsb
ZrBdX44gn8Dq5W7D/7MmQS14GXXuxe+qrSzzkMe4S0VuKhdSJNPqjTCpbRp9BiE4
ikgdoXC+FZ1KOHfbiF50zqgjjUA8/2ykjccfawBT5RUC7VvWTHE=
=Pjgj
-----END PGP SIGNATURE-----

--Apple-Mail=_AD7C635E-80F1-4FD4-823B-C58E141854AE--


From nobody Tue Apr 27 04:06:40 2021
Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF9A3A0FCB; Tue, 27 Apr 2021 04:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 gq27W7rE1_sC; Tue, 27 Apr 2021 04:06:33 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B97C3A0F61; Tue, 27 Apr 2021 04:06:33 -0700 (PDT)
Received: from [192.168.217.112] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FTzTz59T8zyjQ; Tue, 27 Apr 2021 13:06:31 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <22810.1619461385@localhost>
Date: Tue, 27 Apr 2021 13:06:30 +0200
Cc: Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B077F0BB-A409-4FB8-92FB-987B214F9C24@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <14010.1619395579@localhost> <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org> <22810.1619461385@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/wZSjxbsCRi41tGJ_uXFwOp98S1Q>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 11:06:38 -0000

On 26. Apr 2021, at 20:23, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> I find the need for a third case a bit inelegant, but I can live with =
it.

The purpose of the tag is to indicate the semantics, and I agree with =
Ole that prefix =E2=89=A0 interface configuration (address + prefix).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Apr 27 12:15:26 2021
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05AA3A1CAE; Tue, 27 Apr 2021 12:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 igG7JvKyrck4; Tue, 27 Apr 2021 12:15:20 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1739E3A1CAA; Tue, 27 Apr 2021 12:15:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AA5F43898B; Tue, 27 Apr 2021 15:23:23 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JwHKGRPmde4x; Tue, 27 Apr 2021 15:23:22 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 106D438A2E; Tue, 27 Apr 2021 11:48:20 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2651F4F5; Tue, 27 Apr 2021 11:40:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Ole Troan <otroan@employees.org>, cbor@ietf.org, 6man@ietf.org
In-Reply-To: <B077F0BB-A409-4FB8-92FB-987B214F9C24@tzi.org>
References: <12496.1619216560@localhost> <C3A4A868-4B39-4428-93AA-D0B88F79B9BD@employees.org> <14010.1619395579@localhost> <20BFAC30-05C3-4279-92A0-612D2304EE1E@tzi.org> <22810.1619461385@localhost> <B077F0BB-A409-4FB8-92FB-987B214F9C24@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Tue, 27 Apr 2021 11:40:15 -0400
Message-ID: <25231.1619538015@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/AY4VZ-0pXOnE-8I1ecu4ydp0zSA>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-network-addresses-04.txt
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 19:15:25 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Carsten Bormann <cabo@tzi.org> wrote:
    > On 26. Apr 2021, at 20:23, Michael Richardson <mcr+ietf@sandelman.ca>=
 wrote:
    >>
    >> I find the need for a third case a bit inelegant, but I can live wit=
h it.

    > The purpose of the tag is to indicate the semantics, and I agree with
    > Ole that prefix =E2=89=A0 interface configuration (address + prefix).

I am open to whatever consensus the CBOR WG comes to about including this t=
hird case in the document.
I don't have this need myself.

While I think that this third case *could* be added at a later time,  it
seems silly to omit it if there is interest now.

If there was another syntactic way to distinguish address+"netmask" from
prefix, rather than two orderings of the array, I'd be more keen.

One way is to say that it's all prefixes, but that bits beyond the
prefix-length MAY be set.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmCIMF4ACgkQgItw+93Q
3WX0agf/T8bT2AQkrFLiausK6C1COUua1mp6cS4nAHb++QHMy4wkw33NrvMj4ssL
5rNh8GMK9l7PzmzEF6wCBRR+SOvYOSk+ws0GXxG7ImRmqse9DLX6YJwTvNcG1Wrm
dOEoNvJahDLWPCkoeDdiiHQY6cJW/JrZrlnHPVUG8DRLKzvmbexqOAtgfck77ptP
qXJyR75tbVvyXBWnl4u3CIdqRPFmw0rxwwZyocIfEmgL3IvaoOskRxFi9beZC28v
2lm+VipvzOTNDsQZyGsaCOYLVcrh6eYaS3n9cFs14yFw+UN4xFfj6ErnqaZLUXfr
3L5JXxhkUsxR6kANL3pn0Sh6P5M1qA==
=/KPu
-----END PGP SIGNATURE-----
--=-=-=--

