A Semantic Definition Format for Data and Interactions of ThingsJ. Romann Internet-Draft Universität Bremen Intended status: Standards Track R. Mohan Expires: 4 September 2026 Cisco Systems L. Corneo Ericsson 3 March 2026 Semantic Definition Format (SDF): Protocol Mapping for the Constrained Application Protocol (CoAP) draft-romann-asdf-coap-protocol-map-latest Abstract This memo defines vocabulary to integrate the Constrained Application Protocol (CoAP) into Protocol Mappings [I-D.ietf-asdf-sdf-protocol-mapping] for the Semantic Definition Format (SDF) for Data and Interactions of Things [RFC9880]. About This Document This note is to be removed before publishing as an RFC. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-romann-asdf-coap-protocol- map/. Discussion of this document takes place on the A Semantic Definition Format for Data and Interactions of Things Working Group mailing list (mailto:asdf@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/asdf/. Subscribe at https://www.ietf.org/mailman/listinfo/asdf/. Source for this draft and an issue tracker can be found at https://github.com/JKRhb/sdf-coap-protocol-map. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 4 September 2026. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction 2. Conventions and Definitions 3. Security Considerations 4. IANA Considerations 5. References 5.1. Normative References 5.2. Informative References Acknowledgments Authors' Addresses 1. Introduction This memo defines vocabulary to integrate the Constrained Application Protocol (CoAP) [RFC7252] into Protocol Mappings [I-D.ietf-asdf-sdf-protocol-mapping] for the Semantic Definition Format (SDF) for Data and Interactions of Things [RFC9880]. The vocabulary and "feature-based" approach taken within this document is heavily inspired by the CoAP Protocol Binding [WoT-CoAP-Binding] for the W3C Web of Things (WoT), which is to be used with WoT Thing Descriptions (TDs). Considering SDF's role as a "hub format", we aspire to be able to also take into account CoAP vocabulary when converting from and to TDs. An important additional aspect to the base protocol-mapping specification [I-D.ietf-asdf-sdf-protocol-mapping] is the fact that we rely on instance-related messages [I-D.ietf-asdf-instance-information] to complement protocol information present in SDF models. Compared to the WoT approach, we achieve a stricter separation of model and instance information this way, reducing the amount of information that needs to be supplied by a Thing itself to a minimum to enable interactions. 2. Conventions and Definitions The definitions of [RFC9880], [I-D.ietf-asdf-sdf-protocol-mapping], and [I-D.ietf-asdf-instance-information] apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. Security Considerations The security considerations of [RFC9880] as well as [RFC7252] apply to this document as well. 4. IANA Considerations This document has no IANA actions. 5. References 5.1. Normative References [I-D.ietf-asdf-instance-information] Romann, J. and C. Bormann, "Instance Information for SDF", Work in Progress, Internet-Draft, draft-ietf-asdf- instance-information-02, 18 February 2026, . [I-D.ietf-asdf-sdf-protocol-mapping] Mohan, R., Brinckman, B., and L. Corneo, "SDF Protocol Mapping", Work in Progress, Internet-Draft, draft-ietf- asdf-sdf-protocol-mapping-06, 2 March 2026, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained Application Protocol (CoAP)", RFC 7252, DOI 10.17487/RFC7252, June 2014, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC9880] Koster, M., Ed., Bormann, C., Ed., and A. Keränen, "Semantic Definition Format (SDF) for Data and Interactions of Things", RFC 9880, DOI 10.17487/RFC9880, January 2026, . 5.2. Informative References [WoT-CoAP-Binding] Hartke, K. and J. Romann, "Web of Things (WoT) CoAP Binding", . Acknowledgments TODO acknowledge. Authors' Addresses Jan Romann Universität Bremen Email: jan.romann@uni-bremen.de Rohit Mohan Cisco Systems 170 West Tasman Drive San Jose, 95134 United States of America Email: rohitmo@cisco.com Lorenzo Corneo Ericsson Hirsalantie 11 FI-1296 Jorvas Finland Email: lorenzo.corneo@ericsson.com