Internet Engineering Task Force Hans Sjostrand INTERNET DRAFT Ericsson Expires September 2000 Joachim Burkle Marconi Balaji Srinivasan Cplane March 2000 Definitions of Managed Objects for the General Switch Management Protocol (GSMP) < draft-ietf-gsmp-mib-01.txt > Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Distribution of this document is unlimited. Please send comments to the General Switch Management Protocol (gsmp) Working Group, . Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Sjostrand, et.al. Expires September 2000 [Page 1] Internet Draft GSMP MIB March 2000 Abstract This memo defines a portion of the Management Information Base (MIB)for use with network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP). Table of Contents 1. Introduction...................................................... 3 2. The SNMP Management Framework .................................... 3 3. Structure of the MIB.............................................. 5 3.1 MIB groups.................................................... 5 3.1.1 GSMP Session group ..................................... 5 3.1.2 GSMP Encapsulation group ............................... 5 3.1.3 The GSMP Notifications Group ........................... 5 4. GSMP MIB Definitions.............................................. 5 5. Revision History................................................. 17 5.1 Design considerations ....................................... 17 5.1.1 Switch partitions ..................................... 17 5.1.2 Protocol mib........................................... 17 5.1.3 VSCE/VSE/VSC/VS relationships ......................... 17 5.1.4 IANA and ATM TC ....................................... 17 5.2 Changes from < draft-ietf-gsmp-mib-00.txt > ................. 17 6. Acknowledgments.................................................. 17 7. References....................................................... 18 8. Security Considerations ......................................... 19 9. Authors' Addresses............................................... 20 10. Full Copyright Statement ....................................... 20 Sjostrand, et.al. Expires September 2000 [Page 2] Internet Draft GSMP MIB March 2000 1. Introduction This memo defines a portion of the Management Information Base (MIB)for use with network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP). [RFC1987]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 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 components: * 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 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 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 described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and 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 is described in STD 15, RFC 1157 [RFC1157]. A second set of operations and associated PDU formats is described in 1905 [RFC1905]. Sjostrand, et.al. Expires September 2000 [Page 3] Internet Draft GSMP MIB March 2000 * A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. Sjostrand, et.al. Expires September 2000 [Page 4] Internet Draft GSMP MIB March 2000 3. Structure of the MIB This mib describes the managed object needed for GSMPv3. The basic idea behind the design is to make it as simple as possible to be easily implementable and also provide a extendable base for future additions. 3.1 MIB groups 3.1.1 GSMP Session group The GSMP session table provides a way to define, configure and monitor new GSMP session. Each row in the GSMP sesion table will have a correspnding row in the session statistics table. The sessino is defined by a Virtual Switch Controller Entity and Virtual Switch Entity pair. Prior to a successful row createion in the session table a row in the encapsulation table must be defined. Which encapsulation type is used for the specific session is defined in the session type object. If Ethernet is specified, no extra encasulation info is needed. 3.1.2 GSMP Encapsulation group The ATM Encapsulation Table and the TCP/IP Encapsulation Table provides a way to configure information that are encapsulation specific. No config data needed if Ethernet encapsulation is used. The encasulation data is further specified in [25]. 3.1.3 The GSMP Notifications Group This is currently empty, but could be extended with notifications as defined in [24]. 4. GSMP MIB Definitions GSMP-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, Unsigned32, experimental, Counter32,IpAddress FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF Sjostrand, et.al. Expires September 2000 [Page 5] Internet Draft GSMP MIB March 2000 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeInterval FROM SNMPv2-TC InterfaceIndex FROM IF-MIB ; gsmpMIB MODULE-IDENTITY LAST-UPDATED "20000310Z" -- 10 March 2000 ORGANIZATION "General Switch Management Protocol (gsmp) Working Group" CONTACT-INFO "Hans Sjostrand (hans.Sjostrand@etx.ericsson.se) Ericsson Joachim Burkle (joachim.buerkle@marconicomms.com) Marconi Communications GmbH Balaji Srinivasan (balaji@cplane.com) CPlane Inc." DESCRIPTION "This MIB contains managed object definitions for the General Switch Management Protocol, GSMP, version 3" ::= { experimental 9877 } -- to be assigned --**************************************************************** -- GSMP Textual Conventions --**************************************************************** gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 2 } gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 } --**************************************************************** -- IANA Textual Conventions --**************************************************************** GsmpServiceModelType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) The enumerations are described as: default(0) -- Indicates use of the default GSMP model qGSMP(1) -- Indicates use of IEEE qGSMP model 2 - 200 -- Reserved 201 - 255 -- Experimental Requests for new values should be made to IANA via Sjostrand, et.al. Expires September 2000 [Page 6] Internet Draft GSMP MIB March 2000 email (iana@iana.org)." SYNTAX INTEGER { default(0), qGSMP(1) } --**************************************************************** -- ATM MIB Textual Conventions --**************************************************************** AtmVpIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The VPI value for a VPL. The value VPI=0 is not used for a VPL not associated with a VCL. For ATM UNIs supporting VPCs the VPI value ranges from 1 to 255. For ATM UNIs supporting VCCs the VPI value ranges from 0 to 255. The maximum VPI value cannot exceed the value allowable by atmInterfaceMaxVpiBits defined in ATM-MIB." SYNTAX Unsigned32 (0..4095) AtmVcIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The VCI value for a VCL. The maximum VCI value cannot exceed the value allowable by atmInterfaceMaxVciBits defined in ATM-MIB." SYNTAX Unsigned32 (0..65535) --**************************************************************** -- GSMP Encap Objects --**************************************************************** -- -- GSMP Session table -- gsmpSessionTable OBJECT-TYPE SYNTAX SEQUENCE OF GsmpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents the sessions between VSCE and VSE pairs. " ::= { gsmpObjects 1 } gsmpSessionEntry OBJECT-TYPE SYNTAX GsmpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Sjostrand, et.al. Expires September 2000 [Page 7] Internet Draft GSMP MIB March 2000 "An entry in the table showing the data for a specific VSCE and VSE pair." INDEX { gsmpSessionVsceId, gsmpSessionVseId } ::= { gsmpSessionTable 1 } GsmpSessionEntry ::= SEQUENCE { gsmpSessionVsceId OCTET STRING, gsmpSessionVseId OCTET STRING, gsmpSessionEncapType INTEGER, gsmpSessionVersion INTEGER, gsmpSessionMaxVsceVersion INTEGER, gsmpSessionMaxVseVersion INTEGER, gsmpSessionServiceModel GsmpServiceModelType, gsmpSessionSwitchType Unsigned32, gsmpSessionTimer Unsigned32, gsmpSessionState INTEGER, gsmpSessionVsceName OCTET STRING, gsmpSessionVseName OCTET STRING, gsmpSessionVscePort Unsigned32, gsmpSessionVsePort Unsigned32, gsmpSessionVsceInstance Unsigned32, gsmpSessionVseInstance Unsigned32, gsmpSessionPartitionId OCTET STRING, gsmpSessionRowStatus RowStatus } gsmpSessionVsceId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(6)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Virtual Switch Controller Entity Id is a 48- bit quantity that is unique within the operational context of the device. A 48-bit IEEE 802 MAC address, if available, may be used for the VCSE Id." ::= { gsmpSessionEntry 1 } gsmpSessionVseId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(6)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Virtual Switch Entity Id is a 48- bit quantity that is unique within the operational context of the device. A 48-bit IEEE 802 MAC address, if available, may be used for the VSE Id." ::= { gsmpSessionEntry 2 } gsmpSessionEncapType OBJECT-TYPE SYNTAX INTEGER { ethernet(1), atm(2), Sjostrand, et.al. Expires September 2000 [Page 8] Internet Draft GSMP MIB March 2000 tcpip(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The encapsulation used to for this session. If atm, a corresponing row in the gsmpAtmEncapTable has to be defined. If tcpip, a corresponing row in the gsmpTcpIpEncapTable has to be defined." ::= { gsmpSessionEntry 3 } gsmpSessionVersion OBJECT-TYPE SYNTAX INTEGER { version1-1(1), version2-0(2), version3(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The version number of the GSMP protocol being used in this session. The version is negotiated by the adjacency protocol." ::= { gsmpSessionEntry 4 } gsmpSessionMaxVsceVersion OBJECT-TYPE SYNTAX INTEGER { version1-1(1), version2-0(2), version3(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum version number supported by the VSCE" ::= { gsmpSessionEntry 5 } gsmpSessionMaxVseVersion OBJECT-TYPE SYNTAX INTEGER { version1-1(1), version2-0(2), version3(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum version number supported by the VSE" ::= { gsmpSessionEntry 6 } gsmpSessionServiceModel OBJECT-TYPE SYNTAX GsmpServiceModelType MAX-ACCESS read-only STATUS current Sjostrand, et.al. Expires September 2000 [Page 9] Internet Draft GSMP MIB March 2000 DESCRIPTION "Represents the service model used in the session QoS Configuration type." ::= { gsmpSessionEntry 7 } gsmpSessionSwitchType OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A 16-bit field allocated by the manufacturer of the switch. The Switch Type identifies the product. When the Switch Type is combined with the OUI from the VSE Name the product is uniquely identified." ::= { gsmpSessionEntry 8 } gsmpSessionTimer OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The timer specifies the nominal time between periodic adjacency protocol messages. It is a constant for the duration of a GSMP session. The timer is specified in units of 100ms." ::= { gsmpSessionEntry 9 } gsmpSessionState OBJECT-TYPE SYNTAX INTEGER { null(1), synsent(2), synrcvd(3), estab(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The state the session currently is in. " ::= { gsmpSessionEntry 10 } gsmpSessionVsceName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the VSCE as advertised in the adjacency message. The most first three octets must be an Organisationally Unique Identifier (OUI) that identifies the manufacturer of the VSCE. If the VSCE name is unknown then this will be null. " ::= {gsmpSessionEntry 11} gsmpSessionVseName OBJECT-TYPE Sjostrand, et.al. Expires September 2000 [Page 10] Internet Draft GSMP MIB March 2000 SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the VSE as advertised in the adjacency message. The most first three octets must be an Organisationally Unique Identifier (OUI) that identifies the manufacturer of the VSE. If the VSE name is unknown then this will be null. " ::= {gsmpSessionEntry 12} gsmpSessionVscePort OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The local port number for the Virtual Switch Controller Entity. If the local port number for the VSCE is unknown, e.g because it's on the far side of the link and noy yet announced this object is zero." ::= { gsmpSessionEntry 13 } gsmpSessionVsePort OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The local port number for the Virtual Switch Entity. If the local port number for the VSE is unknown, e.g because it's on the far side of the link and noy yet announced this object is zero." ::= { gsmpSessionEntry 14 } gsmpSessionVsceInstance OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The instance number for the Virtual Switch Controller Entity. If the instance number for the VSCE is unknown, e.g because it's on the far side of the link and noy yet announced this object is zero." ::= { gsmpSessionEntry 15 } gsmpSessionVseInstance OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The instance number for the Virtual Switch Entity. If the instance number for the VSE is unknown, e.g because it's on the far side of the link and noy yet announced this object is zero." Sjostrand, et.al. Expires September 2000 [Page 11] Internet Draft GSMP MIB March 2000 ::= { gsmpSessionEntry 16 } gsmpSessionPartitionId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The Id for the specific switch partition that this session is concerned with. The format of the Partition ID is not defined in GSMP. If desired, the Partition ID can be divided into multiple sub-identifiers within a single partition." ::= { gsmpSessionEntry 17 } gsmpSessionRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted using the RowStatus convention." ::= { gsmpSessionEntry 18 } -- -- GSMP Session stat table -- gsmpSessionStatTable OBJECT-TYPE SYNTAX SEQUENCE OF GsmpSessionStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the statistics collected for the different sessions. " ::= { gsmpObjects 2 } gsmpSessionStatEntry OBJECT-TYPE SYNTAX GsmpSessionStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table contains statistics data for a specific session." AUGMENTS { gsmpSessionEntry } ::= { gsmpSessionStatTable 1 } GsmpSessionStatEntry ::= SEQUENCE { gsmpSessionStatUptime Counter32, gsmpSessionStatSendmessages Counter32, gsmpSessionStatFailiureIndication Counter32, gsmpSessionStatReceivedmessages Counter32, gsmpSessionStatReceivedFailiure Counter32 Sjostrand, et.al. Expires September 2000 [Page 12] Internet Draft GSMP MIB March 2000 } gsmpSessionStatUptime OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The time in seconds that the session has been in established state." ::= { gsmpSessionStatEntry 1 } gsmpSessionStatSendmessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of messages that has been sent in this session." ::= { gsmpSessionStatEntry 2 } gsmpSessionStatFailiureIndication OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of messages that has been sent with a failiure indication in this session." ::= { gsmpSessionStatEntry 3 } gsmpSessionStatReceivedmessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of messages that has been received in this session." ::= { gsmpSessionStatEntry 4 } gsmpSessionStatReceivedFailiure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of messages that has been received in this session with a failiure indication." ::= { gsmpSessionStatEntry 5 } -- -- GSMP ATM Encapsulation Table -- gsmpAtmEncapTable OBJECT-TYPE SYNTAX SEQUENCE OF GsmpAtmEncapEntry MAX-ACCESS not-accessible STATUS current Sjostrand, et.al. Expires September 2000 [Page 13] Internet Draft GSMP MIB March 2000 DESCRIPTION "This table contains the atm encapsulation data for the VSCE and VSE pairs that uses atm as encapsulation." ::= { gsmpObjects 3 } gsmpAtmEncapEntry OBJECT-TYPE SYNTAX GsmpAtmEncapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table showing the encapsulation data for a specific VSCE and VSE pair." INDEX { gsmpSessionVsceId, gsmpSessionVseId } ::= { gsmpAtmEncapTable 1 } GsmpAtmEncapEntry ::= SEQUENCE { gsmpAtmEncapIfIndex InterfaceIndex, gsmpAtmEncapVpi Unsigned32, gsmpAtmEncapVci Unsigned32 } gsmpAtmEncapIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION " The interface index for the virtual channel over which the GSMP session is established over, i.e the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer" ::= { gsmpAtmEncapEntry 1 } gsmpAtmEncapVpi OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION " The VPI value for the virtual channel over which the GSMP session is established over, i.e the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer" DEFVAL { 0 } ::= { gsmpAtmEncapEntry 2 } gsmpAtmEncapVci OBJECT-TYPE SYNTAX AtmVcIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION " The VCI value for the virtual channel over which the GSMP session is established over, i.e the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer" Sjostrand, et.al. Expires September 2000 [Page 14] Internet Draft GSMP MIB March 2000 DEFVAL { 15 } ::= { gsmpAtmEncapEntry 3 } -- -- GSMP TCP/IP Encapsulation Table -- gsmpTcpIpEncapTable OBJECT-TYPE SYNTAX SEQUENCE OF GsmpTcpIpEncapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the atm encapsulation data for the VSCE and VSE pairs that uses atmTCP/IP as encapsulation." ::= { gsmpObjects 4 } gsmpTcpIpEncapEntry OBJECT-TYPE SYNTAX GsmpTcpIpEncapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table showing the encapsulation data for a specific VSCE and VSE pair." INDEX { gsmpSessionVsceId, gsmpSessionVseId } ::= { gsmpTcpIpEncapTable 1 } GsmpTcpIpEncapEntry ::= SEQUENCE { gsmpTcpIpEncapAddress IpAddress, gsmpTcpIpPortNumber Unsigned32 } gsmpTcpIpEncapAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP address of the GSMP session peer." ::= { gsmpTcpIpEncapEntry 1 } gsmpTcpIpPortNumber OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The TCP port number used for the TCP session to the GSMP peer. The defaut value of this object is the well know GSMP port number. " ::= { gsmpTcpIpEncapEntry 2 } --****************************************************************** Sjostrand, et.al. Expires September 2000 [Page 15] Internet Draft GSMP MIB March 2000 -- Module Compliance Statement --****************************************************************** gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 } gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 } gsmpModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for agents that support the GSMP MIB." MODULE -- this module MANDATORY-GROUPS { gsmpSessionGroup } ::= { gsmpCompliances 1 } -- units of conformance gsmpSessionGroup OBJECT-GROUP OBJECTS { gsmpSessionEncapType, gsmpSessionVersion, gsmpSessionMaxVsceVersion, gsmpSessionMaxVseVersion, gsmpSessionServiceModel, gsmpSessionSwitchType, gsmpSessionTimer, gsmpSessionState, gsmpSessionVsceName, gsmpSessionVseName, gsmpSessionVscePort, gsmpSessionVsePort, gsmpSessionVsceInstance, gsmpSessionVseInstance, gsmpSessionPartitionId, gsmpSessionRowStatus, gsmpSessionStatUptime, gsmpSessionStatSendmessages, gsmpSessionStatFailiureIndication, gsmpSessionStatReceivedmessages, gsmpSessionStatReceivedFailiure, gsmpAtmEncapIfIndex, gsmpAtmEncapVpi, gsmpAtmEncapVci, gsmpTcpIpEncapAddress, gsmpTcpIpPortNumber } STATUS current DESCRIPTION "Objects that apply to all GSMP implementations." ::= { gsmpGroups 1 } END Sjostrand, et.al. Expires September 2000 [Page 16] Internet Draft GSMP MIB March 2000 5. Revision History This section should be removed when this document is published as an RFC. 5.1 Design considerations 5.1.1 Switch partitions The management of switch partitions falls outside of the management of GSMP, so this is excluded from the GSMP mib. 5.1.2 Protocol mib The GSMP mib is only a protocool mib. It contains object to manage the GSMP protocol. It does not provide any information learned via the protocool, such as "all ports config" information. This is I belive another mib. 5.1.3 VSCE/VSE/VSC/VS relationships The relationships between Virtual Switch Controller Entity, Virtual Switch Entity, Virtual Switch Controller and Virtual Switch are not included in the mib in this version. However, it could very well be included or be considered as an freestanding mib. The advice of the GSMP working group will be guiding in the question. 5.1.4 IANA and ATM TC These Textual conventions will be taken out and imported into the GSMP mib before the mib is published as RFC. The IANA definitina are not yet published and the ATM definitino are there for educational purpuses. 5.2 Changes from < draft-ietf-gsmp-mib-00.txt > Mib totaly remade :-) 6. Acknowledgments The author would like to thank Avri Doria for valuable input and comments. Sjostrand, et.al. Expires September 2000 [Page 17] Internet Draft GSMP MIB March 2000 7. References [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [RFC1906] 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. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999 [RFC1905] 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. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999 Sjostrand, et.al. Expires September 2000 [Page 18] Internet Draft GSMP MIB March 2000 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs.", RFC 2434, IBM, Maxware, October 1998 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General Switch Management Protocol Specification," Version 1.1, RFC 1987, August 1996. [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General Switch Management Protocol Specification," Version 2.0, RFC 2397, March 1998. [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. [RFC2233] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, November 1997. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, Harvard University, March 1997 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, Harvard University, October 1996 [24] Worster, Doria, Hellstrand, Sundell, "General Switch Management Protocol", work in progress, January 2000 [25] Tom Worster, "GSMP Packet Encapsulations for ATM, Ethernet and TCP", work in progress, January 2000 8. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. Sjostrand, et.al. Expires September 2000 [Page 19] Internet Draft GSMP MIB March 2000 Assuming that secure network management (such as SNMP v3) is implemented, the objects represented in this MIB do not pose a threat to the security of the network. 9. Authors' Addresses Hans Sjostrand Ericsson Business Unit Datacom Networks and IP Services S-126 25 Stockholm, Sweden Phone: +46 8 719 9960 Email: hans.sjostrand@etx.ericsson.se Joachim Buerkle Marconi Communications GmbH Dept. Systems Engineering - Wireline Access Systems Gerberstrasse 33 D-71522 Backnang, Germany Phone: +49 7191 13 4602 Email: joachim.buerkle@marconicomms.com Balaji Srinivasan CPlane Inc. 5150 El Camino Real Suite B-31 Los Altos, CA 94022 Phone +1 650 938 8066 ext 103 Email: balaji@cplane.com 10. Full Copyright Statement Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. Sjostrand, et.al. Expires September 2000 [Page 20] Internet Draft GSMP MIB March 2000 The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Sjostrand, et.al. Expires September 2000 [Page 21]