MIPv6 Security: Assessment of Proposals
draft-montenegro-mobileip-mipv6-seceval-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gabriel Montenegro , Alexandre Petrescu | ||
| Last updated | 2001-11-19 | ||
| 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 IESG has identified several security issues with the current Mobile IPv6 specification [MIPv6]. A subsequent effort [MIPv6SecReq] details the security threats introduced by MIPv6. Two major issues are (1) how to obtain a security association between an arbitrary MN and CN such that the binding update (BU) is secure, and, assuming such a mechanism is in place, (2) how to secure the individual BU messages. This document is an assessment of the proposed solutions for problem (1).
Authors
Gabriel Montenegro
Alexandre Petrescu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)