Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
Dave Crocker <dhc@dcrocker.net> Thu, 21 November 2013 17:30 UTC
Return-Path: <dhc@dcrocker.net>
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 F197B1AE206 for <ietf@ietfa.amsl.com>; Thu, 21 Nov 2013 09:30:20 -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 7qTW2urnrDQ3 for <ietf@ietfa.amsl.com>; Thu, 21 Nov 2013 09:30:19 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 13C3D1AE05F for <ietf@ietf.org>; Thu, 21 Nov 2013 09:30:19 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rALHU25g013582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 21 Nov 2013 09:30:05 -0800
Message-ID: <528E42F0.8010902@dcrocker.net>
Date: Thu, 21 Nov 2013 09:29:20 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it> <CAC4RtVBb9FVtmjK4X5hCQpMorHnjmyJLU1sYbNh==iBh8SqztQ@mail.gmail.com> <528CF075.9000204@dcrocker.net> <528CFCBC.30200@cisco.com> <CALaySJ+E=84jTJxfP7dGx=kVHN1DE1b3TyYhRA3454Z0oK+J-w@mail.gmail.com> <528D0CD9.5010300@cisco.com> <9FC35D4E-4A7D-4682-8C94-9FBC31E09A96@harvard.edu> <528D3DB9.1090301@dcrocker.net> <CALaySJJhETrpdgO1mt-9YHY1NJ=Ykg++9V-03GwggtdQUN4PXA@mail.gmail.com> <CAL0qLwYRXNUMtovSpkVOZ_k6AfBROK_MT8Y=PF5C2GzjfaKqyg@mail.gmail.com>
In-Reply-To: <CAL0qLwYRXNUMtovSpkVOZ_k6AfBROK_MT8Y=PF5C2GzjfaKqyg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 21 Nov 2013 09:30:05 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 21 Nov 2013 17:30:21 -0000
On 11/21/2013 12:49 AM, Murray S. Kucherawy wrote: > n Wed, Nov 20, 2013 at 3:10 PM, Barry Leiba <barryleiba@computer.org > <mailto:barryleiba@computer.org>> wrote: >> 2. But if we just process this status change as currently proposed, >> someone looking at the datatracker page for RFC 5617 would see (1) >> that it's Historic ... > > That's true, but there are other sources of RFCs that don't contain such > information, such as http://www.ietf.org/rfc/rfc6376.txt and I think the > one at rfc-editor.org <http://rfc-editor.org>. Someone grabbing the RFC > from such sources (which could easily be seen as official) would not be > aware of the status change or the reason for it. These other paths to an obsolete RFC will typically either not tell the reader that the RFC is obsolte or will tell the reader that the RFC is obsolete and will not point the reader to the fact that there is an RFC explaining that it is obsolete. Having an explanatory RFC provides no incremental benefit. (One exception is rfc-editor.org.) For example: Using Digest Authentication as a SASL Mechanism http://www.rfc-editor.org/rfc/rfc2831.txt is obsolete, but the pointer goes to a page that says it's standards track. My search for rfc2831 on google points to the above, as a first reference, and therefore doesn't tell me that it's obsolete. The second reference is: http://www.rfc-editor.org/info/rfc2831 which /does/ indicate it's obsolete, and yes it points to the explanatory RFC. Gosh, I wonder whether it would be possible for the RFC Editor pages to point to the datatracker page instead? Nah, that's probably too outrageous a request. So, to find: "Moving DIGEST-MD5 to Historic", July 2011 http://www.rfc-editor.org/info/rfc6331 You have to either already know it exists. Or use a search tool that points to it. If you are using a search tool, it can also point to the datatracker entry. The IETF spent quite a lot of money on the datatracker. We should work to have it be the primary search result for RFCs. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- Re: Last Call: Change the status of ADSP (RFC 561… John Levine
- Re: Last Call: Change the status of ADSP (RFC 561… John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- RE: Last Call: Change the status of ADSP (RFC 561… ietfdbh
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… Murray S. Kucherawy
- Re: Last Call: Change the status of ADSP (RFC 561… Hector Santos
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Alessandro Vesely
- Re: Last Call: Change the status of ADSP (RFC 561… Scott Kitterman
- Re: Last Call: Change the status of ADSP (RFC 561… Hector Santos
- Re: Last Call: Change the status of ADSP (RFC 561… John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… Hector Santos
- Re: Last Call: Change the status of ADSP (RFC 561… Douglas Otis
- Re: Last Call: Change the status of ADSP (RFC 561… Murray S. Kucherawy
- How to protect DKIM signatures: Moving ADSP to Hi… Hector Santos
- Re: How to protect DKIM signatures: Moving ADSP t… Barry Leiba
- Re: How to protect DKIM signatures: Moving ADSP t… Hector Santos
- Re: How to protect DKIM signatures: Moving ADSP t… Douglas Otis
- Re: Last Call: Change the status of ADSP (RFC 561… Murray S. Kucherawy
- Re: How to protect DKIM signatures: Moving ADSP t… Hector Santos
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Ted Lemon
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Alexey Melnikov
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Bob Braden
- Re: Last Call: Change the status of ADSP (RFC 561… Eliot Lear
- Re: Last Call: Change the status of ADSP (RFC 561… Ted Lemon
- Re: Last Call: Change the status of ADSP (RFC 561… Ted Lemon
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Eliot Lear
- Re: Last Call: Change the status of ADSP (RFC 561… Ted Lemon
- Re: Last Call: Change the status of ADSP (RFC 561… John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… Hector Santos
- Re: Last Call: Change the status of ADSP (RFC 561… Bradner, Scott
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Bradner, Scott
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… Murray S. Kucherawy
- Procedural Changes through side-effect (was: Re: … John C Klensin
- Re: Last Call: Change the status of ADSP (RFC 561… Dave Crocker
- Re: Procedural Changes through side-effect (was: … S Moonesamy
- Spontaneous Procedure Invention ( was Re: Procedu… Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… S Moonesamy
- Re: Last Call: Change the status of ADSP (RFC 561… Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 561… S Moonesamy