Subject: [core] draft-ietf-core-coap-09 - Multicast NON/RST matching rules

From: "Dijk, Esko" <[email-masked]>
Date: Tue, 17 Apr 2012 10:27:31 +0000

Section 4.3 defines matching based on Message ID for both unicast and multicast. Only for unicast, there is additional source/destination matching required.
Could/should we require matching of source/destination for multicast as well, in as far as possible?

E.g. in NoSec, UDP destination port number of multicast message and unicast response source port must match. [In case we don't include this on purpose, why then is this not needed for multicast but is needed for unicast?]
Or, e.g. for any tbd-in-the-future secured multicast modes the security context MUST match.

Esko Dijk
Senior scientist, Lighting Control Systems

Philips Group Innovation, Research
High Tech Campus 34 (room 1.059)
5656 AE  Eindhoven, The Netherlands
Phone: +31 40 27 47947, E-Mail: [email-masked]<mailto:[email-masked]>
Mobile: +31 6 12642103
www.research.philips.com<http://www.research.philips.com/>

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.