One document matched: draft-iana-ipv4-examples-01.xml

<?xml version="1.0" encoding="iso-8859-1" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<rfc ipr="trust200902"
     docName="draft-iana-ipv4-examples-01"
     category="info"
     updates="1166">

<?rfc toc="no"?> <?rfc symrefs="yes"?> <?rfc autobreaks="yes"?>
<?rfc tocindent="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?>

<front>

<title abbrev="IPv4 Examples">IPv4 Address Blocks Reserved for Documentation</title>

<author initials="J" surname="Arkko" fullname="Jari Arkko">
<organization>Ericsson</organization>
<address>
<postal>
<street/>
<city>Jorvas</city> <code>02420</code>
<country>Finland</country>
</postal>
<email>jari.arkko@piuha.net</email>
</address>
</author>

<author initials="M." surname="Cotton" fullname="Michelle Cotton">

	<organization abbrev="ICANN">

		Internet Corporation for Assigned Names and Numbers

	</organization>

	<address>

		<postal>

			<street>4676 Admiralty Way, Suite 330</street>

			<code>90292</code> <city>Marina del Rey</city>

			<country>United States of America</country>

		</postal>

		<phone>+310-823-9358</phone>

		<email>michelle.cotton@icann.org</email>

		<uri>

			http://www.iana.org/

		</uri>

	</address>

</author>

        <author initials="L." surname="Vegoda" fullname="Leo Vegoda">
                
                <organization abbrev="ICANN">
                        
                        Internet Corporation for Assigned Names and Numbers
                        
                </organization>
                
                <address>
                        
                        <postal>
                                
                                <street>4676 Admiralty Way, Suite 330</street>
                                
                                <code>90292</code> <city>Marina del Rey</city>
                                
                                <country>United States of America</country>
                                
                        </postal>
                        
                        <phone>+310-823-9358</phone>
                        
                        <email>leo.vegoda@icann.org</email>
                        
                        <uri>
                                
                                http://www.iana.org/
                                
                        </uri>
                        
                </address>
                
        </author>

<date month="June" year="2009" />

<keyword>example addresses</keyword>
<keyword>IPv4</keyword>

<abstract>

<t>Three IPv4 unicast address blocks are reserved for use in examples
   in specifications and other documents.  This document describes the
   use of these blocks.</t>

</abstract>

</front>
<middle>

<section anchor="intro" title="Introduction">

   <t>This document describes three IPv4 address blocks that are provided 
      for use in documentation.  The use of designated address ranges for
      documentation and examples reduces the likelihood of conflicts and
      confusion arising from the use of addresses assigned for some other
      purpose.</t>

   <t><xref target="RFC1166"/> reserves the first of the three address blocks,
      192.0.2.0/24.  The other two address blocks have recently been
      allocated for this purpose, to ease the writing of examples involving
      addresses from multiple networks.</t>
   
   <t>Other documentation ranges have been defined in the IETF, including 
      the IPv6 documentation prefix <xref target="RFC3849"/> and example 
      domain names <xref target="RFC2606"/>. Documentation also makes use 
      of the ranges reserved in <xref target="RFC1918"/>.</t>

</section>

<section title="Terminology">
         
	<t>

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be 
interpreted as described in BCP 14, <xref target="RFC2119"/>.

	</t>

</section>

<section title="Documentation Address Blocks">

   <t>The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24
   (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3) are provided for use
   in documentation.
   </t>

</section>

<section title="Operational Implications">

   <t>Addresses within the TEST-NET-1, TEST-NET-2, and TEST-NET-3
   blocks SHOULD NOT appear on the public Internet and are used
   without any coordination with IANA or an Internet registry
   <xref target="RFC2050"/>.  Network operators SHOULD add these
   address blocks to the list of non-routeable address space, and if
   packet filters are deployed, then this address block SHOULD be
   added to packet filters.</t>

   <t>These blocks are not for local use, and the filters may be used
   in both local and public contexts.</t>

</section>

<section title='Security Considerations'>

   <t>This document has no security implications.</t>

</section>

<section title="IANA Considerations">

   <t>IANA should record the allocation of the three address blocks in
   the IPv4 address registry. No end party is to be assigned these
   addresses.</t>

</section>

</middle>
<back>

<references title="Normative References">
      <?rfc include="reference.RFC.2119.xml"?>
</references>

<references title="Informative References">
      <?rfc include="reference.RFC.1166.xml"?>
      <?rfc include="reference.RFC.1918.xml"?>
      <?rfc include="reference.RFC.2050.xml"?>
      <?rfc include="reference.RFC.2606.xml"?>
      <?rfc include="reference.RFC.3849.xml"?>
</references>

<section title="Acknowledgments">

<t>The authors would like to offer a special note of thanks to APNIC,
which nominated 198.51.100.0/24 and 203.0.113.0/24 for this purpose.
The authors would also like to acknowledge that this document inherits
material from <xref target="RFC3849"/>.</t>

<t>The authors would also like to thank Geoff Huston, Peter Koch, Ulf
Olsson, John Klensin and others for interesting discussions of this topic.</t>

</section>

</back>
</rfc>