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

Benjamin Kaduk <kaduk@mit.edu> Mon, 29 April 2019 16:58 UTC

Return-Path: <kaduk@mit.edu>
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 DB8C8120419 for <ace@ietfa.amsl.com>; Mon, 29 Apr 2019 09:58:00 -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 g_Ue0aFdsa4n for <ace@ietfa.amsl.com>; Mon, 29 Apr 2019 09:57:58 -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 65DCD12040F for <ace@ietf.org>; Mon, 29 Apr 2019 09:57:58 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x3TGv0jr030744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Apr 2019 12:57:02 -0400
Date: Mon, 29 Apr 2019 11:57:00 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Jim Schaad <ietf@augustcellars.com>
Cc: "'Carsten Bormann'" <cabo@tzi.org>, "'Felipe Gasper'" <felipe@felipegasper.com>, "'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
Message-ID: <20190429165700.GY60332@kduck.mit.edu>
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> <004d01d4feac$04310b20$0c932160$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004d01d4feac$04310b20$0c932160$@augustcellars.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/LBrVZC9AEO-xer16x7U2NwkpZ4Y>
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:58:01 -0000

On Mon, Apr 29, 2019 at 09:53:01AM -0700, Jim Schaad wrote:
> 
> 
> > -----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.

I think I'm also +1 on that, but do recall that RFC 8529 mandates UTF-8 for
exchange among a non-closed ecosystem (i.e., all internet usage).

-Ben