Skip to main content

IPv4 Address Blocks Reserved for Documentation

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 5737.
Authors Jari Arkko , Michelle Cotton , Leo Vegoda
Last updated 2015-10-14 (Latest revision 2009-09-21)
RFC stream Internet Engineering Task Force (IETF)
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 5737 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Russ Housley
Send notices to (None)
Network Working Group                                           J. Arkko
Internet-Draft                                                  Ericsson
Updates: 1166 (if approved)                                    M. Cotton
Intended status: Informational                                 L. Vegoda
Expires: March 25, 2010                                            ICANN
                                                      September 21, 2009

             IPv4 Address Blocks Reserved for Documentation

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-

   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

   The list of Internet-Draft Shadow Directories can be accessed at

   This Internet-Draft will expire on March 25, 2010.

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 (
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.


   Three IPv4 unicast address blocks are reserved for use in examples in

Arkko, et al.            Expires March 25, 2010                 [Page 1]
Internet-Draft                IPv4 Examples               September 2009

   specifications and other documents.  This document describes the use
   of these blocks.

1.  Introduction

   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

   [RFC1166] reserves the first of the three address blocks,  The other two address blocks have recently been
   allocated for this purpose, primarily to ease the writing of examples
   involving addresses from multiple networks.

   Other documentation ranges have been defined in the IETF, including
   the IPv6 documentation prefix [RFC3849] and example domain names
   [RFC2606].  Documentation also makes use of the ranges reserved in

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in BCP 14, [RFC2119].

3.  Documentation Address Blocks

   The blocks (TEST-NET-1), (TEST-NET-2),
   and (TEST-NET-3) are provided for use in

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 March 25, 2010                 [Page 2]
Internet-Draft                IPv4 Examples               September 2009

5.  The Status of

   Note that has been used for some examples in the past.
   However, this block did not appear in the list of special prefixes in
   [RFC3330] or its successors, and the block is therefore not reserved
   for any special purpose.  The block can be used for regular address
   assignments with caution.

6.  Security Considerations

   This document has no security implications.

7.  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

8.  References

8.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

8.2.  Informative References

   [RFC1166]  Kirkpatrick, S., Stahl, M., and M. Recker, "Internet
              numbers", RFC 1166, July 1990.

   [RFC1918]  Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
              E. Lear, "Address Allocation for Private Internets",
              BCP 5, RFC 1918, February 1996.

   [RFC2050]  Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and
              BCP 12, RFC 2050, November 1996.

   [RFC2606]  Eastlake, D. and A. Panitz, "Reserved Top Level DNS
              Names", BCP 32, RFC 2606, June 1999.

   [RFC3330]  IANA, "Special-Use IPv4 Addresses", RFC 3330,
              September 2002.

   [RFC3849]  Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix

Arkko, et al.            Expires March 25, 2010                 [Page 3]
Internet-Draft                IPv4 Examples               September 2009

              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 and 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, John Klensin and others for interesting discussions of this

Authors' Addresses

   Jari Arkko
   Jorvas  02420


   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

   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

Arkko, et al.            Expires March 25, 2010                 [Page 4]