Connectivity Framework Annex D: Assessment Template: HTTP
D. 6.3 Usage Viewpoint
D. 6.3.1 Architecture( Section 6.3.1)
D. 6.3.2 Technology
Options( Section 6.3.2)
D. 6.3.3 Applications( Section 6.3.3)
D. 6.3.4 Typical
Usage( Section 2.2)
D. 6.3.5 Operations( Section 2.3.8)
D. 6.3.6 Security( Section 2.3.5)
D. 6.3.7 Safety( Section 2.3.9)
D. 6.3.8 Gateways( Section 3.3)
Summarize the main concepts, and high-level architecture, and terminology. Describe the end-to-end information exchange path.
HTTP defines a request-reply application protocol to exchange application state represented as hypertext with embedded resource identifiers. A client can request some action on a server resource, and be informed of the outcome of that request.
A client request consists of an action method and a resource( path) on which the method is to be applied. The server replies to the request with a status code, which informs the client of the outcome of the method or the reason the method was not performed.
Each request or reply message can have associated resource representation metadata header fields, which are name-value pairs, and provide additional information about the operation. Some headers are pre-defined, and applications can add their own headers.
Each request or reply message can also have an optional body to hold a resource representation, which is hypertext with embedded links to resources. List the choices to be made for using the connectivity technology in a system.
• Selection of resource representation format.
• Multiple implementations choices for client and server libraries are available, including open source and proprietary, in a variety of programming languages. Implementations vary in their quality, performance, scalability, availability and security characteristics.
A general statement of the typical applications that rely on this connectivity technology and the reason for using the connectivity technology.
HTTP is most commonly known for navigating web pages and building application server interfaces. HTTP based applications are typically driven by a human end user. In the context of IoT, HTTP is also used as a connectivity transport for Information Technology( IT) applications. What function or where in the system this technology is typically used?
HTTP is typically used for serving web pages, and for exposing application server interfaces, and as a connectivity transport layer for some connectivity frameworks. Can one monitor, manage, and dynamically replace elements of the connectivity function?
Yes, another that can serve the same resources can replace a server. A server can support multiple clients. What are the system security implications of this connectivity technology?
HTTP uses transport layer security( TLS) to provide end-to-end authentication, encryption and integrity. HTTP over TLS is referred to as HTTPS. For systems that need it, are certifiable implementations available? There are no known safety certifiable implementations of HTTP.
List of gateways to core connectivity standards and other relevant connectivity technologies.
Gateways to HTTP are defined by other core connectivity standards:
• OMG’ s Web-Enabled DDS defines a gateway for DDS. It allows HTTP clients to participate in a DDS data space.
• OPC-UA supports a web service protocol using HTTP.
• oneM2M uses HTTP as a connectivity transport option
IIC: PUB: G5: V1.0: PB: 20170228- 96-