IETF Logo Mail Archive

Re: [Rfced-future] Issue 144

Peter Saint-Andre <stpeter@stpeter.im> Thu, 06 January 2022 00:44 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FE23A10D7 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=stpeter.im header.b=hOWQojIV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=SeQX3dS1
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 HJwMsLE4lzOQ for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:44:41 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC7C73A10D5 for <rfced-future@iab.org>; Wed, 5 Jan 2022 16:44:41 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 303883201DB9; Wed, 5 Jan 2022 19:44:38 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 05 Jan 2022 19:44:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:to:cc:references:from :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=h HI7dithp5Hi/yHoT5ZDzCt+PsGf5t/o51WWHSCEJSU=; b=hOWQojIVF9n+ecQY7 LKy8/cipPuThw/uPtl8T3E1Z47IeigHITAGL8seKbPeBodp+r3pzlzKQCVfcXXn6 TCCujqQd6TOLiW7Iu8jOxs9hyY8wHFIIFoJvN0780vXS8RYPCZPXDjDhNQ+mKiYf FnJt/GwSCmtq2AxCxpgzxGoRALU+oXa08OzJpVpYdEXvMk8xwykmAetJ/rEa4STP 4bCWC0YqULZs+NMuBCxh/6kHhuRXoRkG3vHtoke3yKe8ttgAbWRoiu2I4Z8YTXRk hkF+t3YlVUpMM+BZ8WAdOguFzSMrPa3IRnLd5rtHVM9TkNUlJOEaBtRMsmPOdn/m fGZuQ==
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=hHI7dithp5Hi/yHoT5ZDzCt+PsGf5t/o51WWHSCEJ SU=; b=SeQX3dS1DohHD4pzluIcAPM/yoeQwXha40eDoiS2HOXgrm4TYtLOyp373 yyN5X+8QU8uv9LXV5ONh2YAp7ht+lUrOtT0SHc9ZXI9NrlrE8dmrQoR9MCnypQH4 kyeRq6fu4rTr53vtuOaNsUyxr0xn82Y9jQnV9rD3tWzk3py9LNcIIRWMaAMmL59o 1rLTzmeq8sY8/44mITTVZFhPpPbdzVwfJBMLR+RPY5E9x54g31c1P1jaqvxdTLWg bhKrQNgAIv/jEjdYs1JmakIgZQGYtTt29aaekgcRQ0EW0olozKjEqRMUF9JgYHA/ Q2HVQleflPX4W83+8+8wn1D8RCftQ==
X-ME-Sender: <xms:dTvWYRMNvz_frduEyteMmwyv_nlY2ZG1AgV5ZE79heVGjV-BKzlBYg> <xme:dTvWYT-_kZnmhkOmGsE_hZR3ZhMV856FZguq-zMZuuV-nEYj-Q0qbYFL91gCsKCmm cERdxC2titnRt7ZDQ>
X-ME-Received: <xmr:dTvWYQRgVTyAbiipNlFrCBdpxRCkpkICe0QT5ylu7ydfa7qlvk6-l6w2xbEiw2uxGqqGoALsO4BWTxtU3qI1mSY4cJbOfl9lLOqBkhE>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudefjedguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfurghinhhtqdetnhgurhgvuceoshhtphgvthgvrhesshhtphgvthgvrhdrihhmqe enucggtffrrghtthgvrhhnpeehtefhvdejvdfhgeetgefhfeeuudefkeetvdfhkeelleeu heefleekkeekieffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsthhpvghtvghrsehsthhpvghtvghrrdhimh
X-ME-Proxy: <xmx:dTvWYdvlMKW0xBG6eFZBWjRLqcxmW3PDKWmGpcvuh-RwCFLQx43CVQ> <xmx:dTvWYZdkfFBeAx5FepPjbhn6pWRK1HDXHodtuv2RcAzDd7AlHejb3Q> <xmx:dTvWYZ0acTVo_pv5iTUSC8tDlu8X5xE8Dc3pdpmt5bsdMLM74JPXUg> <xmx:dTvWYd5WdWSKHFQgmrWr480fMu7JjJtXmSe0I15yobNhctGm7hUNrQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Jan 2022 19:44:36 -0500 (EST)
Message-ID: <13b8addb-fba2-606f-6ad4-e718b06a7956@stpeter.im>
Date: Wed, 05 Jan 2022 17:44:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Scott Bradner <sob@sobco.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eric Rescorla <ekr@rtfm.com>, rfced-future@iab.org
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <53497e97-ed65-93c8-5f4c-3f4ee9943501@stpeter.im> <abb0c140-2bed-312b-4f25-c36bee0c1f56@gmail.com> <db4d809d-a64e-4350-ecb4-5e85dca8ba40@stpeter.im> <8C799458-F53B-45F1-8AF1-278BE5E5B1C1@sobco.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <8C799458-F53B-45F1-8AF1-278BE5E5B1C1@sobco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ZQdnpKIDioWhmyJmAngJmuyERdA>
Subject: Re: [Rfced-future] Issue 144
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2022 00:44:47 -0000

On 1/5/22 5:43 PM, Scott Bradner wrote:
>   Peter Saint-Andre <stpeter@stpeter.im> wrote:
> However, I don't see exactly where it talks about advance notification for "other working group meetings". I must be missing something obvious.
> 
> 7.1. Session documents
> 
>     All relevant documents to be discussed at a session should be
>     published and available as Internet-Drafts at least two weeks before
>     a session starts.  Any document which does not meet this publication
>     deadline can only be discussed in a working group session with the
>     specific approval of the working group chair(s).  Since it is
>     important that working group members have adequate time to review all
>     documents, granting such an exception should only be done under
>     unusual conditions.  The final session agenda should be posted to the
>     working group mailing list at least two weeks before the session and
>     sent at that time to agenda@ietf.org for publication on the IETF web
>     site.

Right, I suppose that counts as "advance notification" (even though it 
doesn't exactly say when a meeting is to be announced).

Peter

v2.23.0 | Report a Bug | By Email