Re: exploring the process of self retiring one's name from an RFC
Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 April 2019 12:18 UTC
Return-Path: <alexandre.petrescu@gmail.com>
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 B6B161200EA for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 05:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 jvLnshhrXvAm for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 05:18:14 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FE8512009C for <ietf@ietf.org>; Fri, 19 Apr 2019 05:18:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JCICRY084656; Fri, 19 Apr 2019 14:18:12 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0D4402063F8; Fri, 19 Apr 2019 14:18:12 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F3AB0206201; Fri, 19 Apr 2019 14:18:11 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JCIBOG023447; Fri, 19 Apr 2019 14:18:11 +0200
Subject: Re: exploring the process of self retiring one's name from an RFC
To: Jared Mauch <jared@puck.nether.net>
Cc: IETF Discussion <ietf@ietf.org>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <00fde7c6-c8a4-508e-5735-056647cdfb52@gmail.com> <9E3D5C77-C1C8-4D22-97BF-B97324C7DFCC@puck.nether.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <13a585d3-ff7c-757d-3f5d-d60be289e0d1@gmail.com>
Date: Fri, 19 Apr 2019 14:18:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <9E3D5C77-C1C8-4D22-97BF-B97324C7DFCC@puck.nether.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lO_ZKomAyV4MOc3rKqolzvD7S9o>
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, 19 Apr 2019 12:18:17 -0000
Le 19/04/2019 à 13:55, Jared Mauch a écrit : > > >> On Apr 19, 2019, at 7:28 AM, Alexandre Petrescu >> <alexandre.petrescu@gmail.com> wrote: >> >> Hi Scott, >> >> Thank you for the reply. >> >>> Re: exploring the process of self retiring one's name from an >>> RFC "Scott O. Bradner" <sob@sobco.com> Fri, 19 April 2019 10:14 >>> UTCShow header RFCs are not changed after they are published so >>> removing one’s name from a existing RFC cannot be done. >> >> Errata? > > Perhaps. They are requests for comments. One of the comments may be > that technology has changed, or risk profiles (or any number of other > assumptions or realities have been bent). I think retiring > authorship isn’t really a useful way, but is the perpetual archive of > comments just the e-mail archives or should there be a more prominent > way for an author to submit comments for the historical record? With respect to questioning the kinds of comments that could be put: - it's not because the technology has changed that I need my way removed from it. - there is no new risk profiles. - the reality has bent in the sense that the 64bit boundary seems to be imposed now in all new IPv6-over-foo RFCs. It was so in the past (before the RFC), and I was hoping the RFC to change that tendency. The reality is that since that RFC many other IP-over-foo documents have been written, and each time the recommendation is still to use 64bit IID. That was not my intention when co-authoring that RFC. I got into it to falsely believe the recommendation would happen in - what was at the time - the future. With respect to improved usefulness of a perpetual archive to insert up to date feedback (comments answering the Request for Comments): I think it sounds natural and it makes sense. That can not be the email list of the WG having developed the RFC, because it gets shut down. That perpetual archive can not be a new Internet Draft because that expires if not adopted by a WG, which is itself subject to come and go of people. Alex > > - Jared > >
- exploring the process of self retiring one's name… Alexandre Petrescu
- Re: exploring the process of self retiring one's … Scott O. Bradner
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Jared Mauch
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Christian Huitema
- Re: exploring the process of self retiring one's … Behcet Sarikaya
- Re: exploring the process of self retiring one's … Keith Moore
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Eric Rescorla
- Re: exploring the process of self retiring one's … Paul Wouters
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Aaron Falk
- Re: exploring the process of self retiring one's … Paul Wouters
- Re: exploring the process of self retiring one's … John C Klensin
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … John Levine
- Re: exploring the process of self retiring one's … ned+ietf
- Re: exploring the process of self retiring one's … Marco Davids
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Randy Bush
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Tim Chown
- Re: exploring the process of self retiring one's … Alexandre Petrescu