Re: [core] RFC 8516 on "Too Many Requests" Response Code for the Constrained Application Protocol

Carsten Bormann <cabo@tzi.org> Wed, 23 January 2019 06:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6159130DFA for <core@ietfa.amsl.com>; Tue, 22 Jan 2019 22:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Zp1P8yKOb6e7 for <core@ietfa.amsl.com>; Tue, 22 Jan 2019 22:50:48 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB48E1294D0 for <core@ietf.org>; Tue, 22 Jan 2019 22:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x0N6odi1018317 for <core@ietf.org>; Wed, 23 Jan 2019 07:50:44 +0100 (CET)
Received: from [192.168.217.106] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43kwsW1vf4z1Br6; Wed, 23 Jan 2019 07:50:39 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20190123044801.6AB64B825D8@rfc-editor.org>
Date: Wed, 23 Jan 2019 07:50:38 +0100
X-Mao-Original-Outgoing-Id: 569919036.371222-f11f4216a8989e26fcf3bdd104dd3963
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FD84478-A969-41C6-AF49-90FF2DB92470@tzi.org>
References: <20190123044801.6AB64B825D8@rfc-editor.org>
To: "core@ietf.org WG" <core@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/2qTICzSddwVm_OkleP3MlE3zQGo>
Subject: Re: [core] RFC 8516 on "Too Many Requests" Response Code for the Constrained Application Protocol
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2019 06:50:51 -0000

Thank you, Ari, for pulling this through.

Ari submitted the first individual I-D for this on 2018-03-05:
The process up to publication went through in less than 11 months.
(The document approval was 2018-11-19, so the RFC editing was responsible for the last two of those months, which includes two heavy vacation periods in US and Europe, so was much less net time.)

Not bad, but let’s see if we can get better yet.

Grüße, Carsten



> On Jan 23, 2019, at 05:48, rfc-editor@rfc-editor.org wrote:
> 
> 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
> 
> 
>