RFC 2938: Identifying Composite Media Features
In plain English — editorial summary, not part of the RFC
This document describes an abbreviated format for a composite media feature set, based upon a hash of the feature expression describing that composite. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2938
- Published
- September 2000
- Authors
- G. Klyne; L. Masinter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 18
- Also known as
- —
- Updates:
- RFC 2533
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2880Internet Fax T.30 Feature MappingCurrent
August 2000
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
- RFC 4357Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 AlgorithmsCurrent
January 2006
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated
November 2012
- RFC 8819YANG Module TagsCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?