Contents
Features
The major features of Beryllium release:
| Name | Description |
|---|---|
| NSH Support | Support for NSH and SPI-based mappings in LISP Mapping System and LISP SB. |
| Decoupling of SB and NB mappings | Support for parallel data stores for SB registrations and NB mappings. |
| Merge support on SB registrations | Support merging mapping registrations from SB for the same virtual address. |
| Integrating NB policy and SB mappings | Support for combining SB registrations and NB mappings. |
| GUI support | Initial GUI support for adding new mappings and visibility into the mapping system via DLUX. |
| YANG model revision | Updated the YANG models according to the IETF YANG models for LISP where appropriate. |
Non-Code Aspects (user docs, examples, tutorials, articles)
- Release notes
- Architecture Overview
- API Documentation
- Installation Guide(s) - LISP Flow Mapping installation follows the usual installation process. Config options are documented in the User Guide documentation.
ASCII doc commits:
Security Considerations
LISP southbound plugin follows LISP RFC6830 security guidelines. A key/password is associated with every EID prefix which is used to create a MAC (Message Authentication Code) of the UDP LISP control messages for authentication and integrity protection of the UDP messages. This is implemented as specified in the LISP RFC6830. These keys can be defined through the northbound APIs.
Quality Assurance (test coverage, etc)
- Unit Tests: coverage is at 50.3% as reported in Sonar.
- Integration Tests: About 30 integration tests have been implemented and are passed.
- Automated System Tests are all passing:
- System tests performed manually with success.
- No blocking issues identified as yet.
End-of-life (API/Features EOLed in Release)
- The NB API in Lithium is now EoLed.
Bugzilla (summary of bug situation)
Two outstanding bugs, with normal or minor criticality to be addressed in SR1.
Standards (summary of standard compliance)
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.
Schedule (initial schedule and changes over the release cycle)
Original schedule was followed.