Markdown Version | Session Recording

Session Date/Time: 11 Mar 2026 07:00

ASDF

Summary

The ASDF Working Group held its fourth interim meeting to discuss the status of its two Working Group Last Call documents: ASDF NIPSE and ASDF Protocol Mapping. Key discussions focused on setting deadlines for reviews, addressing open issues regarding keyword naming and the inclusion of IP-based protocol examples, and planning for the next steps towards publication. Decisions were made on review deadlines and how to address the remaining issues for both documents.

Key Discussion Points

• ASDF NIPSE Document Status:

  • There had been no new issues or comments submitted on the NIPSE document since the previous interim meeting.
  • Ari and Karsten indicated they planned to provide further reviews, with Karsten noting he was beginning a NITS (Nitpicking Important Technical Suggestions) review.
  • The group discussed the balance between achieving thorough reviews and adhering to a timeline. The sense of those present was to prioritize thorough review to proactively address potential issues before ISG review.

• ASDF Protocol Mapping Document Status:

  • Keyword Naming (Protocol Binding vs. Protocol Mapping): The long-standing discussion regarding the keyword "protocol binding" versus "protocol mapping" was revisited. Bart explained that "binding" has an existing specific meaning in device-to-device communication (e.g., ZigBee), reinforcing the preference for "protocol mapping" to avoid ambiguity. Jan, who had previously favored "binding," expressed satisfaction with this rationale.
  • Connection to Main ASDF RFC: Jan suggested that the Protocol Mapping draft should include prose to explicitly connect its "protocol mapping" concept to the "protocol binding" terminology found in the main ASDF RFC (RFC 9980) for improved conceptual clarity.
  • Inclusion of IP-based Protocol Examples: Wouter's feedback, noting that the document currently lacks IP-based examples despite claiming support for both IP and non-IP protocols, was discussed. The group acknowledged that an IP example would strengthen the document.
  • "SDF Context" Dependency and Normative References: Bart raised a concern about a potential normative dependency on an "SDF context" or "instance information" draft for an experimental CoAP protocol mapping (work being led by Jan). He emphasized that a protocol map for IANA registration should ideally be self-contained and not have normative dependencies on other ASDF-specific drafts. Jan clarified that his experimental CoAP work does use context information to complement class-level protocol information but that any reference in the ASDF Protocol Mapping draft would be informative, not normative, to avoid blocking progress. Karsten advised caution, stating that introducing detailed new examples now could destabilize the document and that "clarity jeopardizes consensus."

Decisions and Action Items

• ASDF NIPSE Review Deadline:

  • Reviews for the ASDF NIPSE document are requested by April 15th.
  • Authors aim to process all received reviews by April 25th.
  • Action: All WG members to provide thorough reviews of the ASDF NIPSE document by April 15th.
  • Action: Bart and co-authors to process incoming reviews and prepare updates by April 25th.

• ASDF Protocol Mapping Updates:

  • The keyword "SDF Protocol Mapping" will be retained.
  • Action: Bart and co-authors to add clarifying prose to the SDF Protocol Mapping draft to link its concept of "protocol mapping" with "protocol binding" as defined in the main ASDF RFC (RFC 9980).
  • IP Example Strategy: If Jan releases a first version of an experimental CoAP protocol mapping draft within the next month, an informative reference to it can be added to the SDF Protocol Mapping document. Otherwise, the document will include text stating that work on IP examples is ongoing. Any references to IP examples will be informative only, to avoid introducing normative dependencies that could hinder IANA registration.
  • Action: Jan to consider releasing a preliminary CoAP protocol mapping draft for informative reference.
  • Action: Bart and co-authors to update the SDF Protocol Mapping draft with the agreed prose and reference strategy for IP examples.

Next Steps

• Next Interim Meeting: The next interim meeting is scheduled for April 22nd at 9:00 AM Eastern European Time.
  • Action: Chairs to book the next interim meeting slot.