RFC 2913 on MIME Content in Media Feature Expressions

[RFC Editor <rfc-ed@xxxxxxx>]

A new Request for Comments is now available in online RFC libraries.


        RFC 2913

        Title:	    MIME Content Types in Media Feature Expressions
        Author(s):  G. Klyne
        Status:     Standards Track
	Date:       September 2000
        Mailbox:    GK@xxxxxxx
        Pages:      9
        Characters: 16095
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-conneg-feature-type-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2913.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 media feature tag whose value is a Multipurpose
Internet Mail Extensions (MIME) content type.  This allows the
construction of feature expressions that take account of the MIME
content type of the corresponding data.

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@xxxxxxxxx  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@xxxxxxxxxxxxxx
        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@xxxxxxxxxxxxxxx  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@xxxxxxxxxxxxxxx  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.

<ftp://ftp.isi.edu/in-notes/rfc2913.txt>