Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A2A130DF9 for ; Wed, 4 Jul 2018 01:26:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nordicsemi.no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJzfnal7b_a4 for ; Wed, 4 Jul 2018 01:26:29 -0700 (PDT) Received: from ironport01.nordicsemi.no (mx01.nordicsemi.no [194.19.86.146]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A39B912426A for ; Wed, 4 Jul 2018 01:26:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nordicsemi.no; l=10407; s=default; t=1530692788; h=from:to:subject:date:message-id:mime-version; bh=/kb0sUNLKC4amhsjB4Mgxalp1xm8fmFsuPMk0BwON38=; b=cPE/YFYE8PTl939L8LtNurXUmBUSpdYuYeI1LcGBqNLEoWqkvout/45p /ub0DYrz6y8AWmi2iIN07ZP2kkmojEoy+lr8f4CALUni8nVoJVArM3Een lEMh2oBrnA8Sp2eYlUOPRUxuKUvQL2uQDds8YfVBbt5SKXE7D82WRwViE 8=; X-IronPort-AV: E=Sophos; i="5.51,306,1526335200"; d="scan'208,217"; a="11226791" From: =?iso-8859-1?Q?R=F8nningstad=2C_=D8yvind?= To: suit Thread-Topic: draft-moran-suit-manifest-02 Thread-Index: AdQTbk+t1KsTGeClRXioTvYSJXY/hw== Date: Wed, 4 Jul 2018 08:26:25 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.9.200.83] Content-Type: multipart/alternative; boundary="_000_edc46af214244a119950582014c8dbfenordicsemino_" MIME-Version: 1.0 Archived-At: Subject: [Suit] draft-moran-suit-manifest-02 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 08:26:33 -0000 --_000_edc46af214244a119950582014c8dbfenordicsemino_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 assu= me 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 whi= ch 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 c= omment 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 process= or 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 us= e the custom types for StorageIdentifier and ComponentIdentifier. * I think digests should have a type, so the user can more easily re= strict its format after choosing a digest algorithm. * Suggestion: Add nint to textKeys group. * AuthenticatedManifest should probably contain an authenticatedMani= festVersion or similar. * "Processor" might be confusing ("does it mean CPU?"). =D8yvind --_000_edc46af214244a119950582014c8dbfenordicsemino_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thank= s Brendan (and Hannes) for all your great work on the documents.=

=  

I hav= e some of questions and comments regarding the manifest format:<= /span>

=  

  • I'm still not 100% sure of the intended differen= ce between extensions and directives, can you put a sentence into the docum= ent?
  • No element has more t= han one inode or onode. How would "one resource may be used by multipl= e processors" work?
  • I= f 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 w= hich 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 de= pendency resources serve as input to processors or targets? If so, what dat= a 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 Pro= cessor, TargetInfo vs Target.
    • There's probably a typo in the definition of Directive. Should it be an= array of maps?
    • Target::s= torageIdentifier and Target::componentIdentifier don't use the custom types= for StorageIdentifier and ComponentIdentifier.
    • I think digests should have a type, so the user can m= ore easily restrict its format after choosing a digest algorithm.
    • Suggestion: Add nint to textKeys gr= oup.
    • AuthenticatedManifest= should probably contain an authenticatedManifestVersion or similar.
    • "Processor" might be c= onfusing (“does it mean CPU?”).

 

=D8yvind

 

--_000_edc46af214244a119950582014c8dbfenordicsemino_--