Discovering And Accessing Software Bills of Materials
draft-lear-iotops-onboard-intr-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eliot Lear | ||
| Last updated | 2021-02-22 | ||
| Replaced by | draft-lear-iotops-deep-thoughts-on-onboarding | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-lear-iotops-deep-thoughts-on-onboarding | |
| 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
With various onboarding methods being built out, one aspect that has been overlooked is the trust relationship between the deployment and the manufacturer. This document asks questions about how that trust should be established, and how it can be leveraged.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)