Radius Mobility Extensions
draft-gondi-radext-radius-mobility-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vamsi Gondi , Nazim Agoulmine | ||
| Last updated | 2008-02-15 | ||
| 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
Increase in the usage of different access networks, the role of Radius server is increased to provide access across different access networks and access technologies. AAA server provides access to user terminals in different security mechanisms in access networks. Due to the robust architecture of radius server, the functionalities of server can be extended to provide different services other than the authentication and access to the user terminal. In this draft we are proposing to extend the functionalities of the radius server for the mobility management of the user in the access networks. In this process the Radius server performs the mobility context management of the user when its roaming or during handover from the visiting network and the home network. In this draft we are proposing to accommodate Proxy Mobile IP (PMIP) using these extensions. In this proposed architecture we have defined new attributes and packet format when a Radius server communicates with the MPA/HA of the PMIP architecture as well as with another Radius server for context management.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)