Re: [Jwt-reg-review] Claims registration question

You can use public collision resistant names like http://genomicsandhealth.org/claims/value1 That also allows for the claim to be documented via the follow your nose principal.
https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.2

You could use that and then register them if there is a need for interoperability outside your community. 

If you established that pattern, it would be unlikely that anyone other than the owner of that namespace is going to register something in the registry that conflicts with you.

John B.
> On Apr 22, 2015, at 7:14 PM, Bart Grantham <bart@genecloud.com> wrote:
> 
> A standards body that my company is involved in, the Global Alliance for Genomic Health (“GA4GH”), is looking at OAuth2/OpenID Connect for identity management amongst the various projects and it occurs to us that it may be necessary for the GA4GH to register domain-specific claims regarding researcher’s qualifications/membership in organizations.
> 
> I’m wondering if it’s possible for the GA4GH to claim, after appropriate discussion and review, a wildcard claim?  Something like org.genomicsandhealth.* ?  This would allow the GA4GH to internally manage the registration of claims that that are relavant to the organization (“org.genomicsandhealth.projects.beacon”, “org.genomicsandhealth.eu_commons”, etc.)
> 
> If this is not possible, is there an alternative to registering each and every claim name that arises with IANA?
> 
> --
> Bart Grantham
> _______________________________________________
> Jwt-reg-review mailing list
> Jwt-reg-review@ietf.org
> https://www.ietf.org/mailman/listinfo/jwt-reg-review