*.suit Filename

[hannestschofenig]

The examples in Section 4.4 give the impression that there is a registered filename suffix with .suit. I don't believe there is.

[dthaler]

They're just examples, and having an extension might be helpful.

[dthaler]

@hannestschofenig what are you proposing here? Remove the .suit suffix?

[hannestschofenig]

My proposal is to remove the suffix.

[kentakayama]

@hannestschofenig @dthaler @mcd500
My apology for slow reply. Do I need to remove the prefix also in the personalization example?
It also affect to the hash value and signature in suit-authentication-wrapper.

• teep-protocol/cbor/suit_personalization.diag.txt

  Line 26 in 36bb3b9

  'suit'

• teep-protocol/cbor/suit_personalization.diag.txt

  Line 50 in 36bb3b9

  'config.suit'

• teep-protocol/cbor/suit_personalization.diag.txt

  Line 67 in 36bb3b9

  / uri / 21: "https://example.org/8d82573a-926d-4754-9353-32dc29997f74.suit"

Note

We need to distinguish the Trusted Component and its SUIT Manifest.
They in the example will be stored like:

• TEEP-Device/
  • SecureFS/
    • 8d82573a926d4754935332dc29997f74/
      • ta
      • suit
    • config.json
    • config.suit

If I remove just .suit it would be

• TEEP-Device/
  • SecureFS/
    • 8d82573a926d4754935332dc29997f74/
      • ta
      • suit
    • config.json
    • config

If I remove all suit it would be

• TEEP-Device/
  • SecureFS/
    • 8d82573a926d4754935332dc29997f74/
      • ta
      • ???
    • config.json
    • config

In my opinion, as the SUIT Manifest itself is also a component, some sort of identifier describing it is a SUIT Manifest is valuable.

[dthaler]

Fixed in draft -17