IETF Logo Mail Archive

Re: Question about pre-meeting document posting deadlines for the IESG and the community

"touch@strayalpha.com" <touch@strayalpha.com> Fri, 15 March 2024 23:59 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 543FCC14F6A5; Fri, 15 Mar 2024 16:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.326
X-Spam-Level:
X-Spam-Status: No, score=-1.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZBKSATpdXc5; Fri, 15 Mar 2024 16:59:01 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83149C14F5F3; Fri, 15 Mar 2024 16:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5sveW3iwpFvqLRRg617ikZv81+lDo69dRmtF+06OBQs=; b=gNcntGzr2c1rFoz4vDkLijZFim qVNBwmSdyOqNEIIAxdAW2ynqH9IdR64msYo63vy58sXledTbz2RjTJMF1fCjVC2uw2abhr8kIxdrV rsOoY6QJ3IZm8uUzm42K+rGKj9VCF9Vxk5d4XP6t64/FRKT54dMdWX9syOr1oa8dqV3Bg89hzvJbd aZcspuBlRpQXK15GGKC+bUpIDGHAQkNkXJPgWqoHwP8vLWMSG62fA3/NgZr3CXDqtUziyZPkjeS/B qvc1wjOVToM1mu1llXrE7i+HwfxM4dO39Z54oDyPALa7k1TfSNVrC6WDpaiIQ4RcU+FDE7uCsKvCR bDLheNTQ==;
Received: from [172.56.186.176] (port=7854 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <touch@strayalpha.com>) id 1rlHRv-00C1H2-0o; Fri, 15 Mar 2024 19:58:59 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_E1FF3F39-2BE9-4160-8E71-7E3E8B6CFC68"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <2780ea4c-6041-901c-bb58-ef5e2b1e8a00@gmail.com>
Date: Fri, 15 Mar 2024 16:58:41 -0700
Cc: Pete Resnick <resnick@episteme.net>, Marc Petit-Huguenin <marc@petit-huguenin.org>, John C Klensin <john-ietf@jck.com>, The IESG <iesg@ietf.org>, ietf@ietf.org
Message-Id: <884A9D78-BF28-4197-92A3-06DC46AADA9E@strayalpha.com>
References: <7826C4F13FA874CD79459A4B@PSB> <65A7921B-2A05-439A-976C-226560C5E7F4@strayalpha.com> <e0702d8a-cea5-4928-b571-98442ccd4f29@petit-huguenin.org> <63B37D76-6744-4A3E-BE64-B181013B33CE@episteme.net> <2780ea4c-6041-901c-bb58-ef5e2b1e8a00@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WN15KDANBtMEHmTlxqhjub5_Yro>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
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>
X-List-Received-Date: Fri, 15 Mar 2024 23:59:06 -0000

> On Mar 15, 2024, at 3:49 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> However, we should consider two other effects of the deadline:
> 
> 1. Negative: A ridiculously large number of drafts are posted within
> ~72 hours, as Carsten pointed out recently**. So anybody who tries to
> track the IETF very broadly is swamped three times a year.

The deadline also delays work that is NOT being presented at the IETF.

Joe

v2.23.0 | Report a Bug | By Email