|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
Rec. ITU-T X.519 references IETF RFC 1738 for using representing an IDM-style communications endpoint by its IP address and its port number
|
|
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=1738
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 1738 was published in December 1994 and is a standards track RFC. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 1738 was published in December 1994 and is a standards track RFC. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 1738 is referenced in H.323, H.225.0, and Annex K/H.323.
|
|
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. URL:ftp://ds.internic.net/rfc/rfc1436.txt /
[2] Anklesaria, F., Lindner, P., McCahill, M., Torrey, D., Johnson, D., and B. Alberti, "Gopher+: Upward compatible enhancements to the Internet Gopher protocol", University of Minnesota, July 1993. URL:ftp://boombox.micro.umn.edu/pub/gopher/gopher_protocol /Gopher+/Gopher+.txt /
[3] 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. URL:ftp://ds.internic.net/rfc/rfc1630.txt /
[4] Berners-Lee, T., "Hypertext Transfer Protocol (HTTP)", CERN, November 1993. URL:ftp://info.cern.ch/pub/www/doc/http-spec.txt.Z /
[5] Braden, R., Editor, "Requirements for Internet Hosts -- Application and Support", STD 3, RFC 1123, IETF, October 1989. URL:ftp://ds.internic.net/rfc/rfc1123.txt/
[6] Crocker, D. "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, UDEL, April 1982. URL:ftp://ds.internic.net/rfc/rfc822.txt/
[7] Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R., Sui, J., and M. Grinbaum, "WAIS Interface Protocol Prototype Functional Specification", (v1.5), Thinking Machines Corporation, April 1990. URL:ftp://quake.think.com/pub/wais/doc/protspec.txt /
[8] Horton, M. and R. Adams, "Standard For Interchange of USENET Messages", RFC 1036, AT&T Bell Laboratories, Center for Seismic Studies, December 1987. URL:ftp://ds.internic.net/rfc/rfc1036.txt /
[9] Huitema, C., "Naming: Strategies and Techniques", Computer Networks and ISDN Systems 23 (1991) 107-110./
[10] Kahle, B., "Document Identifiers, or International Standard Book Numbers for the Electronic Age", 1991. URL:ftp://quake.think.com/pub/wais/doc/doc-ids.txt/
[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. URL:ftp://ds.internic.net/rfc/rfc977.txt/
[12] Kunze, J., "Functional Requirements for Internet Resource Locators", Work in Progress, December 1994. URL:ftp://ds.internic.net/internet-drafts /draft-ietf-uri-irl-fun-req-02.txt/
[13] Mockapetris, P., "Domain Names - Concepts and Facilities", STD 13, RFC 1034, USC/Information Sciences Institute, November 1987. URL:ftp://ds.internic.net/rfc/rfc1034.txt /
[14] Neuman, B., and S. Augart, "The Prospero Protocol", USC/Information Sciences Institute, June 1993. URL:ftp://prospero.isi.edu/pub/prospero/doc /prospero-protocol.PS.Z/
[15] Postel, J. and J. Reynolds, "File Transfer Protocol (FTP)", STD 9, RFC 959, USC/Information Sciences Institute, October 1985. URL:ftp://ds.internic.net/rfc/rfc959.txt /
[16] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, MIT/LCS, Xerox Corporation, December 1994. URL:ftp://ds.internic.net/rfc/rfc1737.txt/
[17] St. Pierre, M, Fullton, J., Gamiel, K., Goldman, J., Kahle, B., Kunze, J., Morris, H., and F. Schiettecatte, "WAIS over Z39.50-1988", RFC 1625, WAIS, Inc., CNIDR, Thinking Machines Corp., UC Berkeley, FS Consulting, June 1994. URL:ftp://ds.internic.net/rfc/rfc1625.txt/
[18] Yeong, W. "Towards Networked Information Retrieval", Technical report 91-06-25-01, Performance Systems International, Inc. URL:ftp://uu.psi.com/wp/nir.txt, June 1991./
[19] Yeong, W., "Representing Public Archives in the Directory",Work in Progress, November 1991./
[20] "Coded Character Set -- 7-bit American Standard Code for Information Interchange", ANSI X3.4-1986.
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
