CoAP option for no server-response
draft-tcs-coap-no-response-option-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-09-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-tcs-coap-no-response-option
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                                                   A. Bhattacharyya
Internet Draft                                         S. Bandyopadhyay
Intended status: Standards track                                 A. Pal
Expires: March 2014                      Tata Consultancy Services Ltd.
                                                      September 6, 2013

                    CoAP option for no server-response
                   draft-tcs-coap-no-response-option-01

   Abstract

   The server end-point does not respond with acknowledgment (ACK) in
   non-confirmable (NON) mode of CoAP. However, the server responds the
   client with a status code indicating "the result of the attempt to
   understand and satisfy the request". But there may be typical
   scenarios, while updating resources in NON mode, where any kind of
   response from the server may be considered redundant. Thus, in this
   case, the transaction becomes completely open-loop with no reverse
   path from the server to the client. This kind of exchange may be
   useful in constrained systems looking for maximized throughput with
   minimized resource consumption. This draft introduces a header
   option: 'No-Resp' to suppress responses from the server and
   discusses an exemplary but practical use case which actually
   motivated this proposition based on real experience. This option not
   only allows suppressing any kind of responses but allows suppressing
   a typical class or a combination of classes of responses. This
   option is applicable for both request/ response as well as resource-
   observe mode and may be effective for both unicast and multicast
   scenarios.

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

Bhattacharyya, et al.   Expires March 6, 2014                 [Page 1]
 Internet-Draft  draft-tcs-coap-no-response-option-01    September 2013

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on March 6, 2009.

Copyright Notice

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

Table of Contents

   1. Introduction ................................................ 3
      1.1. Motivation ............................................. 3
         1.1.1. The use case ...................................... 3
         1.1.2. Problem description ............................... 3
         1.1.3. Solution approach and proposed modification ....... 4
      1.2. Terminology ............................................ 4
   2. Achieving Granular Response-Suppression ..................... 4
   3. Option Definition ........................................... 5
   4. Example ..................................................... 6
      4.1. Request/response Scenario .............................. 6
      4.2. Resource-observe Scenario .............................. 7

Bhattacharyya, et al.   Expires March 6, 2014                 [Page 2]
 Internet-Draft  draft-tcs-coap-no-response-option-01    September 2013

   5. IANA Considerations ......................................... 8
   6. Security Considerations ..................................... 9
   7. Acknowledgments ............................................. 9
Show full document text