RFC 2371: Transaction Internet Protocol Version 3.0
In plain English — editorial summary, not part of the RFC
In many applications where different nodes cooperate on some work, there is a need to guarantee that the work happens atomically. That is, each node must reach the same conclusion as to whether the work is to be completed, even in the face of failures. This document proposes a simple, easily-implemented protocol for achieving this end. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2371
- Published
- July 1998
- Authors
- J. Lyon; K. Evans; J. Klein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2372Transaction Internet Protocol - Requirements and Supplemental InformationCurrent
July 1998
- RFC 2426vCard MIME Directory ProfileObsoleted
September 1998
- RFC 2447iCalendar Message-Based Interoperability Protocol (iMIP)Obsoleted
November 1998
- RFC 2234Augmented BNF for Syntax Specifications: ABNFObsoleted
November 1997
- RFC 2706ECML v1: Field Names for E-CommerceObsoleted
October 1999
- RFC 2801Internet Open Trading Protocol - IOTP Version 1.0Current
April 2000
- RFC 2802Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)Current
April 2000
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
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?