Diameter MIPv6 Application for the Integrated Scenario
draft-tschofenig-dime-mip6-integrated-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hannes Tschofenig | ||
| Last updated | 2008-04-16 (Latest revision 2006-03-01) | ||
| Replaced by | draft-ietf-dime-mip6-integrated | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dime-mip6-integrated | |
| 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
A Mobile IPv6 node requires a home agent address, a home address, and 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 existing authentication, authorization and accounting infrastructure. This document defines a Diameter application to facilitate Mobile IPv6 bootstrapping for the integrated scenario.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)