idnits 2.17.1 draft-ietf-lisp-lcaf-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 208: '...is reserved for future use and MUST be...' RFC 2119 keyword, line 250: '...is reserved for future use and MUST be...' RFC 2119 keyword, line 542: '... See [LISP-MRSIG] for details. The J-bit MUST not be set when the...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: J-bit: this is the Join-Request bit and is used when this LCAF type is present in the destination EID-prefix field of a Map-Request. See [LISP-MRSIG] for details. The J-bit MUST not be set when the L-bit is also set in the same LCAF block. A receiver should not take any specific Join or Leave action when both bits are set. -- The document date (September 18, 2015) is 3136 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Obsolete normative reference: RFC 6830 (Obsoleted by RFC 9300, RFC 9301) == Outdated reference: A later version (-04) exists of draft-quinn-vxlan-gpe-03 == Outdated reference: A later version (-03) exists of draft-herbert-gue-02 == Outdated reference: A later version (-09) exists of draft-ietf-lisp-ddt-01 == Outdated reference: A later version (-06) exists of draft-farinacci-lisp-mr-signaling-03 == Outdated reference: A later version (-19) exists of draft-ermagan-lisp-nat-traversal-03 == Outdated reference: A later version (-08) exists of draft-coras-lisp-re-03 == Outdated reference: A later version (-12) exists of draft-farinacci-lisp-te-03 == Outdated reference: A later version (-08) exists of draft-sridharan-virtualization-nvgre-06 Summary: 5 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Farinacci 3 Internet-Draft lispers.net 4 Intended status: Experimental D. Meyer 5 Expires: March 21, 2016 Brocade 6 J. Snijders 7 NTT Communications 8 September 18, 2015 10 LISP Canonical Address Format (LCAF) 11 draft-ietf-lisp-lcaf-11 13 Abstract 15 This draft defines a canonical address format encoding used in LISP 16 control messages and in the encoding of lookup keys for the LISP 17 Mapping Database System. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 21, 2016. 36 Copyright Notice 38 Copyright (c) 2015 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 55 3. LISP Canonical Address Format Encodings . . . . . . . . . . . 4 56 4. LISP Canonical Address Applications . . . . . . . . . . . . . 7 57 4.1. Segmentation using LISP . . . . . . . . . . . . . . . . . 7 58 4.2. Carrying AS Numbers in the Mapping Database . . . . . . . 8 59 4.3. Assigning Geo Coordinates to Locator Addresses . . . . . 9 60 4.4. NAT Traversal Scenarios . . . . . . . . . . . . . . . . . 12 61 4.5. Multicast Group Membership Information . . . . . . . . . 14 62 4.6. Traffic Engineering using Re-encapsulating Tunnels . . . 16 63 4.7. Storing Security Data in the Mapping Database . . . . . . 17 64 4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 19 65 4.9. Replication List Entries for Multicast Forwarding . . . . 20 66 4.10. Applications for AFI List Type . . . . . . . . . . . . . 21 67 4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 21 68 4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 22 69 4.10.3. ASCII Names in the Mapping Database . . . . . . . . 23 70 4.10.4. Using Recursive LISP Canonical Address Encodings . . 24 71 4.10.5. Compatibility Mode Use Case . . . . . . . . . . . . 25 72 5. Experimental LISP Canonical Address Applications . . . . . . 26 73 5.1. Convey Application Specific Data . . . . . . . . . . . . 26 74 5.2. Generic Database Mapping Lookups . . . . . . . . . . . . 27 75 5.3. PETR Admission Control Functionality . . . . . . . . . . 29 76 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 30 77 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 31 78 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 32 79 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34 80 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 81 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 82 8.1. Normative References . . . . . . . . . . . . . . . . . . 35 83 8.2. Informative References . . . . . . . . . . . . . . . . . 36 84 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 37 85 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 38 86 B.1. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 38 87 B.2. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 38 88 B.3. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 38 89 B.4. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 38 90 B.5. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 39 91 B.6. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 39 92 B.7. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 39 93 B.8. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 39 94 B.9. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 39 95 B.10. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 40 96 B.11. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 40 97 B.12. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 40 98 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 100 1. Introduction 102 The LISP architecture and protocols [RFC6830] introduces two new 103 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators 104 (RLOCs) which are intended to replace most use of IP addresses on the 105 Internet. To provide flexibility for current and future 106 applications, these values can be encoded in LISP control messages 107 using a general syntax that includes Address Family Identifier (AFI), 108 length, and value fields. 110 Currently defined AFIs include IPv4 and IPv6 addresses, which are 111 formatted according to code-points assigned in [AFI] as follows: 113 IPv4 Encoded Address: 115 0 1 2 3 116 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 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | AFI = 1 | IPv4 Address ... | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | ... IPv4 Address | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 IPv6 Encoded Address: 125 0 1 2 3 126 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 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | AFI = 2 | IPv6 Address ... | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | ... IPv6 Address ... | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | ... IPv6 Address ... | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | ... IPv6 Address ... | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | ... IPv6 Address | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 This document describes the currently-defined AFIs the LISP protocol 140 uses along with their encodings and introduces the LISP Canonical 141 Address Format (LCAF) that can be used to define the LISP-specific 142 encodings for arbitrary AFI values. 144 2. Definition of Terms 146 Address Family Identifier (AFI): a term used to describe an address 147 encoding in a packet. An address family currently defined for 148 IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details. The 149 reserved AFI value of 0 is used in this specification to indicate 150 an unspecified encoded address where the the length of the address 151 is 0 bytes following the 16-bit AFI value of 0. 153 Unspecified Address Format: 155 0 1 2 3 156 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 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | AFI = 0 | | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value 162 used in the source and destination address fields of the first 163 (most inner) LISP header of a packet. The host obtains a 164 destination EID the same way it obtains a destination address 165 today, for example through a DNS lookup or SIP exchange. The 166 source EID is obtained via existing mechanisms used to set a 167 host's "local" IP address. An EID is allocated to a host from an 168 EID-prefix block associated with the site where the host is 169 located. An EID can be used by a host to refer to other hosts. 171 Routing Locator (RLOC): the IPv4 or IPv6 address of an egress 172 tunnel router (ETR). It is the output of a EID-to-RLOC mapping 173 lookup. An EID maps to one or more RLOCs. Typically, RLOCs are 174 numbered from topologically aggregatable blocks that are assigned 175 to a site at each point to which it attaches to the global 176 Internet; where the topology is defined by the connectivity of 177 provider networks, RLOCs can be thought of as PA addresses. 178 Multiple RLOCs can be assigned to the same ETR device or to 179 multiple ETR devices at a site. 181 3. LISP Canonical Address Format Encodings 183 IANA has assigned AFI value 16387 (0x4003) to the LISP architecture 184 and protocols. This specification defines the encoding format of the 185 LISP Canonical Address (LCA). This section defines both experimental 186 types as well as types that reside in the registry that have 187 corresponding working group drafts. See IANA Considerations section 188 for a list of types that will reside in the LISP-LCAF Registry. 190 The Address Family AFI definitions from [AFI] only allocate code- 191 points for the AFI value itself. The length of the address or entity 192 that follows is not defined and is implied based on conventional 193 experience. Where the LISP protocol uses LISP Canonical Addresses 194 specifically, the address length definitions will be in this 195 specification and take precedent over any other specification. 197 The first 6 bytes of an LISP Canonical Address are followed by a 198 variable length of fields: 200 0 1 2 3 201 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 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | AFI = 16387 | Rsvd1 | Flags | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | Type | Rsvd2 | Length | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 Rsvd1: this 8-bit field is reserved for future use and MUST be 209 transmitted as 0 and ignored on receipt. 211 Flags: this 8-bit field is for future definition and use. For now, 212 set to zero on transmission and ignored on receipt. 214 Type: this 8-bit field is specific to the LISP Canonical Address 215 formatted encodings, values are: 217 Type 0: Null Body Type 219 Type 1: AFI List Type 221 Type 2: Instance ID Type 223 Type 3: AS Number Type 225 Type 4: Application Data Type 227 Type 5: Geo Coordinates Type 229 Type 6: Opaque Key Type 231 Type 7: NAT-Traversal Type 233 Type 8: Nonce Locator Type 235 Type 9: Multicast Info Type 237 Type 10: Explicit Locator Path Type 239 Type 11: Security Key Type 240 Type 12: Source/Dest Key Type 242 Type 13: Replication List Entry Type 244 Type 14: JSON Data Model Type 246 Type 15: Key/Value Address Pair Type 248 Type 16: Encapsulation Format Type 250 Rsvd2: this 8-bit field is reserved for future use and MUST be 251 transmitted as 0 and ignored on receipt. 253 Length: this 16-bit field is in units of bytes and covers all of the 254 LISP Canonical Address payload, starting and including the byte 255 after the Length field. So any LCAF encoded address will have a 256 minimum length of 8 bytes when the Length field is 0. The 8 bytes 257 include the AFI, Flags, Type, Reserved, and Length fields. When 258 the AFI is not next to encoded address in a control message, then 259 the encoded address will have a minimum length of 6 bytes when the 260 Length field is 0. The 6 bytes include the Flags, Type, Reserved, 261 and Length fields. 263 [RFC6830] states RLOC records are sorted when encoded in control 264 messages so the locator-set has consistent order across all xTRs for 265 a given EID. The sort order is based on sort-key {afi, RLOC- 266 address}. When an RLOC is LCAF encoded, the sort-key is {afi, LCAF- 267 Type, payload}. Therefore, when a locator-set has a mix of AFI 268 records and LCAF records, all LCAF records will appear after all the 269 AFI records. 271 4. LISP Canonical Address Applications 273 4.1. Segmentation using LISP 275 When multiple organizations inside of a LISP site are using private 276 addresses [RFC1918] as EID-prefixes, their address spaces must remain 277 segregated due to possible address duplication. An Instance ID in 278 the address encoding can aid in making the entire AFI based address 279 unique. 281 Another use for the Instance ID LISP Canonical Address Format is when 282 creating multiple segmented VPNs inside of a LISP site where keeping 283 EID-prefix based subnets is desirable. 285 Instance ID LISP Canonical Address Format: 287 0 1 2 3 288 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 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | AFI = 16387 | Rsvd1 | Flags | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 | Type = 2 | IID mask-len | 4 + n | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 | Instance ID | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | AFI = x | Address ... | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 IID mask-len: if the AFI is set to 0, then this format is not 300 encoding an extended EID-prefix but rather an instance-ID range 301 where the 'IID mask-len' indicates the number of high-order bits 302 used in the Instance ID field for the range. 304 Length value n: length in bytes of the AFI address that follows the 305 Instance ID field including the AFI field itself. 307 Instance ID: the low-order 24-bits that can go into a LISP data 308 header when the I-bit is set. See [RFC6830] for details. 310 AFI = x: x can be any AFI value from [AFI]. 312 This LISP Canonical Address Type can be used to encode either EID or 313 RLOC addresses. 315 Usage: When used as a lookup key, the EID is regarded as a extended- 316 EID in the mapping system. And this encoding is used in EID records 317 in Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages. 319 When LISP-DDT [LISP-DDT] is used as the mapping system mechanism, 320 extended EIDs are used in Map-Referral messages. 322 4.2. Carrying AS Numbers in the Mapping Database 324 When an AS number is stored in the LISP Mapping Database System for 325 either policy or documentation reasons, it can be encoded in a LISP 326 Canonical Address. 328 AS Number LISP Canonical Address Format: 330 0 1 2 3 331 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 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 | AFI = 16387 | Rsvd1 | Flags | 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 |n Type = 3 | Rsvd2 | 4 + n | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | AS Number | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | AFI = x | Address ... | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 Length value n: length in bytes of the AFI address that follows the 343 AS Number field including the AFI field itself. 345 AS Number: the 32-bit AS number of the autonomous system that has 346 been assigned either the EID or RLOC that follows. 348 AFI = x: x can be any AFI value from [AFI]. 350 The AS Number Canonical Address Type can be used to encode either EID 351 or RLOC addresses. The former is used to describe the LISP-ALT AS 352 number the EID-prefix for the site is being carried for. The latter 353 is used to describe the AS that is carrying RLOC based prefixes in 354 the underlying routing system. 356 Usage: This encoding can be used in EID or RLOC records in Map- 357 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 358 LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended 359 EIDs are used in Map-Referral messages. 361 4.3. Assigning Geo Coordinates to Locator Addresses 363 If an ETR desires to send a Map-Reply describing the Geo Coordinates 364 for each locator in its locator-set, it can use the Geo Coordinate 365 Type to convey physical location information. 367 Coordinates are specified using the WGS-84 (World Geodetic System) 368 reference coordinate system [WGS-84]. 370 Geo Coordinate LISP Canonical Address Format: 372 0 1 2 3 373 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 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 | AFI = 16387 | Rsvd1 | Flags | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Type = 5 | Rsvd2 | 12 + n | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 379 |N| Latitude Degrees | Minutes | Seconds | 380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 381 |E| Longitude Degrees | Minutes | Seconds | 382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 383 | Altitude | 384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 385 | AFI = x | Address ... | 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 Length value n: length in bytes of the AFI address that follows the 389 8-byte Longitude and Latitude fields including the AFI field 390 itself. 392 N: When set to 1 means North, otherwise South. 394 Latitude Degrees: Valid values range from 0 to 90 degrees above or 395 below the equator (northern or southern hemisphere, respectively). 397 Latitude Minutes: Valid values range from 0 to 59. 399 Latitude Seconds: Valid values range from 0 to 59. 401 E: When set to 1 means East, otherwise West. 403 Longitude Degrees: Value values are from 0 to 180 degrees right or 404 left of the Prime Meridian. 406 Longitude Minutes: Valid values range from 0 to 59. 408 Longitude Seconds: Valid values range from 0 to 59. 410 Altitude: Height relative to sea level in meters. This is a signed 411 integer meaning that the altitude could be below sea level. A 412 value of 0x7fffffff indicates no Altitude value is encoded. 414 AFI = x: x can be any AFI value from [AFI]. 416 The Geo Coordinates Canonical Address Type can be used to encode 417 either EID or RLOC addresses. When used for EID encodings, you can 418 determine the physical location of an EID along with the topological 419 location by observing the locator-set. 421 Usage: This encoding can be used in EID or RLOC records in Map- 422 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 423 LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended 424 EIDs are used in Map-Referral messages. 426 4.4. NAT Traversal Scenarios 428 When a LISP system is conveying global address and mapped port 429 information when traversing through a NAT device, the NAT-Traversal 430 LCAF Type is used. See [LISP-NATT] for details. 432 NAT-Traversal Canonical Address Format: 434 0 1 2 3 435 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 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | AFI = 16387 | Rsvd1 | Flags | 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | Type = 7 | Rsvd2 | 4 + n | 440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 | MS UDP Port Number | ETR UDP Port Number | 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 443 | AFI = x | Global ETR RLOC Address ... | 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 445 | AFI = x | MS RLOC Address ... | 446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 | AFI = x | Private ETR RLOC Address ... | 448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 449 | AFI = x | RTR RLOC Address 1 ... | 450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 451 | AFI = x | RTR RLOC Address k ... | 452 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 Length value n: length in bytes of the AFI addresses that follows 455 the UDP Port Number field including the AFI fields themselves. 457 MS UDP Port Number: this is the UDP port number of the Map-Server 458 and is set to 4342. 460 ETR UDP Port Number: this is the port number returned to a LISP 461 system which was copied from the source port from a packet that 462 has flowed through a NAT device. 464 AFI = x: x can be any AFI value from [AFI]. 466 Global ETR RLOC Address: this is an address known to be globally 467 unique built by NAT-traversal functionality in a LISP router. 469 MS RLOC Address: this is the address of the Map-Server used in the 470 destination RLOC of a packet that has flowed through a NAT device. 472 Private ETR RLOC Address: this is an address known to be a private 473 address inserted in this LCAF format by a LISP router that resides 474 on the private side of a NAT device. 476 RTR RLOC Address: this is an encapsulation address used by an ITR or 477 PITR which resides behind a NAT device. This address is known to 478 have state in a NAT device so packets can flow from it to the LISP 479 ETR behind the NAT. There can be one or more NTR addresses 480 supplied in these set of fields. The number of NTRs encoded is 481 determined by the LCAF length field. When there are no NTRs 482 supplied, the NTR fields can be omitted and reflected by the LCAF 483 length field or an AFI of 0 can be used to indicate zero NTRs 484 encoded. 486 Usage: This encoding can be used in Info-Request and Info-Reply 487 messages. The mapping system does not store this information. The 488 information is used by an xTR and Map-Server to convey private and 489 public address information when traversing NAT and firewall devices. 491 4.5. Multicast Group Membership Information 493 Multicast group information can be published in the mapping database 494 so a lookup on an EID based group address can return a replication 495 list of group addresses or a unicast addresses for single replication 496 or multiple head-end replications. The intent of this type of 497 unicast replication is to deliver packets to multiple ETRs at 498 receiver LISP multicast sites. The locator-set encoding for this EID 499 record type can be a list of ETRs when they each register with "Merge 500 Semantics". The encoding can be a typical AFI encoded locator 501 address. When an RTR list is being registered (with multiple levels 502 according to [LISP-RE]), the Replication List Entry LCAF type is used 503 for locator encoding. 505 This LCAF encoding can be used to send broadcast packets to all 506 members of a subnet when each EIDs are away from their home subnet 507 location. 509 Multicast Info Canonical Address Format: 511 0 1 2 3 512 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 513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 | AFI = 16387 | Rsvd1 | Flags | 515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 516 | Type = 9 | Rsvd2 |R|L|J| 8 + n | 517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 | Instance-ID | 519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 520 | Reserved | Source MaskLen| Group MaskLen | 521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 522 | AFI = x | Source/Subnet Address ... | 523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 524 | AFI = x | Group Address ... | 525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 527 Length value n: length in bytes of fields that follow. 529 Reserved: must be set to zero and ignore on receipt. 531 R-bit: this is the RP-bit that represents PIM (S,G,RP-bit) multicast 532 state. This bit can be set for Joins (when the J-bit is set) or 533 for Leaves (when the L-bit is set). See [LISP-MRSIG] for more 534 usage details. 536 L-bit: this is the Leave-Request bit and is used when this LCAF type 537 is present in the destination EID-prefix field of a Map-Request. 538 See [LISP-MRSIG] for details. 540 J-bit: this is the Join-Request bit and is used when this LCAF type 541 is present in the destination EID-prefix field of a Map-Request. 542 See [LISP-MRSIG] for details. The J-bit MUST not be set when the 543 L-bit is also set in the same LCAF block. A receiver should not 544 take any specific Join or Leave action when both bits are set. 546 Instance ID: the low-order 24-bits that can go into a LISP data 547 header when the I-bit is set. See [RFC6830] for details. The use 548 of the Instance-ID in this LCAF type is to associate a multicast 549 forwarding entry for a given VPN. The instance-ID describes the 550 VPN and is registered to the mapping database system as a 3-tuple 551 of (Instance-ID, S-prefix, G-prefix). 553 Source MaskLen: the mask length of the source prefix that follows. 555 Group MaskLen: the mask length of the group prefix that follows. 557 AFI = x: x can be any AFI value from [AFI]. When a specific AFI has 558 its own encoding of a multicast address, this field must be either 559 a group address or a broadcast address. 561 Usage: This encoding can be used in EID records in Map-Requests, Map- 562 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 563 [LISP-DDT] is used as the mapping system mechanism, extended EIDs are 564 used in Map-Referral messages. 566 4.6. Traffic Engineering using Re-encapsulating Tunnels 568 For a given EID lookup into the mapping database, this LCAF format 569 can be returned to provide a list of locators in an explicit re- 570 encapsulation path. See [LISP-TE] for details. 572 Explicit Locator Path (ELP) Canonical Address Format: 574 0 1 2 3 575 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 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 | AFI = 16387 | Rsvd1 | Flags | 578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 | Type = 10 | Rsvd2 | n | 580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 581 | Rsvd3 |L|P|S| AFI = x | 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 583 | Reencap Hop 1 ... | 584 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 585 | Rsvd3 |L|P|S| AFI = x | 586 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 587 | Reencap Hop k ... | 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 Length value n: length in bytes of fields that follow. 592 Lookup bit (L): this is the Lookup bit used to indicate to the user 593 of the ELP to not use this address for encapsulation but to look 594 it up in the mapping database system to obtain an encapsulating 595 RLOC address. 597 RLOC-Probe bit (P): this is the RLOC-probe bit which means the 598 Reencap Hop allows RLOC-probe messages to be sent to it. When the 599 R-bit is set to 0, RLOC-probes must not be sent. When a Reencap 600 Hop is an anycast address then multiple physical Reencap Hops are 601 using the same RLOC address. In this case, RLOC-probes are not 602 needed because when the closest RLOC address is not reachable 603 another RLOC address can reachable. 605 Strict bit (S): this the strict bit which means the associated 606 Rencap Hop is required to be used. If this bit is 0, the 607 reencapsulator can skip this Reencap Hop and go to the next one in 608 the list. 610 AFI = x: x can be any AFI value from [AFI]. When a specific AFI has 611 its own encoding of a multicast address, this field must be either 612 a group address or a broadcast address. 614 Usage: This encoding can be used in RLOC records in Map-Requests, 615 Map-Replies, Map-Registers, and Map-Notify messages. This encoding 616 not need to be understood by the mapping system for mapping database 617 lookups since this LCAF type is not a lookup key. 619 4.7. Storing Security Data in the Mapping Database 621 When a locator in a locator-set has a security key associated with 622 it, this LCAF format will be used to encode key material. See 623 [LISP-DDT] for details. 625 Security Key Canonical Address Format: 627 0 1 2 3 628 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 629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 630 | AFI = 16387 | Rsvd1 | Flags | 631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 632 | Type = 11 | Rsvd2 | 6 + n | 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 | Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R| 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 | Key Length | Key Material ... | 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 638 | ... Key Material | 639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 640 | AFI = x | Locator Address ... | 641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 643 Length value n: length in bytes of fields that start with the Key 644 Material field. 646 Key Count: the Key Count field declares the number of Key sections 647 included in this LCAF. 649 Key Algorithm: the Algorithm field identifies the key's 650 cryptographic algorithm and specifies the format of the Public Key 651 field. 653 R bit: this is the revoke bit and, if set, it specifies that this 654 Key is being Revoked. 656 Key Length: this field determines the length in bytes of the Key 657 Material field. 659 Key Material: the Key Material field stores the key material. The 660 format of the key material stored depends on the Key Algorithm 661 field. 663 AFI = x: x can be any AFI value from [AFI].This is the locator 664 address that owns the encoded security key. 666 Usage: This encoding can be used in EID or RLOC records in Map- 667 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 668 LISP-DDT [LISP-DDT] is used as the mapping system mechanism, extended 669 EIDs are used in Map-Referral messages. 671 4.8. Source/Destination 2-Tuple Lookups 673 When both a source and destination address of a flow needs 674 consideration for different locator-sets, this 2-tuple key is used in 675 EID fields in LISP control messages. When the Source/Dest key is 676 registered to the mapping database, it can be encoded as a source- 677 prefix and destination-prefix. When the Source/Dest is used as a key 678 for a mapping database lookup the source and destination come from a 679 data packet. 681 Source/Dest Key Canonical Address Format: 683 0 1 2 3 684 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 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | AFI = 16387 | Rsvd1 | Flags | 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | Type = 12 | Rsvd2 | 4 + n | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | Reserved | Source-ML | Dest-ML | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 692 | AFI = x | Source-Prefix ... | 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 694 | AFI = x | Destination-Prefix ... | 695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 697 Length value n: length in bytes of fields that follow. 699 Reserved: must be set to zero and ignore on receipt. 701 Source-ML: the mask length of the source prefix that follows. 703 Dest-ML: the mask length of the destination prefix that follows. 705 AFI = x: x can be any AFI value from [AFI]. When a specific AFI has 706 its own encoding of a multicast address, this field must be either 707 a group address or a broadcast address. 709 Refer to [LISP-TE] for usage details. 711 Usage: This encoding can be used in EID records in Map-Requests, Map- 712 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 713 [LISP-DDT] is used as the mapping system mechanism, extended EIDs are 714 used in Map-Referral messages. 716 4.9. Replication List Entries for Multicast Forwarding 718 The Replication List Entry LCAF type is an encoding for a locator 719 being used for unicast replication according to the specification in 720 [LISP-RE]. This locator encoding is pointed to by a Multicast Info 721 LCAF Type and is registered by Re-encapsulating Tunnel Routers (RTRs) 722 that are participating in an overlay distribution tree. Each RTR 723 will register its locator address and its configured level in the 724 distribution tree. 726 Replication List Entry Address Format: 728 0 1 2 3 729 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 730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 731 | AFI = 16387 | Rsvd1 | Flags | 732 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 733 | Type = 13 | Rsvd2 | 4 + n | 734 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 735 | Rsvd3 | Rsvd4 | Level Value | 736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 737 | AFI = x | RTR/ETR #1 ... | 738 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 | Rsvd3 | Rsvd4 | Level Value | 740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 741 | AFI = x | RTR/ETR #n ... | 742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 744 Length value n: length in bytes of fields that follow. 746 Rsvd{1,2,3,4}: must be set to zero and ignore on receipt. 748 Level Value: this value is associated with the level within the 749 overlay distribution tree hierarchy where the RTR resides. The 750 level numbers are ordered from lowest value being close to the ITR 751 (meaning that ITRs replicate to level-0 RTRs) and higher levels 752 are further downstream on the distribution tree closer to ETRs of 753 multicast receiver sites. 755 AFI = x: x can be any AFI value from [AFI]. A specific AFI has its 756 own encoding of either a unicast or multicast locator address. 757 All RTR/ETR entries for the same level should be combined together 758 by a Map-Server to avoid searching through the entire multi-level 759 list of locator entries in a Map-Reply message. 761 Usage: This encoding can be used in RLOC records in Map-Requests, 762 Map-Replies, Map-Registers, and Map-Notify messages. 764 4.10. Applications for AFI List Type 766 4.10.1. Binding IPv4 and IPv6 Addresses 768 When header translation between IPv4 and IPv6 is desirable a LISP 769 Canonical Address can use the AFI List Type to carry multiple AFIs in 770 one LCAF AFI. 772 Address Binding LISP Canonical Address Format: 774 0 1 2 3 775 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 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 | AFI = 16387 | Rsvd1 | Flags | 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 779 | Type = 1 | Rsvd2 | 2 + 4 + 2 + 16 | 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 781 | AFI = 1 | IPv4 Address ... | 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 | ... IPv4 Address | AFI = 2 | 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 | IPv6 Address ... | 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 787 | ... IPv6 Address ... | 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 | ... IPv6 Address ... | 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 | ... IPv6 Address | 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 Length: length in bytes is fixed at 24 when IPv4 and IPv6 AFI 795 encoded addresses are used. 797 This type of address format can be included in a Map-Request when the 798 address is being used as an EID, but the Mapping Database System 799 lookup destination can use only the IPv4 address. This is so a 800 Mapping Database Service Transport System, such as LISP-ALT 801 [RFC6836], can use the Map-Request destination address to route the 802 control message to the desired LISP site. 804 Usage: This encoding can be used in EID or RLOC records in Map- 805 Requests, Map-Replies, Map-Registers, and Map-Notify messages. See 806 subsections in this section for specific use cases. 808 4.10.2. Layer-2 VPNs 810 When MAC addresses are stored in the LISP Mapping Database System, 811 the AFI List Type can be used to carry AFI 6. 813 MAC Address LISP Canonical Address Format: 815 0 1 2 3 816 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 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 | AFI = 16387 | Rsvd1 | Flags | 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 | Type = 1 | Rsvd2 | 2 + 6 | 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | AFI = 6 | Layer-2 MAC Address ... | 823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 | ... Layer-2 MAC Address | 825 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 827 Length: length in bytes is fixed at 8 when MAC address AFI encoded 828 addresses are used. 830 This address format can be used to connect layer-2 domains together 831 using LISP over an IPv4 or IPv6 core network to create a layer-2 VPN. 832 In this use-case, a MAC address is being used as an EID, and the 833 locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or 834 even another MAC address being used as an RLOC. 836 4.10.3. ASCII Names in the Mapping Database 838 If DNS names or URIs are stored in the LISP Mapping Database System, 839 the AFI List Type can be used to carry an ASCII string where it is 840 delimited by length 'n' of the LCAF Length encoding. 842 ASCII LISP Canonical Address Format: 844 0 1 2 3 845 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 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | AFI = 16387 | Rsvd1 | Flags | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Type = 1 | Rsvd2 | 2 + n | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | AFI = 17 | DNS Name or URI ... | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 Length value n: length in bytes AFI=17 field and the null-terminated 855 ASCII string (the last byte of 0 is included). 857 4.10.4. Using Recursive LISP Canonical Address Encodings 859 When any combination of above is desirable, the AFI List Type value 860 can be used to carry within the LCAF AFI another LCAF AFI. 862 Recursive LISP Canonical Address Format: 864 0 1 2 3 865 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 866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 867 | AFI = 16387 | Rsvd1 | Flags | 868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 869 | Type = 1 | Rsvd2 | 8 + 18 | 870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 | AFI = 16387 | Rsvd1 | Flags | 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | Type = 4 | Rsvd2 | 12 + 6 | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 | IP TOS, IPv6 QQS or Flow Label | Protocol | 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 | Local Port (lower-range) | Local Port (upper-range) | 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 | Remote Port (lower-range) | Remote Port (upper-range) | 880 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 881 | AFI = 1 | IPv4 Address ... | 882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 | ... IPv4 Address | 884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 886 Length: length in bytes is fixed at 18 when an AFI=1 IPv4 address is 887 included. 889 This format could be used by a Mapping Database Transport System, 890 such as LISP-ALT [RFC6836], where the AFI=1 IPv4 address is used as 891 an EID and placed in the Map-Request destination address by the 892 sending LISP system. The ALT system can deliver the Map-Request to 893 the LISP destination site independent of the Application Data Type 894 AFI payload values. When this AFI is processed by the destination 895 LISP site, it can return different locator-sets based on the type of 896 application or level of service that is being requested. 898 4.10.5. Compatibility Mode Use Case 900 A LISP system should use the AFI List Type format when sending to 901 LISP systems that do not support a particular LCAF Type used to 902 encode locators. This allows the receiving system to be able to 903 parse a locator address for encapsulation purposes. The list of AFIs 904 in an AFI List LCAF Type has no semantic ordering and a receiver 905 should parse each AFI element no matter what the ordering. 907 Compatibility Mode Address Format: 909 0 1 2 3 910 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 911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 | AFI = 16387 | Rsvd1 | Flags | 913 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 914 | Type = 1 | Rsvd2 | 8 + 14 + 6 | 915 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 916 | AFI = 16387 | Rsvd1 | Flags | 917 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 918 | Type = 5 | Rsvd2 | 12 + 2 | 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 920 |N| Latitude Degrees | Minutes | Seconds | 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 922 |E| Longitude Degrees | Minutes | Seconds | 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 924 | Altitude | 925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 926 | AFI = 0 | AFI = 1 | 927 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 928 | IPv4 Address | 929 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 If a system does not recognized the Geo Coordinate LCAF Type that is 932 accompanying a locator address, an encoder can include the Geo 933 Coordinate LCAF Type embedded in a AFI List LCAF Type where the AFI 934 in the Geo Coordinate LCAF is set to 0 and the AFI encoded next in 935 the list is encoded with a valid AFI value to identify the locator 936 address. 938 A LISP system is required to support the AFI List LCAF Type to use 939 this procedure. It would skip over 10 bytes of the Geo Coordinate 940 LCAF Type to get to the locator address encoding (an IPv4 locator 941 address). A LISP system that does support the Geo Coordinate LCAF 942 Type can support parsing the locator address within the Geo 943 Coordinate LCAF encoding or in the locator encoding that follows in 944 the AFI List LCAF. 946 5. Experimental LISP Canonical Address Applications 948 5.1. Convey Application Specific Data 950 When a locator-set needs to be conveyed based on the type of 951 application or the Per-Hop Behavior (PHB) of a packet, the 952 Application Data Type can be used. 954 Application Data LISP Canonical Address Format: 956 0 1 2 3 957 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 958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 959 | AFI = 16387 | Rsvd1 | Flags | 960 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 961 | Type = 4 | Rsvd2 | 12 + n | 962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 963 | IP TOS, IPv6 TC, or Flow Label | Protocol | 964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 965 | Local Port (lower-range) | Local Port (upper-range) | 966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 967 | Remote Port (lower-range) | Remote Port (upper-range) | 968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 969 | AFI = x | Address ... | 970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 972 Length value n: length in bytes of the AFI address that follows the 973 8-byte Application Data fields including the AFI field itself. 975 IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS 976 field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow 977 Label used in an IPv6 header. 979 Local Port/Remote Port Ranges: these fields are from the TCP, UDP, 980 or SCTP transport header. A range can be specified by using a 981 lower value and an upper value. When a single port is encoded, 982 the lower and upper value fields are the same. 984 AFI = x: x can be any AFI value from [AFI]. 986 The Application Data Canonical Address Type is used for an EID 987 encoding when an ITR wants a locator-set for a specific application. 988 When used for an RLOC encoding, the ETR is supplying a locator-set 989 for each specific application is has been configured to advertise. 991 Usage: This encoding can be used in EID records in Map-Requests, Map- 992 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 993 [LISP-DDT] is used as the mapping system mechanism, extended EIDs are 994 used in Map-Referral messages. This LCAF type is used as a lookup 995 key to the mapping system that can return a longest-match or exact- 996 match entry. 998 5.2. Generic Database Mapping Lookups 1000 When the LISP Mapping Database system holds information accessed by a 1001 generic formatted key (where the key is not the usual IPv4 or IPv6 1002 address), an opaque key may be desirable. 1004 Opaque Key LISP Canonical Address Format: 1006 0 1 2 3 1007 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 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 | AFI = 16387 | Rsvd1 | Flags | 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 | Type = 6 | Rsvd2 | 3 + n | 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1013 | Key Field Num | Key Wildcard Fields | Key . . . | 1014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1015 | . . . Key | 1016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1018 Length value n: length in bytes of the type's payload. The value n 1019 is the number of bytes that follow this Length field. 1021 Key Field Num: the number of fields (minus 1) the key can be broken 1022 up into. The width of the fields are fixed length. So for a key 1023 size of 8 bytes, with a Key Field Num of 4 allows 4 fields of 2 1024 bytes in length. Valid values for this field range from 0 to 15 1025 supporting a maximum of 16 field separations. 1027 Key Wildcard Fields: describes which fields in the key are not used 1028 as part of the key lookup. This wildcard encoding is a bitfield. 1029 Each bit is a don't-care bit for a corresponding field in the key. 1030 Bit 0 (the low-order bit) in this bitfield corresponds the first 1031 field, right-justified in the key, bit 1 the second field, and so 1032 on. When a bit is set in the bitfield it is a don't-care bit and 1033 should not be considered as part of the database lookup. When the 1034 entire 16-bits is set to 0, then all bits of the key are used for 1035 the database lookup. 1037 Key: the variable length key used to do a LISP Database Mapping 1038 lookup. The length of the key is the value n (shown above) minus 1039 3. 1041 Usage: This is an experimental type where the usage has not been 1042 defined yet. 1044 5.3. PETR Admission Control Functionality 1046 When a public PETR device wants to verify who is encapsulating to it, 1047 it can check for a specific nonce value in the LISP encapsulated 1048 packet. To convey the nonce to admitted ITRs or PITRs, this LCAF 1049 format is used in a Map-Register or Map-Reply locator-record. 1051 Nonce Locator Canonical Address Format: 1053 0 1 2 3 1054 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 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 | AFI = 16387 | Rsvd1 | Flags | 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 | Type = 8 | Rsvd2 | 4 + n | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1060 | Reserved | Nonce | 1061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1062 | AFI = x | Address ... | 1063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1065 Length value n: length in bytes of the AFI address that follows the 1066 Nonce field including the AFI field itself. 1068 Reserved: must be set to zero and ignore on receipt. 1070 Nonce: this is a nonce value returned by an ETR in a Map-Reply 1071 locator-record to be used by an ITR or PITR when encapsulating to 1072 the locator address encoded in the AFI field of this LCAF type. 1074 AFI = x: x can be any AFI value from [AFI]. 1076 Usage: This is an experimental type where the usage has not been 1077 defined yet. 1079 5.4. Data Model Encoding 1081 This type allows a JSON data model to be encoded either as an EID or 1082 RLOC. 1084 JSON Data Model Type Address Format: 1086 0 1 2 3 1087 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 1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1089 | AFI = 16387 | Rsvd1 | Flags | 1090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1091 | Type = 14 | Rsvd2 |B| 2 + n | 1092 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1093 | JSON length | JSON binary/text encoding ... | 1094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1095 | AFI = x | Optional Address ... | 1096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1098 Length value n: length in bytes of fields that follow. 1100 Rsvd{1,2}: must be set to zero and ignore on receipt. 1102 B bit: indicates that the JSON field is binary encoded according to 1103 [JSON-BINARY] when the bit is set to 1. Otherwise the encoding is 1104 based on text encoding according to [RFC4627]. 1106 JSON length: length in octets of the following 'JSON binary/text 1107 encoding' field. 1109 JSON binary/text encoding field: a variable length field that 1110 contains either binary or text encodings. 1112 AFI = x: x can be any AFI value from [AFI]. A specific AFI has its 1113 own encoding of either a unicast or multicast locator address. 1114 All RTR/ETR entries for the same level should be combined together 1115 by a Map-Server to avoid searching through the entire multi-level 1116 list of locator entries in a Map-Reply message. 1118 Usage: This is an experimental type where the usage has not been 1119 defined yet. 1121 5.5. Encoding Key/Value Address Pairs 1123 The Key/Value pair is for example useful for attaching attributes to 1124 other elements of LISP packets, such as EIDs or RLOCs. When 1125 attaching attributes to EIDs or RLOCs, it's necessary to distinguish 1126 between the element that should be used as EID or RLOC, and hence as 1127 key for lookups, and additional attributes. This is especially the 1128 case when the difference cannot be determined from the types of the 1129 elements, such as when two IP addresses are being used. 1131 Key/Value Pair Address Format: 1133 0 1 2 3 1134 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 1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1136 | AFI = 16387 | Rsvd1 | Flags | 1137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1138 | Type = 15 | Rsvd2 | n | 1139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1140 | AFI = x | Address as Key ... | 1141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1142 | AFI = x | Address as Value ... | 1143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1145 Length value n: length in bytes of fields that follow. 1147 Rsvd{1,2}: must be set to zero and ignore on receipt. 1149 AFI = x: x can be any AFI value from [AFI]. A specific AFI has its 1150 own encoding of either a unicast or multicast locator address. 1151 All RTR/ETR entries for the same level should be combined together 1152 by a Map-Server to avoid searching through the entire multi-level 1153 list of locator entries in a Map-Reply message. 1155 Address as Key: this AFI encoded address will be attached with the 1156 attributes encoded in "Address as Value" which follows this field. 1158 Address as Value: this AFI encoded address will be the attribute 1159 address that goes along with "Address as Key" which precedes this 1160 field. 1162 Usage: This is an experimental type where the usage has not been 1163 defined yet. 1165 5.6. Multiple Data-Planes 1167 Overlays are becoming popular in many parts of the network which have 1168 created an explosion of data-plane encapsulation headers. Since the 1169 LISP mapping system can hold many types of address formats, it can 1170 represent the encapsulation format supported by an RLOC as well. 1171 When an encapsulator receives a Map-Reply with an Encapsulation 1172 Format LCAF Type encoded in an RLOC-record, it can select an 1173 encapsulation format, that it can support, from any of the 1174 encapsulation protocols which have the bit set to 1 in this LCAF 1175 type. 1177 Encapsulation Format Address Format: 1179 0 1 2 3 1180 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 1181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1182 | AFI = 16387 | Rsvd1 | Flags | 1183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1184 | Type = 16 | Rsvd2 | 4 + n | 1185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 | Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L| 1187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1188 | AFI = x | Address ... | 1189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1191 Rsvd1/Rsvd2: must be set to zero and ignored on receipt. 1193 Length value n: length in bytes of the AFI address that follows the 1194 next 32-bits including the AFI field itself. 1196 Reserved-for-Future-Encapsulations: must be set to zero and ignored 1197 on receipt. This field will get bits allocated to future 1198 encapsulations, as they are created. 1200 L: The RLOCs listed in the AFI encoded addresses in the next longword 1201 can accept layer3 LISP encapsulation using destination UDP port 1202 4341 [RFC6830]. 1204 l: The RLOCs listed in the AFI encoded addresses in the next longword 1205 can accept layer2 LISP encapsulation using destination UDP port 1206 8472 [L2-LISP]. 1208 V: The RLOCs listed in the AFI encoded addresses in the next longword 1209 can accept VXLAN encapsulation using destination UDP port 4789 1210 [RFC7348]. 1212 v: The RLOCs listed in the AFI encoded addresses in the next longword 1213 can accept VXLAN-GPE encapsulation using destination UDP port 4790 1214 [GPE]. 1216 N: The RLOCs listed in the AFI encoded addresses in the next longword 1217 can accept NV-GRE encapsulation using IPv4/ IPv6 protocol number 1218 47 [NVGRE]. 1220 G: The RLOCs listed in the AFI encoded addresses in the next longword 1221 can accept GENEVE encapsulation using destination UDP port 6081 1222 [GENEVE]. 1224 U: The RLOCs listed in the AFI encoded addresses in the next longword 1225 can accept GUE encapsulation using destination UDP port TBD [GUE]. 1227 Usage: This encoding can be used in RLOC records in Map-Requests, 1228 Map-Replies, Map-Registers, and Map-Notify messages. 1230 6. Security Considerations 1232 There are no security considerations for this specification. The 1233 security considerations are documented for the protocols that use 1234 LISP Canonical Addressing. Refer to the those relevant 1235 specifications. 1237 The use of the Geo-Coordinates LCAF Type may raise physical privacy 1238 issues. It can be up to the mapping system, based on policy 1239 parameters, when this LCAF type is returned to a Map-Requester. 1241 7. IANA Considerations 1243 This document defines a canonical address format encoding used in 1244 LISP control messages and in the encoding of lookup keys for the LISP 1245 Mapping Database System. Such address format is based on a fixed AFI 1246 (16387) and a LISP LCAF Type field. 1248 The LISP LCAF Type field is an 8-bit field specific to the LISP 1249 Canonical Address formatted encodings, for which IANA is to create 1250 and maintain a new registry (as outlined in [RFC5226]) entitled "LISP 1251 LCAF Type". Initial values for the LISP LCAF Type registry are given 1252 below. Future assignments are to be made through expert review with 1253 a specification required publication. Assignments consist of a LISP 1254 LCAF Type name and its associated value: 1256 +-------+------------------------------+------------+ 1257 | Value | LISP LCAF Type Name | Definition | 1258 +-------+------------------------------+------------+ 1259 | 0 | Null Body Type | Section 3 | 1260 | | | | 1261 | 1 | AFI List Type | Section 3 | 1262 | | | | 1263 | 2 | Instance ID Type | Section 3 | 1264 | | | | 1265 | 3 | AS Number Type | Section 3 | 1266 | | | | 1267 | 5 | Geo Coordinates Type | Section 3 | 1268 | | | | 1269 | 7 | NAT-Traversal Type | Section 3 | 1270 | | | | 1271 | 9 | Multicast Info Type | Section 3 | 1272 | | | | 1273 | 10 | Explicit Locator Path Type | Section 3 | 1274 | | | | 1275 | 11 | Security Key Type | Section 3 | 1276 | | | | 1277 | 12 | Source/Dest Key Type | Section 3 | 1278 | | | | 1279 | 13 | Replication List Entry Type | Section 3 | 1280 +-------+------------------------------+------------+ 1282 Table 1: LISP LCAF Type Initial Values 1284 8. References 1286 8.1. Normative References 1288 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 1289 DOI 10.17487/RFC1700, October 1994, 1290 . 1292 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 1293 and E. Lear, "Address Allocation for Private Internets", 1294 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 1295 . 1297 [RFC4627] Crockford, D., "The application/json Media Type for 1298 JavaScript Object Notation (JSON)", RFC 4627, 1299 DOI 10.17487/RFC4627, July 2006, 1300 . 1302 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1303 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1304 DOI 10.17487/RFC5226, May 2008, 1305 . 1307 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 1308 Locator/ID Separation Protocol (LISP)", RFC 6830, 1309 DOI 10.17487/RFC6830, January 2013, 1310 . 1312 [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, 1313 "Locator/ID Separation Protocol Alternative Logical 1314 Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, 1315 January 2013, . 1317 [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, 1318 L., Sridhar, T., Bursell, M., and C. Wright, "Virtual 1319 eXtensible Local Area Network (VXLAN): A Framework for 1320 Overlaying Virtualized Layer 2 Networks over Layer 3 1321 Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, 1322 . 1324 8.2. Informative References 1326 [AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY 1327 NUMBERS http://www.iana.org/numbers.html, Febuary 2007. 1329 [GENEVE] Gross, J., Sridhar, T., Garg, P., Wright, C., Ganga, I., 1330 Agarwal, P., Duda, K., Dutt, D., and J. Hudson, "Geneve: 1331 Generic Network Virtualization Encapsulation", draft- 1332 gross-geneve-02 (work in progress). 1334 [GPE] Quinn, P., Agarwal, P., Fernando, R., Kreeger, L., 1335 Kreeger, L., Lewis, D., Maino, F., Smith, M., Yadav, N., 1336 Yong, L., Xu, X., Elzur, U., and P. Garg, "Generic 1337 Protocol Extension for VXLAN", draft-quinn-vxlan-gpe- 1338 03.txt (work in progress). 1340 [GUE] Herbert, T. and L. Yong, "Generic UDP Encapsulation", 1341 draft-herbert-gue-02.txt (work in progress). 1343 [JSON-BINARY] 1344 "Universal Binary JSON Specification", 1345 URL http://ubjson.org. 1347 [L2-LISP] Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2 1348 (L2) LISP Encapsulation Format", draft-smith-lisp- 1349 layer2-03.txt (work in progress). 1351 [LISP-DDT] 1352 Fuller, V., Lewis, D., and V. Ermagan, "LISP Delegated 1353 Database Tree", draft-ietf-lisp-ddt-01.txt (work in 1354 progress). 1356 [LISP-MRSIG] 1357 Farinacci, D. and M. Napierala, "LISP Control-Plane 1358 Multicast Signaling", draft-farinacci-lisp-mr-signaling- 1359 03.txt (work in progress). 1361 [LISP-NATT] 1362 Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, 1363 F., and C. White, "NAT traversal for LISP", draft-ermagan- 1364 lisp-nat-traversal-03.txt (work in progress). 1366 [LISP-RE] Coras, F., Cabellos-Aparicio, A., Domingo-Pascual, J., 1367 Maino, F., and D. Farinacci, "LISP Replication 1368 Engineering", draft-coras-lisp-re-03.txt (work in 1369 progress). 1371 [LISP-TE] Farinacci, D., Lahiri, P., and M. Kowal, "LISP Traffic 1372 Engineering Use-Cases", draft-farinacci-lisp-te-03.txt 1373 (work in progress). 1375 [NVGRE] Sridharan, M., Greenberg, A., Wang, Y., Garg, P., 1376 Venkataramiah, N., Duda, K., Ganga, I., Lin, G., Pearson, 1377 M., Thaler, P., and C. Tumuluri, "NVGRE: Network 1378 Virtualization using Generic Routing Encapsulation", 1379 draft-sridharan-virtualization-nvgre-06.txt (work in 1380 progress). 1382 [WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic 1383 System 1984", NIMA TR8350.2, January 2000, . 1386 Appendix A. Acknowledgments 1388 The authors would like to thank Vince Fuller, Gregg Schudel, Jesper 1389 Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for 1390 their technical and editorial commentary. 1392 The authors would like to thank Victor Moreno for discussions that 1393 lead to the definition of the Multicast Info LCAF type. 1395 The authors would like to thank Parantap Lahiri and Michael Kowal for 1396 discussions that lead to the definition of the Explicit Locator Path 1397 (ELP) LCAF type. 1399 The authors would like to thank Fabio Maino and Vina Ermagan for 1400 discussions that lead to the definition of the Security Key LCAF 1401 type. 1403 The authors would like to thank Albert Cabellos-Aparicio and Florin 1404 Coras for discussions that lead to the definition of the Replication 1405 List Entry LCAF type. 1407 Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for 1408 suggesting new LCAF types. 1410 Thanks also goes to Terry Manderson for assistance obtaining a LISP 1411 AFI value from IANA. 1413 Appendix B. Document Change Log 1415 B.1. Changes to draft-ietf-lisp-lcaf-11.txt 1417 o Submitted September 2015. 1419 o Reflecting comments from Prague LISP working group. 1421 o Readying document for a LISP LCAF registry, RFC publication, and 1422 for new use-cases that will be defined in the new charter. 1424 B.2. Changes to draft-ietf-lisp-lcaf-10.txt 1426 o Submitted June 2015. 1428 o Fix coauthor Job's contact information. 1430 B.3. Changes to draft-ietf-lisp-lcaf-09.txt 1432 o Submitted June 2015. 1434 o Fix IANA Considerations section to request a registry to allocate 1435 and track LCAF Type values. 1437 B.4. Changes to draft-ietf-lisp-lcaf-08.txt 1439 o Submitted April 2015. 1441 o Comment from Florin. The Application Data Type length field has a 1442 typo. The field should be labeled "12 + n" and not "8 + n". 1444 o Fix length fields in the sections titled "Using Recursive LISP 1445 Canonical Address Encodings", "Generic Database Mapping Lookups", 1446 and "Data Model Encoding". 1448 B.5. Changes to draft-ietf-lisp-lcaf-07.txt 1450 o Submitted December 2014. 1452 o Add a new LCAF Type called "Encapsulation Format" so decapsulating 1453 xTRs can inform encapsulating xTRs what data-plane encapsulations 1454 they support. 1456 B.6. Changes to draft-ietf-lisp-lcaf-06.txt 1458 o Submitted October 2014. 1460 o Make it clear how sorted RLOC records are done when LCAFs are used 1461 as the RLOC record. 1463 B.7. Changes to draft-ietf-lisp-lcaf-05.txt 1465 o Submitted May 2014. 1467 o Add a length field of the JSON payload that can be used for either 1468 binary or text encoding of JSON data. 1470 B.8. Changes to draft-ietf-lisp-lcaf-04.txt 1472 o Submitted January 2014. 1474 o Agreement among ELP implementors to have the AFI 16-bit field 1475 adjacent to the address. This will make the encoding consistent 1476 with all other LCAF type address encodings. 1478 B.9. Changes to draft-ietf-lisp-lcaf-03.txt 1480 o Submitted September 2013. 1482 o Updated references and author's affilations. 1484 o Added Instance-ID to the Multicast Info Type so there is relative 1485 ease in parsing (S,G) entries within a VPN. 1487 o Add port range encodings to the Application Data LCAF Type. 1489 o Add a new JSON LCAF Type. 1491 o Add Address Key/Value LCAF Type to allow attributes to be attached 1492 to an address. 1494 B.10. Changes to draft-ietf-lisp-lcaf-02.txt 1496 o Submitted March 2013. 1498 o Added new LCAF Type "Replication List Entry" to support LISP 1499 replication engineering use-cases. 1501 o Changed references to new LISP RFCs. 1503 B.11. Changes to draft-ietf-lisp-lcaf-01.txt 1505 o Submitted January 2013. 1507 o Change longitude range from 0-90 to 0-180 in section 4.4. 1509 o Added reference to WGS-84 in section 4.4. 1511 B.12. Changes to draft-ietf-lisp-lcaf-00.txt 1513 o Posted first working group draft August 2012. 1515 o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt. 1517 Authors' Addresses 1519 Dino Farinacci 1520 lispers.net 1521 San Jose, CA 1522 USA 1524 Email: farinacci@gmail.com 1526 Dave Meyer 1527 Brocade 1528 San Jose, CA 1529 USA 1531 Email: dmm@1-4-5.net 1533 Job Snijders 1534 NTT Communications 1535 Theodorus Majofskistraat 100 1536 Amsterdam 1065 SZ 1537 NL 1539 Email: job@ntt.net