RE: Deprecating ICMP Source Quench messages

"Dan Wing" <dwing@cisco.com> Tue, 30 November 2010 02:45 UTC

Return-Path: <dwing@cisco.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 02D303A6C55 for <tsvwg@core3.amsl.com>; Mon, 29 Nov 2010 18:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.544
X-Spam-Level:
X-Spam-Status: No, score=-110.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 kDkB2RfQxbfG for <tsvwg@core3.amsl.com>; Mon, 29 Nov 2010 18:45:09 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 56F8B3A6C53 for <tsvwg@ietf.org>; Mon, 29 Nov 2010 18:45:09 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj0DAL/z80yrR7Ht/2dsb2JhbACUQ4FjjGdxpxubV4VHBIRcgSqEEA
X-IronPort-AV: E=Sophos;i="4.59,278,1288569600"; d="scan'208";a="294590787"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 30 Nov 2010 02:46:19 +0000
Received: from dwingWS ([10.32.240.195]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oAU2kJgr013638; Tue, 30 Nov 2010 02:46:19 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Fernando Gont'" <fernando@gont.com.ar>
References: <4CF0454A.8070008@gont.com.ar> <0e2d01cb9011$992edc60$cb8c9520$@com> <4CF43D0A.3000902@gont.com.ar>
In-Reply-To: <4CF43D0A.3000902@gont.com.ar>
Subject: RE: Deprecating ICMP Source Quench messages
Date: Mon, 29 Nov 2010 18:46:19 -0800
Message-ID: <0f7d01cb9038$c448ba20$4cda2e60$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuQJYiXMEsfNGBwR0uEC7NZsnk2tQAEw5gw
Content-Language: en-us
Cc: 'tsvwg' <tsvwg@ietf.org>
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: Tue, 30 Nov 2010 02:45:12 -0000

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Fernando Gont
> Sent: Monday, November 29, 2010 3:54 PM
> To: Dan Wing
> Cc: 'tsvwg'
> Subject: Re: Deprecating ICMP Source Quench messages
> 
> Hi, Dan,
> 
> Thanks so much for your feedback! Please find my comments inline...
> 
> >> FWIW, the document is so short that, even if you have not read it
> >> before, it shouldn't take more than a few minutes to skim through
> it.
> >
> > I read it.  Looks good.
> >
> > Might also want to mention that ICMPv6 didn't bother defining
> > Source Quench.
> 
> Will do.
> 
> BTW, some have argued (off-list) that this document should also update
> RFC 1812 such that the "SHOULD NOT generate ICMP SQ" is changed to
> "MUST
> NOT generate ICMP SQ".
> 
> Thoughts?

My 'line' for MUST-versus-SHOULD is that interoperability is harmed
if a MUST is violated.  A stack compliant with
draft-gont-tsvwg-source-quench
isn't harmed (or helped) by receiving a source quench.  So, I don't
see much value in changing it to MUST.

-d


> Thanks!
> 
> Kind regards,
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
>