|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
This specification defines TFTP protocol widely used in the world, and constitutes an essential part of the Recommendation.
Since this specification consists of huge number of pages, making reference saves a lot of paper in the printing process.
|
|
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=1350
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since July 1992.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 1350 was published in July 1992. It is currently an approved standard, STD33.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 1350 was extended by the following RFCs, RFC1782, RFC1783,
RFC1784, RFC1785, RFC2347, RFC2348 and RFC2349.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] USA Standard Code for Information Interchange, USASI X3.4-1968./
/
[2] Postel, J., "User Datagram Protocol," RFC 768, USC/Information/
Sciences Institute, 28 August 1980./
/
[3] Postel, J., "Telnet Protocol Specification," RFC 764,/
USC/Information Sciences Institute, June, 1980./
/
[4] Braden, R., Editor, "Requirements for Internet Hosts --/
Application and Support", RFC 1123, USC/Information Sciences/
Institute, October 1989.
|
|
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):
|
|
|
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
|
