<?xml version='1.0'?>

<reference anchor='RFC3470'>

<front>
<title abbrev='XML Within IETF Protocols'>
     Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols</title>
<author initials='S.' surname='Hollenbeck' fullname='Scott Hollenbeck'>
<organization>VeriSign, Inc.</organization>
<address>
<postal>
<street>21345 Ridgetop Circle</street>
<city>Dulles</city>
<region>VA</region>
<code>20166-6503</code>
<country>US</country></postal>
<phone>+1 703 948 3257</phone>
<email>shollenbeck@verisign.com</email></address></author>
<author initials='M.' surname='Rose' fullname='Marshall T. Rose'>
<organization>Dover Beach Consulting, Inc.</organization>
<address>
<postal>
<street>POB 255268</street>
<city>Sacramento</city>
<region>CA</region>
<code>95865-5268</code>
<country>US</country></postal>
<phone>+1 916 483 8878</phone>
<email>mrose@dbc.mtview.ca.us</email></address></author>
<author initials='L.' surname='Masinter' fullname='Larry Masinter'>
<organization>Adobe Systems Incorporated</organization>
<address>
<postal>
<street>Mail Stop W14</street>
<street>345 Park Ave.</street>
<city>San Jose</city>
<region>CA</region>
<code>95110</code>
<country>US</country></postal>
<phone>+1 408 536 3024</phone>
<email>LMM@acm.org</email>
<uri>http://larry.masinter.net</uri></address></author>
<date year='2003' month='January' day='23' />
<area>General</area>
<keyword>BCP</keyword>
<keyword>Best Current Practice</keyword>
<keyword>XML</keyword>
<keyword>Extensible Markup Language</keyword>
<abstract>
<t>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.</t>
<t>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.</t></abstract>
<note title='Conventions Used In This Document'>
<t>This document recommends, as policy, what specifications for Internet
      protocols -- and, in particular, IETF standards track protocol documents
      -- should include as normative language within them.  The capitalized
      keywords "SHOULD", "MUST", "REQUIRED", etc. are used in the sense of how
      they would be used within other documents with the meanings as specified
      in BCP 14, RFC 2119 .</t></note></front>

<seriesInfo name='BCP' value='70' />
<seriesInfo name='RFC' value='3470' />
<format type='TXT' octets='64252' target='ftp://ftp.isi.edu/in-notes/rfc3470.txt' />
<format type='HTML' octets='95246' target='http://xml.resource.org/public/rfc/html/rfc3470.html' />
<format type='XML' octets='103046' target='http://xml.resource.org/public/rfc/xml/rfc3470.xml' />
</reference>
