Internet Draft A. Smith
Expires April 2000 Extreme Networks
draft-ietf-issll-is802-sbm-mib-01.txt R. Pabbati
Microsoft
October 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.
This document is a product of the IETF's Integrated Services over
Specific Lower- Layers (ISSLL) Working Group. 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 April 2000 [Page 1]
Internet Draft SBM Parameters October 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 objects are
provided here.
This memo includes a MIB module in a manner that is compliant to the
SNMPv2 SMI [V2SMI].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in an Architecture for
Describing SNMP Management Frameworks [ARCH].
o 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
RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215
[V1TRAPS]. The second version, called SMIv2, is described in
STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58,
RFC 2580 [V2CONFORM].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [V1PROTO]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the
message protocol is called SNMPv3 and described in RFC1906
[V2TRANS], Message Processing and Dispatching [V3MPC] and User-
based Scurity Model [V3USM].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [V1PROTO]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [V2PROTO].
Smith Expires April 2000 [Page 2]
Internet Draft SBM Parameters October 1999
o A set of fundamental applications described in SNMPv3
Applications [V3APPS] and the view-based access control
mechanism described in View-based Access Control Model [V3VACM].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [V3INTRO].
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.
3. Structure of SBM Server MIB
Objects in this MIB are arranged into groups. Each group is organized
as a set of related objects. The overall structure is described below.
3.1. sbmSbmConfigGroup
This group contains objects for configuration of SBM operation. The
sbmConfigTable includes the reporting of some hard-coded parameters
of an SBM implementation and some current state variables. The
sbmTrafficClassConfigTable controls the admission of RSVP sessions
into IEEE 802 traffic classes.
3.2. sbmRsvpConfigGroup
This group contains objects that control operation of the RSVP
protocol for each SBM instance. The sbmRsvpConfigTable controls
behaviour related to policy control on RSVP sessions.
3.3. sbmSbmStatisticsGroup and sbmSbmHCStatisticsGroup
These groups contains objects in the sbmStatsTable that represent
protocol statistics for the RSVP/SBM protocol. The
Smith Expires April 2000 [Page 3]
Internet Draft SBM Parameters October 1999
sbmSbmHCStatisticsGroup includes objects that only need to be
implemented for high speed interfaces where 32-bit counters are
insufficient to represent the values.
3.4. Relationship to Other MIBs
3.4.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.
3.4.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.
3.4.3. Relation to Integrated Services MIBs
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.
4. Editorial information
<this section will be removed before publication>
Smith Expires April 2000 [Page 4]
Internet Draft SBM Parameters October 1999
4.1. Open Issues resolved in this draft
(1) Should we include DCLASS as well as TCLASS config info here? NO.
(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). NO.
4.2. Other changes in this draft
(4) Modified descriptive text for tables e.g. sbmConfigTable to
indicate what entries are expected for what types of SBM. Added new
variable sbmType to describe whether this SBM instance is for a
whole subnet, for half-duplex interface (both directions) or full-
duplex interface (one direction only).
(5) Added references to IEEE 802.1D traffic classes.
(6) Added DEFVAL "enabled" for sbmTrafficClassEnabled.
(7) Added descriptions for stats counters.
(9) Added sbmDsbmElectionState to report the current DSBM election
state and sbmDsbmLastStateChange, a timestamp for when it got
there.
(10) sbmStatsActiveOutgoingFlows, sbmStatsAllocatedOutgoingBits,
sbmStatsMaxAllocatedBandwidthBits: changed from Counter32 to
Gauge32.
(11) Added 64-bit versions of sbmStatsAllocatedOutgoingBits,
sbmStatsMaxAllocatedBandwidthBits with appropriate conformance
clauses. These rely on HCRMON's Gauge64 TC.
(12) Merged sbmStatsInPolicyControlFailures and
sbmStatsOutPolicyControlFailures into
sbmStatsPolicyControlFailures.
Miscellaneous editorial fixes.
Smith Expires April 2000 [Page 5]
Internet Draft SBM Parameters October 1999
4.3. Still Open Issues
(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.
(8) Should counters be zeroed whenever a SBM enters I_AM_DSBM state?
(Propose: NO)
Smith Expires April 2000 [Page 6]
Internet Draft SBM Parameters October 1999
5. Definitions for SBM Server MIB
SBM-SERVER-MIB DEFINITIONS ::= BEGIN
-- -------------------------------------------------------------
-- -------------------------------------------------------------
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Integer32, Gauge32
FROM SNMPv2-SMI
RmonGauge64
FROM HC-RMON-MIB
TimeStamp, 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;
--
-- 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 "9910190000Z"
ORGANIZATION "IETF Integrated Services over Specific Lower-Layers
Working Group"
CONTACT-INFO
" John Wroclawski (Co-chair of ISSLL WG)
Phone: +1 617 253 7885
Email: jtw@lcs.mit.edu
Eric Crawley (Co-chair of ISSLL WG)
Phone: +1 978 486 0665 x125
Email: esc@argon.com
Smith Expires April 2000 [Page 7]
Internet Draft SBM Parameters October 1999
Editor: Andrew Smith
Phone: +1 408 579 2821
Email: andrew@extremenetworks.com
Editor: Ramesh Pabbati
Phone: +1 425 936 9438
Email: rameshpa@microsoft.com"
DESCRIPTION
"The SBM MIB module"
REVISION "9910190000Z"
DESCRIPTION "This version published as draft-ietf-issll-is80-sbm-mib-01."
::= { 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. There may be
one instance per subnet for a shared LAN. For a switched LAN there
may be once instance per LAN segment/network-interface. For a full-
duplex switched LAN segment the SBM instance only represents 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
SYNTAX SbmConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of SBM protocol configuration variables for a given
Smith Expires April 2000 [Page 8]
Internet Draft SBM Parameters October 1999
SBM instance."
INDEX { sbmIndex }
::= { sbmConfigTable 1 }
SbmConfigEntry ::=
SEQUENCE {
sbmIndex Integer32,
sbmDescription SnmpAdminString,
sbmType INTEGER,
sbmIfIndex InterfaceIndex,
sbmEnable TruthValue,
sbmDsbmRefreshInterval Integer32,
sbmDsbmDeadInterval Integer32,
sbmDsbmElectionPriority INTEGER,
sbmDsbmElectionState INTEGER,
sbmDsbmLastStateChange TimeStamp,
sbmDsbmMaxNonResvTxBucketRate BitRate,
sbmDsbmMaxNonResvTxBucketDepth BurstSize,
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 }
sbmType OBJECT-TYPE
SYNTAX INTEGER {
sbmTypeOther(1),
sbmTypeUnknown(2),
sbmTypeSubnet(3),
sbmTypeHalfDuplexInterface(4),
Smith Expires April 2000 [Page 9]
Internet Draft SBM Parameters October 1999
sbmTypeFullDuplexTxInterface(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indicator of the type of LAN segment or domain of control
of this SBM instance.
A value of sbmTypeSubnet(3) indicates that this SBM instance
performs RSVP admission control for a complete IP subnet
that is reached through the interface indicated by sbmIfIndex.
A value of sbmTypeHalfDuplexInterface(4) indicated that this
SBM instance performs RSVP admission control for just the LAN
segment that is reached through the interface indicated by
sbmIfIndex which is a half-duplex segment with other potential
transmitters on it.
A value of sbmTypeFullDuplexTxInterface(5) indicates that this
SBM instance performs RSVP admission control for just the
transmit direction of the full-duplex LAN segment that is
reached through the interface indicated by sbmIfIndex: this
segment, by definition, will have no other transmitters on it.
In this case, the receive statistics in sbmStatsTable may be
invalid.
A value of sbmTypeUnknown(2) indicates that the domain of control
for this SBM instance is not yet known. A value of sbmTypeOther(1)
indicates that this SBM instance has some other domain of control."
::= { sbmConfigEntry 3 }
sbmIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 4 }
sbmEnable OBJECT-TYPE
SYNTAX TruthValue
Smith Expires April 2000 [Page 10]
Internet Draft SBM Parameters October 1999
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control the SBM processing of messages. This SBM will only
attempt to become DSBM and actually control allocation if it
wins the DSBM election procedure, as controlled by the following
parameters. If this SBM does not win that procedure but this flag
is still true(1) then it will act as a client in the SBM protocol
and will forward RSVP/SBM messages to the elected DSBM.
If this flag is false(2) then this node will act as a normal RSVP
protocol entity."
DEFVAL { true }
::= { sbmConfigEntry 5 }
sbmDsbmRefreshInterval OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"DSBM refresh interval."
DEFVAL { 5 }
::= { sbmConfigEntry 6 }
sbmDsbmDeadInterval OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"DSBM Election dead time."
DEFVAL { 15 }
::= { sbmConfigEntry 7 }
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 8 }
sbmDsbmElectionState OBJECT-TYPE
Smith Expires April 2000 [Page 11]
Internet Draft SBM Parameters October 1999
SYNTAX INTEGER {
sbmStateOther(1),
sbmStateUnknown(2),
sbmStateDetectDsbm(3),
sbmStateElectDsbm(4),
sbmStateIdle(5),
sbmStateIAmDsbm(6),
sbmStateShutdown(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current state of DSBM election for this SBM instance.
Values of sbmStateOther(1) or sbmStateUnknown(2) indicate that
this SBM instance is in a non-standard or an unknown state.
Values of sbmStateDetectDsbm(3) and sbmStateElectDsbm(4)
indicate that this SBM instance is participating in an DSBM
election procedure that has not yet completed.
A value of sbmStateIdle(5) indicates that this SBM instance
has discovered another SBM within its domain of control that
has a higher election priority and so it is acting as a SBM client.
A value of sbmStateIAmDsbm(6) indicates that this SBM instance
is in control of admission control over its domain of control.
A value of sbmStateShutdown(7) indicates that this SBM instance
is not participating in DSBM election."
REFERENCE "draft-ietf-issll-is802-sbm-08 Appendix A."
::= { sbmConfigEntry 9 }
sbmDsbmLastStateChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which this SBM instance entered the current DSBM
election state."
::= { sbmConfigEntry 10 }
sbmDsbmMaxNonResvTxBucketRate OBJECT-TYPE
SYNTAX BitRate
UNITS "bits per second"
Smith Expires April 2000 [Page 12]
Internet Draft SBM Parameters October 1999
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 11 }
sbmDsbmMaxNonResvTxBucketDepth OBJECT-TYPE
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 12 }
sbmDsbmMaxNonResvTxPeakRate OBJECT-TYPE
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 13 }
sbmDsbmMaxNonResvTxMinPolicedSize OBJECT-TYPE
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."
REFERENCE "RFC2210 section 3.1"
::= { sbmConfigEntry 14 }
Smith Expires April 2000 [Page 13]
Internet Draft SBM Parameters October 1999
sbmDsbmMaxNonResvTxMaxPacketSize OBJECT-TYPE
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 15 }
-- -------------------------------------------------------------
-- SBM Traffic Class Mapping Table
-- -------------------------------------------------------------
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 not-accessible
Smith Expires April 2000 [Page 14]
Internet Draft SBM Parameters October 1999
STATUS current
DESCRIPTION
"Traffic Class (802.1p user_priority)."
REFERENCE
"ISO/IEC 15802-3: 1998"
::= { 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. Suitable default values for
these targets are discussed in a companion document."
REFERENCE
"draft-ietf-issll-is802-svc-mapping-04.txt"
::= { sbmTrafficClassConfigEntry 2 }
sbmTrafficClassEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Enable admission of flows to this class."
DEFVAL { true }
::= { sbmTrafficClassConfigEntry 3 }
-- -------------------------------------------------------------
-- RSVP Configuration Parameters
-- -------------------------------------------------------------
sbmRsvpConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF SbmRsvpConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of configuration information for the RSVP protocol
per SBM instance. There may be one instance per subnet for a
shared LAN. For a switched LAN there may be once instance per
LAN segment/network-interface. For a full-duplex switched LAN
segment the SBM instance only represents the transmit direction:
in this case the receive controls will have no effect.
Smith Expires April 2000 [Page 15]
Internet Draft SBM Parameters October 1999
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 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."
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
Smith Expires April 2000 [Page 16]
Internet Draft SBM Parameters October 1999
"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
STATUS current
DESCRIPTION
"A table of statistics per SBM instance. There may be one
instance per subnet for a shared LAN. For a switched LAN there
may be once instance per LAN segment/network-interface. For a
full-duplex switched LAN segment the SBM instance only represents
the transmit direction: in this case the receive statistics will
not be valid.
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. Counters are continuous
from restart of the agent."
::= { 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,
Smith Expires April 2000 [Page 17]
Internet Draft SBM Parameters October 1999
sbmStatsReceivedRsvpResvTearMsgs Counter32,
sbmStatsReceivedRsvpConfirmMsgs Counter32,
sbmStatsReceivedRsvpBadMsgs Counter32,
sbmStatsSentRsvpPathMsgs Counter32,
sbmStatsSentRsvpResvMsgs Counter32,
sbmStatsSentRsvpPathErrMsgs Counter32,
sbmStatsSentRsvpResvErrMsgs Counter32,
sbmStatsSentRsvpPathTearMsgs Counter32,
sbmStatsSentRsvpResvTearMsgs Counter32,
sbmStatsSentRsvpConfirmMsgs Counter32,
sbmStatsAdmissionControlFailures Counter32,
sbmStatsPolicyControlFailures Counter32,
sbmStatsOtherFailures Counter32,
sbmStatsInBlockadeStateResvs Counter32,
sbmStatsResvTimeOuts Counter32,
sbmStatsPathTimeOuts Counter32,
sbmStatsReceiveFailsBigMsg Counter32,
sbmStatsSendFailsBigMsg Counter32,
sbmStatsReceiveFailsNoResource Counter32,
sbmStatsSendFailsNoResource Counter32,
sbmStatsActiveOutgoingFlows Gauge32,
sbmStatsAllocatedOutgoingBits Gauge32,
sbmStatsMaxAllocatedBandwidthBits Gauge32,
sbmStatsHCAllocatedOutgoingBits RmonGauge64,
sbmStatsHCMaxAllocatedBandwidthBits RmonGauge64
}
sbmStatsSbmSentBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bytes of RSVP messages sent by this SBM
instance. This includes only the contents of the messages,
not any IP or lower-layer framing headers."
::= { sbmStatsEntry 1 }
sbmStatsSbmReceivedBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of bytes of RSVP messages received by this SBM
Smith Expires April 2000 [Page 18]
Internet Draft SBM Parameters October 1999
instance. This includes only the contents of the messages,
not any IP or lower-layer framing headers."
::= { sbmStatsEntry 2 }
sbmStatsReceivedRsvpPathMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP PATH messages received by this SBM
instance."
::= { sbmStatsEntry 3 }
sbmStatsReceivedRsvpResvMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV messages received by this SBM
instance."
::= { sbmStatsEntry 4 }
sbmStatsReceivedRsvpPathErrMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP PATH ERROR messages received by this SBM
instance."
::= { sbmStatsEntry 5 }
sbmStatsReceivedRsvpResvErrMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV ERROR messages received by this SBM
instance."
::= { sbmStatsEntry 6 }
sbmStatsReceivedRsvpPathTearMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Smith Expires April 2000 [Page 19]
Internet Draft SBM Parameters October 1999
"The number of RSVP PATH TEAR messages received by this SBM
instance."
::= { sbmStatsEntry 7 }
sbmStatsReceivedRsvpResvTearMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV TEAR messages received by this SBM
instance."
::= { sbmStatsEntry 8 }
sbmStatsReceivedRsvpConfirmMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP CONFIRM messages received by this SBM
instance."
::= { sbmStatsEntry 9 }
sbmStatsReceivedRsvpBadMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP messages received by this SBM instance
with bad syntax or semantics."
::= { sbmStatsEntry 10 }
sbmStatsSentRsvpPathMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP PATH messages sent by this SBM instance."
::= { sbmStatsEntry 11 }
sbmStatsSentRsvpResvMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV messages sent by this SBM instance."
Smith Expires April 2000 [Page 20]
Internet Draft SBM Parameters October 1999
::= { sbmStatsEntry 12 }
sbmStatsSentRsvpPathErrMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP PATH ERROR messages sent by this SBM
instance."
::= { sbmStatsEntry 13 }
sbmStatsSentRsvpResvErrMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV ERROR messages sent by this SBM
instance."
::= { sbmStatsEntry 14 }
sbmStatsSentRsvpPathTearMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP PATH TEAR messages sent by this SBM
instance."
::= { sbmStatsEntry 15 }
sbmStatsSentRsvpResvTearMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP RESV TEAR messages sent by this SBM
instance."
::= { sbmStatsEntry 16 }
sbmStatsSentRsvpConfirmMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RSVP CONFIRM messages sent by this SBM
instance."
Smith Expires April 2000 [Page 21]
Internet Draft SBM Parameters October 1999
::= { sbmStatsEntry 17 }
sbmStatsAdmissionControlFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP session was denied due to lack
of data-path resources by this SBM instance."
::= { sbmStatsEntry 18 }
sbmStatsPolicyControlFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP session was denied due to failure
of policy controls applied by this SBM instance."
::= { sbmStatsEntry 19 }
sbmStatsOtherFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP session was denied by this SBM instance
due to other reasons."
::= { sbmStatsEntry 20 }
sbmStatsInBlockadeStateResvs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP message caused the creation of blockade
state by this SBM instance."
::= { sbmStatsEntry 21 }
sbmStatsResvTimeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP session was torn down by this SBM instance
due to timeout of RESV refreshes."
Smith Expires April 2000 [Page 22]
Internet Draft SBM Parameters October 1999
::= { sbmStatsEntry 22 }
sbmStatsPathTimeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP session was torn down by this SBM instance
due to timeout of PATH refreshes."
::= { sbmStatsEntry 23 }
sbmStatsReceiveFailsBigMsg OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP message was received by this SBM instance
but discarded due to excessive size."
::= { sbmStatsEntry 24 }
sbmStatsSendFailsBigMsg OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP message should have been transmitted by
this SBM instance but was prevented due to excessive size."
::= { sbmStatsEntry 25 }
sbmStatsReceiveFailsNoResource OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP message was received by this SBM instance
but was discarded due to insufficient resources to process it."
::= { sbmStatsEntry 26 }
sbmStatsSendFailsNoResource OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an RSVP message should have been transmitted by
this SBM instance but was prevented due to insufficient resources
Smith Expires April 2000 [Page 23]
Internet Draft SBM Parameters October 1999
to send it."
::= { sbmStatsEntry 27 }
sbmStatsActiveOutgoingFlows OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of flows reserved by RSVP by this SBM instance
that are outgoing on this interface."
::= { sbmStatsEntry 28 }
sbmStatsAllocatedOutgoingBits OBJECT-TYPE
SYNTAX Gauge32
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current allocation of bandwidth to flows reserved by RSVP
by this SBM instance that are outgoing on this interface."
::= { sbmStatsEntry 29 }
sbmStatsMaxAllocatedBandwidthBits OBJECT-TYPE
SYNTAX Gauge32
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum allocation of bandwidth to flows reserved
by RSVP by this SBM instance that are outgoing on this interface
that has ever occured since the agent restarted."
::= { sbmStatsEntry 30 }
sbmStatsHCAllocatedOutgoingBits OBJECT-TYPE
SYNTAX RmonGauge64
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current allocation of bandwidth to flows reserved by RSVP
by this SBM instance that are outgoing on this interface. This
is a high-capacity version of sbmStatsAllocatedOutgoingBits."
::= { sbmStatsEntry 31 }
sbmStatsHCMaxAllocatedBandwidthBits OBJECT-TYPE
Smith Expires April 2000 [Page 24]
Internet Draft SBM Parameters October 1999
SYNTAX RmonGauge64
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum allocation of bandwidth to flows reserved
by RSVP by this SBM instance that are outgoing on this interface
that has ever occured since the agent restarted. This
is a high-capacity version of sbmStatsMaxAllocatedBandwidthBits."
::= { sbmStatsEntry 32 }
-- -------------------------------------------------------------
-- Conformance Information
-- -------------------------------------------------------------
sbmConformance OBJECT IDENTIFIER ::= { sbmMIB 2 }
sbmGroups OBJECT IDENTIFIER ::= { sbmConformance 1 }
sbmCompliances OBJECT IDENTIFIER ::= { sbmConformance 2 }
-- -------------------------------------------------------------
-- units of conformance
-- -------------------------------------------------------------
sbmSbmConfigGroup OBJECT-GROUP
OBJECTS {
sbmDescription, sbmType, sbmIfIndex, sbmEnable,
sbmDsbmRefreshInterval, sbmDsbmDeadInterval,
sbmDsbmElectionPriority, sbmDsbmElectionState,
sbmDsbmLastStateChange, sbmDsbmMaxNonResvTxBucketRate,
sbmDsbmMaxNonResvTxBucketDepth, sbmDsbmMaxNonResvTxPeakRate,
sbmDsbmMaxNonResvTxMinPolicedSize,
sbmDsbmMaxNonResvTxMaxPacketSize,
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 {
sbmRsvpCopsEnabled, sbmRsvpSenderPolicyEnabled,
sbmRsvpReceiverPolicyEnabled
Smith Expires April 2000 [Page 25]
Internet Draft SBM Parameters October 1999
}
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,
sbmStatsReceivedRsvpBadMsgs,
sbmStatsSentRsvpPathMsgs, sbmStatsSentRsvpResvMsgs,
sbmStatsSentRsvpPathErrMsgs, sbmStatsSentRsvpResvErrMsgs,
sbmStatsSentRsvpPathTearMsgs,
sbmStatsSentRsvpResvTearMsgs,
sbmStatsSentRsvpConfirmMsgs,
sbmStatsAdmissionControlFailures,
sbmStatsPolicyControlFailures, sbmStatsOtherFailures,
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 }
sbmSbmHCStatisticsGroup OBJECT-GROUP
OBJECTS {
sbmStatsHCAllocatedOutgoingBits,
sbmStatsHCMaxAllocatedBandwidthBits
}
STATUS current
Smith Expires April 2000 [Page 26]
Internet Draft SBM Parameters October 1999
DESCRIPTION
"A collection of objects providing per-SBM statistics of RSVP
protocol operations for high-capacity interfaces, defined
as those that have the value of the corresponding instance of
ifSpeed greater than 4^^32-1 bits/second."
::= { sbmGroups 4 }
-- -------------------------------------------------------------
-- 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
}
GROUP sbmSbmHCStatisticsGroup
DESCRIPTION
"This group is mandatory for SBM implementations that support
high-capacity interfaces. It is optional for all other
implementations."
OBJECT sbmRsvpEnabled
MIN-ACCESS read-only
DESCRIPTION
"Read-only access is allowed."
::= { sbmCompliances 1 }
END
6. References
[RSVP]
Braden, R., L. Zhang, S. Berson, S. Herzog, S. Jamin, "Resource
Smith Expires April 2000 [Page 27]
Internet Draft SBM Parameters October 1999
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, June 1999.
http://www.ietf.org/internet-drafts/draft-ietf-issll-
is802-framework-07.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", STD 15, RFC 1157, May 1990.
[V1SMI]
Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990
[V1CONCISE]
Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC
Smith Expires April 2000 [Page 28]
Internet Draft SBM Parameters October 1999
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.
[]
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
Protocol (SNMP)", RFC 2572, April 1999.
Smith Expires April 2000 [Page 29]
Internet Draft SBM Parameters October 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.
[HCRMON]
Waldbusser, S., "Remote Network Monitoring Management Information
Base for High Capacity Networks", http://www.ietf.org/internet-
drafts/draft-ietf-rmonmib-hcrmon-06.txt, June 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.
[802.1D]
"Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area networks -
Common specifications - Part 3: Media Access Control (MAC) Bridges:
Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992
and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e."
ISO/IEC 15802-3: 1998.
[PROCESS]
Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
RFC 2026, October 1996.
Smith Expires April 2000 [Page 30]
Internet Draft SBM Parameters October 1999
7. Security Considerations
There are a number of management objects defined in this MIB that have a
MAX-ACCESS clause of read-write. 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
(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 [V3USM] and the View-based Access Control Model
[V3VACM] 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.
8. 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 April 2000 [Page 31]
Internet Draft SBM Parameters October 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 April 2000 [Page 32]
