RFC 2372: Transaction Internet Protocol - Requirements and Supplemental Information
In plain English — editorial summary, not part of the RFC
This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2372
- Published
- July 1998
- Authors
- K. Evans; J. Klein; J. Lyon
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2371Transaction Internet Protocol Version 3.0Current
July 1998
- RFC 2426vCard MIME Directory ProfileObsoleted
September 1998
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2447iCalendar Message-Based Interoperability Protocol (iMIP)Obsoleted
November 1998
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2256A Summary of the X.500(96) User Schema for use with LDAPv3Obsoleted
December 1997
- RFC 2255The LDAP URL FormatObsoleted
December 1997
- RFC 2248Network Services Monitoring MIBObsoleted
January 1998
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?