RFC 3888: Message Tracking Model and Requirements
In plain English — editorial summary, not part of the RFC
Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document provides a model of message tracking that can be used for understanding the Internet-wide message infrastructure and to further enhance those capabilities to include message tracking, as well as requirements for proposed message tracking solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3888
- Published
- September 2004
- Authors
- T. Hansen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3887Message Tracking Query ProtocolUpdated
September 2004
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 3897Open Pluggable Edge Services (OPES) Entities and End Points CommunicationCurrent
September 2004
- RFC 3876Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)Current
September 2004
- RFC 3867Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)Current
November 2004
- RFC 3863Presence Information Data Format (PIDF)Current
August 2004
- RFC 3862Common Presence and Instant Messaging (CPIM): Message FormatCurrent
August 2004
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?