PPSP Working Group Ningxia. Zhao Internet-Draft Mo. Sun Intended status: Informational Jun. Shen Expires: January 5, 2012 ZTE Corporation July 4, 2011 LISP Mobile Node extension draft-zhao-lisp-mn-extension-00 Abstract The lisp-MN describes how a lightweight version of LISP's ITR/ETR functionality can be used to provide seamless mobility to a mobile node. The LISP Mobile Node design described in this document uses standard LISP functionality to provide scalable mobility for LISP mobile nodes. This document extends the lisp-MN, introduces some contents that lisp-MN does not include but the author feels need to add them. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on January 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect Zhao, et al. Expires January 5, 2012 [Page 1] Internet-Draft LISP Mobile Node extension July 2011 to this document. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. LISP-MN Extension Operation . . . . . . . . . . . . . . . . . 5 3.1. EID-to-RLOC Mapping Update Operation . . . . . . . . . . . 5 3.2. Map-Unregister Operation . . . . . . . . . . . . . . . . . 5 4. LISP-MN Extension Message . . . . . . . . . . . . . . . . . . 6 4.1. LISP Packet Type Allocations . . . . . . . . . . . . . . . 6 4.2. Map-Update Message Format . . . . . . . . . . . . . . . . 6 4.3. Map-Unregister Message Format . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Zhao, et al. Expires January 5, 2012 [Page 2] Internet-Draft LISP Mobile Node extension July 2011 1. Introduction The lisp-MN specifies the behavior of a new LISP network element: the LISP Mobile Node. It has introduced some aspects of lisp-MN, but there are areas have not covered: o When the lisp-MN moves in Communication process , the lisp-MN registers its EID / RLOC in Map-Server, and the correspond must query the Map-Server to obtain the change and the of the EID and RLOC mapping and update the cache of the EID and RLOC mapping. o The deregister have not be considered. Design goals for the LISP-MN extension design include: o Allowing TCP connections to stay alive while roaming. o Allowing the mobile node to communicate with other mobile nodes while either or both are roaming. o Allowing the mobile node to multi-home (i.e., use multiple interfaces concurrently). o Allowing the mobile node to be a server. o Providing shortest path bidirectional data paths between a mobile node and any other stationary or mobile node. o Not requiring fine-grained routes in the core network to support mobility. o Not requiring a home-agent, foreign agent or other data plane network elements to support mobility. Note since the LISP mobile node design does not require these data plane elements, there is no triangle routing of data packets as is found in Mobile IP [RFC3344][RFC3344]. o Not requiring new IPv6 extension headers to avoid triangle routing[RFC3775] [RFC3775]. The LISP Mobile Node extension design requires the use of the LISP Mobile Node [LISP-MN] technology to allow a LISP mobile node to roam and to be discovered in an efficient. The protocol mechanisms described in this document apply those cases in which a node's IP address changes frequently. Zhao, et al. Expires January 5, 2012 [Page 3] Internet-Draft LISP Mobile Node extension July 2011 2. Terminology This section defines the terms used in this document. LISP Mobile Node (LISP-MN): A LISP capable fast roaming mobile hand- set. Endpoint ID (EID): This is the traditional LISP EID [LISP], and is the address that a LISP mobile node uses as its address for transport connections. A LISP mobile node never changes its EID, which is typically a /32 or /128 prefix and is assigned to a loopback interface. Note that the mobile node can have multiple EIDs, and these EIDs can be from different address families. Routing Locator (RLOC): This is the traditional LISP RLOC, and is in general a routable address that can be used to reach a mobile node. Note that there are cases in which an mobile node may receive an address that it thinks is an RLOC (perhaps via DHCP) which is either an EID or an RFC 1918 address [RFC1918][RFC1918]. This could happen if, for example, if the mobile node roams into a LISP domain or a domain behind a Network Address Translator (NAT)). Map-cache: A data structure which contains an EID-prefix, its associated RLOCs, and the associated policy. Map-caches are typically found in ITRs and PITRs. Map Update: A Map update is the lisp-MN notifies the correspondent to change the EID-to-RLOC mapping when the lisp-MN move to another location in the communication process. Map Unregister: A Map Unregister is the lisp-MN notifies the MS[LISP-Map-Server] to unbind the EID-to-RLOC mapping when the lisp-MN needn't to attached to the network. Zhao, et al. Expires January 5, 2012 [Page 4] Internet-Draft LISP Mobile Node extension July 2011 3. LISP-MN Extension Operation It has introduced some aspects of lisp-MN, but there are areas have not covered in the lisp-MN. 3.1. EID-to-RLOC Mapping Update Operation TBD 3.2. Map-Unregister Operation TBD Zhao, et al. Expires January 5, 2012 [Page 5] Internet-Draft LISP Mobile Node extension July 2011 4. LISP-MN Extension Message TBD 4.1. LISP Packet Type Allocations This section will be the authoritative source for allocating LISP Type values. Current allocations are: o LISP Map-Update: 5 b'0101' o LISP Map-Unregister: 6 b'0110' 4.2. Map-Update Message Format The Map-Update message format is: 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=5 |P| Reserved | Record Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Nonce . . . | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | . . . Nonce | +-> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | Record TTL | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ R | Locator Count | EID mask-len | ACT |A| Reserved | e +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ c | Rsvd | Map-Version Number | EID-prefix-AFI | o +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ r | EID-prefix | d +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | /| Priority | Weight | M Priority | M Weight | | L +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | o | Unused Flags |L|p|R| Loc-AFI | | c +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | \| Locator | +-> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mapping Protocol Data | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Map-Update Message Format Packet field descriptions: Zhao, et al. Expires January 5, 2012 [Page 6] Internet-Draft LISP Mobile Node extension July 2011 Type: 5 (Map-Update) The Map-Update message has the same contents as a Map-Register message. See Map-Register section for field descriptions. 4.3. Map-Unregister Message Format The Map-Unregister message format is: 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=6 |P| Reserved | Record Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Nonce . . . | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | . . . Nonce | +-> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | Record TTL | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ R | Locator Count | EID mask-len | ACT |A| Reserved | e +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ c | Rsvd | Map-Version Number | EID-prefix-AFI | o +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ r | EID-prefix | d +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | /| Priority | Weight | M Priority | M Weight | | L +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | o | Unused Flags |L|p|R| Loc-AFI | | c +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | \| Locator | +-> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mapping Protocol Data | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Packet field descriptions: Type: 6 (Map-Unregister) The Map-Unregister message has the same contents as a Map-Register message. See Map-Register section for field descriptions. Zhao, et al. Expires January 5, 2012 [Page 7] Internet-Draft LISP Mobile Node extension July 2011 5. Security Considerations Security for the LISP-MN design builds upon the security fundamentals found in LISP [LISP] for data-plane security and the LISP Map Server [LISP-MS] registration security. Security issues unique to the LISP-MN design are considered below. Zhao, et al. Expires January 5, 2012 [Page 8] Internet-Draft LISP Mobile Node extension July 2011 6. IANA Considerations This document creates no new requirements on IANA namespaces [RFC5226]. Zhao, et al. Expires January 5, 2012 [Page 9] Internet-Draft LISP Mobile Node extension July 2011 7. Acknowledgments TBD Zhao, et al. Expires January 5, 2012 [Page 10] Internet-Draft LISP Mobile Node extension July 2011 8. References 8.1. Normative References [RFC1918] Rekhter, Y. and R. Moskowitz, "Address Allocation for Private Internets", 1996. [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, March 2002. [RFC3775] Johnson, D., Perkins, C., and G. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. 8.2. Informative References [LISP-Map-Server] Farinacci, D. and V. Fuller, "LISP Map Server", draft-ietf-lisp-ms-08 work in progress, June 2011. Zhao, et al. Expires January 5, 2012 [Page 11] Internet-Draft LISP Mobile Node extension July 2011 Authors' Addresses Ningxia Zhao ZTE Corporation 4F,RD Building 2,Zijinghua Road No.68 Yuhuatai District,Nanjing 210012 P.R.China Phone: +86-025-5287-7612 Email: zhao.ningxia@zte.com.cn Mo Sun ZTE Corporation 4F,RD Building 2,Zijinghua Road No.68 Yuhuatai District,Nanjing 210012 P.R.China Phone: +86-025-5287-7612 Email: wang.jun17@zte.com.cn Jun Shen ZTE Corporation C1-04,RD Building 1,Zijinghua Road No.68 Yuhuatai District,Nanjing 210012 P.R.China Phone: +86-025-5287-2045 Email: meng.yu@zte.com.cn Zhao, et al. Expires January 5, 2012 [Page 12]