Re: BCP 83 PR actions and new media
Toerless Eckert <tte@cs.fau.de> Fri, 25 November 2022 19:57 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 4467EC14CE55; Fri, 25 Nov 2022 11:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 2fwrndf0bPHK; Fri, 25 Nov 2022 11:56:55 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63F59C14F737; Fri, 25 Nov 2022 11:56:53 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 0DDDF54865A; Fri, 25 Nov 2022 20:56:49 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id E8F0C4EC116; Fri, 25 Nov 2022 20:56:48 +0100 (CET)
Date: Fri, 25 Nov 2022 20:56:48 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, exec-director@ietf.org
Cc: Samuel Weiler <weiler@csail.mit.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: BCP 83 PR actions and new media
Message-ID: <Y4EeAMdXbxUpTRV8@faui48e.informatik.uni-erlangen.de>
References: <e9c50be7-3dcf-cdf5-005b-f46a0777b04a@w3.org> <2bbed9bd-98a0-2635-2704-8baf3aa00165@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2bbed9bd-98a0-2635-2704-8baf3aa00165@cs.tcd.ie>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ehq8Vo1PlAAoEvxxEJ4uUbapK4E>
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: Fri, 25 Nov 2022 19:57:01 -0000
a) +1 b) At the risk of rightfully getting slapped by John Daley by sending more work suggestions his way, i wonder if there might be specifically helpfull questions to be asked in his next community feedback to help such "down-the-road" re-considerations for BCP 83. I for once would primarily wonder what it would tell us about the BCP 83 process if a questionaire would show that an overwhelming amount of IETF participants is not aware and does not care. Sorry, really just open ended thoughts. I am all out of opinions. CHeers Toerless On Sun, Nov 13, 2022 at 09:32:21PM +0000, Stephen Farrell wrote: > > Hiya, > > On 09/11/2022 18:31, Samuel Weiler wrote: > > 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. > > FWIW, I understand the dissonance, but disagree that BCP83 > ought apply to anything other than mailing lists, as of now. > Chat rooms such as provided by zulip are an integral part of > meeting attendance (whether remote or in-person) and I don't > read BCP83 as encompassing controls as to who can attend > meetings. I do agree that if/when we revise BCP83 we ought > discuss this topic and make some changes though. (As I said > in the other thread, I hope we wait a year or more before > starting work on an update to BCP83.) > > Cheers, > S. > > > > > > > -- Sam > > -- --- tte@cs.fau.de
- Re: BCP 83 PR actions and new media Keith Moore
- BCP 83 PR actions and new media Samuel Weiler
- Re: BCP 83 PR actions and new media John C Klensin
- Re: BCP 83 PR actions and new media Lars Eggert
- Re: BCP 83 PR actions and new media Abdussalam Baryun
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Joel Halpern
- Re: BCP 83 PR actions and new media Samuel Weiler
- Re: BCP 83 PR actions and new media Lars Eggert
- RE: BCP 83 PR actions and new media Rob Wilton (rwilton)
- RE: BCP 83 PR actions and new media Maisonneuve, Julien (Nokia - FR/Massy)
- RE: BCP 83 PR actions and new media Maisonneuve, Julien (Nokia - FR/Massy)
- Re: BCP 83 PR actions and new media Ofer Inbar
- RE: BCP 83 PR actions and new media Daniele Ceccarelli
- RE: BCP 83 PR actions and new media Daniele Ceccarelli
- Re: BCP 83 PR actions and new media Paul Wouters
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Brian E Carpenter
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Brian E Carpenter
- Re: BCP 83 PR actions and new media Lloyd W
- Re: BCP 83 PR actions and new media Abdussalam Baryun
- Re: BCP 83 PR actions and new media Keith Moore
- Re: BCP 83 PR actions and new media Pete Resnick
- Re: BCP 83 PR actions and new media Stephen Farrell
- Re: BCP 83 PR actions and new media Toerless Eckert