Policies in a Generic AAA Environment
draft-taal-aaaarch-generic-pol-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Arie Taal , Guus Sliepen , David Spence | ||
| Last updated | 2001-03-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
In this document a formal model of a policy is presented in the context of a generic AAA environment. We will focus our attention on that kind of policy that is evaluated in response to a request of a user [OBJMSG]. That policy will determine all requirements that need to be fulfilled before the service asked for will be delivered. We will introduce the concept of a Driving Policy.
Authors
Arie Taal
Guus Sliepen
David Spence
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)