[Suit] draft-moran-suit-manifest-02

[Rønningstad, Øyvind <[e-mail]>]

Thanks Brendan (and Hannes) for all your great work on the documents.

I have some of questions and comments regarding the manifest format:


  *   I'm still not 100% sure of the intended difference between extensions and directives, can you put a sentence into the document?
  *   No element has more than one inode or onode. How would "one resource may be used by multiple processors" work?
  *   If a processing step or target takes multiple input resources (I assume this happens when they all specify the same onode), how does the process know which resource is which (which blob is the compression table, and which is the data)? I.e. how is the order of arguments decided?
  *   What does it mean for a Target to be an alias (I'm referring to the comment on Target::encoding: "the format of the resource (nil when alias)")?
  *   Can dependency resources serve as input to processors or targets? If so, what data does the dependency resource provide as input to that processor or target? If not, what should the onode value be?
  *   CDDL nitpicking:
     *   Some name inconsistencies: ProcessingStep vs Processor, TargetInfo vs Target.
     *   There's probably a typo in the definition of Directive. Should it be an array of maps?
     *   Target::storageIdentifier and Target::componentIdentifier don't use the custom types for StorageIdentifier and ComponentIdentifier.
     *   I think digests should have a type, so the user can more easily restrict its format after choosing a digest algorithm.
     *   Suggestion: Add nint to textKeys group.
     *   AuthenticatedManifest should probably contain an authenticatedManifestVersion or similar.
     *   "Processor" might be confusing ("does it mean CPU?").

Øyvind