RFC 3023: XML Media Types
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7303.
Current document in this lineage: RFC 7303 — XML Media Types
In plain English — editorial summary, not part of the RFC
This document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3023
- Published
- January 2001
- Authors
- M. Murata; S. St. Laurent; D. Kohn
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 39
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2376 (1998)
- RFC 3023 (2001)
- RFC 7303 (2014) ✓
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 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 2831Using Digest Authentication as a SASL MechanismObsoleted
May 2000
- RFC 3229Delta encoding in HTTPCurrent
January 2002
- RFC 3230Instance Digests in HTTPObsoleted
January 2002
- RFC 2756Hyper Text Caching Protocol (HTCP/0.0)Current
January 2000
- RFC 2186Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 3017XML DTD for Roaming Access Phone BookCurrent
December 2000
- RFC 2965HTTP State Management MechanismObsoleted
October 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?