[Search] [txt|pdfized|bibtex] [Tracker] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01                                                         
Network Working Group                                        S. Krishnan
Internet-Draft                                                  Ericsson
Intended status: Informational                               G. Tsirtsis
Expires: October 2, 2008                                        Qualcomm
                                                          March 31, 2008


                       MIPv6 Home Link Detection
                       draft-krishnan-mext-hld-01

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 October 2, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2008).

Abstract

   The MIPv6 bootstrapping procedure allows the mobile node to
   dynamically discover its home prefix using an IKEv2 exchange.  Since
   the home prefix is not statically configured on the mobile node,
   there is a need to specify a mechanism for the mobile node to detect
   if it is on its home link.  This document specifies one such
   mechanism.




Krishnan & Tsirtsis      Expires October 2, 2008                [Page 1]


Internet-Draft          MIPv6 Home Link Detection             March 2008


Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Proposed method . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Mobile Node Operation . . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 4
   Intellectual Property and Copyright Statements  . . . . . . . . . . 6







































Krishnan & Tsirtsis      Expires October 2, 2008                [Page 2]


Internet-Draft          MIPv6 Home Link Detection             March 2008


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].


2.  Introduction

   A Mobile IPv6 node requires a Home Agent address, a home address, and
   IPsec security associations with its Home Agent before it can start
   utilizing Mobile IPv6 service.  The base MIPv6 RFC [RFC3775] requires
   that some or all of these are statically configured.  The MIPv6
   bootstrapping work specified in [RFC5026] describes how the MN can
   acquire such information dynamically.


3.  Proposed method

   This document proposes using the information available from Router
   Advertisements on the local link and the configuration information
   acquired using the IKEv2 exchange as specified in [RFC5026] to
   determine whether or not it has attached to its home link.  It uses
   the Prefix Information Option(s) received in the Router
   Advertisements and the MIP6_HOME_PREFIX configuration payload
   received from the HA.  The MN performs this home link detection
   procedure by following the steps described in Section 4.


4.  Mobile Node Operation

   When an MN arrives on a new link it performs the following steps to
   determine if it is on the home link.
   o  The MN sends out a Router Solicitation
   o  The MN receives a Router Advertisement in response with one or
      more Prefix Information Options as specified in [RFC4861].
   o  The MN autoconfigures an address from one of the received prefixes
      that have the autonomous address configuration flag set.  This
      address is referred to as the Current MN Address (CMA)
   o  The MN stores all the prefix(es) received along with their prefix
      lengths in the RA in a conceptual list called the Current Link
      Prefix List (CLPL)
   o  The MN uses the CMA to initiate the bootstrapping procedure
      described in [RFC5026].  The MN MUST include the MIP6_HOME_PREFIX
      attribute in the CFG_REQUEST message.
   o  The MN receives the home prefix and the corresponding prefix
      length from the HA contained in the MIP6_HOME_PREFIX attribute in
      the CFG_REPLY message.  The MN stores it in a conceptual variable



Krishnan & Tsirtsis      Expires October 2, 2008                [Page 3]


Internet-Draft          MIPv6 Home Link Detection             March 2008


      called the HomePrefix.
   o  The MN iterates through the CLPL and compares HomePrefix to each
      of the entries there in turn.
   o  If one (or more) of the entries in the CLPL matches the
      HomePrefix, the MN can determine that it has attached to its home
      link
   o  If none of the entries in the CLPL matches the HomePrefix, the MN
      can determine that it has not attached to its home link


5.  Acknowledgements

   The authors would like to thank Gerardo Giaretta, Hesham Soliman,
   Julien Laganier and Vijay Devarapalli for their contributions to this
   document.


6.  IANA Considerations

   This document does not require any action from the IANA.


7.  Security Considerations

   This document does not create any new security issues other than
   those specified in [RFC3775] and [RFC5026]


8.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3775]  Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
              in IPv6", RFC 3775, June 2004.

   [RFC4861]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
              "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
              September 2007.

   [RFC5026]  Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
              Bootstrapping in Split Scenario", RFC 5026, October 2007.









Krishnan & Tsirtsis      Expires October 2, 2008                [Page 4]


Internet-Draft          MIPv6 Home Link Detection             March 2008


Authors' Addresses

   Suresh Krishnan
   Ericsson
   8400 Decarie Blvd.
   Town of Mount Royal, QC
   Canada

   Phone: +1 514 345 7900 x42871
   Email: suresh.krishnan@ericsson.com


   George Tsirtsis
   Qualcomm

   Email: tsirtsis@googlemail.com



































Krishnan & Tsirtsis      Expires October 2, 2008                [Page 5]


Internet-Draft          MIPv6 Home Link Detection             March 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   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 & Tsirtsis      Expires October 2, 2008                [Page 6]