Re: Progressing I-Ds Immediately Before Meetings
"Spencer Dawkins" <spencer@wonderhamster.org> Sun, 20 July 2008 19:36 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 06B453A6860; Sun, 20 Jul 2008 12:36:24 -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 954363A6860 for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 12:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.031
X-Spam-Level:
X-Spam-Status: No, score=-2.031 tagged_above=-999 required=5 tests=[AWL=0.568, BAYES_00=-2.599]
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 8Tj0XKNEI-JV for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 12:36:21 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 9E6DA3A67DF for <ietf@ietf.org>; Sun, 20 Jul 2008 12:36:21 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1KKei90SYL-0004oJ; Sun, 20 Jul 2008 15:36:52 -0400
Message-ID: <019e01c8eaa0$0f5450b0$6501a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: John C Klensin <john-ietf@jck.com>, Russ Housley <housley@vigilsec.com>, ietf@ietf.org
References: <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><p06250100c4a9226eac87@[75.145.176.242]><20080720180711.438503A6876@core3.amsl.com> <9AA8ABF0D799785CF27AAEE2@[192.168.1.110]>
Subject: Re: Progressing I-Ds Immediately Before Meetings
Date: Sun, 20 Jul 2008 14:37:26 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX1+g4qF2k/9y3nzP0rZB61q0V+kGrrJDs4L0XN0 RozKRjAWod0BKZEg2RIQYIMLRvnBDLziBB3Zr5yGGPKn71UgD7 3XIT0tiikyIQ1gScfVgNBHbheUUnfQy0NIMQhIbYiE=
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
Hi, Russ, The only statement in this thread I don't agree with is >> People seem to be forgetting that all I-D submissions used to >> be processed an a person. I am still remembering that time all too clearly. I suspect that anyone who worked for the secretariat as that person remembers it even more vividly :-) On everything else, I want to echo Dave's "cool", and John's "thanks". Spencer >> The automated tool is very new. >> When the I-D were processed by hand, the cut-off was necessary >> for the Secretariat to handle the spike of submissions just >> prior to the meeting. Look at the statistics report by IETF >> chair in their plenary presentations for the last few years -- >> the meetings cause a huge spike in I-D submissions. Remember >> back when the I-D submissions were handled by hand, it could >> be days after the submission that the document actually >> appeared in the repository. >> >> Now that we have the tool, it is a reasonable time to see if >> we still need this cut-off rule. I have put the topic on the >> agenda for the IESG discussions in Dublin. > > Russ, > > Thanks. > > FWIW, it appears from various notes on this thread that we actually have > two separate cutoff rules, with one having effectively hidden the other. > One of those rules is the two and three week hard cutoff originally > imposed to protect the Secretariat, as you have described above. That > rule came with a "AD exception" procedure, which seems to have gotten lost > over the years ("lost" == "current ADs didn't know about it"). Whether > that exception model was a good idea or not relative to other things ADs > could do with their time is a separate question -- it did exist and, for > better or worse, it was _very_ rarely used. > > The other rule is an RFC 2418 rule that says "should ... two weeks..." > (note lower-case "should"). It carries with it provision for exceptions > by WG chairs and some guidance as to whether those exceptions should be > granted. > > Many of the recent comments in this thread (including, I fear, mine) have > confused the two. It appears to me that most of the suggestions could be > accommodated by looking at the first set of rules (the posting cutoffs) > only, either eliminating them entirely or cutting them to the point > needed to assure a level playing field for those who are forced into > manual posting by deficiencies in the automatic posting tool. > >> I see this an opportunity for evolution and incremental >> improvement. > > Indeed. And a very welcome and much appreciated one. > > john > > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ 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