Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Message Tracking Query Protocol (RFC3887)

IP.com Disclosure Number: IPCOM000031516D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Sep-28
Document File: 24 page(s) / 43K

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 describes the Message Tracking Query Protocol that is used in conjunction with extensions to the ESMTP protocol to provide a complete message tracking solution for the Internet.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group                                          T. Hansen

Request for Comments: 3887                             AT&T Laboratories

Category: Standards Track                                 September 2004

                    Message Tracking Query Protocol

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  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 describes

   the Message Tracking Query Protocol that is used in conjunction with

   extensions to the ESMTP protocol to provide a complete message

   tracking solution for the Internet.

1.  Introduction

   The Message Tracking Models and Requirements document

   [RFC-MTRK-MODEL] discusses the models that message tracking solutions

   could follow, along with requirements for a message tracking solution

   that can be used with the Internet-wide message infrastructure.  This

   memo and its companions, [RFC-MTRK-ESMTP] and [RFC-MTRK-TSN],

   describe a complete message tracking solution that satisfies those

   requirements.  The memo [RFC-MTRK-ESMTP] defines an extension to the

   SMTP service that provides the information necessary to track

   messages.  This memo defines a protocol that can be used to query the

   status of messages that have been transmitted on the Internet via

   SMTP.  The memo [RFC-MTRK-TSN] describes the message/tracking-status

   [RFC-MIME] media type that is used to report tracking status

   information.  Using the model document's terminology, this solution

   uses active enabling and active requests with both request and

   chaining referrals.

Hansen                      Standards Track                     [Page 1]

RFC 3887            Message Tracking Query Protocol       September 2004

1.1.  Terminology

   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].

   All syntax descriptions use the ABNF specified by [RFC-ABNF].

   Terminal nodes not defined elsewhere in this document are defined in

   [RFC-ABNF], [RFC-URI], [R...