The use of LISP for IPv6 migration

Technical lecture for network engineers - in German

25. Februar 2013, 18 bis 20 Uhr

Digicomp, Limmatstrasse 50, 8005 Zürich

Event sponsor:

DigicompIPv6 Hands-on courses.

Target audience:
Security responsibles, network engineers, IT Professionals

We are pleased to invite you to the first event in 2013. This is also the first event of our new serie of technical-focused events which will be held at Digicomp in Zürich. They will take place the last Monday evening per month. Digicomp is sponsoring the venue and the apéro. 

Gerd Pflüger, Cisco Consulting Engineer, opens the new event series with a very exciting lecture about LISP (Locator/ID Separation Protocol) and its use for IPv6 migration.


17:30 - 18:00Pre-Lounge-Networking and welcoming
18:00 - ca 18:40

Presentation "Migration to IPv6 with LISP" by Gerd Pflüger

- LISP - hos does it work?
- LISP - Usecases
- LISP - IPv6 migration details

18.40 - ca 19:00Q&A and discussion
followed byNetworking apero

Location: Digicomp, Limmatstrasse 50, 8005 Zürich
CHF 20.- (collected at the event)
Apero and snacks start around 7pm.



Locator/ID Separation Protocol (LISP) is a new standard based routing architecture with new semantics for IP-adressing. With LISP you can connect IPv6 islands or IPv6 websites to IPv4 networks to facilitate and accelerate IPv6 migration. 
This technical lecture explains the fundamentals of LISP. Gerd Pflüger depicts briefly the different use cases in order to present in detail the possibilities of LISP and IPv6 migration. Together we discuss the advantages and the different designs. 
Gerd Pflüger, Cisco Consulting Engineer
For many years I have asked myself what could eventually come after MPLS as a routing architecture. And actually, my expectation was that we will solve customer designs with MPLS forever. But now I know that we can do better:  not label IP packets, but encapsulate them in IP. And LISP can do just that! LISP encapsulates in IP and offers similar services like MPLS, only that transport is much easier. Also the control-plane is much easier, going away from distribution of routing information per push to a request procedure with pull. Overall: a very important issue for all network designers!
  • English
  • Deutsch
  • Français