idnits 2.17.1 draft-ietf-tsvwg-limited-xmit-00.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3042 5 Title: Enhancing TCP's Loss Recovery Using Limited 6 Transmit 7 Author(s): M. Allman, H. Balakrishnan, S. Floyd 8 Status: Standards Track 9 Date: January 2001 10 Mailbox: mallman@grc.nasa.gov, hari@lcs.mit.edu, 11 floyd@aciri.org 12 Pages: 9 13 Characters: 19885 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-tsvwg-limited-xmit-00.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3042.txt 20 This document proposes a new Transmission Control Protocol (TCP) 21 mechanism that can be used to more effectively recover lost segments 22 when a connection's congestion window is small, or when a large number 23 of segments are lost in a single transmission window. The "Limited 24 Transmit" algorithm calls for sending a new data segment in response 25 to each of the first two duplicate acknowledgments that arrive at the 26 sender. Transmitting these segments increases the probability that 27 TCP can recover from a single lost segment using the fast retransmit 28 algorithm, rather than using a costly retransmission timeout. Limited 29 Transmit can be used both in conjunction with, and in the absence of, 30 the TCP selective acknowledgment (SACK) mechanism. 32 This document is a product of the Transport Area Working Group of the 33 IETF. 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.