IETF Logo Mail Archive

Re: [Tools-discuss] emailing authors of an RFC

Sandy Ginoza <sginoza@amsl.com> Thu, 13 June 2019 17:21 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71402120123 for <tools-discuss@ietfa.amsl.com>; Thu, 13 Jun 2019 10:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 PSjfCsm5E9VA for <tools-discuss@ietfa.amsl.com>; Thu, 13 Jun 2019 10:21:07 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AFE12011C for <tools-discuss@ietf.org>; Thu, 13 Jun 2019 10:21:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 29B5A1C3DB8; Thu, 13 Jun 2019 10:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNM5rnzLQ9sw; Thu, 13 Jun 2019 10:20:48 -0700 (PDT)
Received: from [IPv6:2605:e000:1524:de:e462:b66b:56e9:f8de] (unknown [IPv6:2605:e000:1524:de:e462:b66b:56e9:f8de]) by c8a.amsl.com (Postfix) with ESMTPSA id C89E91C3DB6; Thu, 13 Jun 2019 10:20:47 -0700 (PDT)
From: Sandy Ginoza <sginoza@amsl.com>
Message-Id: <B97AF188-5ADF-41FE-870A-DED7BFB9E51B@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_83367C9E-8A73-40C4-BA06-4F22FBD872D4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 13 Jun 2019 10:20:11 -0700
In-Reply-To: <8203EB90-A7D1-41E4-98E6-310B339A2941@gmail.com>
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Michael Richardson <mcr+ietf@sandelman.ca>, Carsten Bormann <cabo@tzi.org>, Tools Team Discussion <tools-discuss@ietf.org>, Heather Flanagan <rse@rfc-editor.org>
To: Bob Hinden <bob.hinden@gmail.com>
References: <20190612150100.84AF538185@tuna.sandelman.ca> <31204.1560354351@localhost> <b2d9819e-9174-590e-6de0-ab557e28bd6b@levkowetz.com> <13329.1560365123@localhost> <c1c2f69b-cf24-c6ab-6dcd-1c0dbc907bd0@levkowetz.com> <CBDC4F38-7984-4171-95AE-C05C4A74D07C@tzi.org> <9de6bcc1-2965-eeb0-a200-5581867db81b@levkowetz.com> <8203EB90-A7D1-41E4-98E6-310B339A2941@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/esTOzfErr_DhZS4f8amRcGalrkM>
Subject: Re: [Tools-discuss] emailing authors of an RFC
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2019 17:21:10 -0000

Hi all,

Adding Heather to the thread.  

I think this is a reasonable thing that could be added to the RFC info pages.  My main concern is the ongoing maintenance effort if the underlying addresses are supposed be kept current.  Henrik, if any of the underlying addresses become stale with the existing aliases, what happens?  Do you have a method for keeping them up to date? 

Michael, just curious - what’s your use case for this?  Currently on the info pages, we have text suggesting the user email the WG if they want to discuss the RFC; for example, this is what appears for RFC 7030:
Discuss this RFC: Send questions or comments to pkix@ietf.org <mailto:pkix@ietf.org?subject=Question%20regarding%20RFC%207030>

Thanks,
Sandy

> On Jun 13, 2019, at 8:22 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> Henrik,
> 
>> On Jun 13, 2019, at 6:18 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>> 
>> 
>> On 2019-06-13 08:39, Carsten Bormann wrote:
>>> On Jun 12, 2019, at 22:14, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>>>> 
>>>>> Do we have author aliases for RFCs?  Maybe we don't.
>>>> 
>>>> No.  Not sure if we should.
>>> 
>>> Yes, we should.  (See the discussion over at 
>>> Archived-At: ⁨<https://mailarchive.ietf.org/arch/msg/anima/sfev_MdLg-cgZTVFxE8jl3SQCIo>⁩
>>> for an example why this would be a good idea.)
>> 
>> Let me clarify.  I wasn't trying to say that RFC author aliases wouldn't be
>> a good thing, I was questioning whether the IETF should provide these, rather
>> than the RFC Editor.
> 
> I agree, this is a question for the RFC Editor.
> 
> Personally, I am not sure I see too much value, as maintaining an alias over many years will be difficult.  Especially for people who don’t contribute frequently.  But that is again a question for the RFC Editor.
> 
> Thanks,
> Bob
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org

v2.23.0 | Report a Bug | By Email