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

Jim Schaad <ietf@augustcellars.com> Mon, 29 April 2019 16:53 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C61DD120419 for <ace@ietfa.amsl.com>; Mon, 29 Apr 2019 09:53:34 -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_NONE=-0.0001, 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 W4JfeQyPMS73 for <ace@ietfa.amsl.com>; Mon, 29 Apr 2019 09:53:32 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B21C12040F for <ace@ietf.org>; Mon, 29 Apr 2019 09:53:32 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 29 Apr 2019 09:53:03 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Carsten Bormann' <cabo@tzi.org>, 'Felipe Gasper' <felipe@felipegasper.com>
CC: 'Benjamin Kaduk' <kaduk@mit.edu>, 'Roman Danyliw' <rdd@cert.org>, 'Daniel Migault' <daniel.migault@ericsson.com>, <erdtman@spotify.com>, <ace@ietf.org>, <mbj@microsoft.com>, <erik@wahlstromstekniska.se>, <Hannes.Tschofenig@arm.com>
References: <20190429155553.4F894B8217A@rfc-editor.org> <20190429160038.GS60332@kduck.mit.edu> <27E15D28-2659-41BC-A2EA-413EAC544F79@felipegasper.com> <20190429160544.GV60332@kduck.mit.edu> <466A3BDA-1009-46C0-B4EC-579C8573438B@felipegasper.com> <F2A9D0F9-CEA2-4C66-B016-5575DF58C7F6@tzi.org>
In-Reply-To: <F2A9D0F9-CEA2-4C66-B016-5575DF58C7F6@tzi.org>
Date: Mon, 29 Apr 2019 09:53:01 -0700
Message-ID: <004d01d4feac$04310b20$0c932160$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQI0tL8lCM8SoTMIiGXY6hzypI5jsQJ6EmiOAmUbGpMAtCdV6AMU6EKiAVZ5RlelQ/g9AA==
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/rEVp83PekuwbZY-CV73-3VIhgwE>
X-Mailman-Approved-At: Mon, 29 Apr 2019 10:22:38 -0700
Subject: Re: [Ace] [Technical Errata Reported] RFC8392 (5710)
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 16:53:35 -0000


> -----Original Message-----
> From: Carsten Bormann <cabo@tzi.org>
> Sent: Monday, April 29, 2019 9:41 AM
> To: Felipe Gasper <felipe@felipegasper.com>
> Cc: Benjamin Kaduk <kaduk@mit.edu>du>; Roman Danyliw <rdd@cert.org>rg>;
> Daniel Migault <daniel.migault@ericsson.com>om>; erdtman@spotify.com;
> ietf@augustcellars.com; ace@ietf.org; mbj@microsoft.com;
> erik@wahlstromstekniska.se; Hannes.Tschofenig@arm.com
> Subject: Re: [Ace] [Technical Errata Reported] RFC8392 (5710)
> 
> On Apr 29, 2019, at 18:15, Felipe Gasper <felipe@felipegasper.com> wrote:
> >
> > 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.
> 
> s/CBOR item/CBOR data item/ (this is the term we use in 7049)
> 
> Also, I think
> s/UTF-8 string/text string/g
> The fact that this is encoded in UTF-8 is somewhat on a different level of
> detail.

+1 on this.  There is not really a restriction that UTF-8 strings be the key in JSON.  If you encoded the JSON as UTF-16 then it would be a UTF-16 string.

Jim

> 
> Finally, s/signed/negative/ if you want to follow the CBOR terminology here.
> (Otherwise, all unsigned integers are also signed integers :-)
> 
> Grüße, Carsten