# IETF 121 Recap --- ## What's 121 again? - IETF meetings quarterly - 121 was the most recent - A few parts - Hackathon - Meeting sessions, where the actions happen --- ## Hackathon - Updates to an [implementation of SCRAPI](https://datatracker.ietf.org/doc/draft-ietf-scitt-scrapi/) to kick the draft's tires - Changes needed, coming up in next slides - Feasability of SCITT with YANG-based SBOM ([RFC9472](RFC9472)) - Feasability of SCITT with [Virtualized Conversations (VCON)](https://datatracker.ietf.org/wg/vcon/documents/)) --- ## Session updates - WG wants to push [the architecture](https://datatracker.ietf.org/doc/draft-ietf-scitt-architecture/) for a WG last call - Heads down on SCRAPI - Not JSON responses, CBOR only, JSON/CBOR mismatch confusing and problematic for developers - Possibly remove the [resolve statement endpoint](https://datatracker.ietf.org/doc/html/draft-ietf-scitt-scrapi-02#name-resolve-statement) --- ## Resources - [WG documents](https://datatracker.ietf.org/wg/scitt/documents/) - [IETF 121 agenda for the WG](https://datatracker.ietf.org/doc/agenda-120-mediaman/) - [Slides](https://datatracker.ietf.org/meeting/121/materials/slides-121-scitt-ietf-121-scitt-01) - [YouTube recording](https://www.youtube.com/watch?v=1EQCTediRWI) --- ## What does it mean for us? - IETF needs us to implement - When we implement, we need to focus on - API surface and going all CBOR - Different tree implementations - Interactions between different payloads and API --- ## Conclusion Et fin.