Definitions of Managed Objects for the General Switch Management Protocol (GSMP)
RFC - Proposed Standard (June 2002; No errata)
Was draft-ietf-gsmp-mib (gsmp WG)
plain text html pdf htmlized bibtex
RFC 3295 (Proposed Standard)
Scott Bradner
IESG note
Responsible: RFC Editor
Network Working Group                                       H. Sjostrand
Request for Comments: 3295                                   ipUnplugged
Category: Standards Track                                     J. Buerkle
B. Srinivasan
Cplane
Definitions of Managed Objects for
the General Switch Management Protocol (GSMP)
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2002).  All Rights Reserved.
for the use with the network management protocols in the Internet
community.  In particular, it describes managed objects for the
General Switch Management Protocol (GSMP).
1.  Introduction............................................. 2
2.  The SNMP Management Framework............................ 2
3.  Structure of the MIB..................................... 3
3.1 Overview............................................. 3
3.2 Scope................................................ 4
3.3 MIB guideline........................................ 4
3.4 MIB groups........................................... 5
3.4.1 GSMP Switch Controller group................... 5
3.4.2 GSMP Switch group.............................. 6
3.4.3 GSMP Encapsulation groups...................... 6
3.4.4 GSMP General group............................. 7
3.4.5 The GSMP Notifications Group................... 7
3.5 Textual Conventions.................................  8
4.  GSMP MIB Definitions....................................  9
5.  Acknowledgments......................................... 42
Sjostrand, et. al.          Standards Track                     [Page 1]
RFC 3295                        GSMP MIB                       June 2002
6.  References.............................................. 42
7.  Intellectual Property Rights............................ 44
8.  Security Considerations................................. 45
9.  Authors' Addresses...................................... 46
10. Full Copyright Statement................................ 47
for use with network management protocols in the Internet community.
In particular, it describes managed objects for the General Switch
Management Protocol (GSMP).
document are to be interpreted as described in RFC 2119 [RFC2119].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
*  An overall architecture, described in RFC 2571 [RFC2571].
*  Mechanisms for describing and naming objects and events for the
purpose of management.  The first version of this Structure of
Management Information (SMI) is called SMIv1 and is described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212], and RFC
1215 [RFC1215].  The second version, called SMIv2, is described in
STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579], and RFC
2580[RFC2580].
*  Message protocols for transferring management information.  The
first version of the SNMP message protocol is called SNMPv1 and is
described in STD 15, RFC 1157 [RFC1157].  A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and is described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906].  The third version of the message protocol
is called SNMPv3 and is described in RFC 1906 [RFC1906], RFC 2572
[RFC2572], and RFC 2574 [RFC2574].
*  Protocol operations for accessing management information.  The
first set of protocol operations and associated PDU formats are
described in STD 15, RFC 1157 [RFC1157].  A second set of
operations and associated PDU formats are described in 1905
*  A set of fundamental applications described in RFC 2573 [RFC2573],