|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
RFC - Internet Standard (Legacy Stream) - Also Known As STD 7
|
|
3.
|
Justification for the specific reference:
|
|
|
The TCP/IP binding described in Annex A uses the TCP protocol for transmission and reception of messages between BIP endpoints.
|
|
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=793
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been approved in September 1981. Updated by RFC 3168, RFC 6093, RFC 6528, RFC 1122.
Obsoletes RFC 761. Errata exists.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 0793 was published in September 1981. It is the USA APRA DoD Standard Transmission Control Protocol (TCP) used in many computer networks including the Internet. It is published by the IETF at http://www.ietf.org/rfc/rfc0793.txt.
It was updated by: RFCs 1122, 3168, 6093, 6528
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 793 is a component of the basic suite of internet protocols and standards and is widely used by the internet community. Updated by RFC 3168, RFC 6093, RFC 6528, RFC 1122; Obsoletes RFC 761
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Cerf, V., and R. Kahn, "A Protocol for Packet Network/
Intercommunication", IEEE Transactions on Communications,/
Vol. COM-22, No. 5, pp 637-648, May 1974./
[2] Postel, J. (ed.), "Internet Protocol - DARPA Internet Program/
Protocol Specification", RFC 791, USC/Information Sciences/
Institute, September 1981./
[3] Dalal, Y. and C. Sunshine, "Connection Management in Transport/
Protocols", Computer Networks, Vol. 2, No. 6, pp. 454-473,/
December 1978./
[4] Postel, J., "Assigned Numbers", RFC 790, USC/Information Sciences/
Institute, September 1981.
|
|
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".
|
