One document matched: draft-ietf-conneg-feature-syntax-er-00.txt

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


        RFC 2738

        Title:      Corrections to "A Syntax for Describing Media
                    Feature Sets"
        Author(s):  G. Klyne
        Status:     Standards Track
        Date:       December 1999
        Mailbox:    GK@ACM.ORG
        Pages:      5
        Characters: 8353
        Updates:    RFC 2533
        I-D Tag:    draft-ietf-conneg-feature-syntax-er-00.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2738.txt


In RFC 2533, "A Syntax for Describing Media Feature Sets", an
expression format is presented for describing media feature
capabilities using simple media feature tags.
 
This memo contains two corrections to that specification:  one
fixes an error in the formal syntax specification, and the other
fixes an error in the rules for reducing feature comparison
predicates.

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