On the implementation of TCP urgent data
draft-gont-tcpm-urgent-data-01

 
Document Type Replaced Internet-Draft (individual)
Last updated 2009-02-02
Replaced by draft-ietf-tcpm-urgent-data
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tcpm-urgent-data
Telechat date
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-gont-tcpm-urgent-data-01.txt

Abstract

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.

Authors

Fernando Gont (fernando@gont.com.ar)
Andrew Yourtchenko (ayourtch@cisco.com)

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