Yep. That’s the one - Marko and Paul are working this.
Marko just moved it into net/oic. Paul/Marko have taken iotivity
constrained and plumbed it into Mynewt.
mgmt/mgmt is now the generic system interface to management APIs to
return data. These APIs return responses as key-value pairs, that can
either be encoded in JSON or CBOR.
mgmt/newtmgr is the existing newtmgr protocol, and the newtmgr facade
runs over this. newtmgr is smaller in code size than oic, but is very
mynewt specific as a transport technology.
mgmt/oicmgr is the mgmt/mgmt handlers transported over the OIC/OCF
implementation referenced below.
NOTE: for OIC, Marko/Paul haven’t don’t include 6low/IPSP/DTLS over
BLE, but rather just assume we’re going to run CoAP natively over the
GATT transport, at least by default (and to start with, it may make
sense to have this option later.) There is a WG in OIC underway that is
looking to standardize this approach - as BLE packets are a little small
to justify the full IP/DTLS payload.
Sterling
On 5 Oct 2016, at 10:13, Wayne Keenan wrote:
Hiya,
The OIC and OCF to which you refer, is it this?:
https://openconnectivity.org/resources/specifications
All the best
Wayne
On 29 September 2016 at 16:50, Sterling Hughes <[email protected]>
wrote:
Hey,
On 29 Sep 2016, at 7:42, James Pace wrote:
<snip>
imgmgr, and newtmgr could be broken into a TLD mgmt/ directory.
They
could also be put into “sys.” Other suggestions?
+1 for /mgmt
OK. mgmt carries the day. I really don’t like the name, so if you
have
any other suggestions (I don’t.)
I think iotivity should go into net/ as a sibling to nimble and ip
(maybe
rename to oic?) We should also break out and maintain the coap
implementation from iotivity as another sibling in the net/
directory.
+1
+1, too, on the rename to “oic". although, bear in mind that this
will
become “ocf” with the next rev.
OCF it is. I hope they follow suite when they implement the next
rev, and
don’t decided to separately name the specs from the standards org.
Sterling
