On 2012-05-24 09:02, Mike Jones wrote:
My recollection is that putting it in an appendix was explicitly rejected in
the threads discussing the DISCUSS issues and no one on those threads pushed
back afterwards, particularly after Dick's explanations of why it should stay.
(Why these DISCUSS discussions don't include the full working group is a
mystery to me, but apparently that's the way it's done at this stage of the
IETF spec finalization process. Can anyone tell me why that's the case?)
Anyway, since this feature has been in *every* version of the spec, leaving it
in hardly seemed to require a consensus call. The chairs, of course, can
obviously hold one if they believe one is called for.
...
It is very awkward to have the spec define three ways to do things, and
have one of them marked as "NOT RECOMMENDED" (== "SHOULD NOT"), but
leave it in the same place as the two other methods that are actually
supposed to be used.
The NOT RECOMMENDED is to discourage use. *Keeping* the text is a
compromise because of wide deployment, but then moving the text into an
appendix reflecting the normative status should not negatively affect
deployments, right?
Best regards, Julian
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth
