Multi6 Application Referral Issues
draft-ietf-multi6-app-refer-00
| Document | Type |
Expired Internet-Draft
(multi6 WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Erik Nordmark | ||
| Last updated | 2005-01-11 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)