SUIT Manifest Extensions for Multiple Trust Domains
draft-ietf-suit-trust-domains-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Author | Brendan Moran | ||
Last updated | 2022-10-17 (Latest revision 2022-03-07) | ||
Replaces | draft-moran-suit-trust-domains | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
IOTDIR Early review
(of
-07)
by Thomas Fossati
On the right track
SECDIR Early Review due 2024-10-01
Incomplete
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Associated WG milestones |
|
||
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 specification describes extensions to the SUIT manifest format (as defined in [I-D.ietf-suit-manifest]) for use in deployments with multiple trust domains. A device has more than one trust domain when it uses different trust anchors for different purposes or components in the context of firmware update.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)