Browse Prior Art Database

Message Tracking Model and Requirements (RFC3888)

IP.com Disclosure Number: IPCOM000031517D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Nov-12
Document File: 12 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Hansen: AUTHOR

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group                                          T. Hansen

Request for Comments: 3888                             AT&T Laboratories

Category: Informational                                   September 2004

                Message Tracking Model and Requirements

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

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.

1.  Problem Statement

   Consider sending a package through a package delivery company.  Once

   you've sent a package, you would like to be able to find out if the

   package has been delivered or not, and if not, where that package

   currently is and what its status is.  Note that the status of a

   package may not include whether it was delivered to its addressee,

   but just the destination.  Many package carriers provide such

   services today, often via a web interface.

   Message tracking extends that capability to the Internet-wide message

   infrastructure, analogous to the service provided by package

   carriers:  the ability to quickly locate where a message (package)

   is, and to determine whether or not the message (package) has been

   delivered to its final destination.  An Internet-standard approach

   will allow the development of message tracking applications that can

   operate in a multi-vendor messaging environment, and will encourage

   the operation of the function across administrative boundaries.

Hansen                       Informational                      [Page 1]

RFC 3888        Message Tracking Model and Requirements   September 2004

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

   document are to be interpreted as described in BCP 14, RFC 2119

   [RFC-KEYWORDS].

2.  Definitions

   The following terms are relevant to message tracking.  The terms

   Tracking User Agent and Tracking Server are new, while all other

   terms have been collected here from other sources.

   Originating Mail User Agent (MUA)

           ...