BCP 83 PR actions and new media

Samuel Weiler <weiler@csail.mit.edu> Wed, 09 November 2022 18:31 UTC

Return-Path: <weiler@csail.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C6AC1522A2; Wed, 9 Nov 2022 10:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGmQCN_EGDpZ; Wed, 9 Nov 2022 10:31:16 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BF27C14CF11; Wed, 9 Nov 2022 10:31:15 -0800 (PST)
Received: from dhcp-8c65.meeting.ietf.org ([31.133.140.101]) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <weiler@csail.mit.edu>) id 1ospqz-0002aW-4N; Wed, 09 Nov 2022 18:31:13 +0000
Date: Wed, 09 Nov 2022 13:31:10 -0500
From: Samuel Weiler <weiler@csail.mit.edu>
To: iesg@ietf.org
cc: ietf@ietf.org
Subject: BCP 83 PR actions and new media
Message-ID: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_B12VEm9dWoaXuXT5J3AicjRpM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2022 18:31:16 -0000

Colleagues,

Do PR actions also apply to other-than-email IETF communications such 
as Github, Slack, Zulip, and whatever new collaboration technologies 
we adopt in the future?

I propose that they should and that we should not need to revise BCP 
83 every time we add a new collaboration technology, and I'm hoping 
you agree with me.

As history, RFC 3683 was published in March 2004, around the same time 
the IETF was actively working on Jabber.

-- Sam