[Manycouches] BCP 226, RFC 9137 on Considerations for Cancellation of IETF Meetings

rfc-editor@rfc-editor.org Tue, 12 October 2021 06:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 E14F13A0DF9; Mon, 11 Oct 2021 23:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 lLPT9r-bJsdK; Mon, 11 Oct 2021 23:37:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DBFD3A0DEE; Mon, 11 Oct 2021 23:37:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 499) id CCB2D5CE2B9; Mon, 11 Oct 2021 23:37:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, manycouches@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20211012063737.CCB2D5CE2B9@rfc-editor.org>
Date: Mon, 11 Oct 2021 23:37:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/rM8HK1_XLDlfQF30CJRw7gPIJNo>
Subject: [Manycouches] BCP 226, RFC 9137 on Considerations for Cancellation of IETF Meetings
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, 12 Oct 2021 06:37:46 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 226        
        RFC 9137

        Title:      Considerations for Cancellation of
                    IETF Meetings 
        Author:     M. Duke
        Status:     Best Current Practice
        Stream:     IETF
        Date:       October 2021
        Mailbox:    martin.h.duke@gmail.com
        Pages:      7
        See Also:   BCP 226

        I-D Tag:    draft-ietf-shmoo-cancel-meeting-06.txt

        URL:        https://www.rfc-editor.org/info/rfc9137

        DOI:        10.17487/RFC9137

The IETF ordinarily holds three in-person meetings per year to
discuss issues and advance the Internet. However, various events can
make a planned in-person meeting infeasible. This document provides
criteria to aid the IETF Administration LLC (IETF LLC), the Internet
Engineering Steering Group (IESG), and the Chair of the Internet
Research Task Force (IRTF) in deciding to relocate, virtualize,
postpone, or cancel an in-person IETF meeting.

This document is a product of the Stay Home Meet Only Online Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC