This is a feature release of IoTivity. This version contains additional features compared to IoTivity 1.2.x, in addition to numerous bug fixes.
Please find a detailed list of all changes in the Wiki: https://wiki.iotivity.org/release_note_1.3.0
OCF 1.0 compatibility
This release is meant to be compatible with the upcoming OCF 1.0 specification. At the time of this release, the certification tools from OCF are not yet complete, so it may contain incompatibilities not yet discovered. The IoTivity development team will work closely with the OCF Certification personnel to correct those issues when they arise and will issue patch releases in the 1.3.x series.
Device implementors and application developers are encouraged to use 1.3.0 right now to begin developing their OCF 1.0 services, while retaining the ability to either upgrade to 1.3.x bugfix releases or apply patches that correct the issues found.
Since release 1.3.0, IoTivity no longer includes any cryptographic code, with the previously-bundled TinyDTLS code removed. It does depend on a third-party cryptographic library, called mbedTLS, which is not shipped with IoTivity and must be installed separately during the build process.
The IoTivity Project does not issue security advisories for third-party libraries not bundled and will only issue patch releases if necessary to comply with proper usage of upstream. In all other cases, device implementors and application developers need to follow disclosures from the upstream sources themselves and upgrade or patch those libraries as necessary.
Important new features
- First release of the AllJoyn Bridge
- OCF 1.0 features:
- Version negotiation at the protocol level
- Endpoint list in discovery replies
- Security updates
- API support:
- Java API for generic systems (not Android-based)
- New Procedural Client API
- Plugin manager rewritten
- UPnP Bridge features:
- New sample devices
- Compatibility with the OCF 1.0 Bridge Specification