|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
This protocol is used for transport of data through the interface defined by this 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=1901
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This is an Experimental Standard developed in 1996
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This technology is widely used in the Cable Television industry.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Structure of Management Information for Version 2/
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,/
January 1996./
/
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Textual Conventions for Version 2 of the Simple/
Network Management Protocol (SNMPv2)", RFC 1903, January 1996./
/
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Conformance Statements for Version 2 of the Simple/
Network Management Protocol (SNMPv2)", RFC 1904, January 1996./
/
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Protocol Operations for Version 2 of the Simple/
Network Management Protocol (SNMPv2)", RFC 1905, January 1996./
/
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Transport Mappings for Version 2 of the Simple/
Network Management Protocol (SNMPv2)", RFC 1906, January 1996./
/
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Management Information Base for Version 2 of the/
Simple Network Management Protocol (SNMPv2)", RFC 1907,/
January 1996./
/
[7] Rose, M., and K. McCloghrie, "Structure and Identification of/
Management Information for TCP/IP-based internets", STD 16, RFC/
1155, May 1990./
/
[8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,/
RFC 1212, March 1991./
/
[9] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple Network/
Management Protocol", STD 15, RFC 1157, SNMP Research, Performance/
Systems International, MIT Laboratory for Computer Science, May/
1990./
/
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and/
S. Waldbusser, "Coexistence between Version 1 and Version 2 of the/
Internet-standard Network Management Framework", RFC 1908,/
January 1996./
/
[11] Information processing systems - Open Systems Interconnection -/
Specification of Abstract Syntax Notation One (ASN.1),/
International Organization for Standardization. International/
Standard 8824, (December, 1987).
|
|
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
|
|
