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

<david.black@emc.com> Mon, 03 January 2011 19:00 UTC

Return-Path: <david.black@emc.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 433FD3A6AD2 for <tsvwg@core3.amsl.com>; Mon, 3 Jan 2011 11:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 y5Qkq+wAkDPG for <tsvwg@core3.amsl.com>; Mon, 3 Jan 2011 11:00:17 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id B9E9E3A6AB0 for <tsvwg@ietf.org>; Mon, 3 Jan 2011 11:00:17 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p03J2OPZ013773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 3 Jan 2011 14:02:24 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 3 Jan 2011 14:02:13 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p03J1t7i023388 for <tsvwg@ietf.org>; Mon, 3 Jan 2011 14:01:56 -0500
Received: from mx14a.corp.emc.com ([169.254.1.169]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Mon, 3 Jan 2011 14:01:55 -0500
From: david.black@emc.com
To: tsvwg@ietf.org
Date: Mon, 03 Jan 2011 14:01:54 -0500
Subject: RE: Deprecation of ICMP Source Quench messages (draft-gont-tsvwg-source-quench)
Thread-Topic: Deprecation of ICMP Source Quench messages (draft-gont-tsvwg-source-quench)
Thread-Index: AcurX/FNwE1palWzTeKyEr2f6RZpJQAFkMJA
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E03D7555E02@MX14A.corp.emc.com>
References: <4D21F2FC.2090000@erg.abdn.ac.uk>
In-Reply-To: <4D21F2FC.2090000@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
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: Mon, 03 Jan 2011 19:00:19 -0000

> We'd welcome feedback to the list on the question below:
> 
>     "Does the WG believe this document effectively addresses
>     an existing problem, and should this draft form the basis for
>     a solution?"
> 
> Please email the chairs and/or list if you support this as a work item,
> or have comments on the suitability of this draft as a TSVWG work item.

The problem is that everyone here "knows" that Source Quench is deprecated in "running code", but that knowledge is not documented.  We really should document it just in case someone who isn't in the "know" tries to use Source Quench.  This draft does a reasonable job of that by specifying that Source Quench SHOULD NOT be sent and SHOULD be ignored on receipt.

Proceeding to answer the questions:

1) There is an existing problem, although not a major one.
2) This draft effectively addresses that problem.
3) I support this draft as a tsvwg work item.

A longer list of surveyed implementations in Appendix A would be a good idea (e.g., Windows and MacOS for starters).

Thanks,
--David

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Gorry Fairhurst
> Sent: Monday, January 03, 2011 11:02 AM
> To: tsvwg list; tsvwg-chairs@tools.ietf.org
> Subject: Deprecation of ICMP Source Quench messages (draft-gont-tsvwg-source-quench)
> 
> There was discussion of the draft below on the TSVWG list and at the
> last IETF meeting.
> 
> Deprecation of ICMP Source Quench messages
> (draft-gont-tsvwg-source-quench)
> http://tools.ietf.org/html/draft-gont-tsvwg-source-quench-01
> 
> We'd welcome feedback to the list on the question below:
> 
>     "Does the WG believe this document effectively addresses
>     an existing problem, and should this draft form the basis for
>     a solution?"
> 
> Please email the chairs and/or list if you support this as a work item,
> or have comments on the suitability of this draft as a TSVWG work item.
> 
> Best wishes,
> 
> Gorry & James
> (TSVWG Co-Chairs)