An Architectural Perspective on the LISP Location-Identity Separation System
draft-chiappa-lisp-architecture-01
Document | Type |
Replaced Internet-Draft
(lisp WG)
Expired & archived
|
|
---|---|---|---|
Author | J. Noel Chiappa | ||
Last updated | 2013-01-08 (Latest revision 2012-07-16) | ||
Replaced by | draft-ietf-lisp-architecture | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | Joel M. Halpern | ||
IESG | IESG state | Replaced by draft-ietf-lisp-architecture | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
LISP upgrades the architecture of the IPvN internetworking system by separating location and identity, current intermingled in IPvN addresses. This is a change which has been identified by the IRTF as a critically necessary evolutionary architectural step for the Internet. In LISP, nodes have both a 'locator' (a name which says _where_ in the network's connectivity structure the node is) and an 'identifier' (a name which serves only to provide a persistent handle for the node). A node may have more than one locator, or its locator may change over time (e.g. if the node is mobile), but it keeps the same identifier. This document gives additional architectural insight into LISP, and considers a number of aspects of LISP from a high-level standpoint. [NOTE: This is still a somewhat rough draft version; a few sections at the end are just rough frameworks, but almost all the key sections, and all the front part of the document, are here, and in something like reasonably complete form.]
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)