Last Call: <draft-ietf-core-groupcomm-21.txt> (Group Communication for CoAP) to Informational RFC

The IESG <> Thu, 31 July 2014 20:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2B2A61A0188; Thu, 31 Jul 2014 13:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id riUWgpgbnX66; Thu, 31 Jul 2014 13:39:29 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 6222D1A0108; Thu, 31 Jul 2014 13:39:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-core-groupcomm-21.txt> (Group Communication for CoAP) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 31 Jul 2014 13:39:29 -0700
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Jul 2014 20:39:31 -0000

The IESG has received a request from the Constrained RESTful Environments
WG (core) to consider the following document:
- 'Group Communication for CoAP'
  <draft-ietf-core-groupcomm-21.txt> as Informational RFC

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 mailing lists by 2014-08-14. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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 document provides guidance for how
   the CoAP protocol should be used in a group communication context.
   An approach for using CoAP on top of IP multicast is detailed.  Also,
   various use cases and corresponding protocol flows are provided to
   illustrate important concepts.  Finally, guidance is provided for
   deployment in various network topologies.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.