Browse Prior Art Database

Constrained Application Protocol (CoAP) Option for No Server Response (RFC7967)

IP.com Disclosure Number: IPCOM000247375D
Original Publication Date: 2016-Aug-01
Included in the Prior Art Database: 2016-Aug-30
Document File: 36 page(s) / 40K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Bhattacharyya: AUTHOR [+4]

Abstract

This specification defines a new option for the Constrained Application Protocol (CoAP) [RFC7252] called 'No-Response'. This option enables clients to explicitly express their disinterest in receiving responses back from the server. The disinterest can be expressed at the granularity of response classes (e.g., 2.xx) or a combination of classes (e.g., 2.xx and 5.xx). By default, this option indicates interest in all response classes. The server MAY decide to suppress the response by not transmitting it back to the client according to the value of the No-Response option in the request.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Independent Submission                                  A. Bhattacharyya Request for Comments: 7967                              S. Bandyopadhyay Category: Informational                                           A. Pal ISSN: 2070-1721                                                  T. Bose                                           Tata Consultancy Services Ltd.                                                              August 2016

  Constrained Application Protocol (CoAP) Option for No Server Response

Abstract

   There can be machine-to-machine (M2M) scenarios where server    responses to client requests are redundant.  This kind of open-loop    exchange (with no response path from the server to the client) may be    desired to minimize resource consumption in constrained systems while    updating many resources simultaneously or performing high-frequency    updates.  CoAP already provides Non-confirmable (NON) messages that    are not acknowledged by the recipient.  However, the request/response    semantics still require the server to respond with a status code    indicating "the result of the attempt to understand and satisfy the    request", per RFC 7252.

   This specification introduces a CoAP option called 'No-Response'.    Using this option, the client can explicitly express to the server    its disinterest in all responses against the particular request.    This option also provides granular control to enable expression of    disinterest to a particular response class or a combination of    response classes.  The server MAY decide to suppress the response by    not transmitting it back to the client according to the value of the    No-Response option in the request.  This option may be effective for    both unicast and multicast requests.  This document also discusses a    few examples of applications that benefit from this option.

 Bhattacharyya, et al.         Informational                     [Page 1]
 RFC 7967                 CoAP No-Response Option             August 2016

 Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this docum...