Skip to main content

Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3470.
Authors Dr. Marshall T. Rose , Scott Hollenbeck , Larry M Masinter
Last updated 2020-01-21 (Latest revision 2002-11-07)
RFC stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3470 (Best Current Practice)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ned Freed
IESG note published 24-Jan-2003
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        BCP 70
        RFC 3470

        Title:      Guidelines for the Use of Extensible Markup
                    Language (XML) within IETF Protocols
        Author(s):  S. Hollenbeck, M. Rose, L. Masinter
        Status:     Best Current Practice
        Date:       January 2003
        Pages:      28
        Characters: 64252
        SeeAlso:    BCP 70

        I-D Tag:    draft-hollenbeck-ietf-xml-guidelines-07.txt


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.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.