metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8516: "Too Many Requests" Response Code for the Constrained Application Protocol

In plain English — editorial summary, not part of the RFC

A Constrained Application Protocol (CoAP) server can experience temporary overload because one or more clients are sending requests to the server at a higher rate than the server is capable or willing to handle. This document defines a new CoAP response code for a server to indicate that a client should reduce the rate of requests.

Document record

Document ID
RFC8516
Published
January 2019
Authors
A. Keranen
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
6
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8516-too-many-requests-response-code-for-the-constrained-application-protocol