Securing MIPv6 BUs using return routability (BU3WAY)
draft-nordmark-mobileip-bu3way-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Erik Nordmark | ||
| Last updated | 2001-11-13 | ||
| 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
This document is intended to serve as input to the discussion in the Mobile IP Working Group regarding securing MIPv6 Binding Updates. This document tries to capture a possible extreme point in the design space for a solution to that problem, for the purposes of exploring the design space. The author does not claim that this protocol is better than any other proposed solutions - merely that it is different and the differences can help in understanding design tradeoffs in this space.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)