Connectivity Framework Annex D : Assessment Template : HTTP
D . 6.4 Functional Viewpoint
Data Quality of Service ( QoS ) ( Section 4.1.10 )
Data Security ( Section 4.1.11 )
API ( Section 4.1.12 )
Governance ( Section 4.1.13 )
D . 6.4.2 Core Transport Layer Functions
Messaging Protocol ( Section 5.1.1 )
Communication Modes ( Section 5.1.2 )
Endpoint Addressing ( Section 5.1.3 )
Connectedness ( Section 5.1.4 )
Prioritization ( Section 5.1.5 )
Timing & Synchronization ( Section 5.1.6 )
Message Security ( Section 5.1.7 )
Does it support data QoS ? Summarize the scope and coverage . Highlight the salient aspects .
HTTP does not provide data qualify of service as described in section 4.1.10 . Does it provide a data object security model ? Summarize the salient aspects . HTTP does not provide a data object security model . Is there a standard API ? Which programming languages is it available for ?
HTTP does not provide a standardized programming API . However , libraries are available in most popular programming languages and provide user friendly APIs .
Does it standardize the mechanisms for configuration , administration , and monitoring ? Summarize the salient aspects .
HTTP does not define a standardized way to configure , administer , and manage a server . Configuration , administration , and monitoring of HTTP servers is implementation specific . It common practice to use configuration files for administration and log files for monitoring .
Does it require UDP or TCP ? What are the salient aspects of the messaging protocol ? What are the message size limitations ? What are the usage assumptions ? Is it optimized for certain message requirements ?
HTTP relies on TCP . It required reliable , ordered delivery of requests and responses . It can support partial or chunked delivery of requests and responses . There are no inherent message size limitations . Which communication modes does it support ?
Unicast .
Describe the transport endpoints . How are the endpoints addressed ? What are the limitations , if any , on the number of endpoints ?
A transport endpoint is a server IP address and a port number . There is no inherent limitation on the number of endpoints . Does it require a connected circuit between the endpoints ? Summarize the salient aspects .
No , HTTP does not require a connected circuit between a client and server . TCP connections may be torn down after a request-response , and reestablished for the next one . Does it provide a means to prioritize messages ? Summarize the salient aspects .
No , HTTP does not provide a means to prioritize messages . Does it provide the ability to synchronize time ? Summarize the salient aspects .
No , HTTP does not provide the ability to synchronize time . Does it provide mechanisms for message security ? Summarize the salient aspects . Yes , HTTP can use Transport Layer Security ( TLS ) over TCP to provide message security .
IIC : PUB : G5 : V1.0 : PB : 20170228 - 98 -