[Jwt-reg-review] review JWT claims registration request (was Re: Fwd: Review requested: draft-ietf-stir-passport)

Brian Campbell <bcampbell@pingidentity.com> Wed, 19 October 2016 17:14 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jwt-reg-review@ietfa.amsl.com
Delivered-To: jwt-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A12F1296AA for <jwt-reg-review@ietfa.amsl.com>; Wed, 19 Oct 2016 10:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.com
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 mjxL7eaFzAXI for <jwt-reg-review@ietfa.amsl.com>; Wed, 19 Oct 2016 10:14:38 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F17B612969C for <jwt-reg-review@ietf.org>; Wed, 19 Oct 2016 10:14:37 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id 66so34672479itl.1 for <jwt-reg-review@ietf.org>; Wed, 19 Oct 2016 10:14:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:from:date:message-id:subject:to:cc; bh=YE+xbvUZwWXuJD4anpo2rFZ3RITfoSE90bpfqDh/wZE=; b=B0JxJmIEvfclTS3BdXEkR3Aw+vdBfH2ry2g9p/lm9DPsFoEV4YqgSHgTzgjP72z0wO 3vGpaczJ6w63nehFQ0muH4Xq/TXFEuQ+HE0BPY1CWvfZYnx7DSrhNkme1AUId0uuY05p zBdwKl/tgZi8bQbkWcYNR2UlPiHLS9O+Nz+YE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=YE+xbvUZwWXuJD4anpo2rFZ3RITfoSE90bpfqDh/wZE=; b=lI2W6GfdTHmj4buX/28UwcqfLclIxDNEq/VFpe0PXcW0fAmHb8+BSB3Fc5ils8Mg75 1h7DA7sn2p/iugwO5+6DYYLityTR322oACEsgfkLYRdJPXRSmtXqxFJEzKX3O9jNzN6W c99TgcW37MY0A/hM9aUPd55XPmoTUTfN/W4vUey7FZD5UHKk7mx4RXGMdhZt6J7X9keG A8P207uMoG5SLkh460SjHozJZveASAQU8RqNQ0z4RkOy5eJJN8uP6s6fGsVrN3FZmt6p jCX7kglatx2rn9x0IEjovdQzK4OlIlm9cJ7oMi56/EwkDEo/N+G5N9Exe6kyVjlidwZa dxwA==
X-Gm-Message-State: AA6/9Rm4GBKeNxVK5mGpkzM8PRz8RVO7O4arKQWFl1fo/MJEVYhFPkZVptjg9bLbw5QGQ9JD4Sx+2C7F/hGMvWlV
X-Received: by 10.36.121.131 with SMTP id z125mr4020297itc.79.1476897277250; Wed, 19 Oct 2016 10:14:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.5.148 with HTTP; Wed, 19 Oct 2016 10:14:06 -0700 (PDT)
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 19 Oct 2016 11:14:06 -0600
Message-ID: <CA+k3eCSV=pjEWrdUoHsZcozLzzZjvkY6Z=06fZZwQEcEu3Aq8Q@mail.gmail.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, jwt-reg-review@ietf.org, John Bradley <ve7jtb@ve7jtb.com>, Mike Jones <Michael.Jones@microsoft.com>, Chuck Mortimore <cmortimore@salesforce.com>
Content-Type: multipart/alternative; boundary="001a114abbd294c62b053f3af167"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jwt-reg-review/N4LqPl6_P7KF9Sx_c8FQhBCgJ7w>
Cc: Russ Housley <housley@vigilsec.com>, Alissa Cooper <alissa@cooperw.in>, Sean Turner <sean@sn3rd.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: [Jwt-reg-review] review JWT claims registration request (was Re: Fwd: Review requested: draft-ietf-stir-passport)
X-BeenThere: jwt-reg-review@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Expert review of proposed IANA registrations for JSON Web Token \(JWT\) claims." <jwt-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jwt-reg-review/>
List-Post: <mailto:jwt-reg-review@ietf.org>
List-Help: <mailto:jwt-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 17:14:40 -0000

Thanks for bringing this to my attention, Matt. The message to
jwt-reg-review had somehow gotten lumped together with the jose-reg-review
one in such a way that'd I'd completely overlooked it. I don't know if
maybe the same happened to the other 'experts' so I'm including them and
the jwt-reg-review address again in this message.

Generally I think the draft-ietf-stir-passport claims registrations look
okay. A few comments follow. It'd be a nice courtesy to maybe space and
group section 11.2.1 like was done in
https://tools.ietf.org/html/rfc7519#section-10.1.2 but that's just a nit. I
can't help but see the similarity of "orig"/"dest" to "sub"/"aud" and
wonder if more couldn't have been done to reuse the existing claims. But
having the specific syntax and semantics for PASSporT is understandably
nice too. If it were up to me, I'd use base64url encoding rather than hex
for mky/dig as it is more space efficient and generally in line with how
JWT/JOSE does things but that's just me. You can take or leave those
comments though at your choosing.

Hopefully the other reviewers will see this message and we can move things
forward.







On Wed, Oct 19, 2016 at 6:33 AM, Matt Miller (mamille2) <mamille2@cisco.com>
wrote:

> Hello Brian,
>
> Do you think you can review this JWT registration?
>
> Thanks,
>
> - m&m
> Matt Miller (mobile)
>
> On Oct 18, 2016 1:25 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>
> Hi Matt -
>
> Who should pick this one up? (Jim is taking care of the part that went to
> jose-reg-review).
>
> We're up against some strong external pressure to get this document suite
> published, so any nudging to bring this particular review to conclusion
> would be very helpful.
>
> RjS
>
>
> -------- Forwarded Message --------
> Subject: Review requested: draft-ietf-stir-passport
> Date: Tue, 18 Oct 2016 13:56:37 -0500
> From: Robert Sparks <rjsparks@nostrum.com> <rjsparks@nostrum.com>
> To: jwt-reg-review@ietf.org
> CC: Jon Peterson <jon.peterson@gmail.com> <jon.peterson@gmail.com>,
> chris_wendt@cable.comcast.com <chris_wendt@cable.comcast.com>
> <chris_wendt@cable.comcast.com>, Russ Housley <housley@vigilsec.com>
> <housley@vigilsec.com>, Alissa Cooper <alissa@cooperw.in>
> <alissa@cooperw.in>
>
> Please review the registration request in section 11.2 of
>
> <https://datatracker.ietf.org/doc/draft-ietf-stir-passport/>
> <https://datatracker.ietf.org/doc/draft-ietf-stir-passport/>
>
> The registration request itself is copied below for your convenience.
>
> Robert Sparks - STIR WG co-chair
>
> -----------
>
> 11.2.  JSON Web Token Claims Registration
>
> 11.2.1.  Registry Contents Additions Requested
>
>    o  Claim Name: "orig"
>
>    o  Claim Description: Originating Identity String
>
>    o  Change Controller: IESG
>
>    o  Specification Document(s): Section 5.2.1 of [RFCThis]
>
>    o  Claim Name: "dest"
>
>    o  Claim Description: Destination Identity String
>
>    o  Change Controller: IESG
>
>    o  Specification Document(s): Section 5.2.1 of [RFCThis]
>
>    o  Claim Name: "mky"
>
>    o  Claim Description: Media Key Fingerprint String
>
>    o  Change Controller: IESG
>
>    o  Specification Document(s): Section 5.2.2 of [RFCThis]
>
>
>
>