The 'Pending' Response Code for the Constrained Application Protocol (CoAP)
draft-hartke-core-pending-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                       P. van der Stok
Internet-Draft                                                consultant
Intended status: Informational                                 K. Hartke
Expires: August 31, 2017                         Universitaet Bremen TZI
                                                       February 27, 2017

  The 'Pending' Response Code for the Constrained Application Protocol
                                 (CoAP)
                      draft-hartke-core-pending-00

Abstract

   This document proposes a new CoAP response code, 2.06 Pending.  A
   CoAP server can use this response code to signal that it has accepted
   the request but has not yet started processing it or that processing
   the request will take longer than a client is typically willing to
   wait for a response.  A 2.06 response can include status information
   and indicate a location where the result will become available.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 31, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

van der Stok & Hartke    Expires August 31, 2017                [Page 1]
Internet-Draft    The 'Pending' Response Code for CoAP     February 2017

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  2.06 Pending  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Observing Resources . . . . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Constrained Application Protocol (CoAP) [RFC7252] is a request/
   response protocol not unlike HTTP.  CoAP defines no upper bound for
   the time between a request and the resulting response.  E.g., in CoAP
   over UDP, a server is expected to return an empty Acknowledgement to
   the client if it cannot provide a response right away, but there is
   no limit on when the server should return the Separate Response.

   In particular in the case of requests with long processing times, a
   CoAP client faces the problem that it cannot easily determine how
   long it should wait for the response and whether the CoAP server is
   even still processing the request.  Long processing times occur, for
   example, when requests need manual intervention to authorize their
   processing, or when they perform a long sequence of remote actions.
   An example is provided by the "possibly long" authorization request
   specified in EST-coaps [I-D.vanderstok-ace-coap-est].

   This document proposes a new CoAP response code, 2.06 Pending.  The
   semantics of this response code are modelled after the HTTP [RFC7231]
   202 (Accepted) status code:

      The 202 (Accepted) status code indicates that the request has been
      accepted for processing, but the processing has not been
      completed.  The request might or might not eventually be acted
      upon, as it might be disallowed when processing actually takes
      place. [...] The representation sent with this response ought to
Show full document text