Authentication Mandate for All Registration Reply Messages
draft-perkins-mip4-authreqd-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Charles E. Perkins | ||
| Last updated | 2009-10-12 | ||
| 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
Some implementations of Mobile IP home agents have been observed to supply zero authentication data when sending a Registration Reply to the mobile node that contains rejection code 131 (Mobile Node Failed Authentication). This creates a vulnerability whereby a mobile node could be denied service from its home agent, and thus lose connectivity to the Internet even though mobile node and home agent were otherwise functioning properly.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)