Connectivity Framework Annex D: Assessment Template: HTTP
D. 6.5 Implementation Viewpoint D. 6.5.5 Availability Considerations
Redundancy( Section 4.2.5.1)
Recovery( Section 4.2.5.2)
D. 6.5.6 Deployment Considerations
Platforms Constraints( Section 4.2.6.1)
Incremental Upgrades
( Section 4.2.6.2)
D. 6.5.7 Network Layer Considerations
Topology( Section 5.2.1.1)
Span( Section 5.2.1.2)
Segmentation( Section 5.2.1.3)
Can the connectivity framework support continuous availability over a defined systemrelevant time period?
Yes, HTTP can support continuous availability over a system relevant time period, as evidenced by the WWW. Can the connectivity framework support recovery when fault conditions occur?
Yes, HTTP can support recovery when fault conditions occur.
Does the connectivity framework support the operating system( OS), the CPU and the resource constraints on the platform( s) being used?
HTTP is generally available on a wide variety of operating systems on a variety of CPUs, including embedded devices. Does the connectivity framework facilitate incremental upgrades?
Yes, HTTP facilitates incremental upgrades. Since the hypertext from a server controls the client interface, it can be upgraded any time. This is evidenced by the success of the WWW.
What network topologies are allowed?
HTTP is agnostic to network topologies, as it runs above the network layer. What is the span of the transport: LAN vs. WAN?
HTTP can be used over LAN and WAN. It is typically used over WAN, as is evidenced by the WWW. IT infrastructure and firewall are friendly to HTTP.
Can the transport support multiple independent and isolated communication paths between the same network endpoints?
Yes, HTTP can support multiple independent isolated communication paths between the same network endpoints.
IIC: PUB: G5: V1.0: PB: 20170228- 100-