LISP support for Multi-Tuple EIDs
draft-rodrigueznatal-lisp-multi-tuple-eids-06
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-10-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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)
|
LISP Working Group A. Rodriguez-Natal
Internet-Draft Cisco Systems
Intended status: Experimental A. Cabellos-Aparicio
Expires: April 4, 2019 Technical University of Catalonia
S. Barkai
Fermi Serverless
V. Ermagan
D. Lewis
F. Maino
Cisco Systems
D. Farinacci
lispers.net
October 1, 2018
LISP support for Multi-Tuple EIDs
draft-rodrigueznatal-lisp-multi-tuple-eids-06
Abstract
This document describes extensions for LISP to support EIDs based on
tuples of multiple elements.
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 https://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 April 4, 2019.
Copyright Notice
Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of
Rodriguez-Natal, et al. Expires April 4, 2019 [Page 1]
Internet-Draft LISP-Multi-Tuple-EIDs October 2018
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Definition of terms . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Protocol Operation with Extended-EIDs . . . . . . . . . . . . 4
4.1. LISP Tunnel Routers . . . . . . . . . . . . . . . . . . . 4
4.2. Mapping System . . . . . . . . . . . . . . . . . . . . . 4
5. Extended-EIDs Encoding . . . . . . . . . . . . . . . . . . . 5
5.1. 5-Tuple . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Extended-EID Lookups . . . . . . . . . . . . . . . . . . . . 5
6.1. 5-Tuple (Coarse) . . . . . . . . . . . . . . . . . . . . 5
6.2. 5-Tuple (Exact) . . . . . . . . . . . . . . . . . . . . . 6
7. Mapping Databases for Extended-EIDs . . . . . . . . . . . . . 7
7.1. 5-Tuple (Coarse) . . . . . . . . . . . . . . . . . . . . 7
7.2. 5-Tuple (Exact) . . . . . . . . . . . . . . . . . . . . . 7
8. A Note on Instance-ID . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
11. Security Considerations . . . . . . . . . . . . . . . . . . . 8
12. Normative References . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
This document describes how LISP handles lookups based on Extended-
EIDs, i.e. tuples of n elements. Particularly it describes how the
Tunnel Routers and the Mapping System operate when Extended-EIDs are
in place, the different types of Extended-EIDs defined so far, how
the lookup is performed for each Extended-EID type and which mapping
databases are recommended to use depending on the kind of Extended-
EIDs used.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text