RFC 2839 on Identifying Composite Media Features
RFC Editor <rfc-ed@ISI.EDU> Wed, 04 October 2000 22:46 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03372; Wed, 4 Oct 2000 18:46:24 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA17616 for ietf-123-outbound.10@ietf.org; Wed, 4 Oct 2000 18:45:02 -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 SAA17556 for <all-ietf@loki.ietf.org>; Wed, 4 Oct 2000 18:35:46 -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 SAA03220 for <all-ietf@ietf.org>; Wed, 4 Oct 2000 18:35:44 -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 PAA14045; Wed, 4 Oct 2000 15:35:43 -0700 (PDT)
Message-Id: <200010042235.PAA14045@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2839 on Identifying Composite Media Features
Cc: rfc-ed@ISI.EDU, ietf-medfree@IMC.ORG
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 04 Oct 2000 15:35:43 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2938 Title: Identifying Composite Media Features Author(s): G. Klyne, L. Masinter Status: Standards Track Date: September 2000 Mailbox: GK@ACM.ORG, LMM@acm.org Pages: 18 Characters: 34451 Updates: 2533 I-D Tag: draft-ietf-conneg-feature-hash-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2938.txt In RFC 2533, an expression format is presented for describing media feature capabilities as a combination of simple media feature tags. This document describes an abbreviated format for a composite media feature set, based upon a hash of the feature expression describing that composite. 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.