Protocol Action: Message Context for Internet Mail to Proposed Standard
The IESG <iesg-secretary@ietf.org> Sun, 03 November 2002 16:18 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09505; Sun, 3 Nov 2002 11:18:24 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA17166 for ietf-123-outbound.10@ietf.org; Sun, 3 Nov 2002 11:15:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA17117 for <all-ietf@loki.ietf.org>; Sun, 3 Nov 2002 11:08:35 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09170; Sun, 3 Nov 2002 11:06:08 -0500 (EST)
Message-Id: <200211031606.LAA09170@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@iab.org>
Cc: vpim@lists.neystadt.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Message Context for Internet Mail to Proposed Standard
Date: Sun, 03 Nov 2002 11:06:08 -0500
Sender: scoya@cnri.reston.va.us
The IESG has approved Critical Content of Internet Mail <draft-ietf-vpim-cc-08.txt> for publication as a Proposed Standard This document is the product of the Voice Profile for Internet Mail Working Group. The IESG contact persons are Ned Freed and Patrik Faltstrom. Technical Summary This document describes 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. By knowing what parts of a message the sender deems critical, a content gateway can intelligently handle multi-part messages when gatewaying 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. Working Group Summary This document has been revised after an initial last call to align it with the handling content-type parameter defined in RFC 3204. This mechanism can be used in conjunction with both VPIM and non-VPIM messages. Protocol Quality Ned Freed reviewed these documents for the IESG.