Data Objects and Message Types in the Generic AAA Architecture
draft-spence-aaaarch-objmsg-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Spence | ||
| Last updated | 2001-01-25 | ||
| 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 memo specifies the top level data objects to be carried in an AAA Protocol that supports the generic AAA architecture described in RFC 2903. It also specifies the required message types. Data objects and message types are defined in an abstract way without regard to encoding. The message types defined could be thought of as the use cases (in the UML sense) for a generic AAA server. They define what can be asked of or provided to a generic AAA server. The data objects specify what kinds of information can be routed among the AAA servers in the generic AAA infrastructure. Suggestions as to which data objects would be carried in each message type are provided.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)