Mechanism to Support CHAP Mobile Node Authentication for RADIUS/DIAMETER Hybrid AAA Networks
draft-ietf-mobileip-radius-challenge-00
Document | Type |
Expired Internet-Draft
(mobileip WG)
Expired & archived
|
|
---|---|---|---|
Authors | Ken Peirce , Yingchun Xu , Ed Campbell | ||
Last updated | 1999-06-25 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
Mobile IP Authentication is a requirement for the TR 45.6 CDMA wireless packet data service architecture[8]. Diameter AAA, as described in [1] and [2], is used to support Mobile IP authentication. This requires that both the foreign and home network deploy Diameter servers. Currently, RADIUS servers have been deployed and are widely used in the Internet Service Provider(ISP) arena.While DIAMETER is required to provide the advanced AAA support required by the TR 45.6 architecture, a smooth transition from RADIUS AAA to Diameter AAA is required. At a minimum,the Diameter AAA server located in a foreign network must inter-operate with RADIUS AAA located in Home Network.
Authors
Ken Peirce
Yingchun Xu
Ed Campbell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)