metasystema.org
ObsoletedHISTORICLegacy stream

RFC 1379: Extending TCP for Transactions -- Concepts

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

Current document in this lineage: RFC 2018 — TCP Selective Acknowledgment Options; RFC 6247 — Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status; RFC 7323 — TCP Extensions for High Performance

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

This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard.

Document record

Document ID
RFC1379
Published
November 1992
Authors
R. Braden
Status
HISTORIC
Stream
Legacy
Area
—
Pages
38
Also known as
—
Obsoleted by:
RFC 6247
Updated by:
RFC 1644

Topics

Standards lineage

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

  1. RFC 1072 (1988)
  2. RFC 1106 (1989)
  3. RFC 1110 (1989)
  4. RFC 1145 (1990)
  5. RFC 1146 (1990)
  6. RFC 1185 (1990)
  7. RFC 1323 (1992)
  8. RFC 1379 (1992)
  9. RFC 1644 (1994)
  10. RFC 1693 (1994)
  11. RFC 2018 (1996)
  12. RFC 6247 (2011)
  13. RFC 7323 (2014) ✓

Read the full history of TCP Extensions for High Performance →

Referenced by

2 later RFCs formally update or obsolete 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/1379-extending-tcp-for-transactions-concepts