draft-ietf-lisp-lcaf-16.txt   draft-ietf-lisp-lcaf-17.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: April 4, 2017 Brocade Expires: April 15, 2017 Brocade
J. Snijders J. Snijders
NTT Communications NTT Communications
October 1, 2016 October 12, 2016
LISP Canonical Address Format (LCAF) LISP Canonical Address Format (LCAF)
draft-ietf-lisp-lcaf-16 draft-ietf-lisp-lcaf-17
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 Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 April 4, 2017. This Internet-Draft will expire on April 15, 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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 19 4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 19
4.9. Replication List Entries for Multicast Forwarding . . . . 21 4.9. Replication List Entries for Multicast Forwarding . . . . 21
4.10. Applications for AFI List Type . . . . . . . . . . . . . 22 4.10. Applications for AFI List Type . . . . . . . . . . . . . 22
4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 22 4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 22
4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 23 4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 23
4.10.3. ASCII Names in the Mapping Database . . . . . . . . 24 4.10.3. ASCII Names in the Mapping Database . . . . . . . . 24
4.10.4. Using Recursive LISP Canonical Address Encodings . . 25 4.10.4. Using Recursive LISP Canonical Address Encodings . . 25
4.10.5. Compatibility Mode Use Case . . . . . . . . . . . . 26 4.10.5. Compatibility Mode Use Case . . . . . . . . . . . . 26
5. Experimental LISP Canonical Address Applications . . . . . . 27 5. Experimental LISP Canonical Address Applications . . . . . . 27
5.1. Convey Application Specific Data . . . . . . . . . . . . 27 5.1. Convey Application Specific Data . . . . . . . . . . . . 27
5.2. Generic Database Mapping Lookups . . . . . . . . . . . . 28 5.2. Generic Database Mapping Lookups . . . . . . . . . . . . 29
5.3. PETR Admission Control Functionality . . . . . . . . . . 30 5.3. PETR Admission Control Functionality . . . . . . . . . . 30
5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 31 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 31
5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 32 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 32
5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 33 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 33
6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.1. Normative References . . . . . . . . . . . . . . . . . . 37 8.1. Normative References . . . . . . . . . . . . . . . . . . 37
8.2. Informative References . . . . . . . . . . . . . . . . . 38 8.2. Informative References . . . . . . . . . . . . . . . . . 38
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 39
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 40 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 40
B.1. Changes to draft-ietf-lisp-lcaf-16.txt . . . . . . . . . 40 B.1. Changes to draft-ietf-lisp-lcaf-17.txt . . . . . . . . . 40
B.2. Changes to draft-ietf-lisp-lcaf-15.txt . . . . . . . . . 40 B.2. Changes to draft-ietf-lisp-lcaf-16.txt . . . . . . . . . 40
B.3. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 40 B.3. Changes to draft-ietf-lisp-lcaf-15.txt . . . . . . . . . 40
B.4. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 40 B.4. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 40
B.5. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 40 B.5. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 40
B.6. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 40 B.6. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 40
B.7. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 41 B.7. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 41
B.8. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 41 B.8. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 41
B.9. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 41 B.9. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 41
B.10. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 41 B.10. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 41
B.11. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 41 B.11. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 41
B.12. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 41 B.12. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 42
B.13. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 42 B.13. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 42
B.14. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 42 B.14. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 42
B.15. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 42 B.15. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 42
B.16. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 42 B.16. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 42
B.17. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 42 B.17. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 43
B.18. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
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). To provide flexibility for current and future applications, (RLOCs). To provide flexibility for current and future applications,
these values can be encoded in LISP control messages using a general these values can be encoded in LISP control messages using a general
syntax that includes Address Family Identifier (AFI), length, and syntax that includes Address Family Identifier (AFI), length, and
value fields. value fields.
skipping to change at page 5, line 11 skipping to change at page 5, line 11
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.
Routing Locator (RLOC): the IPv4 or IPv6 address of an egress Routing Locator (RLOC): the IPv4 or IPv6 address of an egress
tunnel router (ETR). It is the output of a EID-to-RLOC mapping tunnel router (ETR). It is the output of a EID-to-RLOC mapping
lookup. An EID maps to one or more RLOCs. Typically, RLOCs are lookup. An EID maps to one or more RLOCs. Typically, RLOCs are
numbered from topologically aggregatable blocks that are assigned numbered from topologically aggregatable blocks that are assigned
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 Provider-Assigned
Multiple RLOCs can be assigned to the same ETR device or to (PA) addresses. Multiple RLOCs can be assigned to the same ETR
multiple ETR devices at a site. device or to 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 all types for LISP Canonical Address (LCA). This section defines all types for
which an initial allocation in the LISP-LCAF registry is requested. which an initial allocation in the LISP-LCAF registry is requested.
See IANA Considerations section for the complete list of such types. See IANA Considerations section for the complete list of such types.
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. When the LISP protocol uses LCAF definitions from this experience. When the LISP protocol uses LCAF definitions from this
document, the AFI-based address lengths are specified in this document, the AFI-based address lengths are specified in this
document. When new LCAF definitions are defined in other use-case document. When new LCAF definitions are defined in other use case
documents, the AFI-based address lengths for any new AFI encoded documents, the AFI-based address lengths for any new AFI encoded
addresses are specified in those documents. addresses are specified in those documents.
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 number of fields of variable length: 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, currently allocated values are: formatted encodings, currently allocated values are:
skipping to change at page 6, line 36 skipping to change at page 6, line 39
Type 12: Source/Dest Key Type Type 12: Source/Dest Key Type
Type 13: Replication List Entry Type Type 13: Replication List Entry Type
Type 14: JSON Data Model Type Type 14: JSON Data Model Type
Type 15: Key/Value Address Pair Type Type 15: Key/Value Address Pair Type
Type 16: Encapsulation Format Type Type 16: Encapsulation Format Type
Rsvd2: this LCAF Type dependent 8-bit field is reserved for future Rsvd2: this LCAF Type-dependent 8-bit field is reserved for future
use and MUST be transmitted as 0 and ignored on receipt. See use and MUST be transmitted as 0 and ignored on receipt. See
specific LCAF Type for specific bits not reserved. specific LCAF Type for specific bits not reserved.
Length: this 16-bit field is in units of bytes and covers all of the Length: this 16-bit field is in units of bytes and covers all of the
LISP Canonical Address payload, starting and including the byte LISP Canonical Address payload, starting and including the byte
after the Length field. When including the AFI, an LCAF encoded after the Length field. When including the AFI, an LCAF encoded
address will have a minimum length of 8 bytes when the Length address will have a minimum length of 8 bytes when the Length
field is 0. The 8 bytes include the AFI, Flags, Type, Reserved, field is 0. The 8 bytes include the AFI, Flags, Type, Reserved,
and Length fields. When the AFI is not next to encoded address in and Length fields. When the AFI is not next to an encoded address
a control message, then the encoded address will have a minimum in a control message, then the encoded address will have a minimum
length of 6 bytes when the Length field is 0. The 6 bytes include length of 6 bytes when the Length field is 0. The 6 bytes include
the Flags, Type, Reserved, and Length fields. the Flags, Type, Reserved, 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}. Therefore, when a locator-set has a mix of AFI records and Type}. Therefore, when a locator-set has a mix of AFI records and
LCAF records, they are ordered from smallest to largest AFI value. LCAF records, they are ordered from smallest to largest AFI value.
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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. The low-order bits used in the Instance ID field for the range. The low-order bits
of the Instance ID field must be 0. of the Instance ID field must be 0.
Length value n: length in bytes of the AFI address that follows the Length: length in bytes starting and including the byte after this
Instance ID field including the AFI field itself. Length field.
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 that 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.
skipping to change at page 9, line 18 skipping to change at page 9, line 18
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AS Number | | AS Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length: length in bytes starting and including the byte after this
AS Number field including the AFI field itself. Length field.
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
skipping to change at page 10, line 21 skipping to change at page 10, line 21
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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: length in bytes starting and including the byte after this
8-byte Longitude and Latitude fields including the AFI field Length field.
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).
Latitude Minutes: Valid values range from 0 to 59. Latitude Minutes: Valid values range from 0 to 59.
Latitude Seconds: Valid values range from 0 to 59. Latitude Seconds: Valid values range from 0 to 59.
E: When set to 1 means East, otherwise West. E: When set to 1 means East, otherwise West.
Longitude Degrees: Value values are from 0 to 180 degrees right or Longitude Degrees: Valid values are from 0 to 180 degrees right or
left of the Prime Meridian. left of the Prime Meridian.
Longitude Minutes: Valid values range from 0 to 59. Longitude Minutes: Valid values range from 0 to 59.
Longitude Seconds: Valid values range from 0 to 59. Longitude Seconds: Valid values range from 0 to 59.
Altitude: Height relative to sea level in meters. This is a two's Altitude: Height relative to sea level in meters. This is a two's
complement signed integer meaning that the altitude could be below complement signed integer meaning that the altitude could be below
sea level. A value of 0x7fffffff indicates no Altitude value is sea level. A value of 0x7fffffff indicates no Altitude value is
encoded. encoded.
skipping to change at page 12, line 18 skipping to change at page 12, line 18
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 [I-D.ermagan-lisp-nat-traversal] 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
the UDP Port Number field including the AFI fields themselves. Length field.
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.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
Global ETR RLOC Address: this is an address known to be globally Global ETR RLOC Address: this is an address known to be globally
unique built by NAT-traversal functionality in a LISP router. unique built by NAT-traversal functionality in a LISP router.
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 by a LISP router that resides on the
on the private side of a NAT device. 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 NAT Reencapsulating ETR behind the NAT. There can be one or more NAT Reencapsulating
Tunnel Router (RTR) [I-D.ermagan-lisp-nat-traversal] addresses Tunnel Router (RTR) [I-D.ermagan-lisp-nat-traversal] addresses
supplied in these set of fields. The number of RTRs encoded is supplied in these set of fields. The number of RTRs encoded is
determined by the LCAF length field. When there are no RTRs determined by the LCAF length field. When there are no RTRs
supplied, the RTR fields can be omitted and reflected by the LCAF supplied, the RTR fields can be omitted and reflected by the LCAF
length field or an AFI of 0 can be used to indicate zero RTRs length field or an AFI of 0 can be used to indicate zero RTRs
encoded. 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 group address EID can return a replication list of So a lookup on a group address EID can return a replication list of
RLOC group addresses or RLOC unicast addresses. The intent of this RLOC group addresses or RLOC unicast addresses. The intent of this
type of unicast replication is to deliver packets to multiple ETRs at type of 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 [I-D.coras-lisp-re]), the Replication List Entry LCAF according to [I-D.coras-lisp-re]), the Replication List Entry LCAF
type is used 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 an EID is away from it's 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
Length field.
Reserved: must be set to zero and ignore on receipt. Reserved: must be set to zero and ignored 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
of (Instance-ID, S-prefix, G-prefix). of (Instance-ID, S-prefix, G-prefix).
Source MaskLen: the mask length of the source prefix that follows. Source MaskLen: the mask length of the source prefix that follows.
The length is the number of high-order mask bits set.
Group MaskLen: the mask length of the group prefix that follows. Group MaskLen: the mask length of the group prefix that follows.
The length is the number of high-order mask bits set.
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 address
its own encoding of a multicast address, this field must be either family has a multicast address semantic, this field must be either
a group address or a broadcast address. a group address or a broadcast address.
Source/Subnet Address is the source address or prefix for encoding a Source/Subnet Address is the source address or prefix for encoding a
(S,G) multicast entry. (S,G) multicast entry.
Group Address is the group address or group prefix for encoding Group Address is the group address or group prefix for encoding
(S,G) or (*,G) multicast entries. (S,G) or (*,G) multicast entries.
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
[I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended
EIDs are 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 can be
can be returned to provide a list of locators in an explicit re- returned to provide a list of locators in an explicit re-
encapsulation path. See [I-D.farinacci-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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
Length field.
Rsvd3: this field is reserved for future use and MUST be transmitted Rsvd3: this field is reserved for future use and MUST be transmitted
as 0 and ignored on receipt. as 0 and ignored on receipt.
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
skipping to change at page 17, line 17 skipping to change at page 17, line 17
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
does not need to be understood by the mapping system for mapping does not need to be understood by the mapping system for mapping
database 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 will be used to encode key material. See
[I-D.ietf-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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
Material field. Length 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. A key section is made up the "Key Length" included in this LCAF. A key section is made up the "Key Length"
and "Key Material" fields. and "Key Material" fields.
Rsvd3: this field is reserved for future use and MUST be transmitted Rsvd3: this field is reserved for future use and MUST be transmitted
as 0 and ignored on receipt. as 0 and ignored on receipt.
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. Refer to the [I-D.ietf-lisp-ddt] and field. Refer to the [I-D.ietf-lisp-ddt] and
[I-D.ietf-lisp-crypto] use-cases for definitions of this field. [I-D.ietf-lisp-crypto] use cases for definitions of this field.
Rsvd4: this field is reserved for future use and MUST be transmitted Rsvd4: this field is reserved for future use and MUST be transmitted
as 0 and ignored on receipt. as 0 and ignored on receipt.
R bit: this is the revoke bit and, if set, it specifies that this R bit: this is the revoke bit and, if set, it specifies that this
Key is being Revoked. Key is being Revoked.
Key Length: this field determines the length in bytes of the Key Key Length: this field determines the length in bytes of the Key
Material field. Material field.
skipping to change at page 19, line 12 skipping to change at page 19, line 12
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 [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism,
extended 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 need
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
Length field.
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. The
length is the number of high-order mask bits set.
Dest-ML: the mask length of the destination prefix that follows. Dest-ML: the mask length of the destination prefix that follows.
The length is the number of high-order mask bits set.
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
[I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended
EIDs are used in Map-Referral messages. Refer to EIDs are used in Map-Referral messages. Refer to
[I-D.farinacci-lisp-te] for usage details of this LCAF type. [I-D.farinacci-lisp-te] for usage details of this LCAF type.
skipping to change at page 21, line 22 skipping to change at page 21, line 22
tree. Each RTR will register its locator address and its configured tree. Each RTR will register its locator address and its configured
level in the 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
Length field.
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.
skipping to change at page 22, line 20 skipping to change at page 22, line 23
Canonical Address can use the AFI List Type to carry a variable Canonical Address can use the AFI List Type to carry a variable
number of AFIs in one LCAF AFI. number of AFIs in 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 starting and including the byte after this
encoded addresses are used. Length field.
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.
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. See Requests, Map-Replies, Map-Registers, and Map-Notify messages. See
skipping to change at page 23, line 17 skipping to change at page 23, line 17
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 starting and including the byte after this
addresses are used. Length field.
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. See even another MAC address being used as an RLOC. See
[I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when [I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when
doing EID mobility. 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
ASCII string (the last byte of 0 is included). Length field.
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 (for can be used to carry within the LCAF AFI another LCAF AFI (for
example, Application Specific Data see Section 5.1. 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 4 | Rsvd2 | 12 + 6 | | Type = 4 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP TOS, IPv6 QQS 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 = 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 starting and including the byte after this
included. Length field.
Length2: length in bytes starting and including the byte after this
Length2 field.
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
LISP site, it can return different locator-sets based on the type of LISP site, it can return different locator-sets based on the type of
application or level of service that is being requested. application or level of service that is being requested.
skipping to change at page 26, line 21 skipping to change at page 26, line 21
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = 16387 | Rsvd1 | Flags | | AFI = 16387 | Rsvd1 | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 5 | Rsvd2 | 12 + 2 | | Type = 5 | Rsvd2 | Length2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: length in bytes starting and including the byte after this
Length field.
Length2: length in bytes starting and including the byte after this
Length2 field.
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
LCAF Type to get to the locator address encoding (an IPv4 locator LCAF Type to get to the locator address encoding (an IPv4 locator
address). A LISP system that does support the Geo Coordinate LCAF address). A LISP system that does support the Geo Coordinate LCAF
Type can support parsing the locator address within the Geo Type can support parsing the locator address within the Geo
Coordinate LCAF encoding or in the locator encoding that follows in Coordinate LCAF encoding or in the locator encoding that follows in
the AFI List LCAF. the AFI List LCAF.
skipping to change at page 27, line 20 skipping to change at page 28, line 12
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
8-byte Application Data fields including the AFI field itself. Length field.
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
lower value and an upper value. When a single port is encoded, lower value and an upper value. When a single port is encoded,
the lower and upper value fields are the same. the lower and upper value fields are the same.
skipping to change at page 28, line 21 skipping to change at page 29, line 18
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
is the number of bytes that follow this Length field. Length field.
Key Field Num: the value of this field is the the number of "Key" Key Field Num: the value of this field is the the number of "Key"
sub-fields minus 1, the "Key" field can be broken up into. So if sub-fields minus 1, the "Key" field can be broken up into. So if
this field has a value of 0, there is 1 sub-field in the "Key". this field has a value of 0, there is 1 sub-field in the "Key".
The width of the sub-fields are fixed length. So for a key size The width of the sub-fields are fixed length. So for a key size
of 8 bytes, with a Key Field Num of 3, allows 4 sub-fields of 2 of 8 bytes, with a Key Field Num of 3, allows 4 sub-fields of 2
bytes each in length. Allowing for a reasonable number of 16 sub- bytes each in length. Allowing for a reasonable number of 16 sub-
field separators, valid values range from 0 to 15. field 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
skipping to change at page 30, line 9 skipping to change at page 30, line 9
Key: the variable length key used to do a LISP Database Mapping Key: the variable length key used to do a LISP Database Mapping
lookup. The length of the key is the value n (as shown above). lookup. The length of the key is the value n (as shown above).
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.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 is
format is used in a Map-Register or Map-Reply locator-record. 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Nonce | | Reserved | Nonce |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of the AFI address that follows the Length: length in bytes starting and including the byte after this
Nonce field including the AFI field itself. Length field.
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 This nonce value is inserted in the nonce field in the LISP header
encapsulation. encapsulation.
AFI = x: x can be any AFI value from [AFI]. AFI = x: x can be any AFI value from [AFI].
skipping to change at page 31, line 17 skipping to change at page 31, line 17
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| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 the fields that follow the "JSON Length: length in bytes starting and including the byte after this
length" field. Length field.
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 [RFC7159]. 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.
skipping to change at page 32, line 7 skipping to change at page 32, line 7
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.
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.5. Encoding Key/Value Address Pairs 5.5. Encoding Key/Value Address Pairs
The Key/Value pair is for example useful for attaching attributes to The Key/Value pair is, for example, useful for attaching attributes
other elements of LISP packets, such as EIDs or RLOCs. When to 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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address as Key ... | | AFI = x | Address as Key ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = y | Address as Value ... | | AFI = y | Address as Value ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length value n: length in bytes of fields that follow. Length: length in bytes starting and including the byte after this
Length field.
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 is the "Address as Key" AFI that can have any value from AFI = x: x is the "Address as Key" AFI that can have any value from
[AFI]. A specific AFI has its own encoding of either a unicast or [AFI]. A specific AFI has its own encoding of either a unicast or
multicast locator address. All RTR/ETR entries for the same level multicast locator address. All RTR/ETR entries for the same level
should be combined together by a Map-Server to avoid searching should be combined together by a Map-Server to avoid searching
through the entire multi-level list of locator entries in a Map- through the entire multi-level list of locator entries in a Map-
Reply message. Reply message.
Address as Key: this AFI encoded address will be attached with the Address as Key: this AFI-encoded address will be attached with the
attributes encoded in "Address as Value" which follows this field. attributes encoded in "Address as Value" which follows this field.
AFI = y: y is the "Address of Value" AFI that can have any value AFI = y: y is the "Address of Value" AFI that can have any value
from [AFI]. A specific AFI has its own encoding of either a from [AFI]. A specific AFI has its own encoding of either a
unicast or multicast locator address. All RTR/ETR entries for the unicast or multicast locator address. All RTR/ETR entries for the
same level should be combined together by a Map-Server to avoid same level should be combined together by a Map-Server to avoid
searching through the entire multi-level list of locator entries searching through the entire multi-level list of locator entries
in a Map-Reply message. in a Map-Reply message.
Address as Value: this AFI encoded address will be the attribute Address as Value: this AFI-encoded address will be the attribute
address that goes along with "Address as Key" which precedes this address that goes along with "Address as Key" which precedes this
field. field.
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.6. Multiple Data-Planes 5.6. Multiple Data-Planes
Overlays are becoming popular in many parts of the network which have Overlays are becoming popular in many parts of the network which have
created an explosion of data-plane encapsulation headers. Since the created an explosion of data-plane encapsulation headers. Since the
skipping to change at page 34, line 12 skipping to change at page 34, line 12
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 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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: length in bytes starting and including the byte after this
next 32-bits including the AFI field itself. Length field.
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 layer 3 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 layer 2 LISP encapsulation using destination UDP port
8472 [I-D.smith-lisp-layer2]. 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
[I-D.quinn-vxlan-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 [RFC7637]. 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
[I-D.gross-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 can accept GUE encapsulation using destination UDP port TBD
[I-D.herbert-gue]. [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
skipping to change at page 38, line 51 skipping to change at page 38, line 51
[I-D.ietf-lisp-ddt] [I-D.ietf-lisp-ddt]
Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A.
Smirnov, "LISP Delegated Database Tree", draft-ietf-lisp- Smirnov, "LISP Delegated Database Tree", draft-ietf-lisp-
ddt-08 (work in progress), September 2016. ddt-08 (work in progress), September 2016.
[I-D.portoles-lisp-eid-mobility] [I-D.portoles-lisp-eid-mobility]
Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino, Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino,
F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a
Unified Control Plane", draft-portoles-lisp-eid- Unified Control Plane", draft-portoles-lisp-eid-
mobility-00 (work in progress), April 2016. mobility-01 (work in progress), October 2016.
[I-D.quinn-vxlan-gpe] [I-D.quinn-vxlan-gpe]
Quinn, P., Manur, R., Kreeger, L., Lewis, D., Maino, F., Quinn, P., Manur, R., Kreeger, L., Lewis, D., Maino, F.,
Smith, M., Agarwal, P., Yong, L., Xu, X., Elzur, U., Garg, Smith, M., Agarwal, P., Yong, L., Xu, X., Elzur, U., Garg,
P., and D. Melman, "Generic Protocol Extension for VXLAN", P., and D. Melman, "Generic Protocol Extension for VXLAN",
draft-quinn-vxlan-gpe-04 (work in progress), February draft-quinn-vxlan-gpe-04 (work in progress), February
2015. 2015.
[I-D.smith-lisp-layer2] [I-D.smith-lisp-layer2]
Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2 Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2
skipping to change at page 40, line 9 skipping to change at page 40, line 9
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
[RFC Editor: Please delete this section on publication as RFC.] [RFC Editor: Please delete this section on publication as RFC.]
B.1. Changes to draft-ietf-lisp-lcaf-16.txt B.1. Changes to draft-ietf-lisp-lcaf-17.txt
o Submitted October 2016.
o Addressed comments from Gen-ART reviewer Peter Yee.
o Addressed IESG last-call comments from Suresh Krishnan.
B.2. Changes to draft-ietf-lisp-lcaf-16.txt
o Submitted October 2016. o Submitted October 2016.
o Addressed comments from Security Directorate reviewer David o Addressed comments from Security Directorate reviewer David
Mandelberg. Mandelberg.
B.2. Changes to draft-ietf-lisp-lcaf-15.txt B.3. Changes to draft-ietf-lisp-lcaf-15.txt
o Submitted September 2016. o Submitted September 2016.
o Addressed comments from Routing Directorate reviewer Stig Venass. o Addressed comments from Routing Directorate reviewer Stig Venass.
B.3. Changes to draft-ietf-lisp-lcaf-14.txt B.4. Changes to draft-ietf-lisp-lcaf-14.txt
o Submitted July 2016. o Submitted July 2016.
o Fix IDnits errors and comments from Luigi Iannone, document o Fix IDnits errors and comments from Luigi Iannone, document
shepherd. shepherd.
B.4. Changes to draft-ietf-lisp-lcaf-13.txt B.5. 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.5. Changes to draft-ietf-lisp-lcaf-12.txt B.6. 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.6. Changes to draft-ietf-lisp-lcaf-11.txt B.7. 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.7. Changes to draft-ietf-lisp-lcaf-10.txt B.8. 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.8. Changes to draft-ietf-lisp-lcaf-09.txt B.9. 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.9. Changes to draft-ietf-lisp-lcaf-08.txt B.10. 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.10. Changes to draft-ietf-lisp-lcaf-07.txt B.11. 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.11. Changes to draft-ietf-lisp-lcaf-06.txt B.12. 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.12. Changes to draft-ietf-lisp-lcaf-05.txt B.13. 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.13. Changes to draft-ietf-lisp-lcaf-04.txt B.14. 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.14. Changes to draft-ietf-lisp-lcaf-03.txt B.15. 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.15. Changes to draft-ietf-lisp-lcaf-02.txt B.16. 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.16. Changes to draft-ietf-lisp-lcaf-01.txt B.17. 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.17. Changes to draft-ietf-lisp-lcaf-00.txt B.18. 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. 103 change blocks. 
139 lines changed or deleted 167 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/