CoAP Option Extension: Patience
draft-li-core-coap-patience-option-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-21
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                                                               K. Li
Internet-Draft                                           B. Greevenbosch
Intended status: Standards Track                     Huawei Technologies
Expires: April 25, 2013                                          E. Dijk
                                                        Philips Research
                                                               S. Loreto
                                                                Ericsson
                                                        October 22, 2012

                    CoAP Option Extension: Patience
                 draft-li-core-coap-patience-option-01

Abstract

   CoAP is a RESTful application protocol for constrained nodes and
   networks.  This specification provides a simple extension for CoAP,
   the Patience Option.  This Option informs a recipient of the
   preferred time frame for a request or response depending on usage
   context.  In a unicast request, it indicates the patience a client
   has in waiting for a response.  The CoAP server tries to return the
   response within the specified time frame.  In a multicast request, it
   indicates the patience a server should have in sending its response.
   The recipient would then try to randomly delay its response within
   the time frame that the requester indicated or computed by the
   recipient itself.  In a CoAP observe notification, it indicates the
   patience an observer should have in both waiting for a subsequent
   notification and in re-establishing an observation relation.

Note

   Discussion and suggestions for improvement are requested, and should
   be sent to core@ietf.org.

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."

Li, et al.               Expires April 25, 2013                 [Page 1]
Internet-Draft            CoAP Patience Option              October 2012

   This Internet-Draft will expire on April 25, 2013.

Copyright Notice

   Copyright (c) 2012 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
   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.

Li, et al.               Expires April 25, 2013                 [Page 2]
Internet-Draft            CoAP Patience Option              October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Justification  . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Patience Option Extension  . . . . . . . . . . . . . . . . . .  5
     2.1.  Patience Option Definition . . . . . . . . . . . . . . . .  5
     2.2.  Using the Patience Option  . . . . . . . . . . . . . . . .  6
       2.2.1.  Unicast usage  . . . . . . . . . . . . . . . . . . . .  6
       2.2.2.  Multicast usage  . . . . . . . . . . . . . . . . . . .  7
       2.2.3.  Observe usage  . . . . . . . . . . . . . . . . . . . .  7
     2.3.  Detection of IP unicast or multicast CoAP request  . . . .  8
   3.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     3.1.  Unicast Usage Example  . . . . . . . . . . . . . . . . . .  9
     3.2.  Observe Usage Example  . . . . . . . . . . . . . . . . . .  9
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Li, et al.               Expires April 25, 2013                 [Page 3]
Show full document text