![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This draft is the original community specification created outside the IETF. It was this work that inspired the creation of the OAUTH WG and is explicitly set as the initial draft for the WG in its charter. The draft is submitted as an informational RFC to document existing deployment and practices. It is not a WG product. EHL > -----Original Message----- > From: ietf-bounces at ietf.org [mailto:ietf-bounces at ietf.org] On Behalf Of > Cullen Jennings > Sent: Tuesday, October 27, 2009 7:12 AM > To: IESG IESG > Cc: IETF Discussion > Subject: Re: Last Call: draft-hammer-oauth (The OAuth Core 1.0 > Protocol) to Informational RFC > > > I'm very confused about the relationship of this draft and the work > the OAUTH WG is doing. Can you explain? > > > On Oct 9, 2009, at 15:38 , The IESG wrote: > > > The IESG has received a request from an individual submitter to > > consider > > the following document: > > > > - 'The OAuth Core 1.0 Protocol ' > > <draft-hammer-oauth-03.txt> as an Informational RFC > > > > The IESG plans to make a decision in the next few weeks, and solicits > > final comments on this action. Please send substantive comments to > > the > > ietf at ietf.org mailing lists by 2009-11-06. Exceptionally, > > comments may be sent to iesg at ietf.org instead. In either case, please > > retain the beginning of the Subject line to allow automated sorting. > > > > The file can be obtained via > > http://www.ietf.org/internet-drafts/draft-hammer-oauth-03.txt > > > > > > IESG discussion can be tracked via > > > https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag > =17736&rfc_flag=0 > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce at ietf.org > > https://www.ietf.org/mailman/listinfo/ietf-announce > > _______________________________________________ > Ietf mailing list > Ietf at ietf.org > https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.