RFC 2533: A Syntax for Describing Media Feature Sets
In plain English — editorial summary, not part of the RFC
This document introduces and describes a syntax that can be used to define feature sets which are formed from combinations and relations involving individual media features. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2533
- Published
- March 1999
- Authors
- G. Klyne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 37
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2306Tag Image File Format (TIFF) - F Profile for FacsimileCurrent
March 1998
- RFC 2305A Simple Mode of Facsimile Using Internet MailObsoleted
March 1998
- RFC 3965A Simple Mode of Facsimile Using Internet MailCurrent
December 2004
- RFC 2534Media Features for Display, Print, and FaxCurrent
March 1999
- RFC 2577FTP Security ConsiderationsCurrent
May 1999
- RFC 2653CIP Transport ProtocolsCurrent
August 1999
- RFC 2254The String Representation of LDAP Search FiltersObsoleted
December 1997
- RFC 2253Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished NamesObsoleted
December 1997
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?