Hi William,

that was the idea.

Ciao
Hannes

From: OAuth [mailto:[email protected]] On Behalf Of William Denniss
Sent: 19 July 2018 16:32
To: Mike Jones
Cc: oauth
Subject: Re: [OAUTH-WG] Call for adoption for "Resource Indicators for OAuth 
2.0"

Question: if this is adopted along with 
https://datatracker.ietf.org/doc/draft-hardt-oauth-distributed/, is the plan 
for this spec to be the authoritative definition, and Distributed OAuth to take 
a reference instead of redefining?

On Thu, Jul 19, 2018 at 1:29 PM, Mike Jones 
<[email protected]<mailto:[email protected]>>
 wrote:
I support adoption.  The “resource” request parameter that it defines is 
already widely used.

                                                       -- Mike

From: OAuth <[email protected]<mailto:[email protected]>> On Behalf 
Of Rifaat Shekh-Yusef
Sent: Thursday, July 19, 2018 4:02 PM
To: oauth <[email protected]<mailto:[email protected]>>
Subject: [OAUTH-WG] Call for adoption for "Resource Indicators for OAuth 2.0"

Hi all,

This is the call for adoption of the 'Resource Indicators for OAuth 2.0' 
document
following the positive call for adoption at the Montreal IETF meeting.

Here is the document:
https://tools.ietf.org/html/draft-campbell-oauth-resource-indicators-02

Please let us know by August 2nd whether you accept / object to the
adoption of this document as a starting point for work in the OAuth
working group.

Regards,
Rifaat

_______________________________________________
OAuth mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/oauth

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to