Threats Introduced by Rserpool and Requirements for Security in response to Threats
draft-stillman-rserpool-threats-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Maureen Stillman | ||
| Last updated | 2002-03-01 | ||
| 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 Internet draft is an attempt to describe security threats against the Rserpool protocol. This draft presents requirements for a security solution to thwart these threats in environments where it is likely to be deployed. The threats and requirements identified herein and the document should be considered as work in progress.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)