< draft-iana-ipv4-examples-01.txt		draft-iana-ipv4-examples-02.txt >
	Network Working Group J. Arkko		Network Working Group J. Arkko
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Updates: 1166 (if approved) M. Cotton		Updates: 1166 (if approved) M. Cotton
	Intended status: Informational L. Vegoda		Intended status: Informational L. Vegoda
	Expires: December 27, 2009 ICANN		Expires: March 25, 2010 ICANN
	June 25, 2009		September 21, 2009
	IPv4 Address Blocks Reserved for Documentation		IPv4 Address Blocks Reserved for Documentation
	draft-iana-ipv4-examples-01		draft-iana-ipv4-examples-02
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on December 27, 2009.		This Internet-Draft will expire on March 25, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 17 ¶		skipping to change at page 2, line 17 ¶
	1. Introduction		1. Introduction
	This document describes three IPv4 address blocks that are provided		This document describes three IPv4 address blocks that are provided
	for use in documentation. The use of designated address ranges for		for use in documentation. The use of designated address ranges for
	documentation and examples reduces the likelihood of conflicts and		documentation and examples reduces the likelihood of conflicts and
	confusion arising from the use of addresses assigned for some other		confusion arising from the use of addresses assigned for some other
	purpose.		purpose.
	[RFC1166] reserves the first of the three address blocks,		[RFC1166] reserves the first of the three address blocks,
	192.0.2.0/24. The other two address blocks have recently been		192.0.2.0/24. The other two address blocks have recently been
	allocated for this purpose, to ease the writing of examples involving		allocated for this purpose, primarily to ease the writing of examples
	addresses from multiple networks.		involving addresses from multiple networks.
	Other documentation ranges have been defined in the IETF, including		Other documentation ranges have been defined in the IETF, including
	the IPv6 documentation prefix [RFC3849] and example domain names		the IPv6 documentation prefix [RFC3849] and example domain names
	[RFC2606]. Documentation also makes use of the ranges reserved in		[RFC2606]. Documentation also makes use of the ranges reserved in
	[RFC1918].		[RFC1918].
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	skipping to change at page 3, line 5 ¶		skipping to change at page 3, line 5 ¶
	Addresses within the TEST-NET-1, TEST-NET-2, and TEST-NET-3 blocks		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		SHOULD NOT appear on the public Internet and are used without any
	coordination with IANA or an Internet registry [RFC2050]. Network		coordination with IANA or an Internet registry [RFC2050]. Network
	operators SHOULD add these address blocks to the list of non-		operators SHOULD add these address blocks to the list of non-
	routeable address space, and if packet filters are deployed, then		routeable address space, and if packet filters are deployed, then
	this address block SHOULD be added to packet filters.		this address block SHOULD be added to packet filters.
	These blocks are not for local use, and the filters may be used in		These blocks are not for local use, and the filters may be used in
	both local and public contexts.		both local and public contexts.
	5. Security Considerations		5. The Status of 128.66.0.0/16
			Note that 128.66.0.0/16 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.		This document has no security implications.
	6. IANA Considerations		7. IANA Considerations
	IANA should record the allocation of the three address blocks in the		IANA should record the allocation of the three address blocks in the
	IPv4 address registry. No end party is to be assigned these		IPv4 address registry. No end party is to be assigned these
	addresses.		addresses.
	7. References		8. References
	7.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	7.2. Informative References		8.2. Informative References
	[RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet		[RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet
	numbers", RFC 1166, July 1990.		numbers", RFC 1166, July 1990.
	[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and		[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
	E. Lear, "Address Allocation for Private Internets",		E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, February 1996.		BCP 5, RFC 1918, February 1996.
	[RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and		[RFC2050] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D., and
	J. Postel, "INTERNET REGISTRY IP ALLOCATION GUIDELINES",		J. Postel, "INTERNET REGISTRY IP ALLOCATION GUIDELINES",
	BCP 12, RFC 2050, November 1996.		BCP 12, RFC 2050, November 1996.
	[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS		[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS
	Names", BCP 32, RFC 2606, June 1999.		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		[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
	Reserved for Documentation", RFC 3849, July 2004.		Reserved for Documentation", RFC 3849, July 2004.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
	The authors would like to offer a special note of thanks to APNIC,		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.		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		The authors would also like to acknowledge that this document
	inherits material from [RFC3849].		inherits material from [RFC3849].
End of changes. 10 change blocks.
	11 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/