IETF Logo Mail Archive

Re: [Gendispatch] Internet-Drafts Don't Expire

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 26 November 2019 19:34 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E09120A87 for <gendispatch@ietfa.amsl.com>; Tue, 26 Nov 2019 11:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 kjueQSQzWbYY for <gendispatch@ietfa.amsl.com>; Tue, 26 Nov 2019 11:34:32 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29662120A84 for <gendispatch@ietf.org>; Tue, 26 Nov 2019 11:34:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 47MvHD0dpDz2dLyt; Tue, 26 Nov 2019 11:34:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1574796872; bh=7pPiZdJK2TCONcFlrZ2n/dKRUSvXBn7DuVuX6AEIUEg=; h=Subject:To:References:From:Date:In-Reply-To:From; b=In+Bru211TWRvFzN/SLl2bKxQaO0owLryXDitT1I+q04SxZE4Omoh42VDtd0tXmmD gvacWk0AkJJxn48cW1Ogf7icmiWWDTIs1CGL83Tk3cQFuLf903BAsSfFZ8g/Gdfaa8 xtXYdjM6zkge6Mwar1qJV4pSKktuWRzNXtizN5t8=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 47MvHC31Shz2dLyV; Tue, 26 Nov 2019 11:34:31 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Phillip Hallam-Baker <phill@hallambaker.com>, gendispatch@ietf.org
References: <CAMm+LwjjSAK8YLDbnhX9k8jYHz58GazvbGy2Cna=EgZyH=b22A@mail.gmail.com> <95bf9a55-805e-db7d-1bf5-23d9daaa25ec@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <3248945d-0d75-98d0-ea0a-7f94c4a44c80@joelhalpern.com>
Date: Tue, 26 Nov 2019 14:34:29 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <95bf9a55-805e-db7d-1bf5-23d9daaa25ec@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/pMSWhjM5GZprsWRerm-Yl1hkIzU>
Subject: Re: [Gendispatch] Internet-Drafts Don't Expire
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2019 19:34:34 -0000

As a working group chair, I do expect the editors of WG drafts to 
refresh them.  This tells me that they are continuing to participate, 
and I do not need to find a new editor (or, conversely, that I do need 
to find a new editor.)  Yes, I could set calendar reminders and send 
email of my own.  For WG drafts, I think the expiration is useful to 
help folks get a more accurate image from the WG page.

Yours,
Joel

On 11/26/2019 2:26 PM, Brian E Carpenter wrote:
>> The question that came to me on the plane back was 'how many documents have to be put through IETF process purely to stop them expiring?'
> 
> None. Since expired documents are available for ever, there is absolutely no point in "refreshing" a draft with no changes except the date. People do so, but I'm not sure why. I quite often cite https://tools.ietf.org/html/draft-carpenter-aeiou-00 when people propose alternatives to IPv6, as an example of a failed solution.
> 
> Regards
>     Brian
>

v2.23.0 | Report a Bug | By Email