RFC 8974: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8974
- Published
- January 2021
- Authors
- K. Hartke; M. Richardson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7554Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet of Things (IoT): Problem StatementCurrent
May 2015
- RFC 8985The RACK-TLP Loss Detection Algorithm for TCPCurrent
February 2021
- RFC 8961Requirements for Time-Based Loss DetectionCurrent
November 2020
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 9001Using TLS to Secure QUICCurrent
May 2021
- RFC 9002QUIC Loss Detection and Congestion ControlCurrent
May 2021
- RFC 8942HTTP Client HintsCurrent
February 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?