Debian Codegraph @

rfc7390.html

raw
1 <pre>Internet Engineering Task Force (IETF) A. Rahman, Ed.
2 Request for Comments: 7390 InterDigital Communications, LLC
3 Category: Experimental E. Dijk, Ed.
4 ISSN: 2070-1721 Philips Research
5 October 2014
6
7
8 <span class="h1">Group Communication for the Constrained Application Protocol (CoAP)</span>
9
10 Abstract
11
12 The Constrained Application Protocol (CoAP) is a specialized web
13 transfer protocol for constrained devices and constrained networks.
14 It is anticipated that constrained devices will often naturally
15 operate in groups (e.g., in a building automation scenario, all
16 lights in a given room may need to be switched on/off as a group).
17 This specification defines how CoAP should be used in a group
18 communication context. An approach for using CoAP on top of IP
19 multicast is detailed based on existing CoAP functionality as well as
20 new features introduced in this specification. Also, various use
21 cases and corresponding protocol flows are provided to illustrate
22 important concepts. Finally, guidance is provided for deployment in
23 various network topologies.
24
25 Status of This Memo
26
27 This document is not an Internet Standards Track specification; it is
28 published for examination, experimental implementation, and
29 evaluation.
30
31 This document defines an Experimental Protocol for the Internet
32 community. This document is a product of the Internet Engineering
33 Task Force (IETF). It represents the consensus of the IETF
34 community. It has received public review and has been approved for
35 publication by the Internet Engineering Steering Group (IESG). Not
36 all documents approved by the IESG are a candidate for any level of
37 Internet Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
38
39 Information about the current status of this document, any errata,
40 and how to provide feedback on it may be obtained at
41 <a href="http://www.rfc-editor.org/info/rfc7390">http://www.rfc-editor.org/info/rfc7390</a>.
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Rahman &amp; Dijk Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2014 IETF Trust and the persons identified as the
60 document authors. All rights reserved. This document is subject to
61 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal Provisions Relating to IETF
62 Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the
63 date of publication of this document. Please review these documents
64 carefully, as they describe your rights and restrictions with respect
65 to this document. Code Components extracted from this document must
66 include Simplified BSD License text as described in Section 4.e of
67 the Trust Legal Provisions and are provided without warranty as
68 described in the Simplified BSD License.
69
70 Table of Contents
71
72 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
73 <a href="#section-1.1">1.1</a>. Background . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
74 <a href="#section-1.2">1.2</a>. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-1.3">1.3</a>. Conventions and Terminology . . . . . . . . . . . . . . . <a href="#page-4">4</a>
76 <a href="#section-2">2</a>. Protocol Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
77 <a href="#section-2.1">2.1</a>. IP Multicast Background . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
78 <a href="#section-2.2">2.2</a>. Group Definition and Naming . . . . . . . . . . . . . . . <a href="#page-6">6</a>
79 <a href="#section-2.3">2.3</a>. Port and URI Configuration . . . . . . . . . . . . . . . <a href="#page-7">7</a>
80 <a href="#section-2.4">2.4</a>. RESTful Methods . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
81 <a href="#section-2.5">2.5</a>. Request and Response Model . . . . . . . . . . . . . . . <a href="#page-9">9</a>
82 <a href="#section-2.6">2.6</a>. Membership Configuration . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
83 <a href="#section-2.6.1">2.6.1</a>. Background . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
84 <a href="#section-2.6.2">2.6.2</a>. Membership Configuration RESTful Interface . . . . . <a href="#page-11">11</a>
85 <a href="#section-2.7">2.7</a>. Request Acceptance and Response Suppression Rules . . . . <a href="#page-17">17</a>
86 <a href="#section-2.8">2.8</a>. Congestion Control . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
87 <a href="#section-2.9">2.9</a>. Proxy Operation . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
88 <a href="#section-2.10">2.10</a>. Exceptions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
89 <a href="#section-3">3</a>. Use Cases and Corresponding Protocol Flows . . . . . . . . . <a href="#page-22">22</a>
90 <a href="#section-3.1">3.1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
91 <a href="#section-3.2">3.2</a>. Network Configuration . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a>
92 <a href="#section-3.3">3.3</a>. Discovery of Resource Directory . . . . . . . . . . . . . <a href="#page-25">25</a>
93 <a href="#section-3.4">3.4</a>. Lighting Control . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
94 <a href="#section-3.5">3.5</a>. Lighting Control in MLD-Enabled Network . . . . . . . . . <a href="#page-30">30</a>
95 <a href="#section-3.6">3.6</a>. Commissioning the Network Based on Resource Directory . . <a href="#page-31">31</a>
96 <a href="#section-4">4</a>. Deployment Guidelines . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
97 <a href="#section-4.1">4.1</a>. Target Network Topologies . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
98 <a href="#section-4.2">4.2</a>. Networks Using the MLD Protocol . . . . . . . . . . . . . <a href="#page-33">33</a>
99 <a href="#section-4.3">4.3</a>. Networks Using RPL Multicast without MLD . . . . . . . . <a href="#page-33">33</a>
100 <a href="#section-4.4">4.4</a>. Networks Using MPL Forwarding without MLD . . . . . . . . <a href="#page-34">34</a>
101 <a href="#section-4.5">4.5</a>. 6LoWPAN Specific Guidelines for the 6LBR . . . . . . . . <a href="#page-35">35</a>
102 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
103 <a href="#section-5.1">5.1</a>. Security Configuration . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
104 <a href="#section-5.2">5.2</a>. Threats . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
105
106
107
108 <span class="grey">Rahman &amp; Dijk Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
111
112
113 <a href="#section-5.3">5.3</a>. Threat Mitigation . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
114 <a href="#section-5.3.1">5.3.1</a>. WiFi Scenario . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
115 <a href="#section-5.3.2">5.3.2</a>. 6LoWPAN Scenario . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
116 <a href="#section-5.3.3">5.3.3</a>. Future Evolution . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
117 <a href="#section-5.4">5.4</a>. Monitoring Considerations . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
118 <a href="#section-5.4.1">5.4.1</a>. General Monitoring . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
119 <a href="#section-5.4.2">5.4.2</a>. Pervasive Monitoring . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
120 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
121 <a href="#section-6.1">6.1</a>. New 'core.gp' Resource Type . . . . . . . . . . . . . . . <a href="#page-39">39</a>
122 <a href="#section-6.2">6.2</a>. New 'coap-group+json' Internet Media Type . . . . . . . . <a href="#page-39">39</a>
123 <a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
124 <a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
125 <a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
126 <a href="#appendix-A">Appendix A</a>. Multicast Listener Discovery (MLD) . . . . . . . . . <a href="#page-45">45</a>
127 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-45">45</a>
128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-46">46</a>
129
130 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
131
132 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Background</span>
133
134 CoAP is a web transfer protocol based on Representational State
135 Transfer (REST) for resource constrained devices operating in an IP
136 network [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>]. CoAP has many similarities to HTTP [<a href="./rfc7230" title="&quot;Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing&quot;">RFC7230</a>] but
137 also some key differences. Constrained devices can be large in
138 numbers but are often related to each other in function or by
139 location. For example, all the light switches in a building may
140 belong to one group, and all the thermostats may belong to another
141 group. Groups may be preconfigured before deployment or dynamically
142 formed during operation. If information needs to be sent to or
143 received from a group of devices, group communication mechanisms can
144 improve efficiency and latency of communication and reduce bandwidth
145 requirements for a given application. HTTP does not support any
146 equivalent functionality to CoAP group communication.
147
148 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Scope</span>
149
150 Group communication involves a one-to-many relationship between CoAP
151 endpoints. Specifically, a single CoAP client can simultaneously get
152 (or set) resources from multiple CoAP servers using CoAP over IP
153 multicast. An example would be a CoAP light switch turning on/off
154 multiple lights in a room with a single CoAP group communication PUT
155 request and handling the potential multitude of (unicast) responses.
156
157 The base protocol aspects of sending CoAP requests on top of IP
158 multicast and processing the (unicast IP) responses are given in
159 <a href="./rfc7252#section-8">Section&nbsp;8 of [RFC7252]</a>. To provide a more complete CoAP group
160 communication functionality, this specification introduces new CoAP
161
162
163
164 <span class="grey">Rahman &amp; Dijk Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
167
168
169 processing functionality (e.g., new rules for reuse of Token values,
170 request suppression, and proxy operation) and a new management
171 interface for RESTful group membership configuration.
172
173 CoAP group communication will run in the Any Source Multicast (ASM)
174 mode [<a href="./rfc5110" title="&quot;Overview of the Internet Multicast Routing Architecture&quot;">RFC5110</a>] of IP multicast operation. This means that there is
175 no restriction on the source node that sends (originates) the CoAP
176 messages to the IP multicast group. For example, the source node may
177 or may not be part of the IP multicast group. Also, there is no
178 restriction on the number of source nodes.
179
180 While <a href="./rfc7252#section-9.1">Section&nbsp;9.1 of [RFC7252]</a> supports various modes of security
181 based on Datagram Transport Layer Security (DTLS) for CoAP over
182 unicast IP, it does not specify any security modes for CoAP over IP
183 multicast. That is, it is assumed per [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>] that CoAP over IP
184 multicast is not encrypted, nor authenticated, nor access controlled.
185 This document assumes the same security model (see <a href="#section-5.1">Section 5.1</a>).
186 However, there are several promising security approaches being
187 developed that should be considered in the future for protecting CoAP
188 group communications (see <a href="#section-5.3.3">Section 5.3.3</a>).
189
190 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Conventions and Terminology</span>
191
192 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
193 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
194 "OPTIONAL" in this document are to be interpreted as described in
195 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] when they appear in ALL CAPS. When these words are not in
196 ALL CAPS (such as "should" or "Should"), they have their usual
197 English meanings and are not to be interpreted as [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] key
198 words.
199
200 Note that this document refers back to other RFCs, and especially
201 [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>], to help explain overall CoAP group communication features.
202 However, use of [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] key words is reserved for new CoAP
203 functionality introduced by this specification.
204
205 This document assumes readers are familiar with the terms and
206 concepts that are used in [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>]. In addition, this document
207 defines the following terminology:
208
209 Group Communication:
210 A source node sends a single application-layer (e.g., CoAP)
211 message that is delivered to multiple destination nodes, where all
212 destinations are identified to belong to a specific group. The
213 source node itself may be part of the group. The underlying
214 mechanisms for CoAP group communication are UDP/IP multicast for
215
216
217
218
219
220 <span class="grey">Rahman &amp; Dijk Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
223
224
225 the requests and unicast UDP/IP for the responses. The network
226 involved may be a constrained network such as a low-power, lossy
227 network.
228
229 Reliable Group Communication:
230 A special case of group communication where for each destination
231 node, it is guaranteed that the node either 1) eventually receives
232 the message sent by the source node or 2) does not receive the
233 message and the source node is notified of the non-reception
234 event. An example of a reliable group communication protocol is
235 [<a href="./rfc5740" title="&quot;NACK-Oriented Reliable Multicast (NORM) Transport Protocol&quot;">RFC5740</a>].
236
237 Multicast:
238 Sending a message to multiple destination nodes with one network
239 invocation. There are various options to implement multicast,
240 including layer 2 (Media Access Control) and layer 3 (IP)
241 mechanisms.
242
243 IP Multicast:
244 A specific multicast approach based on the use of IP multicast
245 addresses as defined in "IANA Guidelines for IPv4 Multicast
246 Address Assignments" [<a href="./rfc5771" title="&quot;IANA Guidelines for IPv4 Multicast Address Assignments&quot;">RFC5771</a>] and "IP Version 6 Addressing
247 Architecture" [<a href="./rfc4291" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC4291</a>]. A complete IP multicast solution may
248 include support for managing group memberships and IP multicast
249 routing/forwarding (see <a href="#section-2.1">Section 2.1</a>).
250
251 Low-Power and Lossy Network (LLN):
252 A type of constrained IP network where devices are interconnected
253 by low-power and lossy links. The links may be composed of one or
254 more technologies such as IEEE 802.15.4, Bluetooth Low Energy
255 (BLE), Digital Enhanced Cordless Telecommunication (DECT), and
256 IEEE P1901.2 power-line communication.
257
258 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Protocol Considerations</span>
259
260 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. IP Multicast Background</span>
261
262 IP multicast protocols have been evolving for decades, resulting in
263 standards such as Protocol Independent Multicast - Sparse Mode (PIM-
264 SM) [<a href="./rfc4601" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC4601</a>]. IP multicast is very popular in specific deployments
265 such as in enterprise networks (e.g., for video conferencing), smart
266 home networks (e.g., Universal Plug and Play (UPnP)), and carrier
267 IPTV deployments. The packet economy and minimal host complexity of
268 IP multicast make it attractive for group communication in
269 constrained environments.
270
271
272
273
274
275
276 <span class="grey">Rahman &amp; Dijk Experimental [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
279
280
281 To achieve IP multicast beyond link-local (LL) scope, an IP multicast
282 routing or forwarding protocol needs to be active on IP routers. An
283 example of a routing protocol specifically for LLNs is the IPv6
284 Routing Protocol for Low-Power and Lossy Networks (RPL) (<a href="./rfc6550#section-12">Section&nbsp;12
285 of [RFC6550]</a>), and an example of a forwarding protocol for LLNs is
286 the Multicast Protocol for Low-Power and Lossy Networks (MPL)
287 [<a href="#ref-MCAST-MPL">MCAST-MPL</a>]. RPL and MPL do not depend on each other; each can be
288 used in isolation, and both can be used in combination in a network.
289 Finally, PIM-SM [<a href="./rfc4601" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC4601</a>] is often used for multicast routing in
290 traditional IP networks (i.e., networks that are not constrained).
291
292 IP multicast can also be run in an LL scope. This means that there
293 is no routing involved, and an IP multicast message is only received
294 over the link on which it was sent.
295
296 For a complete IP multicast solution, in addition to a routing/
297 forwarding protocol, a "listener" protocol may be needed for the
298 devices to subscribe to groups (see <a href="#section-4.2">Section 4.2</a>). Also, a multicast
299 forwarding proxy node [<a href="./rfc4605" title="&quot;Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding (&quot;">RFC4605</a>] may be required.
300
301 IP multicast is generally classified as an unreliable service in that
302 packets are not guaranteed to be delivered to each and every member
303 of the group. In other words, it cannot be directly used as a basis
304 for "reliable group communication" as defined in <a href="#section-1.3">Section 1.3</a>.
305 However, the level of reliability can be increased by employing a
306 multicast protocol that performs periodic retransmissions as is done,
307 for example, in MPL.
308
309 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Group Definition and Naming</span>
310
311 A CoAP group is defined as a set of CoAP endpoints, where each
312 endpoint is configured to receive CoAP group communication requests
313 that are sent to the group's associated IP multicast address. The
314 individual response by each endpoint receiver to a CoAP group
315 communication request is always sent back as unicast. An endpoint
316 may be a member of multiple groups. Group membership of an endpoint
317 may dynamically change over time.
318
319 All CoAP server nodes SHOULD join the "All CoAP Nodes" multicast
320 group (<a href="./rfc7252#section-12.8">Section&nbsp;12.8 of [RFC7252]</a>) by default to enable CoAP
321 discovery. For IPv4, the address is 224.0.1.187, and for IPv6, a
322 server node joins at least both the link-local scoped address
323 ff02::fd and the site-local scoped address ff05::fd. IPv6 addresses
324 of other scopes MAY be enabled.
325
326 A CoAP group URI has the scheme 'coap' and includes in the authority
327 part either a group IP multicast address or a hostname (e.g., Group
328 Fully Qualified Domain Name (FQDN)) that can be resolved to the group
329
330
331
332 <span class="grey">Rahman &amp; Dijk Experimental [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
335
336
337 IP multicast address. A group URI also contains an optional CoAP
338 port number in the authority part. Group URIs follow the regular
339 CoAP URI syntax (<a href="./rfc7252#section-6">Section&nbsp;6 of [RFC7252]</a>).
340
341 Note: A group URI is needed to initiate CoAP group communications.
342 For CoAP client implementations, it is recommended to use the URI
343 decomposition method of <a href="./rfc7252#section-6.4">Section&nbsp;6.4 of [RFC7252]</a> in such a way that,
344 from a group URI, a CoAP group communication request is generated.
345
346 For sending nodes, it is recommended to use the IP multicast address
347 literal in a group URI. (This is because DNS infrastructure may not
348 be deployed in many constrained network deployments.) However, in
349 case a group hostname is used, it can be uniquely mapped to an IP
350 multicast address via DNS resolution (if supported). Some examples
351 of hierarchical group FQDN naming (and scoping) for a building
352 control application are shown below:
353
354 URI authority Targeted group of nodes
355 --------------------------------------- --------------------------
356 all.bldg6.example.com "all nodes in building 6"
357 all.west.bldg6.example.com "all nodes in west wing,
358 building 6"
359 all.floor1.west.bldg6.example.com "all nodes in floor 1,
360 west wing, building 6"
361 all.bu036.floor1.west.bldg6.example.com "all nodes in office bu036,
362 floor 1, west wing,
363 building 6"
364
365 Similarly, if supported, reverse mapping (from IP multicast address
366 to Group FQDN) is possible using the reverse DNS resolution technique
367 ([<a href="./rfc1033" title="&quot;Domain administrators operations guide&quot;">RFC1033</a>]). Reverse mapping is important, for example, in
368 troubleshooting to translate IP multicast addresses back to human-
369 readable hostnames to show in a diagnostics user interface.
370
371 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Port and URI Configuration</span>
372
373 A CoAP server that is a member of a group listens for CoAP messages
374 on the group's IP multicast address, usually on the CoAP default UDP
375 port, 5683. If the group uses a specified non-default UDP port, be
376 careful to ensure that all group members are configured to use that
377 same port.
378
379 Different ports for the same IP multicast address are preferably not
380 used to specify different CoAP groups. If disjoint groups share the
381 same IP multicast address, then all the devices interested in one
382 group will accept IP traffic also for the other disjoint groups, only
383 to ultimately discard the traffic higher in their IP stack (based on
384 UDP port discrimination).
385
386
387
388 <span class="grey">Rahman &amp; Dijk Experimental [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
391
392
393 CoAP group communication will not work if there is diversity in the
394 authority port (e.g., different dynamic port addresses across the
395 group) or if other parts of the group URI such as the path, or the
396 query, differ on different endpoints. Therefore, some measures must
397 be present to ensure uniformity in port number and resource names/
398 locations within a group. All CoAP group communication requests MUST
399 be sent using a port number according to one of the below options:
400
401 1. A preconfigured port number.
402
403 2. If the client is configured to use service discovery including
404 URI and port discovery, it uses the port number obtained via a
405 service discovery lookup operation for the targeted CoAP group.
406
407 3. Use the default CoAP UDP port (5683).
408
409 For a CoAP server node that supports resource discovery, the default
410 port 5683 must be supported (<a href="./rfc7252#section-7.1">Section&nbsp;7.1 of [RFC7252]</a>) for the "All
411 CoAP Nodes" group. Regardless of the method of selecting the port
412 number, the same port MUST be used across all CoAP servers in a group
413 and across all CoAP clients performing the group requests.
414
415 All CoAP group communication requests SHOULD operate on group URI
416 paths in one of the following ways:
417
418 1. Preconfigured group URI paths, if available. Implementers are
419 free to define the paths as they see fit. However, note that
420 [<a href="./rfc7320" title="&quot;URI Design and Ownership&quot;">RFC7320</a>] prescribes that a specification must not constrain or
421 define the structure or semantics for any path component. So for
422 this reason, a predefined URI path is not specified in this
423 document and also must not be provided in other specifications.
424
425 2. If the client is configured to use default Constrained RESTful
426 Environments (CoRE) resource discovery, it uses URI paths
427 retrieved from a "/.well-known/core" lookup on a group member.
428 The URI paths the client will use MUST be known to be available
429 also in all other endpoints in the group. The URI path
430 configuration mechanism on servers MUST ensure that these URIs
431 (identified as being supported by the group) are configured on
432 all group endpoints.
433
434 3. If the client is configured to use another form of service
435 discovery, it uses group URI paths from an equivalent service
436 discovery lookup that returns the resources supported by all
437 group members.
438
439
440
441
442
443
444 <span class="grey">Rahman &amp; Dijk Experimental [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
447
448
449 4. If the client has received a group URI through a previous RESTful
450 interaction with a trusted server, it can use this URI in a CoAP
451 group communication request. For example, a commissioning tool
452 may instruct a sensor device in this way to which target group
453 (group URI) it should report sensor events.
454
455 However, when the URI path is selected, the same path MUST be used
456 across all CoAP servers in a group and all CoAP clients performing
457 the group requests.
458
459 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. RESTful Methods</span>
460
461 Group communication most often uses the idempotent CoAP methods GET
462 and PUT. The idempotent method DELETE can also be used. The non-
463 idempotent CoAP method POST may only be used for group communication
464 if the resource being POSTed to has been designed to cope with the
465 unreliable and lossy nature of IP multicast. For example, a client
466 may resend a multicast POST request for additional reliability. Some
467 servers will receive the request two times while others may receive
468 it only once. For idempotent methods, all these servers will be in
469 the same state while for POST, this is not guaranteed; so, the
470 resource POST operation must be specifically designed to take message
471 loss into account.
472
473 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Request and Response Model</span>
474
475 All CoAP requests that are sent via IP multicast must be Non-
476 confirmable (<a href="./rfc7252#section-8.1">Section&nbsp;8.1 of [RFC7252]</a>). The Message ID in an IP
477 multicast CoAP message is used for optional message deduplication as
478 detailed in <a href="./rfc7252#section-4.5">Section&nbsp;4.5 of [RFC7252]</a>.
479
480 A server optionally sends back a unicast response to the CoAP group
481 communication request (e.g., response "2.05 Content" to a group GET
482 request). The unicast responses received by the CoAP client may be a
483 mixture of success (e.g., 2.05 Content) and failure (e.g., 4.04 Not
484 Found) codes depending on the individual server processing results.
485 Detailed processing rules for IP multicast request acceptance and
486 unicast response suppression are given in <a href="#section-2.7">Section 2.7</a>.
487
488 A CoAP request sent over IP multicast and any unicast response it
489 causes must take into account the congestion control rules defined in
490 <a href="#section-2.8">Section 2.8</a>.
491
492 The CoAP client can distinguish the origin of multiple server
493 responses by the source IP address of the UDP message containing the
494 CoAP response or any other available unique identifier (e.g.,
495
496
497
498
499
500 <span class="grey">Rahman &amp; Dijk Experimental [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
503
504
505 contained in the CoAP payload). In case a CoAP client sent multiple
506 group requests, the responses are as usual matched to a request using
507 the CoAP Token.
508
509 For multicast CoAP requests, there are additional constraints on the
510 reuse of Token values, compared to the unicast case. In the unicast
511 case, receiving a response effectively frees up its Token value for
512 reuse since no more responses will follow. However, for multicast
513 CoAP, the number of responses is not bounded a priori. Therefore,
514 the reception of a response cannot be used as a trigger to "free up"
515 a Token value for reuse. Reusing a Token value too early could lead
516 to incorrect response/request matching in the client and would be a
517 protocol error. Therefore, the time between reuse of Token values
518 used in multicast requests MUST be greater than:
519
520 NON_LIFETIME + MAX_LATENCY + MAX_SERVER_RESPONSE_DELAY
521
522 where NON_LIFETIME and MAX_LATENCY are defined in <a href="./rfc7252#section-4.8">Section&nbsp;4.8 of
523 [RFC7252]</a>. MAX_SERVER_RESPONSE_DELAY is defined here as the expected
524 maximum response delay over all servers that the client can send a
525 multicast request to. This delay includes the maximum Leisure time
526 period as defined in <a href="./rfc7252#section-8.2">Section&nbsp;8.2 of [RFC7252]</a>. CoAP does not define
527 a time limit for the server response delay. Using the default CoAP
528 parameters, the Token reuse time MUST be greater than 250 seconds
529 plus MAX_SERVER_RESPONSE_DELAY. A preferred solution to meet this
530 requirement is to generate a new unique Token for every multicast
531 request, such that a Token value is never reused. If a client has to
532 reuse Token values for some reason, and also
533 MAX_SERVER_RESPONSE_DELAY is unknown, then using
534 MAX_SERVER_RESPONSE_DELAY = 250 seconds is a reasonable guideline.
535 The time between Token reuses is in that case set to a value greater
536 than 500 seconds.
537
538 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Membership Configuration</span>
539
540 <span class="h4"><a class="selflink" id="section-2.6.1" href="#section-2.6.1">2.6.1</a>. Background</span>
541
542 <span class="h5"><a class="selflink" id="section-2.6.1.1" href="#section-2.6.1.1">2.6.1.1</a>. Member Discovery</span>
543
544 CoAP groups, and the membership of these groups, can be discovered
545 via the lookup interfaces in the Resource Directory (RD) defined in
546 [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>]. This discovery interface is not required to invoke CoAP
547 group communications. However, it is a potential complementary
548 interface useful for overall management of CoAP groups. Other
549 methods to discover groups (e.g., proprietary management systems) can
550 also be used. An example of doing some of the RD-based lookups is
551 given in <a href="#section-3.6">Section 3.6</a>.
552
553
554
555
556 <span class="grey">Rahman &amp; Dijk Experimental [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
559
560
561 <span class="h5"><a class="selflink" id="section-2.6.1.2" href="#section-2.6.1.2">2.6.1.2</a>. Configuring Members</span>
562
563 The group membership of a CoAP endpoint may be configured in one of
564 the following ways. First, the group membership may be preconfigured
565 before node deployment. Second, a node may be programmed to discover
566 (query) its group membership using a specific service discovery
567 means. Third, it may be configured by another node (e.g., a
568 commissioning device).
569
570 In the first case, the preconfigured group information may be either
571 an IP multicast address or a hostname (FQDN) that is resolved later
572 (during operation) to an IP multicast address by the endpoint using
573 DNS (if supported).
574
575 For the second case, a CoAP endpoint may look up its group membership
576 using techniques such as DNS-based Service Discovery (DNS-SD) and RD
577 [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>].
578
579 In the third case, typical in scenarios such as building control, a
580 dynamic commissioning tool determines to which group(s) a sensor or
581 actuator node belongs, and writes this information to the node, which
582 can subsequently join the correct IP multicast group(s) on its
583 network interface. The information written per group may again be an
584 IP multicast address or a hostname.
585
586 <span class="h4"><a class="selflink" id="section-2.6.2" href="#section-2.6.2">2.6.2</a>. Membership Configuration RESTful Interface</span>
587
588 To achieve better interoperability between endpoints from different
589 manufacturers, an OPTIONAL CoAP membership configuration RESTful
590 interface for configuring endpoints with relevant group information
591 is described here. This interface provides a solution for the third
592 case mentioned above. To access this interface, a client will use
593 unicast CoAP methods (GET/PUT/POST/DELETE). This interface is a
594 method of configuring group information in individual endpoints.
595
596 Also, a form of authorization (preferably making use of unicast DTLS-
597 secured CoAP per <a href="./rfc7252#section-9.1">Section&nbsp;9.1 of [RFC7252]</a>) should be used such that
598 only authorized controllers are allowed by an endpoint to configure
599 its group membership.
600
601 It is important to note that other approaches may be used to
602 configure CoAP endpoints with relevant group information. These
603 alternative approaches may support a subset or superset of the
604 membership configuration RESTful interface described in this
605 document. For example, a simple interface to just read the endpoint
606 group information may be implemented via a classical Management
607 Information Base (MIB) approach (e.g., following the approach of
608 [<a href="./rfc3433" title="&quot;Entity Sensor Management Information Base&quot;">RFC3433</a>]).
609
610
611
612 <span class="grey">Rahman &amp; Dijk Experimental [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
615
616
617 <span class="h5"><a class="selflink" id="section-2.6.2.1" href="#section-2.6.2.1">2.6.2.1</a>. CoAP-Group Resource Type and Media Type</span>
618
619 CoAP endpoints implementing the membership configuration RESTful
620 interface MUST support the CoAP group configuration Internet Media
621 Type "application/coap-group+json" (<a href="#section-6.2">Section 6.2</a>).
622
623 A resource offering this representation can be annotated for direct
624 discovery [<a href="./rfc6690" title="&quot;Constrained RESTful Environments (CoRE) Link Format&quot;">RFC6690</a>] using the Resource Type (rt=) Link Target
625 Attribute "core.gp", where "gp" is shorthand for "group"
626 (<a href="#section-6.1">Section 6.1</a>). An authorized client uses this media type to query/
627 manage group membership of a CoAP endpoint as defined in the
628 following subsections.
629
630 The Group Configuration resource and its sub-resources have a content
631 format based on JavaScript Object Notation (JSON) (as indicated by
632 the "application/coap-group+json" media type). The resource includes
633 zero or more group membership JSON objects [<a href="./rfc7159" title="&quot;The JavaScript Object Notation (JSON) Data Interchange Format&quot;">RFC7159</a>] in a format as
634 defined in <a href="#section-2.6.2.4">Section 2.6.2.4</a>. A group membership JSON object contains
635 one or more key/value pairs as defined below, and represents a single
636 IP multicast group membership for the CoAP endpoint. Each key/value
637 pair is encoded as a member of the JSON object, where the key is the
638 member name and the value is the member's value.
639
640 Examples of four different group membership objects are as follows:
641
642 { "n": "All-Devices.floor1.west.bldg6.example.com",
643 "a": "[ff15::4200:f7fe:ed37:abcd]:4567" }
644
645 { "n": "sensors.floor2.east.bldg6.example.com" }
646
647 { "n": "coap-test",
648 "a": "224.0.1.187:56789" }
649
650 { "a": "[ff15::c0a7:15:c001]" }
651
652 The OPTIONAL "n" key/value pair stands for "name" and identifies the
653 group with a hostname (and optionally the port number), for example,
654 an FQDN. The OPTIONAL "a" key/value pair specifies the IP multicast
655 address (and optionally the port number) of the group. It contains
656 an IPv4 address (in dotted-decimal notation) or an IPv6 address. The
657 following ABNF rule can be used for parsing the address, referring to
658 the definitions in <a href="./rfc3986#section-3.2.2">Section&nbsp;3.2.2 of [RFC3986]</a> that are also used in
659 the base CoAP (<a href="./rfc7252#section-6">Section&nbsp;6 of [RFC7252]</a>.
660
661 group-address = IPv4address [ ":" port ]
662 / "[" IPv6address "]" [":" port ]
663
664
665
666
667
668 <span class="grey">Rahman &amp; Dijk Experimental [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
671
672
673 In any group membership object, if the IP address is known when the
674 object is created, it is included in the "a" key/value pair. If the
675 "a" value cannot be provided, the "n" value MUST be included,
676 containing a valid hostname with an optional port number that can be
677 translated to an IP multicast address via DNS.
678
679 group-name = host [ ":" port ]
680
681 If the port number is not provided, then the endpoint will attempt to
682 look up the port number from DNS if it supports a method to do this.
683 The possible DNS methods include DNS SRV [<a href="./rfc2782" title="&quot;A DNS RR for specifying the location of services (DNS SRV)&quot;">RFC2782</a>] or DNS-SD
684 [<a href="./rfc6763" title="&quot;DNS-Based Service Discovery&quot;">RFC6763</a>]. If port lookup is not supported or not provided by DNS,
685 the default CoAP port (5683) is assumed.
686
687 After any change on a Group Configuration resource, the endpoint MUST
688 effect registration/deregistration from the corresponding IP
689 multicast group(s) by making use of APIs such as IPV6_RECVPKTINFO
690 [<a href="./rfc3542" title="&quot;Advanced Sockets Application Program Interface (API) for IPv6&quot;">RFC3542</a>].
691
692 <span class="h5"><a class="selflink" id="section-2.6.2.2" href="#section-2.6.2.2">2.6.2.2</a>. Creating a New Multicast Group Membership (POST)</span>
693
694 Method: POST
695 URI Template: /{+gp}
696 Location-URI Template: /{+gp}/{index}
697 URI Template Variables:
698 gp - Group Configuration Function Set path (mandatory).
699 index - Group index. Index MUST be a string of maximum two (2)
700 alphanumeric ASCII characters (case insensitive). It MUST be
701 locally unique to the endpoint server. It indexes the particular
702 endpoint's list of group memberships.
703
704 Example:
705 Req: POST /coap-group
706 Content-Format: application/coap-group+json
707 { "n": "All-Devices.floor1.west.bldg6.example.com",
708 "a": "[ff15::4200:f7fe:ed37:abcd]:4567" }
709 Res: 2.01 Created
710 Location-Path: /coap-group/12
711
712 For the 'gp' variable, it is recommended to use the path "coap-group"
713 by default. The "a" key/value pair is always used if it is given.
714 The "n" pair is only used when there is no "a" pair. If only the "n"
715 pair is given, the CoAP endpoint performs DNS resolution to obtain
716 the IP multicast address from the hostname in the "n" pair. If DNS
717 resolution is not successful, then the endpoint does not attempt
718 joining or listening to any multicast group for this case since the
719 IP multicast address is unknown.
720
721
722
723
724 <span class="grey">Rahman &amp; Dijk Experimental [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
727
728
729 After any change on a Group Configuration resource, the endpoint MUST
730 effect registration/deregistration from the corresponding IP
731 multicast group(s) by making use of APIs such as IPV6_RECVPKTINFO
732 [<a href="./rfc3542" title="&quot;Advanced Sockets Application Program Interface (API) for IPv6&quot;">RFC3542</a>]. When a POST payload contains an "a", an IP multicast
733 address to which the endpoint is already subscribed, no change to
734 that subscription is needed.
735
736 <span class="h5"><a class="selflink" id="section-2.6.2.3" href="#section-2.6.2.3">2.6.2.3</a>. Deleting a Single Group Membership (DELETE)</span>
737
738 Method: DELETE
739 URI Template: {+location}
740 URI Template Variables:
741 location - The Location-Path returned by the CoAP server
742 as a result of a successful group creation.
743
744 Example:
745 Req: DELETE /coap-group/12
746 Res: 2.02 Deleted
747
748 <span class="h5"><a class="selflink" id="section-2.6.2.4" href="#section-2.6.2.4">2.6.2.4</a>. Reading All Group Memberships at Once (GET)</span>
749
750 A (unicast) GET on the CoAP-group resource returns a JSON object
751 containing multiple keys and values. The keys (member names) are
752 group indices, and the values (member values) are the corresponding
753 group membership objects. Each group membership object describes one
754 IP multicast group membership. If no group memberships are
755 configured, then an empty JSON object is returned.
756
757 Method: GET
758
759 URI Template: /{+gp}
760
761 URI Template Variables:
762
763 gp - see <a href="#section-2.6.2.2">Section 2.6.2.2</a>
764
765 Example:
766 Req: GET /coap-group
767 Res: 2.05 Content
768 Content-Format: application/coap-group+json
769 { "8" :{ "a": "[ff15::4200:f7fe:ed37:14ca]" },
770 "11":{ "n": "sensors.floor1.west.bldg6.example.com",
771 "a": "[ff15::4200:f7fe:ed37:25cb]" },
772 "12":{ "n": "All-Devices.floor1.west.bldg6.example.com",
773 "a": "[ff15::4200:f7fe:ed37:abcd]:4567" }
774 }
775
776
777
778
779
780 <span class="grey">Rahman &amp; Dijk Experimental [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
783
784
785 Note: the returned IPv6 address string will represent the same IPv6
786 address that was originally submitted in group membership creation,
787 though it might be a different string because of different choices in
788 IPv6 string representation formatting that may be allowed for the
789 same address (see [<a href="./rfc5952" title="&quot;A Recommendation for IPv6 Address Text Representation&quot;">RFC5952</a>]).
790
791 <span class="h5"><a class="selflink" id="section-2.6.2.5" href="#section-2.6.2.5">2.6.2.5</a>. Reading a Single Group Membership (GET)</span>
792
793 Similar to <a href="#section-2.6.2.4">Section 2.6.2.4</a>, but only a single group membership is
794 read. If the requested group index does not exist, then a 4.04 Not
795 Found response is returned.
796
797 Method: GET
798
799 URI Template 1: {+location}
800
801 URI Template 2: /{+gp}/{index}
802
803 URI Template Variables:
804
805 location - see <a href="#section-2.6.2.3">Section 2.6.2.3</a>
806
807 gp, index - see <a href="#section-2.6.2.2">Section 2.6.2.2</a>
808
809 Example:
810 Req: GET /coap-group/12
811 Res: 2.05 Content
812 Content-Format: application/coap-group+json
813 {"n": "All-Devices.floor1.west.bldg6.example.com",
814 "a": "[ff15::4200:f7fe:ed37:abcd]:4567"}
815
816 <span class="h5"><a class="selflink" id="section-2.6.2.6" href="#section-2.6.2.6">2.6.2.6</a>. Creating/Updating All Group Memberships at Once (PUT)</span>
817
818 A (unicast) PUT with a group configuration media type as payload will
819 replace all current group memberships in the endpoint with the new
820 ones defined in the PUT request. This operation MUST only be used to
821 delete or update group membership objects for which the CoAP client,
822 invoking this operation, is responsible. The responsibility is based
823 on application-level knowledge. For example, a commissioning tool
824 will be responsible for any group membership objects that it created.
825
826 Method: PUT
827
828 URI Template: /{+gp}
829
830 URI Template Variables:
831
832 gp - see <a href="#section-2.6.2.2">Section 2.6.2.2</a>
833
834
835
836 <span class="grey">Rahman &amp; Dijk Experimental [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
839
840
841 Example: (replacing all existing group memberships with two new
842 group memberships)
843 Req: PUT /coap-group
844 Content-Format: application/coap-group+json
845 { "1":{ "a": "[ff15::4200:f7fe:ed37:1234]" },
846 "2":{ "a": "[ff15::4200:f7fe:ed37:5678]" }
847 }
848 Res: 2.04 Changed
849
850 Example: (clearing all group memberships at once)
851 Req: PUT /coap-group
852 Content-Format: application/coap-group+json
853 {}
854 Res: 2.04 Changed
855
856 After a successful PUT on the Group Configuration resource, the
857 endpoint MUST effect registration to any new IP multicast group(s)
858 and deregistration from any previous IP multicast group(s), i.e., not
859 any more present in the new memberships. An API such as
860 IPV6_RECVPKTINFO [<a href="./rfc3542" title="&quot;Advanced Sockets Application Program Interface (API) for IPv6&quot;">RFC3542</a>] should be used for this purpose. Also, it
861 MUST take into account the group indices present in the new resource
862 during the generation of any new unique group indices in the future.
863
864 <span class="h5"><a class="selflink" id="section-2.6.2.7" href="#section-2.6.2.7">2.6.2.7</a>. Updating a Single Group Membership (PUT)</span>
865
866 A (unicast) PUT with a group membership JSON object will replace an
867 existing group membership in the endpoint with the new one defined in
868 the PUT request. This can be used to update the group membership.
869
870 Method: PUT
871
872 URI Template 1: {+location}
873
874 URI Template 2: /{+gp}/{index}
875
876 URI Template Variables:
877
878 location - see <a href="#section-2.6.2.3">Section 2.6.2.3</a>
879
880 gp, index - see <a href="#section-2.6.2.2">Section 2.6.2.2</a>
881
882 Example: (group name and IP multicast port change)
883 Req: PUT /coap-group/12
884 Content-Format: application/coap-group+json
885 {"n": "All-My-Devices.floor1.west.bldg6.example.com",
886 "a": "[ff15::4200:f7fe:ed37:abcd]"}
887 Res: 2.04 Changed
888
889
890
891
892 <span class="grey">Rahman &amp; Dijk Experimental [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
895
896
897 After a successful PUT on the Group Configuration resource, the
898 endpoint MUST effect registration to any new IP multicast group(s)
899 and deregistration from any previous IP multicast group(s), i.e., not
900 any more present in the new membership. An API such as
901 IPV6_RECVPKTINFO [<a href="./rfc3542" title="&quot;Advanced Sockets Application Program Interface (API) for IPv6&quot;">RFC3542</a>] should be used for this purpose.
902
903 <span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Request Acceptance and Response Suppression Rules</span>
904
905 CoRE Link Format [<a href="./rfc6690" title="&quot;Constrained RESTful Environments (CoRE) Link Format&quot;">RFC6690</a>] and <a href="#section-8">Section 8</a> of CoAP [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>] define
906 behaviors for the following:
907
908 1. IP multicast request acceptance -- in which cases a CoAP request
909 is accepted and executed, and when it is not.
910
911 2. IP multicast response suppression -- in which cases the CoAP
912 response to an already executed request is returned to the
913 requesting endpoint, and when it is not.
914
915 A CoAP response differs from a CoAP ACK; ACKs are never sent by
916 servers in response to an IP multicast CoAP request. This section
917 first summarizes these behaviors and then presents additional
918 guidelines for response suppression. Also, a number of IP multicast
919 example applications are given to illustrate the overall approach.
920
921 To apply any rules for request and/or response suppression, a CoAP
922 server must be aware that an incoming request arrived via IP
923 multicast by making use of APIs such as IPV6_RECVPKTINFO [<a href="./rfc3542" title="&quot;Advanced Sockets Application Program Interface (API) for IPv6&quot;">RFC3542</a>].
924
925 For IP multicast request acceptance, the behaviors are as follows:
926
927 o A server should not accept an IP multicast request that cannot be
928 "authenticated" in some way (i.e, cryptographically or by some
929 multicast boundary limiting the potential sources); see
930 <a href="./rfc7252#section-11.3">Section&nbsp;11.3 of [RFC7252]</a>. See <a href="#section-5.3">Section 5.3</a> for examples of
931 multicast boundary limiting methods.
932
933 o A server should not accept an IP multicast discovery request with
934 a query string (as defined in CoRE Link Format [<a href="./rfc6690" title="&quot;Constrained RESTful Environments (CoRE) Link Format&quot;">RFC6690</a>]) if
935 filtering [<a href="./rfc6690" title="&quot;Constrained RESTful Environments (CoRE) Link Format&quot;">RFC6690</a>] is not supported by the server.
936
937 o A server should not accept an IP multicast request that acts on a
938 specific resource for which IP multicast support is not required.
939 (Note that for the resource "/.well-known/core", IP multicast
940 support is required if "multicast resource discovery" is supported
941 as specified in <a href="./rfc6690#section-1.2.1">Section&nbsp;1.2.1 of [RFC6690]</a>.) Implementers are
942 advised to disable IP multicast support by default on any other
943 resource, until explicitly enabled by an application or by
944 configuration.
945
946
947
948 <span class="grey">Rahman &amp; Dijk Experimental [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
951
952
953 o Otherwise, accept the IP multicast request.
954
955 For IP multicast response suppression, the behaviors are as follows:
956
957 o A server should not respond to an IP multicast discovery request
958 if the filter specified by the request's query string does not
959 match.
960
961 o A server may choose not to respond to an IP multicast request if
962 there's nothing useful to respond back (e.g., error or empty
963 response).
964
965 The above response suppression behaviors are complemented by the
966 following guidelines. CoAP servers should implement configurable
967 response suppression, enabling at least the following options per
968 resource that supports IP multicast requests:
969
970 o Suppression of all 2.xx success responses;
971
972 o Suppression of all 4.xx client errors;
973
974 o Suppression of all 5.xx server errors; and
975
976 o Suppression of all 2.05 responses with empty payload.
977
978 A number of CoAP group communication example applications are given
979 below to illustrate how to make use of response suppression:
980
981 o CoAP resource discovery: Suppress 2.05 responses with empty
982 payload and all 4.xx and 5.xx errors.
983
984 o Lighting control: Suppress all 2.xx responses after a lighting
985 change command.
986
987 o Update configuration data in a group of devices using group
988 communication PUT: No suppression at all. The client uses
989 collected responses to identify which group members did not
990 receive the new configuration and then attempts using CoAP CON
991 unicast to update those specific group members. Note that in this
992 case, the client implements a "reliable group communication" (as
993 defined in <a href="#section-1.3">Section 1.3</a>) function using additional, non-
994 standardized functions above the CoAP layer.
995
996 o IP multicast firmware update by sending blocks of data: Suppress
997 all 2.xx and 5.xx responses. After having sent all IP multicast
998 blocks, the client checks each endpoint by unicast to identify
999 which data blocks are still missing in each endpoint.
1000
1001
1002
1003
1004 <span class="grey">Rahman &amp; Dijk Experimental [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1007
1008
1009 o Conditional reporting for a group (e.g., sensors) based on a group
1010 URI query: Suppress all 2.05 responses with empty payload (i.e.,
1011 if a query produces no matching results).
1012
1013 <span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Congestion Control</span>
1014
1015 CoAP group communication requests may result in a multitude of
1016 responses from different nodes, potentially causing congestion.
1017 Therefore, both the sending of IP multicast requests and the sending
1018 of the unicast CoAP responses to these multicast requests should be
1019 conservatively controlled.
1020
1021 CoAP [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>] reduces IP multicast-specific congestion risks through
1022 the following measures:
1023
1024 o A server may choose not to respond to an IP multicast request if
1025 there's nothing useful to respond to (e.g., error or empty
1026 response); see <a href="./rfc7252#section-8.2">Section&nbsp;8.2 of [RFC7252]</a>. See <a href="#section-2.7">Section 2.7</a> for more
1027 detailed guidelines on response suppression.
1028
1029 o A server should limit the support for IP multicast requests to
1030 specific resources where multicast operation is required
1031 (<a href="./rfc7252#section-11.3">Section&nbsp;11.3 of [RFC7252]</a>).
1032
1033 o An IP multicast request must be Non-confirmable (<a href="./rfc7252#section-8.1">Section&nbsp;8.1 of
1034 [RFC7252]</a>).
1035
1036 o A response to an IP multicast request should be Non-confirmable
1037 (<a href="./rfc7252#section-5.2.3">Section&nbsp;5.2.3 of [RFC7252]</a>).
1038
1039 o A server does not respond immediately to an IP multicast request
1040 and should first wait for a time that is randomly picked within a
1041 predetermined time interval called the Leisure (<a href="./rfc7252#section-8.2">Section&nbsp;8.2 of
1042 [RFC7252]</a>).
1043
1044 Additional guidelines to reduce congestion risks defined in this
1045 document are as follows:
1046
1047 o A server in an LLN should only support group communication GET for
1048 resources that are small. For example, the payload of the
1049 response is limited to approximately 5% of the IP Maximum Transmit
1050 Unit (MTU) size, so it fits into a single link-layer frame in case
1051 IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN) (see
1052 <a href="./rfc4944#section-4">Section&nbsp;4 of [RFC4944]</a>) is used.
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Rahman &amp; Dijk Experimental [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1063
1064
1065 o A server can minimize the payload length in response to a group
1066 communication GET on "/.well-known/core" by using hierarchy in
1067 arranging link descriptions for the response. An example of this
1068 is given in <a href="./rfc6690#section-5">Section&nbsp;5 of [RFC6690]</a>.
1069
1070 o A server can also minimize the payload length of a response to a
1071 group communication GET (e.g., on "/.well-known/core") using CoAP
1072 blockwise transfers [<a href="#ref-BLOCKWISE-CoAP">BLOCKWISE-CoAP</a>], returning only a first block
1073 of the CoRE Link Format description. For this reason, a CoAP
1074 client sending an IP multicast CoAP request to "/.well-known/core"
1075 should support core-block.
1076
1077 o A client should use CoAP group communication with the smallest
1078 possible IP multicast scope that fulfills the application needs.
1079 As an example, site-local scope is always preferred over global
1080 scope IP multicast if this fulfills the application needs.
1081 Similarly, realm-local scope is always preferred over site-local
1082 scope if this fulfills the application needs.
1083
1084 More guidelines specific to the use of CoAP in 6LoWPAN networks
1085 [<a href="./rfc4919" title="&quot;IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals&quot;">RFC4919</a>] are given in <a href="#section-4.5">Section 4.5</a> of this document.
1086
1087 <span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Proxy Operation</span>
1088
1089 CoAP (<a href="./rfc7252#section-5.7.2">Section&nbsp;5.7.2 of [RFC7252]</a>) allows a client to request a
1090 forward-proxy to process its CoAP request. For this purpose, the
1091 client specifies either the request group URI as a string in the
1092 Proxy-URI option or the Proxy-Scheme option with the group URI
1093 constructed from the usual Uri-* options. This approach works well
1094 for unicast requests. However, there are certain issues and
1095 limitations of processing the (unicast) responses to a CoAP group
1096 communication request made in this manner through a proxy.
1097
1098 A proxy may buffer all the individual (unicast) responses to a CoAP
1099 group communication request and then send back only a single
1100 (aggregated) response to the client. However, there are some issues
1101 with this aggregation approach:
1102
1103 o Aggregation of (unicast) responses to a CoAP group communication
1104 request in a proxy is difficult. This is because the proxy does
1105 not know how many members there are in the group or how many group
1106 members will actually respond. Also, the proxy does not know how
1107 long to wait before deciding to send back the aggregated response
1108 to the client.
1109
1110 o There is no default format defined in CoAP for aggregation of
1111 multiple responses into a single response.
1112
1113
1114
1115
1116 <span class="grey">Rahman &amp; Dijk Experimental [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1119
1120
1121 Alternatively, if a proxy follows directly the specification for a
1122 CoAP Proxy (<a href="./rfc7252#section-5.7.2">Section&nbsp;5.7.2 of [RFC7252]</a>), the proxy would simply
1123 forward all the individual (unicast) responses to a CoAP group
1124 communication request to the client (i.e., no aggregation). There
1125 are also issues with this approach:
1126
1127 o The client may be confused as it may not have known that the
1128 Proxy-URI contained a group URI target. That is, the client may
1129 be expecting only one (unicast) response but instead receives
1130 multiple (unicast) responses, potentially leading to fault
1131 conditions in the application.
1132
1133 o Each individual CoAP response will appear to originate (IP source
1134 address) from the CoAP Proxy, and not from the server that
1135 produced the response. This makes it impossible for the client to
1136 identify the server that produced each response.
1137
1138 Due to the above issues, a CoAP Proxy SHOULD NOT support processing
1139 an IP multicast CoAP request but rather return a 501 (Not
1140 Implemented) response in such case. The exception case here (i.e.,
1141 to process it) is allowed if all the following conditions are met:
1142
1143 o The CoAP Proxy MUST be explicitly configured (whitelist) to allow
1144 proxied IP multicast requests by a specific client(s).
1145
1146 o The proxy SHOULD return individual (unicast) CoAP responses to the
1147 client (i.e., not aggregated). The exception case here occurs
1148 when a (future) standardized aggregation format is being used.
1149
1150 o It MUST be known to the person/entity doing the configuration of
1151 the proxy, or otherwise verified in some way, that the client
1152 configured in the whitelist supports receiving multiple responses
1153 to a proxied unicast CoAP request.
1154
1155 <span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Exceptions</span>
1156
1157 CoAP group communication using IP multicast offers improved network
1158 efficiency and latency among other benefits. However, group
1159 communication may not always be implementable in a given network.
1160 The primary reason for this will be that IP multicast is not (fully)
1161 supported in the network.
1162
1163 For example, if only RPL [<a href="./rfc6550" title="&quot;RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks&quot;">RFC6550</a>] is used in a network with its
1164 optional multicast support disabled, there will be no IP multicast
1165 routing at all. The only multicast that works in this case is link-
1166 local IPv6 multicast. This implies that any CoAP group communication
1167 request will be delivered to nodes on the local link only, regardless
1168 of the scope value used in the IPv6 destination address.
1169
1170
1171
1172 <span class="grey">Rahman &amp; Dijk Experimental [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1175
1176
1177 CoAP Observe [<a href="#ref-OBSERVE-CoAP">OBSERVE-CoAP</a>] is a feature for a client to "observe"
1178 resources (i.e., to retrieve a representation of a resource and keep
1179 this representation updated by the server over a period of time).
1180 CoAP Observe does not support a group communication mode. CoAP
1181 Observe only supports a unicast mode of operation.
1182
1183 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Use Cases and Corresponding Protocol Flows</span>
1184
1185 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Introduction</span>
1186
1187 The use of CoAP group communication is shown in the context of the
1188 following two use cases and corresponding protocol flows:
1189
1190 o Discovery of RD [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>]: discovering the local CoAP RD, which
1191 contains links to resources stored on other CoAP servers
1192 [<a href="./rfc6690" title="&quot;Constrained RESTful Environments (CoRE) Link Format&quot;">RFC6690</a>].
1193
1194 o Lighting Control: synchronous operation of a group of
1195 IPv6-connected lights (e.g., 6LoWPAN [<a href="./rfc4944" title="&quot;Transmission of IPv6 Packets over IEEE 802.15.4 Networks&quot;">RFC4944</a>] lights).
1196
1197 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Network Configuration</span>
1198
1199 To illustrate the use cases, we define two IPv6 network
1200 configurations. Both are based on the topology as shown in Figure 1.
1201 The two configurations using this topology are as follows:
1202
1203 1. Subnets are 6LoWPAN networks; the routers Rtr-1 and Rtr-2 are
1204 6LoWPAN Border Routers (6LBRs) [<a href="./rfc6775" title="&quot;Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)&quot;">RFC6775</a>].
1205
1206 2. Subnets are Ethernet links; the routers Rtr-1 and Rtr-2 are
1207 multicast-capable Ethernet routers.
1208
1209 Both configurations are further specified by the following:
1210
1211 o A large room (Room-A) with three lights (Light-1, Light-2, Light-
1212 3) controlled by a light switch (Light Switch). The devices are
1213 organized into two subnets. In reality, there could be more
1214 lights (up to several hundreds) but, for clarity, only three are
1215 shown.
1216
1217 o Light-1 and the light switch are connected to a router (Rtr-1).
1218
1219 o Light-2 and Light-3 are connected to another router (Rtr-2).
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Rahman &amp; Dijk Experimental [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1231
1232
1233 o The routers are connected to an IPv6 network backbone (Network
1234 Backbone) that is also multicast enabled. In the general case,
1235 this means the network backbone and Rtr-1/Rtr-2 support a PIM-
1236 based multicast routing protocol and Multicast Listener Discovery
1237 (MLD) for forming groups.
1238
1239 o A CoAP RD is connected to the network backbone.
1240
1241 o The DNS server (DNS Server) is optional. If the server is there
1242 (connected to the network backbone), then certain DNS-based
1243 features are available (e.g., DNS resolution of the hostname to
1244 the IP multicast address). If the DNS server is not there, then
1245 different provisioning of the network is required (e.g., IP
1246 multicast addresses are hard-coded into devices, or manually
1247 configured, or obtained via a service discovery method).
1248
1249 o A controller (CoAP client) is connected to the backbone, which is
1250 able to control various building functions including lighting.
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Rahman &amp; Dijk Experimental [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1287
1288
1289 ################################################
1290 # ********************** Room-A #
1291 # ** Subnet-1 ** # Network
1292 # * ** # Backbone
1293 # * +----------+ * # |
1294 # * | Light |-------+ * # |
1295 # * | Switch | | * # |
1296 # * +----------+ +---------+ * # |
1297 # * | Rtr-1 |-----------------------------+
1298 # * +---------+ * # |
1299 # * +----------+ | * # |
1300 # * | Light-1 |--------+ * # |
1301 # * +----------+ * # |
1302 # ** ** # |
1303 # ************************** # |
1304 # # |
1305 # ********************** # +------------+ |
1306 # ** Subnet-2 ** # | DNS Server | |
1307 # * ** # | (Optional) |--+
1308 # * +----------+ * # +------------+ |
1309 # * | Light-2 |-------+ * # |
1310 # * | | | * # |
1311 # * +----------+ +---------+ * # |
1312 # * | Rtr-2 |-----------------------------+
1313 # * +---------+ * # |
1314 # * +----------+ | * # |
1315 # * | Light-3 |--------+ * # |
1316 # * +----------+ * # +------------+ |
1317 # ** ** # | Controller |--+
1318 # ************************** # | Client | |
1319 ################################################ +------------+ |
1320 +------------+ |
1321 | CoAP | |
1322 | Resource |-----------------+
1323 | Directory |
1324 +------------+
1325
1326
1327 Figure 1: Network Topology of a Large Room (Room-A)
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Rahman &amp; Dijk Experimental [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1343
1344
1345 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Discovery of Resource Directory</span>
1346
1347 The protocol flow for discovery of the CoAP RD for the given network
1348 (of Figure 1) is shown in Figure 2:
1349
1350 o Light-2 is installed and powered on for the first time.
1351
1352 o Light-2 will then search for the local CoAP RD by sending out a
1353 group communication GET request (with the "/.well-known/
1354 core?rt=core.rd" request URI) to the site-local "All CoAP Nodes"
1355 multicast address (ff05:::fd).
1356
1357 o This multicast message will then go to each node in Subnet-2.
1358 Rtr-2 will then forward it into the network backbone where it will
1359 be received by the CoAP RD. All other nodes in Subnet-2 will
1360 ignore the group communication GET request because it is qualified
1361 by the query string "?rt=core.rd" (which indicates it should only
1362 be processed by the endpoint if it contains a resource of type
1363 "core.rd").
1364
1365 o The CoAP RD will then send back a unicast response containing the
1366 requested content, which is a CoRE Link Format representation of a
1367 resource of type "core.rd".
1368
1369 o Note that the flow is shown only for Light-2 for clarity. Similar
1370 flows will happen for Light-1, Light-3, and light switch when they
1371 are first installed.
1372
1373 The CoAP RD may also be discovered by other means such as by assuming
1374 a default location (e.g., on a 6LBR), using DHCP, anycast address,
1375 etc. However, these approaches do not invoke CoAP group
1376 communication so are not further discussed here. (See [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>] for
1377 more details.)
1378
1379 For other discovery use cases such as discovering local CoAP servers,
1380 services, or resources, CoAP group communication can be used in a
1381 similar fashion as in the above use case. For example, link-local,
1382 realm-local, admin-local, or site-local scoped discovery can be done
1383 this way.
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Rahman &amp; Dijk Experimental [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1399
1400
1401 Light CoAP
1402 Light-1 Light-2 Light-3 Switch Rtr-1 Rtr-2 RD
1403 | | | | | | |
1404 | | | | | | |
1405 ********************************** | | |
1406 * Light-2 is installed * | | |
1407 * and powers on for first time * | | |
1408 ********************************** | | |
1409 | | | | | | |
1410 | | | | | | |
1411 | | COAP NON Mcast(GET | |
1412 | | /.well-known/core?rt=core.rd) | |
1413 | |---------&gt;--------------------------------&gt;| |
1414 | | | | | |---------&gt;|
1415 | | | | | | |
1416 | | | | | | |
1417 | | COAP NON (2.05 Content | |
1418 | | &lt;/rd&gt;;rt="core.rd";ins="Primary") |&lt;---------|
1419 | |&lt;------------------------------------------| |
1420 | | | | | | |
1421
1422
1423 Figure 2: Resource Directory Discovery via Multicast Request
1424
1425 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Lighting Control</span>
1426
1427 The protocol flow for a building automation lighting control scenario
1428 for the network (Figure 1) is shown in Figure 3. The network is
1429 assumed to be in a 6LoWPAN configuration. Also, it is assumed that
1430 the CoAP servers in each light are configured to suppress CoAP
1431 responses for any IP multicast CoAP requests related to lighting
1432 control. (See <a href="#section-2.7">Section 2.7</a> for more details on response suppression
1433 by a server.)
1434
1435 In addition, Figure 4 shows a protocol flow example for the case that
1436 servers do respond to a lighting control IP multicast request with
1437 (unicast) CoAP NON responses. There are two success responses and
1438 one 5.00 error response. In this particular case, the light switch
1439 does not check that all lights in the group received the IP multicast
1440 request by examining the responses. This is because the light switch
1441 is not configured with an exhaustive list of the IP addresses of all
1442 lights belonging to the group. However, based on received error
1443 responses, it could take additional action such as logging a fault or
1444 alerting the user via its LCD display. In case a CoAP message is
1445 delivered multiple times to a light, the subsequent CoAP messages can
1446 be filtered out as duplicates, based on the CoAP Message ID.
1447
1448
1449
1450
1451
1452 <span class="grey">Rahman &amp; Dijk Experimental [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1455
1456
1457 Reliability of IP multicast is not guaranteed. Therefore, one or
1458 more lights in the group may not have received the CoAP control
1459 request due to packet loss. In this use case, there is no detection
1460 nor correction of such situations: the application layer expects that
1461 the IP multicast forwarding/routing will be of sufficient quality to
1462 provide on average a very high probability of packet delivery to all
1463 CoAP endpoints in an IP multicast group. An example protocol to
1464 accomplish this using randomized retransmission is the MPL forwarding
1465 protocol for LLNs [<a href="#ref-MCAST-MPL">MCAST-MPL</a>].
1466
1467 We assume the following steps have already occurred before the
1468 illustrated flows:
1469
1470 1) Startup phase: 6LoWPANs are formed. IPv6 addresses are assigned
1471 to all devices. The CoAP network is formed.
1472
1473 2) Network configuration (application independent): 6LBRs are
1474 configured with IP multicast addresses, or address blocks, to
1475 filter out or to pass through to/from the 6LoWPAN.
1476
1477 3a) Commissioning phase (application related): The IP multicast
1478 address of the group (Room-A-Lights) has been configured in all
1479 the lights and in the light switch.
1480
1481 3b) As an alternative to the previous step, when a DNS server is
1482 available, the light switch and/or the lights have been
1483 configured with a group hostname that each node resolves to the
1484 above IP multicast address of the group.
1485
1486 Note for the Commissioning phase: the switch's 6LoWPAN/CoAP software
1487 stack supports sending unicast, multicast, or proxied unicast CoAP
1488 requests, including processing of the multiple responses that may be
1489 generated by an IP multicast CoAP request.
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Rahman &amp; Dijk Experimental [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1511
1512
1513 Light Network
1514 Light-1 Light-2 Light-3 Switch Rtr-1 Rtr-2 Backbone
1515 | | | | | | |
1516 | | | | | | |
1517 | | *********************** | |
1518 | | * User flips on * | |
1519 | | * light switch to * | |
1520 | | * turn on all the * | |
1521 | | * lights in Room-A * | |
1522 | | *********************** | |
1523 | | | | | | |
1524 | | | | | | |
1525 | | | COAP NON Mcast(PUT, | |
1526 | | | Payload=lights ON) | |
1527 |&lt;-------------------------------+---------&gt;| | |
1528 ON | | | |--------------------&gt;|
1529 | | | | | |&lt;---------|
1530 | |&lt;---------|&lt;-------------------------------| |
1531 | ON ON | | | |
1532 ^ ^ ^ | | | |
1533 *********************** | | | |
1534 * Lights in Room-A * | | | |
1535 * turn on (nearly * | | | |
1536 * simultaneously) * | | | |
1537 *********************** | | | |
1538 | | | | | | |
1539
1540
1541 Figure 3: Light Switch Sends Multicast Control Message
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 <span class="grey">Rahman &amp; Dijk Experimental [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1567
1568
1569 Light Network
1570 Light-1 Light-2 Light-3 Switch Rtr-1 Rtr-2 Backbone
1571 | | | | | | |
1572 | COAP NON (2.04 Changed) | | | |
1573 |-------------------------------&gt;| | | |
1574 | | | | | | |
1575 | | | | | | |
1576 | COAP NON (2.04 Changed) | | |
1577 | |------------------------------------------&gt;| |
1578 | | | | | |---------&gt;|
1579 | | | | |&lt;--------------------|
1580 | | | |&lt;---------| | |
1581 | | | | | | |
1582 | | COAP NON (5.00 Internal Server Error) |
1583 | | |-------------------------------&gt;| |
1584 | | | | | |---------&gt;|
1585 | | | | |&lt;--------------------|
1586 | | | |&lt;---------| | |
1587 | | | | | | |
1588
1589
1590 Figure 4: Lights (Optionally) Respond to Multicast CoAP Request
1591
1592 Another, but similar, lighting control use case is shown in Figure 5.
1593 In this case, a controller connected to the network backbone sends a
1594 CoAP group communication request to turn on all lights in Room-A.
1595 Every light sends back a CoAP response to the controller after being
1596 turned on.
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Rahman &amp; Dijk Experimental [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1623
1624
1625 Network
1626 Light-1 Light-2 Light-3 Rtr-1 Rtr-2 Backbone Controller
1627 | | | | | | |
1628 | | | | | COAP NON Mcast(PUT,
1629 | | | | | Payload=lights ON)
1630 | | | | | |&lt;-------|
1631 | | | |&lt;----------&lt;---------| |
1632 |&lt;--------------------------------| | | |
1633 ON | | | | | |
1634 | |&lt;----------&lt;---------------------| | |
1635 | ON ON | | | |
1636 ^ ^ ^ | | | |
1637 *********************** | | | |
1638 * Lights in Room-A * | | | |
1639 * turn on (nearly * | | | |
1640 * simultaneously) * | | | |
1641 *********************** | | | |
1642 | | | | | | |
1643 | | | | | | |
1644 | COAP NON (2.04 Changed) | | | |
1645 |--------------------------------&gt;| | | |
1646 | | | |--------------------&gt;| |
1647 | | COAP NON (2.04 Changed) | |-------&gt;|
1648 | |--------------------------------&gt;| | |
1649 | | | | |---------&gt;| |
1650 | | | COAP NON (2.04 Changed) |-------&gt;|
1651 | | |---------------------&gt;| | |
1652 | | | | |---------&gt;| |
1653 | | | | | |-------&gt;|
1654 | | | | | | |
1655
1656
1657 Figure 5: Controller on Backbone Sends Multicast Control Message
1658
1659 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Lighting Control in MLD-Enabled Network</span>
1660
1661 The use case in the previous section can also apply in networks where
1662 nodes support the MLD protocol [<a href="./rfc3810" title="&quot;Multicast Listener Discovery Version 2 (MLDv2) for IPv6&quot;">RFC3810</a>]. The lights then take on
1663 the role of MLDv2 listener, and the routers (Rtr-1 and Rtr-2) are
1664 MLDv2 routers. In the Ethernet-based network configuration, MLD may
1665 be available on all involved network interfaces. Use of MLD in the
1666 6LoWPAN-based configuration is also possible but requires MLD support
1667 in all nodes in the 6LoWPAN. In current 6LoWPAN implementations, MLD
1668 is, however, not supported.
1669
1670 The resulting protocol flow is shown in Figure 6. This flow is
1671 executed after the commissioning phase, as soon as lights are
1672 configured with a group address to listen to. The (unicast) MLD
1673
1674
1675
1676 <span class="grey">Rahman &amp; Dijk Experimental [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1679
1680
1681 Reports may require periodic refresh activity as specified by the MLD
1682 protocol. In the figure, 'LL' denotes link-local communication.
1683
1684 After the shown sequence of MLD Report messages has been executed,
1685 both Rtr-1 and Rtr-2 are automatically configured to forward IP
1686 multicast traffic destined to Room-A-Lights onto their connected
1687 subnet. Hence, no manual network configuration of routers, as
1688 previously indicated in <a href="#section-3.4">Section 3.4</a>, step 2, is needed anymore.
1689
1690 Light Network
1691 Light-1 Light-2 Light-3 Switch Rtr-1 Rtr-2 Backbone
1692 | | | | | | |
1693 | | | | | | |
1694 | | | | | | |
1695 | MLD Report: Join | | | | |
1696 | Group (Room-A-Lights) | | | |
1697 |---LL-------------------------------------&gt;| | |
1698 | | | | |MLD Report: Join |
1699 | | | | |Group (Room-A-Lights)|
1700 | | | | |---LL----&gt;----LL----&gt;|
1701 | | | | | | |
1702 | | MLD Report: Join | | | |
1703 | | Group (Room-A-Lights) | | |
1704 | |---LL-------------------------------------&gt;| |
1705 | | | | | | |
1706 | | | MLD Report: Join | | |
1707 | | | Group (Room-A-Lights) | |
1708 | | |---LL--------------------------&gt;| |
1709 | | | | | | |
1710 | | | | |MLD Report: Join |
1711 | | | | |Group (Room-A-Lights)|
1712 | | | | |&lt;--LL-----+---LL----&gt;|
1713 | | | | | | |
1714 | | | | | | |
1715
1716
1717 Figure 6: Joining Lighting Groups Using MLD
1718
1719 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Commissioning the Network Based on Resource Directory</span>
1720
1721 This section outlines how devices in the lighting use case (both
1722 switches and lights) can be commissioned, making use of the RD
1723 [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>] and its group configuration feature.
1724
1725 Once the RD is discovered, the Switches and lights need to be
1726 discovered and their groups need to be defined. For the
1727 commissioning of these devices, a commissioning tool can be used that
1728
1729
1730
1731
1732 <span class="grey">Rahman &amp; Dijk Experimental [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1735
1736
1737 defines the entries in the RD. The commissioning tool has the
1738 authority to change the contents of the RD and the light/switch
1739 nodes. DTLS-based unicast security is used by the commissioning tool
1740 to modify operational data in RD, switches, and lights.
1741
1742 In our particular use case, a group of three lights is defined with
1743 one IP multicast address and hostname:
1744
1745 "Room-A-Lights.floor1.west.bldg6.example.com"
1746
1747 The commissioning tool has a list of the three lights and the
1748 associated IP multicast address. For each light in the list, the
1749 tool learns the IP address of the light and instructs the RD with
1750 three (unicast) POST commands to store the endpoints associated with
1751 the three lights as prescribed by the RD specification [<a href="#ref-CoRE-RD" title="&quot;CoRE Resource Directory&quot;">CoRE-RD</a>].
1752 Finally, the commissioning tool defines the group in the RD to
1753 contain these three endpoints. Also the commissioning tool writes
1754 the IP multicast address in the light endpoints with, for example,
1755 the (unicast) POST command discussed in <a href="#section-2.6.2.2">Section 2.6.2.2</a>.
1756
1757 The light switch can discover the group in RD and thus learn the IP
1758 multicast address of the group. The light switch will use this
1759 address to send CoAP group communication requests to the members of
1760 the group. When the message arrives, the lights should recognize the
1761 IP multicast address and accept the message.
1762
1763 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Deployment Guidelines</span>
1764
1765 This section provides guidelines on how IP multicast-based CoAP group
1766 communication can be deployed in various network configurations.
1767
1768 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Target Network Topologies</span>
1769
1770 CoAP group communication can be deployed in various network
1771 topologies. First, the target network may be a traditional IP
1772 network, or an LLN such as a 6LoWPAN network, or consist of mixed
1773 traditional/constrained network segments. Second, it may be a single
1774 subnet only or a multi-subnet, e.g., multiple 6LoWPAN networks joined
1775 by a single backbone LAN. Third, a wireless network segment may have
1776 all its nodes reachable in a single IP hop (fully connected), or it
1777 may require multiple IP hops for some pairs of nodes to reach each
1778 other.
1779
1780 Each topology may pose different requirements on the configuration of
1781 routers and protocol(s), in order to enable efficient CoAP group
1782 communication. To enable all the above target network topologies, an
1783 implementation of CoAP group communication needs to allow the
1784 following:
1785
1786
1787
1788 <span class="grey">Rahman &amp; Dijk Experimental [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1791
1792
1793 1. Routing/forwarding of IP multicast packets over multiple hops.
1794
1795 2. Routing/forwarding of IP multicast packets over subnet boundaries
1796 between traditional and constrained (e.g., LLN) networks.
1797
1798 The remainder of this section discusses solutions to enable both
1799 features.
1800
1801 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Networks Using the MLD Protocol</span>
1802
1803 CoAP nodes that are IP hosts (i.e., not IP routers) are generally
1804 unaware of the specific IP multicast routing/forwarding protocol
1805 being used. When such a host needs to join a specific (CoAP)
1806 multicast group, it requires a way to signal to IP multicast routers
1807 which IP multicast traffic it wants to receive.
1808
1809 The MLD protocol [<a href="./rfc3810" title="&quot;Multicast Listener Discovery Version 2 (MLDv2) for IPv6&quot;">RFC3810</a>] (see <a href="#appendix-A">Appendix A</a> of this document) is the
1810 standard IPv6 method to achieve this; therefore, this approach should
1811 be used on traditional IP networks. CoAP server nodes would then act
1812 in the role of MLD Multicast Address Listener.
1813
1814 The guidelines from [<a href="./rfc6636" title="&quot;Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless Networks&quot;">RFC6636</a>] on the tuning of MLD for mobile and
1815 wireless networks may be useful when implementing MLD in LLNs.
1816 However, on LLNs and 6LoWPAN networks, the use of MLD may not be
1817 feasible at all due to constraints on code size, memory, or network
1818 capacity.
1819
1820 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Networks Using RPL Multicast without MLD</span>
1821
1822 It is assumed in this section that the MLD protocol is not
1823 implemented in a network, for example, due to resource constraints.
1824 The RPL routing protocol (see <a href="./rfc6550#section-12">Section&nbsp;12 of [RFC6550]</a>) defines the
1825 advertisement of IP multicast destinations using Destination
1826 Advertisement Object (DAO) messages and routing of multicast IPv6
1827 packets based on this. It requires the RPL mode of operation to be 3
1828 (Storing mode with multicast support).
1829
1830 Hence, RPL DAO can be used by CoAP nodes that are RPL routers, or are
1831 RPL Leaf Nodes, to advertise IP multicast group membership to parent
1832 routers. Then, RPL is used to route IP multicast CoAP requests over
1833 multiple hops to the correct CoAP servers.
1834
1835 The same DAO mechanism can be used to convey IP multicast group
1836 membership information to an edge router (e.g., 6LBR), in case the
1837 edge router is also the root of the RPL Destination-Oriented Directed
1838 Acyclic Graph (DODAG). This is useful because the edge router then
1839 learns which IP multicast traffic it needs to pass through from the
1840 backbone network into the LLN subnet. In 6LoWPAN networks, such
1841
1842
1843
1844 <span class="grey">Rahman &amp; Dijk Experimental [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1847
1848
1849 selective "filtering" helps to avoid congestion of a 6LoWPAN subnet
1850 by IP multicast traffic from the traditional backbone IP network.
1851
1852 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Networks Using MPL Forwarding without MLD</span>
1853
1854 The MPL forwarding protocol [<a href="#ref-MCAST-MPL">MCAST-MPL</a>] can be used for propagation
1855 of IPv6 multicast packets to all MPL Forwarders within a predefined
1856 network domain, over multiple hops. MPL is designed to work in LLNs.
1857 In this section, it is again assumed that MLD is not implemented in
1858 the network, for example, due to resource limitations in an LLN.
1859
1860 The purpose of MPL is to let a predefined group of Forwarders
1861 collectively work towards the goal of distributing an IPv6 multicast
1862 packet throughout an MPL Domain. (A Forwarder node may be associated
1863 to multiple MPL Domains at the same time.) So, it would appear that
1864 there is no need for CoAP servers to advertise their multicast group
1865 membership, since any IP multicast packet that enters the MPL Domain
1866 is distributed to all MPL Forwarders without regard to what multicast
1867 addresses the individual nodes are listening to.
1868
1869 However, if an IP multicast request originates just outside the MPL
1870 Domain, the request will not be propagated by MPL. An example of
1871 such a case is the network topology of Figure 1 where the subnets are
1872 6LoWPAN subnets and for each 6LoWPAN subnet, one Realm-Local
1873 ([<a href="./rfc7346" title="&quot;IPv6 Multicast Address Scopes&quot;">RFC7346</a>]) MPL Domain is defined. The backbone network in this case
1874 is not part of any MPL Domain.
1875
1876 This situation can become a problem in building control use cases,
1877 for example, when the controller client needs to send a single IP
1878 multicast request to the group Room-A-Lights. By default, the
1879 request would be blocked by Rtr-1 and by Rtr-2 and not enter the
1880 Realm-Local MPL Domains associated to Subnet-1 and Subnet-2. The
1881 reason is that Rtr-1 and Rtr-2 do not have the knowledge that devices
1882 in Subnet-1/2 want to listen for IP packets destined to IP multicast
1883 group Room-A-Lights.
1884
1885 To solve the above issue, the following solutions could be applied:
1886
1887 1. Extend the MPL Domain, e.g., in the above example, include the
1888 network backbone to be part of each of the two MPL Domains. Or,
1889 in the above example, create just a single MPL Domain that
1890 includes both 6LoWPAN subnets plus the backbone link, which is
1891 possible since MPL is not tied to a single link-layer technology.
1892
1893 2. Manual configuration of an edge router(s) as an MPL Seed(s) for
1894 specific IP multicast traffic. In the above example, this could
1895 be done through the following three steps: First, configure Rtr-1
1896 and Rtr-2 to act as MLD Address Listeners for the Room-A-Lights
1897
1898
1899
1900 <span class="grey">Rahman &amp; Dijk Experimental [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1903
1904
1905 IP multicast group. This step allows any (other) routers on the
1906 backbone to learn that at least one node on the backbone link is
1907 interested in receiving any IP multicast traffic to
1908 Room-A-Lights. Second, configure both routers to "inject" any IP
1909 multicast packets destined to group Room-A-Lights into the
1910 (Realm-Local) MPL Domain that is associated to that router.
1911 Third, configure both routers to propagate any IPv6 multicast
1912 packets originating from within their associated MPL Domain to
1913 the backbone, if at least one node on the backbone has indicated
1914 interest in receiving such IPv6 packets (for which MLD is used on
1915 the backbone).
1916
1917 3. Use an additional protocol/mechanism for injection of IP
1918 multicast traffic from outside an MPL Domain into that MPL
1919 Domain, based on IP multicast group subscriptions of Forwarders
1920 within the MPL Domain. Such a protocol is currently not defined
1921 in [<a href="#ref-MCAST-MPL">MCAST-MPL</a>].
1922
1923 In conclusion, MPL can be used directly in case all sources of IP
1924 multicast CoAP requests (CoAP clients) and also all the destinations
1925 (CoAP servers) are inside a single MPL Domain. Then, each source
1926 node acts as an MPL Seed. In all other cases, MPL can only be used
1927 with additional protocols and/or configuration on how IP multicast
1928 packets can be injected from outside into an MPL Domain.
1929
1930 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. 6LoWPAN Specific Guidelines for the 6LBR</span>
1931
1932 To support multi-subnet scenarios for CoAP group communication, it is
1933 recommended that a 6LBR will act in an MLD router role on the
1934 backbone link. If this is not possible, then the 6LBR should be
1935 configured to act as an MLD Multicast Address Listener (see
1936 <a href="#appendix-A">Appendix A</a>) on the backbone link.
1937
1938 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
1939
1940 This section describes the relevant security configuration for CoAP
1941 group communication using IP multicast. The threats to CoAP group
1942 communication are also identified, and various approaches to mitigate
1943 these threats are summarized.
1944
1945 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Security Configuration</span>
1946
1947 As defined in Sections <a href="#section-8.1">8.1</a> and <a href="#section-9.1">9.1</a> of [<a href="./rfc7252" title="&quot;The Constrained Application Protocol (CoAP)&quot;">RFC7252</a>], CoAP group
1948 communication based on IP multicast will do the following:
1949
1950 o Operate in CoAP NoSec (No Security) mode, until a future group
1951 security solution is developed (see also <a href="#section-5.3.3">Section 5.3.3</a>).
1952
1953
1954
1955
1956 <span class="grey">Rahman &amp; Dijk Experimental [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
1959
1960
1961 o Use the "coap" scheme. The "coaps" scheme should only be used
1962 when a future group security solution is developed (see also
1963 <a href="#section-5.3.3">Section 5.3.3</a>).
1964
1965 Essentially, the above configuration means that there is currently no
1966 security at the CoAP layer for group communication. Therefore, for
1967 sensitive and mission-critical applications (e.g., health monitoring
1968 systems and alarm monitoring systems), it is currently recommended to
1969 deploy CoAP group communication with an application-layer security
1970 mechanism (e.g., data object security) for improved security.
1971
1972 Application-level security has many desirable properties, including
1973 maintaining security properties while forwarding traffic through
1974 intermediaries (proxies). Application-level security also tends to
1975 more cleanly separate security from the dynamics of group membership
1976 (e.g., the problem of distributing security keys across large groups
1977 with many members that come and go).
1978
1979 Without application-layer security, CoAP group communication should
1980 only be currently deployed in non-critical applications (e.g., read-
1981 only temperature sensors). Only when security solutions at the CoAP
1982 layer are mature enough (see <a href="#section-5.3.3">Section 5.3.3</a>) should CoAP group
1983 communication without application-layer security be considered for
1984 sensitive and mission-critical applications.
1985
1986 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Threats</span>
1987
1988 As noted above, there is currently no security at the CoAP layer for
1989 group communication. This is due to the fact that the current DTLS-
1990 based approach for CoAP is exclusively unicast oriented and does not
1991 support group security features such as group key exchange and group
1992 authentication. As a direct consequence of this, CoAP group
1993 communication is vulnerable to all attacks mentioned in <a href="./rfc7252#section-11">Section&nbsp;11 of
1994 [RFC7252]</a> for IP multicast.
1995
1996 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Threat Mitigation</span>
1997
1998 <a href="./rfc7252#section-11">Section&nbsp;11 of [RFC7252]</a> identifies various threat mitigation
1999 techniques for CoAP group communication. In addition to those
2000 guidelines, it is recommended that for sensitive data or safety-
2001 critical control, a combination of appropriate link-layer security
2002 and administrative control of IP multicast boundaries should be used.
2003 Some examples are given below.
2004
2005
2006
2007
2008
2009
2010
2011
2012 <span class="grey">Rahman &amp; Dijk Experimental [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2015
2016
2017 <span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. WiFi Scenario</span>
2018
2019 In a home automation scenario (using WiFi), the WiFi encryption
2020 should be enabled to prevent rogue nodes from joining. The Customer
2021 Premises Equipment (CPE) that enables access to the Internet should
2022 also have its IP multicast filters set so that it enforces multicast
2023 scope boundaries to isolate local multicast groups from the rest of
2024 the Internet (e.g., as per [<a href="./rfc6092" title="&quot;Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service&quot;">RFC6092</a>]). In addition, the scope of the
2025 IP multicast should be set to be site-local or smaller scope. For
2026 site-local scope, the CPE will be an appropriate multicast scope
2027 boundary point.
2028
2029 <span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. 6LoWPAN Scenario</span>
2030
2031 In a building automation scenario, a particular room may have a
2032 single 6LoWPAN network with a single edge router (6LBR). Nodes on
2033 the subnet can use link-layer encryption to prevent rogue nodes from
2034 joining. The 6LBR can be configured so that it blocks any incoming
2035 (6LoWPAN-bound) IP multicast traffic. Another example topology could
2036 be a multi-subnet 6LoWPAN in a large conference room. In this case,
2037 the backbone can implement port authentication (IEEE 802.1X) to
2038 ensure only authorized devices can join the Ethernet backbone. The
2039 access router to this secured network segment can also be configured
2040 to block incoming IP multicast traffic.
2041
2042 <span class="h4"><a class="selflink" id="section-5.3.3" href="#section-5.3.3">5.3.3</a>. Future Evolution</span>
2043
2044 In the future, to further mitigate the threats, security enhancements
2045 need to be developed at the IETF for group communications. This will
2046 allow introduction of a secure mode of CoAP group communication and
2047 use of the "coaps" scheme for that purpose.
2048
2049 At the time of writing this specification, there are various
2050 approaches being considered for security enhancements for group
2051 communications. Specifically, a lot of the current effort at the
2052 IETF is geared towards developing DTLS-based group communication.
2053 This is primarily motivated by the fact that unicast CoAP security is
2054 DTLS based (<a href="./rfc7252#section-9.1">Section&nbsp;9.1 of [RFC7252]</a>. For example, [<a href="#ref-MCAST-SECURITY">MCAST-SECURITY</a>]
2055 proposes DTLS-based IP multicast security. However, it is too early
2056 to conclude if this is the best approach. Alternatively,
2057 [<a href="#ref-IPSEC-PAYLOAD">IPSEC-PAYLOAD</a>] proposes IPsec-based IP multicast security. This
2058 approach also needs further investigation and validation.
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Rahman &amp; Dijk Experimental [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2071
2072
2073 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Monitoring Considerations</span>
2074
2075 <span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. General Monitoring</span>
2076
2077 CoAP group communication is meant to be used to control a set of
2078 related devices (e.g., simultaneously turn on all the lights in a
2079 room). This intrinsically exposes the group to some unique
2080 monitoring risks that solitary devices (i.e., devices not in a group)
2081 are not as vulnerable to. For example, assume an attacker is able to
2082 physically see a set of lights turn on in a room. Then the attacker
2083 can correlate a CoAP group communication message to that easily
2084 observable coordinated group action even if the contents of the
2085 message are encrypted by a future security solution (see
2086 <a href="#section-5.3.3">Section 5.3.3</a>). This will give the attacker side-channel information
2087 to plan further attacks (e.g., by determining the members of the
2088 group, then some network topology information may be deduced).
2089
2090 One mitigation to group communication monitoring risks that should be
2091 explored in the future is methods to decorrelate coordinated group
2092 actions. For example, if a CoAP group communication GET is sent to
2093 all the alarm sensors in a house, then their (unicast) responses
2094 should be as decorrelated as possible. This will introduce greater
2095 entropy into the system and will make it harder for an attacker to
2096 monitor and gather side-channel information.
2097
2098 <span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. Pervasive Monitoring</span>
2099
2100 A key additional threat consideration for group communication is
2101 pointed to by [<a href="./rfc7258" title="&quot;Pervasive Monitoring Is an Attack&quot;">RFC7258</a>], which warns of the dangers of pervasive
2102 monitoring. CoAP group communication solutions that are built on top
2103 of IP multicast need to pay particular heed to these dangers. This
2104 is because IP multicast is easier to intercept (e.g., and to secretly
2105 record) compared to unicast traffic. Also, CoAP traffic is meant for
2106 the Internet of Things. This means that CoAP traffic (once future
2107 security solutions are developed as in <a href="#section-5.3.3">Section 5.3.3</a>) may be used for
2108 the control and monitoring of critical infrastructure (e.g., lights,
2109 alarms, etc.) that may be prime targets for attack.
2110
2111 For example, an attacker may attempt to record all the CoAP traffic
2112 going over the smart grid (i.e., networked electrical utility) of a
2113 country and try to determine critical nodes for further attacks. For
2114 example, the source node (controller) sends out the CoAP group
2115 communication messages. CoAP multicast traffic is inherently more
2116 vulnerable (compared to a unicast packet) as the same packet may be
2117 replicated over many links, so there is a much higher probability of
2118 it getting captured by a pervasive monitoring system.
2119
2120
2121
2122
2123
2124 <span class="grey">Rahman &amp; Dijk Experimental [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2127
2128
2129 One useful mitigation to pervasive monitoring is to restrict the
2130 scope of the IP multicast to the minimal scope that fulfills the
2131 application need. Thus, for example, site-local IP multicast scope
2132 is always preferred over global scope IP multicast if this fulfills
2133 the application needs. This approach has the added advantage that it
2134 coincides with the guidelines for minimizing congestion control (see
2135 <a href="#section-2.8">Section 2.8</a>).
2136
2137 In the future, even if all the CoAP multicast traffic is encrypted,
2138 an attacker may still attempt to capture the traffic and perform an
2139 off-line attack, though of course having the multicast traffic
2140 protected is always desirable as it significantly raises the cost to
2141 an attacker (e.g., to break the encryption) versus unprotected
2142 multicast traffic.
2143
2144 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
2145
2146 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. New 'core.gp' Resource Type</span>
2147
2148 This memo registers a new Resource Type (rt=) Link Target Attribute,
2149 'core.gp', in the "Resource Type (rt=) Link Target Attribute Values"
2150 subregistry under the "Constrained RESTful Environments (CoRE)
2151 Parameters" registry.
2152
2153 Attribute Value: core.gp
2154
2155 Description: Group Configuration resource. This resource is used to
2156 query/manage the group membership of a CoAP server.
2157
2158 Reference: See <a href="#section-2.6.2">Section 2.6.2</a>.
2159
2160 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. New 'coap-group+json' Internet Media Type</span>
2161
2162 This memo registers a new Internet media type for the CoAP Group
2163 Configuration resource called 'application/coap-group+json'.
2164
2165 Type name: application
2166
2167 Subtype name: coap-group+json
2168
2169 Required parameters: None
2170
2171 Optional parameters: None
2172
2173 Encoding considerations: 8-bit UTF-8.
2174
2175 JSON to be represented using UTF-8, which is 8-bit compatible (and
2176 most efficient for resource constrained implementations).
2177
2178
2179
2180 <span class="grey">Rahman &amp; Dijk Experimental [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2183
2184
2185 Security considerations:
2186
2187 Denial-of-Service attacks could be performed by constantly
2188 (re-)setting the Group Configuration resource of a CoAP endpoint to
2189 different values. This will cause the endpoint to register (or
2190 deregister) from the related IP multicast group. To prevent this, it
2191 is recommended that a form of authorization (making use of unicast
2192 DTLS-secured CoAP) be used such that only authorized controllers are
2193 allowed by an endpoint to configure its group membership.
2194
2195 Interoperability considerations: None
2196
2197 Published specification: <a href="./rfc7390">RFC 7390</a>
2198
2199 Applications that use this media type:
2200
2201 CoAP client and server implementations that wish to set/read the
2202 Group Configuration resource via the 'application/coap-group+json'
2203 payload as described in <a href="#section-2.6.2">Section 2.6.2</a>.
2204
2205 Fragment identifier considerations: N/A
2206
2207 Additional Information:
2208
2209 Deprecated alias names for this type: None
2210
2211 Magic number(s): None
2212
2213 File extension(s): *.json
2214
2215 Macintosh file type code(s): TEXT
2216
2217 Person and email address to contact for further information:
2218
2219 Esko Dijk ("[email protected]")
2220
2221 Intended usage: COMMON
2222
2223 Restrictions on usage: None
2224
2225 Author: CoRE WG
2226
2227 Change controller: IETF
2228
2229 Provisional registration? (standards tree only): N/A
2230
2231
2232
2233
2234
2235
2236 <span class="grey">Rahman &amp; Dijk Experimental [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2239
2240
2241 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
2242
2243 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
2244
2245 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
2246 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997,
2247 &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.
2248
2249 [<a id="ref-RFC2782">RFC2782</a>] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
2250 specifying the location of services (DNS SRV)", <a href="./rfc2782">RFC 2782</a>,
2251 February 2000, &lt;<a href="http://www.rfc-editor.org/info/rfc2782">http://www.rfc-editor.org/info/rfc2782</a>&gt;.
2252
2253 [<a id="ref-RFC3376">RFC3376</a>] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
2254 Thyagarajan, "Internet Group Management Protocol, Version
2255 3", <a href="./rfc3376">RFC 3376</a>, October 2002,
2256 &lt;<a href="http://www.rfc-editor.org/info/rfc3376">http://www.rfc-editor.org/info/rfc3376</a>&gt;.
2257
2258 [<a id="ref-RFC3433">RFC3433</a>] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor
2259 Management Information Base", <a href="./rfc3433">RFC 3433</a>, December 2002,
2260 &lt;<a href="http://www.rfc-editor.org/info/rfc3433">http://www.rfc-editor.org/info/rfc3433</a>&gt;.
2261
2262 [<a id="ref-RFC3542">RFC3542</a>] Stevens, W., Thomas, M., Nordmark, E., and T. Jinmei,
2263 "Advanced Sockets Application Program Interface (API) for
2264 IPv6", <a href="./rfc3542">RFC 3542</a>, May 2003,
2265 &lt;<a href="http://www.rfc-editor.org/info/rfc3542">http://www.rfc-editor.org/info/rfc3542</a>&gt;.
2266
2267 [<a id="ref-RFC3810">RFC3810</a>] Vida, R. and L. Costa, "Multicast Listener Discovery
2268 Version 2 (MLDv2) for IPv6", <a href="./rfc3810">RFC 3810</a>, June 2004,
2269 &lt;<a href="http://www.rfc-editor.org/info/rfc3810">http://www.rfc-editor.org/info/rfc3810</a>&gt;.
2270
2271 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
2272 Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
2273 <a href="./rfc3986">3986</a>, January 2005,
2274 &lt;<a href="http://www.rfc-editor.org/info/rfc3986">http://www.rfc-editor.org/info/rfc3986</a>&gt;.
2275
2276 [<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
2277 Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006,
2278 &lt;<a href="http://www.rfc-editor.org/info/rfc4291">http://www.rfc-editor.org/info/rfc4291</a>&gt;.
2279
2280 [<a id="ref-RFC4601">RFC4601</a>] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
2281 "Protocol Independent Multicast - Sparse Mode (PIM-SM):
2282 Protocol Specification (Revised)", <a href="./rfc4601">RFC 4601</a>, August 2006,
2283 &lt;<a href="http://www.rfc-editor.org/info/rfc4601">http://www.rfc-editor.org/info/rfc4601</a>&gt;.
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Rahman &amp; Dijk Experimental [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2295
2296
2297 [<a id="ref-RFC4919">RFC4919</a>] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6
2298 over Low-Power Wireless Personal Area Networks (6LoWPANs):
2299 Overview, Assumptions, Problem Statement, and Goals", <a href="./rfc4919">RFC</a>
2300 <a href="./rfc4919">4919</a>, August 2007,
2301 &lt;<a href="http://www.rfc-editor.org/info/rfc4919">http://www.rfc-editor.org/info/rfc4919</a>&gt;.
2302
2303 [<a id="ref-RFC4944">RFC4944</a>] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
2304 "Transmission of IPv6 Packets over IEEE 802.15.4
2305 Networks", <a href="./rfc4944">RFC 4944</a>, September 2007,
2306 &lt;<a href="http://www.rfc-editor.org/info/rfc4944">http://www.rfc-editor.org/info/rfc4944</a>&gt;.
2307
2308 [<a id="ref-RFC5110">RFC5110</a>] Savola, P., "Overview of the Internet Multicast Routing
2309 Architecture", <a href="./rfc5110">RFC 5110</a>, January 2008,
2310 &lt;<a href="http://www.rfc-editor.org/info/rfc5110">http://www.rfc-editor.org/info/rfc5110</a>&gt;.
2311
2312 [<a id="ref-RFC5771">RFC5771</a>] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
2313 IPv4 Multicast Address Assignments", <a href="https://www.rfc-editor.org/bcp/bcp51">BCP 51</a>, <a href="./rfc5771">RFC 5771</a>,
2314 March 2010, &lt;<a href="http://www.rfc-editor.org/info/rfc5771">http://www.rfc-editor.org/info/rfc5771</a>&gt;.
2315
2316 [<a id="ref-RFC5952">RFC5952</a>] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
2317 Address Text Representation", <a href="./rfc5952">RFC 5952</a>, August 2010,
2318 &lt;<a href="http://www.rfc-editor.org/info/rfc5952">http://www.rfc-editor.org/info/rfc5952</a>&gt;.
2319
2320 [<a id="ref-RFC6092">RFC6092</a>] Woodyatt, J., "Recommended Simple Security Capabilities in
2321 Customer Premises Equipment (CPE) for Providing
2322 Residential IPv6 Internet Service", <a href="./rfc6092">RFC 6092</a>, January
2323 2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6092">http://www.rfc-editor.org/info/rfc6092</a>&gt;.
2324
2325 [<a id="ref-RFC6550">RFC6550</a>] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
2326 Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
2327 Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
2328 Lossy Networks", <a href="./rfc6550">RFC 6550</a>, March 2012,
2329 &lt;<a href="http://www.rfc-editor.org/info/rfc6550">http://www.rfc-editor.org/info/rfc6550</a>&gt;.
2330
2331 [<a id="ref-RFC6636">RFC6636</a>] Asaeda, H., Liu, H., and Q. Wu, "Tuning the Behavior of
2332 the Internet Group Management Protocol (IGMP) and
2333 Multicast Listener Discovery (MLD) for Routers in Mobile
2334 and Wireless Networks", <a href="./rfc6636">RFC 6636</a>, May 2012,
2335 &lt;<a href="http://www.rfc-editor.org/info/rfc6636">http://www.rfc-editor.org/info/rfc6636</a>&gt;.
2336
2337 [<a id="ref-RFC6690">RFC6690</a>] Shelby, Z., "Constrained RESTful Environments (CoRE) Link
2338 Format", <a href="./rfc6690">RFC 6690</a>, August 2012,
2339 &lt;<a href="http://www.rfc-editor.org/info/rfc6690">http://www.rfc-editor.org/info/rfc6690</a>&gt;.
2340
2341 [<a id="ref-RFC6763">RFC6763</a>] Cheshire, S. and M. Krochmal, "DNS-Based Service
2342 Discovery", <a href="./rfc6763">RFC 6763</a>, February 2013,
2343 &lt;<a href="http://www.rfc-editor.org/info/rfc6763">http://www.rfc-editor.org/info/rfc6763</a>&gt;.
2344
2345
2346
2347
2348 <span class="grey">Rahman &amp; Dijk Experimental [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2351
2352
2353 [<a id="ref-RFC6775">RFC6775</a>] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,
2354 "Neighbor Discovery Optimization for IPv6 over Low-Power
2355 Wireless Personal Area Networks (6LoWPANs)", <a href="./rfc6775">RFC 6775</a>,
2356 November 2012, &lt;<a href="http://www.rfc-editor.org/info/rfc6775">http://www.rfc-editor.org/info/rfc6775</a>&gt;.
2357
2358 [<a id="ref-RFC7159">RFC7159</a>] Bray, T., "The JavaScript Object Notation (JSON) Data
2359 Interchange Format", <a href="./rfc7159">RFC 7159</a>, March 2014,
2360 &lt;<a href="http://www.rfc-editor.org/info/rfc7159">http://www.rfc-editor.org/info/rfc7159</a>&gt;.
2361
2362 [<a id="ref-RFC7230">RFC7230</a>] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
2363 (HTTP/1.1): Message Syntax and Routing", <a href="./rfc7230">RFC 7230</a>, June
2364 2014, &lt;<a href="http://www.rfc-editor.org/info/rfc7230">http://www.rfc-editor.org/info/rfc7230</a>&gt;.
2365
2366 [<a id="ref-RFC7252">RFC7252</a>] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
2367 Application Protocol (CoAP)", <a href="./rfc7252">RFC 7252</a>, June 2014,
2368 &lt;<a href="http://www.rfc-editor.org/info/rfc7252">http://www.rfc-editor.org/info/rfc7252</a>&gt;.
2369
2370 [<a id="ref-RFC7258">RFC7258</a>] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
2371 Attack", <a href="https://www.rfc-editor.org/bcp/bcp188">BCP 188</a>, <a href="./rfc7258">RFC 7258</a>, May 2014,
2372 &lt;<a href="http://www.rfc-editor.org/info/rfc7258">http://www.rfc-editor.org/info/rfc7258</a>&gt;.
2373
2374 [<a id="ref-RFC7320">RFC7320</a>] Nottingham, M., "URI Design and Ownership", <a href="https://www.rfc-editor.org/bcp/bcp190">BCP 190</a>, <a href="./rfc7320">RFC</a>
2375 <a href="./rfc7320">7320</a>, July 2014, &lt;<a href="http://www.rfc-editor.org/info/rfc7320">http://www.rfc-editor.org/info/rfc7320</a>&gt;.
2376
2377 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
2378
2379 [<a id="ref-RFC1033">RFC1033</a>] Lottor, M., "Domain administrators operations guide", <a href="./rfc1033">RFC</a>
2380 <a href="./rfc1033">1033</a>, November 1987,
2381 &lt;<a href="http://www.rfc-editor.org/info/rfc1033">http://www.rfc-editor.org/info/rfc1033</a>&gt;.
2382
2383 [<a id="ref-RFC4605">RFC4605</a>] Fenner, B., He, H., Haberman, B., and H. Sandick,
2384 "Internet Group Management Protocol (IGMP) / Multicast
2385 Listener Discovery (MLD)-Based Multicast Forwarding
2386 ("IGMP/MLD Proxying")", <a href="./rfc4605">RFC 4605</a>, August 2006,
2387 &lt;<a href="http://www.rfc-editor.org/info/rfc4605">http://www.rfc-editor.org/info/rfc4605</a>&gt;.
2388
2389 [<a id="ref-RFC5740">RFC5740</a>] Adamson, B., Bormann, C., Handley, M., and J. Macker,
2390 "NACK-Oriented Reliable Multicast (NORM) Transport
2391 Protocol", <a href="./rfc5740">RFC 5740</a>, November 2009,
2392 &lt;<a href="http://www.rfc-editor.org/info/rfc5740">http://www.rfc-editor.org/info/rfc5740</a>&gt;.
2393
2394 [<a id="ref-RFC7346">RFC7346</a>] Droms, R., "IPv6 Multicast Address Scopes", <a href="./rfc7346">RFC 7346</a>,
2395 August 2014, &lt;<a href="http://www.rfc-editor.org/info/rfc7346">http://www.rfc-editor.org/info/rfc7346</a>&gt;.
2396
2397 [<a id="ref-BLOCKWISE-CoAP">BLOCKWISE-CoAP</a>]
2398 Bormann, C. and Z. Shelby, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Blockwise+transfers+in+CoAP%22'>"Blockwise transfers in CoAP"</a>,
2399 Work in Progress, <a href="./draft-ietf-core-block-15">draft-ietf-core-block-15</a>, July 2014.
2400
2401
2402
2403
2404 <span class="grey">Rahman &amp; Dijk Experimental [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2407
2408
2409 [<a id="ref-CoRE-RD">CoRE-RD</a>] Shelby, Z., Bormann, C., and S. Krco, "CoRE Resource
2410 Directory", Work in Progress, <a href="./draft-ietf-core-resource-directory-01">draft-ietf-core-resource-</a>
2411 <a href="./draft-ietf-core-resource-directory-01">directory-01</a>, December 2013.
2412
2413 [<a id="ref-OBSERVE-CoAP">OBSERVE-CoAP</a>]
2414 Hartke, K., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Observing+Resources+in+CoAP%22'>"Observing Resources in CoAP"</a>, Work in
2415 Progress, <a href="./draft-ietf-core-observe-14">draft-ietf-core-observe-14</a>, June 2014.
2416
2417 [<a id="ref-MCAST-MPL">MCAST-MPL</a>]
2418 Hui, J. and R. Kelsey, "Multicast Protocol for Low power
2419 and Lossy Networks (MPL)", Work in Progress, <a href="./draft-ietf-roll-trickle-mcast-09">draft-ietf-</a>
2420 <a href="./draft-ietf-roll-trickle-mcast-09">roll-trickle-mcast-09</a>, April 2014.
2421
2422 [<a id="ref-MCAST-SECURITY">MCAST-SECURITY</a>]
2423 Keoh, S., Kumar, S., Garcia-Morchon, O., Dijk, E., and A.
2424 Rahman, "DTLS-based Multicast Security in Constrained
2425 Environments", Work in Progress, <a href="./draft-keoh-dice-multicast-security-08">draft-keoh-dice-</a>
2426 <a href="./draft-keoh-dice-multicast-security-08">multicast-security-08</a>, July 2014.
2427
2428 [<a id="ref-IPSEC-PAYLOAD">IPSEC-PAYLOAD</a>]
2429 Migault, D. and C. Bormann, "IPsec/ESP for Application
2430 Payload", Work in Progress, <a href="./draft-mglt-dice-ipsec-for-application-payload-00">draft-mglt-dice-ipsec-for-</a>
2431 <a href="./draft-mglt-dice-ipsec-for-application-payload-00">application-payload-00</a>, July 2014.
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460 <span class="grey">Rahman &amp; Dijk Experimental [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2463
2464
2465 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Multicast Listener Discovery (MLD)</span>
2466
2467 In order to extend the scope of IP multicast beyond link-local scope,
2468 an IP multicast routing or forwarding protocol has to be active in
2469 routers on an LLN. To achieve efficient IP multicast routing (i.e.,
2470 avoid always flooding IP multicast packets), routers have to learn
2471 which hosts need to receive packets addressed to specific IP
2472 multicast destinations.
2473
2474 The MLD protocol [<a href="./rfc3810" title="&quot;Multicast Listener Discovery Version 2 (MLDv2) for IPv6&quot;">RFC3810</a>] (or its IPv4 equivalent, IGMP [<a href="./rfc3376" title="&quot;Internet Group Management Protocol, Version 3&quot;">RFC3376</a>])
2475 is today the method of choice used by a (IP multicast-enabled) router
2476 to discover the presence of IP multicast listeners on directly
2477 attached links, and to discover which IP multicast addresses are of
2478 interest to those listening nodes. MLD was specifically designed to
2479 cope with fairly dynamic situations in which IP multicast listeners
2480 may join and leave at any time.
2481
2482 Optimal tuning of the parameters of MLD/IGMP for routers for mobile
2483 and wireless networks is discussed in [<a href="./rfc6636" title="&quot;Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless Networks&quot;">RFC6636</a>]. These guidelines
2484 may be useful when implementing MLD in LLNs.
2485
2486 Acknowledgements
2487
2488 Thanks to Jari Arkko, Peter Bigot, Anders Brandt, Ben Campbell,
2489 Angelo Castellani, Alissa Cooper, Spencer Dawkins, Badis Djamaa,
2490 Adrian Farrel, Stephen Farrell, Thomas Fossati, Brian Haberman,
2491 Bjoern Hoehrmann, Matthias Kovatsch, Guang Lu, Salvatore Loreto,
2492 Kerry Lynn, Andrew McGregor, Kathleen Moriarty, Pete Resnick, Dale
2493 Seed, Zach Shelby, Martin Stiemerling, Peter van der Stok, Gengyu
2494 Wei, and Juan Carlos Zuniga for their helpful comments and
2495 discussions that have helped shape this document.
2496
2497 Special thanks to Carsten Bormann and Barry Leiba for their extensive
2498 and thoughtful Chair and AD reviews of the document. Their reviews
2499 helped to immeasurably improve the document quality.
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516 <span class="grey">Rahman &amp; Dijk Experimental [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc7390">RFC 7390</a> Group Communication for CoAP October 2014</span>
2519
2520
2521 Authors' Addresses
2522
2523 Akbar Rahman (editor)
2524 InterDigital Communications, LLC
2525 1000 Sherbrooke Street West
2526 Montreal, Quebec H3A 3G4
2527 Canada
2528
2529 EMail: [email protected]
2530
2531
2532 Esko Dijk (editor)
2533 Philips Research
2534 High Tech Campus 34
2535 Eindhoven 5656AE
2536 Netherlands
2537
2538 EMail: [email protected]
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572 Rahman &amp; Dijk Experimental [Page 46]
2573 </pre>