Connectivity Framework Annex E: Assessment Template: CoAP
E. 6.5 Implementation Viewpoint E. 6.5.4 Scalability Considerations
Data Objects( Section 4.2.4.1)
Apps( Section 4.2.4.2)
E. 6.5.5 Availability Considerations
Redundancy( Section 4.2.5.1)
Recovery( Section 4.2.5.2)
E. 6.5.6 Deployment Considerations
Platforms Constraints( Section 4.2.6.1)
Incremental Upgrades( Section 4.2.6.2)
Can the connectivity framework effectively handle an increasing number of data objects? What limits data object size?
Yes, CoAP can handle an effectively increasing number of data objects without constraints, as the limit of the resource identifier is the string size.
Can the connectivity framework effectively support interface evolution for an increasing number of distributed application components?
CoAP is designed with evolution and long-term robustness in mind; it can support future changes or extensions to the servers or clients, much like HTTP.
Can the connectivity framework support continuous availability over a defined systemrelevant time period?
Data availability will be determined by the availability of the CoAP Server, if the server is down a cached version of the resource can be accessed but it won’ t be“ fresh”.
CoAP doesn ' t provide functionality for redundancy as part of the protocol. This is considered part of the application layer. Can the connectivity framework support recovery when fault conditions occur?
CoAP doesn ' t provide functionality for recovery of fault conditions. This is considered part of the application layer.
Does the connectivity framework support the operating system( OS), the CPU and the resource constraints on the platform( s) being used?
CoAP is supported by several platforms, OSs and hardware. CoAP has been architected to work with constrained devices and networks in mind, and so can be made available on the smallest of platforms. Does the connectivity framework facilitate incremental upgrades?
CoAP, like HTTP, is designed with incremental updates and long-lasting client and server lifecycles. As a protocol CoAP does not place constraints on the upgradability of CoAP clients or servers. CoAP clients and server can use standard techniques for upgrading the CoAP client or server( load-balancers, clusters, virtualized environments).
IIC: PUB: G5: V1.0: PB: 20170228- 110-