draft-ietf-msgtrk-smtpext-00.txt   draft-ietf-msgtrk-smtpext-01.txt 
Internet Draft E. Allman Internet Draft E. Allman
draft-ietf-msgtrk-smtpext-00.txt Sendmail, Inc. draft-ietf-msgtrk-smtpext-01.txt Sendmail, Inc.
Valid for six months T. Hansen Valid for six months T. Hansen
Updates: RFC 1891 AT&T Laboratories Updates: RFC 1891 AT&T Laboratories
December 14, 2000 March 20, 2001
SMTP Service Extension SMTP Service Extension
for Message Tracking for Message Tracking
<draft-ietf-msgtrk-smtpext-00.txt> <draft-ietf-msgtrk-smtpext-01.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. Internet-Drafts are with all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also dis- areas, and its working groups. Note that other groups may also dis-
tribute working documents as Internet-Drafts. tribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 3, line 23 skipping to change at page 3, line 23
4.1. The MTRK parameter to the ESMTP MAIL command 4.1. The MTRK parameter to the ESMTP MAIL command
Any sender wishing to track a message must first tag that Any sender wishing to track a message must first tag that
message as trackable by creating two values A and B: message as trackable by creating two values A and B:
A = some-large-random-number A = some-large-random-number
B = SHA1(A) B = SHA1(A)
The large random number A is calculated on a host-dependent The large random number A is calculated on a host-dependent
basis as described in [DRAFT-MTRK-MODEL]. See also [RFC-RANDOM] basis. See [RFC-RANDOM] for a discussion of choosing good ran-
for a discussion of choosing good random numbers. This random dom numbers. This random number MUST be at least 128 bits but
number MUST be at least 128 bits but MUST NOT be more than 1024 MUST NOT be more than 1024 bits.
bits.
The 128-bit hash B of A is then computed using the SHA-1 The 128-bit hash B of A is then computed using the SHA-1
algorithm as described in [NIST-SHA1]. algorithm as described in [NIST-SHA1].
The sender then base64 encodes value B and passes that The sender then base64 encodes value B and passes that
value as the mtrk-certifier on the MAIL FROM command: value as the mtrk-certifier on the MAIL FROM command:
mtrk-parameter = "MTRK=" mtrk-certifier [ ":" mtrk-timeout ] mtrk-parameter = "MTRK=" mtrk-certifier [ ":" mtrk-timeout ]
mtrk-certifier = base64 ; authenticator mtrk-certifier = base64 ; authenticator
mtrk-timeout = 1*9digit; seconds until timeout mtrk-timeout = 1*9digit; seconds until timeout
skipping to change at page 4, line 27 skipping to change at page 4, line 24
4.2. Use of ENVID 4.2. Use of ENVID
To function properly, Message Tracking requires that each To function properly, Message Tracking requires that each
message have a unique identifier that is never reused by any message have a unique identifier that is never reused by any
other message. For that purpose, if the MTRK parameter is other message. For that purpose, if the MTRK parameter is
given, an ENVID parameter MUST be included, and the syntax of given, an ENVID parameter MUST be included, and the syntax of
ENVID from RFC 1891 section 5.4 is extended as follows: ENVID from RFC 1891 section 5.4 is extended as follows:
envid-parameter = "ENVID=" unique-envid envid-parameter = "ENVID=" unique-envid
unique-envid = xtext "@" fqhn unique-envid = local-envid "@" fqhn
local-envid = xtext
fqhn = xtext fqhn = xtext
Any retransmissions of this message MUST assign a new ENVID. In The unique-envid MUST be chosen in such a way that the same
this context, "retransmission" includes forwarding or resending ENVID will never be used by any other message sent from this
a message. system or any other system. In most cases, this means setting
fqhn to be the fully qualified host name of the system generat-
ing this ENVID, and local-envid to an identifier that is never
re-used by that host.
Any retransmissions of this message MUST assign a new
ENVID. In this context, "retransmission" includes forwarding or
resending a message.
4.3. Forwarding Tracking Certifiers 4.3. Forwarding Tracking Certifiers
MTAs SHOULD forward unexpired tracking certifiers to com- MTAs SHOULD forward unexpired tracking certifiers to com-
pliant mailers as the mail is transferred during regular hop-to- pliant mailers as the mail is transferred during regular hop-to-
hop transfers. If the "downstream" MTA is not MTRK-compliant, hop transfers. If the "downstream" MTA is not MTRK-compliant,
then the MTRK= parameter MUST be deleted. If the downstream MTA then the MTRK= parameter MUST be deleted. If the downstream MTA
is DSN-compliant, then the ENVID and ORCPT parameters MUST NOT is DSN-compliant, then the ENVID and ORCPT parameters MUST NOT
be deleted. be deleted.
 End of changes. 7 change blocks. 
11 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/