Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"

SM <sm@resistor.net> Tue, 20 August 2013 20:52 UTC

Return-Path: <sm@resistor.net>
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 9E72B11E82BC; Tue, 20 Aug 2013 13:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level:
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itupb40AjhM8; Tue, 20 Aug 2013 13:52:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A306D11E8286; Tue, 20 Aug 2013 13:52:34 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7KKqS9O005996; Tue, 20 Aug 2013 13:52:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377031954; bh=czckfCmSSfOapliSdZqUyXZcxA0pnOIYv0/QYJFJKbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2/0iRt6QU8bhmIzpyZbGzP4LyQPAwmrTRpS1d/f1ddaBSnBYrSWKmxRaJZmUOmKu/ GcloCacLao4c0LdetulX28IQaPR/loFe+k1Mx+uTAuOcxxv5jeqax7+QmkbW3L62aW KvbkKv051GT6p3FUI2BcExUyQ0V0PStcFN0tIKcQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377031954; i=@resistor.net; bh=czckfCmSSfOapliSdZqUyXZcxA0pnOIYv0/QYJFJKbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Mb/fgQA6pnEW1vaTTnM7F0C1KqDqO28ppmuEGd+yHUD2Qtke5QLY6gYfRgt6zI/Tu JA9Z8kvm/JIimTJesUeAX/Y8ut+UyCm8u3ffoK1Hedtv5VjPFFlZKQFR3yJVfMIxWP W9UJiiKmEwka3Hum0/4U6XrjgCLZ7LR5N7uDWjUU=
Message-Id: <6.2.5.6.2.20130820134308.0b8a6b38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 13:51:05 -0700
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
In-Reply-To: <5213BD15.2080500@qti.qualcomm.com>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <5213BD15.2080500@qti.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: iab@iab.org, ietf@ietf.org
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: Tue, 20 Aug 2013 20:52:36 -0000

Hi Pete,
At 12:01 20-08-2013, Pete Resnick wrote:
>The IESG and the IAB had an email exchange about these two points. 
>Moving a document from Standard to Historic is really an IETF thing 
>to do. And it would be quite simple for the IETF to say, "We are no 
>longer asking for the 'Official Protocol Standards' RFC to be 
>maintained" by updating (well, effectively removing) the one 
>paragraph in 2026 that asks for it, and requesting the move from 
>Standard to Historic. So I prepared a *very* short document to do that:
>
>http://datatracker.ietf.org/doc/draft-resnick-retire-std1/

I read the draft.  I agree with what is written above.

>I'm asking Jari to Last Call it along with a status change for STD 1 
>(RFC 5000) to Historic. If the RFC Editor wants to explain more of 
>the history and whatever else they're going to do in a separate 
>document, that's up to the IAB. But declaring Standards to be 
>Historic is something the RFC Editor or IAB shouldn't be doing. The 
>above document solves the problem by making it clear that the IETF 
>isn't interested in the document being updated anymore.

I support moving the draft to Last Call as it solves the problem.

Regards,
-sm