Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site

Alessandro Vesely <vesely@tana.it> Thu, 06 September 2012 17:06 UTC

Return-Path: <vesely@tana.it>
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 0AD8421F870E for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2012 10:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.595
X-Spam-Level:
X-Spam-Status: No, score=-4.595 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyWHT1HZIFj9 for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2012 10:06:05 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id D8B2621F86A8 for <ietf@ietf.org>; Thu, 6 Sep 2012 10:06:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1346951161; bh=cSDK+Lfh242QF66Amz7MET5tL1kVr9FzUvpZDjjheOY=; l=1895; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=HFnKzcsIXakDzGsttk5+0K53DZ/S+nb99kgiAEUIGEea9niQq/T2cLoGoPaikCw/n UfmsFl+6iLALgwkKGf62AHvZhIZFYnBclFHxltY3KNtJxpIfbL6VIB25F3sX6u+EfE j4VsqUrP6HGkNQd4zxIRnblBkO+QZMsLhz4SC9eY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 06 Sep 2012 19:06:01 +0200 id 00000000005DC04A.000000005048D7F9.00004675
Message-ID: <5048D7F8.2030906@tana.it>
Date: Thu, 06 Sep 2012 19:06:00 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com> <6.2.5.6.2.20120905104856.0ad916a8@resistor.net> <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
In-Reply-To: <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 06 Sep 2012 17:06:06 -0000

On Wed 05/Sep/2012 21:59:56 +0200 John C Klensin wrote:
> --On Wednesday, September 05, 2012 11:02 -0700 SM <sm@resistor.net> wrote:
>> At 09:04 05-09-2012, Brian E Carpenter wrote:
>>> That's an interesting but not very informative statement.
>> 
>> http://www.ietf.org/mail-archive/web/ietf/current/msg71391.html
> 
> Of course, there is a case to be made that, if we had a more
> sophisticated posting system that enforced the few rules we
> already have, it would not have been accepted and posted in the
> first place.  Individual drafts are supposed to be title
> draft-OneOfTheAuthorNames-foo-bar-NN.  This one didn't meet that
> rule.

The I-D /was/ named after one of the author names.  Although expired,
http://tools.ietf.org/html/draft-ordogh-spam-reporting-using-imap-kleansed
is still accessible.

> From the standpoint of those rules/conventions about naming at
> least, it is as if I posted something as draft-moonesamy-foobar-00
> or draft-carpenter-barfoo-00 in the hope that would get extra
> attention.

I removed much more than I added, so putting my name would have been
overly selfish.

> That said, the author in this particular case could presumably have
> posted draft-vesely-spam-reporting-using-imap-kleansed-00 and then
> persuaded the Secretariat that it replaced 
> draft-ordogh-spam-reporting-using-imap-kleansed-00, thereby causing
> the latter to be removed from the _active_ I-D repository and moved
> off to the historical I-D archive.

That maneuver sounds more contrived than what I did.  I thought about
posting a new version with null content, or possibly with tombstone
text, but that would still have left version 00 in place.

In order to invalidate an archived version, we'd need a process
mechanically similar to rfc-editor's "Errata".  If visually winsome,
Errata's content could then be rendered the new way as well.