Architectural Implications of Locator/ID Separation
draft-meyer-loc-id-implications-01

Document Type Expired Internet-Draft (individual)
Last updated 2009-01-26
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-meyer-loc-id-implications-01.txt

Abstract

Recent work on Locator/ID Separation has focused primarily on the control plane protocols concerned with finding Identifier-to-Locator mappings. However, experience gained with a trial deployment of a system designed to implement Locator/ID Separation has revealed two general classes of problems which must be resolved after the mapping is found: The Locator Path Liveness Problem and the State Synchronization Problem. These problems have implications for the data plane as well as the control plane.

Authors

Darrel Lewis (darlewis@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)