Re: [stir] Proposed JWT Constraints Syntax

Russ Housley <housley@vigilsec.com> Thu, 30 March 2017 15:18 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 A18D81296AF for <stir@ietfa.amsl.com>; Thu, 30 Mar 2017 08:18:23 -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] 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 NF6fvjvYyUBo for <stir@ietfa.amsl.com>; Thu, 30 Mar 2017 08:18:22 -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 4E6D1127419 for <stir@ietf.org>; Thu, 30 Mar 2017 08:18:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B2D88300433 for <stir@ietf.org>; Thu, 30 Mar 2017 11:18:21 -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 pGYZaMICT-QU for <stir@ietf.org>; Thu, 30 Mar 2017 11:18:21 -0400 (EDT)
Received: from dhcp-8696.meeting.ietf.org (dhcp-8696.meeting.ietf.org [31.133.134.150]) by mail.smeinc.net (Postfix) with ESMTPSA id E43E130022B for <stir@ietf.org>; Thu, 30 Mar 2017 11:18:20 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Thu, 30 Mar 2017 11:18:20 -0400
References: <3EA11324-E4D2-4AB2-A6AA-F0FD83B58394@vigilsec.com>
To: IETF STIR Mail List <stir@ietf.org>
In-Reply-To: <3EA11324-E4D2-4AB2-A6AA-F0FD83B58394@vigilsec.com>
Message-Id: <A13F3663-63F2-4795-A547-9079D5C5BD3A@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/BvYQeCvBUt3qu3BK7rPoxk1XwIc>
Subject: Re: [stir] Proposed JWT Constraints Syntax
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 30 Mar 2017 15:18:24 -0000

Based on the discussion in the room, the claim values should allow UTF8String, not just IA5String.

That change would result in:


JWTClaimConstraints ::= SEQUENCE {
  mustInclude [0] JWTClaimNames OPTIONAL,
     -- The listed claim names MUST appear in the PASSporT in addition to iat, orig, dest
     -- If absent, iat, orig, dest MUST appear in the PASSporT
  permittedValues [1] JWTClaimPermittedValuesList OPTIONAL }
     -- If the claim name is present, the claim MUST contain one of the listed values
   ( WITH COMPONENTS { ..., mustInclude PRESENT }
  | WITH COMPONENTS { ..., permittedValues PRESENT } )

JWTClaimPermittedValuesList SEQUENCE SIZE (1..MAX) OF JWTClaimPermittedValues
JWTClaimPermittedValues ::= SEQUENCE {
   claim  JWTClaimName,
   permitted  SEQUENCE SIZE (1..MAX) OF UTF8String }

JWTClaimNames ::= SEQUENCE SIZE (1..MAX) OF JWTClaimName
JWTClaimName ::= IA5String