IETF Logo Mail Archive

Re: Last Call: Change the status of ADSP (RFC 5617) to Historic

Ted Lemon <ted.lemon@nominum.com> Wed, 20 November 2013 19:28 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 277331AE13E for <ietf@ietfa.amsl.com>; Wed, 20 Nov 2013 11:28:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 I4IQPoXMsVB9 for <ietf@ietfa.amsl.com>; Wed, 20 Nov 2013 11:28:01 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id C93FF1AE0DE for <ietf@ietf.org>; Wed, 20 Nov 2013 11:28:00 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUo0NOlyC+cEl7H1TFU16KJWfJLbn4dBZ@postini.com; Wed, 20 Nov 2013 11:27:54 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 78A0C1B82E5 for <ietf@ietf.org>; Wed, 20 Nov 2013 11:27:54 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7013A190043; Wed, 20 Nov 2013 11:27:54 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 20 Nov 2013 11:27:54 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <528D095F.80908@dcrocker.net>
Date: Wed, 20 Nov 2013 14:27:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <55AE2FE6-2441-4DA3-958F-08211C337524@nominum.com>
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it> <CAC4RtVBb9FVtmjK4X5hCQpMorHnjmyJLU1sYbNh==iBh8SqztQ@mail.gmail.com> <528CF075.9000204@dcrocker.net> <528CF4FB.2060505@isode.com> <528CF649.5000209@dcrocker.net> <B5317E33-E56D-4174-8A3C-AA781BEB5270@nominum.com> <528D095F.80908@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 20 Nov 2013 19:28:02 -0000

On Nov 20, 2013, at 2:11 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> a google search of "rfc 5617 historic" produced ready access to the relevant part of the ietf list archive.

Maybe so, but you just wrecked that, because what you just said and my reply will now show up as more relevant in the search results.   Which is why relying on google search for this, useful as I agree it is, is the wrong solution.

The datatracker is better, but I think it's relatively unusual for people to wind up in the datatracker or to know to go looking there for this sort of information.   A document that's listed in the metadata is clearly better, although possibly not _enough_ better to justify the effort.

v2.23.0 | Report a Bug | By Email