Contents
Name
OpenDaylight LISP Mapping Service
Repo Name
lispflowmapping (Lisp Flow Mapping)
Description
Today, most dominant use cases of SDN are defined in the context of Network Virtualization, enabled by network overlays. LISP (RFC6830) is a protocol that enables separation of Endpoint Identity (EID) from Routing Location (RLOC) by defining an overlay in the EID space which is mapped to the underlying network in the RLOC space. LISP also provides a Mapping Service that provides the EID-to-RLOC mapping information including forwarding policy (load balancing, traffic engineering, etc.) to LISP routers for tunneling and forwarding purposes. In the context of Network virtualization, a Mapping Service can be queried by LISP-enabled network devices (virtual/physical) to provide the mapping of the virtual network endpoints to the underlying physical network, including the associated forwarding policies.
The LISP Mapping Service can serve the mapping data to dataplane nodes as well as to ODL applications. To leverage this service, a northbound API allows OpenDaylight applications and services to define the mappings and policies in the LISP Mapping Service. This project also includes a southbound LISP plugin that enables LISP dataplane devices to interact with the OpenDaylight via the LISP protocol.
The following figure depicts the described components.
Scope
The OpenDaylight LISP Mapping Service includes:
- LISP Map Server
- LISP Map Resolver
- Southbound ODL plugin supporting LISP protocol
- LISP Mapping Services northbound API
Resources Committed (developers committed to working)
Committers listed below are committed as resources for development:
Committers:
- Gal Mainzer (ConteXtream)
- Guy Sela (ConteXtream)
- David Goldberg (ConteXtream)
- Vina Ermagan (Cisco)
- Lori Jakab (Cisco)
Contributors
List of main contributors to the project include:
- Gal Mainzer (ConteXtream)
- Guy Sela (ConteXtream)
- David Goldberg (ConteXtream)
- Alberto Rodriguez-Natal (UPC)
- Vina Ermagan (Cisco)
- Lori Jakab (Cisco)
Vendor Neutral
- No vendor package names in code
- No vendor branding / trademark present in code or output of build
- No vendor branding / trademark present in documentation
MeetsBoardPolicy(including IPR)
- Inbound Code Review Complete with no issues {Phil Robb: 7/10/13}
Back to LISP FLow Mapping Main Page
Back to LISP FLow Mapping Main