Shim6 Application Referral Issues
draft-ietf-shim6-app-refer-00
| Document | Type | Expired Internet-Draft (shim6 WG) | |
|---|---|---|---|
| Last updated | 2005-07-05 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| 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-ietf-shim6-app-refer-00.txt
https://www.ietf.org/archive/id/draft-ietf-shim6-app-refer-00.txt
Abstract
In order to fully solve the scalable multihoming problem there is a need to separate the current IP address functionality into identifiers (which are used to identify e.g., TCP connections) and locators which are used to forward packets in the routing system. Such a separation has an impact on the current use of IP address in the application layer. This document presents these issues for the purposes of stimulating discussions.
Authors
Erik Nordmark (nordmark@acm.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)