API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 7967
[ACTIVE]

Constrained Application Protocol (CoAP) Option for No Server Response

Metadata

Publisher
IETF
Doc Type
Informational
Pages
18
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.
Publication Date
2016-08-01
Status Note
Informational
DOI
10.17487/RFC7967
Link
https://doi.org/10.17487/RFC7967
Author(s)
Abhijan Bhattacharyya
Soma Bandyopadhyay
Arpan Pal
Tulika Bose
Keyword(s)
No-Response
Latest version of IETF RFC 7967

Document Versions — IETF RFC 7967

  • ▶ IETF RFC 7967 (2016-08-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • 10.1007-978-3-319-11569-6_58 — ITS-LIGHT EXTERNAL
  • 10.1145-2517351.2517422 — CoAP-ADAPT EXTERNAL
  • IETF.draft-ietf-core-coap-tcp-tls-04 — CoAP-TCP-TLS EXTERNAL
  • IETF.draft-ietf-core-http-mapping-13 — HTTP-to-CoAP EXTERNAL
  • IETF.draft-koster-core-coap-pubsub-05 — CoAP-PUBSUB EXTERNAL
  • IETF RFC 5405 [Superseded*]
  • IETF RFC 7390 [Active*]
  • IETF RFC 7641 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC7967.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 7967, Constrained Application Protocol (CoAP) Option for No Server Response. Available at https://doi.org/10.17487/RFC7967
Snippet:
IETF RFC 7967, Constrained Application Protocol (CoAP) Option for No Server Response. Available at https://doi.org/10.17487/RFC7967

HTML (ISO 690 compliant)

Preview:
IETF RFC 7967, Constrained Application Protocol (CoAP) Option for No Server Response. Available at https://doi.org/10.17487/RFC7967
Snippet:
<span class="citation"><cite>IETF RFC 7967</cite>, Constrained Application Protocol (CoAP) Option for No Server Response. Available at <a href="https://doi.org/10.17487/RFC7967" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7967</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 7967, Constrained Application Protocol (CoAP) Option for No Server Response
doi: 10.17487/RFC7967
url: https://doi.org/10.17487/RFC7967
Snippet:
<li>
<cite id="bib-rfc7967">IETF RFC 7967</cite>, Constrained Application Protocol (CoAP) Option for No Server Response
<span class="doi">10.17487/RFC7967</span>
</li>

Referenced By