Capabilities and Limitations of an Endpoint-only Security Solution
draft-taddei-smart-cless-introduction-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Arnaud Taddei , Candid Wueest , Kevin A. Roundy , Dominique Lazanski | ||
| Last updated | 2020-07-12 (Latest revision 2020-01-09) | ||
| RFC stream | (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 the context of existing, proposed and newly published protocols, this draft RFC is to establish the capabilities and limitations of endpoint-only security solutions and explore benefits and alternatives to mitigate those limits with the support of real case studies.
Authors
Arnaud Taddei
Candid Wueest
Kevin A. Roundy
Dominique Lazanski
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)