lispers.net

San Jose CA United States of America farinacci@gmail.com

Brocade

San Jose CA United States of America dmm@1-4-5.net

NTT Communications

Theodorus Majofskistraat 100 Amsterdam 1065 SZ The Netherlands job@ntt.net

This document defines a canonical address format encoding used in Locator/ID Separation Protocol (LISP) control messages and in the encoding of lookup keys for the LISP Mapping Database System.

The LISP architecture and protocol introduces two new numbering spaces: Endpoint Identifiers (EIDs) and Routing Locators (RLOCs). To provide flexibility for current and future applications, these values can be encoded in LISP control messages using a general syntax that includes Address Family Identifier (AFI), length, and value fields. Currently defined AFIs include IPv4 and IPv6 addresses, which are formatted according to code-points assigned in the "Address Family Numbers" registry as follows:

IPv4-Encoded Address:

IPv6-Encoded Address:

This document describes the currently defined AFIs that LISP uses along with their encodings and introduces the LISP Canonical Address Format (LCAF) that can be used to define the LISP-specific encodings for arbitrary AFI values. Specific detailed uses for the LCAF Types defined in this document can be found in the use-case documents that implement them. The same LCAF Type may be used by more than one use-case document. As an Experimental specification, this work is, by definition, incomplete. The LCAF Types defined in this document are to support experimentation and are intended for cautious use in self-contained environments in support of the corresponding use-case documents. This document provides assignment for an initial set of approved LCAF Types (registered with IANA) and additional unapproved LCAF Types . The unapproved LCAF encodings are defined to support further study and experimentation.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

a term used to describe an address encoding in a packet. Address families are defined for IPv4 and IPv6. See and for details. The reserved AFI value of 0 is used in this specification to indicate an unspecified encoded address where the length of the address is 0 bytes following the 16-bit AFI value of 0.

Unspecified Address Format: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ]]>

a 32-bit (for IPv4) or 128-bit (for IPv6) value used in the source and destination address fields of the first (most inner) LISP header of a packet. The host obtains a destination EID the same way it obtains a destination address today, for example, through a DNS lookup or SIP exchange. The source EID is obtained via existing mechanisms used to set a host's "local" IP address. An EID is allocated to a host from an EID-prefix block associated with the site where the host is located. An EID can be used by a host to refer to other hosts. the IPv4 or IPv6 address of an Egress Tunnel Router (ETR). It is the output of an EID-to-RLOC mapping lookup. An EID maps to one or more RLOCs. Typically, RLOCs are numbered from topologically aggregatable blocks that are assigned to a site at each point to which it attaches to the global Internet; where the topology is defined by the connectivity of provider networks, RLOCs can be thought of as Provider-Assigned (PA) addresses. Multiple RLOCs can be assigned to the same ETR device or to multiple ETR devices at a site.

IANA has assigned AFI value 16387 (0x4003) to the LISP Canonical Address Format (LCAF). This specification defines the encoding format of the LISP Canonical Address (LCA). This section defines all Types for which an initial allocation in the LISP-LCAF registry is requested. See for the complete list of such Types. The AFI definitions in only allocate code-points for the AFI value itself. The length of the address or entity that follows is not defined and is implied based on conventional experience. When LISP uses LCAF definitions from this document, the AFI-based address lengths are specified in this document. When new LCAF definitions are defined in other use-case documents, the AFI-based address lengths for any new AFI-encoded addresses are specified in those documents.

The first 6 bytes of a LISP Canonical Address are followed by a variable number of fields of variable length:

these 8-bit fields are reserved for future use and MUST be transmitted as 0 and ignored on receipt. this 8-bit field is for future definition and use. For now, set to zero on transmission and ignored on receipt. this 8-bit field is specific to the LISP Canonical Address Format encodings. Both approved and unapproved values are listed below. Unapproved values are indicated; see Section 5 for more details. Null Body AFI List Instance ID AS Number Application Data (unapproved; see Section 5) Geo-Coordinates Opaque Key (unapproved; see Section 5) NAT-Traversal Nonce Locator (unapproved; see Section 5) Multicast Info Explicit Locator Path Security Key Source/Dest Key Replication List Entry JSON Data Model (unapproved; see Section 5) Key/Value Address Pair (unapproved; see Section 5) Encapsulation Format (unapproved; see Section 5) this 16-bit field is in units of bytes and covers all of the LISP Canonical Address payload, starting and including the byte after the Length field. When including the AFI, an LCAF-encoded address will have a minimum length of 8 bytes when the Length field is 0. The 8 bytes include the AFI, Flags, Type, Rsvd1, Rsvd2, and Length fields. When the AFI is not next to an encoded address in a control message, the encoded address will have a minimum length of 6 bytes when the Length field is 0. The 6 bytes include the Flags, Type, Rsvd1, Rsvd2, and Length fields. states RLOC-records based on an IP address are sorted when encoded in control messages, so the locator-set has consistent order across all xTRs for a given EID. The sort order is based on sort-key {afi, RLOC-address}. When an RLOC based on an IP address is LCAF encoded, the sort-key is {afi, LCAF-Type}. Therefore, when a locator-set has a mix of AFI records and LCAF records, they are ordered from smallest to largest AFI value.

The following sections define the LCAF for the currently approved initial set of Type values.

When multiple organizations inside of a LISP site are using private addresses as EID prefixes, their address spaces must remain segregated due to possible address duplication. An Instance ID in the address encoding can aid in making the entire AFI-based address unique. Another use for the Instance ID LISP Canonical Address Format is when creating multiple segmented VPNs inside of a LISP site where keeping EID-prefix-based subnets is desirable.

Instance ID LISP Canonical Address Format:

if the AFI is set to 0, then this format is not encoding an extended EID prefix, but rather an Instance ID range where the 'IID mask-len' indicates the number of high-order bits used in the Instance ID field for the range. The low-order bits of the Instance ID field must be 0. length in bytes starting and including the byte after this Length field. the low-order 24 bits that can go into a LISP data header when the I bit is set. See for details. The reason for the length difference is so that the maximum number of instances supported per mapping system is 2^32, while conserving space in the LISP data header. This comes at the expense of limiting the maximum number of instances per xTR to 2^24. If an xTR is configured with multiple Instance IDs where the value in the high-order 8 bits is the same, then the low-order 24 bits MUST be unique. x can be any AFI value from . This LISP Canonical Address Type can be used to encode either EID or RLOC addresses. Usage: When used as a lookup key, the EID is regarded as an extended-EID in the mapping system. This encoding is used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP Delegated Database Tree (LISP-DDT) is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.

When an Autonomous System (AS) number is stored in the LISP Mapping Database System for either policy or documentation reasons, it can be encoded in a LISP Canonical Address.

AS Number LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. the 32-bit AS number of the autonomous system that has been assigned to either the EID or RLOC that follows. x can be any AFI value from . The AS Number LCAF Type can be used to encode either EID or RLOC addresses. The former is used to describe the LISP-ALT AS number the EID prefix for the site is being carried for. The latter is used to describe the AS that is carrying RLOC based prefixes in the underlying routing system. Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.

If an ETR desires to send a Map-Reply describing the Geo-Coordinates for each locator in its locator-set, it can use the Geo-Coordinates LCAF Type to convey physical location information. Coordinates are specified using the WGS 84 (World Geodetic System 1984) reference coordinate system .

Geo-Coordinates LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. When set to 1 means north; otherwise, south. Valid values range from 0 to 90 degrees above or below the equator (northern or southern hemisphere, respectively). Valid values range from 0 to 59. Valid values range from 0 to 59. When set to 1 means east; otherwise, west. Valid values are from 0 to 180 degrees right or left of the Prime Meridian. Valid values range from 0 to 59. Valid values range from 0 to 59. Height relative to sea level in meters. This is a two's complement signed integer meaning that the altitude could be below sea level. A value of 0x7fffffff indicates no Altitude value is encoded. x can be any AFI value from . The Geo-Coordinates LCAF Type can be used to encode either EID or RLOC addresses. When used for EID encodings, you can determine the physical location of an EID along with the topological location by observing the locator-set. Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages. The use of the Geo-Coordinates LCAF encoding raises privacy issues as location information is privacy sensitive, and possibly unexpectedly privacy-sensitive information may be conveyed, e.g., if the location information corresponds to a router located in a person's home. Therefore, this encoding should not be used unless needed for operation of a LISP deployment. Before electing to utilize this encoding, care should be taken to ensure the appropriate policies are being used by the EID for controlling the conveyed information.

When a LISP system is conveying global-address and mapped-port information when traversing through a NAT device, the NAT-Traversal LCAF Type is used. See for details.

NAT-Traversal Canonical Address Format:

length in bytes starting and including the byte after this Length field. this is the UDP port number of the Map-Server and is set to 4342. this is the port number returned to a LISP system that was copied from the source port from a packet that has flowed through a NAT device. x can be any AFI value from . this is an address known to be globally unique built by NAT-traversal functionality in a LISP router. this is the address of the Map-Server used in the destination RLOC of a packet that has flowed through a NAT device. this is an address known to be a private address inserted in this LCAF by a LISP router that resides on the private side of a NAT device. this is an encapsulation address used by an Ingress Tunnel Router (ITR) or Proxy Ingress Tunnel Router (PITR) that resides behind a NAT device. This address is known to have state in a NAT device so packets can flow from it to the LISP ETR behind the NAT. There can be one or more NAT Re-encapsulating Tunnel Router (RTR) addresses supplied in these set of fields. The number of RTRs encoded is determined by parsing each field. When there are no RTRs supplied, the RTR fields can be omitted and reflected by the LCAF length field or an AFI of 0 can be used to indicate zero RTRs encoded. Usage: This encoding can be used in Info-Request and Info-Reply messages. The mapping system does not store this information. The information is used by an xTR and Map-Server to convey private and public address information when traversing NAT and firewall devices. Care should be taken to protect privacy against the adverse use of a Global or Private ETR RLOC Address by ensuring policy controls are used during EID registrations that use this LCAF Type in RLOC-records. Refer to the use-case documents for additional information.

Multicast group information can be published in the mapping database. So a lookup on a group address EID can return a replication list of RLOC group addresses or RLOC unicast addresses. The intent of this type of unicast replication is to deliver packets to multiple ETRs at receiver LISP multicast sites. The locator-set encoding for this EID-record Type can be a list of ETRs when they each register with "Merge Semantics". The encoding can be a typical AFI-encoded locator address. When an RTR list is being registered (with multiple levels according to ), the Replication List Entry LCAF Type is used for locator encoding. This LCAF encoding can be used to send broadcast packets to all members of a subnet when an EID is away from its home subnet location.

Multicast Info Canonical Address Format:

length in bytes starting and including the byte after this Length field. must be set to zero and ignored on receipt. the low-order 24 bits that can go into a LISP data header when the I bit is set. See for details. The use of the Instance ID in this LCAF Type is to associate a multicast forwarding entry for a given VPN. The Instance ID describes the VPN and is registered to the mapping database system as a 3-tuple of (Instance ID, S-prefix, G-prefix). the mask length of the source prefix that follows. The length is the number of high-order mask bits set. the mask length of the group prefix that follows. The length is the number of high-order mask bits set. x can be any AFI value from . When a specific address family has a multicast address semantic, this field must be either a group address or a broadcast address. the source address or prefix for encoding an (S,G) multicast entry. the group address or group prefix for encoding (S,G) or (*,G) multicast entries. Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.

For a given EID lookup into the mapping database, this LCAF can be returned to provide a list of locators in an explicit re-encapsulation path. See for details.

Explicit Locator Path (ELP) Canonical Address Format:

length in bytes starting and including the byte after this Length field. this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt. this is the Lookup bit used to indicate to the user of the ELP not to use this address for encapsulation but to look it up in the mapping database system to obtain an encapsulating RLOC address. this is the RLOC Probe bit that means the Reencap Hop allows RLOC-probe messages to be sent to it. When the R bit is set to 0, RLOC-probes must not be sent. When a Reencap Hop is an anycast address then multiple physical Reencap Hops are using the same RLOC address. In this case, RLOC-probes are not needed because when the closest RLOC address is not reachable, another RLOC address can be reachable. this is the Strict bit, which means the associated Reencap Hop is required to be used. If this bit is 0, the re-encapsulator can skip this Reencap Hop and go to the next one in the list. x can be any AFI value from . When a specific AFI has its own encoding of a multicast address, this field must be either a group address or a broadcast address. Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. This encoding does not need to be understood by the mapping system for mapping database lookups, since this LCAF Type is not a lookup key.

When a locator in a locator-set has a security key associated with it, this LCAF will be used to encode key material. See for details.

Security Key Canonical Address Format:

length in bytes starting and including the byte after this Length field. the Key Count field declares the number of Key sections included in this LCAF. A Key section is made up of Key Length and Key Material fields. this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt. the Key Algorithm field identifies the key's cryptographic algorithm and specifies the format of the Public Key field. Refer to the and use cases for definitions of this field. this field is reserved for future use and MUST be transmitted as 0 and ignored on receipt. this is the Revoke bit and, if set, it specifies that this key is being revoked. this field determines the length in bytes of the Key Material field. the Key Material field stores the key material. The format of the key material stored depends on the Key Algorithm field. x can be any AFI value from . This is the locator address that owns the encoded security key. Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages.

When both a source and destination address of a flow need consideration for different locator-sets, this 2-tuple key is used in EID fields in LISP control messages. When the Source/Dest key is registered to the mapping database, it can be encoded as a source-prefix and destination-prefix. When the Source/Dest is used as a key for a mapping database lookup, the source and destination come from a data packet.

Source/Dest Key Canonical Address Format:

length in bytes starting and including the byte after this Length field. must be set to zero and ignored on receipt. the mask length of the source prefix that follows. The length is the number of high-order mask bits set. the mask length of the destination prefix that follows. The length is the number of high-order mask bits set. x can be any AFI value from . y can be any AFI value from . When a specific address family has a multicast address semantic, this field must be either a group address or a broadcast address. Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages. Refer to for usage details of this LCAF Type.

The Replication List Entry LCAF Type is an encoding for a locator being used for unicast replication according to the specification in . This locator encoding is pointed to by a Multicast Info LCAF Type and is registered by Re-encapsulating Tunnel Routers (RTRs) that are participating in an overlay distribution tree. Each RTR will register its locator address and its configured level in the distribution tree.

Replication List Entry Canonical Address Format:

length in bytes starting and including the byte after this Length field. must be set to zero and ignored on receipt. this value is associated with the level within the overlay distribution tree hierarchy where the RTR resides. The level numbers are ordered from lowest value being close to the ITR (meaning that ITRs replicate to level-0 RTRs) and higher levels are further downstream on the distribution tree closer to ETRs of multicast receiver sites. x can be any AFI value from . A specific AFI has its own encoding of either a unicast or multicast locator address. For efficiency reasons, all RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message. Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages.

When header translation between IPv4 and IPv6 is desirable, a LISP Canonical Address can use the AFI List LCAF Type to carry a variable number of AFIs in one LCAF AFI.

Address Binding LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. This type of address format can be included in a Map-Request when the address is being used as an EID, but the LISP Mapping Database System lookup destination can use only the IPv4 address. This is so a Mapping Database Service Transport System, such as LISP-ALT , can use the Map-Request destination address to route the control message to the desired LISP site. Usage: This encoding can be used in EID-records or RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. See the other subsections in this section for specific use cases.

When Media Access Control (MAC) addresses are stored in the LISP Mapping Database System, the AFI List LCAF Type can be used to carry AFI 6.

MAC Address LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. This address format can be used to connect Layer 2 domains together using LISP over an IPv4 or IPv6 core network to create a Layer 2 VPN. In this use case, a MAC address is being used as an EID, and the locator-set that this EID maps to can be an IPv4 or IPv6 RLOC, or even another MAC address being used as an RLOC. See for how Layer 2 VPNs operate when doing EID mobility. Care should be taken to protect privacy against the adverse use of a Layer 2 MAC address by ensuring policy controls are used during EID registrations that use AFI=6 encodings in RLOC-records. Refer to the use-case documents for additional information.

If DNS names or URIs are stored in the LISP Mapping Database System, the AFI List LCAF Type can be used to carry an ASCII string.

ASCII LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. An example for using DNS names is when an ETR registers a mapping with an EID-record encoded as (AFI=1, 10.0.0.0/8) with an RLOC-record (AFI=17, "router.abc.com").

When any combination of above is desirable, the AFI List LCAF Type value can be used to carry within the LCAF AFI another LCAF AFI (for example, Application-Specific Data in ).

Recursive LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. length in bytes starting and including the byte after this Length2 field. This format could be used by a Mapping Database Service Transport System, such as LISP-ALT , where the AFI=1 IPv4 address is used as an EID and placed in the Map-Request destination address by the sending LISP system. The ALT system can deliver the Map-Request to the LISP destination site independent of the Application Data LCAF Type AFI payload values. When this AFI is processed by the destination LISP site, it can return different locator-sets based on the type of application or level of service that is being requested.

A LISP system should use the AFI List LCAF Type format when sending to LISP systems that do not support a particular LCAF Type used to encode locators. This allows the receiving system to be able to parse a locator address for encapsulation purposes. The list of AFIs in an AFI List LCAF Type has no semantic ordering and a receiver should parse each AFI element no matter what the ordering.

Compatibility Mode Address Format:

length in bytes starting and including the byte after this Length field. length in bytes starting and including the byte after this Length2 field. If a system does not recognized the Geo-Coordinates LCAF Type that is accompanying a locator address, an encoder can include the Geo-Coordinates LCAF Type embedded in an AFI List LCAF Type where the AFI in the Geo-Coordinates LCAF Type is set to 0 and the AFI encoded next in the list is encoded with a valid AFI value to identify the locator address. A LISP system is required to support the AFI List LCAF Type to use this procedure. It would skip over 10 bytes of the Geo-Coordinates LCAF Type to get to the locator address encoding (an IPv4 locator address). A LISP system that does support the Geo-Coordinates LCAF Type can support parsing the locator address within the Geo-Coordinates LCAF Type encoding or in the locator encoding that follows in the AFI List LCAF Type.

The following sections describe experimental LCAF encodings. These LCAF Types are not approved (i.e., not registered with IANA). The inclusion of these encodings in this document is in support of further study and experimentation to determine whether these encodings are functional, if there is a demand for these use cases, and to better understand deployment considerations. As noted previously, these LCAF Types are restricted to cautious use in self-contained environments in support of the corresponding use-case documents.

When a locator-set needs to be conveyed based on the type of application or the Per-Hop Behavior (PHB) of a packet, the Application Data LCAF Type can be used.

Application Data LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. this field stores the 8-bit IPv4 TOS field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow Label used in an IPv6 header. these fields are from the TCP, UDP, or Stream Control Transmission Protocol (SCTP) transport header. A range can be specified by using a lower value and an upper value. When a single port is encoded, the lower and upper value fields are the same. x can be any AFI value from . The Application Data LCAF Type is used for an EID encoding when an ITR wants a locator-set for a specific application. When used for an RLOC encoding, the ETR is supplying a locator-set for each specific application is has been configured to advertise. Usage: This encoding can be used in EID-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages. When LISP-DDT is used as the mapping system mechanism, extended EIDs are used in Map-Referral messages. This LCAF Type is used as a lookup key to the mapping system that can return a longest-match or exact-match entry.

When the LISP Mapping Database System holds information accessed by a generic formatted key (where the key is not the usual IPv4 or IPv6 address), an opaque key may be desirable.

Opaque Key LISP Canonical Address Format:

length in bytes starting and including the byte after this Length field. the value of this field is the number of "Key" sub-fields minus 1, the Key field can be broken up into. So, if this field has a value of 0, there is one sub-field in the "Key". The width of the sub-fields are fixed length. So, for a key size of 8 bytes, with a Key Field Num of 3, four sub-fields of 2 bytes each in length are allowed. Allowing for a reasonable number of 16 sub-field separators, valid values range from 0 to 15. describes which fields in the key are not used as part of the key lookup. This wildcard encoding is a bitfield. Each bit is a don't-care bit for a corresponding field in the key. Bit 0 (the low-order bit) in this bitfield corresponds the first field, the low-order field in the key, bit 1 the second field, and so on. When a bit is set in the bitfield, it is a don't-care bit and should not be considered as part of the database lookup. When the entire 16 bits are set to 0, then all bits of the key are used for the database lookup. the variable length key used to do a LISP Mapping Database System lookup. The length of the key is the value n (as shown above). Usage: This is an experimental Type where the usage has not yet been defined.

When a public Proxy Egress Tunnel Router (PETR) device wants to verify who is encapsulating to it, it can check for a specific nonce value in the LISP-encapsulated packet. To convey the nonce to admitted ITRs or PITRs, this LCAF is used in a Map-Register or Map-Reply locator-record.

Nonce Locator Canonical Address Format:

length in bytes starting and including the byte after this Length field. must be set to zero and ignored on receipt. a nonce value returned by an ETR in a Map-Reply locator-record to be used by an ITR or PITR when encapsulating to the locator address encoded in the AFI field of this LCAF Type. This nonce value is inserted in the nonce field in the LISP header encapsulation. x can be any AFI value from . Usage: This is an experimental Type where the usage has not yet been defined.

This Type allows a JSON data model to be encoded as either an EID or an RLOC.

JSON Data Model Type Address Format:

length in bytes starting and including the byte after this Length field. indicates that the JSON field is binary encoded according to when the bit is set to 1. Otherwise, the encoding is based on text encoding according to . length in octets of the following JSON binary/text encoding field. a variable-length field that contains either binary or text encodings. x can be any AFI value from . A specific AFI has its own encoding of either a unicast or multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message. Usage: This is an experimental Type where the usage has not yet been defined. An example mapping is an EID-record encoded as a distinguished-name "cpe-router" and an RLOC-record encoded as a JSON string "{ "router-address" : "1.1.1.1", "router-mask" : "8" }".

The Key/Value pair is, for example, useful for attaching attributes to other elements of LISP packets, such as EIDs or RLOCs. When attaching attributes to EIDs or RLOCs, it's necessary to distinguish between the element that should be used as EID or RLOC and, hence, as the key for lookups and additional attributes. This is especially the case when the difference cannot be determined from the Types of the elements, such as when two IP addresses are being used.

Key/Value Address Pair Address Format:

length in bytes starting and including the byte after this Length field. x is the "Address as Key" AFI that can have any value from . A specific AFI has its own encoding of either a unicast or a multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message. AFI-encoded address that will be attached with the attributes encoded in "Address as Value", which follows this field. y is the "Address of Value" AFI that can have any value from . A specific AFI has its own encoding of either a unicast or a multicast locator address. All RTR/ETR entries for the same level should be combined by a Map-Server to avoid searching through the entire multilevel list of locator entries in a Map-Reply message. AFI-encoded address that will be the attribute address that goes along with "Address as Key" which precedes this field. Usage: This is an experimental Type where the usage has not yet been defined.

Overlays are becoming popular in many parts of the network, which has created an explosion of data-plane encapsulation headers. Since the LISP mapping system can hold many types of address formats, it can represent the encapsulation format supported by an RLOC as well. When an encapsulator receives a Map-Reply with an Encapsulation Format LCAF Type encoded in an RLOC-record, it can select an encapsulation format, that it can support, from any of the encapsulation protocols that have the bit set to 1 in this LCAF Type.

Encapsulation Format Address Format:

length in bytes starting and including the byte after this Length field. must be set to zero and ignored on receipt. This field will get bits allocated to future encapsulations, as they are created. The RLOCs listed in the AFI-encoded addresses in the next longword can accept Generic UDP Encapsulation (GUE) using destination UDP port 6080 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept Geneve encapsulation using destination UDP port 6081 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept NV-GRE (Network Virtualization - Generic Routing Encapsulation) using IPv4/IPv6 protocol number 47 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept VXLAN-GPE (Generic Protocol Extension) encapsulation using destination UDP port 4790 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept Virtual eXtensible Local Area Network (VXLAN) encapsulation using destination UDP port 4789 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept Layer 2 LISP encapsulation using destination UDP port 8472 . The RLOCs listed in the AFI-encoded addresses in the next longword can accept Layer 3 LISP encapsulation using destination UDP port 4341 . Usage: This encoding can be used in RLOC-records in Map-Request, Map-Reply, Map-Register, and Map-Notify messages.

This document is classified as Experimental. The LCAF encodings defined in this document are intended to be used with their corresponding use cases and in self-contained environments. Users should carefully consider how the threat model applies to their particular use case. The use of the Geo-Coordinates LCAF Type may raise physical privacy issues. Care should be taken when configuring the mapping system to use specific policy parameters so geolocation information is not returned gratuitously. It is recommended that any documents that specify the use of the Geo-Coordinates LCAF Type should consider the applicability of RFC 6280 (BCP 160) for location-based privacy protection. Additional privacy concerns have arisen since publication of BCP 160, and future work on LISP should examine potential threats beyond BCP 160 and address improving privacy and security for LISP deployments.

This document defines a canonical address format encoding used in LISP control messages and in the encoding of lookup keys for the LISP Mapping Database System. Such an address format is based on a fixed AFI (16387) and a LISP LCAF Type field. The LISP LCAF Type field is an 8-bit field specific to the LISP Canonical Address Format encodings. IANA has created a new registry (as outlined in ) titled "LISP Canonical Address Format (LCAF) Types". Initial values for the "LISP Canonical Address Format (LCAF) Types" registry are given below. Future assignments are to be made using the Specification Required policy . Assignments consist of a LISP LCAF Type Name and its associated value: Value LISP LCAF Type Name Reference 0 Null Body Section 3 1 AFI List Section 3 2 Instance ID Section 3 3 AS Number Section 3 5 Geo-Coordinates Section 3 7 NAT-Traversal Section 3 9 Multicast Info Section 3 10 Explicit Locator Path Section 3 11 Security Key Section 3 12 Source/Dest Key Section 3 13 Replication List Entry Section 3

IANA This document describes a mechanism for IPv4 NAT traversal for LISP tunnel routers (xTR) and LISP Mobile Nodes (LISP-MN) behind a NAT device. A LISP device both detects the NAT and initializes its state. Forwarding to the LISP device through a NAT is enabled by the LISP Re-encapsulating Tunnel Router (RTR) network element, which acts as an anchor point in the data plane, forwarding traffic from unmodified LISP devices through the NAT. The LISP control plane offers the flexibility to support multiple overlay flavors simultaneously. This document specifies how LISP can be used to provide control-plane support to deploy a unified L2 and L3 overlay solution, as well as analyzing possible deployment options and models. This document describes a method to build and optimize inter-domain LISP router distribution trees for locator-based unicast and multicast replication of EID-sourced multicast packets. This memo describes an encapsulation method for carrying Ethernet and IEEE 802 media access control (MAC) frames within the Locator/ID Separation Protocol (LISP). This draft describes extending Virtual eXtensible Local Area Network (VXLAN), via changes to the VXLAN header, with three new capabilities: support for multi-protocol encapsulation, operations, administration and management (OAM) signaling and explicit versioning. Network virtualization involves the cooperation of devices with a wide variety of capabilities such as software and hardware tunnel endpoints, transit fabrics, and centralized control clusters. As a result of their role in tying together different elements in the system, the requirements on tunnels are influenced by all of these components. Flexibility is therefore the most important aspect of a tunnel protocol if it is to keep pace with the evolution of the system. This draft describes Geneve, a protocol designed to recognize and accommodate these changing capabilities and needs. This specification describes Generic UDP Encapsulation (GUE), which is a scheme for using UDP to encapsulate packets of different IP protocols for transport across layer 3 networks. By encapsulating packets in UDP, specialized capabilities in networking hardware for efficient handling of UDP packets can be leveraged. GUE specifies basic encapsulation methods upon which higher level constructs, such tunnels and overlay networks for network virtualization, can be constructed. GUE is extensible by allowing optional data fields as part of the encapsulation, and is generic in that it can encapsulate packets of various IP protocols. National Imagery and Mapping Agency

The authors would like to thank Vince Fuller, Gregg Schudel, Jesper Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for their technical and editorial commentary. The authors would like to thank Victor Moreno for discussions that led to the definition of the Multicast Info LCAF Type. The authors would like to thank Parantap Lahiri and Michael Kowal for discussions that led to the definition of the Explicit Locator Path (ELP) LCAF Type. The authors would like to thank Fabio Maino and Vina Ermagan for discussions that led to the definition of the Security Key LCAF Type. The authors would like to thank Albert Cabellos-Aparicio and Florin Coras for discussions that led to the definition of the Replication List Entry LCAF Type. Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for suggesting new LCAF Types. Thanks also goes to Terry Manderson for assistance obtaining a LISP AFI value from IANA. And finally, the authors thank Stephen Farrell (Security Area Director) and Deborah Brungard (Routing Area Director) for their suggested text to get the document through IESG review.