Re: [alto] Adopting two I-Ds as WG documents

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Tue, 07 April 2009 20:12 UTC

Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BFEE3A6DE3 for <alto@core3.amsl.com>; Tue, 7 Apr 2009 13:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level:
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=-2.065, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 j1IEmpjtKucH for <alto@core3.amsl.com>; Tue, 7 Apr 2009 13:12:11 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 2DCE43A6830 for <alto@ietf.org>; Tue, 7 Apr 2009 13:12:10 -0700 (PDT)
Received: from ([24.40.15.118]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.59315872; Tue, 07 Apr 2009 16:12:53 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 7 Apr 2009 16:12:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 07 Apr 2009 16:12:40 -0400
Message-ID: <74CCBBDF76102846AFA7B29F3A98D3F602896FC5@PACDCEXCMB06.cable.comcast.com>
In-Reply-To: <49DB978F.2070707@alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [alto] Adopting two I-Ds as WG documents
Thread-Index: Acm3ridyl4KNJ8hEQ8aPoOOxc1uyMAADYeUw
References: <49DB5D36.60700@alcatel-lucent.com><547F018265F92642B577B986577D671C7FE2A4@VENUS.office><74CCBBDF76102846AFA7B29F3A98D3F602896FC2@PACDCEXCMB06.cable.comcast.com> <49DB978F.2070707@alcatel-lucent.com>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
X-OriginalArrivalTime: 07 Apr 2009 20:12:53.0409 (UTC) FILETIME=[3BA43910:01C9B7BD]
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Adopting two I-Ds as WG documents
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 20:12:12 -0000

> I don't think there is a deadline for objecting to an I-D.

You are correct that objections may come at any time in the lifecycle of
an I-D (and errata can be posted against an RFC).

But it does help to set a "weak deadline" for objections to accepting
these documents as WG drafts, for a few reasons:

1. Deadlines help prioritize effort. If the WG knows that there is a two
week deadline to object (say), then individuals can schedule time in the
next two weeks to read the two drafts
(draft-marocco-alto-problem-statement-05 and draft-kiesel-alto-reqs-02)
and make their own decision: adopt, object, or not offer an opinion.

2. If no one objects by the deadline, then the WG chairs have a good
sense of WG consensus. And it avoids 'voting'.

3. Adopting the drafts as WG drafts is a matter of efficiency. While the
drafts are not 'done', at least they represent the best written
understanding of the WG with regards to the problem statement and
requirements. Non-WG members can see the adopted drafts on the WG
webpage, e.g. http://www.ietf.org/html.charters/alto-charter.html. So
the sooner that the WG chairs can gauge consensus, the better it is for
everyone.

4. If someone's objection misses the deadline, it is not a catastrophe,
as only an RFC is permanently published. Regardless, it would be helpful
to the efforts and direction of the WG as a whole if the deadline was
honored.

-- Rich, a former WG co-chair :)

-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
Vijay K. Gurbani
Sent: Tuesday, April 07, 2009 2:13 PM
To: Woundy, Richard
Cc: alto
Subject: Re: [alto] Adopting two I-Ds as WG documents

Woundy, Richard wrote:
> I also am in favor of making both items into WG items.

Rich: OK, thanks.

> Incidentally, is there a WG deadline for objecting?

Interesting question.  I don't think there is a deadline
for objecting to an I-D.  Technical dissent and solving
it through consensus is the life-blood of a WG, so objections
can be raised at any point in the process -- pre-WGLC, WGLC,
Gen-Art review, and finally, IESG review.

Even after a I-D becomes an RFC, errata can be filed against
the RFC.  In the most egregious case, the flawed RFC can
be obsoleted with a new RFC.

I must preface in that the above is my understanding, subject
to corrections from the AD or other parties with more
information and experience on the process.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto