RFC 1644: T/TCP -- TCP Extensions for Transactions Functional Specification
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 specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This memo describes an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1644
- Published
- July 1994
- Authors
- R. Braden
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 38
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.
- RFC 1072 (1988)
- RFC 1106 (1989)
- RFC 1110 (1989)
- RFC 1145 (1990)
- RFC 1146 (1990)
- RFC 1185 (1990)
- RFC 1323 (1992)
- RFC 1379 (1992)
- RFC 1644 (1994)
- RFC 1693 (1994)
- RFC 2018 (1996)
- RFC 6247 (2011)
- RFC 7323 (2014) ✓
Read the full history of TCP Extensions for High Performance →
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.
- RFC 1613cisco Systems X.25 over TCP (XOT)Current
May 1994
- RFC 1693An Extension to TCP : Partial Order ServiceObsoleted
November 1994
- RFC 1792TCP/IPX Connection Mib SpecificationCurrent
April 1995
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
October 1995
- RFC 2001TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery AlgorithmsObsoleted
January 1997
- RFC 2126ISO Transport Service on top of TCP (ITOT)Current
March 1997
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 2229A Dictionary Server ProtocolCurrent
October 1997
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?