[core] "Too Many Requests Response Code for CoAP" draft (draft-keranen-core-too-many-reqs-00)

Ari Keränen <ari.keranen@ericsson.com> Mon, 05 March 2018 14:52 UTC

Return-Path: <ari.keranen@ericsson.com>
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 56C7412711E for <core@ietfa.amsl.com>; Mon, 5 Mar 2018 06:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 2WWHc4fmBk6q for <core@ietfa.amsl.com>; Mon, 5 Mar 2018 06:52:18 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 6654712711D for <core@ietf.org>; Mon, 5 Mar 2018 06:52:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1520261536; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KbCAwbEgh+G11Hj47xVqzwHHCbbIR11Luf75JFqAbSI=; b=Ur5acNdixiHG0m8mKVMR13cDGqoVsME3L9CJXR7J3neAL0vscI7PW64WH+ke20Fe 6w5FR+eg4eO+ggYF2PwmX3X1w+5sRdanQoMF2BpLa7rS7AxyinJjdQvjtBI/DMgX lJXrxBdfcQHmyuCPHqTa5gw42T4qVHOeUG+y+P9n7vQ=;
X-AuditID: c1b4fb25-44ba69c000002d5f-62-5a9d59a0cff8
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 00.C5.11615.0A95D9A5; Mon, 5 Mar 2018 15:52:16 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.82]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0352.000; Mon, 5 Mar 2018 15:52:03 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: core <core@ietf.org>
Thread-Topic: "Too Many Requests Response Code for CoAP" draft (draft-keranen-core-too-many-reqs-00)
Thread-Index: AQHTtJGF3s1hygoqikCLwnlBtqOdjw==
Date: Mon, 5 Mar 2018 14:52:03 +0000
Message-ID: <225023B8-B663-482A-93E6-8DD054606A79@ericsson.com>
References: <152025806136.14652.11784946748337213501.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [193.234.218.122]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <67AC64D6E56ED146922D7CFA59DD33A5@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyM2K7iu6CyLlRBleu6Vrse7ue2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGTcWdbEUfOOv2LdpFVsD4yOeLkZODgkBE4lTm+awdDFycQgJ HGaUaNhylRXCWcQo8XDDVhaQKjYBe4nJaz4ygtgiAhISnV/3s4PYwgKJEhc2H2GFiKdJrLm7 AMrWkzjd/RSonoODRUBF4uC0XJAwL9CYmV8/sIHYQgJ+Etdm3mYGsRkFxCS+n1rDBGIzC4hL 3HoynwniOAGJJXvOM0PYohIvH/9jhbCVJdY9eMIIUa8ncWPqFDYI21qiaedHFghbW2LZwtfM EHsFJU7OfMIygVFkFpIVs5C0z0LSPgtJ+ywk7QsYWVcxihanFiflphsZ66UWZSYXF+fn6eWl lmxiBMbEwS2/VXcwXn7jeIhRgINRiYfX0ntulBBrYllxZe4hRgkOZiURXilJoBBvSmJlVWpR fnxRaU5q8SFGaQ4WJXHeOcLtUUIC6YklqdmpqQWpRTBZJg5OqQbGmNkBL02nzbTfOon3420x ph9bJojVZX+10c76uXJ7aDh3SdqmEu4I8UwZ5ile5/euEm+b2VQvfUMsYqpqR7pAYcIdiy9Z rcwLHlgYx0gx/l8U95phw8ubARbO67j+Kf1W/5cofF5QT2dKT9zzCtMvy5J+Poj8nmkWuV6D 7dadhHoFReUTB/mUWIozEg21mIuKEwEDlkqyhQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/j17VgQGjwjqm1x_jSU5Q77CwhPM>
Subject: [core] "Too Many Requests Response Code for CoAP" draft (draft-keranen-core-too-many-reqs-00)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 05 Mar 2018 14:52:20 -0000

Hi all,

I submitted a new draft about the "Too Many Requests" CoAP Response Code (see details below). This was part of the CoAP pub/sub draft before, but as discussed in the previous meeting, there's also more wider use for this response code so it makes sense to have a separate draft about it.

While thinking about the details, I did realize that we may want to also define ways for the server to indicate what kind of requests are OK, or not OK. However, that topic may also be applicable beyond this Response Code so I didn't yet put any details here, just TBD markers. Perhaps that's also something to discuss at the London meeting.


Cheers,
Ari

> A new version of I-D, draft-keranen-core-too-many-reqs-00.txt
> has been successfully submitted by Ari Keranen and posted to the
> IETF repository.
> 
> Name:		draft-keranen-core-too-many-reqs
> Revision:	00
> Title:		Too Many Requests Response Code for the Constrained Application Protocol
> Document date:	2018-03-05
> Group:		Individual Submission
> Pages:		4
> URL:            https://www.ietf.org/internet-drafts/draft-keranen-core-too-many-reqs-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-keranen-core-too-many-reqs/
> Htmlized:       https://tools.ietf.org/html/draft-keranen-core-too-many-reqs-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-keranen-core-too-many-reqs-00
> 
> 
> Abstract:
>   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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>