CoAP Protocol Indication
draft-amsuess-core-transport-indication-03
| Document | Type |
Replaced Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Amsüss | ||
| Last updated | 2022-04-14 (Latest revision 2022-03-03) | ||
| Replaced by | draft-ietf-core-transport-indication | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-core-transport-indication | |
| 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] to express alternative transports available to a device, and to optimize exchanges using these.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)