metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6093: On the Implementation of the TCP Urgent Mechanism

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9293.

Current document in this lineage: RFC 7805 — Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status; RFC 9293 — Transmission Control Protocol (TCP)

In plain English — editorial summary, not part of the RFC

This document analyzes how current TCP implementations process TCP urgent indications and how the behavior of some widely deployed middleboxes affects how end systems process urgent indications. This document updates the relevant specifications such that they accommodate current practice in processing TCP urgent indications, raises awareness about the reliability of TCP urgent indications in the Internet, and recommends against the use of urgent indications (but provides advice to applications that do). [STANDARDS-TRACK]

Document record

Document ID
RFC6093
Published
January 2011
Authors
F. Gont; A. Yourtchenko
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
12
Also known as
—
Obsoleted by:
RFC 9293
Updates:
RFC 793, RFC 1011, RFC 1122

Topics

Standards lineage

This document is one revision in a chain of 18 RFCs, each formally replacing the one before it.

  1. RFC 675 (1974)
  2. RFC 721 (1976)
  3. RFC 761 (1980)
  4. RFC 793 (1981)
  5. RFC 813 (1982)
  6. RFC 816 (1982)
  7. RFC 879 (1983)
  8. RFC 896 (1984)
  9. RFC 1078 (1988)
  10. RFC 1948 (1996)
  11. RFC 2873 (2000)
  12. RFC 6013 (2011)
  13. RFC 6093 (2011)
  14. RFC 6429 (2011)
  15. RFC 6528 (2012)
  16. RFC 6691 (2012)
  17. RFC 7805 (2016)
  18. RFC 9293 (2022) ✓

Read the full history of Transmission Control Protocol (TCP) →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6093-on-the-implementation-of-the-tcp-urgent-mechanism