RFC 8516 on "Too Many Requests" Response Code for the Constrained Application Protocol
rfc-editor@rfc-editor.org Wed, 23 January 2019 04:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6CA1130E16; Tue, 22 Jan 2019 20:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TjQScPQkYGW; Tue, 22 Jan 2019 20:48:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34BA130DFA; Tue, 22 Jan 2019 20:48:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6AB64B825D8; Tue, 22 Jan 2019 20:48:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8516 on "Too Many Requests" Response Code for the Constrained Application Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190123044801.6AB64B825D8@rfc-editor.org>
Date: Tue, 22 Jan 2019 20:48:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/eft6G0rqnoft4A7LO7Vps9Hos9M>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2019 04:48:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8516
Title: "Too Many Requests" Response Code
for the Constrained Application Protocol
Author: A. Keränen
Status: Standards Track
Stream: IETF
Date: January 2019
Mailbox: ari.keranen@ericsson.com
Pages: 6
Characters: 11786
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-core-too-many-reqs-06.txt
URL: https://www.rfc-editor.org/info/rfc8516
DOI: 10.17487/RFC8516
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.
This document is a product of the Constrained RESTful Environments Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC