LISP Canonical Address Format (LCAF)

Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)

“…(See Section 4.7 of [RFC8060] for details regarding the R bit.) The DDT node must also include a signature in the Record that covers this Record; this is computed using the private key corresponding to the key being revoked.…”

“…o Additional key structures for use with LISP-DDT, such as key structures to support additional EID formats as defined in [RFC8060].…”

Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT) Referral Internet Groper (RIG)

“…Endpoint Identifier (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value (or an address encoded per [RFC8060]) used in the source and destination address fields of the first (innermost) LISP header of a packet. The host obtains a destination EID the same way it obtains a destination address today --for example, through a Domain Name System (DNS) [RFC1034] lookup or a Session Initiation Protocol (SIP) [RFC3261] exchange.…”

Location and identity privacy for LISP-MN

“…This could include the geo-coordinates of the RTRs, their the current load, the probability of an attack on each on them, etc. The exact information included is up to the specific implementation, but it can be encoded in the LISP control messages using the format defined in [16]. The MN can use that extra information provided by the Mapping System to choose the most suitable RTR for its needs, e.g either choose a close RTR to reduce the latency or choose a far away one to better mislead possible attackers.…”