Network Working Group J. Arkko Internet-Draft Ericsson Updates: 1166 (if approved) M. Cotton Intended status: Informational L. Vegoda Expires: December 14, 2009 ICANN June 12, 2009 IPv4 Address Blocks Reserved for Documentation draft-iana-ipv4-examples-00 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on December 14, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract Three IPv4 unicast address blocks are reserved for use in examples in Arkko, et al. Expires December 14, 2009 [Page 1]
Internet-Draft IPv4 Examples June 2009 specifications and other documents. This document describes the use of these blocks. 1. Introduction This document describes the 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. [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. These addresses are complementary to other documentation ranges defined in the IETF, including the IPv6 documentation prefixes [RFC3849] and example domain names [RFC2606]. 2. Terminology 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, [RFC2119]. 3. Documentation Address Blocks 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. 4. Operational Implications 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 [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. These blocks are not for local use, and the filters may be used in both local and public contexts. Arkko, et al. Expires December 14, 2009 [Page 2]
Internet-Draft IPv4 Examples June 2009 5. Security Considerations This document has no security implications. 6. IANA Considerations IANA should record the allocation of the three address blocks in the IPv4 address registry. No end party is to be assigned these addresses. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet numbers", RFC 1166, July 1990. [RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and J. Postel, "INTERNET REGISTRY IP ALLOCATION GUIDELINES", BCP 12, RFC 2050, November 1996. [RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 32, RFC 2606, June 1999. [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004. Appendix A. Acknowledgments 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 [RFC3849]. The authors would also like to thank Geoff Huston, Peter Koch, Ulf Olsson and others for interesting discussions of this topic. Arkko, et al. Expires December 14, 2009 [Page 3]
Internet-Draft IPv4 Examples June 2009 Authors' Addresses Jari Arkko Ericsson Jorvas 02420 Finland Email: jari.arkko@piuha.net Michelle Cotton Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey 90292 United States of America Phone: +310-823-9358 Email: michelle.cotton@icann.org URI: http://www.iana.org/ Leo Vegoda Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey 90292 United States of America Phone: +310-823-9358 Email: leo.vegoda@icann.org URI: http://www.iana.org/ Arkko, et al. Expires December 14, 2009 [Page 4]
