idnits 2.17.1 draft-farinacci-lisp-name-encoding-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 14, 2020) is 1259 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-31) exists of draft-ietf-lisp-rfc6833bis-29 ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 6830 (Obsoleted by RFC 9300, RFC 9301) == Outdated reference: A later version (-15) exists of draft-farinacci-lisp-geo-10 == Outdated reference: A later version (-06) exists of draft-farinacci-lisp-simple-nat-01 == Outdated reference: A later version (-12) exists of draft-ietf-lisp-ecdsa-auth-04 Summary: 2 errors (**), 0 flaws (~~), 5 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 November 14, 2020 5 Expires: May 18, 2021 7 LISP Distinguished Name Encoding 8 draft-farinacci-lisp-name-encoding-11 10 Abstract 12 This draft defines how to use the AFI=17 Distinguished Names in LISP. 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at https://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on May 18, 2021. 31 Copyright Notice 33 Copyright (c) 2020 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (https://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3 50 3. Distinguished Name Format . . . . . . . . . . . . . . . . . . 3 51 4. Example Use-Cases . . . . . . . . . . . . . . . . . . . . . . 5 52 5. Name Collision Considerations . . . . . . . . . . . . . . . . 5 53 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 54 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 55 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 56 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 57 8.2. Informative References . . . . . . . . . . . . . . . . . 6 58 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6 59 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 6 60 B.1. Changes to draft-farinacci-lisp-name-encoding-11 . . . . 6 61 B.2. Changes to draft-farinacci-lisp-name-encoding-10 . . . . 7 62 B.3. Changes to draft-farinacci-lisp-name-encoding-09 . . . . 7 63 B.4. Changes to draft-farinacci-lisp-name-encoding-08 . . . . 7 64 B.5. Changes to draft-farinacci-lisp-name-encoding-07 . . . . 7 65 B.6. Changes to draft-farinacci-lisp-name-encoding-06 . . . . 7 66 B.7. Changes to draft-farinacci-lisp-name-encoding-05 . . . . 7 67 B.8. Changes to draft-farinacci-lisp-name-encoding-04 . . . . 7 68 B.9. Changes to draft-farinacci-lisp-name-encoding-03 . . . . 7 69 B.10. Changes to draft-farinacci-lisp-name-encoding-02 . . . . 8 70 B.11. Changes to draft-farinacci-lisp-name-encoding-01 . . . . 8 71 B.12. Changes to draft-farinacci-lisp-name-encoding-00 . . . . 8 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 The LISP architecture and protocols [RFC6830] introduces two new 77 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators 78 (RLOCs) which are intended to replace most use of IP addresses on the 79 Internet. To provide flexibility for current and future 80 applications, these values can be encoded in LISP control messages 81 using a general syntax that includes Address Family Identifier (AFI) 82 [RFC1700]. 84 The length of the value field is implicit in the type of address that 85 follows. For AFI 17, a Distinguished Name can be encoded. A name 86 can be a variable length field so the length cannot be determined 87 solely from the AFI value 17. This draft defines a termination 88 character, an 8-bit value of 0 to be used as a string terminator so 89 the length can be determined. 91 LISP Distinguished Names are useful when encoded either in EID- 92 records or RLOC-records in LISP control messages. As EIDs, they can 93 be registered in the mapping system to find resources, services, or 94 simply used as a self-documenting feature that accompany other 95 address specific EIDs. As RLOCs, Distinguished Names, along with 96 RLOC specific addresses and parameters, can be used as labels to 97 identify equipment type, location, or any self-documenting string a 98 registering device desires to convey. 100 2. Definition of Terms 102 Address Family Identifier (AFI): a term used to describe an address 103 encoding in a packet. An address family currently defined for 104 IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details on 105 other types of information that can be AFI encoded. 107 3. Distinguished Name Format 108 An AFI=17 Distinguished Name is encoded as: 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | AFI = 17 | ASCII String ... | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | ... ASCII String | 0 | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 The string of characters are encoded in the ASCII character-set 119 definition [RFC0020]. 121 When Distinguished Names are encoded for EIDs, the EID-prefix length 122 of the EIDs as they appear in EID-records for all LISP control 123 messages is the length of the string in bits (include the null 0 124 byte). Where Distinguished Names are encoded anywhere else (i.e. 125 nested in LCAF encodings), then any length field is the length of the 126 ASCII string including the null 0 byte in units of bytes. 128 When Map-Requests are sent for an EID encoded in Distinguished Name 129 format, an exact match request is performed. So the Map-Server (when 130 configured for proxy-Map-Replying) or the ETR will return a Map-Reply 131 with the same EID-prefix length. 133 4. Example Use-Cases 135 This section identifies three specific use-cases for the 136 Distinguished Name format. Two are used for an EID encoding and one 137 for a RLOC-record encoding. When storing public keys in the mapping 138 system, as in [I-D.ietf-lisp-ecdsa-auth], a well known format for a 139 public-key hash can be encoded as a Distinguished Name. When street 140 location to GPS coordinate mappings exist in the mapping system, as 141 in [I-D.farinacci-lisp-geo], the street location can be a free form 142 ascii representation (with whitespace characters) encoded as a 143 Distinguished Name. An RLOC that describes an xTR behind a NAT 144 device can be identified by its router name, as in 145 [I-D.farinacci-lisp-simple-nat], uses a Distinguished Name encoding. 146 As well as identifying the router name (neither an EID or an RLOC) in 147 NAT Info-Request messages uses Distinguished Name encodings. 149 5. Name Collision Considerations 151 When a Distinguished Name encoding is used to format an EID, the 152 uniqueness and allocation concerns are no different than registering 153 IPv4 or IPv6 EIDs to the mapping system. See 154 [I-D.ietf-lisp-rfc6833bis] for more details. Also, the use-case 155 documents specified in Section 4 provide allocation recommendations 156 for their specific uses. 158 6. Security Considerations 160 There are no security considerations. 162 7. IANA Considerations 164 The code-point values in this specification are already allocated in 165 [AFI]. 167 8. References 169 8.1. Normative References 171 [AFI] "Address Family Identifier (AFIs)", ADDRESS FAMILY 172 NUMBERS http://www.iana.org/numbers.html, Febuary 2007. 174 [I-D.ietf-lisp-rfc6833bis] 175 Farinacci, D., Maino, F., Fuller, V., and A. Cabellos- 176 Aparicio, "Locator/ID Separation Protocol (LISP) Control- 177 Plane", draft-ietf-lisp-rfc6833bis-29 (work in progress), 178 September 2020. 180 [RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, 181 RFC 20, DOI 10.17487/RFC0020, October 1969, 182 . 184 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 185 DOI 10.17487/RFC1700, October 1994, 186 . 188 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 189 Locator/ID Separation Protocol (LISP)", RFC 6830, 190 DOI 10.17487/RFC6830, January 2013, 191 . 193 8.2. Informative References 195 [I-D.farinacci-lisp-geo] 196 Farinacci, D., "LISP Geo-Coordinate Use-Cases", draft- 197 farinacci-lisp-geo-10 (work in progress), October 2020. 199 [I-D.farinacci-lisp-simple-nat] 200 Farinacci, D., "A Simple LISP NAT-Traversal 201 Implementation", draft-farinacci-lisp-simple-nat-01 (work 202 in progress), November 2020. 204 [I-D.ietf-lisp-ecdsa-auth] 205 Farinacci, D. and E. Nordmark, "LISP Control-Plane ECDSA 206 Authentication and Authorization", draft-ietf-lisp-ecdsa- 207 auth-04 (work in progress), September 2020. 209 Appendix A. Acknowledgments 211 The author would like to thank the LISP WG for their review and 212 acceptance of this draft. 214 Appendix B. Document Change Log 216 B.1. Changes to draft-farinacci-lisp-name-encoding-11 218 o Submitted November 2020. 220 o Made changes to reflect working group comments. 222 o Update references and document expiry timer. 224 B.2. Changes to draft-farinacci-lisp-name-encoding-10 226 o Submitted August 2020. 228 o Update references and document expiry timer. 230 B.3. Changes to draft-farinacci-lisp-name-encoding-09 232 o Submitted March 2020. 234 o Update references and document expiry timer. 236 B.4. Changes to draft-farinacci-lisp-name-encoding-08 238 o Submitted September 2019. 240 o Update references and document expiry timer. 242 B.5. Changes to draft-farinacci-lisp-name-encoding-07 244 o Submitted March 2019. 246 o Update referenes and document expiry timer. 248 B.6. Changes to draft-farinacci-lisp-name-encoding-06 250 o Submitted September 2018. 252 o Update document expiry timer. 254 B.7. Changes to draft-farinacci-lisp-name-encoding-05 256 o Submitted March 2018. 258 o Update document expiry timer. 260 B.8. Changes to draft-farinacci-lisp-name-encoding-04 262 o Submitted September 2017. 264 o Update document expiry timer. 266 B.9. Changes to draft-farinacci-lisp-name-encoding-03 268 o Submitted March 2017. 270 o Update document expiry timer. 272 B.10. Changes to draft-farinacci-lisp-name-encoding-02 274 o Submitted October 2016. 276 o Add a comment that the distinguished-name encoding is restricted 277 to ASCII character encodings only. 279 B.11. Changes to draft-farinacci-lisp-name-encoding-01 281 o Submitted October 2016. 283 o Update document timer. 285 B.12. Changes to draft-farinacci-lisp-name-encoding-00 287 o Initial draft submitted April 2016. 289 Author's Address 291 Dino Farinacci 292 lispers.net 293 San Jose, CA 294 USA 296 Email: farinacci@gmail.com