Group Communication for the Constrained Application Protocol (CoAP)
draft-ietf-core-groupcomm-bis-18

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, cabo@tzi.org, core-chairs@ietf.org, core@ietf.org, draft-ietf-core-groupcomm-bis@ietf.org, mbishop@evequefou.be, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Group Communication for the Constrained Application Protocol (CoAP)' to Proposed Standard (draft-ietf-core-groupcomm-bis-17.txt)

The IESG has approved the following document:
- 'Group Communication for the Constrained Application Protocol (CoAP)'
  (draft-ietf-core-groupcomm-bis-17.txt) as Proposed Standard

This document is the product of the Constrained RESTful Environments Working
Group.

The IESG contact persons are Gorry Fairhurst and Mike Bishop.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-groupcomm-bis/

Ballot Text

Technical Summary

   This document specifies the use of the Constrained Application
   Protocol (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.

Working Group Summary

   This is a substantial document addressing a somewhat specialized topic
(multicast), so there is no surprise that there were only about four
responses (all positive) to the second WGLC, albeit with several
detailed reviews coming in earlier. There was no controversy about particular points 
nor decisions where the consensus was particularly rough.

Document Quality

   There exist several implementations.  Multicast CoAP is sufficiently entrenched that we didn't do a
survey of existing implementations.  For these, the document provides
information that will aid in their further development; several
implementers have contributed reviews.

Personnel

   The Document Shepherd for this document is Carsten Bormann. The
   Responsible Area Director is Mike Bishop.

RFC Editor Note