Skip to main content

On the implementation of TCP urgent data

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Fernando Gont , Andrew Yourtchenko
Last updated 2009-02-02
Replaced by draft-ietf-tcpm-urgent-data
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tcpm-urgent-data
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document analyzes how current TCP implementations process TCP urgent indications, and how the behavior of some widely-deployed middle-boxes affect how urgent indications are processed by end systems. This document updates the relevant specifications such that they accommodate current practice in processing TCP urgent indications, and raises awareness about the reliability of TCP urgent indications in the current Internet.


Fernando Gont
Andrew Yourtchenko

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