Re: [Gendispatch] I-D Action: draft-thomson-gendispatch-no-expiry-00.txt

"Pete Resnick" <resnick@episteme.net> Tue, 05 November 2019 23:14 UTC

Return-Path: <resnick@episteme.net>
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 1C82C12087A for <gendispatch@ietfa.amsl.com>; Tue, 5 Nov 2019 15:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 gidmm7rKhcLV for <gendispatch@ietfa.amsl.com>; Tue, 5 Nov 2019 15:14:30 -0800 (PST)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4472A120C0E for <gendispatch@ietf.org>; Tue, 5 Nov 2019 15:14:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 1F18E933F67A; Tue, 5 Nov 2019 17:14:29 -0600 (CST)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TIGG1VOv6zw; Tue, 5 Nov 2019 17:14:23 -0600 (CST)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 149D0933F66F; Tue, 5 Nov 2019 17:14:22 -0600 (CST)
From: Pete Resnick <resnick@episteme.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: gendispatch@ietf.org, mt@lowentropy.net
Date: Tue, 05 Nov 2019 17:14:17 -0600
X-Mailer: MailMate (1.13r5655)
Message-ID: <E1922906-E8B5-45CF-A107-23DAA14735B2@episteme.net>
In-Reply-To: <afe1d8ef-979d-6c8f-0fe6-b69a2d3d3f56@gmail.com>
References: <157290645420.13916.12275765354821078575@ietfa.amsl.com> <afe1d8ef-979d-6c8f-0fe6-b69a2d3d3f56@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/pB_Vl0cxfb13QlgJl1xWH8MfSCw>
Subject: Re: [Gendispatch] I-D Action: draft-thomson-gendispatch-no-expiry-00.txt
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, 05 Nov 2019 23:14:36 -0000

Given that Martin isn't subscribed to the gendispatch list, I expect 
he'll need to be Cc'ed to see this. I have now done so.

Martin, shall I take this to mean that you'd like agenda time in 
Singapore?

pr

On 4 Nov 2019, at 16:48, Brian E Carpenter wrote:

> Hi,
>
> First a major nit: I-D expiry is mandated by RFC2026:
> https://tools.ietf.org/html/rfc2026#section-6.1.2
> The mention in RFC2418 is incidental.
>
> Then:
>
>> Forced expiration serves no purpose that is not adequately served by
>> the publication date on the document.
>
> A date of publication alone does not communicate that a draft is
> a draft and that, as BCP9 says:
>
>>       *   Under no circumstances should an Internet-Draft    *
>>       *   be referenced by any paper, report, or Request-    *
>>       *   for-Proposal, nor should a vendor claim compliance *
>>       *   with an Internet-Draft.                            *
>
> While the choice of 6 months might seem arbitary, the defined
> date of expiry IMHO helps to communicate to readers that
> a draft is only a draft. And it also acts as a signal that
> there might be a lack of momentum behind a proposal, if a
> draft has expired without being updated.
>
> Regards
>    Brian
>
> On 05-Nov-19 11:27, internet-drafts@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>>
>>
>>         Title           : Internet-Drafts Don't Expire
>>         Author          : Martin Thomson
>> 	Filename        : draft-thomson-gendispatch-no-expiry-00.txt
>> 	Pages           : 4
>> 	Date            : 2019-11-04
>>
>> Abstract:
>>    The long-standing insistence that Internet-Drafts carry expiration
>>    dates is a concept that is no longer necessary.  This document
>>    removes requirements for expiration for Internet-Drafts from RFC
>>    2418/BCP 25.
>>
>> Note to Readers
>>
>>    Discussion of this document takes place on the GENDISPATCH Working
>>    Group mailing list (gendispatch@ietf.org), which is archived at
>>    https://mailarchive.ietf.org/arch/browse/gendispatch/ [1].
>>
>>    Source for this draft and an issue tracker can be found at
>>    https://github.com/martinthomson/no-expiry [2].
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-thomson-gendispatch-no-expiry/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-thomson-gendispatch-no-expiry-00
>> https://datatracker.ietf.org/doc/html/draft-thomson-gendispatch-no-expiry-00
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>


-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best