CoAP Transport Indication
draft-ietf-core-transport-indication-09
| Document | Type |
Expired Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Amsüss , Martine Sophie Lenders | ||
| Last updated | 2026-01-08 (Latest revision 2025-07-07) | ||
| Replaces | draft-amsuess-core-transport-indication | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
Working Group Repo
Mailing list discussion |
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Constrained Application Protocol (CoAP, [RFC7252]) is available over different transports (UDP, DTLS, TCP, TLS, WebSockets), but lacks a way to unify these addresses. This document provides terminology and provisions based on Web Linking [RFC8288] and Service Bindings (SVCB, [RFC9460]) to express alternative transports available to a device, and to optimize exchanges using these.
Authors
Christian Amsüss
Martine Sophie Lenders
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)