LISP Canonical Address Format (LCAF)
RFC 8060
| Document | Type |
RFC - Experimental
(February 2017; No errata)
Was draft-ietf-lisp-lcaf (lisp WG)
|
|
|---|---|---|---|
| Last updated | 2017-02-02 | ||
| Replaces | draft-farinacci-lisp-lcaf | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Luigi Iannone | ||
| Shepherd write-up | Show (last changed 2016-07-21) | ||
| IESG | IESG state | RFC 8060 (Experimental) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | "Luigi Iannone" <ggx@gigix.net> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) D. Farinacci
Request for Comments: 8060 lispers.net
Category: Experimental D. Meyer
ISSN: 2070-1721 Brocade
J. Snijders
NTT
February 2017
LISP Canonical Address Format (LCAF)
Abstract
This document defines a canonical address format encoding used in
Locator/ID Separation Protocol (LISP) control messages and in the
encoding of lookup keys for the LISP Mapping Database System.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Engineering
Task Force (IETF). It represents the consensus of the IETF
community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8060.
Farinacci, et al. Experimental [Page 1]
RFC 8060 LISP Canonical Address Format (LCAF) February 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, et al. Experimental [Page 2]
RFC 8060 LISP Canonical Address Format (LCAF) February 2017
Table of Contents
1. Introduction ....................................................4
2. Terminology .....................................................5
2.1. Requirements Language ......................................5
2.2. Definition of Terms ........................................5
3. LISP Canonical Address Format Encodings .........................6
4. LISP Canonical Address Applications .............................8
4.1. Segmentation Using LISP ....................................8
4.2. Carrying AS Numbers in the Mapping Database ................9
4.3. Assigning Geo-Coordinates to Locator Addresses ............10
4.4. NAT Traversal Scenarios ...................................11
4.5. Multicast Group Membership Information ....................13
4.6. Traffic Engineering Using Re-encapsulating Tunnels ........15
4.7. Storing Security Data in the Mapping Database .............16
4.8. Source/Destination 2-Tuple Lookups ........................17
4.9. Replication List Entries for Multicast Forwarding .........18
4.10. Applications for AFI List LCAF Type ......................19
4.10.1. Binding IPv4 and IPv6 Addresses ...................19
4.10.2. Layer 2 VPNs ......................................20
4.10.3. ASCII Names in the Mapping Database ...............21
4.10.4. Using Recursive LISP Canonical Address Encodings ..22
4.10.5. Compatibility Mode Use Case .......................23
5. Experimental LISP Canonical Address Applications ...............24
5.1. Convey Application-Specific Data ..........................24
5.2. Generic Database Mapping Lookups ..........................25
5.3. PETR Admission Control Functionality ......................26
5.4. Data Model Encoding .......................................27
5.5. Encoding Key/Value Address Pairs ..........................28
5.6. Multiple Data-Planes ......................................29
6. Security Considerations ........................................31
7. IANA Considerations ............................................31
8. References .....................................................32
8.1. Normative References ......................................32
8.2. Informative References ....................................33
Show full document text