RADIUS Mobile IPv6 Support
draft-chowdhury-mip6-radius-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Kuntal Chowdhury | ||
| Last updated | 2008-03-03 (Latest revision 2006-06-28) | ||
| Replaced by | draft-ietf-mip6-radius | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mip6-radius | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-chowdhury-mip6-radius-02.txt
Abstract
A Mobile IPv6 node requires a home agent address, a home address, and an IPsec security association with its home agent before it can start utilizing Mobile IPv6 service. RFC 3775 requires that some or all of these parameters are statically configured. Ongoing work aims to make this information dynamically available to the mobile node. An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with the existing authentication, authorization and accounting infrastructure. This document defines new attributes that facilitate Mobile IPv6 bootstrapping via a RADIUS infrastructure. This information exchange may take place as part of the initial network access authentication procedure or as part of a separate protocol exchange between the mobile node, the home agent and the AAA infrastructure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)