IETF Logo Mail Archive

Re: Progressing I-Ds Immediately Before Meetings

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 20 July 2008 00:55 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 3714A3A6828; Sat, 19 Jul 2008 17:55:59 -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 5B67D3A6828 for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 17:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level:
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.482, 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 Ym1xLLU1Xjn8 for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 17:55:57 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by core3.amsl.com (Postfix) with ESMTP id 9E8113A67F7 for <ietf@ietf.org>; Sat, 19 Jul 2008 17:55:57 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so587016wfd.31 for <ietf@ietf.org>; Sat, 19 Jul 2008 17:56:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=36JdPVR2o+oOrUwlJHlqUGyFoic94zOsWPsYQ2vpqrk=; b=uu1jteY0BMmAcKzQ7Wx5wfovGMZIuDL57glBhN6cWEOESdoAUqmuPmWhS67ekd8zKe 1JwjRLkUy6OfKIv9Gf7v9LYPT+x9+uFCUC6XHhWXiqfm3NiGuyzc7Zwp4WrQKDb1FV3j ZxbkxuaFlmm8W4JrL50kbRlNGah6uA3Xs5u54=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Q5o3E7LAJIUqzmr+mv/9s1LV2SYPex3WzTmyeenUqiQWcSlD0lYhJXGzvUKN0VpHAQ 8W+J5KjYnXx/r1S93D5Y6nTaNblTdxB3nce+GzIuPh0GmrRSIUS2ejTIhsBipJAz7C1X T3GoPdRr01Fv3QMP/89OwvAuqVARDUurKeJpk=
Received: by 10.142.170.6 with SMTP id s6mr696091wfe.102.1216515393635; Sat, 19 Jul 2008 17:56:33 -0700 (PDT)
Received: from ?10.1.1.4? ( [118.93.54.65]) by mx.google.com with ESMTPS id 30sm2040520wfd.1.2008.07.19.17.56.30 (version=SSLv3 cipher=RC4-MD5); Sat, 19 Jul 2008 17:56:33 -0700 (PDT)
Message-ID: <48828D3B.4050006@gmail.com>
Date: Sun, 20 Jul 2008 12:56:27 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Progressing I-Ds Immediately Before Meetings
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>
In-Reply-To: <01MXCGZDHDXW000078@mauve.mrochek.com>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Ned,

...
> Frankly, I think it is more about trusting groups to be able to manage
> themselves than anything else.

I don't think that's quite fair. If you think about a participant
who is tracking several WGs and/or topics that cut across many WGs,
that person needs to be able to read everything relevant before
arriving. A cutoff about two weeks in advance does make that feasible.
(Let's see - I still have about 12 drafts to read - is that unusual
with one week to go?) I would much rather have that situation, so
that I can prioritize the drafts, than have them arriving until
after I'm already in the air, which would be the inevitable result
of relaxing the cutoff rules.

That said, exceptions should definitely be possible, and I would
delegate that to WG Chair level.

    Brian
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email