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

To: Ted Lemon <ted.lemon@xxxxxxxxxxx>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
From: Dave Crocker <dhc@xxxxxxxxxxxx>
Date: Wed, 20 Nov 2013 11:11:27 -0800
Cc: IETF discussion list <ietf@xxxxxxxx>
Delivered-to: ietf@xxxxxxxxxxxxxx
In-reply-to: <B5317E33-E56D-4174-8A3C-AA781BEB5270@nominum.com>
Organization: Brandenburg InternetWorking
Reply-to: dcrocker@xxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0

On 11/20/2013 11:08 AM, Ted Lemon wrote:

Because it's hard to find this information in the IETF mailing list archive



uhhh...doesn't seem to be.

a google search of "rfc 5617 historic" produced ready access to therelevant part of the ietf list archive.


d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net

Follow-Ups:
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Ted Lemon

References:
- Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
  - From: John Levine
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Alessandro Vesely
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Barry Leiba
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Alexey Melnikov
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Dave Crocker
- Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  - From: Ted Lemon