Actually, I am NOT an author of use cases; I am just a proponent of
this work. The decision of whether and when to move to publishing
belongs to the authors: George, Torsten, and Zachary.
Of course, if the authors choose to do so, the draft can go to the RFC
Editor as an Independent (or AD-sponsored) submission, but I see two
drawbacks here: 1) This would break the connection of the use cases to
the protocol work and thus counter their/* *//*raison d'être*/ and 2)
this may take very, very long. (As a former WG chair and an author of a
few RFCs, one of which was AD-sponsored and another Independent, I have
learned all of this the hard way...)
This is why my inclination has been, and still is, toward Eran's second
option.
Igor
Eran Hammer-Lahav wrote:
I don't see why we can't just publish this document as an informational RFC
now. I sure hope we are not going to accommodate any new use cases...
Also, since this is not a normative document, the WG value here is minimal. I
think Igor can move forward with publishing this as an individual submission,
but will also be supportive of making it a working group item and quickly
moving to final WG LC and off to the IESG.
EHL
-----Original Message-----
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
Of Igor Faynberg
Sent: Monday, May 09, 2011 12:18 PM
To: Barry Leiba
Cc: oauth@ietf.org; oauth-...@tools.ietf.org
Subject: Re: [OAUTH-WG] Revised Charter
Barry,
I agree. Indeed, after ascertaining that the next rechartering is scheduled for
October, I personally see no problem with deferring the use cases. (I thought
that the current rechartering was already post-2.0, which is what had
confused me.)
With thanks for thorough follow-ups,
Igor
Barry Leiba wrote:
...
Igor, on the use cases: The point of this rechartering is to focus
tightly on getting the base protocol done Very Soon. I agree with you
that a use-cases document would be great to publish, and if that's
kept current with any new discussions here it should be easy to pop it
out right away after the next recharter. But we (and the ADs) don't
want to have any distractions from getting OAuth 2.0 out.
.
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
