idnits 2.17.1 draft-ietf-lisp-lcaf-22.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 28, 2016) is 2699 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'BCP160' is defined on line 1392, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Obsolete normative reference: RFC 6830 (Obsoleted by RFC 9300, RFC 9301) ** Obsolete normative reference: RFC 7159 (Obsoleted by RFC 8259) == Outdated reference: A later version (-19) exists of draft-ermagan-lisp-nat-traversal-11 == Outdated reference: A later version (-12) exists of draft-farinacci-lisp-te-11 == Outdated reference: A later version (-09) exists of draft-ietf-lisp-ddt-08 == Outdated reference: A later version (-29) exists of draft-ietf-lisp-sec-12 == Outdated reference: A later version (-02) exists of draft-portoles-lisp-eid-mobility-01 Summary: 3 errors (**), 0 flaws (~~), 8 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: June 1, 2017 Brocade 6 J. Snijders 7 NTT 8 November 28, 2016 10 LISP Canonical Address Format (LCAF) 11 draft-ietf-lisp-lcaf-22 13 Abstract 15 This document defines a canonical address format encoding used in 16 LISP control messages and in the encoding of lookup keys for the LISP 17 Mapping Database System. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in [RFC2119]. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on June 1, 2017. 42 Copyright Notice 44 Copyright (c) 2016 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 61 3. LISP Canonical Address Format Encodings . . . . . . . . . . . 5 62 4. LISP Canonical Address Applications . . . . . . . . . . . . . 8 63 4.1. Segmentation using LISP . . . . . . . . . . . . . . . . . 8 64 4.2. Carrying AS Numbers in the Mapping Database . . . . . . . 9 65 4.3. Assigning Geo Coordinates to Locator Addresses . . . . . 11 66 4.4. NAT Traversal Scenarios . . . . . . . . . . . . . . . . . 13 67 4.5. Multicast Group Membership Information . . . . . . . . . 15 68 4.6. Traffic Engineering using Re-encapsulating Tunnels . . . 17 69 4.7. Storing Security Data in the Mapping Database . . . . . . 18 70 4.8. Source/Destination 2-Tuple Lookups . . . . . . . . . . . 20 71 4.9. Replication List Entries for Multicast Forwarding . . . . 22 72 4.10. Applications for AFI List Type . . . . . . . . . . . . . 23 73 4.10.1. Binding IPv4 and IPv6 Addresses . . . . . . . . . . 23 74 4.10.2. Layer-2 VPNs . . . . . . . . . . . . . . . . . . . . 24 75 4.10.3. ASCII Names in the Mapping Database . . . . . . . . 25 76 4.10.4. Using Recursive LISP Canonical Address Encodings . . 26 77 4.10.5. Compatibility Mode Use Case . . . . . . . . . . . . 27 78 5. Experimental LISP Canonical Address Applications . . . . . . 28 79 5.1. Convey Application Specific Data . . . . . . . . . . . . 29 80 5.2. Generic Database Mapping Lookups . . . . . . . . . . . . 30 81 5.3. PETR Admission Control Functionality . . . . . . . . . . 32 82 5.4. Data Model Encoding . . . . . . . . . . . . . . . . . . . 33 83 5.5. Encoding Key/Value Address Pairs . . . . . . . . . . . . 34 84 5.6. Multiple Data-Planes . . . . . . . . . . . . . . . . . . 35 85 6. Security Considerations . . . . . . . . . . . . . . . . . . . 37 86 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 87 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 88 8.1. Normative References . . . . . . . . . . . . . . . . . . 39 89 8.2. Informative References . . . . . . . . . . . . . . . . . 40 90 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 42 91 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 42 92 B.1. Changes to draft-ietf-lisp-lcaf-22.txt . . . . . . . . . 42 93 B.2. Changes to draft-ietf-lisp-lcaf-21.txt . . . . . . . . . 43 94 B.3. Changes to draft-ietf-lisp-lcaf-20.txt . . . . . . . . . 43 95 B.4. Changes to draft-ietf-lisp-lcaf-19.txt . . . . . . . . . 43 96 B.5. Changes to draft-ietf-lisp-lcaf-18.txt . . . . . . . . . 43 97 B.6. Changes to draft-ietf-lisp-lcaf-17.txt . . . . . . . . . 43 98 B.7. Changes to draft-ietf-lisp-lcaf-16.txt . . . . . . . . . 43 99 B.8. Changes to draft-ietf-lisp-lcaf-15.txt . . . . . . . . . 44 100 B.9. Changes to draft-ietf-lisp-lcaf-14.txt . . . . . . . . . 44 101 B.10. Changes to draft-ietf-lisp-lcaf-13.txt . . . . . . . . . 44 102 B.11. Changes to draft-ietf-lisp-lcaf-12.txt . . . . . . . . . 44 103 B.12. Changes to draft-ietf-lisp-lcaf-11.txt . . . . . . . . . 44 104 B.13. Changes to draft-ietf-lisp-lcaf-10.txt . . . . . . . . . 44 105 B.14. Changes to draft-ietf-lisp-lcaf-09.txt . . . . . . . . . 45 106 B.15. Changes to draft-ietf-lisp-lcaf-08.txt . . . . . . . . . 45 107 B.16. Changes to draft-ietf-lisp-lcaf-07.txt . . . . . . . . . 45 108 B.17. Changes to draft-ietf-lisp-lcaf-06.txt . . . . . . . . . 45 109 B.18. Changes to draft-ietf-lisp-lcaf-05.txt . . . . . . . . . 45 110 B.19. Changes to draft-ietf-lisp-lcaf-04.txt . . . . . . . . . 45 111 B.20. Changes to draft-ietf-lisp-lcaf-03.txt . . . . . . . . . 46 112 B.21. Changes to draft-ietf-lisp-lcaf-02.txt . . . . . . . . . 46 113 B.22. Changes to draft-ietf-lisp-lcaf-01.txt . . . . . . . . . 46 114 B.23. Changes to draft-ietf-lisp-lcaf-00.txt . . . . . . . . . 46 115 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 117 1. Introduction 119 The LISP architecture and protocols [RFC6830] introduces two new 120 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators 121 (RLOCs). To provide flexibility for current and future applications, 122 these values can be encoded in LISP control messages using a general 123 syntax that includes Address Family Identifier (AFI), length, and 124 value fields. 126 Currently defined AFIs include IPv4 and IPv6 addresses, which are 127 formatted according to code-points assigned in [AFI] as follows: 129 IPv4 Encoded Address: 131 0 1 2 3 132 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 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | AFI = 1 | IPv4 Address ... | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | ... IPv4 Address | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 IPv6 Encoded Address: 140 0 1 2 3 141 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 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 | AFI = 2 | IPv6 Address ... | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | ... IPv6 Address ... | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | ... IPv6 Address ... | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | ... IPv6 Address ... | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | ... IPv6 Address | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 This document describes the currently-defined AFIs the LISP protocol 155 uses along with their encodings and introduces the LISP Canonical 156 Address Format (LCAF) that can be used to define the LISP-specific 157 encodings for arbitrary AFI values. 159 Specific detail uses for the LCAF types defined in this document can 160 be found in the use-case documents that use them. The same LCAF type 161 may be used by more than one use-case document. As an experimental 162 specification, this work is by definition, incomplete. The LCAF 163 types defined in this document are to support experimentation and 164 intended for cautious use in self-contained environments in support 165 of the corresponding use-case documents. This document provides 166 assignment for an initial set of approved LCAF Types (registered with 167 IANA) and additional unapproved LCAF Types [RFC6830]. The unapproved 168 LCAF encodings are defined to support further study and 169 experimentation. 171 2. Definition of Terms 173 Address Family Identifier (AFI): a term used to describe an address 174 encoding in a packet. Address families are defined for IPv4 and 175 IPv6. See [AFI] and [RFC3232] for details. The reserved AFI 176 value of 0 is used in this specification to indicate an 177 unspecified encoded address where the length of the address is 0 178 bytes following the 16-bit AFI value of 0. 180 Unspecified Address Format: 182 0 1 2 3 183 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 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | AFI = 0 | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit (for IPv6) value 189 used in the source and destination address fields of the first 190 (most inner) LISP header of a packet. The host obtains a 191 destination EID the same way it obtains a destination address 192 today, for example through a DNS lookup or SIP exchange. The 193 source EID is obtained via existing mechanisms used to set a 194 host's "local" IP address. An EID is allocated to a host from an 195 EID-prefix block associated with the site where the host is 196 located. An EID can be used by a host to refer to other hosts. 198 Routing Locator (RLOC): the IPv4 or IPv6 address of an egress 199 tunnel router (ETR). It is the output of a EID-to-RLOC mapping 200 lookup. An EID maps to one or more RLOCs. Typically, RLOCs are 201 numbered from topologically aggregatable blocks that are assigned 202 to a site at each point to which it attaches to the global 203 Internet; where the topology is defined by the connectivity of 204 provider networks, RLOCs can be thought of as Provider-Assigned 205 (PA) addresses. Multiple RLOCs can be assigned to the same ETR 206 device or to multiple ETR devices at a site. 208 3. LISP Canonical Address Format Encodings 210 IANA has assigned AFI value 16387 (0x4003) to the LISP architecture 211 and protocols. This specification defines the encoding format of the 212 LISP Canonical Address (LCA). This section defines all types for 213 which an initial allocation in the LISP-LCAF registry is requested. 214 See IANA Considerations section for the complete list of such types. 216 The Address Family AFI definitions from [AFI] only allocate code- 217 points for the AFI value itself. The length of the address or entity 218 that follows is not defined and is implied based on conventional 219 experience. When the LISP protocol uses LCAF definitions from this 220 document, the AFI-based address lengths are specified in this 221 document. When new LCAF definitions are defined in other use case 222 documents, the AFI-based address lengths for any new AFI encoded 223 addresses are specified in those documents. 225 The first 6 bytes of an LISP Canonical Address are followed by a 226 variable number of fields of variable length: 228 0 1 2 3 229 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 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | AFI = 16387 | Rsvd1 | Flags | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Type | Rsvd2 | Length | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | . . . | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 238 Rsvd1/Rsvd2: these 8-bit fields are reserved for future use and MUST 239 be transmitted as 0 and ignored on receipt. 241 Flags: this 8-bit field is for future definition and use. For now, 242 set to zero on transmission and ignored on receipt. 244 Type: this 8-bit field is specific to the LISP Canonical Address 245 formatted encodings. Currently allocated (both approved and 246 unapproved) values are: 248 Type 0: Null Body Type 250 Type 1: AFI List Type 252 Type 2: Instance ID Type 254 Type 3: AS Number Type 256 Type 4: Application Data Type 258 Type 5: Geo Coordinates Type 260 Type 6: Opaque Key Type 262 Type 7: NAT-Traversal Type 264 Type 8: Nonce Locator Type 266 Type 9: Multicast Info Type 268 Type 10: Explicit Locator Path Type 270 Type 11: Security Key Type 272 Type 12: Source/Dest Key Type 273 Type 13: Replication List Entry Type 275 Type 14: JSON Data Model Type 277 Type 15: Key/Value Address Pair Type 279 Type 16: Encapsulation Format Type 281 Length: this 16-bit field is in units of bytes and covers all of the 282 LISP Canonical Address payload, starting and including the byte 283 after the Length field. When including the AFI, an LCAF encoded 284 address will have a minimum length of 8 bytes when the Length 285 field is 0. The 8 bytes include the AFI, Flags, Type, Rsvd1, 286 Rsvd2, and Length fields. When the AFI is not next to an encoded 287 address in a control message, then the encoded address will have a 288 minimum length of 6 bytes when the Length field is 0. The 6 bytes 289 include the Flags, Type, Rsvd1, Rsvd2, and Length fields. 291 [RFC6830] states RLOC records based on an IP address are sorted when 292 encoded in control messages so the locator-set has consistent order 293 across all xTRs for a given EID. The sort order is based on sort-key 294 {afi, RLOC-address}. When an RLOC based on an IP address is LCAF 295 encoded, the sort-key is {afi, LCAF-Type}. Therefore, when a locator- 296 set has a mix of AFI records and LCAF records, they are ordered from 297 smallest to largest AFI value. 299 4. LISP Canonical Address Applications 301 The following sections define the LCAF for the currently approved 302 initial set of Type values. 304 4.1. Segmentation using LISP 306 When multiple organizations inside of a LISP site are using private 307 addresses [RFC1918] as EID-prefixes, their address spaces must remain 308 segregated due to possible address duplication. An Instance ID in 309 the address encoding can aid in making the entire AFI-based address 310 unique. 312 Another use for the Instance ID LISP Canonical Address Format is when 313 creating multiple segmented VPNs inside of a LISP site where keeping 314 EID-prefix based subnets is desirable. 316 Instance ID LISP Canonical Address Format: 318 0 1 2 3 319 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 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | AFI = 16387 | Rsvd1 | Flags | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 | Type = 2 | IID mask-len | Length | 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 | Instance ID | 326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 327 | AFI = x | Address ... | 328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 IID mask-len: if the AFI is set to 0, then this format is not 331 encoding an extended EID-prefix but rather an instance-ID range 332 where the 'IID mask-len' indicates the number of high-order bits 333 used in the Instance ID field for the range. The low-order bits 334 of the Instance ID field must be 0. 336 Length: length in bytes starting and including the byte after this 337 Length field. 339 Instance ID: the low-order 24-bits that can go into a LISP data 340 header when the I-bit is set. See [RFC6830] for details. The 341 reason for the length difference is so that the maximum number of 342 instances supported per mapping system is 2^32 while conserving 343 space in the LISP data header. This comes at the expense of 344 limiting the maximum number of instances per xTR to 2^24. If an 345 xTR is configured with multiple instance-IDs where the value in 346 the high-order 8 bits are the same, then the low-order 24 bits 347 MUST be unique. 349 AFI = x: x can be any AFI value from [AFI]. 351 This LISP Canonical Address Type can be used to encode either EID or 352 RLOC addresses. 354 Usage: When used as a lookup key, the EID is regarded as an extended- 355 EID in the mapping system. This encoding is used in EID records in 356 Map-Requests, Map-Replies, Map-Registers, and Map-Notify messages. 357 When LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system 358 mechanism, extended EIDs are used in Map-Referral messages. 360 4.2. Carrying AS Numbers in the Mapping Database 362 When an AS number is stored in the LISP Mapping Database System for 363 either policy or documentation reasons, it can be encoded in a LISP 364 Canonical Address. 366 AS Number LISP Canonical Address Format: 368 0 1 2 3 369 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 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | AFI = 16387 | Rsvd1 | Flags | 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 | Type = 3 | Rsvd2 | Length | 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 | AS Number | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | AFI = x | Address ... | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 Length: length in bytes starting and including the byte after this 381 Length field. 383 AS Number: the 32-bit AS number of the autonomous system that has 384 been assigned to either the EID or RLOC that follows. 386 AFI = x: x can be any AFI value from [AFI]. 388 The AS Number Canonical Address Type can be used to encode either EID 389 or RLOC addresses. The former is used to describe the LISP-ALT AS 390 number the EID-prefix for the site is being carried for. The latter 391 is used to describe the AS that is carrying RLOC based prefixes in 392 the underlying routing system. 394 Usage: This encoding can be used in EID or RLOC records in Map- 395 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 396 LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, 397 extended EIDs are used in Map-Referral messages. 399 4.3. Assigning Geo Coordinates to Locator Addresses 401 If an ETR desires to send a Map-Reply describing the Geo Coordinates 402 for each locator in its locator-set, it can use the Geo Coordinate 403 Type to convey physical location information. 405 Coordinates are specified using the WGS-84 (World Geodetic System) 406 reference coordinate system [WGS-84]. 408 Geo Coordinate LISP Canonical Address Format: 410 0 1 2 3 411 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 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | AFI = 16387 | Rsvd1 | Flags | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | Type = 5 | Rsvd2 | Length | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 |N| Latitude Degrees | Minutes | Seconds | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 |E| Longitude Degrees | Minutes | Seconds | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Altitude | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | AFI = x | Address ... | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 Length: length in bytes starting and including the byte after this 427 Length field. 429 N: When set to 1 means North, otherwise South. 431 Latitude Degrees: Valid values range from 0 to 90 degrees above or 432 below the equator (northern or southern hemisphere, respectively). 434 Latitude Minutes: Valid values range from 0 to 59. 436 Latitude Seconds: Valid values range from 0 to 59. 438 E: When set to 1 means East, otherwise West. 440 Longitude Degrees: Valid values are from 0 to 180 degrees right or 441 left of the Prime Meridian. 443 Longitude Minutes: Valid values range from 0 to 59. 445 Longitude Seconds: Valid values range from 0 to 59. 447 Altitude: Height relative to sea level in meters. This is a two's 448 complement signed integer meaning that the altitude could be below 449 sea level. A value of 0x7fffffff indicates no Altitude value is 450 encoded. 452 AFI = x: x can be any AFI value from [AFI]. 454 The Geo Coordinates Canonical Address Type can be used to encode 455 either EID or RLOC addresses. When used for EID encodings, you can 456 determine the physical location of an EID along with the topological 457 location by observing the locator-set. 459 Usage: This encoding can be used in EID or RLOC records in Map- 460 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 461 LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, 462 extended EIDs are used in Map-Referral messages. 464 The use of the Geo-Coordinates LCAF encoding raises privacy issues as 465 location information is privacy sensitive, and possibly unexpectedly 466 privacy sensitive information may be conveyed, e.g. if the location 467 information corresponds to a router located in a person's home. 468 Therefore, this encoding should not be used unless needed for 469 operation of a LISP deployment. Before electing to utilize this 470 encoding, care should be taken to ensure the appropriate policies are 471 being used by the EID for controlling the conveyed information. 473 4.4. NAT Traversal Scenarios 475 When a LISP system is conveying global address and mapped port 476 information when traversing through a NAT device, the NAT-Traversal 477 LCAF Type is used. See [I-D.ermagan-lisp-nat-traversal] for details. 479 NAT-Traversal Canonical Address Format: 481 0 1 2 3 482 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 483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 484 | AFI = 16387 | Rsvd1 | Flags | 485 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 486 | Type = 7 | Rsvd2 | Length | 487 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 488 | MS UDP Port Number | ETR UDP Port Number | 489 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 490 | AFI = x | Global ETR RLOC Address ... | 491 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 492 | AFI = x | MS RLOC Address ... | 493 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 494 | AFI = x | Private ETR RLOC Address ... | 495 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 496 | AFI = x | RTR RLOC Address 1 ... | 497 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 498 | AFI = x | RTR RLOC Address k ... | 499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 501 Length: length in bytes starting and including the byte after this 502 Length field. 504 MS UDP Port Number: this is the UDP port number of the Map-Server 505 and is set to 4342. 507 ETR UDP Port Number: this is the port number returned to a LISP 508 system which was copied from the source port from a packet that 509 has flowed through a NAT device. 511 AFI = x: x can be any AFI value from [AFI]. 513 Global ETR RLOC Address: this is an address known to be globally 514 unique built by NAT-traversal functionality in a LISP router. 516 MS RLOC Address: this is the address of the Map-Server used in the 517 destination RLOC of a packet that has flowed through a NAT device. 519 Private ETR RLOC Address: this is an address known to be a private 520 address inserted in this LCAF by a LISP router that resides on the 521 private side of a NAT device. 523 RTR RLOC Address: this is an encapsulation address used by an ITR or 524 PITR which resides behind a NAT device. This address is known to 525 have state in a NAT device so packets can flow from it to the LISP 526 ETR behind the NAT. There can be one or more NAT Reencapsulating 527 Tunnel Router (RTR) [I-D.ermagan-lisp-nat-traversal] addresses 528 supplied in these set of fields. The number of RTRs encoded is 529 determined by parsing each field. When there are no RTRs 530 supplied, the RTR fields can be omitted and reflected by the LCAF 531 length field or an AFI of 0 can be used to indicate zero RTRs 532 encoded. 534 Usage: This encoding can be used in Info-Request and Info-Reply 535 messages. The mapping system does not store this information. The 536 information is used by an xTR and Map-Server to convey private and 537 public address information when traversing NAT and firewall devices. 539 Care should be taken to protect privacy against the adverse use of a 540 Global or Private ETR RLOC Address by ensuring policy controls are 541 used during EID registrations that use this LCAF Type in RLOC- 542 records. Refer to the use case documents for additional information. 544 4.5. Multicast Group Membership Information 546 Multicast group information can be published in the mapping database. 547 So a lookup on a group address EID can return a replication list of 548 RLOC group addresses or RLOC unicast addresses. The intent of this 549 type of unicast replication is to deliver packets to multiple ETRs at 550 receiver LISP multicast sites. The locator-set encoding for this EID 551 record type can be a list of ETRs when they each register with "Merge 552 Semantics". The encoding can be a typical AFI-encoded locator 553 address. When an RTR list is being registered (with multiple levels 554 according to [I-D.coras-lisp-re]), the Replication List Entry LCAF 555 type is used for locator encoding. 557 This LCAF encoding can be used to send broadcast packets to all 558 members of a subnet when an EID is away from its home subnet 559 location. 561 Multicast Info Canonical Address Format: 563 0 1 2 3 564 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 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | AFI = 16387 | Rsvd1 | Flags | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | Type = 9 | Rsvd2 | Length | 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 | Instance-ID | 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | Reserved | Source MaskLen| Group MaskLen | 573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 574 | AFI = x | Source/Subnet Address ... | 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | AFI = x | Group Address ... | 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 Length: length in bytes starting and including the byte after this 580 Length field. 582 Reserved: must be set to zero and ignored on receipt. 584 Instance ID: the low-order 24-bits that can go into a LISP data 585 header when the I-bit is set. See [RFC6830] for details. The use 586 of the Instance-ID in this LCAF type is to associate a multicast 587 forwarding entry for a given VPN. The instance-ID describes the 588 VPN and is registered to the mapping database system as a 3-tuple 589 of (Instance-ID, S-prefix, G-prefix). 591 Source MaskLen: the mask length of the source prefix that follows. 592 The length is the number of high-order mask bits set. 594 Group MaskLen: the mask length of the group prefix that follows. 595 The length is the number of high-order mask bits set. 597 AFI = x: x can be any AFI value from [AFI]. When a specific address 598 family has a multicast address semantic, this field must be either 599 a group address or a broadcast address. 601 Source/Subnet Address: is the source address or prefix for encoding 602 a (S,G) multicast entry. 604 Group Address: is the group address or group prefix for encoding 605 (S,G) or (*,G) multicast entries. 607 Usage: This encoding can be used in EID records in Map-Requests, Map- 608 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 609 [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended 610 EIDs are used in Map-Referral messages. 612 4.6. Traffic Engineering using Re-encapsulating Tunnels 614 For a given EID lookup into the mapping database, this LCAF can be 615 returned to provide a list of locators in an explicit re- 616 encapsulation path. See [I-D.farinacci-lisp-te] for details. 618 Explicit Locator Path (ELP) Canonical Address Format: 620 0 1 2 3 621 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 622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 623 | AFI = 16387 | Rsvd1 | Flags | 624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 625 | Type = 10 | Rsvd2 | Length | 626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 627 | Rsvd3 |L|P|S| AFI = x | 628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 | Reencap Hop 1 ... | 630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 631 | Rsvd3 |L|P|S| AFI = x | 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 633 | Reencap Hop k ... | 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 Length: length in bytes starting and including the byte after this 637 Length field. 639 Rsvd3: this field is reserved for future use and MUST be transmitted 640 as 0 and ignored on receipt. 642 Lookup bit (L): this is the Lookup bit used to indicate to the user 643 of the ELP to not use this address for encapsulation but to look 644 it up in the mapping database system to obtain an encapsulating 645 RLOC address. 647 RLOC-Probe bit (P): this is the RLOC-probe bit which means the 648 Reencap Hop allows RLOC-probe messages to be sent to it. When the 649 R-bit is set to 0, RLOC-probes must not be sent. When a Reencap 650 Hop is an anycast address then multiple physical Reencap Hops are 651 using the same RLOC address. In this case, RLOC-probes are not 652 needed because when the closest RLOC address is not reachable 653 another RLOC address can be reachable. 655 Strict bit (S): this is the strict bit which means the associated 656 Reencap Hop is required to be used. If this bit is 0, the 657 reencapsulator can skip this Reencap Hop and go to the next one in 658 the list. 660 AFI = x: x can be any AFI value from [AFI]. When a specific AFI has 661 its own encoding of a multicast address, this field must be either 662 a group address or a broadcast address. 664 Usage: This encoding can be used in RLOC records in Map-Requests, 665 Map-Replies, Map-Registers, and Map-Notify messages. This encoding 666 does not need to be understood by the mapping system for mapping 667 database lookups since this LCAF type is not a lookup key. 669 4.7. Storing Security Data in the Mapping Database 671 When a locator in a locator-set has a security key associated with 672 it, this LCAF will be used to encode key material. See 673 [I-D.ietf-lisp-ddt] for details. 675 Security Key Canonical Address Format: 677 0 1 2 3 678 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 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 680 | AFI = 16387 | Rsvd1 | Flags | 681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 | Type = 11 | Rsvd2 | Length | 683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 684 | Key Count | Rsvd3 | Key Algorithm | Rsvd4 |R| 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | Key Length | Key Material ... | 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | ... Key Material | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | AFI = x | Locator Address ... | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 Length: length in bytes starting and including the byte after this 694 Length field. 696 Key Count: the Key Count field declares the number of Key sections 697 included in this LCAF. A key section is made up of "Key Length" 698 and "Key Material" fields. 700 Rsvd3: this field is reserved for future use and MUST be transmitted 701 as 0 and ignored on receipt. 703 Key Algorithm: the Algorithm field identifies the key's 704 cryptographic algorithm and specifies the format of the Public Key 705 field. Refer to the [I-D.ietf-lisp-ddt] and 706 [I-D.ietf-lisp-crypto] use cases for definitions of this field. 708 Rsvd4: this field is reserved for future use and MUST be transmitted 709 as 0 and ignored on receipt. 711 R bit: this is the revoke bit and, if set, it specifies that this 712 Key is being Revoked. 714 Key Length: this field determines the length in bytes of the Key 715 Material field. 717 Key Material: the Key Material field stores the key material. The 718 format of the key material stored depends on the Key Algorithm 719 field. 721 AFI = x: x can be any AFI value from [AFI]. This is the locator 722 address that owns the encoded security key. 724 Usage: This encoding can be used in EID or RLOC records in Map- 725 Requests, Map-Replies, Map-Registers, and Map-Notify messages. When 726 LISP-DDT [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, 727 extended EIDs are used in Map-Referral messages. 729 4.8. Source/Destination 2-Tuple Lookups 731 When both a source and destination address of a flow need 732 consideration for different locator-sets, this 2-tuple key is used in 733 EID fields in LISP control messages. When the Source/Dest key is 734 registered to the mapping database, it can be encoded as a source- 735 prefix and destination-prefix. When the Source/Dest is used as a key 736 for a mapping database lookup the source and destination come from a 737 data packet. 739 Source/Dest Key Canonical Address Format: 741 0 1 2 3 742 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 743 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 744 | AFI = 16387 | Rsvd1 | Flags | 745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 746 | Type = 12 | Rsvd2 | Length | 747 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 748 | Reserved | Source-ML | Dest-ML | 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 | AFI = x | Source-Prefix ... | 751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 752 | AFI = y | Destination-Prefix ... | 753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 755 Length: length in bytes starting and including the byte after this 756 Length field. 758 Reserved: must be set to zero and ignore on receipt. 760 Source-ML: the mask length of the source prefix that follows. The 761 length is the number of high-order mask bits set. 763 Dest-ML: the mask length of the destination prefix that follows. 764 The length is the number of high-order mask bits set. 766 AFI = x: x can be any AFI value from [AFI]. 768 AFI = y: y can be any AFI value from [AFI]. When a specific address 769 family has a multicast address semantic, this field must be either 770 a group address or a broadcast address. 772 Usage: This encoding can be used in EID records in Map-Requests, Map- 773 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 774 [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended 775 EIDs are used in Map-Referral messages. Refer to 776 [I-D.farinacci-lisp-te] for usage details of this LCAF type. 778 4.9. Replication List Entries for Multicast Forwarding 780 The Replication List Entry LCAF type is an encoding for a locator 781 being used for unicast replication according to the specification in 782 [I-D.coras-lisp-re]. This locator encoding is pointed to by a 783 Multicast Info LCAF Type and is registered by Re-encapsulating Tunnel 784 Routers (RTRs) that are participating in an overlay distribution 785 tree. Each RTR will register its locator address and its configured 786 level in the distribution tree. 788 Replication List Entry Address Format: 790 0 1 2 3 791 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 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 793 | AFI = 16387 | Rsvd1 | Flags | 794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 795 | Type = 13 | Rsvd2 | Length | 796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 797 | Rsvd3 | Rsvd4 | Level Value | 798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 799 | AFI = x | RTR/ETR #1 ... | 800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 801 | Rsvd3 | Rsvd4 | Level Value | 802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 803 | AFI = x | RTR/ETR #n ... | 804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 Length: length in bytes starting and including the byte after this 807 Length field. 809 Rsvd3/Rsvd4: must be set to zero and ignore on receipt. 811 Level Value: this value is associated with the level within the 812 overlay distribution tree hierarchy where the RTR resides. The 813 level numbers are ordered from lowest value being close to the ITR 814 (meaning that ITRs replicate to level-0 RTRs) and higher levels 815 are further downstream on the distribution tree closer to ETRs of 816 multicast receiver sites. 818 AFI = x: x can be any AFI value from [AFI]. A specific AFI has its 819 own encoding of either a unicast or multicast locator address. 820 For efficiency reasons, all RTR/ETR entries for the same level 821 should be combined together by a Map-Server to avoid searching 822 through the entire multi-level list of locator entries in a Map- 823 Reply message. 825 Usage: This encoding can be used in RLOC records in Map-Requests, 826 Map-Replies, Map-Registers, and Map-Notify messages. 828 4.10. Applications for AFI List Type 830 4.10.1. Binding IPv4 and IPv6 Addresses 832 When header translation between IPv4 and IPv6 is desirable a LISP 833 Canonical Address can use the AFI List Type to carry a variable 834 number of AFIs in one LCAF AFI. 836 Address Binding LISP Canonical Address Format: 838 0 1 2 3 839 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 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 841 | AFI = 16387 | Rsvd1 | Flags | 842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 843 | Type = 1 | Rsvd2 | Length | 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 | AFI = 1 | IPv4 Address ... | 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | ... IPv4 Address | AFI = 2 | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | IPv6 Address ... | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | ... IPv6 Address ... | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 | ... IPv6 Address ... | 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 | ... IPv6 Address | 856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 858 Length: length in bytes starting and including the byte after this 859 Length field. 861 This type of address format can be included in a Map-Request when the 862 address is being used as an EID, but the Mapping Database System 863 lookup destination can use only the IPv4 address. This is so a 864 Mapping Database Service Transport System, such as LISP-ALT 865 [RFC6836], can use the Map-Request destination address to route the 866 control message to the desired LISP site. 868 Usage: This encoding can be used in EID or RLOC records in Map- 869 Requests, Map-Replies, Map-Registers, and Map-Notify messages. See 870 subsections in this section for specific use cases. 872 4.10.2. Layer-2 VPNs 874 When MAC addresses are stored in the LISP Mapping Database System, 875 the AFI List Type can be used to carry AFI 6. 877 MAC Address LISP Canonical Address Format: 879 0 1 2 3 880 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 881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 882 | AFI = 16387 | Rsvd1 | Flags | 883 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 884 | Type = 1 | Rsvd2 | Length | 885 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 886 | AFI = 6 | Layer-2 MAC Address ... | 887 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 888 | ... Layer-2 MAC Address | 889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 891 Length: length in bytes starting and including the byte after this 892 Length field. 894 This address format can be used to connect layer-2 domains together 895 using LISP over an IPv4 or IPv6 core network to create a layer-2 VPN. 896 In this use case, a MAC address is being used as an EID, and the 897 locator-set that this EID maps to can be an IPv4 or IPv6 RLOCs, or 898 even another MAC address being used as an RLOC. See 899 [I-D.portoles-lisp-eid-mobility] for how layer-2 VPNs operate when 900 doing EID mobility. 902 Care should be taken to protect privacy against the adverse use of a 903 Layer-2 MAC Address by ensuring policy controls are used during EID 904 registrations that use AFI=6 encodings in RLOC-records. Refer to the 905 use case documents for additional information. 907 4.10.3. ASCII Names in the Mapping Database 909 If DNS names [RFC1035] or URIs [RFC3986] are stored in the LISP 910 Mapping Database System, the AFI List Type can be used to carry an 911 ASCII string. 913 ASCII LISP Canonical Address Format: 915 0 1 2 3 916 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 917 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 918 | AFI = 16387 | Rsvd1 | Flags | 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 920 | Type = 1 | Rsvd2 | Length | 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 922 | AFI = 17 | DNS Name or URI ... | 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 925 Length: length in bytes starting and including the byte after this 926 Length field. 928 An example for using DNS names is when an ETR registers a mapping 929 with an EID-record encoded as (AFI=1, 10.0.0.0/8) with a RLOC-record 930 (AFI=17, "router.abc.com"). 932 4.10.4. Using Recursive LISP Canonical Address Encodings 934 When any combination of above is desirable, the AFI List Type value 935 can be used to carry within the LCAF AFI another LCAF AFI (for 936 example, Application Specific Data see Section 5.1. 938 Recursive LISP Canonical Address Format: 940 0 1 2 3 941 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 942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 | AFI = 16387 | Rsvd1 | Flags | 944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 945 | Type = 1 | Rsvd2 | Length | 946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 947 | AFI = 16387 | Rsvd1 | Flags | 948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 949 | Type = 4 | Rsvd2 | Length2 | 950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 951 | IP TOS, IPv6 TC or Flow Label | Protocol | 952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 953 | Local Port (lower-range) | Local Port (upper-range) | 954 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 955 | Remote Port (lower-range) | Remote Port (upper-range) | 956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 | AFI = 1 | IPv4 Address ... | 958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 959 | ... IPv4 Address | 960 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 962 Length: length in bytes starting and including the byte after this 963 Length field. 965 Length2: length in bytes starting and including the byte after this 966 Length2 field. 968 This format could be used by a Mapping Database Transport System, 969 such as LISP-ALT [RFC6836], where the AFI=1 IPv4 address is used as 970 an EID and placed in the Map-Request destination address by the 971 sending LISP system. The ALT system can deliver the Map-Request to 972 the LISP destination site independent of the Application Data Type 973 AFI payload values. When this AFI is processed by the destination 974 LISP site, it can return different locator-sets based on the type of 975 application or level of service that is being requested. 977 4.10.5. Compatibility Mode Use Case 979 A LISP system should use the AFI List Type format when sending to 980 LISP systems that do not support a particular LCAF Type used to 981 encode locators. This allows the receiving system to be able to 982 parse a locator address for encapsulation purposes. The list of AFIs 983 in an AFI List LCAF Type has no semantic ordering and a receiver 984 should parse each AFI element no matter what the ordering. 986 Compatibility Mode Address Format: 988 0 1 2 3 989 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 990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 | AFI = 16387 | Rsvd1 | Flags | 992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 993 | Type = 1 | Rsvd2 | Length | 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 995 | AFI = 16387 | Rsvd1 | Flags | 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 | Type = 5 | Rsvd2 | Length2 | 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 |N| Latitude Degrees | Minutes | Seconds | 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1001 |E| Longitude Degrees | Minutes | Seconds | 1002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1003 | Altitude | 1004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1005 | AFI = 0 | AFI = 1 | 1006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1007 | IPv4 Address | 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1010 Length: length in bytes starting and including the byte after this 1011 Length field. 1013 Length2: length in bytes starting and including the byte after this 1014 Length2 field. 1016 If a system does not recognized the Geo Coordinate LCAF Type that is 1017 accompanying a locator address, an encoder can include the Geo 1018 Coordinate LCAF Type embedded in a AFI List LCAF Type where the AFI 1019 in the Geo Coordinate LCAF is set to 0 and the AFI encoded next in 1020 the list is encoded with a valid AFI value to identify the locator 1021 address. 1023 A LISP system is required to support the AFI List LCAF Type to use 1024 this procedure. It would skip over 10 bytes of the Geo Coordinate 1025 LCAF Type to get to the locator address encoding (an IPv4 locator 1026 address). A LISP system that does support the Geo Coordinate LCAF 1027 Type can support parsing the locator address within the Geo 1028 Coordinate LCAF encoding or in the locator encoding that follows in 1029 the AFI List LCAF. 1031 5. Experimental LISP Canonical Address Applications 1033 The following sections describe experimental LCAF encodings. These 1034 LCAF Types are not approved (registered with IANA). The inclusion of 1035 these encodings in this document are in support of further study and 1036 experimentation to determine whether these encodings are functional, 1037 if there is a demand for these use cases, and better understand 1038 deployment considerations. As noted previously, these LCAF Types are 1039 restricted to cautious use in self-contained environments in support 1040 of the corresponding use-case documents. 1042 5.1. Convey Application Specific Data 1044 When a locator-set needs to be conveyed based on the type of 1045 application or the Per-Hop Behavior (PHB) of a packet, the 1046 Application Data Type can be used. 1048 Application Data LISP Canonical Address Format: 1050 0 1 2 3 1051 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 1052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1053 | AFI = 16387 | Rsvd1 | Flags | 1054 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1055 | Type = 4 | Rsvd2 | Length | 1056 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1057 | IP TOS, IPv6 TC, or Flow Label | Protocol | 1058 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1059 | Local Port (lower-range) | Local Port (upper-range) | 1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 | Remote Port (lower-range) | Remote Port (upper-range) | 1062 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1063 | AFI = x | Address ... | 1064 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1066 Length: length in bytes starting and including the byte after this 1067 Length field. 1069 IP TOS, IPv6 TC, or Flow Label: this field stores the 8-bit IPv4 TOS 1070 field used in an IPv4 header, the 8-bit IPv6 Traffic Class or Flow 1071 Label used in an IPv6 header. 1073 Local Port/Remote Port Ranges: these fields are from the TCP, UDP, 1074 or SCTP transport header. A range can be specified by using a 1075 lower value and an upper value. When a single port is encoded, 1076 the lower and upper value fields are the same. 1078 AFI = x: x can be any AFI value from [AFI]. 1080 The Application Data Canonical Address Type is used for an EID 1081 encoding when an ITR wants a locator-set for a specific application. 1082 When used for an RLOC encoding, the ETR is supplying a locator-set 1083 for each specific application is has been configured to advertise. 1085 Usage: This encoding can be used in EID records in Map-Requests, Map- 1086 Replies, Map-Registers, and Map-Notify messages. When LISP-DDT 1087 [I-D.ietf-lisp-ddt] is used as the mapping system mechanism, extended 1088 EIDs are used in Map-Referral messages. This LCAF type is used as a 1089 lookup key to the mapping system that can return a longest-match or 1090 exact-match entry. 1092 5.2. Generic Database Mapping Lookups 1094 When the LISP Mapping Database system holds information accessed by a 1095 generic formatted key (where the key is not the usual IPv4 or IPv6 1096 address), an opaque key may be desirable. 1098 Opaque Key LISP Canonical Address Format: 1100 0 1 2 3 1101 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 1102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1103 | AFI = 16387 | Rsvd1 | Flags | 1104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1105 | Type = 6 | Rsvd2 | Length | 1106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1107 | Key Field Num | Key Wildcard Fields | Key . . . | 1108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1109 | . . . Key | 1110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1112 Length: length in bytes starting and including the byte after this 1113 Length field. 1115 Key Field Num: the value of this field is the number of "Key" sub- 1116 fields minus 1, the "Key" field can be broken up into. So if this 1117 field has a value of 0, there is 1 sub-field in the "Key". The 1118 width of the sub-fields are fixed length. So for a key size of 8 1119 bytes, with a Key Field Num of 3, allows 4 sub-fields of 2 bytes 1120 each in length. Allowing for a reasonable number of 16 sub-field 1121 separators, valid values range from 0 to 15. 1123 Key Wildcard Fields: describes which fields in the key are not used 1124 as part of the key lookup. This wildcard encoding is a bitfield. 1125 Each bit is a don't-care bit for a corresponding field in the key. 1126 Bit 0 (the low-order bit) in this bitfield corresponds the first 1127 field, the low-order field in the key, bit 1 the second field, and 1128 so on. When a bit is set in the bitfield it is a don't-care bit 1129 and should not be considered as part of the database lookup. When 1130 the entire 16-bits is set to 0, then all bits of the key are used 1131 for the database lookup. 1133 Key: the variable length key used to do a LISP Database Mapping 1134 lookup. The length of the key is the value n (as shown above). 1136 Usage: This is an experimental type where the usage has not been 1137 defined yet. 1139 5.3. PETR Admission Control Functionality 1141 When a public PETR device wants to verify who is encapsulating to it, 1142 it can check for a specific nonce value in the LISP encapsulated 1143 packet. To convey the nonce to admitted ITRs or PITRs, this LCAF is 1144 used in a Map-Register or Map-Reply locator-record. 1146 Nonce Locator Canonical Address Format: 1148 0 1 2 3 1149 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 1150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1151 | AFI = 16387 | Rsvd1 | Flags | 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1153 | Type = 8 | Rsvd2 | Length | 1154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1155 | Reserved | Nonce | 1156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1157 | AFI = x | Address ... | 1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1160 Length: length in bytes starting and including the byte after this 1161 Length field. 1163 Reserved: must be set to zero and ignore on receipt. 1165 Nonce: this is a nonce value returned by an ETR in a Map-Reply 1166 locator-record to be used by an ITR or PITR when encapsulating to 1167 the locator address encoded in the AFI field of this LCAF type. 1168 This nonce value is inserted in the nonce field in the LISP header 1169 encapsulation. 1171 AFI = x: x can be any AFI value from [AFI]. 1173 Usage: This is an experimental type where the usage has not been 1174 defined yet. 1176 5.4. Data Model Encoding 1178 This type allows a JSON data model to be encoded either as an EID or 1179 RLOC. 1181 JSON Data Model Type Address Format: 1183 0 1 2 3 1184 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 1185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1186 | AFI = 16387 | Rsvd1 | Flags | 1187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1188 | Type = 14 | Rsvd2 |B| Length | 1189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1190 | JSON length | JSON binary/text encoding ... | 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | AFI = x | Optional Address ... | 1193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1195 Length: length in bytes starting and including the byte after this 1196 Length field. 1198 B bit: indicates that the JSON field is binary encoded according to 1199 [JSON-BINARY] when the bit is set to 1. Otherwise the encoding is 1200 based on text encoding according to [RFC7159]. 1202 JSON length: length in octets of the following 'JSON binary/text 1203 encoding' field. 1205 JSON binary/text encoding field: a variable length field that 1206 contains either binary or text encodings. 1208 AFI = x: x can be any AFI value from [AFI]. A specific AFI has its 1209 own encoding of either a unicast or multicast locator address. 1210 All RTR/ETR entries for the same level should be combined together 1211 by a Map-Server to avoid searching through the entire multi-level 1212 list of locator entries in a Map-Reply message. 1214 Usage: This is an experimental type where the usage has not been 1215 defined yet. An example mapping is an EID-record encoded as a 1216 distinguished-name "cpe-rotuer" and a RLOC-record encoded as a JSON 1217 string "{ "router-address" : "1.1.1.1", "router-mask" : "8" }". 1219 5.5. Encoding Key/Value Address Pairs 1221 The Key/Value pair is, for example, useful for attaching attributes 1222 to other elements of LISP packets, such as EIDs or RLOCs. When 1223 attaching attributes to EIDs or RLOCs, it's necessary to distinguish 1224 between the element that should be used as EID or RLOC, and hence as 1225 the key for lookups, and additional attributes. This is especially 1226 the case when the difference cannot be determined from the types of 1227 the elements, such as when two IP addresses are being used. 1229 Key/Value Pair Address Format: 1231 0 1 2 3 1232 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 1233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1234 | AFI = 16387 | Rsvd1 | Flags | 1235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1236 | Type = 15 | Rsvd2 | Length | 1237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1238 | AFI = x | Address as Key ... | 1239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1240 | AFI = y | Address as Value ... | 1241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1243 Length: length in bytes starting and including the byte after this 1244 Length field. 1246 AFI = x: x is the "Address as Key" AFI that can have any value from 1247 [AFI]. A specific AFI has its own encoding of either a unicast or 1248 multicast locator address. All RTR/ETR entries for the same level 1249 should be combined together by a Map-Server to avoid searching 1250 through the entire multi-level list of locator entries in a Map- 1251 Reply message. 1253 Address as Key: this AFI-encoded address will be attached with the 1254 attributes encoded in "Address as Value" which follows this field. 1256 AFI = y: y is the "Address of Value" AFI that can have any value 1257 from [AFI]. A specific AFI has its own encoding of either a 1258 unicast or multicast locator address. All RTR/ETR entries for the 1259 same level should be combined together by a Map-Server to avoid 1260 searching through the entire multi-level list of locator entries 1261 in a Map-Reply message. 1263 Address as Value: this AFI-encoded address will be the attribute 1264 address that goes along with "Address as Key" which precedes this 1265 field. 1267 Usage: This is an experimental type where the usage has not been 1268 defined yet. 1270 5.6. Multiple Data-Planes 1272 Overlays are becoming popular in many parts of the network which have 1273 created an explosion of data-plane encapsulation headers. Since the 1274 LISP mapping system can hold many types of address formats, it can 1275 represent the encapsulation format supported by an RLOC as well. 1276 When an encapsulator receives a Map-Reply with an Encapsulation 1277 Format LCAF Type encoded in an RLOC-record, it can select an 1278 encapsulation format, that it can support, from any of the 1279 encapsulation protocols which have the bit set to 1 in this LCAF 1280 type. 1282 Encapsulation Format Address Format: 1284 0 1 2 3 1285 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 1286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1287 | AFI = 16387 | Rsvd1 | Flags | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1289 | Type = 16 | Rsvd2 | Length | 1290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1291 | Reserved-for-Future-Encapsulations |U|G|N|v|V|l|L| 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1293 | AFI = x | Address ... | 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1296 Length: length in bytes starting and including the byte after this 1297 Length field. 1299 Reserved-for-Future-Encapsulations: must be set to zero and ignored 1300 on receipt. This field will get bits allocated to future 1301 encapsulations, as they are created. 1303 L: The RLOCs listed in the AFI-encoded addresses in the next longword 1304 can accept layer 3 LISP encapsulation using destination UDP port 1305 4341 [RFC6830]. 1307 l: The RLOCs listed in the AFI-encoded addresses in the next longword 1308 can accept layer 2 LISP encapsulation using destination UDP port 1309 8472 [I-D.smith-lisp-layer2]. 1311 V: The RLOCs listed in the AFI-encoded addresses in the next longword 1312 can accept VXLAN encapsulation using destination UDP port 4789 1313 [RFC7348]. 1315 v: The RLOCs listed in the AFI-encoded addresses in the next longword 1316 can accept VXLAN-GPE encapsulation using destination UDP port 4790 1317 [I-D.quinn-vxlan-gpe]. 1319 N: The RLOCs listed in the AFI-encoded addresses in the next longword 1320 can accept NV-GRE encapsulation using IPv4/ IPv6 protocol number 1321 47 [RFC7637]. 1323 G: The RLOCs listed in the AFI-encoded addresses in the next longword 1324 can accept GENEVE encapsulation using destination UDP port 6081 1325 [I-D.gross-geneve]. 1327 U: The RLOCs listed in the AFI-encoded addresses in the next longword 1328 can accept GUE encapsulation using destination UDP port TBD 1329 [I-D.herbert-gue]. 1331 Usage: This encoding can be used in RLOC records in Map-Requests, 1332 Map-Replies, Map-Registers, and Map-Notify messages. 1334 6. Security Considerations 1336 This document is classified as Experimental. The LCAF encodings 1337 defined in this document are intended to be used with their 1338 corresponding use cases and in self-contained environments. Users 1339 should carefully consider how the [I-D.ietf-lisp-sec] threat model 1340 applies to their particular use case. 1342 The use of the Geo-Coordinates LCAF Type may raise physical privacy 1343 issues. Care should be taken when configuring the mapping system to 1344 use specific policy parameters so geo-location information is not 1345 returned gratuitously. It is recommended that any documents that 1346 specify the use of the Geo-Coordinates LCAF Type should consider the 1347 applicability of the BCP160 [RFC6280] for location-based privacy 1348 protection. 1350 Additional privacy concerns have arisen since publication of BCP160, 1351 and future work on LISP should examine potential threats beyond 1352 BCP160 and address improving privacy and security for LISP 1353 deployments. 1355 7. IANA Considerations 1357 This document defines a canonical address format encoding used in 1358 LISP control messages and in the encoding of lookup keys for the LISP 1359 Mapping Database System. Such address format is based on a fixed AFI 1360 (16387) and a LISP LCAF Type field. 1362 The LISP LCAF Type field is an 8-bit field specific to the LISP 1363 Canonical Address formatted encodings, for which IANA is to create 1364 and maintain a new registry (as outlined in [RFC5226]) entitled "LISP 1365 LCAF Type". Initial values for the LISP LCAF Type registry are given 1366 below. Future assignments are to be made based on specification 1367 required. Assignments consist of a LISP LCAF Type name and its 1368 associated value: 1370 +-------+------------------------------+------------+ 1371 | Value | LISP LCAF Type Name | Definition | 1372 +-------+------------------------------+------------+ 1373 | 0 | Null Body Type | Section 3 | 1374 | 1 | AFI List Type | Section 3 | 1375 | 2 | Instance ID Type | Section 3 | 1376 | 3 | AS Number Type | Section 3 | 1377 | 5 | Geo Coordinates Type | Section 3 | 1378 | 7 | NAT-Traversal Type | Section 3 | 1379 | 9 | Multicast Info Type | Section 3 | 1380 | 10 | Explicit Locator Path Type | Section 3 | 1381 | 11 | Security Key Type | Section 3 | 1382 | 12 | Source/Dest Key Type | Section 3 | 1383 | 13 | Replication List Entry Type | Section 3 | 1384 +-------+------------------------------+------------+ 1386 Table 1: LISP LCAF Type Initial Values 1388 8. References 1390 8.1. Normative References 1392 [BCP160] "An Architecture for Location and Location Privacy in 1393 Internet Applications", Best Current Practices 1394 https://www.rfc-editor.org/bcp/bcp160.txt, July 2011. 1396 [RFC1035] Mockapetris, P., "Domain names - implementation and 1397 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 1398 November 1987, . 1400 [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., 1401 and E. Lear, "Address Allocation for Private Internets", 1402 BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, 1403 . 1405 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1406 Requirement Levels", BCP 14, RFC 2119, 1407 DOI 10.17487/RFC2119, March 1997, 1408 . 1410 [RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced 1411 by an On-line Database", RFC 3232, DOI 10.17487/RFC3232, 1412 January 2002, . 1414 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1415 Resource Identifier (URI): Generic Syntax", STD 66, 1416 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1417 . 1419 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1420 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1421 DOI 10.17487/RFC5226, May 2008, 1422 . 1424 [RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J., 1425 Tschofenig, H., and H. Schulzrinne, "An Architecture for 1426 Location and Location Privacy in Internet Applications", 1427 BCP 160, RFC 6280, DOI 10.17487/RFC6280, July 2011, 1428 . 1430 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 1431 Locator/ID Separation Protocol (LISP)", RFC 6830, 1432 DOI 10.17487/RFC6830, January 2013, 1433 . 1435 [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, 1436 "Locator/ID Separation Protocol Alternative Logical 1437 Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, 1438 January 2013, . 1440 [RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 1441 Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March 1442 2014, . 1444 [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, 1445 L., Sridhar, T., Bursell, M., and C. Wright, "Virtual 1446 eXtensible Local Area Network (VXLAN): A Framework for 1447 Overlaying Virtualized Layer 2 Networks over Layer 3 1448 Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, 1449 . 1451 [RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network 1452 Virtualization Using Generic Routing Encapsulation", 1453 RFC 7637, DOI 10.17487/RFC7637, September 2015, 1454 . 1456 8.2. Informative References 1458 [AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY 1459 NUMBERS http://www.iana.org/assignments/address-family- 1460 numbers/address-family-numbers.xhtml?, Febuary 2007. 1462 [I-D.coras-lisp-re] 1463 Coras, F., Cabellos-Aparicio, A., Domingo-Pascual, J., 1464 Maino, F., and D. Farinacci, "LISP Replication 1465 Engineering", draft-coras-lisp-re-08 (work in progress), 1466 November 2015. 1468 [I-D.ermagan-lisp-nat-traversal] 1469 Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, 1470 F., and C. White, "NAT traversal for LISP", draft-ermagan- 1471 lisp-nat-traversal-11 (work in progress), August 2016. 1473 [I-D.farinacci-lisp-te] 1474 Farinacci, D., Kowal, M., and P. Lahiri, "LISP Traffic 1475 Engineering Use-Cases", draft-farinacci-lisp-te-11 (work 1476 in progress), September 2016. 1478 [I-D.gross-geneve] 1479 Gross, J., Sridhar, T., Garg, P., Wright, C., Ganga, I., 1480 Agarwal, P., Duda, K., Dutt, D., and J. Hudson, "Geneve: 1481 Generic Network Virtualization Encapsulation", draft- 1482 gross-geneve-02 (work in progress), October 2014. 1484 [I-D.herbert-gue] 1485 Herbert, T., Yong, L., and O. Zia, "Generic UDP 1486 Encapsulation", draft-herbert-gue-03 (work in progress), 1487 March 2015. 1489 [I-D.ietf-lisp-crypto] 1490 Farinacci, D. and B. Weis, "LISP Data-Plane 1491 Confidentiality", draft-ietf-lisp-crypto-10 (work in 1492 progress), October 2016. 1494 [I-D.ietf-lisp-ddt] 1495 Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. 1496 Smirnov, "LISP Delegated Database Tree", draft-ietf-lisp- 1497 ddt-08 (work in progress), September 2016. 1499 [I-D.ietf-lisp-sec] 1500 Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D. 1501 Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-12 1502 (work in progress), November 2016. 1504 [I-D.portoles-lisp-eid-mobility] 1505 Portoles-Comeras, M., Ashtaputre, V., Moreno, V., Maino, 1506 F., and D. Farinacci, "LISP L2/L3 EID Mobility Using a 1507 Unified Control Plane", draft-portoles-lisp-eid- 1508 mobility-01 (work in progress), October 2016. 1510 [I-D.quinn-vxlan-gpe] 1511 Quinn, P., Manur, R., Kreeger, L., Lewis, D., Maino, F., 1512 Smith, M., Agarwal, P., Yong, L., Xu, X., Elzur, U., Garg, 1513 P., and D. Melman, "Generic Protocol Extension for VXLAN", 1514 draft-quinn-vxlan-gpe-04 (work in progress), February 1515 2015. 1517 [I-D.smith-lisp-layer2] 1518 Smith, M., Dutt, D., Farinacci, D., and F. Maino, "Layer 2 1519 (L2) LISP Encapsulation Format", draft-smith-lisp- 1520 layer2-03 (work in progress), September 2013. 1522 [JSON-BINARY] 1523 "Universal Binary JSON Specification", 1524 URL http://ubjson.org. 1526 [WGS-84] Geodesy and Geophysics Department, DoD., "World Geodetic 1527 System 1984", NIMA TR8350.2, January 2000, . 1530 Appendix A. Acknowledgments 1532 The authors would like to thank Vince Fuller, Gregg Schudel, Jesper 1533 Skriver, Luigi Iannone, Isidor Kouvelas, and Sander Steffann for 1534 their technical and editorial commentary. 1536 The authors would like to thank Victor Moreno for discussions that 1537 lead to the definition of the Multicast Info LCAF type. 1539 The authors would like to thank Parantap Lahiri and Michael Kowal for 1540 discussions that lead to the definition of the Explicit Locator Path 1541 (ELP) LCAF type. 1543 The authors would like to thank Fabio Maino and Vina Ermagan for 1544 discussions that lead to the definition of the Security Key LCAF 1545 type. 1547 The authors would like to thank Albert Cabellos-Aparicio and Florin 1548 Coras for discussions that lead to the definition of the Replication 1549 List Entry LCAF type. 1551 Thanks goes to Michiel Blokzijl and Alberto Rodriguez-Natal for 1552 suggesting new LCAF types. 1554 Thanks also goes to Terry Manderson for assistance obtaining a LISP 1555 AFI value from IANA. 1557 And finally, the authors thank Stephen Farrell (Security Area 1558 Director) and Deborah Brungard (Routing Area Director) for their 1559 suggested text to get the document through IESG review. 1561 Appendix B. Document Change Log 1563 [RFC Editor: Please delete this section on publication as RFC.] 1565 B.1. Changes to draft-ietf-lisp-lcaf-22.txt 1567 o Submitted November 2016. 1569 o Take into account RTG area director Deborah Brungard's comments 1570 suggestions. 1572 o The changes put in shoudl clear Stephen's DISCUSS comments on 1573 RLOC-record ordering and privacy concerns with the Geo-Coordinate 1574 LCAF type. 1576 B.2. Changes to draft-ietf-lisp-lcaf-21.txt 1578 o Submitted November 2016. 1580 o Reflect Alexey's DISCUSS comments. 1582 o Add text to intro section that says the details for any LCAF type 1583 can be found in other use-case documents. 1585 o Provide general examples for JSON and DNS LCAF types. 1587 B.3. Changes to draft-ietf-lisp-lcaf-20.txt 1589 o Submitted October 2016. 1591 o Put in references to DNS names and URIs per Alexey's comment. 1593 B.4. Changes to draft-ietf-lisp-lcaf-19.txt 1595 o Submitted October 2016. 1597 o Make it more clear that any use-case documents that use the Geo- 1598 Coordinates LCAF type should discuss RFC6280 compliance. 1600 B.5. Changes to draft-ietf-lisp-lcaf-18.txt 1602 o Submitted October 2016 after October 13th telechat. 1604 o Addressed comments from Ben Campbell, Jari Arrko, Stephen Farrel, 1605 Peter Yee, Dale Worley, Mirja Kuehlewind, and Suresh Krishnan. 1607 B.6. Changes to draft-ietf-lisp-lcaf-17.txt 1609 o Submitted October 2016. 1611 o Addressed comments from Gen-ART reviewer Peter Yee. 1613 o Addressed IESG last-call comments from Suresh Krishnan. 1615 B.7. Changes to draft-ietf-lisp-lcaf-16.txt 1617 o Submitted October 2016. 1619 o Addressed comments from Security Directorate reviewer David 1620 Mandelberg. 1622 B.8. Changes to draft-ietf-lisp-lcaf-15.txt 1624 o Submitted September 2016. 1626 o Addressed comments from Routing Directorate reviewer Stig Venass. 1628 B.9. Changes to draft-ietf-lisp-lcaf-14.txt 1630 o Submitted July 2016. 1632 o Fix IDnits errors and comments from Luigi Iannone, document 1633 shepherd. 1635 B.10. Changes to draft-ietf-lisp-lcaf-13.txt 1637 o Submitted May 2016. 1639 o Explain the Instance-ID LCAF Type is 32-bits in length and the 1640 Instance-ID field in the LISP encapsulation header is 24-bits. 1642 B.11. Changes to draft-ietf-lisp-lcaf-12.txt 1644 o Submitted March 2016. 1646 o Updated references and document timer. 1648 o Removed the R, J, and L bits from the Multicast Info Type LCAF 1649 since working group decided to not go forward with draft- 1650 farinacci-lisp-mr-signaling-03.txt in favor of draft- ietf-lisp- 1651 signal-free-00.txt. 1653 B.12. Changes to draft-ietf-lisp-lcaf-11.txt 1655 o Submitted September 2015. 1657 o Reflecting comments from Prague LISP working group. 1659 o Readying document for a LISP LCAF registry, RFC publication, and 1660 for new use cases that will be defined in the new charter. 1662 B.13. Changes to draft-ietf-lisp-lcaf-10.txt 1664 o Submitted June 2015. 1666 o Fix coauthor Job's contact information. 1668 B.14. Changes to draft-ietf-lisp-lcaf-09.txt 1670 o Submitted June 2015. 1672 o Fix IANA Considerations section to request a registry to allocate 1673 and track LCAF Type values. 1675 B.15. Changes to draft-ietf-lisp-lcaf-08.txt 1677 o Submitted April 2015. 1679 o Comment from Florin. The Application Data Type length field has a 1680 typo. The field should be labeled "12 + n" and not "8 + n". 1682 o Fix length fields in the sections titled "Using Recursive LISP 1683 Canonical Address Encodings", "Generic Database Mapping Lookups", 1684 and "Data Model Encoding". 1686 B.16. Changes to draft-ietf-lisp-lcaf-07.txt 1688 o Submitted December 2014. 1690 o Add a new LCAF Type called "Encapsulation Format" so decapsulating 1691 xTRs can inform encapsulating xTRs what data-plane encapsulations 1692 they support. 1694 B.17. Changes to draft-ietf-lisp-lcaf-06.txt 1696 o Submitted October 2014. 1698 o Make it clear how sorted RLOC records are done when LCAFs are used 1699 as the RLOC record. 1701 B.18. Changes to draft-ietf-lisp-lcaf-05.txt 1703 o Submitted May 2014. 1705 o Add a length field of the JSON payload that can be used for either 1706 binary or text encoding of JSON data. 1708 B.19. Changes to draft-ietf-lisp-lcaf-04.txt 1710 o Submitted January 2014. 1712 o Agreement among ELP implementors to have the AFI 16-bit field 1713 adjacent to the address. This will make the encoding consistent 1714 with all other LCAF type address encodings. 1716 B.20. Changes to draft-ietf-lisp-lcaf-03.txt 1718 o Submitted September 2013. 1720 o Updated references and author's affilations. 1722 o Added Instance-ID to the Multicast Info Type so there is relative 1723 ease in parsing (S,G) entries within a VPN. 1725 o Add port range encodings to the Application Data LCAF Type. 1727 o Add a new JSON LCAF Type. 1729 o Add Address Key/Value LCAF Type to allow attributes to be attached 1730 to an address. 1732 B.21. Changes to draft-ietf-lisp-lcaf-02.txt 1734 o Submitted March 2013. 1736 o Added new LCAF Type "Replication List Entry" to support LISP 1737 replication engineering use cases. 1739 o Changed references to new LISP RFCs. 1741 B.22. Changes to draft-ietf-lisp-lcaf-01.txt 1743 o Submitted January 2013. 1745 o Change longitude range from 0-90 to 0-180 in section 4.4. 1747 o Added reference to WGS-84 in section 4.4. 1749 B.23. Changes to draft-ietf-lisp-lcaf-00.txt 1751 o Posted first working group draft August 2012. 1753 o This draft was renamed from draft-farinacci-lisp-lcaf-10.txt. 1755 Authors' Addresses 1757 Dino Farinacci 1758 lispers.net 1759 San Jose, CA 1760 USA 1762 Email: farinacci@gmail.com 1763 Dave Meyer 1764 Brocade 1765 San Jose, CA 1766 USA 1768 Email: dmm@1-4-5.net 1770 Job Snijders 1771 NTT Communications 1772 Theodorus Majofskistraat 100 1773 Amsterdam 1065 SZ 1774 The Netherlands 1776 Email: job@ntt.net