Endpoint Security Classification
draft-mcfadden-endpoint-classification-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark McFadden | ||
| Last updated | 2021-05-06 (Latest revision 2020-11-02) | ||
| 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
It seems reasonable to suggest that, despite the huge variety of types of endpoints on the Internet, there are categories of similarity. These categories are important because categories of endpoint devices may share particular advantages or limitations for endpoint security. This draft attempts to suggest a classification of endpoints as a foundation for further work on operational security. The goal is to identify classes of endpoints with similar characteristics. Those characteristics may lead to the discovery that the devices in a particular category share similar characteristics for endpoint security.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)