< draft-ietf-msgtrk-smtpext-04.txt		draft-ietf-msgtrk-smtpext-05.txt >
	Internet Draft E. Allman		Internet Draft E. Allman
	draft-ietf-msgtrk-smtpext-04.txt Sendmail, Inc.		draft-ietf-msgtrk-smtpext-05.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
	October 21, 2002		March 19, 2003
	SMTP Service Extension		SMTP Service Extension
	for Message Tracking		for Message Tracking
	<draft-ietf-msgtrk-smtpext-04.txt>		<draft-ietf-msgtrk-smtpext-05.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		areas, and its working groups. Note that other groups may also
	distribute working documents as Internet-Drafts.		distribute 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 2, line ? ¶		skipping to change at page 2, line ? ¶
	MTRK-MODEL].		MTRK-MODEL].
	Doing a Message Tracking query is intended as a "last resort"		Doing a Message Tracking query is intended as a "last resort"
	mechanism. Normally, Delivery Status Notifications (DSNs) [RFC-		mechanism. Normally, Delivery Status Notifications (DSNs) [RFC-
	DSN-SMTP] and Message Disposition Notifications (MDNs) [RFC-MDN]		DSN-SMTP] and Message Disposition Notifications (MDNs) [RFC-MDN]
	would provide the primary delivery status. Only if the message is		would provide the primary delivery status. Only if the message is
	not received, or there is no response from either of these		not received, or there is no response from either of these
	mechanisms should a Message Tracking query be issued.		mechanisms should a Message Tracking query be issued.
	The definition of the base64 token is imported from section		The definition of the base64 token is imported from section
	6.8 of [RFC-MIME].		6.8 of [RFC-MIME]. Formally,
			base64 = %2b / %2f / %x30-39 / %x41-5a / %x61-7a
			The definition of the DIGIT token is imported from [RFC-
			MSGFMT]. Formally,
			DIGIT = %x30-39
	Syntax notation in this document conforms to [RFC-ABNF].		Syntax notation in this document conforms to [RFC-ABNF].
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
	NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"		NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
	in this document are to be interpreted as described in RFC 2119		in this document are to be interpreted as described in RFC 2119
	[RFC-KEYWORDS].		[RFC-KEYWORDS].
	3. SMTP Extension Overview		3. SMTP Extension Overview
	skipping to change at page 3, line 53 ¶		skipping to change at page 4, line 7 ¶
	but MUST NOT be more than 1024 bits.		but MUST NOT be more than 1024 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 command:		value as the mtrk-certifier on the MAIL 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
	A is stored in the originator's tracking database to		A is stored in the originator's tracking database to
	validate future tracking requests as described in [DRAFT-MTRK-		validate future tracking requests as described in [DRAFT-MTRK-
	MTQP]. B is stored in tracking databases of compliant receiver		MTQP]. B is stored in tracking databases of compliant receiver
	MTAs and used to authenticate future tracking requests.		MTAs and used to authenticate future tracking requests.
	The mtrk-timeout field indicates the number of seconds that		The mtrk-timeout field indicates the number of seconds that
	the client requests that this tracking information be retained		the client requests that this tracking information be retained
	on intermediate servers, as measured from the initial receipt of		on intermediate servers, as measured from the initial receipt of
	the message at that server. Servers MAY ignore this value if it		the message at that server. Servers MAY ignore this value if it
End of changes. 5 change blocks.
	5 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/