IETF Logo Mail Archive

Re: [stir] WG Last Call Comments: draft-ietf-stir-passport-divert-05

Russ Housley <housley@vigilsec.com> Tue, 16 April 2019 18:58 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 649F31203CA for <stir@ietfa.amsl.com>; Tue, 16 Apr 2019 11:58:27 -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] 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 N5q_WGr6T7LR for <stir@ietfa.amsl.com>; Tue, 16 Apr 2019 11:58:25 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BFA41203A1 for <stir@ietf.org>; Tue, 16 Apr 2019 11:58:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 30E93300A99 for <stir@ietf.org>; Tue, 16 Apr 2019 14:40:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nfguflRjSRDR for <stir@ietf.org>; Tue, 16 Apr 2019 14:40:05 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id DAD91300201; Tue, 16 Apr 2019 14:40:05 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <A4512AD5-F52A-4AA2-B7F5-11BFE2AEC6F2@team.neustar>
Date: Tue, 16 Apr 2019 14:58:23 -0400
Cc: IETF STIR Mail List <stir@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <90E14B2C-05AA-46EF-8906-9692217FCBE9@vigilsec.com>
References: <3162DDF4-CB71-41F8-983B-8572D33B460B@vigilsec.com> <23FC946B-A5BC-4DAC-A281-9DB202C1DC93@team.neustar> <060587D1-11D4-45D0-8605-0B11D38415ED@vigilsec.com> <A4512AD5-F52A-4AA2-B7F5-11BFE2AEC6F2@team.neustar>
To: "Peterson, Jon" <jon.peterson@team.neustar>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/VMptu_nmK6jTtVObGdrPiP4zeIE>
Subject: Re: [stir] WG Last Call Comments: draft-ietf-stir-passport-divert-05
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2019 18:58:27 -0000

Jon:

> <Russ> My reading of RFC 8225 is that the payload is composed of a collection of claims.  Some of the claims are defined in the JWT specifications, and other are defined specifically for PASSporT.  In the document, it is not clear to me whether a "claim object" is one of the claims in this collection or the whole collection.  If the term payload was used for the whole collection, I think it would be more consistent and clear.</Russ>
> 
> I agree that we don't want that ambiguity about whether the "claims object" refers to a single claim or the set of claims. I guess I am a little hesitant to require that we use the JWS term "payload" for this, though, because looking through the RFCs JWT seems to favor the term "claims set". I don't want to get too pedantic about this, but maybe I can remove "claims object" in favor of using either "payload" or "claims set" where their semantics seems to fit?

That would totally resolve my concern.

Russ

v2.23.0 | Report a Bug | By Email