Re: Progressing I-Ds Immediately Before Meetings
Pete Resnick <presnick@qualcomm.com> Sun, 20 July 2008 17:26 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D40823A689A; Sun, 20 Jul 2008 10:26:31 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FF603A689A for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 10:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level:
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 0s-hpj+LphkE for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 10:26:29 -0700 (PDT)
Received: from episteme-software.com (mail.episteme-software.com [75.145.176.241]) by core3.amsl.com (Postfix) with ESMTP id EFF293A6841 for <ietf@ietf.org>; Sun, 20 Jul 2008 10:26:28 -0700 (PDT)
Received: from [75.145.176.242] (127.0.0.1) by episteme-software.com with ESMTP (EIMS X 3.3.7); Sun, 20 Jul 2008 12:27:03 -0500
Mime-Version: 1.0
X-Sender: presnick@resnick1.qualcomm.com@resnick1.qualcomm.com
Message-Id: <p06250100c4a9226eac87@[75.145.176.242]>
In-Reply-To: <01MXDEUGJPR400007A@mauve.mrochek.com> <20080719231903.GB64676@verdi> <013501c8ea6a$271e28a0$6501a8c0@china.huawei.com>
References: <043101c8e8ec$fa67c650$0200a8c0@your029b8cecfe> <200807181819.m6IIJCIR025085@mta6.iomartmail.com> <048401c8e924$ab2ce600$0200a8c0@your029b8cecfe> <XFE-SJC-211BBtNtxy0000033b7@xfe-sjc-211.amer.cisco.com> <4881CFF5.3090008@piuha.net> <1EFD708A-8509-42A6-BBC9-824C27A7DCFA@multicasttech.com> <6BA8110C64663A4908066554@p3.JCK.COM> <48821469.4050907@employees.org> <20080719191556.567F03A6A32@core3.amsl.com> <48826DC0.8000307@dcrocker.net> <01MXCGZDHDXW000078@mauve.mrochek.com> <48828D3B.4050006@gmail.com> <01MXCL869C4K00007A@mauve.mrochek.com> <4882A2AD.8040405@dcrocker.net> <013501c8ea6a$271e28a0$6501a8c0@china.huawei.com> <01MXDEUGJPR400007A@mauve.mrochek.com> <043101c8e8ec$fa67c650$0200a8c0@your029b8cecfe> <200807181819.m6IIJCIR025085@mta6.iomartmail.com> <048401c8e924$ab2ce600$0200a8c0@your029b8cecfe> <XFE-SJC-211BBtNtxy0000033b7@xfe-sjc-211.amer.cisco.com> <4881CFF5.3090008@piuha.net> <1EFD708A-8509-42A6-BBC9-824C27A7DCFA@multicasttech.com> <6BA8110C64663A4908066554@p3.JCK.COM> <48821469.4050907@employees.org> <20080719191556.567F03A6A32@core3.amsl.com> <48826DC0.8000307@dcrocker.net> <20080719231903.GB64676@verdi> <043101c8e8ec$fa67c650$0200a8c0@your029b8cecfe> <200807181819.m6IIJCIR025085@mta6.iomartmail.com> <048401c8e924$ab2ce600$0200a8c0@your029b8cecfe> <XFE-SJC-211BBtNtxy0000033b7@xfe-sjc-211.amer.cisco.com> <4881CFF5.3090008@piuha.net> <1EFD708A-8509-42A6-BBC9-824C27A7DCFA@multicasttech.com> <6BA8110C64663A4908066554@p3.JCK.COM><48821469.4050907@employees.org> <20080719191556.567F03A6A32@core3.amsl.com> <48826DC0.8000307@dcrocker.net> <01MXCGZDHDXW000078@mauve.mrochek.com><48828D3B.4050006@gmail.com> <01MXCL869C4K00007A@mauve.mrochek.com> <4882A2AD.8040405@dcrocker.net> <013501c8ea6a$271e28a0$6501a8c0@china.huawei.com>
User-Agent: Eudora 6.2.5b1(Macintosh)
Date: Sun, 20 Jul 2008 12:27:10 -0500
To: John Leslie <john@jlc.net>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Progressing I-Ds Immediately Before Meetings
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On 7/19/08 at 7:19 PM -0400, John Leslie wrote: >You're missing the nature of consensus process. Actually, John, I'm afraid it was you who missed the consensus. As Spencer writes: >The relevant text in 2418 says > >7.1. Session documents > > All relevant documents to be discussed at a session should be > published and available as Internet-Drafts at least two weeks before > a session starts. Any document which does not meet this publication > deadline can only be discussed in a working group session with the > specific approval of the working group chair(s). Since it is > important that working group members have adequate time to review all > documents, granting such an exception should only be done under > unusual conditions. The final session agenda should be posted to the > working group mailing list at least two weeks before the session and > sent at that time to agenda@ietf.org for publication on the IETF web > site. > >So I don't know where the "must have AD approval for exceptions" >thing came from, unless it's a misplaced need to have ADs approve >everything. The consensus was to have WG chairs make a two-week deadline with exceptions if needed. As Ned pointed out: >Funny, I myself don't see anything in here at all about an I-D >cutoff. What I do see is a fairly reasonable rule [...] about having >stuff available for review sufficiently early. > >You're confusing a rule with a procedure which has as one purpose to >try and enforce that rule. Since the procedure is something >implemented by the Secretariat, the question is what whose authority >would they accept to make an exception. Maybe they'd accept a >request from a WG chair. Or maybe not. The cutoff is an arbitrary procedure to try (poorly IMO) to enforce the 2418 rule. It is the procedure, and the resultant non-consensus rule ("No drafts within 2 weeks of an IETF meeting") which is garnering these complaints. >In consensus process, we work towards a situation that everyone can >agree to live with. We don't attempt to get everyone's view on >record. > >Once you reach consensus, you expect it to represent stability, >because people don't want to go through all that trouble again. >People adapt to the consensus. On this we agree. >Removing the automated cutoff would require changes in the way >various things are done. Well, it might require changes to how things are done. However, it would not require changes to the consensus, and (IMO) would not change the outcome. WG chairs would be expected to follow the consensus as laid out in 2418, two weeks would be given for review (as now), exceptions could be made (as now), and the ADs would not have to be in the loop (which was never required by the consensus). pr -- Pete Resnick <http://www.qualcomm.com/~presnick/> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Progressing I-Ds Immediately Before Meetings Adrian Farrel
- Re: Progressing I-Ds Immediately Before Meetings Russ Housley
- Re: Progressing I-Ds Immediately Before Meetings Adrian Farrel
- Re: Progressing I-Ds Immediately Before Meetings James M. Polk
- Re: Progressing I-Ds Immediately Before Meetings Jari Arkko
- Re: Progressing I-Ds Immediately Before Meetings Spencer Dawkins
- Re: Progressing I-Ds Immediately Before Meetings Scott Brim
- Re: Progressing I-Ds Immediately Before Meetings Marshall Eubanks
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings Scott Brim
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings Russ Housley
- Re: Progressing I-Ds Immediately Before Meetings Jari Arkko
- Re: Progressing I-Ds Immediately Before Meetings Dave Crocker
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings Steven M. Bellovin
- Re: Progressing I-Ds Immediately Before Meetings John Leslie
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Brian E Carpenter
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Brian E Carpenter
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Dave Crocker
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Dave Crocker
- Re: Progressing I-Ds Immediately Before Meetings Spencer Dawkins
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Spencer Dawkins
- Re: Progressing I-Ds Immediately Before Meetings Pete Resnick
- Re: Progressing I-Ds Immediately Before Meetings Russ Housley
- Re: Progressing I-Ds Immediately Before Meetings Dave Crocker
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings Spencer Dawkins
- RE: Progressing I-Ds Immediately Before Meetings Eric Gray
- RE: Progressing I-Ds Immediately Before Meetings ned+ietf
- Re: Progressing I-Ds Immediately Before Meetings John C Klensin
- Re: Progressing I-Ds Immediately Before Meetings Ned Freed
- RE: Progressing I-Ds Immediately Before Meetings Eric Gray
- RE: Progressing I-Ds Immediately Before Meetings ned+ietf