RFC 2703: Protocol-independent Content Negotiation Framework
In plain English — editorial summary, not part of the RFC
This memo sets out terminology, an abstract framework and goals for protocol-independent content negotiation, and identifies some technical issues which may need to be addressed. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2703
- Published
- September 1999
- Authors
- G. Klyne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2717Registration Procedures for URL Scheme NamesObsoleted
November 1999
- RFC 2718Guidelines for new URL SchemesObsoleted
November 1999
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2531Content Feature Schema for Internet FaxObsoleted
March 1999
- RFC 2879Content Feature Schema for Internet Fax (V2)Current
August 2000
- RFC 2880Internet Fax T.30 Feature MappingCurrent
August 2000
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?