FW: I-D ACTION:draft-ietf-vpim-cc-07.txt

"Eric Burger" <[email protected]> Wed, 5 Jun 2002 07:11:45 -0400
Newsgroups gmane.ietf.vpim
Message-ID <[email protected]>
This is a multi-part message in MIME format.

------=_NextPart_000_00F1_01C20C60.405FA940
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

This refresh addresses the issues raised by the IESG.  Fixing it for the
IESG also addressed Jutta's issue, by removing the vnd.* type.

Do we need another WGLC, or can it go straight to the IESG for final review?

-----Original Message-----
From: [email protected] [mailto:[email protected]]On
Behalf Of [email protected]
Sent: Tuesday, June 04, 2002 7:45 AM
To: IETF-Announce:
Cc: [email protected]
Subject: I-D ACTION:draft-ietf-vpim-cc-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Voice Profile for Internet Mail Working
Group of the IETF.

	Title		: Critical Content MIME Parameter
	Author(s)	: E. Burger
	Filename	: draft-ietf-vpim-cc-07.txt
	Pages		: 17
	Date		: 03-Jun-02

This document describes the use of a mechanism for identifying body
parts that a sender deems critical in a multi-part Internet mail
message.  The mechanism described is a parameter to Content-
Disposition, as described by RFC 3204.
By knowing what parts of a message the sender deems critical, a
content gateway can intelligently handle multi-part messages when
providing gateway services to systems of lesser capability.
Critical content can help a content gateway to decide what parts to
forward.  It can indicate how hard a gateway should try to deliver a
body part.  It can help the gateway to pick body parts that are safe
to silently delete when a system of lesser capability receives a
message.  In addition, critical content can help the gateway chose
the notification strategy for the receiving system.  Likewise, if
the sender expects the destination to do some processing on a body
part, critical content allows the sender to mark body parts that the
receiver must process.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-vpim-cc-07.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-ietf-vpim-cc-07.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-ietf-vpim-cc-07.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_000_00F1_01C20C60.405FA940
Content-Type: Message/External-body;
	name="ATT00178.dat"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="ATT00178.dat"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-vpim-cc-07.txt

------=_NextPart_000_00F1_01C20C60.405FA940
Content-Type: Message/External-body;
	name="draft-ietf-vpim-cc-07.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="draft-ietf-vpim-cc-07.txt"

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

------=_NextPart_000_00F1_01C20C60.405FA940--

----------------------------------------------------------
This message was sent to you, since you are subscribed to
[email protected]. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo