1 / 10

End Host Mobility Use Cases for LISP

End Host Mobility Use Cases for LISP. draft- hertoghs -lisp-mobility-use- cases Yves Hertoghs Marc Binderberger. Overview. Use Case Draft for LISP for network-assisted host mobility 7 Use Cases

vinnie
Download Presentation

End Host Mobility Use Cases for LISP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. End Host Mobility Use Cases for LISP draft-hertoghs-lisp-mobility-use-cases Yves Hertoghs Marc Binderberger

  2. Overview • Use Case Draft for LISP for network-assisted host mobility • 7 Use Cases • Mobility when subnet is L2 extended (non-LISP technology) across LISP sites (EID = IPv4/6 address) • IP Mobility across subnets/LISP sites (EID = IPv4/6 address • Layer 2 Mobility/Extension using LISP (EID = MAC-Address) • A Combination of 1 and 3 : (EID = IPv4/6 address for inter-subnet, EID = MAC for intra-subnet) • Unified L2/L3 LISP: Use EID = IPv4/6 for all IP Mobility (intra and intersubnet), Use EID = MAC-Address for all non-IP traffic • Multi-hop variant of 1 : Mobility detection and LISP signalling are one or more L3 hops apart • Multi-hop variant of 2 : Mobility detection and LISP signalling are one or more L3 hops away

  3. 1. LISP IP Mobility Extended Subnets Remote LISP site W Remote NON-LISP site LISP xTR RLOC Namespace LISP PxTR LISP xTR LISP xTR EID Prefix ‘A’ LISP Site Z L2 Extension EID Prefix ‘A’ LISP Site Y Host_1 EID = IP Host Move

  4. 2. LISP IP Mobility Across Subnets Remote LISP site W Remote NON-LISP site LISP xTR RLOC Namespace LISP PxTR LISP xTR LISP xTR EID Prefix ‘B’ LISP Site Z EID Prefix ‘A’ LISP Site Y Host_1 EID = IP Host Move

  5. 3. LISP MAC-Layer Mobility (LISP as Layer 2 extension) RLOC Namespace LISP xTR LISP xTR L2 Domain ‘A’ LISP Site Z L2 Domain ‘A’ LISP Site Y Host_1 EID = MAC Host Move

  6. 4. LISP Combined L2/L3 Mobility Remote LISP site W Remote NON-LISP site LISP xTR RLOC Namespace LISP PxTR LISP xTR LISP xTR EID Prefix ‘A’ LISP Site Z EID Prefix ‘A’ LISP Site Y Host_1 EID = MAC EID = IP Host Move

  7. 5. LISP Unified L2/L3 Mobility Remote LISP site W Remote NON-LISP site LISP xTR RLOC Namespace LISP PxTR LISP xTR LISP xTR EID Prefix ‘A’ LISP Site Z EID Prefix ‘A’ LISP Site Y Host_1 EID = IP (EID = MAC for non-IP) Host Move

  8. Unified L2/L3 LISP xTR • First hop device is a LISP xTR, and the default gateway for all traffic • Default Gateway identity (MAC/IP address) is the same per subnet independent of location • Offers simultaneous support for IP and non-IP traffic, independent of subnets and location. • IP and MAC EID’s are registered to support IP. • MAC EIDs are registered to support non-IP (when needed) • Forwarding of all IP traffic involves an IP lookup (intra- and inter-subnet/LISP IID traffic), forwarding on non-IP involves a MAC lookup. • Registering both IP and MAC addresses for IP aids ARP/IPv6 ND handling as well as rewrites to allow transparency for intrasubnet IP forwarding from a host perspective. • Why? • Optimal forwarding for IP traffic, no traffic tromboning independent of End-station location, or intra- versus inter subnet/LISP IID. • Single lookup for IP traffic independent of destination • No need for network wide broadcast domains to achieve Mobility intra-subnet

  9. Multihop Mobility • Decoupling of Host-Detection and LISP Signaling • Can cater for extended subnet and across subnet use cases (1 and 2)

  10. Request to WG • Consider this draft as a Use Case for LISP • Consider this draft as input for potential future development of the LISP protocol • Request comments and eventually move to WG Draft

More Related