**Session Date/Time:** 18 Mar 2025 02:30

# core

## Summary
This session of the core working group at IETF 122 covered a wide range of topics, including document status updates, clarifications, conditional attributes, DNS over CoAP, PubSub, transport indication, multicast notifications, key updates, and CoAP in space.  Significant progress was reported on several documents moving towards publication.  Discussions focused on technical details, outstanding issues, and future directions for the working group.

## Key Discussion Points

*   **Corrections and Clarifications Document (Korklar):** Discussed including "gaps" (unsatisfactory semantics in existing specifications) in the Korklar document alongside incorrect and incomplete cases.  Decision made to proceed with adding gaps to the document.
*   **Kau-Conf:** Discussed the status of YANG model SID assignment. Currently generating SIDs for all YANG models in RFCs and will then allocate SID ranges for each. A fork of fog of Piang tool is available.
*   **HRF (Constrained Resource Identifiers):** Draft-20 has addressed working group last call comments. Discussion on whether to submit to IESG now or conduct a second working group last call. Will follow up with the shepherd (Thomas) before proceeding.
*   **Conditional Attributes for CoAP Observe:** Open issues related to handling complex data structures and mixing query parameters. Consideration of limiting support to scalar/boolean values.
*   **DNS over CoAP Bundle:** Two documents, dns-over-coap and coap-dtls-clpn, are ready to proceed to the shepherd write-up. Cordial (DNS over CoAP with OSCAR) needs sharpening and reviews.
*   **PubSub for CoAP:**  Review of recent updates, including IANA clarifications and addressing shepherd write-up issues.  Discussion on RFC and Ops attribute elision. The decision was to elide the resource type.
*   **Transport Indication:**  Discussion of the document's goals: advertising transport capabilities and establishing a process for new CoAP transports.  Need for reviews, with a focus on the question of whether the literal part needs to be present in this document or whether a sketch is sufficient.
*   **Observe Multicast Notifications:**  Discussion of forbidden redirections, a point of time parameter for terminating group observations, and reverse proxy setup.  Suggestion to separate the specification from examples to improve accessibility. The reverse proxy setup may be moved to another document as it's not normative.
*   **Kudos (Key Update for OSCORE):** Update on major redesign with a more flexible and simpler approach based on nances. Updates for aligning the ID Update and Key Usage Limit documents.
*   **CoAP over Bundle Protocol and CoAP in Space:** Updates on new sections on proxying and message aggregation. In scenarios with CoAP proxies, BPSEC cannot ensure the protection of application layer data between a CoAP client and the CoAP origin server (OSCORE should be used). Also, there is a request for IANA to add the payload length option to the co-option numbers registry.

## Decisions and Action Items

*   **Korklar:** Add "gaps" to the document, describing unsatisfactory semantics in existing specifications.
*   **HRF:** Follow up with shepherd Thomas regarding the necessity of another working group last call.
*   **Conditional Attributes:** Bill will update the document based on discussion, including potential limitations on supporting complex data structures.
*   **DNS over CoAP Bundle:** Complete shepherd write-ups for dns-over-coap and coap-dtls-clpn.
*   **PubSub for CoAP:**  Jaime will update the editor copy in GitHub with the changes, submit version 19, and then start the shepherd write-up.
*   **Transport Indication:**  Authors to address the feedback regarding how literals are handled. Focus review efforts on this document.
*   **Observe Multicast Notifications:**  Explore separating the specification from examples, potentially moving proxy-related content to a separate informational document.
*   **Kudos:** Align related documents on ID Update and Key Usage Limits with the new kudos state machine design.

## Next Steps

*   Authors to implement changes based on feedback.
*   Shepherds to continue shepherding documents towards publication.
*   Working group to provide reviews on outstanding drafts.
*   Coordinate with other working groups (e.g., T2TRG, tip-top) where applicable.