DIAMETER Framework Document
draft-calhoun-diameter-framework-09
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Glen Zorn , Ping Pan , Pat R. Calhoun , Haseeb Akhtar | ||
| Last updated | 2001-02-05 | ||
| 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
Current Internet Service Providers (ISPs) scale their networks by using the RADIUS protocol, which provides user Authentication, Authorization and Accounting (AAA) of Dial-up PPP clients. The recent work done in the Roaming Operations (ROAMOPS) Working Group was to investigate whether RADIUS could be used in a roaming network, and concluded that RADIUS was ill-suited for inter-domain purposes. The IETF has formed a new NAS Requirements Working Group, and part of their charter is to document the next generation NAS' AAA requirements. Recently, the Mobile-IP Working Group also documented their own AAA requirements that would help Mobile IP scale for Inter-Domain mobility. The DIAMETER protocol is a follow-on to the RADIUS protocol. DIAMETER addresses the known RADIUS deficiencies, and is intended for use with the NASREQ and Mobile IP application space.
Authors
Glen Zorn
Ping Pan
Pat R. Calhoun
Haseeb Akhtar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)