Re: [Suit] intentional rollback of firmware

[Michael Richardson <[e-mail]>]

Dave Thaler <[e-mail]> wrote:
    > https://tools.ietf.org/html/draft-ietf-suit-information-model-04#section-4.3.1 says:
    >> Note: This is not a firmware version.  It is a manifest sequence
    >> number.  A firmware version may be rolled back by creating a new
    >> manifest for the old firmware version with a later sequence number.

    > The information model doc is referenced in several places in the
    > architecture, but maybe it should be explicit about the threat model is
    > covered in detail in the information model document.

Thank you for this pointer.
I didn't think I'd find it in the info model, but in hindsight, it makes
sense.  It shows that I haven't paid enough attention to the information
model document. (Damn WG conflicts. I see it's in WGLC, which I had spaced too)

I want to suggest a tweak to the abstract:

OLD:
   One component of such a firmware update is a concise and machine-
   processable meta-data document, or manifest, that describes the
   firmware image(s) and offers appropriate protection.  This document
   describes the information that must be present in the manifest.

NEW:
   One component of such a firmware update is a concise and machine-
   processable meta-data document, or manifest, that describes the
   firmware image(s) and offers appropriate protection.  This document
   describes a series of security threats, along with the types of
   information that must be present in the manifest in order to deal
   with the threats.



--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-