mipv6 R. Jaksa Internet-Draft S. Dawkins Expires: April 19, 2006 C. Williams Futurewei October 16, 2005 Discussion on Requesting a mobile nodes binding information from a Home Agent draft-jaksa-mn-busolict-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 April 19, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This draft documents an idea whereby a Mobile IPv6 node may request binding information from its respective Home Agent about other Mobile IPv6 nodes all using the same home agent. Jaksa, et al. Expires April 19, 2006 [Page 1] Internet-Draft Requesting MN binding from a home agent October 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Usage Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Normative references . . . . . . . . . . . . . . . . . . . 4 5.2. Informative References . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Jaksa, et al. Expires April 19, 2006 [Page 2] Internet-Draft Requesting MN binding from a home agent October 2005 1. Introduction The tunneling of packets between the correspondent node and the mobile node via the home agent is known as bidirectional tunneling. Bidirectional tunneling ensures that the mobile node is always reachable when it is away from home, even if the correspondent node is not Mobile IPv6-capable. The sending of packets directly between a mobile node and a Mobile IPv6-capable correspondent node is known as route optimization. [1] There may be usage scenarios whereby a correspondent node may wish to maintain the binding information for other Mobile IPv6 nodes without first exchanging data packets or requiring a mobile node to send binding updates to the correspondent node. This draft documents a proposal whereby a correspondent node may query a home agent for binding information about another mobile node. In particular this draft seeks to document a couple of usage cases. It is assumed throughout this draft that the requesting correspondent node is also a Mobile IPv6 supported node that is requesting binding information from its respective Home Agent about another Mobile IPv6 node that is also being serviced by the same Home Agent. 2. Terminology See [2] for mobility terminology used in this document. 3. Usage Cases Mobile IPv6 [1] defines a process during which a mobile node sends a Binding Update to its home agent or a correspondent node, causing a binding for the mobile node to be registered. Usage scenarios exist whereby a correspondent node may wish to request the mobile node's binding from it's home agent. Mobile based applications or services may need to know if another mobile node is connected or active. For example, the absence of a binding association for a homeless mobile node may mean that the node is not active or connected. Perhaps the mobile node is in nomadic mode and is currently inactive. A correspondent node can make a request to the home agent for the binding information. Applications may then use the binding cache to obtain information about on-line or active status for the respective mobile node. Examples may include end-to-end gaming applications that may need to know if nodes within some predefined communication group are active (i.e., on-line). Here the Home agent is providing information to a node about the current reachability status of another node. Jaksa, et al. Expires April 19, 2006 [Page 3] Internet-Draft Requesting MN binding from a home agent October 2005 Location based service support for mobile nodes is another usage case. For example, a server may wish to periodically track the movement and/or location of mobile nodes that are subscribing to its services even though there is not an active on-going session. The correspondent node providing the services may periodically check the location of the mobile node by requesting its binding information from the home agent. Services may then retrieve the binding cache and push location-based information to the mobile node. 4. Security Considerations It is assumed throughout this draft that the requesting correspondent node is also a Mobile IPv6 supported node that is requesting binding information from its respective Home Agent about another Mobile IPv6 node that is also being serviced by the same Home Agent. As such there is already a security association between the nodes requesting binding information and the home agent. Instead of sending a binding update to the home agent, a request for another mobile nodes binding information is being made. What needs to be fretted out is a way to keep private home agent binding cache entries for mobile nodes that don't want to disclose this information. 5. References 5.1. Normative references [1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. [2] Manner, J. and M. Kojo, "Mobility Related Terminology", RFC 3753, June 2004. 5.2. Informative References Jaksa, et al. Expires April 19, 2006 [Page 4] Internet-Draft Requesting MN binding from a home agent October 2005 Authors' Addresses Robert Jaksa Futurewei 1700 Alma Dr., Suite 102 Plano, Tx 75075 USA Phone: 1 972 509 5599 Email: rjaksa@futurewei.com Spencer Dawkins Futurewei 1700 Alma Dr., Suite 102 Plano, Tx 75075 USA Phone: 1 972 509 5599 Email: sdawkins@futurewei.com Carl Williams Futurewei Consultant, Palo Alto, CA 94306 USA Phone: +1.650.279.5903 Email: carlw@mcsr-labs.org Jaksa, et al. Expires April 19, 2006 [Page 5] Internet-Draft Requesting MN binding from a home agent October 2005 Intellectual Property Statement 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. Disclaimer of Validity 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 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. Copyright Statement Copyright (C) The Internet Society (2005). 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Jaksa, et al. Expires April 19, 2006 [Page 6]