|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3584 (2003)
|
|
Title:
|
Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
|
|
|
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=3584
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes: 2576
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
9.1. Normative References/
/
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification/
of Management Information for TCP/IP-based internets",/
STD 16, RFC 1155, May 1990./
/
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and C. Davin,/
"Simple Network Management Protocol (SNMP)", STD 15, RFC/
1157, May 1990./
/
[RFC1212] Rose, M. and K. McCloghrie, Eds., "Concise MIB/
Definitions", STD 16, RFC 1212, March 1991./
/
[RFC1215] Rose, M., "A Convention for Defining Traps for use with/
the SNMP", RFC 1215, March 1991./
/
[RFC1303] McCloghrie, K. and M. Rose, "A Convention for Describing/
SNMP-based Agents", RFC 1303, February 1992./
/
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,/
"Introduction to Community-based SNMPv2", RFC 1901,/
January 1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,/
"Structure of Management Information Version 2 (SMIv2)",/
RFC 2578, STD 58, 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./
/
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An/
Architecture for Describing Simple Network Management/
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,/
December 2002./
/
[RFC3412] Case, J., Harrington, D., Presuhn, R. and B. Wijnen,/
"Message Processing and Dispatching for the Simple/
Network Management Protocol (SNMP)", STD 62, RFC 3412,/
December 2002./
/
[RFC3413] Levi, D., Meyer, P. and B. Stewart, "Simple Network/
Management Protocol (SNMP) Applications", STD 62, RFC/
3413, December 2002./
/
[RFC3414] Blumenthal, U. and B. Wijnen, "The User-Based Security/
Model (USM) for Version 3 of the Simple Network/
Management Protocol (SNMP)", STD 62, RFC 3414, December/
2002./
/
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based/
Access Control Model (VACM) for the Simple Network/
Management Protocol (SNMP)", STD 62, RFC 3415, December/
2002./
/
[RFC3416] Presuhn, R., Ed., "Version 2 of the Protocol Operations/
for the Simple Network Management Protocol (SNMPv2)", STD/
62, RFC 3416, December 2002./
/
[RFC3417] Presuhn, R., Ed., "Transport Mappings for Version 2 of/
the Simple Network Management Protocol (SNMPv2)", STD 62,/
RFC 3417, December 2002./
/
[RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for/
Version 2 of the Simple Network Management Protocol/
(SNMP)", STD 62, RFC 3418, December 2002./
/
[ASN1] 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
|
|
