Network Working Group S. Krishnan Internet-Draft Ericsson Intended status: Standards Track June 7, 2007 Expires: December 9, 2007 Client Initiated Selection of Proxy Mobility draft-krishnan-netlmm-pmip-sel-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 December 9, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Krishnan Expires December 9, 2007 [Page 1] Internet-Draft pmipsel June 2007 Abstract Proxy MobileIPv6 describes a protocol solution for network based mobility management that relies on Mobile IPv6 signaling and reuse of home agent functionality. This document describes a mechanism by which a mobile node in a PMIPv6 network can signal to the network whether it would like to make use of the Proxy Mobility service. Table of Contents 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Changes to Router Solicitation Message Format . . . . . . . . 6 5. Backward Compatibility . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 Intellectual Property and Copyright Statements . . . . . . . . . . 11 Krishnan Expires December 9, 2007 [Page 2] Internet-Draft pmipsel June 2007 1. Requirements notation 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]. Krishnan Expires December 9, 2007 [Page 3] Internet-Draft pmipsel June 2007 2. Introduction Proxy MobileIPv6 [PMIPv6] describes a protocol solution for network based mobility management that relies on Mobile IPv6 signaling and reuse of home agent functionality. A proxy mobility agent in the network which manages the mobility for a mobile node is the reason for referring to this protocol as Proxy Mobile IPv6. This protocol is targeted mainly towards mobile nodes that are incapable or unwilling to do their own mobility signaling. If a mobile node that wishes to do its own mobility signaling enters a PMIPv6 network it cannot do so since the PMIP domain makes the MN believe that it is in fact in its home network. This document describes a mechanism by which a mobile node in a PMIPv6 network can signal to the PMIPv6 network whether it would like to make use of the Proxy Mobility service or not. Krishnan Expires December 9, 2007 [Page 4] Internet-Draft pmipsel June 2007 3. Mechanism According to [PMIPv6] the mobile node uses the Router Advertisements from the Access Router (which is the proxy mobility agent) to autoconfigure its address on the new link. The PMA receives a Router Solicitation from the MN and responds with a Router Advertisement containing the MN's home prefix. The proposed mechanism uses this Router Solicitation to signal to the PMA as to whether it requests the Proxy Mobility Service or not. For this purpose, this document creates a new flag bit in the IPv6 Router Solicitation called the C bit. A mobile node that utilises this mechanism and wants to perform its own signaling, MUST set the C bit to one. The PMA that receives it SHOULD respond with a Router Advertisement containing a topologically correct prefix for the link (i.e. Not the home prefix). Krishnan Expires December 9, 2007 [Page 5] Internet-Draft pmipsel June 2007 4. Changes to Router Solicitation Message Format This document modifies the format of the Router Solicitation Message specified in [RFC2461] to look like the following 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |C| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options ... +-+-+-+-+-+-+-+-+-+-+-+- ICMP Fields: Type 133 Code 0 Checksum The ICMP checksum. See [ICMPv6]. C If this bit is set, it means that the sending MN would like to perform its own signaling. Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver. Figure 1: Router Solicitation Format Krishnan Expires December 9, 2007 [Page 6] Internet-Draft pmipsel June 2007 5. Backward Compatibility MNs which are not aware of this specification will not set the C bit and hence the PMA would provide them with proxy mobility service. PMAs not aware of this bit when a client sets the C bit to 1 will ignore it as specified in [RFC2461] Krishnan Expires December 9, 2007 [Page 7] Internet-Draft pmipsel June 2007 6. Security Considerations The mechanism described in this document signals to the network infrastructure that the sending MN is capable of doing its own mobility signaling and does not wish to avail of the proxy mobility service. If a node is incapable of doing so, an on-link attacker can send a spoofed router solicitation and deny proxy mobility service to the node. The usage of SEND [RFC3971] would prevent this from happening. Krishnan Expires December 9, 2007 [Page 8] Internet-Draft pmipsel June 2007 7. Normative References [PMIPv6] Gundavelli, S., "Proxy Mobile IPv6", draft-sgundave-mip6-proxymip6-02 (work in progress), March 2007. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998. [RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March 2005. Krishnan Expires December 9, 2007 [Page 9] Internet-Draft pmipsel June 2007 Author's Address Suresh Krishnan Ericsson 8400 Decarie Blvd. Town of Mount Royal, QC Canada Phone: +1 514 345 7900 x42871 Email: suresh.krishnan@ericsson.com Krishnan Expires December 9, 2007 [Page 10] Internet-Draft pmipsel June 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). Krishnan Expires December 9, 2007 [Page 11]