|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC. Obsoleted by RFC 7826.
|
|
3.
|
Justification for the specific reference:
|
|
|
The reference to RFC 2326 is needed in Rec. E.804 to define the Real Time Streaming 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=2326
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since April 1998 and is very widely used as video on demand control protocol. Obsoleted by RFC 7826. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2326 was published in April 1998. It is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.ietf.org/rfc/rfc5000
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Schulzrinne, H., "RTP profile for audio and video conferences with minimal control", RFC 1890, January 1996./
[2] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, "Hypertext transfer protocol - HTTP/1.1", RFC 2068, January 1997./
[3] Yergeau, F., Nicol, G., Adams, G., and M. Duerst, "Internationalization of the hypertext markup language", RFC 2070, January 1997./
[4] Bradner, S., "Key words for use in RFCs to indicate requirement levels", BCP 14, RFC 2119, March 1997./
[5] ISO/IEC, "Information technology - generic coding of moving pictures and associated audio information - part 6: extension for digital storage media and control," Draft International Standard ISO 13818-6, International Organization for Standardization ISO/IEC JTC1/SC29/WG11, Geneva, Switzerland, Nov. 1995./
[6] Handley, M., and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998./
[7] Franks, J., Hallam-Baker, P., and J. Hostetler, "An extension to HTTP: digest access authentication", RFC 2069, January 1997./
[8] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980./
[9] Hinden, B. and C. Partridge, "Version 2 of the reliable data protocol (RDP)", RFC 1151, April 1990./
[10] Postel, J., "Transmission control protocol", STD 7, RFC 793, September 1981./
[11] H. Schulzrinne, "A comprehensive multimedia control architecture for the Internet," in Proc. International Workshop on Network and Operating System Support for Digital Audio and Video (NOSSDAV), (St. Louis, Missouri), May 1997./
[12] International Telecommunication Union, "Visual telephone systems and equipment for local area networks which provide a non-guaranteed quality of service," Recommendation H.323, Telecommunication Standardization Sector of ITU, Geneva, Switzerland, May 1996./
[13] McMahon, P., "GSS-API authentication method for SOCKS version 5", RFC 1961, June 1996./
[14] J. Miller, P. Resnick, and D. Singer, "Rating services and rating systems (and their machine readable descriptions)," Recommendation REC-PICS-services-961031, W3C (World Wide Web Consortium), Boston, Massachusetts, Oct. 1996./
[15] J. Miller, T. Krauskopf, P. Resnick, and W. Treese, "PICS label distribution label syntax and communication protocols," Recommendation REC-PICS-labels-961031, W3C (World Wide Web Consortium), Boston, Massachusetts, Oct. 1996./
[16] Crocker, D. and P. Overell, "Augmented BNF for syntax specifications: ABNF", RFC 2234, November 1997./
[17] Braden, B., "Requirements for internet hosts - application and support", STD 3, RFC 1123, October 1989./
[18] Elz, R., "A compact representation of IPv6 addresses", RFC 1924, April 1996./
[19] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform resource locators (URL)", RFC 1738, December 1994./
[20] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998./
[21] Braden, B., "T/TCP - TCP extensions for transactions functional specification", RFC 1644, July 1994./
[22] W. R. Stevens, TCP/IP illustrated: the implementation, vol. 2. Reading, Massachusetts: Addison-Wesley, 1994./
[23] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: a transport protocol for real-time applications", RFC 1889, January 1996./
[24] Fielding, R., "Relative uniform resource locators", RFC 1808, June 1995.
|
|
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.
|
|
