RFC 2912 on Indicating Media Features for MIME Content
RFC Editor <rfc-ed@ISI.EDU> Tue, 12 September 2000 18:49 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11938; Tue, 12 Sep 2000 14:49:48 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA25334 for ietf-123-outbound.10@ietf.org; Tue, 12 Sep 2000 14:35:00 -0400 (EDT)
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 OAA25303 for <all-ietf@loki.ietf.org>; Tue, 12 Sep 2000 14:26:22 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11412 for <all-ietf@ietf.org>; Tue, 12 Sep 2000 14:26:20 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA25881; Tue, 12 Sep 2000 11:26:20 -0700 (PDT)
Message-Id: <200009121826.LAA25881@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2912 on Indicating Media Features for MIME Content
Cc: rfc-ed@ISI.EDU, ietf-medfree@IMC.ORG
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 12 Sep 2000 11:26:20 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2912 Title: Indicating Media Features for MIME Content Author(s): G. Klyne Status: Standards Track Date: September 2000 Mailbox: GK@ACM.ORG Pages: 11 Characters: 20618 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-conneg-content-features-03.txt URL: ftp://ftp.isi.edu/in-notes/rfc2912.txt In "A Syntax for Describing Media Feature Sets", an expression format is presented for describing media feature capabilities using simple media feature tags. This memo defines a Multipurpose Internet Mail Extensions (MIME) 'Content-features:' header that can be used to annotate a MIME message part using this expression format, and indicates some ways it might be used. This document is a product of the Content Negotiation Working Group of the IETF. This is now a Proposed 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.