Network Working Group M. Cotton Internet-Draft L. Vegoda Obsoletes: 5156, 5735 Internet Corporation for (if approved) Assigned Names and Numbers Updates: 4773,5736 (if approved) R. Bonica, Ed. Intended status: BCP Juniper Networks Expires: April 18, 2013 B. Haberman Johns Hopkins University Applied Physics Lab October 15, 2012 Special-Purpose Address Registries draft-bonica-special-purpose-03 Abstract This memo instructs IANA to restructure its IPv4 and IPv6 Special- Purpose Address Registries. Upon restructuring, the aforementioned registries will record all special-purpose address blocks, maintaining a common set of information regarding each address block. This memo updates RFC 5736 and RFC 4773, which define the current structure of the IPv4 and IPv6 Special-Purpose Address Registries. It also obsoletes RFC 5735 and RFC 5156 which document special- purpose address blocks that are not currently, but will in the future, be recorded in the IPv4 and IPv6 Special-Purpose Address Registries. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on April 18, 2013. Copyright Notice Cotton, et al. Expires April 18, 2013 [Page 1]
Internet-Draft Special-Purpose Address Registries October 2012 Copyright (c) 2012 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 (http://trustee.ietf.org/license-info) 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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 2.1. Information Requirements . . . . . . . . . . . . . . . . . 4 2.2. IPv4 Special-Purpose Address Registry Entries . . . . . . 5 2.3. IPv6 Special-Purpose Address Registry Entries . . . . . . 11 3. Security Considerations . . . . . . . . . . . . . . . . . . . 16 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 5. Informative References . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Cotton, et al. Expires April 18, 2013 [Page 2]
Internet-Draft Special-Purpose Address Registries October 2012 1. Introduction In order to support new protocols and practices, the IETF occasionally reserves an address block a for special purpose. For example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to represent the local (i.e., "this") network. Likewise, [RFC4291] reserves an IPv6 address block (fe80::/10) to represent link-scoped unicast addresses. Periodically, the IETF publishes an RFC that catalogs special-purpose address blocks. Currently, [RFC5735] catalogs all IPv4 special- purpose address blocks and [RFC5156] catalogs all IPv6 special- purpose address blocks. [RFC5736] assigns an IPv4 address block (192.0.0.0/24) to IANA and instructs IANA to allocate special-purpose address blocks from this space. [RFC5736] also instructs IANA to create an IPv4 Special- Purpose Address Registry that records allocations from this address space. However, [RFC5736] does not instruct IANA to record special- purpose address block reservations from outside of the aforementioned space in the IPv4 Special-Purpose Address Registry. Likewise, [RFC2928] assigns an IPv6 address block (2001:0000::/23) to IANA and instructs IANA to allocate special-purpose address blocks from this space. [RFC4773] instructs IANA to create an IPv6 Special- Purpose Address Registry that records allocations from this address space. However, [RFC4773] does not instruct IANA to record special- purpose address block reservations from outside of the aforementioned space in the IPv6 Special-Purpose Address Registry. This memo instructs IANA to restructure its IPv4 and IPv6 Special- Purpose Address Registries. Therefore, this document updates [RFC5736] and [RFC4773] which define the current structure of the aforementioned registries. Specifically, this memo instructs IANA to record all special-purpose address blocks in the aforementioned registries. These include, but are not limited to, IPv4 allocations from 192.0.0.0/24 and IPv6 allocations from 2001:0000::/23. When the aforementioned registries include all special-purpose address blocks, [RFC5735] and [RFC5156] will become redundant with the registries. Therefore, this memo obsoletes [RFC5735] and [RFC5156]. Furthermore, this memo defines: o a common set of information that the registries will maintain regarding each special-purpose address block Cotton, et al. Expires April 18, 2013 [Page 3]
Internet-Draft Special-Purpose Address Registries October 2012 o a common set of requirements for future entries 2. IANA Considerations IANA will restructure the following registries: o IPv4 Special-Purpose Address Registry o IPv6 Special-Purpose Address Registry The IPv4 Special-Purpose Address Registry will record all IPv4 special-purpose address blocks. These reservations will include, but not be limited to, allocations from the 192.0.0.0/24 address block. Likewise, the IPv6 Special-Purpose Address Registry will record all IPv6 special-purpose address blocks. These reservations will include, but not be limited to, allocations from the 2001:0000::/23 address block. Section 2.1 of this document describes information that both registries will maintain for each entry. Initially, IANA will populate the IPv4 Special-Purpose Address Registry with information taken from Section 2.2 of this document. Likewise, IANA will populate the IPv6 Special-Purpose Address Registry with information taken from Section 2.3 of this document. IANA will update the aforementioned registries as requested in the "IANA Considerations" section of an IESG-reviewed document. The " IANA Considerations" section must include all of the information specified in Section 2.1 of this document. 2.1. Information Requirements The IPv4 and IPv6 Special-Purpose Address Registries will maintain the following information regarding each entry: o Prefix - An IPv4 or IPv6 prefix that identifies the special- purpose address block o Name - A descriptive name for the special-purpose address block o RFC - The RFC though which the special-purpose address block was requested o Allocation Date - The date upon which the special purpose address block was allocated Cotton, et al. Expires April 18, 2013 [Page 4]
Internet-Draft Special-Purpose Address Registries October 2012 o Termination Date - The date upon which the allocation is to be terminated. This field is applicable for limited-use allocations only. o Source - A boolean value indicated whether an address from the allocated special-purpose address block is valid when used as the source address of an IP datagram that transits two devices o Destination - A boolean value indicated whether an address from the allocated special-purpose address block is valid when used as the destination address of an IP datagram that transits two devices o Routable - A boolean value indicating whether a IP datagram whose destination address is drawn from the allocated special-purpose address block is routable (i.e., may traverse more than a single IP interface) o Global - A boolean value indicating whether a IP datagram whose destination address is drawn from the allocated special-purpose address block is routable beyond a specified administrative domain. If the value of "Destination" is FALSE, the values of "Routable" and "Global" must also be false. 2.2. IPv4 Special-Purpose Address Registry Entries Table 1 though Table 16, below, represent entries with which the IANA will initially populate the IPv4 Special-Purpose Address Registry. +------------------+---------------------------+ | Attribute | Value | +------------------+---------------------------+ | Prefix | 0.0.0.0/8 | | Name | "This" Network | | RFC | [RFC1122] Section 3.2.1.3 | | Allocation Date | September, 1981 | | Termination Date | N/A | | Source | True | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------------+ Table 1: "This" Network Cotton, et al. Expires April 18, 2013 [Page 5]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+---------------+ | Attribute | Value | +------------------+---------------+ | Prefix | 10.0.0.0/8 | | Name | Private-Use | | RFC | [RFC1918] | | Allocation Date | February 1996 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+---------------+ Table 2: Private-Use Networks +------------------+----------------------+ | Attribute | Value | +------------------+----------------------+ | Prefix | 100.64.0.0/10 | | Name | Shared Address Space | | RFC | [RFC6598] | | Allocation Date | April 2012 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+----------------------+ Table 3: Shared Address Space +------------------+---------------------------+ | Attribute | Value | +------------------+---------------------------+ | Prefix | 127.0.0.0/8 | | Name | Loopback | | RFC | [RFC1122] Section 3.2.1.3 | | Allocation Date | September 1981 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------------+ Table 4: Loopback Cotton, et al. Expires April 18, 2013 [Page 6]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+----------------+ | Attribute | Value | +------------------+----------------+ | Prefix | 169.254.0.0/16 | | Name | Link Local | | RFC | [RFC3927] | | Allocation Date | May 2005 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | False | | Global | False | +------------------+----------------+ Table 5: Link Local +------------------+---------------+ | Attribute | Value | +------------------+---------------+ | Prefix | 172.16.0.0/12 | | Name | Private-Use | | RFC | [RFC1122] | | Allocation Date | February 1996 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+---------------+ Table 6: Private-Use Networks +------------------+---------------------------+ | Attribute | Value | +------------------+---------------------------+ | Prefix | 192.0.0.0/24 [1] | | Name | IETF Protocol Assignments | | RFC | [RFC5736] | | Allocation Date | January 2010 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------------+ Table 7: IETF Protocol Assignments Cotton, et al. Expires April 18, 2013 [Page 7]
Internet-Draft Special-Purpose Address Registries October 2012 [1] Not useable unless by virtue of a more specific reservation. +------------------+--------------+ | Attribute | Value | +------------------+--------------+ | Prefix | 192.0.0.0/29 | | Name | DS-Lite | | RFC | [RFC6333] | | Allocation Date | June 2011 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+--------------+ Table 8: DS-Lite +------------------+----------------------------+ | Attribute | Value | +------------------+----------------------------+ | Prefix | 192.0.2.0/24 | | Name | Documentation (TEST-NET-1) | | RFC | [RFC5737] | | Allocation Date | January 2010 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+----------------------------+ Table 9: TEST-NET-1 Cotton, et al. Expires April 18, 2013 [Page 8]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+--------------------+ | Attribute | Value | +------------------+--------------------+ | Prefix | 192.88.99.0/24 | | Name | 6to4 Relay Anycast | | RFC | [RFC3068] | | Allocation Date | June 2001 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | True | +------------------+--------------------+ Table 10: 6to4 Relay Anycast +------------------+----------------+ | Attribute | Value | +------------------+----------------+ | Prefix | 192.168.0.0/16 | | Name | Private-Use | | RFC | [RFC1918] | | Allocation Date | February 196 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | Flase | +------------------+----------------+ Table 11: Private-Use Networks +------------------+---------------+ | Attribute | Value | +------------------+---------------+ | Prefix | 198.18.0.0/15 | | Name | Benchmarking | | RFC | [RFC2544] | | Allocation Date | March 1999 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+---------------+ Table 12: Network Interconnect Device Benchmark Testing Cotton, et al. Expires April 18, 2013 [Page 9]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+----------------------------+ | Attribute | Value | +------------------+----------------------------+ | Prefix | 198.51.100.0/24 | | Name | Documentation (TEST-NET-2) | | RFC | [RFC5737] | | Allocation Date | January 2010 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+----------------------------+ Table 13: TEST-NET-2 +------------------+----------------------------+ | Attribute | Value | +------------------+----------------------------+ | Prefix | 203.0.113.0/24 | | Name | Documentation (TEST-NET-3) | | RFC | [RFC5737] | | Allocation Date | January 2010 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+----------------------------+ Table 14: TEST-NET-3 +------------------+---------------------+ | Attribute | Value | +------------------+---------------------+ | Prefix | 240.0.0.0/4 | | Name | Reserved | | RFC | [RFC1112] Section 4 | | Allocation Date | August 1989 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------+ Table 15: Reserved for Future Use Cotton, et al. Expires April 18, 2013 [Page 10]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+---------------------+ | Attribute | Value | +------------------+---------------------+ | Prefix | 255.255.255.255/32 | | Name | Limited Broadcast | | RFC | [RFC0919] Section 7 | | Allocation Date | October 1984 | | Termination Date | N/A | | Source | False | | Destination | True | | Routable | False | | Global | False | +------------------+---------------------+ Table 16: Limited Broadcast 2.3. IPv6 Special-Purpose Address Registry Entries Table 17 through Table 28, below, represent entries with which the IANA will initially populate the IPv6 Special-Purpose Address Registry. +------------------+------------------+ | Attribute | Value | +------------------+------------------+ | Prefix | ::1/128 | | Name | Loopback Address | | RFC | [RFC4291] | | Allocation Date | February 2006 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+------------------+ Table 17: Loopback Address Cotton, et al. Expires April 18, 2013 [Page 11]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+---------------------+ | Attribute | Value | +------------------+---------------------+ | Prefix | ::/128 | | Name | Unspecified Address | | RFC | [RFC4291] | | Allocation Date | February 2006 | | Termination Date | N/A | | Source | True | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------+ Table 18: Unspecified Address +------------------+---------------------+ | Attribute | Value | +------------------+---------------------+ | Prefix | ::FFFF:0:0/96 | | Name | IPv4-mapped Address | | RFC | [RFC4291] | | Allocation Date | February 2006 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+---------------------+ Table 19: IPv4-mapped Address +------------------+---------------------+ | Attribute | Value | +------------------+---------------------+ | Prefix | 0100::/64 | | Name | Discard-Only Prefix | | RFC | [RFC6666] | | Allocation Date | June 2012 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+---------------------+ Table 20: Discard-Only Prefix Cotton, et al. Expires April 18, 2013 [Page 12]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+---------------------------+ | Attribute | Value | +------------------+---------------------------+ | Prefix | 2001:0000::/23 | | Name | IETF Protocol Assignments | | RFC | [RFC2928] | | Allocation Date | September 2000 | | Termination Date | N/A | | Source | False[2] | | Destination | False[2] | | Routable | False[2] | | Global | False[2] | +------------------+---------------------------+ Table 21: IETF Protocol Assignments [2] Unless allowed by a more specific allocation +------------------+----------------+ | Attribute | Value | +------------------+----------------+ | Prefix | 2001:0000::/32 | | Name | TEREDO | | RFC | [RFC4380] | | Allocation Date | January 2006 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+----------------+ Table 22: TEREDO Cotton, et al. Expires April 18, 2013 [Page 13]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+----------------+ | Attribute | Value | +------------------+----------------+ | Prefix | 2001:0002::/48 | | Name | Benchmarking | | RFC | [RFC5180] | | Allocation Date | April 2008 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+----------------+ Table 23: Benchmarking +------------------+---------------+ | Attribute | Value | +------------------+---------------+ | Prefix | 2001:db8::/32 | | Name | Documentation | | RFC | [RFC3849] | | Allocation Date | July 2004 | | Termination Date | N/A | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+---------------+ Table 24: Documentation +------------------+--------------+ | Attribute | Value | +------------------+--------------+ | Prefix | 2001:10::/28 | | Name | ORCHID | | RFC | [RFC4843] | | Allocation Date | March 2007 | | Termination Date | March 2014 | | Source | False | | Destination | False | | Routable | False | | Global | False | +------------------+--------------+ Table 25: ORCHID Cotton, et al. Expires April 18, 2013 [Page 14]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+---------------+ | Attribute | Value | +------------------+---------------+ | Prefix | 2002::/16 [3] | | Name | 6to4 | | RFC | [RFC3056] | | Allocation Date | February 2001 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | N/A[4] | +------------------+---------------+ Table 26: 6to4 [3] See [RFC3056] for details. +------------------+--------------+ | Attribute | Value | +------------------+--------------+ | Prefix | FC00::/7 | | Name | Unique-Local | | RFC | [RFC4193] | | Allocation Date | October 2005 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | True | | Global | False | +------------------+--------------+ Table 27: Unique-Local Cotton, et al. Expires April 18, 2013 [Page 15]
Internet-Draft Special-Purpose Address Registries October 2012 +------------------+-----------------------+ | Attribute | Value | +------------------+-----------------------+ | Prefix | FE80::/10 | | Name | Linked-Scoped Unicast | | RFC | [RFC4291] | | Allocation Date | February 2006 | | Termination Date | N/A | | Source | True | | Destination | True | | Routable | False | | Global | False | +------------------+-----------------------+ Table 28: Linked-Scoped Unicast 3. Security Considerations Security of the Internet's routing system relies on the ability to authenticate an assertion of unique control of an address block. Measures to authenticate such assertions rely on validation that the address block forms part of an existing allocated address block, and that there is a trustable and unique reference in the IANA address registries. The proposed registry is intended to provide an authoritative source of information regarding the currency and intended purpose of special purpose address blocks that are designated from the IANA-administered Special Purpose registry. This is a small step towards the creation of a comprehensive registry framework that can be used as a trust point for commencing a chain of address validation. Consideration should be given to IANA registry publication formats that are machine parseable, and also the use of file signatures and associated certificate mechanisms to allow applications to confirm that the registry contents are current, and that they have been published by the IANA. 4. Acknowledgements The authors would like to acknowledge an anonymous donor, without whom this document would not have been written. 5. Informative References [RFC0919] Mogul, J., "Broadcasting Internet Datagrams", STD 5, Cotton, et al. Expires April 18, 2013 [Page 16]
Internet-Draft Special-Purpose Address Registries October 2012 RFC 919, October 1984. [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, August 1989. [RFC1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989. [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996. [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, March 1999. [RFC2928] Hinden, R., Deering, S., Fink, R., and T. Hain, "Initial IPv6 Sub-TLA ID Assignments", RFC 2928, September 2000. [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC 3056, February 2001. [RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay Routers", RFC 3068, June 2001. [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849, July 2004. [RFC3927] Cheshire, S., Aboba, B., and E. Guttman, "Dynamic Configuration of IPv4 Link-Local Addresses", RFC 3927, May 2005. [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, March 2005. [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast Addresses", RFC 4193, October 2005. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380, February 2006. [RFC4773] Huston, G., "Administration of the IANA Special Purpose IPv6 Address Block", RFC 4773, December 2006. Cotton, et al. Expires April 18, 2013 [Page 17]
Internet-Draft Special-Purpose Address Registries October 2012 [RFC4843] Nikander, P., Laganier, J., and F. Dupont, "An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)", RFC 4843, April 2007. [RFC5156] Blanchet, M., "Special-Use IPv6 Addresses", RFC 5156, April 2008. [RFC5180] Popoviciu, C., Hamza, A., Van de Velde, G., and D. Dugatkin, "IPv6 Benchmarking Methodology for Network Interconnect Devices", RFC 5180, May 2008. [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", BCP 153, RFC 5735, January 2010. [RFC5736] Huston, G., Cotton, M., and L. Vegoda, "IANA IPv4 Special Purpose Address Registry", RFC 5736, January 2010. [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks Reserved for Documentation", RFC 5737, January 2010. [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion", RFC 6333, August 2011. [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address Space", BCP 153, RFC 6598, April 2012. [RFC6666] Hilliard, N. and D. Freedman, "A Discard Prefix for IPv6", RFC 6666, August 2012. Authors' Addresses Michelle Cotton Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 USA Phone: +310-823-9358 Fax: Email: michelle.cotton@icann.org URI: http://www.icann.org/ Cotton, et al. Expires April 18, 2013 [Page 18]
Internet-Draft Special-Purpose Address Registries October 2012 Leo Vegoda Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 LosAngeles, CA 90094-2536 USA Phone: +310-823-9358 Fax: Email: leo.vegoda@icann.org URI: http://www.icann.org/ Ronald P Bonica (editor) Juniper Networks 2251 Corporate Park Drive Herndon, Virginia 20171 USA Email: rbonica@juniper.net Brian Haberman Johns Hopkins University Applied Physics Lab 11100 Johns Hopkins Road Laurel, Maryland 20723-6099 USA Email: brian@innovationslab.net Cotton, et al. Expires April 18, 2013 [Page 19]
