Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

Benjamin Kaduk <kaduk@mit.edu> Tue, 27 February 2018 03:45 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 E3D3212DA16; Mon, 26 Feb 2018 19:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 zF_ZJcoMmPsn; Mon, 26 Feb 2018 19:44:59 -0800 (PST)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 1456A124BAC; Mon, 26 Feb 2018 19:44:58 -0800 (PST)
X-AuditID: 12074422-68bff700000024cf-84-5a94d43873d8
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 88.2E.09423.934D49A5; Mon, 26 Feb 2018 22:44:57 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id w1R3itFd003663; Mon, 26 Feb 2018 22:44:55 -0500
Received: from kduck.kaduk.org (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.13.8/8.12.4) with ESMTP id w1R3ipca007594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Feb 2018 22:44:53 -0500
Date: Mon, 26 Feb 2018 21:44:51 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dan Romascanu <dromasca@gmail.com>
Cc: gen-art@ietf.org, ace@ietf.org, ietf@ietf.org, draft-ietf-ace-cbor-web-token.all@ietf.org
Message-ID: <20180227034450.GU50954@kduck.kaduk.org>
References: <151967178760.21771.14005895812023525211@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <151967178760.21771.14005895812023525211@ietfa.amsl.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42IR4hTV1rW8MiXK4OZmWYvv33qYLbbufsxq 0fhYy+Lqq88sFs82zmdxYPXYOesuu8eSJT+ZApiiuGxSUnMyy1KL9O0SuDL+nV7LWDCNq6J7 +Qf2BsbpHF2MnBwSAiYSm0/OY+xi5OIQEljMJNGyYREjSEJIYCOjxJSuMIjEVSaJ1ofH2UES LAKqEo/uHAArYhNQkWjovswMYosIqElse/yaCcRmFkiTuDd7LhuILSzgLvHoSwMriM0LtO3w hzZmiAUuEndu/GCHiAtKnJz5hAWiV0vixr+XQHM4gGxpieX/wA7lFHCVuDf3Bth4UQFlib19 h9gnMArMQtI9C0n3LITuBYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3RN9XIzS/RSU0o3MYIC mN1FaQfjxH9ehxgFOBiVeHg7lk2JEmJNLCuuzD3EKMnBpCTKy74GKMSXlJ9SmZFYnBFfVJqT WnyIUYKDWUmEd+XiyVFCvCmJlVWpRfkwKWkOFiVxXg8T7SghgfTEktTs1NSC1CKYrAwHh5IE 74tLQEMFi1LTUyvSMnNKENJMHJwgw3mAhjOC1PAWFyTmFmemQ+RPMepy3Hjxuo1ZiCUvPy9V Spy34jJQkQBIUUZpHtwcUOKRyN5f84pRHOgtYV4LkCoeYNKCm/QKaAkT0BL3/xNAlpQkIqSk GhiV/Ftf5QvqCTSkzLqyd7eO/wYZl+wVUbJXw5LYpoowt294VuLUF6t+RXTRTAWps2v4JOKs Pt3qXPNIxkxZ/Z3VY8vmuGdH3LYb5O6JSZHP779343S4kMyW4pmtS1KPR5zpa9+nfElbJEe8 JJZt9c6JwmY2BhtZQtycr/QFJokVPBeebKEppcRSnJFoqMVcVJwIAIY2v9gXAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/aQUkAxehqq9L7EDzdw2vzi9zqKc>
Subject: Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 03:45:01 -0000

On Mon, Feb 26, 2018 at 11:03:07AM -0800, Dan Romascanu wrote:
> 
> 1. CWT is derived from JWT (RFC 7519) using CBOR rather than JSON for encoding.
> The rationale as explained in the document is related to efficiency for some
> IoT systems. The initial claims registry defined in Section 9.1 is identical
> (semantically) with the initial claims registry defined in Section 10.1 of RFC
> 7519. Is this parallelism supposed to continue? If the two registries will
> continue to evolve in parallel, maybe there should be a mechanism at IANA to
> make this happen. Was this discussed by the WG? Maybe there is a need to
> include some text about the relationship between the two registries.

The shepherd writeup includes a note to the IESG recommending that
there be overlap between the experts for the CWT and JWT registries:

  Since near-total overlap is expected between the CWT and JWT
  registry contents, overlap in the corresponding pools of Experts
  would be useful, to help ensure that the appropriate amount of
  overlap between the registries is maintained.

So I expect that the right thing will happen in practice, though
you're probably right that having some text in the document itself
(and the registry template as well) would be a good safety net.

-Benjamin