IETF Logo Mail Archive

Re: [Manycouches] BCP # for draft-ietf-shmoo-cancel-meeting?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 05 October 2021 12:59 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4473A0C5A for <manycouches@ietfa.amsl.com>; Tue, 5 Oct 2021 05:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 6JmK1gEUbv2W for <manycouches@ietfa.amsl.com>; Tue, 5 Oct 2021 05:59:44 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 599533A0C59 for <manycouches@ietf.org>; Tue, 5 Oct 2021 05:59:44 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 195CxfaL027801 for <manycouches@ietf.org>; Tue, 5 Oct 2021 14:59:41 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 32D0E2071FC for <manycouches@ietf.org>; Tue, 5 Oct 2021 14:59:41 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 28D812071FA for <manycouches@ietf.org>; Tue, 5 Oct 2021 14:59:41 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 195Cxfkm005616 for <manycouches@ietf.org>; Tue, 5 Oct 2021 14:59:41 +0200
To: manycouches@ietf.org
References: <CAM4esxRkJUug58t73UKPRpdutzujsAg1WvG5G73pQLOwRDRPoA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <86946798-f8b3-418c-6ef5-ad99d367f03b@gmail.com>
Date: Tue, 05 Oct 2021 14:59:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <CAM4esxRkJUug58t73UKPRpdutzujsAg1WvG5G73pQLOwRDRPoA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/v0iiTB1ATNRp42RZW5S3643QjuA>
Subject: Re: [Manycouches] BCP # for draft-ietf-shmoo-cancel-meeting?
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2021 12:59:49 -0000

Sounds reasonable to group together these documents in a common unique
place to find guidance about a same high-level topic.

One point I'd mention too is that, this being the first time I hear
about several RFCs being 'in' a single BCP, I wonder whether there will
be an undesirable situation in which people refer to BCP226 and actually
talk about another RFC than this cancel rule, thus a potential place for
confusion.  Or maybe it's just me discovering this 'in' relationship for
BCP RFCs.

Alex

Le 04/10/2021 à 17:21, Martin Duke a écrit :
> Hi SHMOO,
> 
> draft-ietf-shmoo-cancel-meeting (soon to be RFC 9137) needs a BCP
> number.
> 
> There are two sensible options I am aware of: - Stand by itself as
> BCP 235. - Be grouped into BCP 226
> <https://www.rfc-editor.org/info/bcp226>, which is all about meeting
> policies.
> 
> I have no strong opinion on this, but if forced to decide I'd put it
> in with 226. I'm happy to receive suggestions on this topic
> (including some /other/ BCP in which this clearly fits.)
> 
> Thanks Martin
> 
> _______________________________________________ Manycouches mailing
> list Manycouches@ietf.org 
> https://www.ietf.org/mailman/listinfo/manycouches
>

v2.23.0 | Report a Bug | By Email