Group Communication for CoAP
draft-ietf-core-groupcomm-06

The information below is for an old version of the document
Document Type Active Internet-Draft (core WG)
Last updated 2013-04-12
Replaces draft-rahman-core-groupcomm
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document Oct 2013
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                        A. Rahman, Ed.
Internet-Draft                          InterDigital Communications, LLC
Intended status: Informational                            E.O. Dijk, Ed.
Expires: October 14, 2013                               Philips Research
                                                          April 12, 2013

                      Group Communication for CoAP
                      draft-ietf-core-groupcomm-06

Abstract

   CoAP is a RESTful transfer protocol for constrained devices and
   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 for both constrained
   and un-constrained networks.  Also, various use cases and
   corresponding protocol flows are provided to illustrate important
   concepts.  Finally, guidance is provided for deployment in various
   network topologies.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 14, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Rahman & Dijk           Expires October 14, 2013                [Page 1]
Internet-Draft        Group Communication for CoAP            April 2013

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Protocol Considerations . . . . . . . . . . . . . . . . . . .   4
     3.1.  IP Multicast Routing Background . . . . . . . . . . . . .   4
     3.2.  Group Definition and Naming . . . . . . . . . . . . . . .   5
     3.3.  Port and URI Configuration  . . . . . . . . . . . . . . .   6
     3.4.  Group Methods . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Group Member Discovery  . . . . . . . . . . . . . . . . .   7
     3.6.  Configuring Group Membership In Endpoints . . . . . . . .   7
     3.7.  Multicast Request Acceptance and Response Suppression . .   9
     3.8.  Congestion Control  . . . . . . . . . . . . . . . . . . .  11
     3.9.  Proxy Operation . . . . . . . . . . . . . . . . . . . . .  12
     3.10. Exceptions  . . . . . . . . . . . . . . . . . . . . . . .  13
   4.  Use Cases and Corresponding Protocol Flows  . . . . . . . . .  13
     4.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .  13
     4.2.  Network Configuration . . . . . . . . . . . . . . . . . .  14
     4.3.  Discovery of Resource Directory . . . . . . . . . . . . .  16
     4.4.  Lighting Control  . . . . . . . . . . . . . . . . . . . .  17
     4.5.  Lighting Control in MLD Enabled Network . . . . . . . . .  20
     4.6.  Commissioning the Network Based On Resource Directory . .  21
   5.  Deployment Guidelines . . . . . . . . . . . . . . . . . . . .  22
     5.1.  Target Network Topologies . . . . . . . . . . . . . . . .  22
     5.2.  Advertising Membership of Multicast Groups  . . . . . . .  22
       5.2.1.  Using the Multicast Listener Discovery (MLD) Protocol  23
       5.2.2.  Using the RPL Routing Protocol  . . . . . . . . . . .  23
       5.2.3.  Using the MPL Forwarding Protocol . . . . . . . . . .  23
     5.3.  6LoWPAN-Specific Guidelines . . . . . . . . . . . . . . .  24
Show full document text