Re: [Rfced-future] Issue 144

Scott Bradner <sob@sobco.com> Thu, 06 January 2022 00:47 UTC

Return-Path: <sob@sobco.com>
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 585393A10E0 for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.916
X-Spam-Level:
X-Spam-Status: No, score=-0.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PDS_RDNS_DYNAMIC_FP=0.002, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 NSrSFzuLVokO for <rfced-future@ietfa.amsl.com>; Wed, 5 Jan 2022 16:46:56 -0800 (PST)
Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id 956FD3A10DD for <rfced-future@iab.org>; Wed, 5 Jan 2022 16:46:56 -0800 (PST)
Received: from smtpclient.apple (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id DFADF1096241; Wed, 5 Jan 2022 19:46:55 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <13b8addb-fba2-606f-6ad4-e718b06a7956@stpeter.im>
Date: Wed, 05 Jan 2022 19:46:55 -0500
Cc: rfced-future@iab.org, Eric Rescorla <ekr@rtfm.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <96BCD1DF-9C2F-4F29-9136-2EE1B4AF463E@sobco.com>
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> <13b8addb-fba2-606f-6ad4-e718b06a7956@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/C1yywb6B-LqIpfeUFG5Grs2cyOs>
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:47:01 -0000

agreed - not as clear as it might have been :-)

> On Jan 5, 2022, at 7:44 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
> 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
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future