Re: [Suit] Proposal for changes to draft-ietf-suit-manifest

[Brendan Moran <[e-mail]>]

I have now added the final set of changes prior to submission of this update. The text is available in GitHub. If there is no feedback, I plan to submit this version early this evening.

https://github.com/suit-wg/manifest-spec/pull/1

Best Regards,
Brendan

> On 1 Nov 2019, at 08:53, Brendan Moran <[e-mail]> wrote:
>
> I have published a pull-request that has this proposed structure.
>
> https://github.com/suit-wg/manifest-spec/pull/1
>
> Best Regards,
> Brendan
>
>> On 31 Oct 2019, at 14:16, Brendan Moran <[e-mail]> wrote:
>>
>> I would like to propose a set of changes to draft-ietf-suit-manifest for the 02 version.  This set of changes has no effect on the encoding and is purely organisational for the draft, though it introduces new text. This new organisation would have approximately the following layout:
>>
>>  1.  Introduction
>>  2.  Conventions and Terminology
>>  3.  Overview
>>      3.1.  How to use this document
>>      3.2.  Background
>>            3.2.1.  Landscape
>>            3.2.2.  Update Workflow Model
>>            3.2.3.  SUIT Manifest goals
>>            3.2.4.  SUIT manifest design summary
>>  4.  Interpreter Behaviour
>>      4.1.  Interpreter Setup
>>      4.2.  Required Checks
>>      4.3.  Interpreter fundamental properties
>>      4.4.  Abstract Machine Description
>>            4.4.1.  Parameters
>>            4.4.2.  Commands
>>            4.4.3.  Command Behaviour
>>      4.5.  Serialized Processing Interpreter
>>  5.  Creating Manifests
>>      5.1.  Manifest Source Material
>>      5.2.  Use Case Templates
>>  6.  Manifest Structure
>>  7.  Dependency processing
>>  8.  Access Control Lists
>>  9.  SUIT digest container
>>  10.  Creating conditional sequences
>>  11.  Full CDDL
>>  12.  Examples
>>
>> Sections 3, 4, 5 are new. 3 contains mostly existing content with a new “how to use this document” section. Section 4 describes the behaviour of a manifest interpreter. Section 4 could give rise to a set of test vectors for manifest interpreters so that we can ensure correctness. Section 5 specifies what a manifest compiler needs to do.
>>
>> I would also like feedback from the working group on the possibility of removing the examples section and placing that in a separate informative draft.
>>
>> Best Regards,
>> Brendan
>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>> _______________________________________________
>> Suit mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/suit
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> _______________________________________________
> Suit mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/suit

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.