RFC 2531: Content Feature Schema for Internet Fax
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2879.
Current version: RFC 2879 — Content Feature Schema for Internet Fax (V2)
In plain English — editorial summary, not part of the RFC
This document defines a content feature schema that is a profile of the media feature registration mechanisms for use in performing capability identification between extended Internet fax systems. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2531
- Published
- March 1999
- Authors
- G. Klyne; L. McIntyre
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 51
- Also known as
- —
- Obsoleted by:
- RFC 2879
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2506Media Feature Tag Registration ProcedureCurrent
March 1999
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2703Protocol-independent Content Negotiation FrameworkCurrent
September 1999
- RFC 2291Requirements for a Distributed Authoring and Versioning Protocol for the World Wide WebCurrent
February 1998
- RFC 2880Internet Fax T.30 Feature MappingCurrent
August 2000
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 2048Multipurpose Internet Mail Extensions (MIME) Part Four: Registration ProceduresObsoleted
November 1996
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
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?