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

Pete Resnick <presnick@qti.qualcomm.com> Tue, 20 August 2013 21:16 UTC

Return-Path: <presnick@qti.qualcomm.com>
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 684BB11E82CE for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.455
X-Spam-Level:
X-Spam-Status: No, score=-106.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 y24Xf0CuB40a for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:16:04 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id CF97A11E82CF for <ietf@ietf.org>; Tue, 20 Aug 2013 14:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377033359; x=1408569359; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=BtPr+6rgKHSOJF6YXglW5vQbYIdEh/9H+0vVcbHkB/8=; b=lnpNxgi6R7stSf6cfvsvmzknA0eGEUxxbgGhD5o66JECoKipRdjc3l/9 6AKcaQVUX66M/TG+3iLIlqJcXBdohNRmqpkNQ8hFWgwqvPS+Q7LGjxu9N tyw9UkJ+pTWKRE82qPJ3YUh7LbzpOBffSK03bgWDY3sN7+uHOpCF0mJPc M=;
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="69512500"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 20 Aug 2013 14:15:58 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="524123889"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Aug 2013 14:15:57 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 20 Aug 2013 14:15:57 -0700
Message-ID: <5213DC8A.3020703@qti.qualcomm.com>
Date: Tue, 20 Aug 2013 16:15:54 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <6E29F0AB625F4250CB35B273@192.168.1.128> <520E7ADD.9060509@gmail.com> <CAMm+Lwi7z0S6HR5R8NpZ_J6WNACmPjP2ZxM+GD4Gx0UK4qgNTQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwi7z0S6HR5R8NpZ_J6WNACmPjP2ZxM+GD4Gx0UK4qgNTQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, IAB IAB <iab@iab.org>, IETF Discussion Mailing List <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 21:16:09 -0000

On 8/20/13 3:26 PM, Phillip Hallam-Baker wrote:
> If the data is in a database then surely the production of RFC xx00 
> standards series is simply running an automated query on the database 
> and emitting the result as an RFC?

I'm sure that such a tool could be created. To date, I believe the 
document was being built by hand.

However, the document hasn't been produced in over 5 years and nobody 
seems to miss it. The RFC Editor has indicated that they're not 
enthusiastic about keeping the document up to date given that there's a 
web page with that information that is getting good use. So the thinking 
behind the document I submitted was, "Let the RFC Editor off the hook. 
We, the IETF, don't need the RFC published separately anymore, so we 
should just say that."

I suppose if there's a real resurgence of sentiment that the RFC Editor 
should keep producing that document, we can tell the IAB that the IETF 
still really wants that document produced and send them off to write a 
tool that queries their database and auto-creates the RFC. In the 
absence of such sentiment, I think we should just use the web-based 
database and clean up the STD series as stated.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478