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

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

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26FC93A1333 for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 00:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, 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 ryDclfQXO-2E for <rfced-future@ietfa.amsl.com>; Thu, 3 Mar 2022 00:22:02 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10F7B3A1332 for <rfced-future@iab.org>; Thu, 3 Mar 2022 00:22:01 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 8DA15549AF2; Thu, 3 Mar 2022 09:21:54 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 797A64EA7F0; Thu, 3 Mar 2022 09:21:54 +0100 (CET)
Date: Thu, 03 Mar 2022 09:21:54 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: rfced-future@iab.org, RFC Interest <rfc-interest@rfc-editor.org>
Message-ID: <YiB6onawMbNZlYI0@faui48e.informatik.uni-erlangen.de>
References: <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> <YiBz6FNcjxrwiHVS@faui48e.informatik.uni-erlangen.de> <DCED11B7-B942-4183-830A-08FE69132B4F@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <DCED11B7-B942-4183-830A-08FE69132B4F@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qMLNkO9XB_MEck77JVaDJzawCts>
Subject: Re: [Rfced-future] [rfc-i] RSWG & AUTH48 (was Re: [admin-discuss] Public archival of AUTH48 communications)
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2022 08:22:07 -0000

On Thu, Mar 03, 2022 at 09:06:26AM +0100, Carsten Bormann wrote:
> Processes are much easier to design if you know everyone will always do their tasks perfectly and on time.
> (In Software Engineering, we call this process confabulation.)
> 
> Yes, public AUTH48 is a small additional safety net, and a very thin one.

Right. Thats how it should be described/sold.

> >>> ("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.
> 
> During AUTH48 — yes, you have to follow the list.

Which would depend on someone making an issue public during AUTH48.
Which  we seem to believe may not be sufficient. 

> > Which publically available status change notification system are you
> > referring to ?
> 
> 1 Go to https://datatracker.ietf.org/wg/core/documents/ (for a WG of your choice)
> 2 Scroll to the end
> 3 Click “Subscribe to changes” (or “Change subscription”)
> 4 Fill in the form (“All changes”).  Submit.
> 5 Profit from the magically improved situational awareness you now have achieved.

Thanks!

> I don’t know how to subscribe to AD-sponsored documents, though.

Actually seems to be possible (luckily) to enable for non-wg docs, like
draft-iab-rfcefdp-rfced-model, at least i found a "Track" thingy to click
on for it just on the datatracker page for the doc itself. Let's see if it works.

(i was actually looking long on the page to find something and didn't, and
 only after you sent your explanation did i find the "track" thingy on the
 documents page, so i am sure that features you're not made aware of first
 really don't exist ;-)

Cheers
    Toerless

> (You can also get an atom feed.)
> 
> > 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.
> 
> See above.
> 
> 
> Grüße, Carsten

-- 
---
tte@cs.fau.de