Re: [OAUTH-WG] OAuth specs in IETF last call

Peter Saint-Andre <stpeter@stpeter.im> Mon, 23 January 2012 17:39 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00FD121F86AB for <oauth@ietfa.amsl.com>; Mon, 23 Jan 2012 09:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level:
X-Spam-Status: No, score=-102.655 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9vIDXKDL4HT3 for <oauth@ietfa.amsl.com>; Mon, 23 Jan 2012 09:39:38 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2638B21F8664 for <oauth@ietf.org>; Mon, 23 Jan 2012 09:39:38 -0800 (PST)
Received: from dhcp-64-101-72-243.cisco.com (unknown [64.101.72.243]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 30EAB40058 for <oauth@ietf.org>; Mon, 23 Jan 2012 10:49:16 -0700 (MST)
Message-ID: <4F1D9B57.1030501@stpeter.im>
Date: Mon, 23 Jan 2012 10:39:35 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: oauth@ietf.org
References: <4E1F6AAD24975D4BA5B168042967394366375EB9@TK5EX14MBXC284.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394366375EB9@TK5EX14MBXC284.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.3.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [OAUTH-WG] OAuth specs in IETF last call
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2012 17:39:39 -0000

On 1/23/12 10:11 AM, Mike Jones wrote:
> FYI, the OAuth Core and Bearer specifications have reached IETF last
> call status - the last step before becoming RFCs.  See the following
> notes from the Internet Engineering Steering Group (IESG).

Well, "last step" might be a bit optimistic. :)

For those who aren't familiar with the process, the next steps are:

1. IETF Last Call, which lasts two weeks. This is essentially your last
opportunity to provide feedback!

2. During IETF Last Call, the documents will be reviewed by several
cross-area teams within the IETF, including folks like the "GEN-ART"
review team and the AppsDir. We'll expect at least some feedback from
those teams. And at this stage anyone in the Internet community can
provide feedback, too.

3. After IETF Last Call, this WG's document editors will work to address
any feedback we've received.

4. The documents will then be scheduled for disussion during an IESG
telechat. Before the telechat, all the members of the Internet
Engineering Steering Group will review the specs and also provide
feedback. If there are "DISCUSSES" and "COMMENTS" lodged then the
document editors will need to address those (often in concert with the
WG chairs). If some of those issues are substantive, the editors and
chairs might bring those issues back to the WG for more discussion.

5. Assuming the documents are approved by the IESG, they will then be
handed off to the RFC Editor team for final copy editing, proofreading,
reference checking, etc.

As you can see, because there are still many steps left in the process,
it might be a few months before these specs are published as RFCs.

Just so you know!

Peter

--
Peter Saint-Andre
https://stpeter.im/