The IESG has received a request from the Constrained RESTful Environments WG (core) to consider the following document: - 'Group Communication for the Constrained Application Protocol (CoAP)' <draft-ietf-core-groupcomm-bis-14.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2025-07-29. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Constrained Application Protocol (CoAP) is a web transfer protocol for constrained devices and constrained networks. In a number of use cases, constrained devices 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 document specifies the use of CoAP for group communication, including the use of UDP/IP multicast as the default underlying data transport. Both unsecured and secured CoAP group communication are specified. Security is achieved by use of the Group Object Security for Constrained RESTful Environments (Group OSCORE) protocol. The target application area of this specification is any group communication use cases that involve resource-constrained devices or networks that support CoAP. This document replaces and obsoletes RFC 7390, while it updates RFC 7252 and RFC 7641. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-core-groupcomm-bis/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc7967: Constrained Application Protocol (CoAP) Option for No Server Response (Informational - Independent Submission stream) _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
