Connectivity Framework Annex D : Assessment Template : HTTP
D . 6.2 Business Viewpoint
D . 6.2.1 Purpose ( Section 6.2.1 )
D . 6.2.2 Pedigree ( Section 6.2.2 )
D . 6.2.3 Variants ( Section 6.2.3 )
D . 6.2.4 Maturity ( Section 6.2.4 )
D . 6.2.5 Stability ( Section 6.2.5 )
D . 6.2.6 Standards
Body ( Section 6.2.6 )
D . 6.2.7 Openness ( Section 6.2.7 )
Give the general motivation and expectation for the Connectivity Technology . This section provides the business rationale . It communicates the fundamental " why and what " for the project .
HTTP is the core connectivity transport of the World Wide Web ( WWW ). It was developed to support browsing the web of interconnected pages of hypertext markup language ( HTML ) and associated resources required to render a web page . As a result of its widespread availability , it has been used for exposing application sever interfaces , commonly referred to as web service APIs .
Describe the derivation , origin or history of the system . The objective is to understand the brief evolutionary context of this technology .
HTTP originated in 1990-92 with informal drafts describing it as a protocol for collaborative hypermedia applications . HTTP / 1.0 appeared as an IETF informational RFC in 1996 . HTTP / 1.1 appeared as a draft standard in 1999 . It expanded upon the TCP / IP binding , and was finalized in 2014 . HTTP / 2 appeared in 2015 . It further optimized the TCP / IP binding , while preserving the semantics . Describe the options and variants from the original generic description of the technology .
None .
Estimate the technology maturity , state of development and condition relative to perfection . How refined are the connectivity concepts , requirements and demonstrated capabilities ? Is the technology consistent and uniform ?
HTTP is a mature technology . It forms the basis of the World Wide Web .
Describe whether the connectivity technology has been in use for long enough that most of its initial faults and inherent problems have been removed or reduced ; how easy is it to use for both non-experts and professionals ? Has there been a reduction in the rate of new breakthrough advances related to it ?
Yes , HTTP is stable . HTTP / 1 . x is widely deployed . Toolkits for writing HTTP clients are available in nearly all the popular programming languages . There is a large selection of HTTP server implementations to choose from . Open-source and proprietary implementations are available .
List the relevant organizational bodies developing , coordinating , promulgating , revising , amending , reissuing , interpreting or otherwise producing technical standards and guidelines intended to address the needs of the base of affected adopters .
Internet Engineering Task Force ( IETF )
Is it an open standard ? Who can participate ? Are the specifications freely available ? Are open source implementations available ? Does it require any single component from any single vendor ?
Yes , HTTP is an open standard managed by the IETF . Participation in the standards process is open to all . There are no annual dues and the IETF standards are available free of charge . The specifications process is open to participation by both vendors and users .
Open source and commercial implementations are available . No , the specifications do not rely on any single component from any single vendor .
IIC : PUB : G5 : V1.0 : PB : 20170228 - 95 -