draft-ietf-lisp-introduction-08.txt   draft-ietf-lisp-introduction-09.txt 
Network Working Group A. Cabellos Network Working Group A. Cabellos
Internet-Draft UPC-BarcelonaTech Internet-Draft UPC-BarcelonaTech
Intended status: Informational D. Saucez (Ed.) Intended status: Informational D. Saucez (Ed.)
Expires: May 16, 2015 INRIA Expires: May 16, 2015 INRIA
November 12, 2014 November 12, 2014
An Architectural Introduction to the Locator/ID Separation Protocol An Architectural Introduction to the Locator/ID Separation Protocol
(LISP) (LISP)
draft-ietf-lisp-introduction-08.txt draft-ietf-lisp-introduction-09.txt
Abstract Abstract
This document describes the architecture of the Locator/ID Separation This document describes the architecture of the Locator/ID Separation
Protocol (LISP), making it easier to read the rest of the LISP Protocol (LISP), making it easier to read the rest of the LISP
specifications and providing a basis for discussion about the details specifications and providing a basis for discussion about the details
of the LISP protocols. This document is used for introductory of the LISP protocols. This document is used for introductory
purposes, more details can be found in RFC6830, the protocol purposes, more details can be found in RFC6830, the protocol
specification. specification.
skipping to change at page 4, line 11 skipping to change at page 4, line 11
o An EID within a LISP site carries identifier and limited locator o An EID within a LISP site carries identifier and limited locator
semantics to nodes at other LISP sites (i.e., enough locator semantics to nodes at other LISP sites (i.e., enough locator
information to tell that the EID is external to the site) information to tell that the EID is external to the site)
The relationship described above is not unique to LISP but it is The relationship described above is not unique to LISP but it is
common to other overlay technologies. common to other overlay technologies.
The initial motivation in the LISP effort is to be find in the The initial motivation in the LISP effort is to be find in the
routing scalability problem [RFC4984], where, if LISP is completely routing scalability problem [RFC4984], where, if LISP is completely
deployed, the Internet core is populated with RLOCs while Traffic deployed, the Internet core is populated with RLOCs while Traffic
Engineering mechanisms are pushed to the Mapping System. Where RLOCs Engineering mechanisms are pushed to the Mapping System. In such
are quasi-static (i.e., low churn) and hence, the routing system scenario RLOCs are quasi-static (i.e., low churn), hence making the
scalable [Quoitin] while EIDs can roam anywhere with no churn to the routing system scalable [Quoitin], while EIDs can roam anywhere with
underlying routing system. However, the separation between location no churn to the underlying routing system. [RFC7215] discusses the
and identity that LISP offers makes it suitable for use in additional impact of LISP on the global routing system during the transition
scenarios such as Traffic Engineering (TE), multihoming, and mobility period. However, the separation between location and identity that
among others. LISP offers makes it suitable for use in additional scenarios such as
Traffic Engineering (TE), multihoming, and mobility among others.
This document describes the LISP architecture, its main operational This document describes the LISP architecture, its main operational
mechanisms as its design rationale. It is important to note that mechanisms as its design rationale. It is important to note that
this document does not specify or complement the LISP protocol. The this document does not specify or complement the LISP protocol. The
interested reader should refer to the main LISP specifications interested reader should refer to the main LISP specifications
[RFC6830] and the complementary documents [RFC6831], [RFC6832], [RFC6830] and the complementary documents [RFC6831], [RFC6832],
[RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC7052] for the [RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC7052] for the
protocol specifications along with the LISP deployment guidelines protocol specifications along with the LISP deployment guidelines
[RFC7215]. [RFC7215].
 End of changes. 2 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/