Trust Router Problem Statement
draft-schaad-trust-router-problem-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jim Schaad | ||
| Last updated | 2013-12-01 (Latest revision 2013-05-30) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-schaad-trust-router-problem-01.txt
https://www.ietf.org/archive/id/draft-schaad-trust-router-problem-01.txt
Abstract
There are a number of problems with using the current AAA framework for doing access control, this document looks at a number of these issues and poses some questions about how to create a new trust router system.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)