|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
The specification is employed in the gathering and use of information necessary for the implementation of recommendation.
|
|
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=4113
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
good quality
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
stable
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes: 2454, 2013
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,/
August 1980./
/
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,/
"Structure of Management Information Version 2 (SMIv2)",/
STD 58, RFC 2578, April 1999./
/
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,/
"Textual Conventions for SMIv2", STD 58, RFC 2579, April/
1999./
/
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,/
"Conformance Statements for SMIv2", STD 58, RFC 2580,/
April 1999./
/
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the/
Simple Network Management Protocol (SNMP)", STD 62, RFC/
3418, December 2002./
/
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J./
Schoenwaelder, "Textual Conventions for Internet Network/
Addresses", RFC 4001, February 2005./
|
|
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". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs
|
|
