Re: [tcpm] 1323 & TCP MSS in Appendix A

Matt Mathis <mathis@psc.edu> Tue, 19 February 2008 13:57 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: ietfarch-tcpm-archive@core3.amsl.com
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E19C628C571; Tue, 19 Feb 2008 05:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 zv-Slht6yEpi; Tue, 19 Feb 2008 05:57:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 177BB28C580; Tue, 19 Feb 2008 05:57:18 -0800 (PST)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9725B28C549 for <tcpm@core3.amsl.com>; Tue, 19 Feb 2008 05:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 IQCCJP9s61F0 for <tcpm@core3.amsl.com>; Tue, 19 Feb 2008 05:57:14 -0800 (PST)
Received: from mailer2.psc.edu (unknown [IPv6:2001:5e8:2:42:2e0:81ff:fe30:e898]) by core3.amsl.com (Postfix) with ESMTP id DC50628C581 for <tcpm@ietf.org>; Tue, 19 Feb 2008 05:56:57 -0800 (PST)
Received: from tesla.psc.edu (tesla.psc.edu [128.182.58.233]) by mailer2.psc.edu (8.14.2/8.13.3) with ESMTP id m1JDuqX7029177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Feb 2008 08:56:53 -0500 (EST)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.13.1/8.13.1) with ESMTP id m1JDuqZ9006712; Tue, 19 Feb 2008 08:56:52 -0500
Date: Tue, 19 Feb 2008 08:56:52 -0500 (EST)
From: Matt Mathis <mathis@psc.edu>
To: TCP Maintenance and Minor Extensions WG <tcpm@ietf.org>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5804B70C05@xmb-sjc-21c.amer.cisco.com>
Message-ID: <Pine.LNX.4.64.0802190847330.30331@tesla.psc.edu>
References: <25C477DF-381D-46E7-BF8F-05461B3FCC56@windriver.com> <0C53DCFB700D144284A584F54711EC5804B70C05@xmb-sjc-21c.amer.cisco.com>
MIME-Version: 1.0
Cc: David Borman <david.borman@windriver.com>
Subject: Re: [tcpm] 1323 & TCP MSS in Appendix A
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

On Fri, 15 Feb 2008, Anantha Ramaiah (ananth) wrote:
>
> I think having a separate document which explains the pro's and con's of
> accounting the the options in the advertised MSS, clarifying the right
> approach sounds good. Another point in favour of a separate doc is that
> TCP MSS description probably looks out of place in RFC 1323 which mainly
> talks about high performance TCP options.

I agree.

The MSS option really has a different scope: it applies to all TCP 
implementations, high speed or otherwise and is essentially a mandatory 
clarification of earlier documents.  It is also valuable and important to help 
middle box implementers (who often futz with the MSS option) to get it less 
wrong.

Thanks,
--MM--

_______________________________________________
tcpm mailing list
tcpm@ietf.org
http://www.ietf.org/mailman/listinfo/tcpm