FWD: I-D ACTION:draft-klensin-email-envelope-00.txt

--==========205C0896BCAF102B84B0==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The draft posted/described in the attached is a bizarre idea, 
partially to see if it is possible to consider a radical 
solution to an increasingly troublesome problem, and partially 
to see if the supportive comments about "Email NG" in 
Minneapolis were really serious.

I am not at all convinced that it is a _good_ idea, only that, 
if we are talking about radical changes to the mail 
infrastructure to support various extended services, this is the 
sort of "clean up the warts that get in the way" option we might 
want to consider.

And even if it were a good idea, some of the details are 
probably not right -- if this looks like it received a day's 
thought, you would probably be guessing much too high.

Discussion should probably go to the SMTP list; IMAA is copied 
only because this could interact a bit with some of the "UTF-8 
header" discussions.

   john

--==========205C0896BCAF102B84B0==========
Content-Type: message/rfc822;
 name="I-D ACTION:draft-klensin-email-envelope-00.txt"

Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Fri, 23 Jan 2004 16:17:32 -0500
Received: from [132.151.6.40] (helo=asgard.ietf.org)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Ak8gC-000Gxo-00
	for [email protected]; Fri, 23 Jan 2004 16:17:28 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ak8SP-0001Bz-IT
	for [email protected]; Fri, 23 Jan 2004 16:03:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ak8OY-00018X-AI
	for [email protected]; Fri, 23 Jan 2004 15:59:14 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21888
	for <[email protected]>; Fri, 23 Jan 2004 15:59:11 -0500 (EST)
Message-Id: <[email protected]>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: [email protected]
Reply-to: [email protected]
Subject: I-D ACTION:draft-klensin-email-envelope-00.txt
Date: Fri, 23 Jan 2004 15:59:11 -0500
Sender: [email protected]
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Cleaner SMTP Envelope for Internet Mail
	Author(s)	: J. Klensin
	Filename	: draft-klensin-email-envelope-00.txt
	Pages		: 0
	Date		: 2004-1-23
	
During the last few years, a number of proposals for
extensions or improvements to email have run into trouble with a
side-effect of mail relaying.  In the current Internet Mail model, every SMTP server is required to break strict layering by inserting one or more additional 'trace' headers into the message headers which are actually part of the SMTP payload.  Since the headers are
altered in transit, header-signing is not an available option, various
anti-spam and internationalization strategies are infeasible or much
more complex, and so on.  This document proposes to change the
Internet mail model to place the in-transit trace information in the
envelope, removing the requirement that relaying systems modify the
message payload.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klensin-email-envelope-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-klensin-email-envelope-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email protected].
In the body type:
	"FILE /internet-drafts/draft-klensin-email-envelope-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID:	<[email protected]>

ENCODING mime
FILE /internet-drafts/draft-klensin-email-envelope-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-klensin-email-envelope-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email protected]>

--OtherAccess--

--NextPart--




--==========205C0896BCAF102B84B0==========--