SACM ECP Recommendations
draft-haynes-sacm-ecp-recommendations-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Haynes , Charles Schmidt , Jessica Fitzgerald-McKay | ||
| Last updated | 2016-04-20 (Latest revision 2015-10-18) | ||
| 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 document builds off of [I-D.fitzgeraldmckay-sacm-endpointcompliance] and [I-D.haynes-sacm-ecp-mapping] to provide high-level recommendations for which Trusted Computing Group [TCG] Endpoint Compliance Profile [Endpoint-Compliance-Profile] specifications might be most productively brought into the IETF SACM Working Group (WG). Each section considers the alignment of an ECP specification with SACM, how the specification could be leveraged by SACM as well as potential modifications, and suggests a prioritization of specifications for submission to the SACM WG.
Authors
Daniel Haynes
Charles Schmidt
Jessica Fitzgerald-McKay
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)