RFC 2880: Internet Fax T.30 Feature Mapping
In plain English — editorial summary, not part of the RFC
This document describes how to map Group 3 fax capability identification bits, described in ITU T.30, into the Internet fax feature schema described in "Content feature schema for Internet fax". This memo provides information for the Internet community.
Document record
- Document ID
- RFC2880
- Published
- August 2000
- Authors
- L. McIntyre; G. Klyne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2879Content Feature Schema for Internet Fax (V2)Current
August 2000
- RFC 2938Identifying Composite Media FeaturesCurrent
September 2000
- RFC 2703Protocol-independent Content Negotiation FrameworkCurrent
September 1999
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2531Content Feature Schema for Internet FaxObsoleted
March 1999
- 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?