Re: [stir] Alexey Melnikov's Discuss on draft-ietf-stir-certificates-11: (with DISCUSS and COMMENT)
Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 03 November 2016 14:06 UTC
Return-Path: <aamelnikov@fastmail.fm>
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 C7483129A52; Thu, 3 Nov 2016 07:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=aaq6pahj; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=kZRhwzZY
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 dSzxEV7kkpO2; Thu, 3 Nov 2016 07:06:26 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D7D5129A20; Thu, 3 Nov 2016 07:06:17 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0B3D220707; Thu, 3 Nov 2016 10:06:17 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute1.internal (MEProxy); Thu, 03 Nov 2016 10:06:17 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=JeFiO0fz5817jvBJqT3NAQArMV 8=; b=aaq6pahjoRnnu0OS0qBZfk4vrwmP+osDNklpw/KFWyk2q4K4BfJ/pLqG7C J/R08QQZJu/yP+FNkpfZDBlfxjCoCX1wFaUhQD11zgbprd8+/xe40xzghzELTokS BeaEx8DzpyngCgB2UFEirQETOdHNt3jx/WPjl1bXaCb+arFco=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=Je FiO0fz5817jvBJqT3NAQArMV8=; b=kZRhwzZY9M98rBGNzYODmaCgJDC8FELRX9 MyDXQZHb2Nv0h4U0/RvFLmTsNgEIJ+lDKMnRdUEQQC20KKAaewOcHvOxcI5H/dW0 kmyN9jKF9KJg6d60iAdhilipFwL8qGvKGpgWxv0uXil2/nBChZE4Y5uECjFfgnxX CDzNZrlq4=
X-ME-Sender: <xms:WEQbWOoEYox7WtQsHnV7qLRiLa-yBW1eQcXiPMPhgiRl8T9zV0Uq3g>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id CF2835A679; Thu, 3 Nov 2016 10:06:16 -0400 (EDT)
Message-Id: <1478181976.498603.776283929.7563270E@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "Peterson, Jon" <jon.peterson@neustar.biz>, Alissa Cooper <alissa@cooperw.in>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-8f4ad78c
In-Reply-To: <D440B612.1C1FFA%jon.peterson@neustar.biz>
Date: Thu, 03 Nov 2016 14:06:16 +0000
References: <147800730286.23932.1515952198717955239.idtracker@ietfa.amsl.com> <BE53511C-3C37-4C94-8C01-681EB413C670@sn3rd.com> <1478101725.216255.775166569.1BD2E379@webmail.messagingengine.com> <58F5F6BD-02E0-4DC9-8A69-D918AB5A4B65@vigilsec.com> <26856EBB-3272-4D70-A60E-2714E8B1FB15@cooperw.in> <1478114264.260284.775416225.782F8598@webmail.messagingengine.com> <D440AC6C.1C1F3D%jon.peterson@neustar.biz> <1478180233.490936.776249657.710E2360@webmail.messagingengine.com> <D440B612.1C1FFA%jon.peterson@neustar.biz>
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/JMvNyVfdjkK5Xl7oueQ9DsvBO1E>
Cc: Russ Housley <housley@vigilsec.com>, IETF STIR Mail List <stir@ietf.org>, IESG <iesg@ietf.org>, draft-ietf-stir-certificates@ietf.org, stir-chairs@ietf.org, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [stir] Alexey Melnikov's Discuss on draft-ietf-stir-certificates-11: (with DISCUSS and COMMENT)
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Nov 2016 14:06:34 -0000
On Thu, Nov 3, 2016, at 01:46 PM, Peterson, Jon wrote: > > >> > >> >Are claim tokens likely to be allocated by IANA? > >> > >> ... PASSporT simply reuses the IANA allocation method of JWT, so yes, > >>the > >> claims are allocated by IANA. This is the registry. > > > >I think this document should say so. > > I mean, the thing in stir-certs is called "JWT Claim Constraints". I > think > it would be clear that to figure out how you register claims, you look at > JWT. The section also refers you to PASSporT, which pretty quickly drops > you back to JWT, like stir-passport Section 8.3: > > "Specifying new claims follows the baseline JWT procedures ([RFC7519] > Section 10.1)." Please stick the relevant reference in Section 8 of this draft, this was not clear to me, especially as I read this document first. > > Do you just want us to put another copy of that sentence in stir-certs? > > > > >> http://www.iana.org/assignments/jwt/jwt.xhtml > >> > >> > >> To your more recent question, "I was also wondering if any of these > >>value > >> can possible contain non ASCII Unicode characters, and if they do, how > >> can > >> they be encoded as IA5String." If the question is "can possibly" then > >>I'm > >> not sure JWS/JWT specifically bars it (someone likely knows better than > >> me, this may just devolve back to how JSON member strings are defined). > >> However, I don't think any of the existing or planned registered values > >> fall outside of ASCII ranges. I don't think I'd lose much sleep over it, > >> given what the review processes are like and what the likely constraints > >> are CAs would want to apply. > > > >I would just add a warning about possibility to alert future readers and > >Expert Reviewers. > > Makes sense, we can do that - though again I might ask the reviewers (Jim > Schaad etc) whether their reading of the existing procedures wouldn't > make > that warning redundant. > > Jon Peterson > Neustar, Inc. >
- [stir] Alexey Melnikov's Discuss on draft-ietf-st… Alexey Melnikov
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Sean Turner
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Russ Housley
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alissa Cooper
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Dave Crocker
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Peterson, Jon
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Peterson, Jon
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Peterson, Jon
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Alissa Cooper
- Re: [stir] Alexey Melnikov's Discuss on draft-iet… Dave Crocker