Re: [OAUTH-WG] Additional Oauth Dynamic Client Registration Protocol Information

[Justin Richer <[e-mail]>]

Additionally, there is an individual draft that registers LRDD Link 
Types for discovery using LRDD and HostMeta:

http://tools.ietf.org/html/draft-wmills-oauth-lrdd-07

  -- Justin

On 02/20/2013 02:37 PM, Mike Jones wrote:
>
> Hi Don,
>
> Discovery is a process that happens before Registration, and that's 
> the point at which you would return the AS (and registration!) 
> endpoints to the Client.  The OAuth WG considered doing its own 
> discovery work but ultimately decided to have that happen in the Apps 
> Area WG instead, which is close to completing the WebFinger discovery 
> specification.
>
> If you want to see how OpenID Connect is performing discovery using 
> WebFinger, including discovery of the AS endpoint, have a look at 
> http://openid.net/specs/openid-connect-discovery-1_0.html.
>
> Best wishes,
>
> -- Mike
>
> *From:*[e-mail] [mailto:[e-mail]] *On 
> Behalf Of *Donald F Coffin
> *Sent:* Wednesday, February 20, 2013 11:30 AM
> *To:* Justin Richer
> *Cc:* [e-mail]
> *Subject:* [OAUTH-WG] Additional Oauth Dynamic Client Registration 
> Protocol Information
>
> Justin,
>
> I understand the current Client Registration request and response 
> information is based on the OPENID model for consistency, but has 
> there been any thought or discussion of adding the AS OAuth 2.0 
> endpoint URIs as part of the registration response?  I believe the 
> addition of the endpoint URIs would make the dynamic client 
> registration process truly a dynamic feature of OAuth 2.0.
>
> If the ability to discover the AS OAuth 2.0 endpoint URIs is being 
> covered by another IETF draft, I'd appreciate learning which current 
> draft is being worked on to achieve that result.
>
> Best regards,
>
> Don
>
> Donald F. Coffin
>
> Founder/CTO
>
> REMI Networks
>
> 22751 El Prado Suite 6216
>
> Rancho Santa Margarita, CA  92688-3836
>
> Phone: [phone]
>
> Email: [e-mail] 
> <mailto:[e-mail]>
>