[tcpm] [Errata Held for Document Update] RFC7323 (5585)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 18 March 2019 14:10 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECAB12AF83; Mon, 18 Mar 2019 07:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.191
X-Spam-Level:
X-Spam-Status: No, score=-4.191 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, L_8BIT_MISMATCH=0.01, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWmP02egK2Ju; Mon, 18 Mar 2019 07:10:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C982A12872C; Mon, 18 Mar 2019 07:10:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 484DBB80088; Mon, 18 Mar 2019 07:10:14 -0700 (PDT)
To: marco.caspers@t-mobilethuis.nl, david.borman@quantum.com, braden@isi.edu, vanj@google.com, rs@netapp.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ietf@kuehlewind.net, iesg@ietf.org, tcpm@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190318141014.484DBB80088@rfc-editor.org>
Date: Mon, 18 Mar 2019 07:10:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/i6mbXkyzSNbJoFAh0mhWjj4MH3I>
Subject: [tcpm] [Errata Held for Document Update] RFC7323 (5585)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 18 Mar 2019 14:10:29 -0000
The following errata report has been held for document update for RFC7323, "TCP Extensions for High Performance". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5585 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Marco Caspers <marco.caspers@t-mobilethuis.nl> Date Reported: 2018-12-27 Held by: Mirja Kühlewind (IESG) Section: 2.2 Original Text ------------- 2.2. Window Scale Option The three-byte Window Scale option MAY be sent in a <SYN> segment by a TCP. It has two purposes: (1) indicate that the TCP is prepared to both send and receive window scaling, and (2) communicate the exponent of a scale factor to be applied to its receive window. Thus, a TCP that is prepared to scale windows SHOULD send the option, even if its own scale factor is 1 and the exponent 0. The scale factor is limited to a power of two and encoded logarithmically, so it may be implemented by binary shift operations. The maximum scale exponent is limited to 14 for a maximum permissible receive window size of 1 GiB (2^(14+16)). Corrected Text -------------- 2.2. Window Scale Option The three-byte Window Scale option MAY be sent in a <SYN> segment by a TCP. It has two purposes: (1) indicate that the TCP is prepared to both send and receive window scaling, and (2) communicate the exponent of a scale factor to be applied to its receive window. Thus, a TCP that is prepared to scale windows SHOULD send the option, even if its own scale factor is 1 and the exponent 0. The scale factor is limited to a power of two and encoded logarithmically, so it may be implemented by binary shift operations. The maximum scale exponent is limited to 14 for a maximum permissible receive window size of approximately 1 GiB ((2^30-1) - (2^14-1)). Notes ----- Left shift inserts zero's on the right hand side so the maximum window size is actually 16KiB shy of 1 GiB. The exact calculation would be ((2^30-1) - (2^14-1)). As it is stated as "approximately 1 GiB" the text is not incorrect but it would be good to provide the complete calculation in a document update to avoid invalid implementations. -------------------------------------- RFC7323 (draft-ietf-tcpm-1323bis-21) -------------------------------------- Title : TCP Extensions for High Performance Publication Date : September 2014 Author(s) : D. Borman, B. Braden, V. Jacobson, R. Scheffenegger, Ed. Category : PROPOSED STANDARD Source : TCP Maintenance and Minor Extensions Area : Transport Stream : IETF Verifying Party : IESG
- [tcpm] [Errata Held for Document Update] RFC7323 … RFC Errata System