[Jwt-reg-review] Claims registration question

Bart Grantham <bart@genecloud.com> Wed, 22 April 2015 22:14 UTC

Return-Path: <bart@genecloud.com>
X-Original-To: jwt-reg-review@ietfa.amsl.com
Delivered-To: jwt-reg-review@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8A51B2BFF for <jwt-reg-review@ietfa.amsl.com>; Wed, 22 Apr 2015 15:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_22=0.6] autolearn=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 WLTTqRI1rjM3 for <jwt-reg-review@ietfa.amsl.com>; Wed, 22 Apr 2015 15:14:18 -0700 (PDT)
Received: from smtp.intertrust.com (smtp.intertrust.com [12.107.176.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C19061B2B8C for <jwt-reg-review@ietf.org>; Wed, 22 Apr 2015 15:14:18 -0700 (PDT)
Received: from exch-1.corp.intertrust.com ([::1]) by exch-1.corp.intertrust.com ([::1]) with mapi id 14.02.0387.000; Wed, 22 Apr 2015 15:14:18 -0700
From: Bart Grantham <bart@genecloud.com>
To: "jwt-reg-review@ietf.org" <jwt-reg-review@ietf.org>
Thread-Topic: Claims registration question
Thread-Index: AQHQfUms45dD1eut60CXD6+WfoHcQg==
Date: Wed, 22 Apr 2015 22:14:17 +0000
Message-ID: <etPan.55381d39.643c9869.158@Macintosh-5.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.250.106]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5D5E4DAE553301499560560BE53B1B0A@corp.intertrust.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/jwt-reg-review/FZiQsiTWupq5tJ_-oHwdmugFw9s>
X-Mailman-Approved-At: Thu, 23 Apr 2015 08:42:52 -0700
Subject: [Jwt-reg-review] Claims registration question
X-BeenThere: jwt-reg-review@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Expert review of proposed IANA registrations for JSON Web Token \(JWT\) claims." <jwt-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jwt-reg-review/>
List-Post: <mailto:jwt-reg-review@ietf.org>
List-Help: <mailto:jwt-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 22:15:39 -0000

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