|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 1945 (1996)
|
|
Title:
|
Hypertext Transfer Protocol - HTTP/1.0. T. Berners-Lee, R. Fielding, H. Frystyk. May 1996.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
The HTTP/SOAP binding (Annex C) can use HTTP 1.0 or HTTP 1.1 as a carrier protocol.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1945
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in May 1996 (http://www.ietf.org/rfc/rfc1945.txt). The status is INFORMATIONAL.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in May 1996 (http://www.ietf.org/rfc/rfc1945.txt). The status is INFORMATIONAL.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
HTTP is used is many Internet communications and referenced by documents providing extensions and also in Fast Web Services (X.892).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., Torrey, D., and B. Alberti, "The Internet Gopher Protocol: A Distributed Document Search and Retrieval Protocol", RFC 1436, University of Minnesota, March 1993./
[2] Berners-Lee, T., "Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web", RFC 1630, CERN, June 1994./
[3] Berners-Lee, T., and D. Connolly, "Hypertext Markup Language - 2.0", RFC 1866, MIT/W3C, November 1995./
[4] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, CERN, Xerox PARC, University of Minnesota, December 1994./
[5] Borenstein, N., and N. Freed, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies", RFC 1521, Bellcore, Innosoft, September 1993./
[6] Braden, R., "Requirements for Internet hosts - Application and Support", STD 3, RFC 1123, IETF, October 1989./
[7] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, UDEL, August 1982./
[8] F. Davis, B. Kahle, H. Morris, J. Salem, T. Shen, R. Wang, J. Sui, and M. Grinbaum. "WAIS Interface Protocol Prototype Functional Specification." (v1.5), Thinking Machines Corporation, April 1990./
[9] Fielding, R., "Relative Uniform Resource Locators", RFC 1808, UC Irvine, June 1995./
[10] Horton, M., and R. Adams, "Standard for interchange of USENET Messages", RFC 1036 (Obsoletes RFC 850), AT&T Bell Laboratories, Center for Seismic Studies, December 1987./
[11] Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A Proposed Standard for the Stream-Based Transmission of News", RFC 977, UC San Diego, UC Berkeley, February 1986./
[12] Postel, J., "Simple Mail Transfer Protocol." STD 10, RFC 821, USC/ISI, August 1982./
[13] Postel, J., "Media Type Registration Procedure." RFC 1590, USC/ISI, March 1994./
[14] Postel, J., and J. Reynolds, "File Transfer Protocol (FTP)", STD 9, RFC 959, USC/ISI, October 1985./
[15] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1700, USC/ISI, October 1994./
[16] Sollins, K., and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, MIT/LCS, Xerox Corporation, December 1994./
[17] US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986./
[18] ISO-8859. International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets --/
Part 1: Latin alphabet No. 1, ISO 8859-1:1987./
Part 2: Latin alphabet No. 2, ISO 8859-2, 1987./
Part 3: Latin alphabet No. 3, ISO 8859-3, 1988./
Part 4: Latin alphabet No. 4, ISO 8859-4, 1988./
Part 5: Latin/Cyrillic alphabet, ISO 8859-5, 1988./
Part 6: Latin/Arabic alphabet, ISO 8859-6, 1987./
Part 7: Latin/Greek alphabet, ISO 8859-7, 1987./
Part 8: Latin/Hebrew alphabet, ISO 8859-8, 1988./
Part 9: Latin alphabet No. 5, ISO 8859-9, 1990./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
