IETF Logo Mail Archive

Re: [rfc-i] [Rfced-future] RSWG & AUTH48 (was Re: [admin-discuss] Public archival of AUTH48 communications)

Toerless Eckert <tte@cs.fau.de> Thu, 03 March 2022 07:53 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E123A141A; Wed, 2 Mar 2022 23:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level:
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 oQNkaZtYNcSP; Wed, 2 Mar 2022 23:53:25 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AFCD3A12C2; Wed, 2 Mar 2022 23:53:25 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 442FA3BAA5; Wed, 2 Mar 2022 23:53:25 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id E6E033BAA5 for <rfc-interest@rfc-editor.org>; Wed, 2 Mar 2022 23:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iXH1wBPScTmI for <rfc-interest@rfc-editor.org>; Wed, 2 Mar 2022 23:53:20 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) by rfc-editor.org (Postfix) with ESMTPS id C10B63BA9D for <rfc-interest@rfc-editor.org>; Wed, 2 Mar 2022 23:53:19 -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 5CF61549FC5; Thu, 3 Mar 2022 08:53:12 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 402E64EA7EF; Thu, 3 Mar 2022 08:53:12 +0100 (CET)
Date: Thu, 03 Mar 2022 08:53:12 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <YiBz6FNcjxrwiHVS@faui48e.informatik.uni-erlangen.de>
References: <EEF0F457622EDF74E090BC66@PSB> <BEB26FE0-CC24-4EC2-B7E5-6556A2425A24@eggert.org> <11721.1646248947@localhost> <af3a9d13-7ec2-4e48-355a-a3870af06361@joelhalpern.com> <a52626d5-13aa-ab1a-cb13-282bd9bcf812@gmail.com> <269b5f09-4840-b038-085c-839e0a1c3c6b@huitema.net> <YiBc6Mjj2++jxE0h@faui48e.informatik.uni-erlangen.de> <D5AC5684-506B-4214-9678-75B5C1FCBED2@tzi.org> <YiBjw7P7CW5Lf2oH@faui48e.informatik.uni-erlangen.de> <A9CDA47A-9CA0-4CF4-ABDC-4F0821F2349D@tzi.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <A9CDA47A-9CA0-4CF4-ABDC-4F0821F2349D@tzi.org>
Subject: Re: [rfc-i] [Rfced-future] RSWG & AUTH48 (was Re: [admin-discuss] Public archival of AUTH48 communications)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfced-future@iab.org, RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Thu, Mar 03, 2022 at 07:51:46AM +0100, Carsten Bormann wrote:
> > Let me rephrase: How would you describe the responsibitiles and
> > accountabilities to improve the process ?
> > 
> > "Make it public and let them come" ?
> 
> Yes.
> Those who truly care about an RFC-to-be are likely to come if we don’t make access too onerous.

Not necessarily those who might have the best input though.

Aka: this can IMHO only be a secondary add-on option and
must not replace some primary responsibility of authors/AD/shepherd/rfc-editor
to alert the right expert/groups from whom to explicitly seek
input if/when such a situation arises during AUTH48.

> > ("All the planning charts and demolition orders have been on display at your local planning department…")
> 
> Yes, but the first thing to alert you is the status change on the I-D.
> You have subscribed to the status changes, no?

I am not aware of any status changes during auth48 to be publically available.
But lets assume we would add that.

Which publically available status change notification system are you
referring to ? All events on planet earth, the just slightly less
poluted i-d-announce mailing list or something more specific i can
easily subscribe to. I am not aware of the latter.

Cheers
    Toerless
> 
> Grüße, Carsten

-- 
---
tte@cs.fau.de
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.40.4 | Report a Bug | By Email | System Status