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

2013-02-20 Thread Donald F Coffin
ks.com From: Justin Richer [mailto:jric...@mitre.org] Sent: Wednesday, February 20, 2013 11:50 AM To: Mike Jones Cc: Donald F Coffin; oauth@ietf.org Subject: Re: [OAUTH-WG] Additional Oauth Dynamic Client Registration Protocol Information Additionally, there is an individual draft that reg

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

2013-02-20 Thread Donald F Coffin
ks.com From: Mike Jones [mailto:michael.jo...@microsoft.com] Sent: Wednesday, February 20, 2013 11:38 AM To: Donald F Coffin; Justin Richer Cc: oauth@ietf.org Subject: RE: [OAUTH-WG] Additional Oauth Dynamic Client Registration Protocol Information Hi Don, Discovery is a process that h

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

2013-02-20 Thread Justin Richer
onald F Coffin *Sent:* Wednesday, February 20, 2013 11:30 AM *To:* Justin Richer *Cc:* oauth@ietf.org *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 O

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

2013-02-20 Thread Mike Jones
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

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

2013-02-20 Thread Donald F Coffin
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