Short Paths in CoAP
draft-amsuess-core-shopinc-02
| Document | Type |
Replaced Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Amsüss , Michael Richardson | ||
| Last updated | 2025-09-24 (Latest revision 2025-09-09) | ||
| Replaced by | draft-ietf-core-uri-path-abbrev | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
Mailing list discussion |
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-core-uri-path-abbrev | |
| 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
Applications built on CoAP face a conflict between the technical need for short message sizes and the interoperability requirement of following BCP190 and thus registering (relatively verbose) well-known URI paths. This document introduces an option that allows expressing well-known paths in as little as two bytes.
Authors
Christian Amsüss
Michael Richardson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)