Thoughts About Layer 3.5 Redirection Security
draft-van-beijnum-multi6-redirection-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Iljitsch van Beijnum | ||
| Last updated | 2004-08-16 | ||
| 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
The new multi6 design team as of august 2004 is chartered to explore multihoming by means of a "layer 3.5 wedge" that allows unmodified applications and transport protocols to become address agile. In order to do this, the two hosts involved must communicate certain parameters. The exact nature of this communication isn't specified at this time. However, this document discusses certain security issues pertaining to such communication.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)