IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 19 April 2019 20:13 UTC

Return-Path: <brian.e.carpenter@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 29E07120175 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 13:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 L7furth8HziB for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 13:13:46 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 9F0DF12004A for <ietf@ietf.org>; Fri, 19 Apr 2019 13:13:46 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id c207so2975707pfc.7 for <ietf@ietf.org>; Fri, 19 Apr 2019 13:13:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=YElFUbohVWZ9yywISnOVqgSbRU3tnhD0HypEajp8n+k=; b=r04pHy+vsPqYl+NK+cRrRECjlwrPhvWLRSLFgmNio0PLEgn2TK+DYLAS5AeBf98FrC zoRCq11VQCqAf2lGq9g9cG2IbyYa7XbVj36dIj1Kr1OsQtPZDX5UwGbza7mhb55FnnZt sTstR03QsZaCTH756WrN/Z+t+F2//43372Ng5HC68MNrkm3B09o1GvlZAlll+0O0fDG2 ygVhgoTpoRO9kP4O42/vMMW9H0t/wiugjAS9GI+7JR+hZggmpqV6JT3aSg0wIK/F6fye XzePnLNaMgcBP7A9OtUuDeqresl7oEdShnTBDEpCUb36aJMmK834IMhexvWPdycIMQ8h ztYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YElFUbohVWZ9yywISnOVqgSbRU3tnhD0HypEajp8n+k=; b=r2Xv5SRYIqR+RLW0NU+z0jsm8zCBIXQ9HXJwToYl3BuK040tVsF1MFTRlX1m2o43Wl KQKsUEefwqpszuaEdcJADwB/T79yl/fkbSUngMir2wa83VQlp0VXL6uQS29QpF0dukYA b5+G54o+qeXOzGk9OokkwlLXoxXNC99CU2pYaVbIj8yC0pf5YfYUrbmxk992iS/5ge4O 5yqdJ/U7TshxrNJ49pHg5Zz3LovZ9VB3YZ3nctxQP58kokPqrPVRfLyvwNtke+DDg2kY KT3i4guJdE1GZMxsTkvNDhdRNyPnVtDAJ1HrBv6sV4kNJCIXIiP2HTheAiFqTLcRJUg0 /2WA==
X-Gm-Message-State: APjAAAWFHG2NX6OAn8jtTyWeVS2KttBkxkb2fVr70qzVz3aGSOFb2sc4 OoWZuY23975Z6M7Pb5IZNL7KORks
X-Google-Smtp-Source: APXvYqwj1RhkwniedXCRy+2pr0xZCZJ9dCWUkyTEB25iyTRfT87cHB+J2OjDWBnLNBIn2/kAKn8uYg==
X-Received: by 2002:a62:5707:: with SMTP id l7mr6077201pfb.205.1555704825803; Fri, 19 Apr 2019 13:13:45 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id l2sm6165441pgl.2.2019.04.19.13.13.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Apr 2019 13:13:45 -0700 (PDT)
Subject: Re: exploring the process of self retiring one's name from an RFC
To: sarikaya@ieee.org
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> <13a585d3-ff7c-757d-3f5d-d60be289e0d1@gmail.com> <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net> <CAC8QAcf=CswTTrxcsqWW7azwb97OMyh6iXFSx3=KhB9wtE8mEA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d20d7980-ca12-173e-7ce8-77a85ce639a1@gmail.com>
Date: Sat, 20 Apr 2019 08:13:43 +1200
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: <CAC8QAcf=CswTTrxcsqWW7azwb97OMyh6iXFSx3=KhB9wtE8mEA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/18JNKH_CSVDx7-bh6w9CoiaryRg>
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 20:13:48 -0000

On 20-Apr-19 02:44, Behcet Sarikaya wrote:
...> 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 draft may quickly be progressed to become a new RFC to supersede RFCxxx.

Why would the co-authors, the IETF, and the RFC Editor agree to a falsification of history? I suggest re-reading the novel "1984" for further elaboration of this point. Deleting authors is a very Stalinist approach to history.

  Brian (co-author of RFC7421, which by the way makes no recommendations whatever)

v2.23.0 | Report a Bug | By Email