Re: RFC793#ietf.org (was: Re: Proposed ietf.org email address policy)
Toerless Eckert <tte@cs.fau.de> Fri, 11 June 2021 20:14 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 414713A141D for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 13:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 FW8PigFm9cbm for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 13:13:59 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF74D3A141B for <ietf@ietf.org>; Fri, 11 Jun 2021 13:13:58 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1DB8354806A; Fri, 11 Jun 2021 22:13:52 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 10C014E772A; Fri, 11 Jun 2021 22:13:52 +0200 (CEST)
Date: Fri, 11 Jun 2021 22:13:52 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, John C Klensin <john-ietf@jck.com>, Lloyd W <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org>, IETF <ietf@ietf.org>
Subject: Re: RFC793#ietf.org (was: Re: Proposed ietf.org email address policy)
Message-ID: <20210611201352.GE36947@faui48e.informatik.uni-erlangen.de>
References: <CAKKJt-evvxAN75T5YRyGsTZMgwnjO+UJgHevS1vb6GtTZ1gMaw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKKJt-evvxAN75T5YRyGsTZMgwnjO+UJgHevS1vb6GtTZ1gMaw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rlXWiD8gKKnLY4r-5SOWyNSx-AI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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, 11 Jun 2021 20:14:04 -0000
Spencer: I think i asked the tools team similar questions and i think the answers where: - there are not and never where rfc*@ietf.org aliases. - draft-*@ietf.org aliases are also retired after a while. I think something like one or two years after expiry or becoming RFC (cannot remember). Extrapolating from todays discuss also about stable addresses such as name@members.ietf.org, i have to conclude that you will get any positive feedback from the IETF tools team to improve communications about RFC than what we have today: -> To figure out current adresses of authors you have to name match them on datatracker and hope they have an account there and are updating their email addresss, and if they do not have any active role or recent RFC put their current email into the bio section (which almost nobody has). -> To figure out a working group or non-working group mailing list address to discuss an RFC you first need to track back the WG and hope its list wasn't closed without being superceeded when it is closed. Now, of course this is all convoluted and also IMHO not as good as it could be, but then in fairness to IETF tooling: Show me an SDO that does better. Cheers Toerless On Fri, Jun 11, 2021 at 02:51:56PM -0500, Spencer Dawkins at IETF wrote: > Following up on one point ... > > On Fri, Jun 11, 2021 at 12:31 PM Michael Richardson <mcr+ietf@sandelman.ca> > wrote: > > > > > I know we have draft-xxx@ietf.org aliases, and those can get updated via > > the > > DT, I'm unclear if I can email rfcxxxx@ietf.org to reach the authors, and > > that's not what's listed in the RFC. > > > > I just made sure - I sent to the address that would be my most recent RFC, > and got back "550 5.1.1 <rfc8462@ietf.org>: Recipient address rejected: > User unknown in virtual alias table". > > So, that's a "nope". > > The minor question is that I'd expect such addresses to be > RFC793@rfc-editor.org(*) addresses, but let's ignore that for now. > > We might be able to pull this off, going forward, but we're doing AUTH48 on > drafts in the 9040 range now. I'd bet that there are a *lot *of past > authors who aren't reachable at an email address that the RFC Editor knows > about for a variety of reasons > > So it would be good to figure out what the objective would be - to find > someone who might still be knowledgeable about the topic of the RFC, or > still caring about the topic of the RFC, or still reading e-mail, or what, > exactly? > > One objective might be to find someone who "is responsible for" the RFC - > I was chasing down who was responsible for the work produced by a concluded > WG, literally "yesterday", so that objective seems worthy, but I'm sure > there are others. > > Best, > > Spencer > > (*) Yes, I chose one of Jon Postel's RFCs on purpose ... ????
- RFC793#ietf.org (was: Re: Proposed ietf.org email… Spencer Dawkins at IETF
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… Toerless Eckert
- Re: lots of dead addresses, was RFC793#ietf.org (… John Levine
- Re: lots of dead addresses, was RFC793#ietf.org (… Carsten Bormann
- Re: lots of dead addresses, was RFC793#ietf.org (… Michael Richardson
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… John C Klensin
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… John Levine
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… Carsten Bormann
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… Michael Richardson
- Re: RFC793#ietf.org (was: Re: Proposed ietf.org e… Spencer Dawkins at IETF