Message Tracking Model and Requirements
RFC 3888, “Message Tracking Model and Requirements”, is an Informational document published in September 2004 by T. Hansen. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3888 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3887 Message Tracking Query Protocol
- RFC 3886 An Extensible Message Format for Message Tracking Responses
- RFC 3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol
- RFC 3885 SMTP Service Extension for Message Tracking
- RFC 3891 The Session Initiation Protocol "Replaces" Header
- RFC 3884 Use of IPsec Transport Mode for Dynamic Routing
- RFC 3892 The Session Initiation Protocol Referred-By Mechanism
- RFC 3883 Detecting Inactive Neighbors over OSPF Demand Circuits