RFC 7390: Group Communication for the Constrained Application Protocol (CoAP)
In plain English — editorial summary, not part of the RFC
The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for constrained devices and constrained networks. It is anticipated that constrained devices will often naturally operate in groups (e.g., in a building automation scenario, all lights in a given room may need to be switched on/off as a group). This specification defines how CoAP should be used in a group communication context. An approach for using CoAP on top of IP multicast is detailed based on existing CoAP functionality as well as new features introduced in this specification. Also, various use cases and corresponding protocol flows are provided to illustrate important concepts. Finally, guidance is provided for deployment in various network topologies.
Document record
- Document ID
- RFC7390
- Published
- October 2014
- Authors
- A. Rahman; E. Dijk
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 6284Port Mapping between Unicast and Multicast RTP SessionsCurrent
June 2011
- RFC 8798Additional Units for Sensor Measurement Lists (SenML)Current
June 2020
- RFC 9100Sensor Measurement Lists (SenML) Features and VersionsCurrent
August 2021
- RFC 9193Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-FormatCurrent
June 2022
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?