Re: Deprecation of ICMP Source Quench messages (draft-gont-tsvwg-source-quench)

Wesley Eddy <wes@mti-systems.com> Fri, 07 January 2011 02:49 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78E173A6E3B for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 18:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZSFI6zb3fNi4 for <tsvwg@core3.amsl.com>; Thu, 6 Jan 2011 18:49:04 -0800 (PST)
Received: from omr6.networksolutionsemail.com (omr6.networksolutionsemail.com [205.178.146.56]) by core3.amsl.com (Postfix) with ESMTP id 5C0023A6DF7 for <tsvwg@ietf.org>; Thu, 6 Jan 2011 18:49:04 -0800 (PST)
Received: from cm-omr6 (mail.networksolutionsemail.com [205.178.146.50]) by omr6.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p072pAnn017620 for <tsvwg@ietf.org>; Thu, 6 Jan 2011 21:51:10 -0500
Authentication-Results: cm-omr6 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [174.130.41.205] ([174.130.41.205:25813] helo=[192.168.1.104]) by cm-omr6 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 82/08-22185-E9F762D4; Thu, 06 Jan 2011 21:51:10 -0500
Message-ID: <4D267F98.6050508@mti-systems.com>
Date: Thu, 06 Jan 2011 21:51:04 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, tsvwg@ietf.org
Subject: Re: Deprecation of ICMP Source Quench messages (draft-gont-tsvwg-source-quench)
References: <4D21F2FC.2090000@erg.abdn.ac.uk> <FE2AD841-7CAD-4A09-A766-73A1D5BE1F56@cisco.com> <068B22BC-E1B4-4C7F-99C5-3B8B483EB057@cisco.com> <20110106092048.GA14506@openss7.org> <4D2602D5.30608@isi.edu> <4D260555.8050901@gont.com.ar> <4D26071C.30303@isi.edu> <4D260B3A.1050804@gont.com.ar> <4D260D1F.3000809@isi.edu>
In-Reply-To: <4D260D1F.3000809@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 02:49:05 -0000

On 1/6/2011 1:42 PM, Joe Touch wrote:
>
>
> On 1/6/2011 10:34 AM, Fernando Gont wrote:
>>
>> Please be realistic.
>
> We all are. Realistically, an RFC officially deprecating a feature that
> is already recommended against, and is already not being used (far as
> any of us can tell) serves no *urgent* purpose.
>
> Yes, that means this issue might wait on the shelf for a long time. So
> what?
>


Realistically, if there isn't an RFC, 2 years from now someone will come 
and re-write Fernando's document and ask to have an RFC published and 
we'll waste more time on the same discussion, so I'm in favor of 
blasting this through the process and getting it published as long as 
there's rough consensus on it.  We publish plenty of similarly useless 
book-keeping RFCs without controversy.

--
Wes Eddy
MTI Systems