Opened 10 years ago

Closed 10 years ago

#252 closed protocol defect (fixed)

Conflicting security requirements in groupcomm/core-coap

Reported by: esko.dijk@… Owned by: draft-ietf-core-groupcomm@…
Priority: major Milestone:
Component: groupcomm Version:
Severity: Active WG Document Keywords:


Conflicting security requirements:
core-coap-12: "CoAP servers SHOULD NOT accept multicast requests that can not be authenticated".
groupcomm-03: "Group communications MUST operate in CoAP NoSec? (No Security) mode"

Should be resolved perhaps in either groupcomm, core-coap, or both?

Change History (2)

comment:1 Changed 10 years ago by cabo@…

There is some additional wording in coap-13, svn [1100].
This does not solve the problem, but describes what can be done at this point.
Leaving this open so additional work can be done in groupcomm.

comment:2 Changed 10 years ago by esko.dijk@…

  • Resolution set to fixed
  • Status changed from new to closed

Additional work added in GroupComm? svn [1210]. Describes some methods to meet the "authentication" requirement for multicast added in core-coap-13 svn [1100].

Note: See TracTickets for help on using tickets.