AAA Considerations for Middleware
draft-bakker-middleware-considerations-aaa-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Steven Bakker | ||
| Last updated | 1999-06-29 | ||
| 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
The IETF AAA Working Group is currently looking at defining the requirements for Authentication, Authorization and Accounting. Various documents have already been written that outline AAA requirements for various services and protocols. This document falls into that category, as it outlines some ideas for middleware that have specific AAA requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)