idnits 2.17.1 draft-farinacci-lisp-name-encoding-06.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 (September 11, 2018) is 2052 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 6830 (Obsoleted by RFC 9300, RFC 9301) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 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 September 11, 2018 5 Expires: March 15, 2019 7 LISP Distinguished Name Encoding 8 draft-farinacci-lisp-name-encoding-06 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 March 15, 2019. 31 Copyright Notice 33 Copyright (c) 2018 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. Security Considerations . . . . . . . . . . . . . . . . . . . 4 52 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 53 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 54 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 4 55 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 4 56 B.1. Changes to draft-farinacci-lisp-name-encoding-06 . . . . 4 57 B.2. Changes to draft-farinacci-lisp-name-encoding-05 . . . . 4 58 B.3. Changes to draft-farinacci-lisp-name-encoding-04 . . . . 5 59 B.4. Changes to draft-farinacci-lisp-name-encoding-03 . . . . 5 60 B.5. Changes to draft-farinacci-lisp-name-encoding-02 . . . . 5 61 B.6. Changes to draft-farinacci-lisp-name-encoding-01 . . . . 5 62 B.7. Changes to draft-farinacci-lisp-name-encoding-00 . . . . 5 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 The LISP architecture and protocols [RFC6830] introduces two new 68 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators 69 (RLOCs) which are intended to replace most use of IP addresses on the 70 Internet. To provide flexibility for current and future 71 applications, these values can be encoded in LISP control messages 72 using a general syntax that includes Address Family Identifier (AFI) 73 [RFC1700]. 75 The length of the value field is implicit in the type of address that 76 follows. For AFI 17, a Distinguished Name can be encoded. A name 77 can be a variable length field so the length cannot be determined 78 solely from the AFI value 17. This draft defines a termination 79 character, an 8-bit value of 0 to be used as a string terminator so 80 the length can be determined. 82 LISP Distinguished Names are useful when encoded either in EID- 83 records or RLOC-records in LISP control messages. As EIDs, they can 84 be registered in the mapping system to find resources, services, or 85 simply used as a self-documenting feature that accompany other 86 address specific EIDs. As RLOCs, Distinguished Names, along with 87 RLOC specific addresses and parameters, can be used as labels to 88 identify equipment type, location, or any self-documenting string a 89 registering device desires to convey. 91 2. Definition of Terms 93 Address Family Identifier (AFI): a term used to describe an address 94 encoding in a packet. An address family currently defined for 95 IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details on 96 other types of information that can be AFI encoded. 98 3. Distinguished Name Format 100 An AFI=17 Distinguished Name is encoded as: 102 0 1 2 3 103 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 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | AFI = 17 | ASCII String ... | 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | ... ASCII String | 0 | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 The string of characters are encoded in the ASCII character-set 111 definition [RFC0020]. 113 4. Security Considerations 115 There are no security considerations. 117 5. IANA Considerations 119 The code-point values in this specification are already allocated in 120 [AFI]. 122 6. Normative References 124 [AFI] IANA, "Address Family Identifier (AFIs)", ADDRESS FAMILY 125 NUMBERS http://www.iana.org/numbers.html, Febuary 2007. 127 [RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, 128 RFC 20, DOI 10.17487/RFC0020, October 1969, 129 . 131 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 132 DOI 10.17487/RFC1700, October 1994, 133 . 135 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 136 Locator/ID Separation Protocol (LISP)", RFC 6830, 137 DOI 10.17487/RFC6830, January 2013, 138 . 140 Appendix A. Acknowledgments 142 The author would like to thank the LISP WG for their review and 143 acceptance of this draft. 145 Appendix B. Document Change Log 147 B.1. Changes to draft-farinacci-lisp-name-encoding-06 149 o Submitted September 2018. 151 o Update document expiry timer. 153 B.2. Changes to draft-farinacci-lisp-name-encoding-05 155 o Submitted March 2018. 157 o Update document expiry timer. 159 B.3. Changes to draft-farinacci-lisp-name-encoding-04 161 o Submitted September 2017. 163 o Update document expiry timer. 165 B.4. Changes to draft-farinacci-lisp-name-encoding-03 167 o Submitted March 2017. 169 o Update document expiry timer. 171 B.5. Changes to draft-farinacci-lisp-name-encoding-02 173 o Submitted October 2016. 175 o Add a comment that the distinguished-name encoding is restricted 176 to ASCII character encodings only. 178 B.6. Changes to draft-farinacci-lisp-name-encoding-01 180 o Submitted October 2016. 182 o Update document timer. 184 B.7. Changes to draft-farinacci-lisp-name-encoding-00 186 o Initial draft submitted April 2016. 188 Author's Address 190 Dino Farinacci 191 lispers.net 192 San Jose, CA 193 USA 195 Email: farinacci@gmail.com