idnits 2.17.1 draft-ietf-tsvwg-tcp-eifel-alg-07.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 3522 5 Title: The Eifel Detection Algorithm for TCP 6 Author(s): R. Ludwig, M. Meyer 7 Status: Experimental 8 Date: April 2003 9 Mailbox: Reiner.Ludwig@eed.ericsson.se, 10 Michael.Meyer@eed.ericsson.se 11 Pages: 14 12 Characters: 33729 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-tsvwg-tcp-eifel-alg-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3522.txt 19 The Eifel detection algorithm allows a TCP sender to detect a 20 posteriori whether it has entered loss recovery unnecessarily. It 21 requires that the TCP Timestamps option defined in RFC 1323 be enabled 22 for a connection. The Eifel detection algorithm makes use of the fact 23 that the TCP Timestamps option eliminates the retransmission 24 ambiguity in TCP. Based on the timestamp of the first acceptable ACK 25 that arrives during loss recovery, it decides whether loss recovery 26 was entered unnecessarily. The Eifel detection algorithm provides a 27 basis for future TCP enhancements. This includes response algorithms 28 to back out of loss recovery by restoring a TCP sender's congestion 29 control state. 31 This document is a product of the Transport Area Working Group Working 32 Group of the IETF. 34 This memo defines an Experimental Protocol for the Internet community. 35 It does not specify an Internet standard of any kind. Discussion and 36 suggestions for improvement are requested. Distribution of this memo 37 is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.