**Session Date/Time:** 19 Feb 2026 07:00

# [ASDF](../wg/asdf.html)

## Summary

This interim meeting focused on updates to the `SDF Supplements` (formerly mapping files), `Instance Information`, `Nipsey`, and `SDF Protocol Mapping` drafts. The working group celebrated the publication of the ASDF base specification as an RFC. Key discussions revolved around structural and terminology updates in the supplements draft, clarifications to the Nipsey triggers, and a proposed simplification for protocol mappings in the SDF protocol mapping draft. The group also discussed the timing of the Nipsey Last Call and tentatively scheduled the next interim meeting.

## Key Discussion Points

*   **ASDF Base Specification Publication:** The working group celebrated the publication of the ASDF base specification as an RFC.
*   **SDF Supplements (formerly Mapping File) Draft:**
    *   The draft was recently adopted by the working group.
    *   Renamed from "mapping file" to "supplements" to avoid ambiguity and ensure consistent terminology.
    *   The `map` quality was reworked to `amend`, now modeled as an array of objects to enable deterministic processing of patches, with a JSON pointer specifying the patch location.
    *   An algorithm for tracing the provenance of augmented models was added, including a pointer to the original SDF model and a log of augmentations.
    *   **Future work items:** Revisit the JSON merge patch algorithm for potential semantic references, specify a collection/container for combining models with multiple supplements, and address model evolution questions, including indicating backward compatibility of individual patches.
    *   The basic functionality for deterministic patch application is considered stable for implementation, with future extensions for different patch mechanisms or parameters being compatible additions.
*   **Instance Information Draft:**
    *   A new revision was published with minor updates, including referencing the newly published ASDF base RFC, fixing an example, and updating terminology.
    *   Continued engagement with Etri and the Litmus test is planned.
*   **Nipsey Draft (draft-ietf-asdf-nipsey):**
    *   Draft 17 was published, closing all 11 previously open GitHub issues.
    *   Trigger APIs were updated (YAML, CDDL, text) based on feedback regarding event-triggered actions.
    *   New IANA registries were added for protocol info and the pub-sub CBOR interface.
    *   **Nipsey Triggers Refinement:** It was clarified that triggers should *always* be installed on an event and *always* trigger an action, as triggering on an action by the gateway is redundant. Existing event reporting in the PubSub interface is sufficient to inform applications of trigger execution.
    *   The triggers functionality has not yet been implemented, and an implementation is unlikely before the Last Call.
    *   **Working Group Last Call (WGLC) Discussion:** The current WGLC is scheduled to end around March 4th. Concerns were raised by participants about insufficient time for review before this deadline. A sense of those present indicated a preference for extending the review period by approximately one week or allowing the WGLC to run its course and incorporating feedback shortly after, delaying the forwarding for publication. This would be discussed with the Area Director.
*   **SDF Protocol Mapping Draft:**
    *   Draft 4 was published, primarily updating references (e.g., SDF draft to RFC) and making minor type fixes.
    *   **Pending Issue (Protocol Mapping Structure):** A key pending issue involved the placement of the `protocolMap` keyword. Currently, it is at the affordance level for properties but under `SDF input/output data` for actions and events. A proposal was made to simplify this by placing `protocolMap` consistently at the affordance level for all three (properties, actions, events).
    *   **Discussion on Protocol Mapping Simplification:** No clear use cases for different input/output protocol mappings were identified at the Nipsey level. It was noted that lower-level protocols like CoAP already have mechanisms to handle different request/response paths. The working group's sense was that this simplification makes sense, and extensions for input/output specific mappings could be added later if a strong use case emerges, potentially with an override mechanism.

## Decisions and Action Items

*   **SDF Supplements:**
    *   **Decision:** The draft name is formally changed to "SDF Supplements," and internal terminology is updated to consistently use "supplements" and "amendments."
    *   **Action Item:** Jan to continue work on the identified future items, including revisiting the JSON merge patch algorithm, defining a container for supplements, and addressing model evolution.
*   **Nipsey Draft:**
    *   **Decision:** Nipsey triggers will be specified to *only* be installed on events and *always* trigger actions. The existing PubSub event reporting is sufficient for execution notification.
    *   **Action Item:** Bart/Rohit to discuss with the AD (Michael) the possibility of extending the Working Group Last Call review period or allowing it to run and incorporate feedback shortly after its official end.
    *   **Action Item:** All WG participants are encouraged to perform a final review of the Nipsey draft.
*   **SDF Protocol Mapping Draft:**
    *   **Decision:** The `protocolMap` keyword will be simplified to be consistently placed at the affordance level for properties, actions, and events.
    *   **Action Item:** Rohit to implement the agreed-upon simplification for the `protocolMap` structure in the draft.
    *   **Action Item:** Rohit to prepare the draft for a final working group review before Last Call.

## Next Steps

*   **Next Interim Meeting:** A next interim meeting is tentatively scheduled for **March 11th, at 8 AM Central European Time**, with a focus on Nipsey and SDF Protocol Mappings. Further coordination for participant availability will be conducted.