<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<rfc ipr="trust200902" obsoletes="10, 120" updates="2010, 2120" submissionType="IETF" prepTime="2017-11-23T09:52:58Z" version="3">
<link href="http://example1.com"/><link href="http://example2.com" rel="author"/>
<front>
  <title abbrev="IP Datagrams on Avian Carriers">vCard Format Specification</title>
  <seriesInfo name="RFC" status="full-standard 1149" stream="IETF" value="1149"/>
  <author fullname="Simon Perreault" surname="Perreault">
    <organization>BBN STC</organization>
    <address>
      <postal>
        <street>10 Moulton Street</street>
        <city>Cambridge</city>
        <code>MA 02238</code>
      </postal>
      <phone>(617) 873-4323</phone>
      <email>simon.perreault@viagenie.ca</email>
      <uri>http://bbn.com</uri>
    </address>
  </author>
  <date day="1" month="April" year="1990"/>
  <area>Internet</area>
  <workgroup>Network Working Group</workgroup>
  <keyword>this</keyword>
  <keyword>that</keyword>

</front><middle>
<section anchor="_introduction" numbered="false">
  <name>Introduction</name>
  <t>The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of <xref target="RFC2119"/> and <xref target="RFC2629"/>, Pete
Resnick, who got this effort started and provided help along the way,
as well as the following individuals who have participated in the
drafting, review, and discussion of this memo:
<xref target="RFC2119">RFC 2119</xref> 0
<xref format="counter" target="RFC2119">RFC 2119</xref> 1
<relref displayFormat="comma" section="2.4" target="RFC2119"/> 2
<relref relative="section2_4" displayFormat="comma" section="2.4" target="RFC2119"/> 3</t>
</section>
</middle><back>
<references anchor="_normative_references">
  <name>Normative References</name>
  <reference anchor="RFC2629" target="https://www.rfc-editor.org/info/rfc2629">
<front>
<title>Writing I-Ds and RFCs using XML</title>
<author initials="M." surname="Rose" fullname="M. Rose">
<organization/>
</author>
<date year="1999" month="June"/>
<abstract>
<t>
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series. This memo provides information for the Internet community.
</t>
</abstract>
</front>
<seriesInfo name="RFC" value="2629"/>
<seriesInfo name="DOI" value="10.17487/RFC2629"/>
</reference>
</references>
<references anchor="_informative_references">
  <name>Informative References</name>
  <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
<front>
<title>
Key words for use in RFCs to Indicate Requirement Levels
</title>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization/>
</author>
<date year="1997" month="March"/>
<abstract>
<t>
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
</references>
</back>
</rfc>