[OAUTH-WG] Device flow to move to an extension

Eran Hammer-Lahav <eran@hueniverse.com> Fri, 11 June 2010 07:41 UTC

From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Date: Fri, 11 Jun 2010 00:41:23 -0700
Thread-Topic: Device flow to move to an extension
Thread-Index: AcsJOX1e+S8/2cmcQnaAz3XlGMB0bw==
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3EAF74BC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [OAUTH-WG] Device flow to move to an extension
Precedence: list

Unlike the rest of the flows, the device flow lacks deployment experience and is still likely to change. It also uses a very different architecture than the rest of the flows (which becomes more obvious in my -07 rewrite). Unless there is strong objection, I am going to remove it from the core spec and republish it as a new draft.

In general, I am going to iterate through the spec in the next couple weeks and move unstable (and non-essential) features out to extension specs.

EHL

[OAUTH-WG] Device flow to move to an extension Eran Hammer-Lahav
[OAUTH-WG] Device flow to move to an extension Eran Hammer-Lahav