RFC 8974

Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP), January 2021

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Updates:
RFC 7252, RFC 8323
Authors:
K. Hartke
M. Richardson
Stream:
IETF
Source:
core (wit)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8974

Discuss this RFC: Send questions or comments to the mailing list core@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8974


Abstract

This document provides considerations for alleviating Constrained Application Protocol (CoAP) clients and intermediaries of keeping per-request state. To facilitate this, this document additionally introduces a new, optional CoAP protocol extension for extended token lengths.

This document updates RFCs 7252 and 8323 with an extended definition of the "TKL" field in the CoAP message header.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search