| Internet-Draft | SDF Protocol Mapping for CoAP | March 2026 |
| Romann, et al. | Expires 4 September 2026 | [Page] |
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].¶
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.¶
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 (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.¶
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.¶
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.¶
The security considerations of [RFC9880] as well as [RFC7252] apply to this document as well.¶
This document has no IANA actions.¶
TODO acknowledge.¶