IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Wed, 20 November 2013 19:26 UTC

Return-Path: <lear@cisco.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 1C9B31AE113 for <ietf@ietfa.amsl.com>; Wed, 20 Nov 2013 11:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.026
X-Spam-Level:
X-Spam-Status: No, score=-15.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 JBZOCjhSA0KP for <ietf@ietfa.amsl.com>; Wed, 20 Nov 2013 11:26:29 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B7E5F1ADF7F for <ietf@ietf.org>; Wed, 20 Nov 2013 11:26:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=703; q=dns/txt; s=iport; t=1384975583; x=1386185183; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bH2jkwxAAeRnNDEADcuyU63p4hu+0Ll8NK3jr1jo4qQ=; b=TY6dLdzcE4yFJmySRAdQGl1+To6+tqaLlnZ0GsGb0zpq8YtQhB8sBqd7 CuBDO6upwKhvm6Rk5keD18gEyVh8CkUXAPhMIIksNO4OXEc2OK9GZCjej Bq1/kURA1iqTlYfQAfVnEucofXCYCq29+IJMQ+4I+bozNoEgtS9rs9egl w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFANcLjVKrRDoG/2dsb2JhbABZgwc4g0m6e4EaFnSCJQEBAQQjVQEQCxgCAgUWCwICCQMCAQIBKxoGAQwBBwEBh3wOr1qREhMEgSmOLgeCa4FHA5gSkg2DKTs
X-IronPort-AV: E=Sophos;i="4.93,738,1378857600"; d="scan'208";a="95057937"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 20 Nov 2013 19:26:21 +0000
Received: from mctiny.local ([10.61.218.42]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rAKJQHXs007932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Nov 2013 19:26:19 GMT
Message-ID: <528D0CD9.5010300@cisco.com>
Date: Wed, 20 Nov 2013 20:26:17 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, John Klensin <klensin@jck.com>
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>
In-Reply-To: <CALaySJ+E=84jTJxfP7dGx=kVHN1DE1b3TyYhRA3454Z0oK+J-w@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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:26:31 -0000

Well, I'll answer for myself:

Not necessary.  If someone wants to write a document, tho, I wouldn't
try to stop 'em.

Eliot

On 11/20/13 8:09 PM, Barry Leiba wrote:
>> If someone is willing to write the document and explain why ADSP has
>> been moved to Historic, that's good for capturing lessons learned.  I
>> don't think it's required for the status change, but a bonus.
> Do you think that more than this is necessary?:
> https://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>
> I should, in particular, direct that question to John, as he's the one
> who brought up the question of documenting why... so I am adding John
> to the "To" here.
>
> Barry
>
>

v2.23.0 | Report a Bug | By Email