Re: [dispatch] Cutoff for 110?

Mark Nottingham <mnot@mnot.net> Mon, 18 January 2021 23:21 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A50713A0CCD for <dispatch@ietfa.amsl.com>; Mon, 18 Jan 2021 15:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level:
X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=jwlczuSi; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=K3ciQj1v
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmjTICQ5RRHv for <dispatch@ietfa.amsl.com>; Mon, 18 Jan 2021 15:21:46 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB0703A0CC7 for <dispatch@ietf.org>; Mon, 18 Jan 2021 15:21:46 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id DB4935C01B4; Mon, 18 Jan 2021 18:21:45 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 18 Jan 2021 18:21:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=D KdhSameFVIKDaf2svpOmwjB7GHMWclaUqndiLLy+kg=; b=jwlczuSifMXrIMcA8 mcsLBXBLt8X5K3ZCymLsP/pgxcJmhsS9jyWiJIsKX+w5g58IJDiBRBy7ir0A7Neo 3JZRozUhS33YhJrnB4r5b8H1ENjRBJvU+UJic6InQ2iYX0RKbmL0FuQhtiEDWryy 1bhkA8Hs4UsxfPrlI9UTaI3e+lYv5N4TbPDMsu8R+l8VV+IIe4WE5jiXfCFAv7Jc fj7K1dQ/lQyEvOTz0r+hitfyJ0Xw9OQkKQI4GN2CflX1YG7yDsOfOUAMyohuafxK 9UeYOXPSeLM419t0TAwI4DBLl7OTZj75g3hTxmZaVnin5pZqCynCtwGN4zr/cdzl zb2pQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=DKdhSameFVIKDaf2svpOmwjB7GHMWclaUqndiLLy+ kg=; b=K3ciQj1vbyM+dji6josm66rp1JDCsmDTKSkW32a/On8TIHMfhzs4EtRsc i/t/pWGpLeXEiD4tG9y+eBkUgKq1Is2qlT39qw4Ebxic4B2yqMtftBKLSaGbMluy Q/8bLpDl9movRCeT6FURSHi54FtoPoCHkw/BYY4HgW+NO2xrBI3SKfOxuEben8Xe jI0rbj1vk+WFpYA0zvXZjlwdTFGRsTKt0/PtvxvdmI/yl6YU+4mqB+lEGNw7laM5 1QM68PKElmbqYSME9xX28vBBwRLlczE+i16m4g4mgsEWxTANCmOYBh3J4Lxtr6Dp PTjMZyK23AKvYP17J6hXXS9TPX+xg==
X-ME-Sender: <xms:CBgGYMZm33tvAt4TJ8_Dhd79GzDOaoO9eUthAXDeb2nAjlh3NnA_Ww> <xme:CBgGYHbC8i4J6u6PRQKpCqdT65DlqWcSS6LD2Dq6UDiAJRLiUUM9wCTrVVn8u-LfE W9fWp2T2aRC_8mcVw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdelgddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeduvdeljeegtefhveekhfdtveekleevkeefgeeludeihfdugedvieeuffdttdfh necuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecukfhppeduudelrd dujedrudehkedrvdehudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:CRgGYG8oO6jQdmtKf6CSTiTz-j7e5lMzRVolqFf52Fhrzo6XwviU1A> <xmx:CRgGYGpdu5R0HRCgfqY7Lg8bcFfeFDgkF-38VfwMpHphgFQuJzif0w> <xmx:CRgGYHrGr-_EQVaytpI2kQdkPzDFJpreSNjnxJ001KovfDtX65-GTw> <xmx:CRgGYGWkq4qK90Gw-mQzCMT6UmjqSFv3NGu1Vsr96QKUAj_xwxqmRA>
Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id EB65D24005E; Mon, 18 Jan 2021 18:21:43 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAHBDyN6HSXgZtWrBeh5ZTrfDokKt-K9x6-VjcpujR9eKRiRwWA@mail.gmail.com>
Date: Tue, 19 Jan 2021 10:21:41 +1100
Cc: Martin Thomson <mt@lowentropy.net>, DISPATCH <dispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD96D546-515A-4BB6-8B52-94E659FA7F86@mnot.net>
References: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> <CAHBDyN6HSXgZtWrBeh5ZTrfDokKt-K9x6-VjcpujR9eKRiRwWA@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Fo2TV_0ipyqDzguAqaJF0xkZPRA>
Subject: Re: [dispatch] Cutoff for 110?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2021 23:21:49 -0000

I'd interpret the current situation being 'no deadlines' as well.

If so, that's a good outcome; I always found the seeming rigidity* of the DISPATCH process distinctly unwelcoming, especially in a group that's very likely to be someone's first experience of the IETF.

Regardless of whether there are deadlines or not, I think DISPATCH has a duty to clearly document and publicise its processes, expectations and norms. Expecting them to find RFC7957 is *not* adequate.

Cheers,


* I know that there was supposed to be flexibility in the dates, etc., but that was less than clear unless you were an 'insider.'



> On 19 Jan 2021, at 8:17 am, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
> 
> That's because no one has updated the wiki since I was removed as a co-chair.  Personally, I found it extremely helpful to have the dates there and to keep up with how work items were dispatched since names of activities change.  But, that's for the new chairs to decide if they want to spend the time on it (I did it as part of pre- and post- meeting activities).
> 
> As far as IETF-110 dates, I had expected to find them at least in the IETF-109 chair slides, but they're not there either. 
> 
> So, I guess there are no deadlines other than the draft deadline this time :)
> 
> Regards,
> Mary. 
> 
> On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson <mt@lowentropy.net> wrote:
> I'm looking at the wiki and its very much out of date.  Based on the one example of the dates in the Wiki, the dates might have passed already, but I haven't seen any notices to the list.  Where are we at?
> 
> (Answer to the obvious question: I'm working on something with others, but it's not quite ready yet.)
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

--
Mark Nottingham   https://www.mnot.net/