Re: [stir] Alexey Melnikov's Discuss on draft-ietf-stir-certificates-11: (with DISCUSS and COMMENT)

["Peterson, Jon" <[e-mail]>]

>> 
>> >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)."

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.