LISP Flow Mapping

Major Features




Security Considerations

  • Do you have any external interfaces other than RESTCONF?
  • Yes, the southbound plugin
    • If so, how are they secure? * LISP southbound plugin follows LISP RFC6833 security guidelines.
    • What port numbers do they use? * Port used: 4342
  • Other security issues? * None

Quality Assurance

  • Link to Sonar Report (59.6%)
  • Link to CSIT Jobs
  • All modules have been unit tested. Integration tests have been performed for all major features. System tests have been performed on most major features.
  • Registering and retrieval of basic mappings have been tested more thoroughly. More complicated mapping policies have gone through less testing.


  • Is it possible to migrate from the previous release? If so, how?
    • LISP Flow Mapping service will auto-populate the datastructures from existing MD-SAL data upon service start if the data has already been migrated separately. No automated way for transfering the data is provided in this release.


  • Is this release compatible with the previous release?
    • Yes
  • Any API changes?
    • No
  • Any configuration changes?
    • No

Bugs Fixed

  • None

Known Issues

  • Clustering is still an experimental feature and may have some issues particularly related to operational datastore consistency.
  • Link to Open Bugs


  • None


  • The LISP implementation module and southbound plugin conforms to the IETF RFC6830 and RFC6833 , with the following exceptions:
    • In Map-Request message, M bit(Map-Reply Record exist in the MapRequest) is processed but any mapping data at the bottom of a Map-Request are discarded.
    • LISP LCAFs are limited to only up to one level of recursion, as described in the IETF LISP YANG draft.
    • No standards exist for the LISP Mapping System northbound API as of this date.

Release Mechanics