Re: [oauth-ext-review] Request to register OAuth Authorization Server Metadata: claims_interaction_endpoint, uma_profiles_supported, permission_endpoint, resource_registration_endpoint

Eve Maler <eve.maler@forgerock.com> Wed, 28 June 2017 22:46 UTC

Return-Path: <eve.maler@forgerock.com>
X-Original-To: oauth-ext-review@ietfa.amsl.com
Delivered-To: oauth-ext-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1B812EC82 for <oauth-ext-review@ietfa.amsl.com>; Wed, 28 Jun 2017 15:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forgerock.com
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 cjjZbR7dVvjH for <oauth-ext-review@ietfa.amsl.com>; Wed, 28 Jun 2017 15:46:51 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 155C612EC81 for <oauth-ext-review@ietf.org>; Wed, 28 Jun 2017 15:46:51 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id p66so53384967oia.0 for <oauth-ext-review@ietf.org>; Wed, 28 Jun 2017 15:46:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forgerock.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n1P2jeRsBm/w3WW2A14SMi/89aHLp6zf3k2Ge8CFnwQ=; b=kMxkJcLZGTMvA3YeDQcqgE03pmr4Y+mlXFlL10dYbSvI1iqHY7rsMhzqAVymjFsUfx r7OxxpHVlB06o8abNdAPuCowGMZae2b6wL9Sq2r9CT7CTqFNqTRc5gRgF5Dz09PRgVH4 sNtvPrdD2S1kqo74trX4dpq22OAkYZOd9TigM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n1P2jeRsBm/w3WW2A14SMi/89aHLp6zf3k2Ge8CFnwQ=; b=pgJtluJNbW4dROuCEXKaKm2wtvcVveZZCgvScd7VZWyfd8Qe1iBv8hT0XfPMHJHQ4s dHTYeYDQ05z4p6xlO3eDmvizMI9BcZsL1qPSngp4dKFk+rN/fACjGw2Alt+t0GRtqHje 3KCyDwhXyo9ODAY3ZxoEO5sGJY3gm9xI91EvXuxLjud1du6Ngm4A3zbcP29UaMXfVlim Q/0z4tAxd+Dbp7mb7RZYJp99MPIPQC3Z8/T5q0bnFRrufjjePEAQSti5ENQRnHwJNS14 gmlgX/XE7XSozbar4axgN2AsY+r30FvKs/Avt2vY2+lwxiEyWwD0pegBPkt6P4xBBozW j0zA==
X-Gm-Message-State: AKS2vOzPGvykiGxq1vArSxLDpdKEw4TiRm3lOz8d9tWXvYdOFl/vEiyZ gORbAGe1y8k5XhQkUqxzIhQxa78TBXkH
X-Received: by 10.202.232.135 with SMTP id f129mr7942457oih.157.1498690010446; Wed, 28 Jun 2017 15:46:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.106.9 with HTTP; Wed, 28 Jun 2017 15:46:34 -0700 (PDT)
In-Reply-To: <CY4PR21MB0504106E9DA09715B4400652F5DD0@CY4PR21MB0504.namprd21.prod.outlook.com>
References: <CAMPbGmguVObYrbV5urxQV=tVFg1srfo3G8m1sQqDF1r+1XXuUg@mail.gmail.com> <CY4PR21MB0504106E9DA09715B4400652F5DD0@CY4PR21MB0504.namprd21.prod.outlook.com>
From: Eve Maler <eve.maler@forgerock.com>
Date: Wed, 28 Jun 2017 15:46:34 -0700
Message-ID: <CAMPbGmio0qMnnwD3Uagm3PA4FbGisdQF6WRiZKb5dt=j0H9zvQ@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: "oauth-ext-review@ietf.org" <oauth-ext-review@ietf.org>, Maciej Machulak <maciej.machulak@gmail.com>, Justin Richer <justin@bspk.io>
Content-Type: multipart/alternative; boundary="001a11407fc0b3908205530cf5e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/rQeiaU1DhMLCcIJgDt4RlDcJJaQ>
Subject: Re: [oauth-ext-review] Request to register OAuth Authorization Server Metadata: claims_interaction_endpoint, uma_profiles_supported, permission_endpoint, resource_registration_endpoint
X-BeenThere: oauth-ext-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Review of proposed IANA registrations for OAuth." <oauth-ext-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth-ext-review/>
List-Post: <mailto:oauth-ext-review@ietf.org>
List-Help: <mailto:oauth-ext-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jun 2017 22:46:54 -0000

Righto. :-) Should we keep this IANA request subsection in the spec, do you
think, and change it over into a note about it being a forward/future
reference?


*Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

On Wed, Jun 28, 2017 at 3:25 PM, Mike Jones <Michael.Jones@microsoft.com>
wrote:

> As I mentioned to you in person, Eve, this registry won’t exist until
> draft-ietf-oauth-discovery is an RFC.  Hopefully this will happen within a
> few months, at which point, your registration request can be considered.
>
>
>
>                                                                 Best
> wishes,
>
>                                                                 -- Mike
>
>
>
> *From:* oauth-ext-review [mailto:oauth-ext-review-bounces@ietf.org] *On
> Behalf Of *Eve Maler
> *Sent:* Friday, June 16, 2017 5:41 PM
> *To:* oauth-ext-review@ietf.org
> *Cc:* Maciej Machulak <maciej.machulak@gmail.com>; Justin Richer <
> justin@bspk.io>
> *Subject:* [oauth-ext-review] Request to register OAuth Authorization
> Server Metadata: claims_interaction_endpoint, uma_profiles_supported,
> permission_endpoint, resource_registration_endpoint
>
>
>
> As required by draft-ietf-oauth-discovery (currently at 06) Section 7, the
> authors of the specifications User-Managed Access (UMA) 2.0 Grant for
> OAuth 2.0 Authorization
> <https://docs.kantarainitiative.org/uma/wg/oauth-uma-grant-2.0-05.html> and
> Federated Authorization for User-Managed Access (UMA) 2.0
> <https://docs.kantarainitiative.org/uma/wg/oauth-uma-federated-authz-2.0-05.html> are
> requesting to register the following four items of OAuth Authorization
> Server Metadata:
>
>    - For the UMA Grant spec (metadata definitions appear in Section 2
>    <https://docs.kantarainitiative.org/uma/wg/oauth-uma-grant-2.0-05.html#as-config>;
>    IANA request appears in Section 7.2
>    <https://docs.kantarainitiative.org/uma/wg/oauth-uma-grant-2.0-05.html#rfc.section.7.2>
>    ):
>
>
>    - claims_interaction_endpoint
>       - uma_profiles_supported
>
>
>    - For the UMA Federated Authorization spec (metadata definitions
>    appear in Section 2
>    <https://docs.kantarainitiative.org/uma/wg/oauth-uma-federated-authz-2.0-05.html#as-config>;
>    IANA request appears in Section 9.1
>    <https://docs.kantarainitiative.org/uma/wg/oauth-uma-federated-authz-2.0-05.html#rfc.section.9.1>
>    ):
>
>
>    - permission_endpoint
>       - resource_registration_endpoint
>
> Thank you. We look forward to your response.
>
>
> *Eve Maler *ForgeRock Office of the CTO | VP Innovation & Emerging
> Technology
> Cell +1 425.345.6756 <(425)%20345-6756> | Skype: xmlgrrl | Twitter:
> @xmlgrrl
>