Skip to main content

TCP Retransmit (RXT) Flag
draft-ludwig-tsvwg-tcp-rxt-flag-03

Document Type Expired Internet-Draft (individual)
Authors Ludwig Reiner , Michael Meyer
Last updated 2001-11-21
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ludwig-tsvwg-tcp-rxt-flag-03.txt

Abstract

This document proposes a solution to TCP’s retransmission ambiguity problem. It is based on using a single bit, named the Retransmit (RXT) flag, taken from the Reserved field of the TCP header. The TCP sender sets the RXT flag in segments containing retransmitted data. In response to such a segment, the TCP receiver sends an immediate pure ACK with the RXT flag set. By inspecting the RXT flag of the ACKs that arrive after a retransmit the TCP sender can then resolve the retransmission ambiguity. This protocol feature provides a basis for future TCP enhancements such as schemes to detect and respond to spurious timeouts and packet re-orderings.

Authors

Ludwig Reiner
Michael Meyer

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)