RFC 3803 on Content Duration MIME Header Definition
rfc-editor@rfc-editor.org Fri, 25 June 2004 16:41 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20908 for <ietf-announce-archive@ietf.org>; Fri, 25 Jun 2004 12:41:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdtln-0006sj-6l for ietf-announce-archive@ietf.org; Fri, 25 Jun 2004 12:41:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdtjw-0006Dr-00 for ietf-announce-archive@ietf.org; Fri, 25 Jun 2004 12:39:48 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1Bdtig-0005Wb-00; Fri, 25 Jun 2004 12:38:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BdtFv-00060q-FY; Fri, 25 Jun 2004 12:08:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdd9E-00072u-8E for ietf-announce@megatron.ietf.org; Thu, 24 Jun 2004 18:56:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25091 for <ietf-announce@ietf.org>; Thu, 24 Jun 2004 18:56:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdd8z-0005og-8l for ietf-announce@ietf.org; Thu, 24 Jun 2004 18:56:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BdcVU-0004Zp-00 for ietf-announce@ietf.org; Thu, 24 Jun 2004 18:15:45 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BdbkW-0003Av-00 for ietf-announce@ietf.org; Thu, 24 Jun 2004 17:27:12 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5OLPqJ15755; Thu, 24 Jun 2004 14:25:52 -0700 (PDT)
Message-Id: <200406242125.i5OLPqJ15755@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 24 Jun 2004 14:25:52 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Fri, 25 Jun 2004 12:08:45 -0400
Cc: vpim@lists.neystadt.org, rfc-editor@rfc-editor.org
Subject: RFC 3803 on Content Duration MIME Header Definition
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries. RFC 3803 Title: Content Duration MIME Header Definition Author(s): G. Vaudreuil, G. Parsons Status: Standards Track Date: June 2004 Mailbox: gregv@ieee.org, gparsons@nortelnetworks.com Pages: 5 Characters: 8213 Obsoletes: 2424 I-D Tag: draft-ietf-vpim-vpimv2r2-dur-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3803.txt This document describes the MIME header Content-Duration that is intended for use with any time varying media content (typically audio/* or video/*). This document is a product of the Voice Profile for Internet Mail Working Group of the IETF. This is now a Draft Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce