Network Access Server Requirements Next Generation (NASREQNG) Operational Model
draft-mitton-nasreqng-model-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Mitton | ||
| Last updated | 1998-08-07 | ||
| 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
This document describes the terminology and an operational model of typical Network Access Server (NAS). The purpose of this effort is to set the reference space for describing and evaluating NAS service protocols, such as RADIUS (RFC 2138, 2139) and follow-on efforts like Diameter (draft-calhoun-diameter-04.txt). These are protocols for carrying authentication, authorization, and user configuration information between a Network Access Server which desires to authenticate its calls and a shared Authentication Server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)