[RAI] Document states
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 20 July 2010 08:44 UTC
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: rai@core3.amsl.com
Delivered-To: rai@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BCBC3A67A4 for <rai@core3.amsl.com>; Tue, 20 Jul 2010 01:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.791
X-Spam-Level:
X-Spam-Status: No, score=-103.791 tagged_above=-999 required=5 tests=[AWL=-1.192, 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 mr6+70nehdGf for <rai@core3.amsl.com>; Tue, 20 Jul 2010 01:44:38 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id A1EF13A69A4 for <rai@ietf.org>; Tue, 20 Jul 2010 01:44:37 -0700 (PDT)
X-AuditID: c1b4fb39-b7b91ae000001aef-3f-4c456204bfdb
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 3D.F2.06895.402654C4; Tue, 20 Jul 2010 10:44:52 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Jul 2010 10:44:51 +0200
Received: from [131.160.126.163] ([131.160.126.163]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Jul 2010 10:44:51 +0200
Message-ID: <4C456203.4040202@ericsson.com>
Date: Tue, 20 Jul 2010 11:44:51 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: rai@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jul 2010 08:44:51.0711 (UTC) FILETIME=[D191C0F0:01CB27E7]
X-Brightmail-Tracker: AAAAAA==
Subject: [RAI] Document states
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 08:44:40 -0000
Folks, based on my conversations with many of you and the questions I usually get, most people are not familiar with the process documents follow since the leave their WG (the chairs request the publication of the document) until the document gets published as an RFC. For most people, this process seems to be like a black box. Most people would like to know how they can help progress documents more efficiently when the document is in different states within the process. The following draft contains useful information on the states documents can have: https://datatracker.ietf.org/doc/draft-ietf-proto-wgdocument-states/ In short, when the chairs request the publication of a draft, the draft is first reviewed by the AD responsible for the WG. Then, the draft will be reviewed by the whole IETF community during its IETC LC. Finally, the draft will be reviewed by the IESG. While having authors respond to questions in a timely manner is always important, it is specially important in the IETF LC and IESG review stages. This is because you are going to be dealing with reviewers outside your WG who do not have the context to understand the draft permanently in their heads. If a reviewer asks a question and the author does not answer quickly enough, the reviewer will have to reconstruct all that context information when he or she eventually gets a response... as you can imagine, this slows things down a lot. So, please, be responsive and do not let that type of context information timeout. If you are interested in the state a particular draft is in at a particular point, just check the tracker. We try and keep the tracker up to date. Cheers, Gonzalo
- [RAI] Document states Gonzalo Camarillo