[Search] [txt|pdf|bibtex] [Tracker] [WG] [Email] [Nits]

Versions: 00 01                                                         
Internet Draft                                                   A. Smith
Expires December 1999                                    Extreme Networks
draft-ietf-issll-is802-sbm-mib-00.txt                          R. Pabbati
                                                                Microsoft
                                                                June 1999

        Definitions of Managed Parameters for SBM network nodes


                          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.
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time.  It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or
"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.

Copyright (C) The Internet Society (1999).  All Rights Reserved.


Abstract

This memo includes a list of manageable parameters for RSVP/SBM server
implementations. These are in addition to those already described in RFC
2206 and RFC 2213. Specifically, it describes parameters for control of
the base signaling protocols themselves, as well as some of the
admission control decisions.  These definitions are not intended to be
exhaustive but they have been identified as useful for practical
implementations.










Smith                     Expires December 1999         [Page 1]


Internet Draft               SBM Parameters                    June 1999


1.  Introduction

SBM server components of the ISSLL/IS802 architecture require some
configuration parameters for operational use.  These fall into 2 main
areas: configuration of RSVP protocol operation and configuration of
SBM-specific parts.  For the former, RFC 2206 and RFC 2213 cover some
configuration operations as SNMP MIBS and some additional objectsd are
provided here.



1.1.  Relationship to Other MIBs

1.1.1.  Relationship to the 'system' group

In MIB-II, the 'system' group is defined as being mandatory for all
systems such that each managed entity contains one instance of each
object in the 'system' group.  Thus, those objects apply to the entity
as a whole irrespective of whether the entity's sole functionality is
the SBM protocol or whether this is only a subset of the entity's
functionality.


1.1.2.  Relation to Interfaces MIB

The Interface MIB Evolution [INTERFACEMIB], requires that any MIB which
is an adjunct of the Interface MIB, clarify specific areas within the
Interface MIB.  These areas were intentionally left vague in the
Interface MIB Evolution to avoid over-constraining the MIB, thereby
precluding management of certain media-types.


1.1.3.

SBM interfaces which are capable of handling outgoing sessions should
each be represented by an entry in the per-interface tables of this MIB
[INTSERVMIB]. <ed: see issue (2) below>.

SBM interfaces which are capable of handling outgoing Guaranteed Service
sessions should be represented by an entry in intSrvGuaranteedIfTable
[INTSERVGSMIB. This entry can be used to characterise the delay
parameters that the SBM will use in its admission control algorithms.








Smith                     Expires December 1999         [Page 2]


Internet Draft               SBM Parameters                    June 1999


2.  Editorial information

<this section will be removed before publication>


2.1.  Open Issues


(1)  Should we include DCLASS as well as TCLASS config info here?

(2)  How to represent more detailed e.g. per-queue/per-class
     information. We could use the per-interface tables from
     RFC2213/RFC2214 int-serv MIBs but we would then need one of these
     per queue per interface. this might need ifStackTable to group them
     together. Could also try to use the intSrvflowQueue object for
     this.

(3)  Should we allow creation of new SBM instances? MIB currently only
     allows configuration of existing SBMs and assumes that the agent
     will create SBM instances appropriately.



3.  Definitions for SBM Server MIB


SBM-SERVER-MIB DEFINITIONS ::= BEGIN

-- -------------------------------------------------------------
-- -------------------------------------------------------------

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32
        FROM SNMPv2-SMI
    TruthValue
        FROM SNMPv2-TC
    InterfaceIndex
        FROM IF-MIB
    SnmpAdminString
        FROM SNMP-FRAMEWORK-MIB
    MODULE-COMPLIANCE, OBJECT-GROUP
        FROM SNMPv2-CONF
    BurstSize, BitRate, MessageSize
        FROM INTEGRATED-SERVICES-MIB;






Smith                     Expires December 1999         [Page 3]


Internet Draft               SBM Parameters                    June 1999


--
--    REFERENCE
--        "Resource Reservation Protocol (RSVP) - Version 1 Functional
--                       Specification", RFC 2205"
--
--        "SBM (Subnet Bandwidth Manager): A Protocol for Admission
--        Control over IEEE 802-style Networks" (draft-ietf-issll-sbm-08.txt)

sbmMIB MODULE-IDENTITY
    LAST-UPDATED "9906100000Z"
    ORGANIZATION "Extreme Networks, Inc."
    CONTACT-INFO
        "       Andrew Smith
         Phone: +1 408 579 2821
         Email: andrew@extremenetworks.com"

        "       Ramesh Pabbati
         Phone: +1 425 936 9438
         Email: rameshpa@microsoft.com"
    DESCRIPTION
        "The SBM MIB module"
    ::= { xxx 1 }

sbmMIBObjects OBJECT IDENTIFIER ::= { sbmMIB 1 }


-- -------------------------------------------------------------
-- SBM Server Parameters
-- -------------------------------------------------------------

sbmConfigTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF SbmConfigEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of configuration information per SBM instance. This might be
        e.g. per-subnet for a shared LAN or per-network-interface for a switched
        LAN. For a full-duplex switched LAN it might only represent the transmit
        direction: in this case the receive controls will have no effect.
        Entries in this table are created automatically by the agent when
        a new SBM entity is created e.g. by addition of new physical hardware
        or creation of a new subnet."
    ::= { sbmMIBObjects 1 }

sbmConfigEntry OBJECT-TYPE





Smith                     Expires December 1999         [Page 4]


Internet Draft               SBM Parameters                    June 1999


    SYNTAX      SbmConfigEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of SBM protocol configuration variables for a given SBM instance."
    INDEX   { sbmIndex }
    ::= { sbmConfigTable 1 }

SbmConfigEntry ::=
    SEQUENCE {
        sbmIndex           Integer32,
        sbmDescription     SnmpAdminString,
        sbmIfIndex         InterfaceIndex,
        sbmEnable          TruthValue,
        sbmDsbmRefreshInterval   Integer32,
        sbmDsbmDeadInterval      Integer32,
        sbmDsbmElectionPriority  INTEGER,
        sbmDsbmMaxNonResvTxBucketRate     BitRate,
        sbmDsbmMaxNonResvTxBucketDepth    MessageSize,
        sbmDsbmMaxNonResvTxPeakRate       BitRate,
        sbmDsbmMaxNonResvTxMinPolicedSize MessageSize,
        sbmDsbmMaxNonResvTxMaxPacketSize  MessageSize
    }

sbmIndex OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "An integer representing a particular SBM instance."
    ::= { sbmConfigEntry 1 }

sbmDescription OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "A description of this SBM instance."
    ::= { sbmConfigEntry 2 }

sbmIfIndex OBJECT-TYPE
    SYNTAX      InterfaceIndex
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION





Smith                     Expires December 1999         [Page 5]


Internet Draft               SBM Parameters                    June 1999


        "The interface index representing the domain of
        control of this SBM instance: e.g. this might be a physical
        interface on a switch device or it might be a subnet represented by
        a propVirtual(53) interface entry. A value of 0 represents an SBM
        instance that has no association to any one particular ifTable entry."
    ::= { sbmConfigEntry 3 }

sbmEnable  OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Enable SBM processing of messages."
    DEFVAL      { true }
    ::= { sbmConfigEntry 4 }

sbmDsbmRefreshInterval OBJECT-TYPE
    SYNTAX      Integer32
    UNITS       "seconds"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "DSBM refresh interval."
    DEFVAL      { 5 }
    ::= { sbmConfigEntry 5 }

sbmDsbmDeadInterval OBJECT-TYPE
    SYNTAX      Integer32
    UNITS       "seconds"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "DSBM Election dead time."
    DEFVAL      { 15 }
    ::= { sbmConfigEntry 6 }

sbmDsbmElectionPriority OBJECT-TYPE
    SYNTAX      INTEGER (0..255)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Election bid for this SBM to become DSBM."
    DEFVAL      { 4 }
    ::= { sbmConfigEntry 7 }






Smith                     Expires December 1999         [Page 6]


Internet Draft               SBM Parameters                    June 1999


sbmDsbmMaxNonResvTxBucketRate
    SYNTAX      BitRate
    UNITS       "bits per second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Maximum Bucket rate that can be sent with out a reservation. This is one
        of the parameters of the effective Tspec that senders are allowed to use
        before any reservation is in place."
    REFERENCE   "RFC2210 section 3.1"
    ::= { sbmConfigEntry 8 }

sbmDsbmMaxNonResvTxBucketDepth
    SYNTAX      BurstSize
    UNITS       "bytes"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Maximum Bucket Depth that can be sent with out a reservation. This is one
        of the parameters of the effective Tspec that senders are allowed to use
        before any reservation is in place."
    REFERENCE   "RFC2210 section 3.1"
    ::= { sbmConfigEntry 9 }

sbmDsbmMaxNonResvTxPeakRate
    SYNTAX      BitRate
    UNITS       "bits per second"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Maximum Peak rate that can be sent with out a reservation. This is
        one of the parameters of the effective Tspec that senders are
        allowed to use before any reservation is in place."
    REFERENCE   "RFC2210 section 3.1"
    ::= { sbmConfigEntry 10 }

sbmDsbmMaxNonResvTxMinPolicedSize
    SYNTAX      MessageSize
    UNITS       "bytes"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Minimum Policed size that can be sent with out a reservation.
        This is one of the parameters of the effective Tspec that senders are
        allowed to use before any reservation is in place."





Smith                     Expires December 1999         [Page 7]


Internet Draft               SBM Parameters                    June 1999


    REFERENCE   "RFC2210 section 3.1"
    ::= { sbmConfigEntry 11 }

sbmDsbmMaxNonResvTxMaxPacketSize
    SYNTAX      MessageSize
    UNITS       "bytes"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Maximum packet length that can be sent with out a reservation.
        This is one of the parameters of the effective Tspec that senders are
        allowed to use before any reservation is in place."
    REFERENCE   "RFC2210 section 3.1"
    ::= { sbmConfigEntry 12 }


sbmTrafficClassConfigTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF SbmTrafficClassConfigEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of parameters for configuring the characteristics of
        the mapping of sessions into layer-2 traffic classes."
    ::= { sbmMIBObjects 2 }

sbmTrafficClassConfigEntry OBJECT-TYPE
    SYNTAX      SbmTrafficClassConfigEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A set of RSVP protocol configuration variables for a given SBM instance."
    INDEX   { sbmIndex, sbmTrafficClass }
    ::= { sbmTrafficClassConfigTable 1 }

SbmTrafficClassConfigEntry ::=
    SEQUENCE {
        sbmTrafficClass          INTEGER (0..7),
        sbmDelayBoundTarget      Integer32,
        sbmTrafficClassEnabled   TruthValue
    }

sbmTrafficClass OBJECT-TYPE
    SYNTAX      INTEGER (0..7)
    MAX-ACCESS  read-write
    STATUS      current





Smith                     Expires December 1999         [Page 8]


Internet Draft               SBM Parameters                    June 1999


    DESCRIPTION
        "Traffic Class (802.1p user_priority)."
    ::= { sbmTrafficClassConfigEntry 1 }

sbmDelayBoundTarget OBJECT-TYPE
    SYNTAX      Integer32
    UNITS       "micro-seconds"
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Target delay bound on flows admitted to this class.
        A value of 0 indicates that there is no quantitative delay bound
        target associated with this class."
    ::= { sbmTrafficClassConfigEntry 2 }

sbmTrafficClassEnabled OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Enable admission of flows to this class."
    ::= { sbmTrafficClassConfigEntry 3 }

-- -------------------------------------------------------------
-- RSVP Configuration Parameters
-- -------------------------------------------------------------

sbmRsvpConfigTable OBJECT-TYPE
    SYNTAX  SEQUENCE OF SbmRsvpConfigEntry
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
        "A table of configuration information per SBM instance. This might be
        e.g. per-subnet for a shared LAN or per-network-interface for a
        switched LAN. For a full-duplex switched LAN it might only represent
        the transmit direction: in this case the receive controls will have
        no effect."
    ::= { sbmMIBObjects 3 }

sbmRsvpConfigEntry OBJECT-TYPE
    SYNTAX  SbmRsvpConfigEntry
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
        "A set of RSVP protocol configuration variables for a given SBM instance."





Smith                     Expires December 1999         [Page 9]


Internet Draft               SBM Parameters                    June 1999


    INDEX   { sbmIndex }
    ::= { sbmRsvpConfigTable 1 }

SbmRsvpConfigEntry ::=
    SEQUENCE {
        sbmRsvpCopsEnabled           TruthValue,
        sbmRsvpSenderPolicyEnabled   TruthValue,
        sbmRsvpReceiverPolicyEnabled TruthValue,
    }

sbmRsvpCopsEnabled OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Enable outsourcing of local policy decisions via the COPS protocol."
    DEFVAL      { false }
    ::= { sbmRsvpConfigEntry 1 }

sbmRsvpSenderPolicyEnabled OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Enable processing of RSVP policy objects in PATH messages."
    DEFVAL      { false }
    ::= { sbmRsvpConfigEntry 2 }

sbmRsvpReceiverPolicyEnabled OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Enable processing of RSVP policy objects in RESV messages."
    DEFVAL      { false }
    ::= { sbmRsvpConfigEntry 3 }


-- -------------------------------------------------------------
-- SBM statistics
-- -------------------------------------------------------------

sbmStatsTable OBJECT-TYPE
    SYNTAX  SEQUENCE OF SbmStatsEntry
    MAX-ACCESS  not-accessible





Smith                     Expires December 1999        [Page 10]


Internet Draft               SBM Parameters                    June 1999


    STATUS  current
    DESCRIPTION
        "A table of statistics per SBM instance. This might be e.g. per-subnet
        for a shared LAN or per-network-interface for a switched LAN. For a
        full-duplex switched LAN it might only represent the transmit
        direction: in this case the receive statistics may be zero."
    ::= { sbmMIBObjects 4 }

sbmStatsEntry OBJECT-TYPE
    SYNTAX  SbmStatsEntry
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
        "A set of SBM protocol statistics for a given SBM instance."
    INDEX   { sbmIndex }
    ::= { sbmStatsTable 1 }

SbmStatsEntry ::=
    SEQUENCE {
        sbmStatsSbmSentBytes              Counter32,
        sbmStatsSbmReceivedBytes          Counter32,
        sbmStatsReceivedRsvpPathMsgs      Counter32,
        sbmStatsReceivedRsvpResvMsgs      Counter32,
        sbmStatsReceivedRsvpPathErrMsgs   Counter32,
        sbmStatsReceivedRsvpResvErrMsgs   Counter32,
        sbmStatsReceivedRsvpPathTearMsgs  Counter32,
        sbmStatsReceivedRsvpResvTearMsgs  Counter32,
        sbmStatsReceivedRsvpConfirmMsgs   Counter32,
        sbmStatsReceivedRsvpBadMsgs       Counter32,
        sbmStatsSentRsvpPathMsgs          Counter32,
        sbmStatsSentRsvpResvMsgs          Counter32,
        sbmStatsSentRsvpPathErrMsgs       Counter32,
        sbmStatsSentRsvpResvErrMsgs       Counter32,
        sbmStatsSentRsvpPathTearMsgs      Counter32,
        sbmStatsSentRsvpResvTearMsgs      Counter32,
        sbmStatsSentRsvpConfirmMsgs       Counter32,
        sbmStatsAdmissionControlFailures  Counter32,
        sbmStatsInPolicyControlFailures   Counter32,
        sbmStatsOutPolicyControlFailures  Counter32,
        sbmStatsOtherFailures             Counter32,
        sbmStatsInBlockadeStateResvs      Counter32,
        sbmStatsResvTimeOuts              Counter32,
        sbmStatsPathTimeOuts              Counter32,
        sbmStatsReceiveFailsBigMsg        Counter32,
        sbmStatsSendFailsBigMsg           Counter32,





Smith                     Expires December 1999        [Page 11]


Internet Draft               SBM Parameters                    June 1999


        sbmStatsReceiveFailsNoResource    Counter32,
        sbmStatsSendFailsNoResource       Counter32,
        sbmStatsActiveOutgoingFlows       Counter32,
        sbmStatsAllocatedOutgoingBits     Counter32,
        sbmStatsMaxAllocatedBandwidthBits Counter32
    }

sbmStatsSbmSentBytes OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "bytes"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 1 }

sbmStatsSbmReceivedBytes OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "bytes"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 2 }

sbmStatsReceivedRsvpPathMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 3 }

sbmStatsReceivedRsvpResvMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 4 }

sbmStatsReceivedRsvpPathErrMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current





Smith                     Expires December 1999        [Page 12]


Internet Draft               SBM Parameters                    June 1999


    DESCRIPTION
        ""
    ::= { sbmStatsEntry 5 }

sbmStatsReceivedRsvpResvErrMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 6 }

sbmStatsReceivedRsvpPathTearMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 7 }

sbmStatsReceivedRsvpResvTearMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 8 }

sbmStatsReceivedRsvpConfirmMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 9 }

sbmStatsReceivedRsvpBadMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Bad syntax or semantics."
    ::= { sbmStatsEntry 10 }

sbmStatsSentRsvpPathMsgs OBJECT-TYPE





Smith                     Expires December 1999        [Page 13]


Internet Draft               SBM Parameters                    June 1999


    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 11 }

sbmStatsSentRsvpResvMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 12 }

sbmStatsSentRsvpPathErrMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 13 }

sbmStatsSentRsvpResvErrMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 14 }

sbmStatsSentRsvpPathTearMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 15 }

sbmStatsSentRsvpResvTearMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""





Smith                     Expires December 1999        [Page 14]


Internet Draft               SBM Parameters                    June 1999


    ::= { sbmStatsEntry 16 }

sbmStatsSentRsvpConfirmMsgs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 17 }

sbmStatsAdmissionControlFailures OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 18 }

sbmStatsInPolicyControlFailures OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 19 }

sbmStatsOutPolicyControlFailures OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 20 }

sbmStatsOtherFailures OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 21 }

sbmStatsInBlockadeStateResvs OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only





Smith                     Expires December 1999        [Page 15]


Internet Draft               SBM Parameters                    June 1999


    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 22 }

sbmStatsResvTimeOuts OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 23 }

sbmStatsPathTimeOuts OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 24 }

sbmStatsReceiveFailsBigMsg OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 25 }

sbmStatsSendFailsBigMsg OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 26 }

sbmStatsReceiveFailsNoResource OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 27 }






Smith                     Expires December 1999        [Page 16]


Internet Draft               SBM Parameters                    June 1999


sbmStatsSendFailsNoResource OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 28 }

sbmStatsActiveOutgoingFlows OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 29 }

sbmStatsAllocatedOutgoingBits OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "bps"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 30 }

sbmStatsMaxAllocatedBandwidthBits OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "bps"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        ""
    ::= { sbmStatsEntry 31 }

-- -------------------------------------------------------------
-- Conformance Information
-- -------------------------------------------------------------

sbmConformance OBJECT IDENTIFIER ::= { sbmMIB 2 }

sbmGroups OBJECT IDENTIFIER ::= { sbmConformance 1 }
sbmCompliances OBJECT IDENTIFIER ::= { sbmConformance 2 }

-- -------------------------------------------------------------
-- units of conformance





Smith                     Expires December 1999        [Page 17]


Internet Draft               SBM Parameters                    June 1999


-- -------------------------------------------------------------

    sbmSbmConfigGroup    OBJECT-GROUP
        OBJECTS {
            sbmIfIndex, sbmEnable, sbmDsbmRefreshInterval,
            sbmDsbmDeadInterval, sbmDsbmElectionPriority,
            sbmTrafficClass, sbmDelayBoundTarget,
            sbmTrafficClassEnabled
        }
        STATUS     current
        DESCRIPTION
            "A collection of objects providing per-SBM control over operation
            of the SBM protocol."
        ::= { sbmGroups 1 }

    sbmRsvpConfigGroup    OBJECT-GROUP
        OBJECTS {
            sbmRsvpEnabled, sbmRsvpCopsEnabled,
            sbmRsvpSenderPolicyEnabled, sbmRsvpReceiverPolicyEnabled,
            sbmRsvpGsDelay, sbmRsvpGsSlack
        }
        STATUS     current
        DESCRIPTION
            "A collection of objects providing per-SBM control over operation
            of the RSVP protocol."
        ::= { sbmGroups 2 }

    sbmSbmStatisticsGroup    OBJECT-GROUP
        OBJECTS {
            sbmStatsSbmSentBytes, sbmStatsSbmReceivedBytes,
            sbmStatsReceivedRsvpPathMsgs,
            sbmStatsReceivedRsvpResvMsgs,
            sbmStatsReceivedRsvpPathErrMsgs,
            sbmStatsReceivedRsvpResvErrMsgs,
            sbmStatsReceivedRsvpPathTearMsgs,
            sbmStatsReceivedRsvpResvTearMsgs,
            sbmStatsReceivedRsvpConfirmMsgs,
            sbmStatsSentRsvpPathMsgs, sbmStatsSentRsvpResvMsgs,
            sbmStatsSentRsvpPathErrMsgs, sbmStatsSentRsvpResvErrMsgs,
            sbmStatsSentRsvpPathTearMsgs,
            sbmStatsSentRsvpResvTearMsgs,
            sbmStatsSentRsvpConfirmMsgs,
            sbmStatsAdmissionControlFailures,
            sbmStatsInPolicyControlFailures,
            sbmStatsOutPolicyControlFailures, sbmStatsOtherFailures,





Smith                     Expires December 1999        [Page 18]


Internet Draft               SBM Parameters                    June 1999


            sbmStatsInBlockadeStateResvs, sbmStatsResvTimeOuts,
            sbmStatsPathTimeOuts, sbmStatsReceiveFailsBigMsg,
            sbmStatsSendFailsBigMsg, sbmStatsReceiveFailsNoResource,
            sbmStatsSendFailsNoResource,
            sbmStatsActiveOutgoingFlows,
            sbmStatsAllocatedOutgoingBits,
            sbmStatsMaxAllocatedBandwidthBits
        }
        STATUS     current
        DESCRIPTION
            "A collection of objects providing per-SBM statistics of RSVP
            protocol operations."
        ::= { sbmGroups 3 }

-- -------------------------------------------------------------
-- compliance statements
-- -------------------------------------------------------------

    sbmCompliance MODULE-COMPLIANCE
        STATUS  current
        DESCRIPTION
            "The compliance statement for SNMP entities
             which manage SBM protocol entities."

        MODULE  -- this module
        MANDATORY-GROUPS
        {
            sbmSbmConfigGroup,
            sbmRsvpConfigGroup,
            sbmSbmStatisticsGroup
        }

        OBJECT      sbmRsvpEnabled
        MIN-ACCESS  read-only
        DESCRIPTION
            "Read-only access is allowed."

         ::= { sbmCompliances 1 }

END

4.  References








Smith                     Expires December 1999        [Page 19]


Internet Draft               SBM Parameters                    June 1999


[RSVP]
     Braden, R., L. Zhang, S. Berson, S. Herzog, S. Jamin, "Resource
     Reservation Protocol (RSVP) - Version 1 Functional Specification",
     RFC 2205, September 1997

[IS802]
     Ghanwani, A., Pace, W., Srinivasan, V., Smith, A., Seaman, M., "A
     Framework for Providing Integrated Services Over Shared and
     Switched LAN Technologies", Internet Draft, April 1999.
     http://www.ietf.org/internet-drafts/draft-ietf-issll-
     is802-framework-06.txt

[SBM]
     Yavatkar, R., Hoffman, D., Bernet, Y., Baker, F., Speer, M., "SBM
     (Subnet Bandwidth Manager): A Protocol for Admission Control over
     IEEE 802-style Networks", Internet Draft, April 1999.
     http://www.ietf.org/internet-drafts/draft-ietf-issll-sbm-08.txt

[IS802MAP]
     Seaman, M., Smith, A., Crawley, E., "Integrated Service Mappings on
     IEEE 802 Networks", Internet Draft, Cmetric, Extreme Networks,
     Argon Networks, June 1999.  http://www.ietf.org/internet-
     drafts/draft-ietf-issll-is802-svc-mapping-04.txt

[RSVPMIB]
     Baker, F., Krawczyk, J., Sastry, A., "RSVP Management Information
     Base using SMIv2", RFC 2206, Sepember 1997

[INTSERVMIB]
     Baker, F., Krawczyk, J., Sastry, A., "Integrated Services
     Management Information Base using SMIv2", RFC 2213, Sepember 1997

[ARCH]
     Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
     Describing SNMP Management Frameworks", RFC 2571, April 1999

[V1PROTO]
     Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network
     Management Protocol", RFC 1157, May 1990.

[V1SMI]
     Rose, M., and K. McCloghrie, "Structure and Identification of
     Management Information for TCP/IP-based Internets", RFC 1155, May
     1990






Smith                     Expires December 1999        [Page 20]


Internet Draft               SBM Parameters                    June 1999


[V1CONCISE]
     Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
     March 1991

[V1TRAPS]
     M. Rose, "A Convention for Defining Traps for use with the SNMP",
     RFC 1215, March 1991

[V2SMI]
     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.

[V2TC]
     McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
     and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC
     2579, April 1999.

[V2CONFORM]
     McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
     and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC
     2580, April 1999.

[V2COMMUNITY]
     Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction
     to Community-based SNMPv2", RFC 1901, January 1996.

[V2TRANS]
     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.

[V2PROTO]
     Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol
     Operations for Version 2 of the Simple Network Management Protocol
     (SNMPv2)", RFC 1905, January 1996.

[V3INTRO]
     Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to
     Version 3 of the Internet-standard Network Management Framework",
     RFC 2570, April 1999.

[V3MPC]
     Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
     Processing and Dispatching for the Simple Network Management





Smith                     Expires December 1999        [Page 21]


Internet Draft               SBM Parameters                    June 1999


     Protocol (SNMP)", RFC 2572, April 1999.

[V3USM]
     Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM)
     for Version 3 of the Simple Network Management Protocol (SNMPv3)",
     RFC 2574, April 1999.

[V3APPS]
     Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573,
     April 1999.

[V3VACM]
     Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
     Control Model for the Simple Network Management Protocol (SNMP)",
     RFC 2575, April 1999.

[ASN1]
     Information processing systems - Open Systems Interconnection -
     Specification of Abstract Syntax Notation One (ASN.1),
     International Organization for Standardization, International
     Standard 8824, December 1987.

[ASN1BER]
     Information processing systems - Open Systems Interconnection -
     Specification of Basic Encoding Rules for Abstract Notation One
     (ASN.1), International Organization for Standardization,
     International Standard 8825, December 1987.

[PROCESS]
     Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
     RFC 2026, October 1996.



5.  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.

SNMPv1 by itself is not a secure environment.  Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET





Smith                     Expires December 1999        [Page 22]


Internet Draft               SBM Parameters                    June 1999


(read/change/create/delete) the objects in this MIB.

It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework.  Specifically, the use of the User-
based Security Model [USM] and the View-based Access Control Model
[VACM] is recommended.

It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them.



6.  Authors' Addresses

     Andrew Smith
     Extreme Networks
     3585 Monroe St.
     Santa Clara CA 95051
     USA
     Phone: +1 408 579 2821
     EMail: andrew@extremenetworks.com

     Ramesh Pabbati
     Microsoft
     1 Microsoft Way
     Redmond, WA 98052
     USA
     Phone: +1 206 936 9438
     Email: rameshpa@microsoft.com



















Smith                     Expires December 1999        [Page 23]


Internet Draft               SBM Parameters                    June 1999


   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 implmentation 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.

   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.

























Smith                     Expires December 1999        [Page 24]