RFC 3470: Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols
In plain English — editorial summary, not part of the RFC
The Extensible Markup Language (XML) is a framework for structuring data. While it evolved from Standard Generalized Markup Language (SGML) -- a markup language primarily focused on structuring documents -- XML has evolved to be a widely-used mechanism for representing structured data. There are a wide variety of Internet protocols being developed; many have need for a representation for structured data relevant to their application. There has been much interest in the use of XML as a representation method. This document describes basic XML concepts, analyzes various alternatives in the use of XML, and provides guidelines for the use of XML within IETF standards-track protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3470
- Published
- January 2003
- Authors
- S. Hollenbeck; M. Rose; L. Masinter
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 28
- Also known as
- BCP70
- Updated by:
- RFC 8996
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 1609Charting Networks in the X.500 DirectoryCurrent
March 1994
- RFC 1608Representing IP Information in the X.500 DirectoryCurrent
March 1994
- RFC 3447Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1Obsoleted
February 2003
- RFC 3406Uniform Resource Names (URN) Namespace Definition MechanismsObsoleted
October 2002
- RFC 3593Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
September 2003
- RFC 3198Terminology for Policy-Based ManagementCurrent
November 2001
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 3150End-to-end Performance Implications of Slow LinksCurrent
July 2001
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?