Re: Progressing I-Ds Immediately Before Meetings
Russ Housley <housley@vigilsec.com> Sun, 20 July 2008 18:07 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 974A23A68B4; Sun, 20 Jul 2008 11:07:13 -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 358403A68B4 for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 11:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level:
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 Cfphel5UqoKC for <ietf@core3.amsl.com>; Sun, 20 Jul 2008 11:07:11 -0700 (PDT)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 438503A6876 for <ietf@ietf.org>; Sun, 20 Jul 2008 11:07:11 -0700 (PDT)
Received: (qmail 22084 invoked by uid 0); 20 Jul 2008 18:07:43 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (72.66.14.12) by woodstock.binhost.com with SMTP; 20 Jul 2008 18:07:43 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 20 Jul 2008 14:07:45 -0400
To: ietf@ietf.org
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Progressing I-Ds Immediately Before Meetings
In-Reply-To: <p06250100c4a9226eac87@[75.145.176.242]>
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> <p06250100c4a9226eac87@[75.145.176.242]>
Mime-Version: 1.0
Message-Id: <20080720180711.438503A6876@core3.amsl.com>
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
People seem to be forgetting that all I-D submissions used to be processed an a person. 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. I see this an opportunity for evolution and incremental improvement. Russ _______________________________________________ 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