Recommends a methodology for measuring TCP Throughput in order to
In addition to Layer 2/3 testing, this framework That Layer 2/3 testing is not enough to adequately ensure end-users' Network providers are coming to the realization To business-class customers is generally based upon Layer 2/3Ĭriteria such as bandwidth, latency, packet loss, and delay In the network industry, the SLA (Service Level Agreement) provided RFC 6349 Framework for TCP Throughput Testing August 2011 1. TCP Transfer Time and Transfer Time RatioĬalculation. Maximum Achievable TCP Throughput Calculation. Round-Trip Time (RTT) and Bottleneck Bandwidth (BB). The Trust Legal Provisions and are provided without warranty asġ.
Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 6349 Framework for TCP Throughput Testing August 2011Ĭopyright (c) 2011 IETF Trust and the persons identified as the
Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬonstantine, et al. Not all documentsĪpproved by the IESG are a candidate for any level of Internet Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This document is not an Internet Standards Track specification it is In thisįramework, TCP and IP parameters are specified to optimize TCP Provide a better indication in regard to user experience. To-end TCP Throughput in a managed IP network. This framework describes a practical methodology for measuring end.
Internet Engineering Task Force (IETF) B.