end host mobility use cases for lisp
Download
Skip this Video
Download Presentation
End Host Mobility Use Cases for LISP

Loading in 2 Seconds...

play fullscreen
1 / 10

End Host Mobility Use Cases for LISP - PowerPoint PPT Presentation


  • 88 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' End Host Mobility Use Cases for LISP' - vinnie


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
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
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
1 lisp ip mobility extended subnets
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

2 lisp ip mobility across subnets
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

3 lisp mac layer mobility lisp as layer 2 extension
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

4 lisp combined l2 l3 mobility
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

5 lisp unified l2 l3 mobility
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

unified l2 l3 lisp xtr
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
multihop mobility
Multihop Mobility
  • Decoupling of Host-Detection and LISP Signaling
  • Can cater for extended subnet and across subnet use cases (1 and 2)
request to wg
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
ad