16ng W. Liang Internet-Draft X. Qin Intended status: Informational Expires: November 16, 2007 Huawei Technologies May 15, 2007 Route Optimization Control by Network draft-qin-16ng-rocontrol-00.txt 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 November 16, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document proposes a method for network to control whether to allow mobile nodes to optimize route. Liang & Qin Expires November 16, 2007 [Page 1] Internet-Draft RO Control May 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Route Optimization Controlled by Network . . . . . . . . . . . 3 2.1. Controlled by Home Network . . . . . . . . . . . . . . . . 3 2.2. Controlled by Access Network . . . . . . . . . . . . . . . 4 3. Message Formats . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Binding Acknowledgement Message . . . . . . . . . . . . . . 4 4. Security Consideration . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Normative Reference . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Liang & Qin Expires November 16, 2007 [Page 2] Internet-Draft RO Control May 2007 1. Introduction According to RFC 3775[RFC3775], mobile nodes can provide current care-of address to correspondent nodes through the correspondent registration. Mobile nodes may use route optimization and send packets with the Home Address destination option. This manner of delivering packets does not require going through the home network, and typically will enable faster and more reliable transmission. However, home network will not be able to transport, control and account mobile nodes' traffic by itself, though access service provider could offer accounting information to home service provider which has accounting agreement with access service provider. This feature restricts service control and account policy which could be exploited by network service provider. This document proposes a method for network to control whether to allow mobile nodes to optimize route. 2. Route Optimization Controlled by Network Either Home network or local access network can gate route optimization procedure. This section introduces both of them. 2.1. Controlled by Home Network Home agent can inform mobile nodes that route optimization feature is not supported and mobile nodes should not initialize Return Route test procedure. As mobile nodes register binding entries with home agent, home agent could identify whether route optimization function is allowed in Bind Acknowledgement message by using a bit, as shown in Section 3. Before correspondent registration, the return routability procedure should be executed to authorize registrations. The return routability procedure is formed by four messages as below: Home Test Init Care-of Test Init Home Test Care-of Test The Home Test Init message is reverse tunneled through the home agent. In order to control route optimization, Home agent may gate return route test procedure. For example, home agent can identify the Home Test Init message, and gate it according to mobile node's Liang & Qin Expires November 16, 2007 [Page 3] Internet-Draft RO Control May 2007 profile which sources from AAA infrastructure. While correspondent nodes do not receive Home Test Init message, return route test procedure could not be finished. Then, mobile nodes always route datagrams through home agent. 2.2. Controlled by Access Network Access network may acquire whether route optimization feature could be supported according to mobile nodes' profile sourced from home AAA infrastructure during access authentication. If mobile node who is assigned care-of address sends datagrams to correspondent nodes' address instead of home agent address, access router may dump these packets. Similarly, access router may dump packets sourced from correspondent nodes. 3. Message Formats 3.1. Binding Acknowledgement Message The Binding Acknowledgement is used to both acknowledge receipt of a Binding Update and inform support of route optimization. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Status |K|O| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | Lifetime | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . . . Mobility options . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Binding Acknowledgement Message Format Route Optimization (O) If this bit is cleared, route optimization is not supported by home agent. Mobile nodes should not initialize return route test procedure after this flag is received. Other bits and options are not changed in this document. Liang & Qin Expires November 16, 2007 [Page 4] Internet-Draft RO Control May 2007 4. Security Consideration The mechanism discussed herein have no significant incremental impact on Internet infrastructure security. 5. IANA Considerations No requirement to IANA. 6. Acknowledgement We would like to thank Xie Yong, Jianjun Wu and Liang Gu for their comments and suggestions on this work. 7. Normative Reference [RFC3775] Johnson, "RFC 3775", June 2004. Authors' Addresses Wenliang Huawei Technologies Email: van.liang@huawei.com Xia Huawei Technologies Email: Alice.Q@huawei.com Liang & Qin Expires November 16, 2007 [Page 5] Internet-Draft RO Control May 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). Liang & Qin Expires November 16, 2007 [Page 6]