Dear all,
with this email I am kindly requesting to become the maintainer of the LISP
(Locator/Identity Separation Protocol) Openwrt package.
A significant update to version 0.3 is available for commit (with the help
of developer "Acinonyx") and has been tested successfully under 12.09
(Attitude Adjustment) RC1.
Ths new version does not rely any more on a kernel module (kmod-lisp-*).
Instead it is just a user space application that makes use of kmod-tun.

More info about the project:

Version 0.3 introduces major changes the most important being to
discontinue the separation of data-plane in kernel-space and control-plane
in
user-space for a merged data+control user-space daemon. This is done through
the use of TUN/TAP, creating a TUN virtual interface to deal with
data-plane.

This big architecture change was also used to perform a general clean-up and
restructure most of the code. Due to this, existing (or partially
developed)
functionalities should be adapted to the new architecture and structure.

This is the list of supported features at this moment:
    - Register to the Mapping System
    - Request mappings
    - Reply to mapping requests
    - Encapsulate data packets
    - Decapsulate data packets
    - RLOC Probing (reply only)

The Locator/ID Separation Protocol (LISP) is being developed within the IETF
as a potential solution to the routing scalability problem documented in RFC
4984. It uses the concept of Endpoint IDentifiers (EIDs) to name hosts in
edge
networks, and Routing LOCators (RLOCs) for nodes in transit networks. EIDs
and
RLOCs are syntactically indistinguishable from current IPv4 and IPv6
addresses,
enabling backwards compatibility with the existing Internet architecture. A
distributed database, the mapping system, is responsible for maintaining the
associations between EIDs and RLOCs.

The LISPmob project aims to deliver a full implementation of this
specification for Linux, but parts of the implementation may be reusable on
other Unix-like operating systems.

LISPmob consists of three major components:
  * data plane
  * control plane
  * tools

Since version 0.3, the user space daemon `lispd` is responsible for both
control plane and data plane functionality. It is responsible to create a
virtual interface for the EID(s), encapsulating/decapsulating packets,
maintaining the mapping cache, etc. (data plane functionality) and for
sending and receiving control messages, managing interfaces, etc. (control
plane functionality), among other features.

Thank you for your consideration and looking forward to your reply!
Vasileios Lakafosis
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to