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

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 19 April 2019 14:44 UTC

Return-Path: <sarikaya2012@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 DD67B120235 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 07:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Iws7XuZRzC0F for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 07:44:54 -0700 (PDT)
Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) (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 DD644120166 for <ietf@ietf.org>; Fri, 19 Apr 2019 07:44:53 -0700 (PDT)
Received: by mail-yw1-xc29.google.com with SMTP id e76so1955198ywa.9 for <ietf@ietf.org>; Fri, 19 Apr 2019 07:44:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=dn0k/rJ21VK+GiLu/L6EMhLuFYsDXhXDa0/Q4YjOUBM=; b=fgdB/Hq2NHzqTlRebHoU7aVXLiKq1AT1xPkwWYsu97M8wIs3tsITbelE1hoe+bd+ly Db0bA1jrzhbsyKfjKUux1qmabHjY0O/oFMJxcHQLSCbtFLW5cJfBs9RgD0qBec+RKuFH I39pGiZ7V/AHMG1F0zXZdtAMGxUyTAOk2eU4nDI5drTY2rz4Z+nt/ZhDW9MS9j0YlI+z 3RH0BHVhrqeoRQTUnEnUTsOmjVElVzmxcjYF/rXj2SjwmXYBy+gqP17nXjs8zuVfqHDc iKrCJX+9ELMoKFNuMX7ySMp9Fx8rmCHVblCqiadQRwED+dA6ran6SL3a+YeZriGO3jiB XubA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=dn0k/rJ21VK+GiLu/L6EMhLuFYsDXhXDa0/Q4YjOUBM=; b=iZFc4z6+4qJY2YXClbEsYrhdZDsezSV4jUpyGS4ZhrstU9H0pw5jc+qKkVMLPvIJ4y AzDp8RUeyqpxAL+T/UKQiit6Rdhb9sUEwHcjB0Ad+x9QpC2L3qsTGLz2THFtsawi+xq9 7xYnMQRnala01rBBsphutV3qzLWbpOgSuTTDIDabLLdJY7LEAfLYDSvOTy8/vZb8KgWT PC306fDn6jKZ2PZJlM3m/2F2nkKmmPGN/7YHBIbn5QtuFdFZsjvqIVuRDkZGGcEZk5Oh BtTGwJJLxuUcnxHpEyVLZpW/l5YHbqzZCFPbXAooPz5epryrh7oKWvrN6M0oHXmjWbJN g4yw==
X-Gm-Message-State: APjAAAUj7Y/TbZHFWmffJ6zTk7659h5R5cynLF5xPnGS42fqGPTzZVrs yOenxBqxcZn64SqckyJqwU8yNs4IMJrREJ+I9OU=
X-Google-Smtp-Source: APXvYqyiOOLjEIaqgUW1uCGHZp2Nw6qhzbU/gILSMscsx3SdGwSBQArLdd/LrTe2XUrjO14icUqZv6TMPQLaW1nFa4A=
X-Received: by 2002:a0d:db43:: with SMTP id d64mr3150367ywe.346.1555685093024; Fri, 19 Apr 2019 07:44:53 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 19 Apr 2019 09:44:41 -0500
Message-ID: <CAC8QAcf=CswTTrxcsqWW7azwb97OMyh6iXFSx3=KhB9wtE8mEA@mail.gmail.com>
Subject: Re: exploring the process of self retiring one's name from an RFC
To: Christian Huitema <huitema@huitema.net>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, IETF Discussion <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
Content-Type: multipart/alternative; boundary="0000000000005a29a40586e3298a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yqhYz2006LTssigZgpX7zDqtKjY>
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 14:44:57 -0000

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 draft may quickly be progressed to become a new RFC to supersede
RFCxxx.

Regards,
Behcet


On Fri, Apr 19, 2019 at 9:09 AM Christian Huitema <huitema@huitema.net>
wrote:

>
>
>
> > On Apr 19, 2019, at 5:18 AM, Alexandre Petrescu <
> alexandre.petrescu@gmail.com> wrote:
> >
> > 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.
>
> In short, you are asking to remove your name of the authorship of and RFC
> because if you knew then what you know now, you would not have written the
> paper that way, nor signed it.
>
> Think about it.
>
> People change opinion all the time, for lots of reasons. Everybody makes
> what they think are mistakes. But the record is the record, and you don't
> get to change it.
>
> You filed an errata to remove your authorship. That errata should be
> rejected, because the document is not actually erroneous. It states that
> you were one of the authors at the time of publication, and there is no
> doubt about that. There is no error.
>
> -- Christian Huitema
>