Threat Models introduced by Mobile IPv6 and Requirements for Security
in Mobile IPv6
draft-team-mobileip-mipv6-sec-reqts-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pekka Nikander | ||
| Last updated | 2001-07-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
The IESG returned the MIP v6 draft to the working group due to concerns about the security and scalability of binding updates and the associated IPSEC processing that is specified in the draft. Since that time discussions have continued to attempt to define what is really needed to make binding updates secure. In the course of discussing the requirements it became apparent that a threat model is needed in order to adequately specify the security requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)