Identifier / Locator Separation: Exploration of the Design Space (ILSE)
draft-nikander-ram-ilse-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pekka Nikander | ||
| Last updated | 2007-02-28 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Implementing the so called identifier / locator separation may have far-reaching consequences to the Internet architecture, depending very much on how exactly it is implemented. That is, here as in many other cases, the devil lies very much in the details. In this document, we attempt to outline the various aspects of the design space. We briefly discuss six main aspects: identifiers, dynamic traffic management, end-to-end issues, security, economics, and deployment. In this initial version of the document, we still lack many details. This document is a reaction to the problem statement effort at the Amsterdam IAB Routing and Addressing Workshop (RAWS).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)