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:23 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 9E98512004A for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 13:23:36 -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 GcjaTzEaAGQS for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 13:23:34 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 C390C120119 for <ietf@ietf.org>; Fri, 19 Apr 2019 13:23:34 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id c207so2983851pfc.7 for <ietf@ietf.org>; Fri, 19 Apr 2019 13:23:34 -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=olW7DwoWUWu4ZbEKfWPvCiNSOMxTIWeaY9zeM3vZ+eo=; b=ILo2Sgd8j0Ro5Dad92ok+5AwmZxSPpzRTUctPRXL7gpijnHqCI5QkM7+XSRUnrprWR wVHbfCNozpbFiINl/pfbGk7r1iHnKEjzTLEocQ1W5JtXFW6/McNTiuav3qCs5W3pfyLj yTgAk+pC57wec3RmuFRzJJo1UzP77usQJtYCTlitnllBBX8OGFgGWjlAGWQvrvmoo2l2 LaMSua4PedMJLIxMetRuSFqRtDZHSSPi2aDfgI+3Y3htEx7tpfzLMR5oiyVF9U6aMbH/ B8HOAWaiHfroIX8thd3958jdMCBkoZiiANMSr/f1I2YnlC4B7w3ttZZsZnxDyvJPkXdN nqXA==
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=olW7DwoWUWu4ZbEKfWPvCiNSOMxTIWeaY9zeM3vZ+eo=; b=jnzUMBBcJEZubk+uKwcJq0YQgHfTX79yauskRKTPTRhfs2pSdaAFtMqBzr47J9fLdy YN5BqiF0TScnKrpQL+KQcguC/iC2gT8PxiP/m/C0SutrvP5Rib9otNDRQgiF6axoiVhV /inWSBTHZYHJVQbrgQ8w4K5YSMhSqPltYRWhUi4xfsrPt3CXaDyS7SUrm0B0h6Ely/Gr Jd8kxiPaZTQ222wbAmDrcE1nbmYuE1eH+ez+pjzGonKazvnIDYckBltvNyACG0Qi53Fr AzLppd4Zz8NHZZI5467u9YEO/1xo6j8ZILPLe3LvMsf3W85tE0uNftQjwoDk0erOk4vA ocIg==
X-Gm-Message-State: APjAAAVuOG7DokeanKlLPyAMQlDoSvEDC1Dq+MzCXIx5YcF7MnI27jAm mNeAg67llees5yoCibc1N7s=
X-Google-Smtp-Source: APXvYqwCRQI48z/ppoA60xpCe+gcfT3t1f4VmGWvCkff43K84FjgqqitqN45S2Uad+FfJe2raBDayQ==
X-Received: by 2002:a63:8f4b:: with SMTP id r11mr5739739pgn.271.1555705414377; Fri, 19 Apr 2019 13:23:34 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id e21sm7497654pfd.177.2019.04.19.13.23.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Apr 2019 13:23:33 -0700 (PDT)
Subject: Re: exploring the process of self retiring one's name from an RFC
To: Eric Rescorla <ekr@rtfm.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, IETF Discussion <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
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> <04e9ef58-98ce-fcef-fb3e-036c21a19d67@gmail.com> <CABcZeBMi-s_CQM5kvNK963TqJOOt7aNBHXkTh0mD8ozBf9mshw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0d7e5939-81e0-02ac-403e-bd8baa80e516@gmail.com>
Date: Sat, 20 Apr 2019 08:23:31 +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: <CABcZeBMi-s_CQM5kvNK963TqJOOt7aNBHXkTh0mD8ozBf9mshw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lAV-RoJH5ruLNaeNYu12QLwDFRY>
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:23:37 -0000

On 20-Apr-19 03:22, Eric Rescorla wrote:
> Without taking a position on this specific case, it seems like there
> are some interesting questions here.
> 
> Consider the hypothetical case where I falsely obtain an RFC in the
> name of some other person (don't worry about how, say they are on
> sabbatical and I guess their password). They then rightly object to
> the RFC being in their name. What do we do? I'm guessing the answer
> is going to be "withdraw the RFC and issue a new one without that
> author and with a different number"?

If such a blatant abuse happened, I've no doubt that the RFC Editor
would act appropriately. "Do the right thing", as Spencer reminds us.

But in this particular case, I could go back through email to find the
bits that Alexandre contributed. The document was intentionally
written as factual analysis, at a given point in time, and not as
a recommendation. It's part of the historical record.

The place for change is draft-ietf-6man-rfc4291bis, which is in
limbo since we haven't found consensus.

   Brian

v2.23.0 | Report a Bug | By Email