draft-ietf-lisp-lcaf-13.txt   draft-ietf-lisp-lcaf-14.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft lispers.net Internet-Draft lispers.net
Intended status: Experimental D. Meyer Intended status: Experimental D. Meyer
Expires: November 4, 2016 Brocade Expires: January 20, 2017 Brocade
J. Snijders J. Snijders
NTT Communications NTT Communications
May 3, 2016 July 19, 2016
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-13 draft-ietf-lisp-lcaf-14
Abstract Abstract
This draft defines a canonical address format encoding used in LISP This draft defines a canonical address format encoding used in LISP
control messages and in the encoding of lookup keys for the LISP control messages and in the encoding of lookup keys for the LISP
Mapping Database System. Mapping Database System.
Requirements Language
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 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 4, 2016. This Internet-Draft will expire on January 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. LISP Canonical Address Format Encodings . . . . . . . . . . . 4 3. LISP Canonical Address Format Encodings . . . . . . . . . . . 5
4. LISP Canonical Address Applications . . . . . . . . . . . . . 7 4. LISP Canonical Address Applications . . . . . . . . . . . . . 7
4.1. Segmentation using LISP . . . . . . . . . . . . . . . . . 7 4.1. Segmentation using LISP . . . . . . . . . . . . . . . . . 7
4.2. Carrying AS Numbers in the Mapping Database . . . . . . . 8 4.2. Carrying AS Numbers in the Mapping Database . . . . . . . 9
4.3. Assigning Geo Coordinates to Locator Addresses . . . . . 9 4.3. Assigning Geo Coordinates to Locator Addresses . . . . . 10
4.4. NAT Traversal Scenarios . . . . . . . . . . . . . . . . . 12 4.4. NAT Traversal Scenarios . . . . . . . . . . . . . . . . . 12
4.5. Multicast Group Membership Information . . . . . . . . . 14 4.5. Multicast Group Membership Information . . . . . . . . . 14
4.6. Traffic Engineering using Re-encapsulating Tunnels . . . 15 4.6. Traffic Engineering using Re-encapsulating Tunnels . . . 15
4.7. Storing Security Data in the Mapping Database . . . . . . 17 4.7. Storing Security Data in the Mapping Database . . . . . . 17
4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 18 4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 18
4.9. Replication List Entries for Multicast Forwarding . . . . 20 4.9. Replication List Entries for Multicast Forwarding . . . . 20
4.10. Applications for AFI List Type . . . . . . . . . . . . . 21 4.10. Applications for AFI List Type . . . . . . . . . . . . . 21
4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 21 4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 21
4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 22 4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 22
4.10.3. ASCII Names in the Mapping Database . . . . . . . . 23 4.10.3. ASCII Names in the Mapping Database . . . . . . . . 23
skipping to change at page 2, line 42 skipping to change at page 2, line 47
5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 30 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 30
5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 31 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 31
5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 32 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 32
6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1. Normative References . . . . . . . . . . . . . . . . . . 35 8.1. Normative References . . . . . . . . . . . . . . . . . . 35
8.2. Informative References . . . . . . . . . . . . . . . . . 36 8.2. Informative References . . . . . . . . . . . . . . . . . 36
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38
B.1. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 38 B.1. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 38
B.2. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 38 B.2. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 38
B.3. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 38 B.3. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 38
B.4. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 38 B.4. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 38
B.5. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 39 B.5. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 38
B.6. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 39 B.6. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 39
B.7. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 39 B.7. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 39
B.8. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 39 B.8. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 39
B.9. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 39 B.9. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 39
B.10. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 39 B.10. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 39
B.11. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 40 B.11. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 39
B.12. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 40 B.12. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 40
B.13. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 40 B.13. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 40
B.14. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 40 B.14. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 40
B.15. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the (RLOCs). To provide flexibility for current and future applications,
Internet. To provide flexibility for current and future these values can be encoded in LISP control messages using a general
applications, these values can be encoded in LISP control messages syntax that includes Address Family Identifier (AFI), length, and
using a general syntax that includes Address Family Identifier (AFI), value fields.
length, and value fields.
Currently defined AFIs include IPv4 and IPv6 addresses, which are Currently defined AFIs include IPv4 and IPv6 addresses, which are
formatted according to code-points assigned in [AFI] as follows: formatted according to code-points assigned in [AFI] as follows:
IPv4 Encoded Address: IPv4 Encoded Address:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... | | AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | | ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Encoded Address: IPv6 Encoded Address:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 2 | IPv6 Address ... | | AFI = 2 | IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... | | ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... | | ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... | | ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address | | ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document describes the currently-defined AFIs the LISP protocol This document describes the currently-defined AFIs the LISP protocol
uses along with their encodings and introduces the LISP Canonical uses along with their encodings and introduces the LISP Canonical
Address Format (LCAF) that can be used to define the LISP-specific Address Format (LCAF) that can be used to define the LISP-specific
encodings for arbitrary AFI values. encodings for arbitrary AFI values.
2. Definition of Terms 2. Definition of Terms
Address Family Identifier (AFI): a term used to describe an address Address Family Identifier (AFI): a term used to describe an address
encoding in a packet. An address family currently defined for encoding in a packet. There is an address family currently
IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details. The defined for IPv4 or IPv6 addresses. See [AFI] and [RFC3232] for
reserved AFI value of 0 is used in this specification to indicate details. The reserved AFI value of 0 is used in this
an unspecified encoded address where the the length of the address specification to indicate an unspecified encoded address where the
is 0 bytes following the 16-bit AFI value of 0. length of the address is 0 bytes following the 16-bit AFI value of
0.
Unspecified Address Format: Unspecified Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | <nothing follows AFI=0> | | AFI = 0 | <nothing follows AFI=0> |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value
used in the source and destination address fields of the first used in the source and destination address fields of the first
(most inner) LISP header of a packet. The host obtains a (most inner) LISP header of a packet. The host obtains a
destination EID the same way it obtains a destination address destination EID the same way it obtains a destination address
today, for example through a DNS lookup or SIP exchange. The today, for example through a DNS lookup or SIP exchange. The
source EID is obtained via existing mechanisms used to set a 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 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 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. located. An EID can be used by a host to refer to other hosts.
skipping to change at page 4, line 48 skipping to change at page 5, line 19
to a site at each point to which it attaches to the global to a site at each point to which it attaches to the global
Internet; where the topology is defined by the connectivity of Internet; where the topology is defined by the connectivity of
provider networks, RLOCs can be thought of as PA addresses. provider networks, RLOCs can be thought of as PA addresses.
Multiple RLOCs can be assigned to the same ETR device or to Multiple RLOCs can be assigned to the same ETR device or to
multiple ETR devices at a site. multiple ETR devices at a site.
3. LISP Canonical Address Format Encodings 3. LISP Canonical Address Format Encodings
IANA has assigned AFI value 16387 (0x4003) to the LISP architecture IANA has assigned AFI value 16387 (0x4003) to the LISP architecture
and protocols. This specification defines the encoding format of the and protocols. This specification defines the encoding format of the
LISP Canonical Address (LCA). This section defines both experimental LISP Canonical Address (LCA). This section defines all types for
types as well as types that reside in the registry that have which an initial allocation in the LISP-LCAF registry is requested.
corresponding working group drafts. See IANA Considerations section See IANA Considerations section for the complete list of such types.
for a list of types that will reside in the LISP-LCAF Registry.
The Address Family AFI definitions from [AFI] only allocate code- The Address Family AFI definitions from [AFI] only allocate code-
points for the AFI value itself. The length of the address or entity points for the AFI value itself. The length of the address or entity
that follows is not defined and is implied based on conventional that follows is not defined and is implied based on conventional
experience. Where the LISP protocol uses LISP Canonical Addresses experience. Where the LISP protocol uses LISP Canonical Addresses
specifically, the address length definitions will be in this specifically, the address length definitions will be in this
specification and take precedent over any other specification. specification and take precedent over any other specification.
The first 6 bytes of an LISP Canonical Address are followed by a The first 6 bytes of an LISP Canonical Address are followed by a
variable length of fields: variable number of fields of variable length:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Rsvd2 | Length | | Type | Rsvd2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Rsvd1: this 8-bit field is reserved for future use and MUST be Rsvd1: this 8-bit field is reserved for future use and MUST be
transmitted as 0 and ignored on receipt. transmitted as 0 and ignored on receipt.
Flags: this 8-bit field is for future definition and use. For now, Flags: this 8-bit field is for future definition and use. For now,
set to zero on transmission and ignored on receipt. set to zero on transmission and ignored on receipt.
Type: this 8-bit field is specific to the LISP Canonical Address Type: this 8-bit field is specific to the LISP Canonical Address
formatted encodings, values are: formatted encodings, currently allocated values are:
Type 0: Null Body Type Type 0: Null Body Type
Type 1: AFI List Type Type 1: AFI List Type
Type 2: Instance ID Type Type 2: Instance ID Type
Type 3: AS Number Type Type 3: AS Number Type
Type 4: Application Data Type Type 4: Application Data Type
Type 5: Geo Coordinates Type Type 5: Geo Coordinates Type
Type 6: Opaque Key Type Type 6: Opaque Key Type
skipping to change at page 6, line 33 skipping to change at page 7, line 4
include the AFI, Flags, Type, Reserved, and Length fields. When include the AFI, Flags, Type, Reserved, and Length fields. When
the AFI is not next to encoded address in a control message, then the AFI is not next to encoded address in a control message, then
the encoded address will have a minimum length of 6 bytes when the the encoded address will have a minimum length of 6 bytes when the
Length field is 0. The 6 bytes include the Flags, Type, Reserved, Length field is 0. The 6 bytes include the Flags, Type, Reserved,
and Length fields. and Length fields.
[RFC6830] states RLOC records are sorted when encoded in control [RFC6830] states RLOC records are sorted when encoded in control
messages so the locator-set has consistent order across all xTRs for 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- a given EID. The sort order is based on sort-key {afi, RLOC-
address}. When an RLOC is LCAF encoded, the sort-key is {afi, LCAF- address}. When an RLOC is LCAF encoded, the sort-key is {afi, LCAF-
Type, payload}. Therefore, when a locator-set has a mix of AFI Type}. Therefore, when a locator-set has a mix of AFI records and
records and LCAF records, all LCAF records will appear after all the LCAF records, all LCAF records will appear after all the AFI records.
AFI records.
4. LISP Canonical Address Applications 4. LISP Canonical Address Applications
4.1. Segmentation using LISP 4.1. Segmentation using LISP
When multiple organizations inside of a LISP site are using private When multiple organizations inside of a LISP site are using private
addresses [RFC1918] as EID-prefixes, their address spaces must remain addresses [RFC1918] as EID-prefixes, their address spaces must remain
segregated due to possible address duplication. An Instance ID in segregated due to possible address duplication. An Instance ID in
the address encoding can aid in making the entire AFI based address the address encoding can aid in making the entire AFI based address
unique. unique.
Another use for the Instance ID LISP Canonical Address Format is when Another use for the Instance ID LISP Canonical Address Format is when
creating multiple segmented VPNs inside of a LISP site where keeping creating multiple segmented VPNs inside of a LISP site where keeping
EID-prefix based subnets is desirable. EID-prefix based subnets is desirable.
Instance ID LISP Canonical Address Format: Instance ID LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 2 | IID mask-len | 4 + n | | Type = 2 | IID mask-len | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID | | Instance ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IID mask-len: if the AFI is set to 0, then this format is not IID mask-len: if the AFI is set to 0, then this format is not
encoding an extended EID-prefix but rather an instance-ID range encoding an extended EID-prefix but rather an instance-ID range
where the 'IID mask-len' indicates the number of high-order bits where the 'IID mask-len' indicates the number of high-order bits
used in the Instance ID field for the range. used in the Instance ID field for the range.
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
Instance ID field including the AFI field itself. Instance ID field including the AFI field itself.
Instance ID: the low-order 24-bits that can go into a LISP data Instance ID: the low-order 24-bits that can go into a LISP data
header when the I-bit is set. See [RFC6830] for details. The header when the I-bit is set. See [RFC6830] for details. The
reason for the length difference is so the maximum number of reason for the length difference is so that the maximum number of
instances supported per mapping system is 2^32 while conserving instances supported per mapping system is 2^32 while conserving
space in the LISP data header. This comes at the expense of 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 limiting the maximum number of instances per xTR to 2^24. If an
xTR is configured with multiple instance-IDs where the value in xTR is configured with multiple instance-IDs where the value in
the high-order 8 bits are the same, then the low-order 24 bits the high-order 8 bits are the same, then the low-order 24 bits
MUST be unique. MUST be unique.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
This LISP Canonical Address Type can be used to encode either EID or This LISP Canonical Address Type can be used to encode either EID or
RLOC addresses. RLOC addresses.
Usage: When used as a lookup key, the EID is regarded as a extended- Usage: When used as a lookup key, the EID is regarded as a extended-
EID in the mapping system. And this encoding is used in EID records EID in the mapping system. This encoding is used in EID records in
in Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages. Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages.
When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, When LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system
extended EIDs are used in Map-Referral messages. mechanism, extended EIDs are used in Map-Referral messages.
4.2. Carrying AS Numbers in the Mapping Database 4.2. Carrying AS Numbers in the Mapping Database
When an AS number is stored in the LISP Mapping Database System for When an AS number is stored in the LISP Mapping Database System for
either policy or documentation reasons, it can be encoded in a LISP either policy or documentation reasons, it can be encoded in a LISP
Canonical Address. Canonical Address.
AS Number LISP Canonical Address Format: AS Number LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 3 | Rsvd2 | 4 + n | | Type = 3 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AS Number | | AS Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
AS Number field including the AFI field itself. AS Number field including the AFI field itself.
AS Number: the 32-bit AS number of the autonomous system that has AS Number: the 32-bit AS number of the autonomous system that has
been assigned either the EID or RLOC that follows. been assigned either the EID or RLOC that follows.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
The AS Number Canonical Address Type can be used to encode either EID The AS Number Canonical Address Type can be used to encode either EID
or RLOC addresses. The former is used to describe the LISP-ALT AS 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 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 is used to describe the AS that is carrying RLOC based prefixes in
the underlying routing system. the underlying routing system.
Usage: This encoding can be used in EID or RLOC records in Map- Usage: This encoding can be used in EID or RLOC records in Map-
Requests, Map-Replies, Map-Registers, and Map-Notify messages. When Requests, Map-Replies, Map-Registers, and Map-Notify messages. When
LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism,
EIDs are used in Map-Referral messages. extended EIDs are used in Map-Referral messages.
4.3. Assigning Geo Coordinates to Locator Addresses 4.3. Assigning Geo Coordinates to Locator Addresses
If an ETR desires to send a Map-Reply describing the Geo Coordinates 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 Coordinate for each locator in its locator-set, it can use the Geo Coordinate
Type to convey physical location information. Type to convey physical location information.
Coordinates are specified using the WGS-84 (World Geodetic System) Coordinates are specified using the WGS-84 (World Geodetic System)
reference coordinate system [WGS-84]. reference coordinate system [WGS-84].
Geo Coordinate LISP Canonical Address Format: Geo Coordinate LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | 12 + n | | Type = 5 | Rsvd2 | 12 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds | |N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds | |E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude | | Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
8-byte Longitude and Latitude fields including the AFI field 8-byte Longitude and Latitude fields including the AFI field
itself. itself.
N: When set to 1 means North, otherwise South. N: When set to 1 means North, otherwise South.
Latitude Degrees: Valid values range from 0 to 90 degrees above or Latitude Degrees: Valid values range from 0 to 90 degrees above or
below the equator (northern or southern hemisphere, respectively). below the equator (northern or southern hemisphere, respectively).
skipping to change at page 11, line 9 skipping to change at page 11, line 18
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
The Geo Coordinates Canonical Address Type can be used to encode The Geo Coordinates Canonical Address Type can be used to encode
either EID or RLOC addresses. When used for EID encodings, you can either EID or RLOC addresses. When used for EID encodings, you can
determine the physical location of an EID along with the topological determine the physical location of an EID along with the topological
location by observing the locator-set. location by observing the locator-set.
Usage: This encoding can be used in EID or RLOC records in Map- Usage: This encoding can be used in EID or RLOC records in Map-
Requests, Map-Replies, Map-Registers, and Map-Notify messages. When Requests, Map-Replies, Map-Registers, and Map-Notify messages. When
LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism,
EIDs are used in Map-Referral messages. extended EIDs are used in Map-Referral messages.
4.4. NAT Traversal Scenarios 4.4. NAT Traversal Scenarios
When a LISP system is conveying global address and mapped port When a LISP system is conveying global address and mapped port
information when traversing through a NAT device, the NAT-Traversal information when traversing through a NAT device, the NAT-Traversal
LCAF Type is used. See [LISP-NATT] for details. LCAF Type is used. See [I-D.ermagan-lisp-nat-traversal] for details.
NAT-Traversal Canonical Address Format: NAT-Traversal Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 7 | Rsvd2 | 4 + n | | Type = 7 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MS UDP Port Number | ETR UDP Port Number | | MS UDP Port Number | ETR UDP Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Global ETR RLOC Address ... | | AFI = x | Global ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | MS RLOC Address ... | | AFI = x | MS RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Private ETR RLOC Address ... | | AFI = x | Private ETR RLOC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address 1 ... | | AFI = x | RTR RLOC Address 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR RLOC Address k ... | | AFI = x | RTR RLOC Address k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI addresses that follows Length value n: length in bytes of the AFI addresses that follows
the UDP Port Number field including the AFI fields themselves. the UDP Port Number field including the AFI fields themselves.
MS UDP Port Number: this is the UDP port number of the Map-Server MS UDP Port Number: this is the UDP port number of the Map-Server
and is set to 4342. and is set to 4342.
ETR UDP Port Number: this is the port number returned to a LISP ETR UDP Port Number: this is the port number returned to a LISP
system which was copied from the source port from a packet that system which was copied from the source port from a packet that
has flowed through a NAT device. has flowed through a NAT device.
skipping to change at page 13, line 12 skipping to change at page 13, line 12
MS RLOC Address: this is the address of the Map-Server used in the MS RLOC Address: this is the address of the Map-Server used in the
destination RLOC of a packet that has flowed through a NAT device. destination RLOC of a packet that has flowed through a NAT device.
Private ETR RLOC Address: this is an address known to be a private Private ETR RLOC Address: this is an address known to be a private
address inserted in this LCAF format by a LISP router that resides address inserted in this LCAF format by a LISP router that resides
on the private side of a NAT device. on the private side of a NAT device.
RTR RLOC Address: this is an encapsulation address used by an ITR or RTR RLOC Address: this is an encapsulation address used by an ITR or
PITR which resides behind a NAT device. This address is known to PITR which 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 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 NTR addresses ETR behind the NAT. There can be one or more NAT Tunnel Router
supplied in these set of fields. The number of NTRs encoded is (NTR) [I-D.ermagan-lisp-nat-traversal] addresses supplied in these
determined by the LCAF length field. When there are no NTRs set of fields. The number of NTRs encoded is determined by the
supplied, the NTR fields can be omitted and reflected by the LCAF LCAF length field. When there are no NTRs supplied, the NTR
length field or an AFI of 0 can be used to indicate zero NTRs fields can be omitted and reflected by the LCAF length field or an
encoded. AFI of 0 can be used to indicate zero NTRs encoded.
Usage: This encoding can be used in Info-Request and Info-Reply Usage: This encoding can be used in Info-Request and Info-Reply
messages. The mapping system does not store this information. The messages. The mapping system does not store this information. The
information is used by an xTR and Map-Server to convey private and information is used by an xTR and Map-Server to convey private and
public address information when traversing NAT and firewall devices. public address information when traversing NAT and firewall devices.
4.5. Multicast Group Membership Information 4.5. Multicast Group Membership Information
Multicast group information can be published in the mapping database Multicast group information can be published in the mapping database.
so a lookup on an EID based group address can return a replication So a lookup on an group address EID can return a replication list of
list of group addresses or a unicast addresses for single replication RLOC group addresses or RLOC unicast addresses. The intent of this
or multiple head-end replications. The intent of this type of type of unicast replication is to deliver packets to multiple ETRs at
unicast replication is to deliver packets to multiple ETRs at
receiver LISP multicast sites. The locator-set encoding for this EID 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 record type can be a list of ETRs when they each register with "Merge
Semantics". The encoding can be a typical AFI encoded locator Semantics". The encoding can be a typical AFI encoded locator
address. When an RTR list is being registered (with multiple levels address. When an RTR list is being registered (with multiple levels
according to [LISP-RE]), the Replication List Entry LCAF type is used according to [I-D.coras-lisp-re]), the Replication List Entry LCAF
for locator encoding. type is used for locator encoding.
This LCAF encoding can be used to send broadcast packets to all This LCAF encoding can be used to send broadcast packets to all
members of a subnet when each EIDs are away from their home subnet members of a subnet when each EIDs are away from their home subnet
location. location.
Multicast Info Canonical Address Format: Multicast Info Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 9 | Rsvd2 | 8 + n | | Type = 9 | Rsvd2 | 8 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance-ID | | Instance-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source MaskLen| Group MaskLen | | Reserved | Source MaskLen| Group MaskLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source/Subnet Address ... | | AFI = x | Source/Subnet Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Group Address ... | | AFI = x | Group Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Reserved: must be set to zero and ignore on receipt. Reserved: must be set to zero and ignore on receipt.
Instance ID: the low-order 24-bits that can go into a LISP data Instance ID: the low-order 24-bits that can go into a LISP data
header when the I-bit is set. See [RFC6830] for details. The use header when the I-bit is set. See [RFC6830] for details. The use
of the Instance-ID in this LCAF type is to associate a multicast of the Instance-ID in this LCAF type is to associate a multicast
forwarding entry for a given VPN. The instance-ID describes the forwarding entry for a given VPN. The instance-ID describes the
VPN and is registered to the mapping database system as a 3-tuple VPN and is registered to the mapping database system as a 3-tuple
skipping to change at page 15, line 13 skipping to change at page 15, line 13
Source MaskLen: the mask length of the source prefix that follows. Source MaskLen: the mask length of the source prefix that follows.
Group MaskLen: the mask length of the group prefix that follows. Group MaskLen: the mask length of the group prefix that follows.
AFI = x: x can be any AFI value from [AFI]. When a specific AFI has AFI = x: x can be any AFI value from [AFI]. When a specific AFI has
its own encoding of a multicast address, this field must be either its own encoding of a multicast address, this field must be either
a group address or a broadcast address. a group address or a broadcast address.
Usage: This encoding can be used in EID records in Map-Requests, Map- Usage: This encoding can be used in EID records in Map-Requests, Map-
Replies, Map-Registers, and Map-Notify messages. When LISP-DDT Replies, Map-Registers, and Map-Notify messages. When LISP-DDT
[LISP-DDT] is used as the mapping system mechanism, extended EIDs are [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended
used in Map-Referral messages. EIDs are used in Map-Referral messages.
4.6. Traffic Engineering using Re-encapsulating Tunnels 4.6. Traffic Engineering using Re-encapsulating Tunnels
For a given EID lookup into the mapping database, this LCAF format For a given EID lookup into the mapping database, this LCAF format
can be returned to provide a list of locators in an explicit re- can be returned to provide a list of locators in an explicit re-
encapsulation path. See [LISP-TE] for details. encapsulation path. See [I-D.farinacci-lisp-te] for details.
Explicit Locator Path (ELP) Canonical Address Format: Explicit Locator Path (ELP) Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 10 | Rsvd2 | n | | Type = 10 | Rsvd2 | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x | | Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop 1 ... | | Reencap Hop 1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 |L|P|S| AFI = x | | Rsvd3 |L|P|S| AFI = x |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reencap Hop k ... | | Reencap Hop k ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Lookup bit (L): this is the Lookup bit used to indicate to the user Lookup bit (L): this is the Lookup bit used to indicate to the user
of the ELP to not use this address for encapsulation but to look of the ELP to not use this address for encapsulation but to look
it up in the mapping database system to obtain an encapsulating it up in the mapping database system to obtain an encapsulating
RLOC address. RLOC address.
RLOC-Probe bit (P): this is the RLOC-probe bit which means the RLOC-Probe bit (P): this is the RLOC-probe bit which means the
Reencap Hop allows RLOC-probe messages to be sent to it. When 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 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 Hop is an anycast address then multiple physical Reencap Hops are
using the same RLOC address. In this case, RLOC-probes are not using the same RLOC address. In this case, RLOC-probes are not
needed because when the closest RLOC address is not reachable needed because when the closest RLOC address is not reachable
another RLOC address can reachable. another RLOC address can be reachable.
Strict bit (S): this the strict bit which means the associated Strict bit (S): this is the strict bit which means the associated
Rencap Hop is required to be used. If this bit is 0, the Rencap Hop is required to be used. If this bit is 0, the
reencapsulator can skip this Reencap Hop and go to the next one in reencapsulator can skip this Reencap Hop and go to the next one in
the list. the list.
AFI = x: x can be any AFI value from [AFI]. When a specific AFI has AFI = x: x can be any AFI value from [AFI]. When a specific AFI has
its own encoding of a multicast address, this field must be either its own encoding of a multicast address, this field must be either
a group address or a broadcast address. a group address or a broadcast address.
Usage: This encoding can be used in RLOC records in Map-Requests, Usage: This encoding can be used in RLOC records in Map-Requests,
Map-Replies, Map-Registers, and Map-Notify messages. This encoding Map-Replies, Map-Registers, and Map-Notify messages. This encoding
not need to be understood by the mapping system for mapping database does not need to be understood by the mapping system for mapping
lookups since this LCAF type is not a lookup key. database lookups since this LCAF type is not a lookup key.
4.7. Storing Security Data in the Mapping Database 4.7. Storing Security Data in the Mapping Database
When a locator in a locator-set has a security key associated with When a locator in a locator-set has a security key associated with
it, this LCAF format will be used to encode key material. See it, this LCAF format will be used to encode key material. See
[LISP-DDT] for details. [I-D.ietf-lisp-ddt] for details.
Security Key Canonical Address Format: Security Key Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 11 | Rsvd2 | 6 + n | | Type = 11 | Rsvd2 | 6 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R| | Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Length | Key Material ... | | Key Length | Key Material ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Key Material | | ... Key Material |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Locator Address ... | | AFI = x | Locator Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that start with the Key Length value n: length in bytes of fields that start with the Key
Material field. Material field.
Key Count: the Key Count field declares the number of Key sections Key Count: the Key Count field declares the number of Key sections
included in this LCAF. included in this LCAF.
Key Algorithm: the Algorithm field identifies the key's Key Algorithm: the Algorithm field identifies the key's
cryptographic algorithm and specifies the format of the Public Key cryptographic algorithm and specifies the format of the Public Key
field. field.
skipping to change at page 18, line 7 skipping to change at page 18, line 7
Key Material: the Key Material field stores the key material. The Key Material: the Key Material field stores the key material. The
format of the key material stored depends on the Key Algorithm format of the key material stored depends on the Key Algorithm
field. field.
AFI = x: x can be any AFI value from [AFI].This is the locator AFI = x: x can be any AFI value from [AFI].This is the locator
address that owns the encoded security key. address that owns the encoded security key.
Usage: This encoding can be used in EID or RLOC records in Map- Usage: This encoding can be used in EID or RLOC records in Map-
Requests, Map-Replies, Map-Registers, and Map-Notify messages. When Requests, Map-Replies, Map-Registers, and Map-Notify messages. When
LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism,
EIDs are used in Map-Referral messages. extended EIDs are used in Map-Referral messages.
4.8. Source/Destination 2-Tuple Lookups 4.8. Source/Destination 2-Tuple Lookups
When both a source and destination address of a flow needs When both a source and destination address of a flow needs
consideration for different locator-sets, this 2-tuple key is used in consideration for different locator-sets, this 2-tuple key is used in
EID fields in LISP control messages. When the Source/Dest key is EID fields in LISP control messages. When the Source/Dest key is
registered to the mapping database, it can be encoded as a source- 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 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 for a mapping database lookup the source and destination come from a
data packet. data packet.
Source/Dest Key Canonical Address Format: Source/Dest Key Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 12 | Rsvd2 | 4 + n | | Type = 12 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Source-ML | Dest-ML | | Reserved | Source-ML | Dest-ML |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Source-Prefix ... | | AFI = x | Source-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Destination-Prefix ... | | AFI = x | Destination-Prefix ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Reserved: must be set to zero and ignore on receipt. Reserved: must be set to zero and ignore on receipt.
Source-ML: the mask length of the source prefix that follows. Source-ML: the mask length of the source prefix that follows.
Dest-ML: the mask length of the destination prefix that follows. Dest-ML: the mask length of the destination prefix that follows.
AFI = x: x can be any AFI value from [AFI]. When a specific AFI has AFI = x: x can be any AFI value from [AFI]. When a specific AFI has
its own encoding of a multicast address, this field must be either its own encoding of a multicast address, this field must be either
a group address or a broadcast address. a group address or a broadcast address.
Refer to [LISP-TE] for usage details.
Usage: This encoding can be used in EID records in Map-Requests, Map- Usage: This encoding can be used in EID records in Map-Requests, Map-
Replies, Map-Registers, and Map-Notify messages. When LISP-DDT Replies, Map-Registers, and Map-Notify messages. When LISP-DDT
[LISP-DDT] is used as the mapping system mechanism, extended EIDs are [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended
used in Map-Referral messages. EIDs are used in Map-Referral messages. Refer to
[I-D.farinacci-lisp-te] for usage details of this LCAF type.
4.9. Replication List Entries for Multicast Forwarding 4.9. Replication List Entries for Multicast Forwarding
The Replication List Entry LCAF type is an encoding for a locator The Replication List Entry LCAF type is an encoding for a locator
being used for unicast replication according to the specification in being used for unicast replication according to the specification in
[LISP-RE]. This locator encoding is pointed to by a Multicast Info [I-D.coras-lisp-re]. This locator encoding is pointed to by a
LCAF Type and is registered by Re-encapsulating Tunnel Routers (RTRs) Multicast Info LCAF Type and is registered by Re-encapsulating Tunnel
that are participating in an overlay distribution tree. Each RTR Routers (RTRs) that are participating in an overlay distribution
will register its locator address and its configured level in the tree. Each RTR will register its locator address and its configured
distribution tree. level in the distribution tree.
Replication List Entry Address Format: Replication List Entry Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 13 | Rsvd2 | 4 + n | | Type = 13 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value | | Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #1 ... | | AFI = x | RTR/ETR #1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rsvd3 | Rsvd4 | Level Value | | Rsvd3 | Rsvd4 | Level Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | RTR/ETR #n ... | | AFI = x | RTR/ETR #n ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Rsvd{1,2,3,4}: must be set to zero and ignore on receipt. Rsvd{1,2,3,4}: must be set to zero and ignore on receipt.
Level Value: this value is associated with the level within the Level Value: this value is associated with the level within the
overlay distribution tree hierarchy where the RTR resides. The overlay distribution tree hierarchy where the RTR resides. The
level numbers are ordered from lowest value being close to the ITR level numbers are ordered from lowest value being close to the ITR
(meaning that ITRs replicate to level-0 RTRs) and higher levels (meaning that ITRs replicate to level-0 RTRs) and higher levels
are further downstream on the distribution tree closer to ETRs of are further downstream on the distribution tree closer to ETRs of
multicast receiver sites. multicast receiver sites.
AFI = x: x can be any AFI value from [AFI]. A specific AFI has its AFI = x: x can be any AFI value from [AFI]. A specific AFI has its
own encoding of either a unicast or multicast locator address. own encoding of either a unicast or multicast locator address.
All RTR/ETR entries for the same level should be combined together For efficiency reasons, all RTR/ETR entries for the same level
by a Map-Server to avoid searching through the entire multi-level should be combined together by a Map-Server to avoid searching
list of locator entries in a Map-Reply message. through the entire multi-level list of locator entries in a Map-
Reply message.
Usage: This encoding can be used in RLOC records in Map-Requests, Usage: This encoding can be used in RLOC records in Map-Requests,
Map-Replies, Map-Registers, and Map-Notify messages. Map-Replies, Map-Registers, and Map-Notify messages.
4.10. Applications for AFI List Type 4.10. Applications for AFI List Type
4.10.1. Binding IPv4 and IPv6 Addresses 4.10.1. Binding IPv4 and IPv6 Addresses
When header translation between IPv4 and IPv6 is desirable a LISP When header translation between IPv4 and IPv6 is desirable a LISP
Canonical Address can use the AFI List Type to carry multiple AFIs in Canonical Address can use the AFI List Type to carry multiple AFIs in
one LCAF AFI. one LCAF AFI.
Address Binding LISP Canonical Address Format: Address Binding LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | 2 + 4 + 2 + 16 | | Type = 1 | Rsvd2 | 2 + 4 + 2 + 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... | | AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | AFI = 2 | | ... IPv4 Address | AFI = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address ... | | IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... | | ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address ... | | ... IPv6 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv6 Address | | ... IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 24 when IPv4 and IPv6 AFI Length: length in bytes is fixed at 24 when IPv4 and IPv6 AFI
encoded addresses are used. encoded addresses are used.
This type of address format can be included in a Map-Request when the This type of address format can be included in a Map-Request when the
address is being used as an EID, but the Mapping Database System address is being used as an EID, but the Mapping Database System
lookup destination can use only the IPv4 address. This is so a lookup destination can use only the IPv4 address. This is so a
Mapping Database Service Transport System, such as LISP-ALT Mapping Database Service Transport System, such as LISP-ALT
[RFC6836], can use the Map-Request destination address to route the [RFC6836], can use the Map-Request destination address to route the
control message to the desired LISP site. control message to the desired LISP site.
skipping to change at page 22, line 12 skipping to change at page 22, line 12
Requests, Map-Replies, Map-Registers, and Map-Notify messages. See Requests, Map-Replies, Map-Registers, and Map-Notify messages. See
subsections in this section for specific use cases. subsections in this section for specific use cases.
4.10.2. Layer-2 VPNs 4.10.2. Layer-2 VPNs
When MAC addresses are stored in the LISP Mapping Database System, When MAC addresses are stored in the LISP Mapping Database System,
the AFI List Type can be used to carry AFI 6. the AFI List Type can be used to carry AFI 6.
MAC Address LISP Canonical Address Format: MAC Address LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | 2 + 6 | | Type = 1 | Rsvd2 | 2 + 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 6 | Layer-2 MAC Address ... | | AFI = 6 | Layer-2 MAC Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Layer-2 MAC Address | | ... Layer-2 MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 8 when MAC address AFI encoded Length: length in bytes is fixed at 8 when MAC address AFI encoded
addresses are used. addresses are used.
This address format can be used to connect layer-2 domains together 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. 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 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 RLOCs, or locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or
even another MAC address being used as an RLOC. even another MAC address being used as an RLOC. See
[I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when
doing EID mobility.
4.10.3. ASCII Names in the Mapping Database 4.10.3. ASCII Names in the Mapping Database
If DNS names or URIs are stored in the LISP Mapping Database System, If DNS names or URIs are stored in the LISP Mapping Database System,
the AFI List Type can be used to carry an ASCII string where it is the AFI List Type can be used to carry an ASCII string where it is
delimited by length 'n' of the LCAF Length encoding. delimited by length 'n' of the LCAF Length encoding.
ASCII LISP Canonical Address Format: ASCII LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | 2 + n | | Type = 1 | Rsvd2 | 2 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 17 | DNS Name or URI ... | | AFI = 17 | DNS Name or URI ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes AFI=17 field and the null-terminated Length value n: length in bytes AFI=17 field and the null-terminated
ASCII string (the last byte of 0 is included). ASCII string (the last byte of 0 is included).
4.10.4. Using Recursive LISP Canonical Address Encodings 4.10.4. Using Recursive LISP Canonical Address Encodings
When any combination of above is desirable, the AFI List Type value When any combination of above is desirable, the AFI List Type value
can be used to carry within the LCAF AFI another LCAF AFI. can be used to carry within the LCAF AFI another LCAF AFI (for
example, Application Specific Data see Section 5.1.
Recursive LISP Canonical Address Format: Recursive LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | 8 + 18 | | Type = 1 | Rsvd2 | 8 + 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | 12 + 6 | | Type = 4 | Rsvd2 | 12 + 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 QQS or Flow Label | Protocol | | IP TOS, IPv6 QQS or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) | | Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) | | Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 1 | IPv4 Address ... | | AFI = 1 | IPv4 Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... IPv4 Address | | ... IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes is fixed at 18 when an AFI=1 IPv4 address is Length: length in bytes is fixed at 18 when an AFI=1 IPv4 address is
included. included.
This format could be used by a Mapping Database Transport System, This format could be used by a Mapping Database Transport System,
such as LISP-ALT [RFC6836], where the AFI=1 IPv4 address is used as such as LISP-ALT [RFC6836], where the AFI=1 IPv4 address is used as
an EID and placed in the Map-Request destination address by the an EID and placed in the Map-Request destination address by the
sending LISP system. The ALT system can deliver the Map-Request to sending LISP system. The ALT system can deliver the Map-Request to
the LISP destination site independent of the Application Data Type the LISP destination site independent of the Application Data Type
AFI payload values. When this AFI is processed by the destination AFI payload values. When this AFI is processed by the destination
skipping to change at page 25, line 16 skipping to change at page 25, line 16
A LISP system should use the AFI List Type format when sending to A LISP system should use the AFI List Type format when sending to
LISP systems that do not support a particular LCAF Type used to LISP systems that do not support a particular LCAF Type used to
encode locators. This allows the receiving system to be able to encode locators. This allows the receiving system to be able to
parse a locator address for encapsulation purposes. The list of AFIs parse a locator address for encapsulation purposes. The list of AFIs
in an AFI List LCAF Type has no semantic ordering and a receiver in an AFI List LCAF Type has no semantic ordering and a receiver
should parse each AFI element no matter what the ordering. should parse each AFI element no matter what the ordering.
Compatibility Mode Address Format: Compatibility Mode Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Rsvd2 | 8 + 14 + 6 | | Type = 1 | Rsvd2 | 8 + 14 + 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | 12 + 2 | | Type = 5 | Rsvd2 | 12 + 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N| Latitude Degrees | Minutes | Seconds | |N| Latitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Longitude Degrees | Minutes | Seconds | |E| Longitude Degrees | Minutes | Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude | | Altitude |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 0 | AFI = 1 | | AFI = 0 | AFI = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If a system does not recognized the Geo Coordinate LCAF Type that is If a system does not recognized the Geo Coordinate LCAF Type that is
accompanying a locator address, an encoder can include the Geo accompanying a locator address, an encoder can include the Geo
Coordinate LCAF Type embedded in a AFI List LCAF Type where the AFI Coordinate LCAF Type embedded in a AFI List LCAF Type where the AFI
in the Geo Coordinate LCAF is set to 0 and the AFI encoded next in in the Geo Coordinate LCAF is set to 0 and the AFI encoded next in
the list is encoded with a valid AFI value to identify the locator the list is encoded with a valid AFI value to identify the locator
address. address.
A LISP system is required to support the AFI List LCAF Type to use 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 Coordinate this procedure. It would skip over 10 bytes of the Geo Coordinate
skipping to change at page 26, line 15 skipping to change at page 26, line 15
5. Experimental LISP Canonical Address Applications 5. Experimental LISP Canonical Address Applications
5.1. Convey Application Specific Data 5.1. Convey Application Specific Data
When a locator-set needs to be conveyed based on the type of 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 or the Per-Hop Behavior (PHB) of a packet, the
Application Data Type can be used. Application Data Type can be used.
Application Data LISP Canonical Address Format: Application Data LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | 12 + n | | Type = 4 | Rsvd2 | 12 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 TC, or Flow Label | Protocol | | IP TOS, IPv6 TC, or Flow Label | Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Port (lower-range) | Local Port (upper-range) | | Local Port (lower-range) | Local Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote Port (lower-range) | Remote Port (upper-range) | | Remote Port (lower-range) | Remote Port (upper-range) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
8-byte Application Data fields including the AFI field itself. 8-byte Application Data fields including the AFI field itself.
IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS
field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow
Label used in an IPv6 header. Label used in an IPv6 header.
Local Port/Remote Port Ranges: these fields are from the TCP, UDP, Local Port/Remote Port Ranges: these fields are from the TCP, UDP,
or SCTP transport header. A range can be specified by using a or SCTP transport header. A range can be specified by using a
skipping to change at page 26, line 52 skipping to change at page 26, line 52
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
The Application Data Canonical Address Type is used for an EID The Application Data Canonical Address Type is used for an EID
encoding when an ITR wants a locator-set for a specific application. 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 When used for an RLOC encoding, the ETR is supplying a locator-set
for each specific application is has been configured to advertise. for each specific application is has been configured to advertise.
Usage: This encoding can be used in EID records in Map-Requests, Map- Usage: This encoding can be used in EID records in Map-Requests, Map-
Replies, Map-Registers, and Map-Notify messages. When LISP-DDT Replies, Map-Registers, and Map-Notify messages. When LISP-DDT
[LISP-DDT] is used as the mapping system mechanism, extended EIDs are [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended
used in Map-Referral messages. This LCAF type is used as a lookup EIDs are used in Map-Referral messages. This LCAF type is used as a
key to the mapping system that can return a longest-match or exact- lookup key to the mapping system that can return a longest-match or
match entry. exact-match entry.
5.2. Generic Database Mapping Lookups 5.2. Generic Database Mapping Lookups
When the LISP Mapping Database system holds information accessed by a When the LISP Mapping Database system holds information accessed by a
generic formatted key (where the key is not the usual IPv4 or IPv6 generic formatted key (where the key is not the usual IPv4 or IPv6
address), an opaque key may be desirable. address), an opaque key may be desirable.
Opaque Key LISP Canonical Address Format: Opaque Key LISP Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 6 | Rsvd2 | 3 + n | | Type = 6 | Rsvd2 | 3 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Key Field Num | Key Wildcard Fields | Key . . . | | Key Field Num | Key Wildcard Fields | Key . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . Key | | . . . Key |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the type's payload. The value n Length value n: length in bytes of the type's payload. The value n
is the number of bytes that follow this Length field. is the number of bytes that follow this Length field.
Key Field Num: the number of fields (minus 1) the key can be broken Key Field Num: the number of fields (minus 1) the key can be broken
up into. The width of the fields are fixed length. So for a key up into. The width of the fields are fixed length. So for a key
size of 8 bytes, with a Key Field Num of 4 allows 4 fields of 2 size of 8 bytes, with a Key Field Num of 4 allows 4 fields of 2
bytes in length. Valid values for this field range from 0 to 15 bytes in length. Allowing for a reasonable number of 16 field
supporting a maximum of 16 field separations. separators, valid values range from 0 to 15.
Key Wildcard Fields: describes which fields in the key are not used Key Wildcard Fields: describes which fields in the key are not used
as part of the key lookup. This wildcard encoding is a bitfield. 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. 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 Bit 0 (the low-order bit) in this bitfield corresponds the first
field, right-justified in the key, bit 1 the second field, and so field, right-justified 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 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 should not be considered as part of the database lookup. When the
entire 16-bits is set to 0, then all bits of the key are used for entire 16-bits is set to 0, then all bits of the key are used for
the database lookup. the database lookup.
skipping to change at page 29, line 14 skipping to change at page 29, line 14
5.3. PETR Admission Control Functionality 5.3. PETR Admission Control Functionality
When a public PETR device wants to verify who is encapsulating to it, When a public PETR device wants to verify who is encapsulating to it,
it can check for a specific nonce value in the LISP encapsulated it can check for a specific nonce value in the LISP encapsulated
packet. To convey the nonce to admitted ITRs or PITRs, this LCAF packet. To convey the nonce to admitted ITRs or PITRs, this LCAF
format is used in a Map-Register or Map-Reply locator-record. format is used in a Map-Register or Map-Reply locator-record.
Nonce Locator Canonical Address Format: Nonce Locator Canonical Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 8 | Rsvd2 | 4 + n | | Type = 8 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Nonce | | Reserved | Nonce |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
Nonce field including the AFI field itself. Nonce field including the AFI field itself.
Reserved: must be set to zero and ignore on receipt. Reserved: must be set to zero and ignore on receipt.
Nonce: this is a nonce value returned by an ETR in a Map-Reply Nonce: this is a nonce value returned by an ETR in a Map-Reply
locator-record to be used by an ITR or PITR when encapsulating to 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. 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.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
Usage: This is an experimental type where the usage has not been Usage: This is an experimental type where the usage has not been
defined yet. defined yet.
5.4. Data Model Encoding 5.4. Data Model Encoding
This type allows a JSON data model to be encoded either as an EID or This type allows a JSON data model to be encoded either as an EID or
RLOC. RLOC.
JSON Data Model Type Address Format: JSON Data Model Type Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 14 | Rsvd2 |B| 2 + n | | Type = 14 | Rsvd2 |B| 2 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JSON length | JSON binary/text encoding ... | | JSON length | JSON binary/text encoding ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Optional Address ... | | AFI = x | Optional Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Rsvd{1,2}: must be set to zero and ignore on receipt. Rsvd{1,2}: must be set to zero and ignore on receipt.
B bit: indicates that the JSON field is binary encoded according to B bit: indicates that the JSON field is binary encoded according to
[JSON-BINARY] when the bit is set to 1. Otherwise the encoding is [JSON-BINARY] when the bit is set to 1. Otherwise the encoding is
based on text encoding according to [RFC4627]. based on text encoding according to [RFC7159].
JSON length: length in octets of the following 'JSON binary/text JSON length: length in octets of the following 'JSON binary/text
encoding' field. encoding' field.
JSON binary/text encoding field: a variable length field that JSON binary/text encoding field: a variable length field that
contains either binary or text encodings. contains either binary or text encodings.
AFI = x: x can be any AFI value from [AFI]. A specific AFI has its AFI = x: x can be any AFI value from [AFI]. A specific AFI has its
own encoding of either a unicast or multicast locator address. own encoding of either a unicast or multicast locator address.
All RTR/ETR entries for the same level should be combined together All RTR/ETR entries for the same level should be combined together
skipping to change at page 31, line 17 skipping to change at page 31, line 17
The Key/Value pair is for example useful for attaching attributes to The Key/Value pair is for example useful for attaching attributes to
other elements of LISP packets, such as EIDs or RLOCs. When other elements of LISP packets, such as EIDs or RLOCs. When
attaching attributes to EIDs or RLOCs, it's necessary to distinguish 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 between the element that should be used as EID or RLOC, and hence as
key for lookups, and additional attributes. This is especially the key for lookups, and additional attributes. This is especially the
case when the difference cannot be determined from the types of the case when the difference cannot be determined from the types of the
elements, such as when two IP addresses are being used. elements, such as when two IP addresses are being used.
Key/Value Pair Address Format: Key/Value Pair Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 15 | Rsvd2 | n | | Type = 15 | Rsvd2 | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address as Key ... | | AFI = x | Address as Key ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address as Value ... | | AFI = x | Address as Value ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length value n: length in bytes of fields that follow.
Rsvd{1,2}: must be set to zero and ignore on receipt. Rsvd{1,2}: must be set to zero and ignore on receipt.
AFI = x: x can be any AFI value from [AFI]. A specific AFI has its AFI = x: x can be any AFI value from [AFI]. A specific AFI has its
own encoding of either a unicast or multicast locator address. own encoding of either a unicast or multicast locator address.
All RTR/ETR entries for the same level should be combined together All RTR/ETR entries for the same level should be combined together
by a Map-Server to avoid searching through the entire multi-level by a Map-Server to avoid searching through the entire multi-level
list of locator entries in a Map-Reply message. list of locator entries in a Map-Reply message.
skipping to change at page 32, line 19 skipping to change at page 32, line 19
LISP mapping system can hold many types of address formats, it can LISP mapping system can hold many types of address formats, it can
represent the encapsulation format supported by an RLOC as well. represent the encapsulation format supported by an RLOC as well.
When an encapsulator receives a Map-Reply with an Encapsulation When an encapsulator receives a Map-Reply with an Encapsulation
Format LCAF Type encoded in an RLOC-record, it can select an Format LCAF Type encoded in an RLOC-record, it can select an
encapsulation format, that it can support, from any of the encapsulation format, that it can support, from any of the
encapsulation protocols which have the bit set to 1 in this LCAF encapsulation protocols which have the bit set to 1 in this LCAF
type. type.
Encapsulation Format Address Format: Encapsulation Format Address Format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 16 | Rsvd2 | 4 + n | | Type = 16 | Rsvd2 | 4 + n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L| | Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Rsvd1/Rsvd2: must be set to zero and ignored on receipt. Rsvd1/Rsvd2: must be set to zero and ignored on receipt.
Length value n: length in bytes of the AFI address that follows the Length value n: length in bytes of the AFI address that follows the
next 32-bits including the AFI field itself. next 32-bits including the AFI field itself.
Reserved-for-Future-Encapsulations: must be set to zero and ignored Reserved-for-Future-Encapsulations: must be set to zero and ignored
on receipt. This field will get bits allocated to future on receipt. This field will get bits allocated to future
encapsulations, as they are created. encapsulations, as they are created.
L: The RLOCs listed in the AFI encoded addresses in the next longword L: The RLOCs listed in the AFI encoded addresses in the next longword
can accept layer3 LISP encapsulation using destination UDP port can accept layer3 LISP encapsulation using destination UDP port
4341 [RFC6830]. 4341 [RFC6830].
l: The RLOCs listed in the AFI encoded addresses in the next longword l: The RLOCs listed in the AFI encoded addresses in the next longword
can accept layer2 LISP encapsulation using destination UDP port can accept layer2 LISP encapsulation using destination UDP port
8472 [L2-LISP]. 8472 [I-D.smith-lisp-layer2].
V: The RLOCs listed in the AFI encoded addresses in the next longword V: The RLOCs listed in the AFI encoded addresses in the next longword
can accept VXLAN encapsulation using destination UDP port 4789 can accept VXLAN encapsulation using destination UDP port 4789
[RFC7348]. [RFC7348].
v: The RLOCs listed in the AFI encoded addresses in the next longword v: The RLOCs listed in the AFI encoded addresses in the next longword
can accept VXLAN-GPE encapsulation using destination UDP port 4790 can accept VXLAN-GPE encapsulation using destination UDP port 4790
[GPE]. [I-D.quinn-vxlan-gpe].
N: The RLOCs listed in the AFI encoded addresses in the next longword N: The RLOCs listed in the AFI encoded addresses in the next longword
can accept NV-GRE encapsulation using IPv4/ IPv6 protocol number can accept NV-GRE encapsulation using IPv4/ IPv6 protocol number
47 [NVGRE]. 47 [RFC7637].
G: The RLOCs listed in the AFI encoded addresses in the next longword G: The RLOCs listed in the AFI encoded addresses in the next longword
can accept GENEVE encapsulation using destination UDP port 6081 can accept GENEVE encapsulation using destination UDP port 6081
[GENEVE]. [I-D.gross-geneve].
U: The RLOCs listed in the AFI encoded addresses in the next longword U: The RLOCs listed in the AFI encoded addresses in the next longword
can accept GUE encapsulation using destination UDP port TBD [GUE]. can accept GUE encapsulation using destination UDP port TBD
[I-D.herbert-gue].
Usage: This encoding can be used in RLOC records in Map-Requests, Usage: This encoding can be used in RLOC records in Map-Requests,
Map-Replies, Map-Registers, and Map-Notify messages. Map-Replies, Map-Registers, and Map-Notify messages.
6. Security Considerations 6. Security Considerations
There are no security considerations for this specification. The There are no security considerations for this specification. The
security considerations are documented for the protocols that use security considerations are documented for the protocols that use
LISP Canonical Addressing. Refer to the those relevant LISP Canonical Addressing.
specifications.
The use of the Geo-Coordinates LCAF Type may raise physical privacy The use of the Geo-Coordinates LCAF Type may raise physical privacy
issues. It can be up to the mapping system, based on policy issues. Care should be taken when configuring the mapping system to
parameters, when this LCAF type is returned to a Map-Requester. use specific policy parameters so geo-location information is not
returned gratutiosly.
7. IANA Considerations 7. IANA Considerations
This document defines a canonical address format encoding used in This document defines a canonical address format encoding used in
LISP control messages and in the encoding of lookup keys for the LISP LISP control messages and in the encoding of lookup keys for the LISP
Mapping Database System. Such address format is based on a fixed AFI Mapping Database System. Such address format is based on a fixed AFI
(16387) and a LISP LCAF Type field. (16387) and a LISP LCAF Type field.
The LISP LCAF Type field is an 8-bit field specific to the LISP The LISP LCAF Type field is an 8-bit field specific to the LISP
Canonical Address formatted encodings, for which IANA is to create Canonical Address formatted encodings, for which IANA is to create
and maintain a new registry (as outlined in [RFC5226]) entitled "LISP and maintain a new registry (as outlined in [RFC5226]) entitled "LISP
LCAF Type". Initial values for the LISP LCAF Type registry are given LCAF Type". Initial values for the LISP LCAF Type registry are given
below. Future assignments are to be made through expert review with below. Future assignments are to be made through expert review with
a specification required publication. Assignments consist of a LISP a specification required publication. Assignments consist of a LISP
LCAF Type name and its associated value: LCAF Type name and its associated value:
+-------+------------------------------+------------+ +-------+------------------------------+------------+
| Value | LISP LCAF Type Name | Definition | | Value | LISP LCAF Type Name | Definition |
+-------+------------------------------+------------+ +-------+------------------------------+------------+
| 0 | Null Body Type | Section 3 | | 0 | Null Body Type | Section 3 |
| | | |
| 1 | AFI List Type | Section 3 | | 1 | AFI List Type | Section 3 |
| | | |
| 2 | Instance ID Type | Section 3 | | 2 | Instance ID Type | Section 3 |
| | | |
| 3 | AS Number Type | Section 3 | | 3 | AS Number Type | Section 3 |
| | | |
| 5 | Geo Coordinates Type | Section 3 | | 5 | Geo Coordinates Type | Section 3 |
| | | |
| 7 | NAT-Traversal Type | Section 3 | | 7 | NAT-Traversal Type | Section 3 |
| | | |
| 9 | Multicast Info Type | Section 3 | | 9 | Multicast Info Type | Section 3 |
| | | |
| 10 | Explicit Locator Path Type | Section 3 | | 10 | Explicit Locator Path Type | Section 3 |
| | | |
| 11 | Security Key Type | Section 3 | | 11 | Security Key Type | Section 3 |
| | | |
| 12 | Source/Dest Key Type | Section 3 | | 12 | Source/Dest Key Type | Section 3 |
| | | |
| 13 | Replication List Entry Type | Section 3 | | 13 | Replication List Entry Type | Section 3 |
+-------+------------------------------+------------+ +-------+------------------------------+------------+
Table 1: LISP LCAF Type Initial Values Table 1: LISP LCAF Type Initial Values
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700,
DOI 10.17487/RFC1700, October 1994,
<http://www.rfc-editor.org/info/rfc1700>.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
<http://www.rfc-editor.org/info/rfc1918>. <http://www.rfc-editor.org/info/rfc1918>.
[RFC4627] Crockford, D., "The application/json Media Type for [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
JavaScript Object Notation (JSON)", RFC 4627, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC4627, July 2006, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc4627>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced
by an On-line Database", RFC 3232, DOI 10.17487/RFC3232,
January 2002, <http://www.rfc-editor.org/info/rfc3232>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830, Locator/ID Separation Protocol (LISP)", RFC 6830,
DOI 10.17487/RFC6830, January 2013, DOI 10.17487/RFC6830, January 2013,
<http://www.rfc-editor.org/info/rfc6830>. <http://www.rfc-editor.org/info/rfc6830>.
[RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol Alternative Logical "Locator/ID Separation Protocol Alternative Logical
Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836,
January 2013, <http://www.rfc-editor.org/info/rfc6836>. January 2013, <http://www.rfc-editor.org/info/rfc6836>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
L., Sridhar, T., Bursell, M., and C. Wright, "Virtual L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
eXtensible Local Area Network (VXLAN): A Framework for eXtensible Local Area Network (VXLAN): A Framework for
Overlaying Virtualized Layer 2 Networks over Layer 3 Overlaying Virtualized Layer 2 Networks over Layer 3
Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
<http://www.rfc-editor.org/info/rfc7348>. <http://www.rfc-editor.org/info/rfc7348>.
[RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network
Virtualization Using Generic Routing Encapsulation",
RFC 7637, DOI 10.17487/RFC7637, September 2015,
<http://www.rfc-editor.org/info/rfc7637>.
8.2. Informative References 8.2. Informative References
[AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY [AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY
NUMBERS http://www.iana.org/numbers.html, Febuary 2007. NUMBERS http://www.iana.org/numbers.html, Febuary 2007.
[GENEVE] Gross, J., Sridhar, T., Garg, P., Wright, C., Ganga, I., [I-D.coras-lisp-re]
Agarwal, P., Duda, K., Dutt, D., and J. Hudson, "Geneve: Coras, F., Cabellos-Aparicio, A., Domingo-Pascual, J.,
Generic Network Virtualization Encapsulation", draft- Maino, F., and D. Farinacci, "LISP Replication
gross-geneve-02 (work in progress). Engineering", draft-coras-lisp-re-08 (work in progress),
November 2015.
[GPE] Quinn, P., Agarwal, P., Fernando, R., Kreeger, L., [I-D.ermagan-lisp-nat-traversal]
Kreeger, L., Lewis, D., Maino, F., Smith, M., Yadav, N., Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino,
Yong, L., Xu, X., Elzur, U., and P. Garg, "Generic F., and C. White, "NAT traversal for LISP", draft-ermagan-
Protocol Extension for VXLAN", draft-quinn-vxlan-gpe- lisp-nat-traversal-10 (work in progress), February 2016.
03.txt (work in progress).
[GUE] Herbert, T. and L. Yong, "Generic UDP Encapsulation", [I-D.farinacci-lisp-te]
draft-herbert-gue-02.txt (work in progress). Farinacci, D., Kowal, M., and P. Lahiri, "LISP Traffic
Engineering Use-Cases", draft-farinacci-lisp-te-10 (work
in progress), March 2016.
[JSON-BINARY] [I-D.gross-geneve]
"Universal Binary JSON Specification", Gross, J., Sridhar, T., Garg, P., Wright, C., Ganga, I.,
URL http://ubjson.org. Agarwal, P., Duda, K., Dutt, D., and J. Hudson, "Geneve:
Generic Network Virtualization Encapsulation", draft-
gross-geneve-02 (work in progress), October 2014.
[L2-LISP] Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2 [I-D.herbert-gue]
(L2) LISP Encapsulation Format", draft-smith-lisp- Herbert, T., Yong, L., and O. Zia, "Generic UDP
layer2-03.txt (work in progress). Encapsulation", draft-herbert-gue-03 (work in progress),
March 2015.
[LISP-DDT] [I-D.ietf-lisp-ddt]
Fuller, V., Lewis, D., and V. Ermagan, "LISP Delegated Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A.
Database Tree", draft-ietf-lisp-ddt-01.txt (work in Smirnov, "LISP Delegated Database Tree", draft-ietf-lisp-
progress). ddt-07 (work in progress), May 2016.
[LISP-NATT] [I-D.portoles-lisp-eid-mobility]
Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino,
F., and C. White, "NAT traversal for LISP", draft-ermagan- F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a
lisp-nat-traversal-10.txt (work in progress). Unified Control Plane", draft-portoles-lisp-eid-
mobility-00 (work in progress), April 2016.
[LISP-RE] Coras, F., Cabellos-Aparicio, A., Domingo-Pascual, J., [I-D.quinn-vxlan-gpe]
Maino, F., and D. Farinacci, "LISP Replication Quinn, P., Manur, R., Kreeger, L., Lewis, D., Maino, F.,
Engineering", draft-coras-lisp-re-08.txt (work in Smith, M., Agarwal, P., Yong, L., Xu, X., Elzur, U., Garg,
progress). P., and D. Melman, "Generic Protocol Extension for VXLAN",
draft-quinn-vxlan-gpe-04 (work in progress), February
2015.
[LISP-TE] Farinacci, D., Lahiri, P., and M. Kowal, "LISP Traffic [I-D.smith-lisp-layer2]
Engineering Use-Cases", draft-farinacci-lisp-te-10.txt Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2
(work in progress). (L2) LISP Encapsulation Format", draft-smith-lisp-
layer2-03 (work in progress), September 2013.
[NVGRE] Sridharan, M., Greenberg, A., Wang, Y., Garg, P., [JSON-BINARY]
Venkataramiah, N., Duda, K., Ganga, I., Lin, G., Pearson, "Universal Binary JSON Specification",
M., Thaler, P., and C. Tumuluri, "NVGRE: Network URL http://ubjson.org.
Virtualization using Generic Routing Encapsulation",
draft-sridharan-virtualization-nvgre-06.txt (work in
progress).
[WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic [WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic
System 1984", NIMA TR8350.2, January 2000, <http://earth- System 1984", NIMA TR8350.2, January 2000, <http://earth-
info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf>. info.nga.mil/GandG/publications/tr8350.2/wgs84fin.pdf>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The authors would like to thank Vince Fuller, Gregg Schudel, Jesper The authors would like to thank Vince Fuller, Gregg Schudel, Jesper
Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for
their technical and editorial commentary. their technical and editorial commentary.
skipping to change at page 38, line 17 skipping to change at page 38, line 7
List Entry LCAF type. List Entry LCAF type.
Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for
suggesting new LCAF types. suggesting new LCAF types.
Thanks also goes to Terry Manderson for assistance obtaining a LISP Thanks also goes to Terry Manderson for assistance obtaining a LISP
AFI value from IANA. AFI value from IANA.
Appendix B. Document Change Log Appendix B. Document Change Log
B.1. Changes to draft-ietf-lisp-lcaf-13.txt [RFC Editor: Please delete this section on publication as RFC.]
B.1. Changes to draft-ietf-lisp-lcaf-14.txt
o Submitted July 2016.
o Fix IDnits errors and comments from Luigi Iannone, document
shepherd.
B.2. Changes to draft-ietf-lisp-lcaf-13.txt
o Submitted May 2016. o Submitted May 2016.
o Explain the Instance-ID LCAF Type is 32-bits in length and the o Explain the Instance-ID LCAF Type is 32-bits in length and the
Instance-ID field in the LISP encapsulation header is 24-bits. Instance-ID field in the LISP encapsulation header is 24-bits.
B.2. Changes to draft-ietf-lisp-lcaf-12.txt B.3. Changes to draft-ietf-lisp-lcaf-12.txt
o Submitted March 2016. o Submitted March 2016.
o Updated references and document timer. o Updated references and document timer.
o Removed the R, J, and L bits from the Multicast Info Type LCAF o Removed the R, J, and L bits from the Multicast Info Type LCAF
since working group decided to not go forward with draft- since working group decided to not go forward with draft-
farinacci-lisp-mr-signaling-03.txt in favor of draft- ietf-lisp- farinacci-lisp-mr-signaling-03.txt in favor of draft- ietf-lisp-
signal-free-00.txt. signal-free-00.txt.
B.3. Changes to draft-ietf-lisp-lcaf-11.txt B.4. Changes to draft-ietf-lisp-lcaf-11.txt
o Submitted September 2015. o Submitted September 2015.
o Reflecting comments from Prague LISP working group. o Reflecting comments from Prague LISP working group.
o Readying document for a LISP LCAF registry, RFC publication, and o Readying document for a LISP LCAF registry, RFC publication, and
for new use-cases that will be defined in the new charter. for new use-cases that will be defined in the new charter.
B.4. Changes to draft-ietf-lisp-lcaf-10.txt B.5. Changes to draft-ietf-lisp-lcaf-10.txt
o Submitted June 2015. o Submitted June 2015.
o Fix coauthor Job's contact information. o Fix coauthor Job's contact information.
B.5. Changes to draft-ietf-lisp-lcaf-09.txt B.6. Changes to draft-ietf-lisp-lcaf-09.txt
o Submitted June 2015. o Submitted June 2015.
o Fix IANA Considerations section to request a registry to allocate o Fix IANA Considerations section to request a registry to allocate
and track LCAF Type values. and track LCAF Type values.
B.6. Changes to draft-ietf-lisp-lcaf-08.txt B.7. Changes to draft-ietf-lisp-lcaf-08.txt
o Submitted April 2015. o Submitted April 2015.
o Comment from Florin. The Application Data Type length field has a o Comment from Florin. The Application Data Type length field has a
typo. The field should be labeled "12 + n" and not "8 + n". typo. The field should be labeled "12 + n" and not "8 + n".
o Fix length fields in the sections titled "Using Recursive LISP o Fix length fields in the sections titled "Using Recursive LISP
Canonical Address Encodings", "Generic Database Mapping Lookups", Canonical Address Encodings", "Generic Database Mapping Lookups",
and "Data Model Encoding". and "Data Model Encoding".
B.7. Changes to draft-ietf-lisp-lcaf-07.txt B.8. Changes to draft-ietf-lisp-lcaf-07.txt
o Submitted December 2014. o Submitted December 2014.
o Add a new LCAF Type called "Encapsulation Format" so decapsulating o Add a new LCAF Type called "Encapsulation Format" so decapsulating
xTRs can inform encapsulating xTRs what data-plane encapsulations xTRs can inform encapsulating xTRs what data-plane encapsulations
they support. they support.
B.8. Changes to draft-ietf-lisp-lcaf-06.txt B.9. Changes to draft-ietf-lisp-lcaf-06.txt
o Submitted October 2014. o Submitted October 2014.
o Make it clear how sorted RLOC records are done when LCAFs are used o Make it clear how sorted RLOC records are done when LCAFs are used
as the RLOC record. as the RLOC record.
B.9. Changes to draft-ietf-lisp-lcaf-05.txt B.10. Changes to draft-ietf-lisp-lcaf-05.txt
o Submitted May 2014. o Submitted May 2014.
o Add a length field of the JSON payload that can be used for either o Add a length field of the JSON payload that can be used for either
binary or text encoding of JSON data. binary or text encoding of JSON data.
B.10. Changes to draft-ietf-lisp-lcaf-04.txt B.11. Changes to draft-ietf-lisp-lcaf-04.txt
o Submitted January 2014. o Submitted January 2014.
o Agreement among ELP implementors to have the AFI 16-bit field o Agreement among ELP implementors to have the AFI 16-bit field
adjacent to the address. This will make the encoding consistent adjacent to the address. This will make the encoding consistent
with all other LCAF type address encodings. with all other LCAF type address encodings.
B.11. Changes to draft-ietf-lisp-lcaf-03.txt B.12. Changes to draft-ietf-lisp-lcaf-03.txt
o Submitted September 2013. o Submitted September 2013.
o Updated references and author's affilations. o Updated references and author's affilations.
o Added Instance-ID to the Multicast Info Type so there is relative o Added Instance-ID to the Multicast Info Type so there is relative
ease in parsing (S,G) entries within a VPN. ease in parsing (S,G) entries within a VPN.
o Add port range encodings to the Application Data LCAF Type. o Add port range encodings to the Application Data LCAF Type.
o Add a new JSON LCAF Type. o Add a new JSON LCAF Type.
o Add Address Key/Value LCAF Type to allow attributes to be attached o Add Address Key/Value LCAF Type to allow attributes to be attached
to an address. to an address.
B.12. Changes to draft-ietf-lisp-lcaf-02.txt B.13. Changes to draft-ietf-lisp-lcaf-02.txt
o Submitted March 2013. o Submitted March 2013.
o Added new LCAF Type "Replication List Entry" to support LISP o Added new LCAF Type "Replication List Entry" to support LISP
replication engineering use-cases. replication engineering use-cases.
o Changed references to new LISP RFCs. o Changed references to new LISP RFCs.
B.13. Changes to draft-ietf-lisp-lcaf-01.txt B.14. Changes to draft-ietf-lisp-lcaf-01.txt
o Submitted January 2013. o Submitted January 2013.
o Change longitude range from 0-90 to 0-180 in section 4.4. o Change longitude range from 0-90 to 0-180 in section 4.4.
o Added reference to WGS-84 in section 4.4. o Added reference to WGS-84 in section 4.4.
B.14. Changes to draft-ietf-lisp-lcaf-00.txt B.15. Changes to draft-ietf-lisp-lcaf-00.txt
o Posted first working group draft August 2012. o Posted first working group draft August 2012.
o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt. o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt.
Authors' Addresses Authors' Addresses
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA San Jose, CA
 End of changes. 109 change blocks. 
487 lines changed or deleted 509 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/