Internet A. Reitzel Internet-Draft Verizon Business Updates: 791 (if approved) August 29, 2007 Intended status: Standards Track Expires: March 1, 2008 Deprecation of Source Routing Options in IPv4 draft-reitzel-ipv4-source-routing-is-evil-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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 March 1, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract [RFC0791] defines two IPv4 options called "Strict Source Routing" and "Loose Source Routing". Functionality provided by these options can be exploited in order to perform remote network discovery, to bypass firewalls and to achieve packet amplification for the purposes of generating denial-of-service traffic. This document updates RFC 791 to deprecate the use of the IPv4 Strict Source Routing Option as well as the IPv4 Loose Source Routing Option. Reitzel Expires March 1, 2008 [Page 1] Internet-Draft Deprecate Source Routing August 2007 Table of Contents 1. Conventions Used In This Document . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Implementation . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 7. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 8.1. Normative References . . . . . . . . . . . . . . . . . . . 4 8.2. Informative References . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Reitzel Expires March 1, 2008 [Page 2] Internet-Draft Deprecate Source Routing August 2007 1. Conventions Used In This Document 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 [RFC2119]. 2. Introduction [RFC0791] defines two IPv4 options called "Strict Source Routing" and "Loose Source Routing". Functionality provided by these options can be exploited in order to perform remote network discovery, to bypass firewalls and to achieve packet amplification for the purposes of generating denial-of-service traffic. This document updates RFC 791 to deprecate the use of the IPv4 Strict Source Routing Option as well as the IPv4 Loose Source Routing Option. 3. Implementation Compliant IPv4 hosts and routers MUST NOT transmit IPv4 datagrams containing either the Strict Source Routing Option or the Loose Source Routing Option. 4. Operations Compliant IPv4 hosts and routers that receive IPv4 datagrams containing either the Strict Source Routing or Loose Source Routing Options MUST silently discard those datagrams without further processing. 5. Security Considerations The purpose of this document is to deprecate an IPv4 feature which has been shown to have serious security implications. These security implications have been well understood in the operator community for many years. For this reason, Internet Service Providers typically block all incoming IPv4 datagrams that include either the Strict Source Routing or Loose Source Routing Options. Recently, researchers [BiondiEbalard] have demonstrated security vulnerabilites associated with the IPv6 Route Header Type 0 Extension. Because of its similar function, vulnerabilities associated with the IPv6 Route Header Type 0 Extension can be generalized to affect the above mentioned IPv4 options. Reitzel Expires March 1, 2008 [Page 3] Internet-Draft Deprecate Source Routing August 2007 6. IANA Considerations This document requests that IANA update the description of IPv4 Strict Source Routing and Loose Source Routing Options to indicate that the use of these options is deprecated. 7. Acknowlegements This document follows in the spirit of [I-D.jabley-ipv6-rh0-is-evil], which proposes the deprecation of the IPv6 Route Header Type 0 Extension. A description of security vulnerabilities associated with the the IPv6 Route Header Type 0 Extension was presented by Philippe Biondi and Arnaud Ebalard at the CanSecWest conference in Vancouver, 2007 [BiondiEbalard]. 8. References 8.1. Normative References [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 8.2. Informative References [BiondiEbalard] Biondi, P. and A. Ebalard, "IPv6 Routing Header Security", April 2007, . [I-D.jabley-ipv6-rh0-is-evil] Abley, J., "Deprecation of Type 0 Routing Headers in IPv6", draft-jabley-ipv6-rh0-is-evil-00 (work in progress), May 2007. Reitzel Expires March 1, 2008 [Page 4] Internet-Draft Deprecate Source Routing August 2007 Author's Address Andrea M. Reitzel Verizon Business 22001 Loudoun County Pkwy Ashburn, VA 20147 US Email: andrea.reitzel@verizonbusiness.com Reitzel Expires March 1, 2008 [Page 5] Internet-Draft Deprecate Source Routing August 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Reitzel Expires March 1, 2008 [Page 6]