idnits 2.17.1 draft-farinacci-lisp-name-encoding-00.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 (April 13, 2016) is 2906 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 April 13, 2016 5 Expires: October 15, 2016 7 LISP Distinguished Name Encoding 8 draft-farinacci-lisp-name-encoding-00 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 http://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 October 15, 2016. 31 Copyright Notice 33 Copyright (c) 2016 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 (http://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 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 57 1. Introduction 59 The LISP architecture and protocols [RFC6830] introduces two new 60 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators 61 (RLOCs) which are intended to replace most use of IP addresses on the 62 Internet. To provide flexibility for current and future 63 applications, these values can be encoded in LISP control messages 64 using a general syntax that includes Address Family Identifier (AFI) 65 [RFC1700]. 67 The length of the value field is implicit in the type of address that 68 follows. For AFI 17, a Distinguished Name can be encoded. A name 69 can be a variable length field so the length cannot be determined 70 solely from the AFI value 17. This draft defines a termination 71 character, an 8-bit value of 0 to be used as a string terminator so 72 the length can be determined. 74 LISP Distinguished Names are useful when encoded either in EID- 75 records or RLOC-records in LISP control messages. As EIDs, they can 76 be registered in the mapping system to find resources, services, or 77 simply used as a self-documenting feature that accompany other 78 address specific EIDs. As RLOCs, Distinguished Names, along with 79 RLOC specific addresses and parameters, can be used as labels to 80 identify equipment type, location, or any self-documenting string a 81 registering device desires to convey. 83 2. Definition of Terms 85 Address Family Identifier (AFI): a term used to describe an address 86 encoding in a packet. An address family currently defined for 87 IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details on 88 other types of information that can be AFI encoded. 90 3. Distinguished Name Format 92 An AFI=17 Distinguished Name is encoded as: 94 0 1 2 3 95 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 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | AFI = 17 | ASCII String ... | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | ... ASCII String | 0 | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 4. Security Considerations 104 There are no security considerations. 106 5. IANA Considerations 108 The code-point values in this specification are already allocated in 109 [AFI]. 111 6. Normative References 113 [AFI] IANA, , "Address Family Identifier (AFIs)", ADDRESS FAMILY 114 NUMBERS http://www.iana.org/numbers.html, Febuary 2007. 116 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 117 DOI 10.17487/RFC1700, October 1994, 118 . 120 [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The 121 Locator/ID Separation Protocol (LISP)", RFC 6830, 122 DOI 10.17487/RFC6830, January 2013, 123 . 125 Appendix A. Acknowledgments 127 The author would like to thank the LISP WG for their review and 128 acceptance of this draft. 130 Author's Address 132 Dino Farinacci 133 lispers.net 134 San Jose, CA 135 USA 137 Email: farinacci@gmail.com