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

[Alexey Melnikov <[e-mail]>]

On Thu, Nov 3, 2016, at 01:12 PM, Peterson, Jon wrote:
> 
> >A followup question: what is the syntax of claim name? (I understand
> >that IA5String provides a restriction, but I am wondering if many people
> >outside of Security area actually know what these restrictions are).
> 
> PASSporT claim names are simply JWT claim names (per stir-passport
> Section
> 5), and...
> 
> >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.

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