Re: Status of draft-christey-wysopal-vuln-disclosure-00.txt

Robert Elz <kre@munnari.OZ.AU> Tue, 24 September 2002 15:10 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01495; Tue, 24 Sep 2002 11:10:49 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA01087 for ietf-outbound.10@loki.ietf.org; Tue, 24 Sep 2002 11:12:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id KAA00719 for <ietf-mainout@loki.ietf.org>; Tue, 24 Sep 2002 10:53:23 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00467 for ietf-mainout@loki.ietf.org; Tue, 24 Sep 2002 10:51:32 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from ratree.psu.ac.th ([202.28.97.9]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08291 for <ietf@ietf.org>; Tue, 24 Sep 2002 01:37:59 -0400 (EDT)
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98]) by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id g8O5bB307799; Tue, 24 Sep 2002 12:37:12 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id g8O5aQ723840; Tue, 24 Sep 2002 12:36:29 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Donald Eastlake 3rd <dee3@torque.pothole.com>
cc: ietf@ietf.org, Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Status of draft-christey-wysopal-vuln-disclosure-00.txt
In-Reply-To: <Pine.LNX.4.44.0209231438210.2872-100000@netbusters.com>
References: <Pine.LNX.4.44.0209231438210.2872-100000@netbusters.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 24 Sep 2002 12:36:26 +0700
Message-ID: <23838.1032845786@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk
X-Loop: ietf@ietf.org

    Date:        Mon, 23 Sep 2002 14:44:06 -0400 (EDT)
    From:        Donald Eastlake 3rd <dee3@torque.pothole.com>
    Message-ID:  <Pine.LNX.4.44.0209231438210.2872-100000@netbusters.com>

  | Drafts expire in six months and get automatically removed

Eventually, which I think is relevant here.   The draft in question
has passed its expiry date, but has not yet been expired.  That will
probably happen sometime relatively soon now, after which it will be
gone from the archives.  (Drafts gets expired in large batches, from
time to time, not on the precise day their 6 months is over).

  | The only way to re-activate an expired draft is to
  | submit a new draft with at least a new version number and expiration
  | date.

And perhaps more importantly here, the only way to withdraw a document,
in the sense of "take it out of circulation" as distinct from "not bother
to push it any more", is to do the same thing - submit a replacement
document.    The replacement need only contain the boilerplate, and
"This draft has been withdrawn", but if it isn't sent, the old one will
remain available, until it naturally expires and is removed as above.

That wasn't done here, so the "officially withdrawn it" really can only be
interpreted as "the authors are no longer pushing this doc".

kre