Re: exploring the process of self retiring one's name from an RFC

Keith Moore <moore@network-heretics.com> Fri, 19 April 2019 15:05 UTC

Return-Path: <moore@network-heretics.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 5C9321202F2 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 08:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 MUBxpKF6t3bj for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 08:05:49 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888431202F1 for <ietf@ietf.org>; Fri, 19 Apr 2019 08:05:49 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id CB767532; Fri, 19 Apr 2019 11:05:46 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 19 Apr 2019 11:05:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=7KxMy/xg1w+KQNGGIdT5W8ltbASSh/YuThRe4gxaQ sQ=; b=OOAQllq6krPmTjsR3SSrUGLWbj68vTyhXx3hLzCzQtUMmYtCP5A3EAKJi JwczLYIcrbnoSUroUeS0QFcqrAVryBmlEWCSYCxEeX3Zwn1c4kCQZQRCEZjlsjQN XF9cjEWjeaqMuhsAFP5alUpaK8hDRXXBDo9LJxiSTwfj/XyEtc/oDatGNr4zHXkn YNTlt8cuHO8LI6WDaJeg8fO7n2hKPN+ggtv+fIIcYWU99dX93eRBYtw/H8IZcP5x ETJ8qK31iCh8PTR25mvHrHMmiQFOwFiuKTwTSJjVQXn8eAXfshkLG2tQ7WYyYNkY HEjPS6TyDv/baBTp9Wbf9KCA+/7eA==
X-ME-Sender: <xms:yuO5XKtIF2_VBkVmvGGVFDr9EaMIzILIw8tyiLYY9mIkeJv59_NZHw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrfeejgdejjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgv thhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:yuO5XOsz1N6BiJQaEV7B6G3_Y-hgVDM7I1OQIQYfDw8e-XCyX1ODNQ> <xmx:yuO5XB_SA2zqgiVe2OPLm8haVMxfjhWyxXxfKwV5Tap02EF9mI86gw> <xmx:yuO5XP-J7Z6HaRjy0xaku2-lRVtNf4WCM4pG2bWcOrjfVzSRrnMdGA> <xmx:yuO5XJOsVJuILxROBgb9tUQ3n3j_CLF0X06ND-_bct54UVOfjOc9OQ>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 00EA8E4173; Fri, 19 Apr 2019 11:05:44 -0400 (EDT)
Subject: Re: exploring the process of self retiring one's name from an RFC
To: 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> <13a585d3-ff7c-757d-3f5d-d60be289e0d1@gmail.com> <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net> <CAC8QAcf=CswTTrxcsqWW7azwb97OMyh6iXFSx3=KhB9wtE8mEA@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <7b5093f3-5b56-b118-67c2-b94db90fe47f@network-heretics.com>
Date: Fri, 19 Apr 2019 11:05:44 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAC8QAcf=CswTTrxcsqWW7azwb97OMyh6iXFSx3=KhB9wtE8mEA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/maDZ3mqpTcfgrcYZxPwtvT_XQx8>
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 15:05:51 -0000

On 4/19/19 10:44 AM, Behcet Sarikaya wrote:

> I agree with Christian.
>
> Alex, my suggestion is to write a new draft call it 
> draft-someone-rfcxxxbis with the current text on the RFC minus you as 
> the author.
> Maybe you can not submit it you need to ask one of the co-authors to 
> submit.
>
That's a bad idea also.   The other authors' opinions in the past may 
not be their opinions now, and submitting their old text today as a new 
draft would presume that their opinions haven't changed.

The RFC is what it is, a record of some people's thoughts as of the time 
it was published.  Anyone who has been around this community very long 
realizes that he or she was once wrong about something he or she wrote 
in the past.   We just need to accept that and move on.

Keith

p.s. The 64-bit boundary was always a dubious idea in much the same way 
as hardwired IPv4 address "classes" were a dubious idea.   I would 
support phasing it out, even with the understanding that prefixes past 
/64 won't work for many existing IP-over-foo mechanisms.   To the extent 
that we can change some of those IP-over-foo mechanisms, it's probably 
worth doing so.