[pilc] Protocol Action: TCP Performance Implications of Network Asymmetry to BCP
Aaron Falk <falk@isi.edu> Thu, 10 October 2002 17:24 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16180 for <pilc-archive@lists.ietf.org>; Thu, 10 Oct 2002 13:24:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHQCv24240; Thu, 10 Oct 2002 13:26:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHNOv24164 for <pilc@optimus.ietf.org>; Thu, 10 Oct 2002 13:23:24 -0400
Received: from nit.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15981 for <pilc@ietf.org>; Thu, 10 Oct 2002 13:21:13 -0400 (EDT)
Received: (from falk@localhost) by nit.isi.edu (8.11.6/8.11.6) id g9AHNI207474; Thu, 10 Oct 2002 10:23:18 -0700
From: Aaron Falk <falk@isi.edu>
To: pilc@ietf.org
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, mahesh@erg.abdn.ac.uk, padmanab@microsoft.com, hari@lcs.mit.edu
Message-ID: <20021010172318.GH2622@isi.edu>
Mail-Followup-To: pilc@ietf.org, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, mahesh@erg.abdn.ac.uk, padmanab@microsoft.com, hari@lcs.mit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: [pilc] Protocol Action: TCP Performance Implications of Network Asymmetry to BCP
Sender: pilc-admin@ietf.org
Errors-To: pilc-admin@ietf.org
X-BeenThere: pilc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=unsubscribe>
List-Id: Performance Implications of Link Characteristics IETF Working Group <pilc.ietf.org>
List-Post: <mailto:pilc@ietf.org>
List-Help: <mailto:pilc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/pilc/>
Date: Thu, 10 Oct 2002 10:23:18 -0700
Congratulations to the authors. Well done! --aaron ----- Forwarded message from The IESG <iesg-secretary@ietf.org> ----- To: IETF-Announce: ; Cc: RFC Editor <rfc-editor@ISI.EDU>, Internet Architecture Board <iab@iab.org>, pilc@grc.nasa.gov From: The IESG <iesg-secretary@ietf.org> Subject: Protocol Action: TCP Performance Implications of Network Asymmetry to BCP Date: Thu, 10 Oct 2002 12:56:52 -0400 The IESG has approved the Internet-Draft 'TCP Performance Implications of Network Asymmetry' <draft-ietf-pilc-asym-08.txt> as a BCP. This document is the product of the Performance Implications of Link Characteristics Working Group. The IESG contact persons are Allison Mankin and Scott Bradner. Technical Summary This document describes TCP performance problems that may arise if network paths have asymmetric characteristics. These problems arise in several access networks, including bandwidth-asymmetric networks and packet radio subnetworks, for different underlying reasons. However, the end result on TCP performance is the same in both cases: performance often degrades significantly because of imperfection and variability in the ACK feedback from the receiver to the sender. This document details several mitigations of these effects, which have either been proposed or evaluated in the literature, or are currently deployed in networks. These solutions use a combination of local link-layer techniques, subnetwork, and end-to-end mechanisms, consisting of: (i) techniques to manage the channel used for the upstream bottleneck link carrying the ACKs, typically using header compression or reducing the frequency of TCP ACKs, (ii) techniques to handle this reduced ACK frequency to retain the TCP sender's acknowledgment-triggered self-clocking and (iii) techniques to schedule the data and ACK packets in the reverse direction to improve performance in the presence of two-way traffic. Each technique is described, together with known issues, and recommendations for when they should be used, and recommendations of techniques that should not be used. Working Group Summary The working group supported the advancement of the document. Protocol Quality This document was reviewed for the IESG by Allison Mankin. ----- End forwarded message ----- _______________________________________________ pilc mailing list pilc@ietf.org https://www1.ietf.org/mailman/listinfo/pilc http://www.ietf.org/html.charters/pilc-charter.html http://pilc.grc.nasa.gov/