|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
Relevant for H.248.64 Back-to-Back IP Host mode.
|
|
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=1122
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since October 1989. It is a standard that is widely used in the internet community.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 1121 was published in October, 1989. It is an Internet Standard. Updated by RFCs 1349, 4379, 5884, 6093, 6298. Errata Exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This RFC is one of a pair that defines and discusses the requirements for Internet host software. RFC 1123 covers the application and support protocols; this RFC covers the communication protocol layers: link layer, IP layer, and transport layer.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
|
|
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".
|
