Agenda for SUIT Working Group at IETF 120
Monday, July 22, 2024, 17:30 - 18:30 PDT

MeetEcho: https://meetings.conf.meetecho.com/ietf120/?session=33182
Zulip: https://zulip.ietf.org/#narrow/stream/suit
Etherpad: https://notes.ietf.org/notes-ietf-120-suit#

1) Logistics

• Agenda Bashing
• Minute Taker: Kathleen Moriarty, Michael Richardson
• Jabber Scribe
• Bluesheets

2) Draft Status report from Chairs.
- reminder to Henk to review suit-management document.
-
4) SUIT Manifest Format

• draft-ietf-suit-manifest-26
• Submitted to IESG for Publication
• Agreed to change “suit-install = 20” from 17, it is still 17
  Section 11.1, 11.2, Appendix A
• SECDIR Last Call Review due 2024-02-21 Incomplete

• Has 2 DISCUSSes. Needs 2 more YES or NO OBJECTION positions to pass.

  • mostly fixed, new definitions added.
  • statement -> expression.
  • waiting on ART review

  • discussion about whether URI are %-encoded, or UTF-8;
    ~~suggestion that it should be UTF-8. ~~

    • https://www.rfc-editor.org/rfc/rfc8949.html#encodedtext
      references RFC3986, so it's potentially %-encoded.
    • Dave Thaler commented that the SUIT manifest draft currently
      says "suit-parameter-uri
      A UTF-8 encoded URI Reference [RFC3986] from which to
      fetch a resource." but RFC 3986
      requires any non ASCII character to be pct-encoded in a URI.
      Since the
      URI is "intended for machine readable uses, not human
      readable uses",
      there's no reason to ever decode one, so it doesn't matter
      whether it represents
      a UTF-8 string or something else.

  • optimization: do not fetch/copy payloads you already have (check
    by hash)

  • agility added to allow for whatever follows COSE at some point
    in the future
  • are we changing SUIT key? ... so we changing the SUIT key.

• IANA comments, need the authors to confirm Data Item field

• TEEP depends on this

3) SUIT Manifest Extensions for Multiple Trust Domains

• draft-ietf-suit-trust-domains-07

• Submitted to IESG for Publication

• TEEP depends on this
  • ACTION: Dave T will update the shepherd writeup during this
    week, so Deb could review the draft next week

4) Firmware Encryption with SUIT Manifests

• draft-ietf-suit-firmware-encryption-20
• Submitted to IESG for Publication, 2024-07-13, waiting for AD
  feedback
• In IETF last call
• IANA OK
• Depends on draft-ietf-cose-key-thumbprint, Waiting for AD
  Go-Ahead::AD Followup

5) Secure Reporting of Update Status

• draft-ietf-suit-report-09
• In WG Last Call, 2024-03-20
• Shepherd (Akira) - Chair (Dave) review needed
• TEEP depends on this
  Chair will go ahead

6) Strong Assertions of IoT Network Access Requirements

• draft-ietf-suit-mud-09
• Depends on draft-ietf-cose-key-thumbprint, Waiting for AD
  Go-Ahead::AD Followup
• Submitted to IESG for Publication
• IESG state: hold until draft-ietf-suit-manifest clears IESG Review.
• IANA review state: Version Changed - Review Needed
• IETF 119 discussion: URI or IRI? -> Addressed to keep URI
  • ACTION: (Hannes) Tell Roman to ready and go

7) Mandatory-to-Implement Algorithms for SUIT Manifests

• draft-ietf-suit-mti-06
• Depends on draft-ietf-suit-firmware-encryption
• WG Consensus: Write-Up needed Dave W.
• TEEP depends on this
  • MCR comments: could not match HSS-LMS parameters to those in
    RFC8554.
  • Thinks that signing and encryption part of each profile should
    be ",", rather than "+"

8) Update Management Extensions for SUIT Manifests

• draft-ietf-suit-update-management-07
• Waiting for WG Chair Go-Ahead
• Requesting for more review, Henk?

Early review can be used to get a few more reviews

9) Any Other Business (if time permits)