[core] CORECONF Hackathon implementation feedback

[Koen Zandberg <[e-mail]>]

Hi all,

During the hackathon I had another opportunity to work on my 
implementation for CORECONF. So far nothing from the spec translates 
into anything hard to implement. Most of the feedback here is either 
clarification I think is needed in the draft or originates from the 
removal of GET and PUT interaction on the individual data node resources.

Terminology: Data node resource needs rephrasing as it doesn't map to a 
single CoAP resource anymore now that GET/PUT on individual coap 
resources is no longer in the spec.

- 3.5.{1,2}: Is multiple RPCs and actions in a single POST request 
allowed and should there be something defined around ordering and 
parallel execution be defined?

- 5.2.2: This section can be removed entirely as far as I can see.

One thing discussed during the hackathon was to remove GET and PUT as 
operations on the full datastore as those could be replaced with FETCH 
and IPATCH operating on SID 0, which would make SID 0 a special full 
datastore SID. From (my) implementation perspective this is trivial to 
implement. The only minor concern I have here is that a DOS or battery 
drain attack might be possible on a device via a FETCH with payload [0, 
0, 0…] in other words, request the full datastore multiple times. Given 
that any interaction with the datastore must be authenticated I don't 
see a large concern here and even then it should be easy to mitigate on 
the device side.

Cheers,

Koen Zandberg