Re: [core] I-D Action: draft-ietf-core-too-many-reqs-01.txt

This version adds simply a hint that a server can use action payload with error response to give client guidance how to act (as discussed at the CoRE meeting in IETF 101). Based on all feedback so far the draft seems to be ready to move forward.

Cheers,
Ari

> On 29 Jun 2018, at 20.35, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Constrained RESTful Environments WG of the IETF.
> 
>        Title           : Too Many Requests Response Code for the Constrained Application Protocol
>        Author          : Ari Keranen
> 	Filename        : draft-ietf-core-too-many-reqs-01.txt
> 	Pages           : 4
> 	Date            : 2018-06-29
> 
> 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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-core-too-many-reqs/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-core-too-many-reqs-01
> https://datatracker.ietf.org/doc/html/draft-ietf-core-too-many-reqs-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-core-too-many-reqs-01
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core