Re: [xmpp] next steps

Peter Saint-Andre <stpeter@stpeter.im> Sun, 17 October 2010 02:52 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76EF93A69DF for <xmpp@core3.amsl.com>; Sat, 16 Oct 2010 19:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level:
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCYAAFHtA6F7 for <xmpp@core3.amsl.com>; Sat, 16 Oct 2010 19:52:55 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id BDBB53A63D2 for <xmpp@ietf.org>; Sat, 16 Oct 2010 19:52:54 -0700 (PDT)
Received: from squire.local (dsl-251-156.dynamic-dsl.frii.net [216.17.251.156]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C2395400EE for <xmpp@ietf.org>; Sat, 16 Oct 2010 21:01:25 -0600 (MDT)
Message-ID: <4CBA6551.1000709@stpeter.im>
Date: Sat, 16 Oct 2010 20:54:09 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: xmpp@ietf.org
References: <4CAE44AB.6060602@stpeter.im>
In-Reply-To: <4CAE44AB.6060602@stpeter.im>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms060804020508050603050400"
Subject: Re: [xmpp] next steps
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Oct 2010 02:52:57 -0000

A further note about the schedule: Gonzalo issued the IETF Last Calls on
October 7 and they expire on October 21. The cut-off date for submitting
revised Internet-Drafts before IETF 79 is October 25 at 24:00 UTC.
Therefore I plan to submit 3920bis-18, address-06, and 3921bis-16
sometime between the end of the Last Calls and the cut-off date
(probably on Monday, October 25).

On 10/7/10 4:07 PM, Peter Saint-Andre wrote:
> Because some folks on this list are new to IETF process, I figured I'd
> provide a brief description of where we go from here.
> 
> 1. Gonzalo Camarillo, the responsible Area Director, has issued an IETF
> Last Call on our three main documents. Because these I-Ds are the
> product of an IETF Working Group, the IETF Last Call will last 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 the "GEN-ART" review team
> and the Security Directorate. We'll expect at least some feedback from
> those teams. And at this stage anyone in the Internet community can
> provide feedback as well.
> 
> 3. After IETF Last Call, your friendly document editor will work as fast
> as possible to address any feedback we've received.
> 
> 4. The documents will then be scheduled for disussion during an IESG
> telechat. There are upcoming telechats on October 28, November 18,
> December 2, and December 16. Before the telechat, all the members of the
> Internet Engineering Steering Group will review the specs and also
> provide feedback (well, except for me, because I'll recuse myself). If
> there are "DISCUSSES" and "COMMENTS" lodged then your document editor
> will need to address those, as well.
> 
> 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. In particular, the documents will not be
> published as RFCs until all normative references have also advanced;
> this includes especially draft-saintandre-tls-server-id-check, which is
> on a parallel track to consideration by the IESG (I'm working to push
> out a revised version of that one in the next few days).
> 
> As you can see, because there are still many steps left in the process,
> it might be a few months before these "bis" drafts are published as
> RFCs. That gives you all plenty of time to bring your implementations
> into conformance. ;-)
> 
> Just so you know!
> 
> Peter
>