Mobile IPv6 Residual Threats
draft-haddad-mext-mip6-residual-threats-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Wassim Haddad , George Tsirtsis , Benjamin Lim , Suresh Krishnan , Francis Dupont | ||
| Last updated | 2008-07-14 | ||
| 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 memo aims to highlight specific "residual" threats in Mobile IPv6 protocol. We call these threats "residual" simply because they were rightfully deemed not urgent during the design of Mobile IPv6 protocol. However, these threats are somehow benefiting from new mechanisms and/or extensions built on top of Mobile IPv6 protocol to improve their effects and likelihood. Hence, our main goal is to motivate designers to re-assess their potential taking into consideration these new mechanisms.
Authors
Wassim Haddad
George Tsirtsis
Benjamin Lim
Suresh Krishnan
Francis Dupont
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)