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