IETF Logo Mail Archive

[tcpm] Definition of SMSS/RMSS in RFC5681 are inaccurate?!

Alexander Zimmermann <alexander.zimmermann@nets.rwth-aachen.de> Mon, 26 July 2010 12:33 UTC

Return-Path: <alexander.zimmermann@nets.rwth-aachen.de>
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 77BEB3A6BB4 for <tcpm@core3.amsl.com>; Mon, 26 Jul 2010 05:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.411
X-Spam-Level:
X-Spam-Status: No, score=-3.411 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, PLING_QUERY=1.39, RCVD_IN_DNSWL_MED=-4]
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 HpTrVltZcp8P for <tcpm@core3.amsl.com>; Mon, 26 Jul 2010 05:33:33 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id 7DD4C3A6BB0 for <tcpm@ietf.org>; Mon, 26 Jul 2010 05:33:10 -0700 (PDT)
MIME-version: 1.0
Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0L66004KQ07P9N90@mta-2.ms.rz.RWTH-Aachen.de> for tcpm@ietf.org; Mon, 26 Jul 2010 14:33:25 +0200 (CEST)
X-IronPort-AV: E=Sophos; i="4.55,261,1278280800"; d="sig'?scan'208"; a="66611282"
Received: from relay-auth-2.ms.rz.rwth-aachen.de (HELO relay-auth-2) ([134.130.7.79]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Mon, 26 Jul 2010 14:33:26 +0200
Received: from miami.nets.rwth-aachen.de ([unknown] [137.226.12.180]) by relay-auth-2.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0L6600IEQ07P9U80@relay-auth-2.ms.rz.rwth-aachen.de> for tcpm@ietf.org; Mon, 26 Jul 2010 14:33:25 +0200 (CEST)
From: Alexander Zimmermann <alexander.zimmermann@nets.rwth-aachen.de>
Content-type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Apple-Mail-1--954787283"
Content-transfer-encoding: 7bit
Date: Mon, 26 Jul 2010 14:33:26 +0200
Message-id: <62315AD7-72BE-42A1-AEFB-E706C54BF50A@nets.rwth-aachen.de>
To: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
X-Pgp-Agent: GPGMail 1.2.3
X-Mailer: Apple Mail (2.1081)
Cc: David Borman <david.borman@windriver.com>
Subject: [tcpm] Definition of SMSS/RMSS in RFC5681 are inaccurate?!
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: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 12:33:40 -0000

Dear WG,

while writing some definitions for my thesis, I stumble on the definition
of SMSS/RMSS in RFC5681:

SENDER MAXIMUM SEGMENT SIZE (SMSS): The SMSS is the size of the largest segment
that the sender can transmit. This value can be based on the maximum transmission
unit of the network, the path MTU discovery [RFC1191, RFC4821] algorithm, RMSS
(see next item), or other factors. The size does not include the TCP/IP headers
and options.

The size does not include the TCP/IP headers and options. This is wrong!
The options are the TCP/IP headers.

BTW: "to include" is in this context very misleading!

David you can update RFC5681 with your darft draft-ietf-tcpm-tcpmss too :-)

Alex

v2.23.0 | Report a Bug | By Email