Re: [Ace] [Technical Errata Reported] RFC8392 (5710)

[Felipe Gasper <[e-mail]>]

> On Apr 29, 2019, at 12:05 PM, Benjamin Kaduk <[e-mail]> wrote:
> 
> On Mon, Apr 29, 2019 at 12:03:57PM -0400, Felipe Gasper wrote:
>> 
>>> On Apr 29, 2019, at 12:00 PM, Benjamin Kaduk <[e-mail]> wrote:
>>> 
>>> On Mon, Apr 29, 2019 at 08:55:53AM -0700, RFC Errata System wrote:
>>>> The following errata report has been submitted for RFC8392,
>>>> "CBOR Web Token (CWT)".
>>>> 
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata/eid5710
>>>> 
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Felipe Gasper <[e-mail]>
>>>> 
>>>> Section: 1.1
>>>> 
>>>> Original Text
>>>> -------------
>>>> In JSON, maps are called objects and only have one kind of map key: a
>>>>  string.  CBOR uses strings, negative integers, and unsigned integers
>>>>  as map keys.
>>>> 
>>>> Corrected Text
>>>> --------------
>>>> In JSON, maps are called objects and only have one kind of map key:
>>>> a string.  CBOR allows other data types, such as strings, negative
>>>> integers, and unsigned integers, as map keys.
>>>> 
>>>> Notes
>>>> -----
>>>> The text as it stands risks an interpretation that CBOR limits map keys to integers and strings; per discussion on the CBOR mailing list, this is not the case.
>>> 
>>> I see the CBOR list traffic in the archive (e.g.,
>>> https://mailarchive.ietf.org/arch/msg/cbor/LyndIfQipxUfx0cu6nlOwi6ceOY) and
>>> agree with the sentiment that the CWT spec should not inadvertently
>>> over-specify the behavior of CBOR
>>> 
>>> The proposed new text is itself flawed, though, as it claims that strings
>>> are an "other data type" with respect to strings.
>> 
>> Ah, agreed. Is there a way I can update my proposed phrase? The editor only seems to allow submission of a new erratum.
> 
> I can edit the "corrected text" field during the verification process...
> 
>> It may be worth disambiguating between binary and UTF-8 strings, too; JSON only allows UTF-8 strings, while CBOR also allows binary.
> 
> ...so we can figure out the right phrasing here on the list, and then I'll
> fix things up in the system.

So maybe something like:

-----
In JSON, maps are called objects and only have one kind of key:
a UTF-8 string. In CBOR, any valid CBOR item can be a map key.
CWT uses signed and unsigned integers, in addition to UTF-8 strings,
as map keys.
-----

-F