LISP Distinguished Name Encoding
draft-farinacci-lisp-name-encoding-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-27
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental March 27, 2017
Expires: September 28, 2017
LISP Distinguished Name Encoding
draft-farinacci-lisp-name-encoding-03
Abstract
This draft defines how to use the AFI=17 Distinguished Names in LISP.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 28, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Farinacci Expires September 28, 2017 [Page 1]
Internet-Draft LISP Distinguished Name Encoding March 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Distinguished Name Format . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 4
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 4
B.1. Changes to draft-farinacci-lisp-name-encoding-03 . . . . 4
B.2. Changes to draft-farinacci-lisp-name-encoding-02 . . . . 4
B.3. Changes to draft-farinacci-lisp-name-encoding-01 . . . . 5
B.4. Changes to draft-farinacci-lisp-name-encoding-00 . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which are intended to replace most use of IP addresses on the
Internet. To provide flexibility for current and future
applications, these values can be encoded in LISP control messages
using a general syntax that includes Address Family Identifier (AFI)
[RFC1700].
The length of the value field is implicit in the type of address that
follows. For AFI 17, a Distinguished Name can be encoded. A name
can be a variable length field so the length cannot be determined
solely from the AFI value 17. This draft defines a termination
character, an 8-bit value of 0 to be used as a string terminator so
the length can be determined.
LISP Distinguished Names are useful when encoded either in EID-
records or RLOC-records in LISP control messages. As EIDs, they can
be registered in the mapping system to find resources, services, or
simply used as a self-documenting feature that accompany other
address specific EIDs. As RLOCs, Distinguished Names, along with
RLOC specific addresses and parameters, can be used as labels to
identify equipment type, location, or any self-documenting string a
registering device desires to convey.
Farinacci Expires September 28, 2017 [Page 2]
Internet-Draft LISP Distinguished Name Encoding March 2017
2. Definition of Terms
Address Family Identifier (AFI): a term used to describe an address
encoding in a packet. An address family currently defined for
IPv4 or IPv6 addresses. See [AFI] and [RFC1700] for details on
other types of information that can be AFI encoded.
Show full document text