draft-ietf-bridge-ext-v2-07.txt   rfc4363.txt 
Internet Draft D. Levi Network Working Group D. Levi
Expires February 2006 Nortel Networks Request for Comments: 4363 Nortel Networks
draft-ietf-bridge-ext-v2-07.txt D.Harrington Obsoletes: 2674 D. Harrington
Obsoletes: RFC 2674 Effective Software Category: Standards Track Effective Software
August 2005 January 2006
Definitions of Managed Objects for Bridges with Traffic Definitions of Managed Objects for Bridges with Traffic
Classes, Multicast Filtering and Virtual LAN Extensions Classes, Multicast Filtering, and Virtual LAN Extensions
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
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 Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP-based internets.
In particular, it defines two MIB modules for managing the In particular, it defines two MIB modules for managing the
capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC
Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards
for bridging between Local Area Network (LAN) segments. One MIB for bridging between Local Area Network (LAN) segments. One MIB
module defines objects for managing the 'Traffic Classes' and module defines objects for managing the 'Traffic Classes' and
'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and
P802.1t-2001 (TM). The other MIB module defines objects for managing P802.1t-2001 (TM). The other MIB module defines objects for managing
VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM) and P802.1v VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM), and P802.1v
(TM). (TM).
Provisions are made for support of transparent bridging. Provisions Provisions are made for support of transparent bridging. Provisions
are also made so that these objects apply to bridges connected by are also made so that these objects apply to bridges connected by
subnetworks other than LAN segments. subnetworks other than LAN segments.
This memo supplements RFC 1493bis, and obsoletes RFC 2674. This memo supplements RFC 4188 and obsoletes RFC 2674.
(NOTE for RFC Ed.: all instances of 'RFC 1493bis' will need to be
updated to reflect the new RFC number for draft-ietf-bridge-
bridgemib-smiv2-10.txt)
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ................... 4 1. The Internet-Standard Management Framework ......................3
2 Overview ..................................................... 4 2. Overview ........................................................3
2.1 Scope ...................................................... 5 2.1. Scope ......................................................3
3 Structure of MIBs ............................................ 5 3. Structure of MIBs ...............................................4
3.1 Structure of Extended Bridge MIB module .................... 6 3.1. Structure of Extended Bridge MIB Module ....................5
3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ...... 6 3.1.1. Relationship to IEEE 802.1D-1998 Manageable
3.1.2 Relationship to IEEE 802.1Q Manageable Objects ........... 8 Objects .............................................5
3.1.3 The dot1dExtBase Subtree ................................. 8 3.1.2. Relationship to IEEE 802.1Q Manageable Objects ......6
3.1.4 The dot1dPriority Subtree ................................ 8 3.1.3. The dot1dExtBase Subtree ............................7
3.1.5 The dot1dGarp Subtree .................................... 9 3.1.4. The dot1dPriority Subtree ...........................7
3.1.6 The dot1dGmrp Subtree .................................... 9 3.1.5. The dot1dGarp Subtree ...............................7
3.1.7 The dot1dTpHCPortTable ................................... 9 3.1.6. The dot1dGmrp Subtree ...............................7
3.1.8 The dot1dTpPortOverflowTable ............................. 9 3.1.7. The dot1dTpHCPortTable ..............................8
3.2 Structure of Virtual Bridge MIB module ..................... 9 3.1.8. The dot1dTpPortOverflowTable ........................8
3.2.1 Relationship to IEEE 802.1Q Manageable Objects ........... 9 3.2. Structure of Virtual Bridge MIB module .....................8
3.2.2 The dot1qBase Subtree .................................... 13 3.2.1. Relationship to IEEE 802.1Q Manageable Objects ......8
3.2.3 The dot1qTp Subtree ...................................... 13 3.2.2. The dot1qBase Subtree ..............................12
3.2.4 The dot1qStatic Subtree .................................. 13 3.2.3. The dot1qTp Subtree ................................12
3.2.5 The dot1qVlan Subtree .................................... 14 3.2.4. The dot1qStatic Subtree ............................12
3.3 Textual Conventions ........................................ 14 3.2.5. The dot1qVlan Subtree ..............................12
3.4 Relationship to Other MIBs ................................. 14 3.3. Textual Conventions .......................................12
3.4.1 Relationship to the SNMPv2-MIB ........................... 15 3.4. Relationship to Other MIBs ................................13
3.4.2 Relationship to the IF-MIB ............................... 15 3.4.1. Relationship to the SNMPv2-MIB .....................13
3.4.2.1 Layering Model ......................................... 16 3.4.2. Relationship to the IF-MIB .........................13
3.4.2.2 ifStackTable ........................................... 17 3.4.2.1. Layering Model ............................14
3.4.2.3 ifRcvAddressTable ...................................... 17 3.4.2.2. ifStackTable ..............................15
3.4.3 Relationship to the BRIDGE-MIB ........................... 17 3.4.2.3. ifRcvAddressTable .........................15
3.4.3.1 The dot1dBase Subtree .................................. 18 3.4.3. Relationship to the BRIDGE-MIB .....................16
3.4.3.2 The dot1dStp Subtree ................................... 18 3.4.3.1. The dot1dBase Subtree .....................16
3.4.3.3 The dot1dTp Subtree .................................... 18 3.4.3.2. The dot1dStp Subtree ......................16
3.4.3.4 The dot1dStatic Subtree ................................ 19 3.4.3.3. The dot1dTp Subtree .......................16
3.4.3.5 Additions to the BRIDGE-MIB ............................ 19 3.4.3.4. The dot1dStatic Subtree ...................17
4 Definitions for Extended Bridge MIB .......................... 20 3.4.3.5. Additions to the BRIDGE-MIB ...............17
5 Definitions for Virtual Bridge MIB ........................... 45 4. Definitions for Extended Bridge MIB ............................18
6 Acknowledgments .............................................. 97 5. Definitions for Virtual Bridge MIB .............................42
7 IANA Considerations .......................................... 97 6. Acknowledgements ...............................................91
8 Security Considerations ...................................... 97 7. Security Considerations ........................................91
9 Normative References ......................................... 100 8. Normative References ...........................................94
10 Informative References ...................................... 101 9. Informative References .........................................95
11 Contact Information ......................................... 103 Appendix A. Email from Tony Jeffrey from IEEE .....................96
Appendix A. Email from Tony Jeffrey from IEEE .................. 105
Copyright Statement ........................................... 105
Disclaimer of Validity ........................................ 105
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 5, line 5 skipping to change at page 3, line 45
feature of switched LAN networks. A VLAN can be viewed as a group of feature of switched LAN networks. A VLAN can be viewed as a group of
end-stations on multiple LAN segments and can communicate as if they end-stations on multiple LAN segments and can communicate as if they
were on a single LAN. IEEE 802.1Q defines port-based Virtual LANs were on a single LAN. IEEE 802.1Q defines port-based Virtual LANs
where membership is determined by the bridge port on which data where membership is determined by the bridge port on which data
frames are received, and port-and-protocol-based Virtual LANs where frames are received, and port-and-protocol-based Virtual LANs where
membership is determined by the bridge port on which frames are membership is determined by the bridge port on which frames are
received and the protocol identifier of the frame. This memo defines received and the protocol identifier of the frame. This memo defines
the objects needed for the management of port-based VLANs in bridge the objects needed for the management of port-based VLANs in bridge
entities. entities.
This memo supplements RFC 4188 [BRIDGE-MIB] and obsoletes RFC 2674
[RFC2674].
2.1. Scope 2.1. Scope
The MIB modules defined in this document include a comprehensive set The MIB modules defined in this document include a comprehensive set
of managed objects which attempts to match the set defined in IEEE of managed objects that attempts to match the set defined in IEEE
802.1D and IEEE 802.1Q. However, to be consistent with the spirit of 802.1D and IEEE 802.1Q. However, to be consistent with the spirit of
the SNMP Framework, a subjective judgement was made to omit the the SNMP Framework, a subjective judgement was made to omit the
objects from those standards most 'costly' to implement in an agent objects from those standards most 'costly' to implement in an agent
and least 'essential' for fault and configuration management. The and least 'essential' for fault and configuration management. The
omissions are described in section 3 below. omissions are described in Section 3 below.
Historical note: Historical note:
The original BRIDGE-MIB [RFC1493] used the following principles for The original BRIDGE-MIB [RFC1493] used the following principles for
determining inclusion of an object in the BRIDGE-MIB module: determining inclusion of an object in the BRIDGE-MIB module:
(1) Start with a small set of essential objects and add only as (1) Start with a small set of essential objects and add only as
further objects are needed. further objects are needed.
(2) Require objects be essential for either fault or configuration (2) Require that objects be essential for either fault or
management. configuration management.
(3) Consider evidence of current use and/or utility. (3) Consider evidence of current use and/or utility.
(4) Limit the total number of objects. (4) Limit the total number of objects.
(5) Exclude objects which are simply derivable from others in this (5) Exclude objects that are simply derivable from others in this
or other MIBs. or other MIBs.
(6) Avoid causing critical sections to be heavily instrumented. (6) Avoid causing critical sections to be heavily instrumented.
The guideline that was followed is one counter per critical The guideline that was followed is one counter per critical
section per layer. section per layer.
3. Structure of MIBs 3. Structure of MIBs
This document defines objects which supplement those in the This document defines objects that supplement those in the BRIDGE-MIB
BRIDGE-MIB module [BRIDGE-MIB]. Section 3.4.3 of the present document module [BRIDGE-MIB]. Section 3.4.3 of the present document contains
contains some recommendations regarding usage of objects in the some recommendations regarding usage of objects in the BRIDGE-MIB by
BRIDGE-MIB by devices implementing the enhancements defined here. devices implementing the enhancements defined here.
An extended bridge MIB module P-BRIDGE-MIB defines managed objects An extended bridge MIB module P-BRIDGE-MIB defines managed objects
for the traffic class and multicast filtering enhancements defined by for the traffic class and multicast filtering enhancements defined by
IEEE 802.1D-1998 [802.1D], including the Restricted Group IEEE 802.1D-1998 [802.1D], including the Restricted Group
Registration control defined by IEEE P802.1t [802.1t]. Registration control defined by IEEE P802.1t [802.1t].
A virtual bridge MIB module Q-BRIDGE-MIB defines managed objects for A virtual bridge MIB module Q-BRIDGE-MIB defines managed objects for
the Virtual LAN bridging enhancements defined by IEEE 802.1Q-2003 the Virtual LAN bridging enhancements defined by IEEE 802.1Q-2003
[802.1Q], including the Restricted VLAN Registration control defined [802.1Q], including the Restricted VLAN Registration control, defined
by IEEE P802.1u [802.1u] and the VLAN Classification by Protocol and by IEEE P802.1u [802.1u], and the VLAN Classification by Protocol and
Port enhancement defined by IEEE P802.1v [802.1v]. Port enhancement, defined by IEEE P802.1v [802.1v].
3.1. Structure of Extended Bridge MIB module 3.1. Structure of Extended Bridge MIB Module
Objects in this MIB are arranged into subtrees. Each subtree is Objects in this MIB are arranged into subtrees. Each subtree is
organized as a set of related objects. The overall structure and organized as a set of related objects. The overall structure and
assignment of objects to their subtrees is shown below. assignment of objects to their subtrees is shown below.
3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects 3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects
This section contains a cross-reference to the objects defined in This section contains a cross-reference to the objects defined in
IEEE 802.1D-1998 [802.1D]. It also details those objects that are IEEE 802.1D-1998 [802.1D]. It also details those objects that are
not considered necessary in this MIB module. not considered necessary in this MIB module.
Some objects defined by IEEE 802.1D-1998 have been included in the Some objects defined by IEEE 802.1D-1998 have been included in the
virtual bridge MIB module rather than this one: entries in virtual bridge MIB module rather than this one: entries in
dot1qTpGroupTable, dot1qForwardAllTable and dot1qTpGroupTable, dot1qForwardAllTable, and
dot1qForwardUnregisteredTable are required for virtual bridged LANs dot1qForwardUnregisteredTable are required for virtual bridged LANs
with additional indexing (e.g. per-VLAN, per-FDB) and so are not with additional indexing (e.g., per-VLAN, per-Filtering-Database
defined here. Instead, devices which do not implement virtual (per-FDB)) and so are not defined here. Instead, devices that do not
bridged LANs but do implement the Extended Forwarding Services implement virtual bridged LANs but do implement the Extended
defined by IEEE 802.1D (i.e. dynamic learning of multicast group Forwarding Services defined by IEEE 802.1D (i.e., dynamic learning of
addresses and group service requirements in the filtering database) multicast group addresses and group service requirements in the
should implement these tables with a fixed value for dot1qFdbId (the filtering database) should implement these tables with a fixed value
value 1 is recommended) or dot1qVlanIndex (the value 1 is for dot1qFdbId (the value 1 is recommended) or dot1qVlanIndex (the
recommended). Devices which support Extended Filtering Services value 1 is recommended). Devices that support Extended Filtering
should support dot1qTpGroupTable, dot1qForwardAllTable and Services should support dot1qTpGroupTable, dot1qForwardAllTable, and
dot1qForwardUnregisteredTable. dot1qForwardUnregisteredTable.
Extended Bridge MIB Name IEEE 802.1D-1998 Name Extended Bridge MIB Name IEEE 802.1D-1998 Name
dot1dExtBase Bridge dot1dExtBase Bridge
dot1dDeviceCapabilities dot1dDeviceCapabilities
dot1dExtendedFilteringServices dot1dExtendedFilteringServices
dot1dTrafficClasses dot1dTrafficClasses
dot1dTrafficClassesEnabled dot1dTrafficClassesEnabled
dot1dGmrpStatus .ApplicantAdministrativeControl dot1dGmrpStatus .ApplicantAdministrativeControl
skipping to change at page 7, line 46 skipping to change at page 6, line 35
dot1dTpPortInOverflowDiscards .DiscardInbound dot1dTpPortInOverflowDiscards .DiscardInbound
The following IEEE 802.1D-1998 management objects have not been The following IEEE 802.1D-1998 management objects have not been
included in the Bridge MIB for the indicated reasons. included in the Bridge MIB for the indicated reasons.
IEEE 802.1D-1998 Object Disposition IEEE 802.1D-1998 Object Disposition
Bridge.StateValue not considered useful Bridge.StateValue not considered useful
Bridge.ApplicantAdministrativeControl Bridge.ApplicantAdministrativeControl
not provided per-attribute not provided per-attribute
(e.g. per-VLAN, per-Group). (e.g., per-VLAN, per-Group).
Only per-{device,port,application} Only per-{device,port,application}
control is provided in this MIB. control is provided in this MIB.
notify group registration failure not considered useful notify group registration failure not considered useful
(IEEE 802.1t 14.10.1.2) (IEEE 802.1t 14.10.1.2)
3.1.2. Relationship to IEEE 802.1Q Manageable Objects 3.1.2. Relationship to IEEE 802.1Q Manageable Objects
This section contains section number cross-references to manageable This section contains section number cross-references to manageable
objects defined in IEEE 802.1Q-2003 [802.1Q]. These objects have objects defined in IEEE 802.1Q-2003 [802.1Q]. These objects have
skipping to change at page 8, line 35 skipping to change at page 7, line 25
dot1dLocalVlanCapable dot1dLocalVlanCapable
dot1dPortCapabilitiesTable dot1dPortCapabilitiesTable
dot1dPortCapabilities dot1dPortCapabilities
dot1qDot1qTagging 5.2 implementation options dot1qDot1qTagging 5.2 implementation options
dot1qConfigurableAcceptableFrameTypes dot1qConfigurableAcceptableFrameTypes
5.2 implementation options 5.2 implementation options
dot1qIngressFiltering 5.2 implementation options dot1qIngressFiltering 5.2 implementation options
3.1.3. The dot1dExtBase Subtree 3.1.3. The dot1dExtBase Subtree
This subtree contains the objects which are applicable to all bridges This subtree contains the objects that are applicable to all bridges
implementing the traffic class and multicast filtering features of implementing the traffic class and multicast filtering features of
IEEE 802.1D-1998 [802.1D]. It includes per-device configuration of IEEE 802.1D-1998 [802.1D]. It includes per-device configuration of
GARP and GMRP protocols. Generic Attribute Registration Protocol (GARP) and GARP Multicast
Registration Protocol (GMRP) protocols.
3.1.4. The dot1dPriority Subtree 3.1.4. The dot1dPriority Subtree
This subtree contains the objects for configuring and reporting This subtree contains the objects for configuring and reporting
status of priority-based queuing mechanisms in a bridge. This status of priority-based queuing mechanisms in a bridge. This
includes per-port user_priority treatment, mapping of user_priority includes per-port user_priority treatment, mapping of user_priority
in frames into internal traffic classes and outbound user_priority in frames into internal traffic classes, and outbound user_priority
and access_priority. and access_priority.
3.1.5. The dot1dGarp Subtree 3.1.5. The dot1dGarp Subtree
This subtree contains the objects for configuring and reporting on This subtree contains the objects for configuring and reporting on
operation of the Generic Attribute Registration Protocol (GARP). operation of the Generic Attribute Registration Protocol (GARP).
3.1.6. The dot1dGmrp Subtree 3.1.6. The dot1dGmrp Subtree
This subtree contains the objects for configuring and reporting on This subtree contains the objects for configuring and reporting on
operation of the GARP Multicast Registration Protocol (GMRP). operation of the GARP Multicast Registration Protocol (GMRP).
3.1.7. The dot1dTpHCPortTable 3.1.7. The dot1dTpHCPortTable
This table extends the dot1dTp subtree from the BRIDGE-MIB This table extends the dot1dTp subtree from the BRIDGE-MIB
[BRIDGE-MIB] and contains the objects for reporting port bridging [BRIDGE-MIB] and contains the objects for reporting port-bridging
statistics for high capacity network interfaces. statistics for high-capacity network interfaces.
3.1.8. The dot1dTpPortOverflowTable 3.1.8. The dot1dTpPortOverflowTable
This table extends the dot1dTp subtree from the BRIDGE-MIB This table extends the dot1dTp subtree from the BRIDGE-MIB
[BRIDGE-MIB] and contains the objects for reporting the upper bits of [BRIDGE-MIB] and contains the objects for reporting the upper bits of
port bridging statistics for high capacity network interfaces for port-bridging statistics for high-capacity network interfaces for
when 32-bit counters are inadequate. when 32-bit counters are inadequate.
3.2. Structure of Virtual Bridge MIB module 3.2. Structure of Virtual Bridge MIB module
Objects in this MIB are arranged into subtrees. Each subtree is Objects in this MIB are arranged into subtrees. Each subtree is
organized as a set of related objects. The overall structure and organized as a set of related objects. The overall structure and
assignment of objects to their subtrees is shown below. Some assignment of objects to their subtrees is shown below. Some
manageable objects defined in the BRIDGE-MIB [BRIDGE-MIB] need to be manageable objects defined in the BRIDGE-MIB [BRIDGE-MIB] need to be
indexed differently when they are used in a VLAN bridging indexed differently when they are used in a VLAN bridging
environment: these objects are, therefore, effectively duplicated by environment: these objects are, therefore, effectively duplicated by
new objects with different indexing which are defined in the Virtual new objects with different indexing, which are defined in the Virtual
Bridge MIB. Bridge MIB.
3.2.1. Relationship to IEEE 802.1Q Manageable Objects 3.2.1. Relationship to IEEE 802.1Q Manageable Objects
This section contains section-number cross-references to manageable This section contains section-number cross-references to manageable
objects defined in clause 12 of IEEE 802.1Q-2003 [802.1Q]. It also objects defined in clause 12 of IEEE 802.1Q-2003 [802.1Q]. It also
details those objects that are not considered necessary in this MIB details those objects that are not considered necessary in this MIB
module. module.
Note: unlike IEEE 802.1D-1998, IEEE 802.1Q-2003 [802.1Q] did not Note: Unlike IEEE 802.1D-1998, IEEE 802.1Q-2003 [802.1Q] did not
define exact syntax for a set of managed objects: the following define exact syntax for a set of managed objects. The following
cross-references indicate the section numbering of the descriptions cross-references indicate the section numbering of the descriptions
of management operations from clause 12 in the latter document. of management operations from clause 12 in the latter document.
Virtual Bridge MIB object IEEE 802.1Q-2003 Reference Virtual Bridge MIB object IEEE 802.1Q-2003 Reference
dot1qBase dot1qBase
dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config
dot1qMaxVlanId 12.10.1.1 read bridge vlan config dot1qMaxVlanId 12.10.1.1 read bridge vlan config
dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config
dot1qNumVlans dot1qNumVlans
skipping to change at page 13, line 25 skipping to change at page 12, line 4
read filtering database (12.7.1.1) read filtering database (12.7.1.1)
filtering database size not considered useful filtering database size not considered useful
number of dynamic group address count rows applicable to each number of dynamic group address count rows applicable to each
entries (12.7.1.3) FDB in dot1dTpGroupTable entries (12.7.1.3) FDB in dot1dTpGroupTable
read garp state (12.9.3.1) not considered useful read garp state (12.9.3.1) not considered useful
notify vlan registration failure not considered useful notify vlan registration failure not considered useful
(12.10.1.6) (12.10.1.6)
notify learning constraint violation notify learning constraint violation
(12.10.3.10) not considered useful (12.10.3.10) not considered useful
3.2.2. The dot1qBase Subtree 3.2.2. The dot1qBase Subtree
This subtree contains the objects which are applicable to all bridges This subtree contains the objects that are applicable to all bridges
implementing IEEE 802.1Q virtual LANs. implementing IEEE 802.1Q virtual LANs.
3.2.3. The dot1qTp Subtree 3.2.3. The dot1qTp Subtree
This subtree contains objects that control the operation and report This subtree contains objects that control the operation and report
the status of transparent bridging. This includes management of the the status of transparent bridging. This includes management of the
dynamic Filtering Databases for both unicast and multicast dynamic Filtering Databases for both unicast and multicast
forwarding. This subtree will be implemented by all bridges that forwarding. This subtree will be implemented by all bridges that
perform destination-address filtering. perform destination-address filtering.
skipping to change at page 14, line 11 skipping to change at page 12, line 32
This subtree contains objects that control static configuration This subtree contains objects that control static configuration
information for transparent bridging. This includes management of information for transparent bridging. This includes management of
the static entries in the Filtering Databases for both unicast and the static entries in the Filtering Databases for both unicast and
multicast forwarding. multicast forwarding.
3.2.5. The dot1qVlan Subtree 3.2.5. The dot1qVlan Subtree
This subtree contains objects that control configuration and report This subtree contains objects that control configuration and report
status of the Virtual LANs known to a bridge. This includes status of the Virtual LANs known to a bridge. This includes
management of the statically configured VLANs as well as reporting management of the statically configured VLANs as well as reporting
VLANs discovered by other means e.g. GVRP. It also controls VLANs discovered by other means (e.g., GARP VLAN Registration
configuration and reports status of per-port objects relating to Protocol (GVRP)). It also controls configuration and reports status
VLANs and reports traffic statistics. It also provides for of per-port objects relating to VLANs and reports traffic statistics.
management of the VLAN Learning Constraints. It also provides for management of the VLAN Learning Constraints.
3.3. Textual Conventions 3.3. Textual Conventions
Various Working Groups have defined standards-track MIB documents Various Working Groups have defined standards-track MIB documents
(for example [RFC2613] and [RFC3318]), that contain objects and (for example, [RFC2613] and [RFC3318]), that contain objects and
Textual Conventions to represent a Virtual Local Area Network Textual Conventions to represent a Virtual Local Area Network
Identifier (VLAN-ID) [802.1Q]. New definitions are showing up in Identifier (VLAN-ID) [802.1Q]. New definitions are showing up in
various Internet-Drafts (for example [I-D.ietf-ipcdn-qos-mib], various documents (for example, [RFC4323] and [RFC4149]).
[I-D.ietf-rmonmib-sspm-mib]). Unfortunately the result is a set of Unfortunately, the result is a set of different definitions for the
different definitions for the same piece of management information. same piece of management information. This may lead to confusion and
This may lead to confusion and unnecessary complexity. In order to unnecessary complexity. In order to address this situation, three
address this situation, three new textual conventions are defined in new textual conventions are defined in the Q-BRIDGE-MIB, called
the Q-BRIDGE-MIB, called VlanIdOrAny, VlanIdOrNone, and VlanIdOrAny, VlanIdOrNone, and VlanIdOrAnyOrNone. These new textual
VlanIdOrAnyOrNone. These new textual conventions should be (re-)used conventions should be (re)used in MIB modules so that they all
in MIB modules, so that they all represent a VLAN-ID in the same way. represent a VLAN-ID in the same way.
These textual conventions provide a means to specify MIB objects that These textual conventions provide a means to specify MIB objects that
refer to either a specific VLAN, to any VLAN, or to no VLAN. For an refer to a specific VLAN, to any VLAN, or to no VLAN. For an example
example of how these textual conventions might be used, consider a of how these textual conventions might be used, consider a MIB
MIB object, with SYNTAX of VlanIdOrAnyOrNone, that specifies the VLAN object, with SYNTAX of VlanIdOrAnyOrNone, that specifies the VLAN on
on which to accept incoming packets of a particular protocol. Such which to accept incoming packets of a particular protocol. Such an
an object would allow the device to be configured to accept packets object would allow the device to be configured to accept packets of
of this protocol received with a specific 802.1q tag value, with any this protocol received with a specific 802.1q tag value, with any
802.1q tag value, or with no 802.1q tag. Note that a MIB object that 802.1q tag value, or with no 802.1q tag. Note that a MIB object that
is defined using one of these textual conventions should clarify the is defined using one of these textual conventions should clarify the
meaning of 'any VLAN' and/or 'no VLAN' in its DESCRIPTION clause. meaning of 'any VLAN' and/or 'no VLAN' in its DESCRIPTION clause.
3.4. Relationship to Other MIBs 3.4. Relationship to Other MIBs
As described above, some IEEE 802.1D management objects have not been As described above, some IEEE 802.1D management objects have not been
included in this MIB because they overlap with objects in other MIBs included in this MIB because they overlap with objects in other MIBs
applicable to a bridge implementing this MIB module. applicable to a bridge implementing this MIB module.
3.4.1. Relationship to the SNMPv2-MIB 3.4.1. Relationship to the SNMPv2-MIB
The SNMPv2-MIB [RFC3418] defines objects that are generally The SNMPv2-MIB [RFC3418] defines objects that are generally
applicable to managed devices. These objects apply to the device as applicable to managed devices. These objects apply to the device as
a whole irrespective of whether the device's sole functionality is a whole, irrespective of whether bridging is the device's sole
bridging, or whether bridging is only a subset of the device's functionality or only a subset of the device's functionality.
functionality.
Full support for the 802.1D management objects requires that the Full support for the 802.1D management objects requires that the
SNMPv2-MIB objects sysDescr and sysUpTime are implemented. Note that SNMPv2-MIB objects sysDescr and sysUpTime be implemented. Note that
compliance to the current SNMPv2-MIB module requires additional compliance to the current SNMPv2-MIB module requires additional
objects and notifications to be implemented as specified in RFC 3418 objects and notifications to be implemented as specified in RFC 3418
[RFC3418]. [RFC3418].
3.4.2. Relationship to the IF-MIB 3.4.2. Relationship to the IF-MIB
The IF-MIB, [RFC2863], requires that any MIB which is an adjunct of The IF-MIB, [RFC2863], requires that any MIB that is an adjunct of
the IF-MIB clarify specific areas within the IF-MIB. These areas the IF-MIB clarify specific areas within the IF-MIB. These areas
were intentionally left vague in the IF-MIB in order to avoid were intentionally left vague in the IF-MIB in order to avoid over-
over-constraining the MIB, thereby precluding management of certain constraining the MIB, thereby precluding management of certain
media-types. media-types.
The IF-MIB enumerates several areas which a media-specific MIB must The IF-MIB enumerates several areas that a media-specific MIB must
clarify. Each of these areas is addressed in a following subsection. clarify. Each of these areas is addressed in a following subsection.
The implementor is referred to the IF-MIB in order to understand the The implementor is referred to the IF-MIB in order to understand the
general intent of these areas. general intent of these areas.
The IF-MIB [RFC2863] defines managed objects for managing network The IF-MIB [RFC2863] defines managed objects for managing network
interfaces. A network interface is thought of as being attached to a interfaces. A network interface is considered attached to a
`subnetwork'. (Note that this term is not to be confused with 'subnetwork'. (Note that this term is not to be confused with
`subnet' which refers to an addressing partitioning scheme used in 'subnet', which refers to an addressing partitioning scheme used in
the Internet suite of protocols.) The term 'segment' is used in this the Internet suite of protocols.) The term 'segment' is used in this
memo to refer to such a subnetwork, whether it be an Ethernet memo to refer to such a subnetwork, whether it be an Ethernet
segment, a 'ring', a WAN link, or even an X.25 virtual circuit. segment, a 'ring', a WAN link, or even an X.25 virtual circuit.
Full support for the 802.1D management objects requires that the Full support for the 802.1D management objects requires that the
IF-MIB objects ifIndex, ifType, ifDescr, ifPhysAddress, and IF-MIB objects ifIndex, ifType, ifDescr, ifPhysAddress, and
ifLastChange are implemented. Note that compliance to the current ifLastChange are implemented. Note that compliance to the current
IF-MIB module requires additional objects and notifications to be IF-MIB module requires additional objects and notifications to be
implemented as specified in RFC 2863 [RFC2863]. implemented as specified in RFC 2863 [RFC2863].
Implicit in this Extended Bridge MIB is the notion of ports on a Implicit in this Extended Bridge MIB is the notion of ports on a
bridge. Each of these ports is associated with one interface of the bridge. Each of these ports is associated with one interface of the
'interfaces' subtree (one row in ifTable) and, in most situations, 'interfaces' subtree (one row in ifTable), and, in most situations,
each port is associated with a different interface. However, there each port is associated with a different interface. However, there
are situations in which multiple ports are associated with the same are situations in which multiple ports are associated with the same
interface. An example of such a situation would be several ports interface. An example of such a situation would be several ports
each corresponding one-to-one with several X.25 virtual circuits but each corresponding one-to-one with several X.25 virtual circuits but
all on the same interface. all on the same interface.
Each port is uniquely identified by a port number. A port number has Each port is uniquely identified by a port number. A port number has
no mandatory relationship to an interface number, but in the simple no mandatory relationship to an interface number, but in the simple
case a port number will have the same value as the corresponding case a port number will have the same value as the corresponding
interface's interface number. Port numbers are in the range interface's interface number. Port numbers are in the range
(1..dot1dBaseNumPorts). (1..dot1dBaseNumPorts).
Some entities perform other functionality as well as bridging through Some entities perform other functionality as well as bridging through
the sending and receiving of data on their interfaces. In such the sending and receiving of data on their interfaces. In such
situations, only a subset of the data sent/received on an interface situations, only a subset of the data sent/received on an interface
is within the domain of the entity's bridging functionality. This is within the domain of the entity's bridging functionality. This
subset is considered to be delineated according to a set of subset is considered delineated according to a set of protocols, with
protocols, with some protocols being bridged, and other protocols not some protocols being bridged, and other protocols not being bridged.
being bridged. For example, in an entity which exclusively performed For example, in an entity that exclusively performed bridging, all
bridging, all protocols would be considered as being bridged, whereas protocols would be considered bridged, whereas in an entity that
in an entity which performed IP routing on IP datagrams and only performed IP routing on IP datagrams and only bridged other
bridged other protocols, only the non-IP data would be considered as protocols, only the non-IP data would be considered bridged.
being bridged.
Thus, this Extended Bridge MIB (and in particular, its counters) is Thus, this Extended Bridge MIB (and in particular, its counters) is
applicable only to that subset of the data on an entity's interfaces applicable only to that subset of the data on an entity's interfaces
which is sent/received for a protocol being bridged. All such data that is sent/received for a protocol being bridged. All such data is
is sent/received via the ports of the bridge. sent/received via the ports of the bridge.
3.4.2.1. Layering Model 3.4.2.1. Layering Model
This memo assumes the interpretation of the Interfaces Subtree to be This memo assumes the interpretation of the Interfaces Subtree to be
in accordance with the IF-MIB [RFC2863] which states that the in accordance with the IF-MIB [RFC2863], which states that the
interfaces table (ifTable) contains information on the managed interfaces table (ifTable) contains information on the managed
resource's interfaces and that each sub-layer below the internetwork resource's interfaces and that each sub-layer below the internetwork
layer of a network interface is considered an interface. layer of a network interface is considered an interface.
This document does not make any assumption that within an entity, This document does not make any assumption that within an entity,
VLANs which are instantiated as an entry in dot1qVlanCurrentTable by VLANs that are instantiated as an entry in dot1qVlanCurrentTable by
either management configuration through dot1qVlanStaticTable or by either management configuration through dot1qVlanStaticTable or by
dynamic means (e.g. through GVRP), are also represented by an entry dynamic means (e.g., through GVRP) are also represented by an entry
in ifTable. in ifTable.
Where an entity contains higher-layer protocol entities e.g. IP-layer Where an entity contains higher-layer protocol entities (e.g.,
interfaces that transmit and receive traffic to/from a VLAN, these IP-layer interfaces that transmit and receive traffic to/from a
should be represented in the ifTable as interfaces of type VLAN), these should be represented in the ifTable as interfaces of
propVirtual(53). Protocol-specific types such as l3ipxvlan(137) type propVirtual(53). Protocol-specific types such as l3ipxvlan(137)
should not be used here since there is no implication that the bridge should not be used here, since there is no implication that the
will perform any protocol filtering before delivering up to these bridge will perform any protocol filtering before delivering up to
virtual interfaces. these virtual interfaces.
3.4.2.2. ifStackTable 3.4.2.2. ifStackTable
In addition, the IF-MIB [RFC2863] defines a table 'ifStackTable' for In addition, the IF-MIB [RFC2863] defines a table 'ifStackTable' for
describing the relationship between logical interfaces within an describing the relationship between logical interfaces within an
entity. It is anticipated that implementors will use this table to entity. It is anticipated that implementors will use this table to
describe the binding of e.g. IP interfaces to physical ports, describe the binding of (for example) IP interfaces to physical
although the presence of VLANs makes the representation less than ports, although the presence of VLANs makes the representation less
perfect for showing connectivity: the ifStackTable cannot represent than perfect for showing connectivity. The ifStackTable cannot
the full capability of the IEEE 802.1Q VLAN bridging standard since represent the full capability of the IEEE 802.1Q VLAN bridging
that makes a distinction between VLAN bindings on 'ingress' to and standard, since that makes a distinction between VLAN bindings on
'egress' from a port: these relationships may or may not be 'ingress' to and 'egress' from a port: these relationships may or may
symmetrical whereas Interface MIB Evolution assumes a symmetrical not be symmetrical whereas Interface MIB Evolution assumes a
binding for transmit and receive. This makes it necessary to define symmetrical binding for transmit and receive. This makes it
other manageable objects for configuring which ports are members of necessary to define other manageable objects for configuring which
which VLANs. ports are members of which VLANs.
3.4.2.3. ifRcvAddressTable 3.4.2.3. ifRcvAddressTable
This table contains all MAC addresses, unicast, multicast, and This table contains all MAC addresses, unicast, multicast, and
broadcast, for which an interface will receive packets and forward broadcast, for which an interface will receive packets and forward
them up to a higher layer entity for local consumption. Note that them up to a higher-layer entity for local consumption. Note that
this does not include addresses for data-link layer control protocols this does not include addresses for data-link layer control protocols
such as Spanning-Tree, GMRP or GVRP. The format of the address, such as Spanning-Tree, GMRP, or GVRP. The format of the address,
contained in ifRcvAddressAddress, is the same as for ifPhysAddress. contained in ifRcvAddressAddress, is the same as for ifPhysAddress.
This table does not include unicast or multicast addresses which are This table does not include unicast or multicast addresses that are
accepted for possible forwarding out some other port. This table is accepted for possible forwarding out some other port. This table is
explicitly not intended to provide a bridge address filtering explicitly not intended to provide a bridge address filtering
mechanism. mechanism.
3.4.3. Relationship to the BRIDGE-MIB 3.4.3. Relationship to the BRIDGE-MIB
This section defines how objects in the BRIDGE-MIB module This section defines how objects in the BRIDGE-MIB module
[BRIDGE-MIB] should be represented for devices which implement the [BRIDGE-MIB] should be represented for devices that implement the
extensions: some of the old objects are less useful in such devices extensions: some of the old objects are less useful in such devices
but must still be implemented for reasons of backwards compatibility. but must still be implemented for reasons of backwards compatibility.
3.4.3.1. The dot1dBase Subtree 3.4.3.1. The dot1dBase Subtree
This subtree contains objects which are applicable to all types of This subtree contains objects that are applicable to all types of
bridges. Interpretation of this subtree is unchanged. bridges. Interpretation of this subtree is unchanged.
3.4.3.2. The dot1dStp Subtree 3.4.3.2. The dot1dStp Subtree
This subtree contains the objects that denote the bridge's state with This subtree contains the objects that denote the bridge's state with
respect to the Spanning Tree Protocol. Interpretation of this respect to the Spanning Tree Protocol. Interpretation of this
subtree is unchanged. subtree is unchanged.
3.4.3.3. The dot1dTp Subtree 3.4.3.3. The dot1dTp Subtree
skipping to change at page 18, line 28 skipping to change at page 16, line 35
This subtree contains objects that describe the entity's state with This subtree contains objects that describe the entity's state with
respect to transparent bridging. respect to transparent bridging.
In a device operating with a single Filtering Database, In a device operating with a single Filtering Database,
interpretation of this subtree is unchanged. interpretation of this subtree is unchanged.
In a device supporting multiple Filtering Databases, this subtree is In a device supporting multiple Filtering Databases, this subtree is
interpreted as follows: interpreted as follows:
dot1dTpLearnedEntryDiscards dot1dTpLearnedEntryDiscards
The number of times that *any* of the FDBs became full. The number of times that *any* of the FDBs became full.
dot1dTpAgingTime dot1dTpAgingTime
This applies to all Filtering Databases. This applies to all Filtering Databases.
dot1dTpFdbTable dot1dTpFdbTable
Report MAC addresses learned on each port, regardless of which Report MAC addresses learned on each port, regardless of which
Filtering Database they have been learnt in. If an address has Filtering Database they have been learned in. If an address has
been learnt in multiple databases on a single port, report it been learned in multiple databases on a single port, report it
only once. If an address has been learnt in multiple databases only once. If an address has been learned in multiple databases
on more than one port, report the entry on any one of the valid on more than one port, report the entry on any one of the valid
ports. ports.
dot1dTpPortTable dot1dTpPortTable
This table is port-based and is not affected by multiple This table is port-based and is not affected by multiple
Filtering Databases or multiple VLANs. The counters should Filtering Databases or multiple VLANs. The counters should
include frames received or transmitted for all VLANs. Note that include frames received or transmitted for all VLANs. Note that
equivalent 64-bit port statistics counters, as well as other equivalent 64-bit port statistics counters, as well as other
objects to represent the upper 32 bits of these counters, are objects to represent the upper 32 bits of these counters, are
defined in this document for high capacity network interfaces. defined in this document for high-capacity network interfaces.
These have conformance statements to indicate for which speeds These have conformance statements to indicate for which speeds
of interface they are required. of interface they are required.
3.4.3.4. The dot1dStatic Subtree 3.4.3.4. The dot1dStatic Subtree
This optional subtree contains objects that describe the This optional subtree contains objects that describe the
configuration of destination-address filtering. configuration of destination-address filtering.
In a device operating with a single Filtering Database, In a device operating with a single Filtering Database,
interpretation of this subtree is unchanged. interpretation of this subtree is unchanged.
In a device supporting multiple Filtering Databases, this subtree is In a device supporting multiple Filtering Databases, this subtree is
interpreted as follows: interpreted as follows:
dot1dStaticTable dot1dStaticTable
Entries read from this table include all static entries from all Entries read from this table include all static entries from all
of the Filtering Databases. Entries for the same MAC address of the Filtering Databases. Entries for the same MAC address
and receive port in more than one Filtering Database must appear and receive port in more than one Filtering Database must appear
only once since these are the indices of this table. This table only once, since these are the indices of this table. This
should be implemented as read-only in devices that support table should be implemented as read-only in devices that support
multiple Forwarding Databases - instead, write access should be multiple Forwarding Databases. Instead, write access should be
provided through dot1qStaticUnicastTable and provided through dot1qStaticUnicastTable and
dot1qStaticMulticastTable, as defined in this document. dot1qStaticMulticastTable, as defined in this document.
3.4.3.5. Additions to the BRIDGE-MIB 3.4.3.5. Additions to the BRIDGE-MIB
To supplement the BRIDGE-MIB [BRIDGE-MIB], this module contains: To supplement the BRIDGE-MIB [BRIDGE-MIB], this module contains:
(1) support for multiple traffic classes and dynamic multicast (1) support for multiple traffic classes and dynamic multicast
filtering as per IEEE 802.1D-1998 [802.1D]. filtering as per IEEE 802.1D-1998 [802.1D].
skipping to change at page 20, line 25 skipping to change at page 18, line 25
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dTp, dot1dTpPort, dot1dBridge, dot1dTp, dot1dTpPort, dot1dBridge,
dot1dBasePortEntry, dot1dBasePort dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
pBridgeMIB MODULE-IDENTITY pBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200507290000Z" LAST-UPDATED "200601090000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: bridge-mib@ietf.org "Email: bridge-mib@ietf.org
ietfmibs@ops.ietf.org ietfmibs@ops.ietf.org
David Levi David Levi
Postal: Nortel Networks Postal: Nortel Networks
4655 Great America Parkway 4655 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
skipping to change at page 21, line 45 skipping to change at page 19, line 44
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing Priority "The Bridge MIB Extension module for managing Priority
and Multicast Filtering, defined by IEEE 802.1D-1998, and Multicast Filtering, defined by IEEE 802.1D-1998,
including Restricted Group Registration defined by including Restricted Group Registration defined by
IEEE 802.1t-2001. IEEE 802.1t-2001.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXXX; See the RFC itself for this MIB module is part of RFC 4363; See the RFC itself for
full legal notices." full legal notices."
-- NOTE to RFC editor: replace XXXX with actual RFC number REVISION "200601090000Z"
-- for this document and remove this note
REVISION "200507290000Z"
DESCRIPTION DESCRIPTION
"Added dot1dPortRestrictedGroupRegistration. "Added dot1dPortRestrictedGroupRegistration.
Deprecated pBridgePortGmrpGroup and pBridgeCompliance Deprecated pBridgePortGmrpGroup and pBridgeCompliance
and added pBridgePortGmrpGroup2 and pBridgeCompliance2." and added pBridgePortGmrpGroup2 and pBridgeCompliance2."
REVISION "199908250000Z" REVISION "199908250000Z"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing Priority "The Bridge MIB Extension module for managing Priority
and Multicast Filtering, defined by IEEE 802.1D-1998. and Multicast Filtering, defined by IEEE 802.1D-1998.
Initial version, published as RFC 2674." Initial version, published as RFC 2674."
::= { dot1dBridge 6 } ::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
skipping to change at page 23, line 28 skipping to change at page 21, line 20
-- can perform filtering of -- can perform filtering of
-- individual multicast addresses -- individual multicast addresses
-- controlled by GMRP. -- controlled by GMRP.
dot1dTrafficClasses(1), dot1dTrafficClasses(1),
-- can map user priority to -- can map user priority to
-- multiple traffic classes. -- multiple traffic classes.
dot1qStaticEntryIndividualPort(2), dot1qStaticEntryIndividualPort(2),
-- dot1qStaticUnicastReceivePort & -- dot1qStaticUnicastReceivePort &
-- dot1qStaticMulticastReceivePort -- dot1qStaticMulticastReceivePort
-- can represent non-zero entries. -- can represent non-zero entries.
dot1qIVLCapable(3), -- Independent VLAN Learning. dot1qIVLCapable(3), -- Independent VLAN Learning (IVL).
dot1qSVLCapable(4), -- Shared VLAN Learning. dot1qSVLCapable(4), -- Shared VLAN Learning (SVL).
dot1qHybridCapable(5), dot1qHybridCapable(5),
-- both IVL & SVL simultaneously. -- both IVL & SVL simultaneously.
dot1qConfigurablePvidTagging(6), dot1qConfigurablePvidTagging(6),
-- whether the implementation -- whether the implementation
-- supports the ability to -- supports the ability to
-- override the default PVID -- override the default PVID
-- setting and its egress status -- setting and its egress status
-- (VLAN-Tagged or Untagged) on -- (VLAN-Tagged or Untagged) on
-- each port. -- each port.
dot1dLocalVlanCapable(7) dot1dLocalVlanCapable(7)
skipping to change at page 24, line 25 skipping to change at page 22, line 15
dot1dGmrpStatus OBJECT-TYPE dot1dGmrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status requested by management for "The administrative status requested by management for
GMRP. The value enabled(1) indicates that GMRP should GMRP. The value enabled(1) indicates that GMRP should
be enabled on this device, in all VLANs, on all ports be enabled on this device, in all VLANs, on all ports
for which it has not been specifically disabled. When for which it has not been specifically disabled. When
disabled(2), GMRP is disabled, in all VLANs, on all disabled(2), GMRP is disabled, in all VLANs and on all
ports and all GMRP packets will be forwarded ports, and all GMRP packets will be forwarded
transparently. This object affects both Applicant and transparently. This object affects both Applicant and
Registrar state machines. A transition from disabled(2) Registrar state machines. A transition from disabled(2)
to enabled(1) will cause a reset of all GMRP state to enabled(1) will cause a reset of all GMRP state
machines on all ports. machines on all ports.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dExtBase 3 } ::= { dot1dExtBase 3 }
skipping to change at page 25, line 31 skipping to change at page 23, line 18
dot1dPortCapabilities OBJECT-TYPE dot1dPortCapabilities OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
dot1qDot1qTagging(0), dot1qDot1qTagging(0),
dot1qConfigurableAcceptableFrameTypes(1), dot1qConfigurableAcceptableFrameTypes(1),
dot1qIngressFiltering(2) dot1qIngressFiltering(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the parts of IEEE 802.1D and 802.1Q that are "Indicates the parts of IEEE 802.1D and 802.1Q that are
optional on a per-port basis that are implemented by optional on a per-port basis, that are implemented by
this device and are manageable through this MIB. this device, and that are manageable through this MIB.
dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of
-- frames and GVRP. -- frames and GVRP.
dot1qConfigurableAcceptableFrameTypes(1), dot1qConfigurableAcceptableFrameTypes(1),
-- allows modified values of -- allows modified values of
-- dot1qPortAcceptableFrameTypes. -- dot1qPortAcceptableFrameTypes.
dot1qIngressFiltering(2) dot1qIngressFiltering(2)
-- supports the discarding of any -- supports the discarding of any
-- frame received on a Port whose -- frame received on a Port whose
-- VLAN classification does not -- VLAN classification does not
skipping to change at page 33, line 18 skipping to change at page 30, line 36
dot1dPortGmrpStatus OBJECT-TYPE dot1dPortGmrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative state of GMRP operation on this port. The "The administrative state of GMRP operation on this port. The
value enabled(1) indicates that GMRP is enabled on this port value enabled(1) indicates that GMRP is enabled on this port
in all VLANs as long as dot1dGmrpStatus is also enabled(1). in all VLANs as long as dot1dGmrpStatus is also enabled(1).
A value of disabled(2) indicates that GMRP is disabled on A value of disabled(2) indicates that GMRP is disabled on
this port in all VLANs: any GMRP packets received will this port in all VLANs: any GMRP packets received will
be silently discarded and no GMRP registrations will be be silently discarded, and no GMRP registrations will be
propagated from other ports. Setting this to a value of propagated from other ports. Setting this to a value of
enabled(1) will be stored by the agent but will only take enabled(1) will be stored by the agent but will only take
effect on the GMRP protocol operation if dot1dGmrpStatus effect on the GMRP protocol operation if dot1dGmrpStatus
also indicates the value enabled(1). This object affects also indicates the value enabled(1). This object affects
all GMRP Applicant and Registrar state machines on this all GMRP Applicant and Registrar state machines on this
port. A transition from disabled(2) to enabled(1) will port. A transition from disabled(2) to enabled(1) will
cause a reset of all GMRP state machines on this port. cause a reset of all GMRP state machines on this port.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
skipping to change at page 34, line 25 skipping to change at page 31, line 39
Registration. Registration.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1t clause 10.3.2.3, 14.10.1.3." "IEEE 802.1t clause 10.3.2.3, 14.10.1.3."
DEFVAL { false } DEFVAL { false }
::= { dot1dPortGmrpEntry 4 } ::= { dot1dPortGmrpEntry 4 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- High-Capacity Port Table for Transparent Bridges
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dTpHCPortTable OBJECT-TYPE dot1dTpHCPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTpHCPortEntry SYNTAX SEQUENCE OF Dot1dTpHCPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains information about every high "A table that contains information about every high-
capacity port that is associated with this transparent capacity port that is associated with this transparent
bridge." bridge."
::= { dot1dTp 5 } ::= { dot1dTp 5 }
dot1dTpHCPortEntry OBJECT-TYPE dot1dTpHCPortEntry OBJECT-TYPE
SYNTAX Dot1dTpHCPortEntry SYNTAX Dot1dTpHCPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Statistics information for each high capacity port of a "Statistics information for each high-capacity port of a
transparent bridge." transparent bridge."
INDEX { dot1dTpPort } INDEX { dot1dTpPort }
::= { dot1dTpHCPortTable 1 } ::= { dot1dTpHCPortTable 1 }
Dot1dTpHCPortEntry ::= Dot1dTpHCPortEntry ::=
SEQUENCE { SEQUENCE {
dot1dTpHCPortInFrames dot1dTpHCPortInFrames
Counter64, Counter64,
dot1dTpHCPortOutFrames dot1dTpHCPortOutFrames
Counter64, Counter64,
skipping to change at page 35, line 47 skipping to change at page 33, line 12
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 2 } ::= { dot1dTpHCPortEntry 2 }
dot1dTpHCPortInDiscards OBJECT-TYPE dot1dTpHCPortInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of valid frames that have been received by this "Count of valid frames that have been received by this
port from its segment which were discarded (i.e., port from its segment that were discarded (i.e.,
filtered) by the Forwarding Process." filtered) by the Forwarding Process."
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 3 } ::= { dot1dTpHCPortEntry 3 }
-- ---------------------------------------------------- -- ----------------------------------------------------
-- Upper part of High-Capacity Port Table for Transparent Bridges
-- ---------------------------------------------------- -- ----------------------------------------------------
dot1dTpPortOverflowTable OBJECT-TYPE dot1dTpPortOverflowTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains the most-significant bits of "A table that contains the most-significant bits of
statistics counters for ports that are associated with this statistics counters for ports that are associated with this
transparent bridge that are on high capacity interfaces, as transparent bridge that are on high-capacity interfaces, as
defined in the conformance clauses for this table. This table defined in the conformance clauses for this table. This table
is provided as a way to read 64-bit counters for agents which is provided as a way to read 64-bit counters for agents that
support only SNMPv1. support only SNMPv1.
Note that the reporting of most-significant and Note that the reporting of most-significant and
least-significant counter bits separately runs the risk of least-significant counter bits separately runs the risk of
missing an overflow of the lower bits in the interval between missing an overflow of the lower bits in the interval between
sampling. The manager must be aware of this possibility, even sampling. The manager must be aware of this possibility, even
within the same varbindlist, when interpreting the results of within the same varbindlist, when interpreting the results of
a request or asynchronous notification." a request or asynchronous notification."
::= { dot1dTp 6 } ::= { dot1dTp 6 }
dot1dTpPortOverflowEntry OBJECT-TYPE dot1dTpPortOverflowEntry OBJECT-TYPE
SYNTAX Dot1dTpPortOverflowEntry SYNTAX Dot1dTpPortOverflowEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The most significant bits of statistics counters for a high "The most significant bits of statistics counters for a high-
capacity interface of a transparent bridge. Each object is capacity interface of a transparent bridge. Each object is
associated with a corresponding object in dot1dTpPortTable associated with a corresponding object in dot1dTpPortTable
which indicates the least significant bits of the counter." that indicates the least significant bits of the counter."
INDEX { dot1dTpPort } INDEX { dot1dTpPort }
::= { dot1dTpPortOverflowTable 1 } ::= { dot1dTpPortOverflowTable 1 }
Dot1dTpPortOverflowEntry ::= Dot1dTpPortOverflowEntry ::=
SEQUENCE { SEQUENCE {
dot1dTpPortInOverflowFrames dot1dTpPortInOverflowFrames
Counter32, Counter32,
dot1dTpPortOutOverflowFrames dot1dTpPortOutOverflowFrames
Counter32, Counter32,
dot1dTpPortInOverflowDiscards dot1dTpPortInOverflowDiscards
skipping to change at page 38, line 47 skipping to change at page 36, line 5
for the Priority services." for the Priority services."
::= { pBridgeGroups 3 } ::= { pBridgeGroups 3 }
pBridgeDefaultPriorityGroup OBJECT-GROUP pBridgeDefaultPriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortDefaultUserPriority dot1dPortDefaultUserPriority
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the User Priority "A collection of objects defining the User Priority
applicable to each port for media which do not support applicable to each port for media that do not support
native User Priority." native User Priority."
::= { pBridgeGroups 4 } ::= { pBridgeGroups 4 }
pBridgeRegenPriorityGroup OBJECT-GROUP pBridgeRegenPriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dRegenUserPriority dot1dRegenUserPriority
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the User Priorities "A collection of objects defining the User Priorities
applicable to each port for media which support native applicable to each port for media that support native
User Priority." User Priority."
::= { pBridgeGroups 5 } ::= { pBridgeGroups 5 }
pBridgePriorityGroup OBJECT-GROUP pBridgePriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortNumTrafficClasses, dot1dPortNumTrafficClasses,
dot1dTrafficClass dot1dTrafficClass
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the traffic classes "A collection of objects defining the traffic classes
within a bridge for each evaluated User Priority." within a bridge for each evaluated User Priority."
::= { pBridgeGroups 6 } ::= { pBridgeGroups 6 }
pBridgeAccessPriorityGroup OBJECT-GROUP pBridgeAccessPriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortOutboundAccessPriority dot1dPortOutboundAccessPriority
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the media dependent "A collection of objects defining the media-dependent
outbound access level for each priority." outbound access level for each priority."
::= { pBridgeGroups 7 } ::= { pBridgeGroups 7 }
pBridgePortGarpGroup OBJECT-GROUP pBridgePortGarpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortGarpJoinTime, dot1dPortGarpJoinTime,
dot1dPortGarpLeaveTime, dot1dPortGarpLeaveTime,
dot1dPortGarpLeaveAllTime dot1dPortGarpLeaveAllTime
} }
STATUS current STATUS current
skipping to change at page 40, line 23 skipping to change at page 37, line 26
pBridgeHCPortGroup OBJECT-GROUP pBridgeHCPortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTpHCPortInFrames, dot1dTpHCPortInFrames,
dot1dTpHCPortOutFrames, dot1dTpHCPortOutFrames,
dot1dTpHCPortInDiscards dot1dTpHCPortInDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing 64-bit statistics "A collection of objects providing 64-bit statistics
counters for high capacity bridge ports." counters for high-capacity bridge ports."
::= { pBridgeGroups 10 } ::= { pBridgeGroups 10 }
pBridgePortOverflowGroup OBJECT-GROUP pBridgePortOverflowGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTpPortInOverflowFrames, dot1dTpPortInOverflowFrames,
dot1dTpPortOutOverflowFrames, dot1dTpPortOutOverflowFrames,
dot1dTpPortInOverflowDiscards dot1dTpPortInOverflowDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing overflow statistics "A collection of objects providing overflow statistics
counters for high capacity bridge ports." counters for high-capacity bridge ports."
::= { pBridgeGroups 11 } ::= { pBridgeGroups 11 }
pBridgePortGmrpGroup2 OBJECT-GROUP pBridgePortGmrpGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortGmrpStatus, dot1dPortGmrpStatus,
dot1dPortGmrpFailedRegistrations, dot1dPortGmrpFailedRegistrations,
dot1dPortGmrpLastPduOrigin, dot1dPortGmrpLastPduOrigin,
dot1dPortRestrictedGroupRegistration dot1dPortRestrictedGroupRegistration
} }
STATUS current STATUS current
skipping to change at page 41, line 41 skipping to change at page 38, line 41
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by the
extended bridge services with media types, such as extended bridge services with media types, such as
Ethernet, that do not support native User Priority." Ethernet, that do not support native User Priority."
GROUP pBridgeRegenPriorityGroup GROUP pBridgeRegenPriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by IEEE 802.1D the priority forwarding operations defined by IEEE 802.1D
and which have interface media types that support and that have interface media types that support
native User Priority e.g. IEEE 802.5." native User Priority, e.g., IEEE 802.5."
GROUP pBridgePriorityGroup GROUP pBridgePriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by IEEE 802.1D." the priority forwarding operations defined by IEEE 802.1D."
GROUP pBridgeAccessPriorityGroup GROUP pBridgeAccessPriorityGroup
DESCRIPTION DESCRIPTION
"This group is optional and is relevant only for devices "This group is optional and is relevant only for devices
supporting the priority forwarding operations defined by supporting the priority forwarding operations defined by
IEEE 802.1D and which have interface media types that IEEE 802.1D and that have interface media types that
support native Access Priority e.g. IEEE 802.5." support native Access Priority, e.g., IEEE 802.5."
GROUP pBridgePortGarpGroup GROUP pBridgePortGarpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting any "This group is mandatory for devices supporting any
of the GARP applications: e.g. GMRP, defined by the of the GARP applications: e.g., GMRP, defined by the
extended filtering services of 802.1D; or GVRP, extended filtering services of 802.1D; or GVRP,
defined by 802.1Q (refer to the Q-BRIDGE-MIB for defined by 802.1Q (refer to the Q-BRIDGE-MIB for
conformance statements for GVRP)." conformance statements for GVRP)."
GROUP pBridgePortGmrpGroup GROUP pBridgePortGmrpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting the "This group is mandatory for devices supporting the
GMRP application, as defined by IEEE 802.1D Extended GMRP application, as defined by IEEE 802.1D Extended
Filtering Services." Filtering Services."
GROUP pBridgeHCPortGroup GROUP pBridgeHCPortGroup
DESCRIPTION DESCRIPTION
"Support for this group in a device is mandatory for those "Support for this group in a device is mandatory for those
bridge ports which map to network interfaces that have the bridge ports that map to network interfaces that have the
value of the corresponding instance of ifSpeed value of the corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP pBridgePortOverflowGroup GROUP pBridgePortOverflowGroup
DESCRIPTION DESCRIPTION
"Support for this group in a device is mandatory for those "Support for this group in a device is mandatory for those
bridge ports which map to network interfaces that have the bridge ports that map to network interfaces that have the
value of the corresponding instance of ifSpeed value of the corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
OBJECT dot1dPortNumTrafficClasses OBJECT dot1dPortNumTrafficClasses
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1dTrafficClass OBJECT dot1dTrafficClass
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 43, line 40 skipping to change at page 40, line 37
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by the
extended bridge services with media types, such as extended bridge services with media types, such as
Ethernet, that do not support native User Priority." Ethernet, that do not support native User Priority."
GROUP pBridgeRegenPriorityGroup GROUP pBridgeRegenPriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by IEEE 802.1D the priority forwarding operations defined by IEEE 802.1D
and which have interface media types that support and that have interface media types that support
native User Priority e.g. IEEE 802.5." native User Priority, e.g., IEEE 802.5."
GROUP pBridgePriorityGroup GROUP pBridgePriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by IEEE 802.1D." the priority forwarding operations defined by IEEE 802.1D."
GROUP pBridgeAccessPriorityGroup GROUP pBridgeAccessPriorityGroup
DESCRIPTION DESCRIPTION
"This group is optional and is relevant only for devices "This group is optional and is relevant only for devices
supporting the priority forwarding operations defined by supporting the priority forwarding operations defined by
IEEE 802.1D and which have interface media types that IEEE 802.1D and that have interface media types that
support native Access Priority e.g. IEEE 802.5." support native Access Priority, e.g., IEEE 802.5."
GROUP pBridgePortGarpGroup GROUP pBridgePortGarpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting any "This group is mandatory for devices supporting any
of the GARP applications: e.g. GMRP, defined by the of the GARP applications: e.g., GMRP, defined by the
extended filtering services of 802.1D; or GVRP, extended filtering services of 802.1D; or GVRP,
defined by 802.1Q (refer to the Q-BRIDGE-MIB for defined by 802.1Q (refer to the Q-BRIDGE-MIB for
conformance statements for GVRP)." conformance statements for GVRP)."
GROUP pBridgePortGmrpGroup2 GROUP pBridgePortGmrpGroup2
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting the "This group is mandatory for devices supporting the
GMRP application, as defined by IEEE 802.1D Extended GMRP application, as defined by IEEE 802.1D Extended
Filtering Services." Filtering Services."
GROUP pBridgeHCPortGroup GROUP pBridgeHCPortGroup
DESCRIPTION DESCRIPTION
"Support for this group in a device is mandatory for those "Support for this group in a device is mandatory for those
bridge ports which map to network interfaces that have the bridge ports that map to network interfaces that have the
value of the corresponding instance of ifSpeed value of the corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP pBridgePortOverflowGroup GROUP pBridgePortOverflowGroup
DESCRIPTION DESCRIPTION
"Support for this group in a device is mandatory for those "Support for this group in a device is mandatory for those
bridge ports which map to network interfaces that have the bridge ports that map to network interfaces that have the
value of the corresponding instance of ifSpeed value of the corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
OBJECT dot1dPortNumTrafficClasses OBJECT dot1dPortNumTrafficClasses
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1dTrafficClass OBJECT dot1dTrafficClass
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 45, line 36 skipping to change at page 42, line 31
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dBasePortEntry, dot1dBasePort dot1dBridge, dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB FROM BRIDGE-MIB
EnabledStatus EnabledStatus
FROM P-BRIDGE-MIB FROM P-BRIDGE-MIB
TimeFilter TimeFilter
FROM RMON2-MIB; FROM RMON2-MIB;
qBridgeMIB MODULE-IDENTITY qBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200507290000Z" LAST-UPDATED "200601090000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org "Email: Bridge-mib@ietf.org
ietfmibs@ops.ietf.org ietfmibs@ops.ietf.org
David Levi David Levi
Postal: Nortel Networks Postal: Nortel Networks
4655 Great America Parkway 4655 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
skipping to change at page 47, line 12 skipping to change at page 43, line 48
USA USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The VLAN Bridge MIB module for managing Virtual Bridged "The VLAN Bridge MIB module for managing Virtual Bridged
Local Area Networks, as defined by IEEE 802.1Q-2003, Local Area Networks, as defined by IEEE 802.1Q-2003,
including Restricted Vlan Registration defined by including Restricted Vlan Registration defined by
IEEE 802.1u-2001 and Vlan Classification defined by IEEE 802.1u-2001 and Vlan Classification defined by
IEEE 802.1v-2001. IEEE 802.1v-2001.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXXX; See the RFC itself for this MIB module is part of RFC 4363; See the RFC itself for
full legal notices." full legal notices."
-- NOTE to RFC editor: replace XXXX with actual RFC number REVISION "200601090000Z"
-- for this document and remove this note
REVISION "200507290000Z"
DESCRIPTION DESCRIPTION
"Added Vlan TEXTUAL-CONVENTIONs, "Added Vlan TEXTUAL-CONVENTIONs,
dot1qPortRestrictedVlanRegistration, dot1vProtocol subtree, dot1qPortRestrictedVlanRegistration, dot1vProtocol subtree,
qBridgeClassificationDeviceGroup, qBridgePortGroup2, qBridgeClassificationDeviceGroup, qBridgePortGroup2,
qBridgeClassificationPortGroup, and qBridgeCompliance2. qBridgeClassificationPortGroup, and qBridgeCompliance2.
Clarified dot1qForwardAllStaticPorts, Clarified dot1qForwardAllStaticPorts,
qPortAcceptableFrameTypes, and qBridgeCompliance. qPortAcceptableFrameTypes, and qBridgeCompliance.
Deprecated qBridgePortGroup and qBridgeCompliance. " Deprecated qBridgePortGroup and qBridgeCompliance. "
REVISION "199908250000Z" REVISION "199908250000Z"
skipping to change at page 48, line 7 skipping to change at page 44, line 38
PortList ::= TEXTUAL-CONVENTION PortList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each octet within this value specifies a set of eight "Each octet within this value specifies a set of eight
ports, with the first octet specifying ports 1 through ports, with the first octet specifying ports 1 through
8, the second octet specifying ports 9 through 16, etc. 8, the second octet specifying ports 9 through 16, etc.
Within each octet, the most significant bit represents Within each octet, the most significant bit represents
the lowest numbered port, and the least significant bit the lowest numbered port, and the least significant bit
represents the highest numbered port. Thus, each port represents the highest numbered port. Thus, each port
of the bridge is represented by a single bit within the of the bridge is represented by a single bit within the
value of this object. If that bit has a value of '1' value of this object. If that bit has a value of '1',
then that port is included in the set of ports; the port then that port is included in the set of ports; the port
is not included if its bit has a value of '0'." is not included if its bit has a value of '0'."
SYNTAX OCTET STRING SYNTAX OCTET STRING
VlanIndex ::= TEXTUAL-CONVENTION VlanIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value used to index per-VLAN tables: values of 0 and "A value used to index per-VLAN tables: values of 0 and
4095 are not permitted; if the value is between 1 and 4095 are not permitted. If the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095 textual convention). If the value is greater than 4095,
then it represents a VLAN with scope local to the then it represents a VLAN with scope local to the
particular agent, i.e. one without a global VLAN-ID particular agent, i.e., one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q but it is convenient to be able to manage them IEEE 802.1Q, but it is convenient to be able to manage them
in the same way using this MIB." in the same way using this MIB."
SYNTAX Unsigned32 SYNTAX Unsigned32
VlanId ::= TEXTUAL-CONVENTION VlanId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID that uniquely identifies a VLAN. This "The VLAN-ID that uniquely identifies a VLAN. This
is the 12-bit VLAN ID used in the VLAN Tag header. is the 12-bit VLAN-ID used in the VLAN Tag header.
The range is defined by the REFERENCEd specification." The range is defined by the REFERENCEd specification."
REFERENCE REFERENCE
"IEEE Std 802.1Q 2003 Edition, Virtual Bridged "IEEE Std 802.1Q 2003 Edition, Virtual Bridged
Local Area Networks." Local Area Networks."
SYNTAX Integer32 (1..4094) SYNTAX Integer32 (1..4094)
VlanIdOrAny ::= TEXTUAL-CONVENTION VlanIdOrAny ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID that uniquely identifies a specific VLAN, "The VLAN-ID that uniquely identifies a specific VLAN,
or any VLAN. The special value of 4095 is used to or any VLAN. The special value of 4095 is used to
indicate a wildcard, i.e. any VLAN. This can be used indicate a wildcard, i.e., any VLAN. This can be used
in any situation where an object or table entry must in any situation where an object or table entry must
refer either to a specific VLAN or to any VLAN. refer either to a specific VLAN or to any VLAN.
Note that a MIB object that is defined using this Note that a MIB object that is defined using this
TEXTUAL-CONVENTION should clarify the meaning of TEXTUAL-CONVENTION should clarify the meaning of
'any VLAN' (i.e., the special value 4095)." 'any VLAN' (i.e., the special value 4095)."
SYNTAX Integer32 (1..4094 | 4095) SYNTAX Integer32 (1..4094 | 4095)
VlanIdOrNone ::= TEXTUAL-CONVENTION VlanIdOrNone ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID that uniquely identifies a specific VLAN, "The VLAN-ID that uniquely identifies a specific VLAN,
or no VLAN. The special value of zero is used to or no VLAN. The special value of zero is used to
indicate that no VLAN ID is present or used. This can indicate that no VLAN-ID is present or used. This can
be used in any situation where an object or a table entry be used in any situation where an object or a table entry
must refer either to a specific VLAN, or to no VLAN. must refer either to a specific VLAN, or to no VLAN.
Note that a MIB object that is defined using this Note that a MIB object that is defined using this
TEXTUAL-CONVENTION should clarify the meaning of TEXTUAL-CONVENTION should clarify the meaning of
'no VLAN' (i.e., the special value 0)." 'no VLAN' (i.e., the special value 0)."
SYNTAX Integer32 (0 | 1..4094) SYNTAX Integer32 (0 | 1..4094)
VlanIdOrAnyOrNone ::= TEXTUAL-CONVENTION VlanIdOrAnyOrNone ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID that uniquely identifies a specific VLAN, "The VLAN-ID that uniquely identifies a specific VLAN,
any VLAN, or no VLAN. The special values 0 and 4095 any VLAN, or no VLAN. The special values 0 and 4095
have the same meaning as described in the VlanIdOrAny have the same meaning as described in the VlanIdOrAny
and VlanIdOrNone TEXTUAL-CONVENTIONs. and VlanIdOrNone TEXTUAL-CONVENTIONs.
Note that a MIB object that is defined using this Note that a MIB object that is defined using this
TEXTUAL-CONVENTION should clarify the meaning of TEXTUAL-CONVENTION should clarify the meaning of
'any VLAN' and 'no VLAN' (i.e., the special values 'any VLAN' and 'no VLAN' (i.e., the special values
0 and 4095)." 0 and 4095)."
SYNTAX Integer32 (0 | 1..4094 | 4095) SYNTAX Integer32 (0 | 1..4094 | 4095)
skipping to change at page 50, line 26 skipping to change at page 46, line 52
supports." supports."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1" "IEEE 802.1Q/D11 Section 12.10.1.1"
::= { dot1qBase 1 } ::= { dot1qBase 1 }
dot1qMaxVlanId OBJECT-TYPE dot1qMaxVlanId OBJECT-TYPE
SYNTAX VlanId SYNTAX VlanId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum IEEE 802.1Q VLAN ID that this device "The maximum IEEE 802.1Q VLAN-ID that this device
supports." supports."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 9.3.2.3" "IEEE 802.1Q/D11 Section 9.3.2.3"
::= { dot1qBase 2 } ::= { dot1qBase 2 }
dot1qMaxSupportedVlans OBJECT-TYPE dot1qMaxSupportedVlans OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 51, line 16 skipping to change at page 47, line 40
dot1qGvrpStatus OBJECT-TYPE dot1qGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status requested by management for "The administrative status requested by management for
GVRP. The value enabled(1) indicates that GVRP should GVRP. The value enabled(1) indicates that GVRP should
be enabled on this device, on all ports for which it has be enabled on this device, on all ports for which it has
not been specifically disabled. When disabled(2), GVRP not been specifically disabled. When disabled(2), GVRP
is disabled on all ports and all GVRP packets will be is disabled on all ports, and all GVRP packets will be
forwarded transparently. This object affects all GVRP forwarded transparently. This object affects all GVRP
Applicant and Registrar state machines. A transition Applicant and Registrar state machines. A transition
from disabled(2) to enabled(1) will cause a reset of all from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on all ports. GVRP state machines on all ports.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qBase 5 } ::= { dot1qBase 5 }
skipping to change at page 52, line 38 skipping to change at page 49, line 12
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of dynamic entries in this "The current number of dynamic entries in this
Filtering Database." Filtering Database."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.1.1.3" "IEEE 802.1Q/D11 Section 12.7.1.1.3"
::= { dot1qFdbEntry 2 } ::= { dot1qFdbEntry 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Multiple Forwarding Databases for 802.1Q Transparent Devices
-- This table is an alternative to the dot1dTpFdbTable, -- This table is an alternative to the dot1dTpFdbTable,
-- previously defined for 802.1D devices that only support a
-- single Forwarding Database. -- single Forwarding Database.
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qTpFdbTable OBJECT-TYPE dot1qTpFdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpFdbEntry SYNTAX SEQUENCE OF Dot1qTpFdbEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains information about unicast entries "A table that contains information about unicast entries
for which the device has forwarding and/or filtering for which the device has forwarding and/or filtering
skipping to change at page 54, line 7 skipping to change at page 50, line 25
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Either the value '0', or the port number of the port on "Either the value '0', or the port number of the port on
which a frame having a source address equal to the value which a frame having a source address equal to the value
of the corresponding instance of dot1qTpFdbAddress has of the corresponding instance of dot1qTpFdbAddress has
been seen. A value of '0' indicates that the port been seen. A value of '0' indicates that the port
number has not been learned but that the device does number has not been learned but that the device does
have some forwarding/filtering information about this have some forwarding/filtering information about this
address (e.g. in the dot1qStaticUnicastTable). address (e.g., in the dot1qStaticUnicastTable).
Implementors are encouraged to assign the port value to Implementors are encouraged to assign the port value to
this object whenever it is learned even for addresses this object whenever it is learned, even for addresses
for which the corresponding value of dot1qTpFdbStatus is for which the corresponding value of dot1qTpFdbStatus is
not learned(3)." not learned(3)."
::= { dot1qTpFdbEntry 2 } ::= { dot1qTpFdbEntry 2 }
dot1qTpFdbStatus OBJECT-TYPE dot1qTpFdbStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
invalid(2), invalid(2),
learned(3), learned(3),
self(4), self(4),
skipping to change at page 55, line 15 skipping to change at page 51, line 29
-- Dynamic Group Registration Table -- Dynamic Group Registration Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qTpGroupTable OBJECT-TYPE dot1qTpGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpGroupEntry SYNTAX SEQUENCE OF Dot1qTpGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing filtering information for VLANs "A table containing filtering information for VLANs
configured into the bridge by (local or network) configured into the bridge by (local or network)
management, or learnt dynamically, specifying the set of management, or learned dynamically, specifying the set of
ports to which frames received on a VLAN for this FDB ports to which frames received on a VLAN for this FDB
and containing a specific Group destination address are and containing a specific Group destination address are
allowed to be forwarded." allowed to be forwarded."
::= { dot1qTp 3 } ::= { dot1qTp 3 }
dot1qTpGroupEntry OBJECT-TYPE dot1qTpGroupEntry OBJECT-TYPE
SYNTAX Dot1qTpGroupEntry SYNTAX Dot1qTpGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Filtering information configured into the bridge by "Filtering information configured into the bridge by
management, or learnt dynamically, specifying the set of management, or learned dynamically, specifying the set of
ports to which frames received on a VLAN and containing ports to which frames received on a VLAN and containing
a specific Group destination address, are allowed to be a specific Group destination address are allowed to be
forwarded. The subset of these ports learnt dynamically forwarded. The subset of these ports learned dynamically
is also provided." is also provided."
INDEX { dot1qVlanIndex, dot1qTpGroupAddress } INDEX { dot1qVlanIndex, dot1qTpGroupAddress }
::= { dot1qTpGroupTable 1 } ::= { dot1qTpGroupTable 1 }
Dot1qTpGroupEntry ::= Dot1qTpGroupEntry ::=
SEQUENCE { SEQUENCE {
dot1qTpGroupAddress dot1qTpGroupAddress
MacAddress, MacAddress,
dot1qTpGroupEgressPorts dot1qTpGroupEgressPorts
PortList, PortList,
skipping to change at page 56, line 24 skipping to change at page 52, line 37
being explicitly forwarded. This does not include ports being explicitly forwarded. This does not include ports
for which this address is only implicitly forwarded, in for which this address is only implicitly forwarded, in
the dot1qForwardAllPorts list." the dot1qForwardAllPorts list."
::= { dot1qTpGroupEntry 2 } ::= { dot1qTpGroupEntry 2 }
dot1qTpGroupLearnt OBJECT-TYPE dot1qTpGroupLearnt OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subset of ports in dot1qTpGroupEgressPorts which "The subset of ports in dot1qTpGroupEgressPorts that
were learnt by GMRP or some other dynamic mechanism, in were learned by GMRP or some other dynamic mechanism, in
this Filtering database." this Filtering database."
::= { dot1qTpGroupEntry 3 } ::= { dot1qTpGroupEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Service Requirements subtree -- Service Requirements subtree
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qForwardAllTable OBJECT-TYPE dot1qForwardAllTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardAllEntry SYNTAX SEQUENCE OF Dot1qForwardAllEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 58, line 6 skipping to change at page 54, line 15
to which all multicast group-addressed frames are to be to which all multicast group-addressed frames are to be
forwarded. Ports entered in this list will also appear forwarded. Ports entered in this list will also appear
in the complete set shown by dot1qForwardAllPorts. This in the complete set shown by dot1qForwardAllPorts. This
value will be restored after the device is reset. This value will be restored after the device is reset. This
only applies to ports that are members of the VLAN, only applies to ports that are members of the VLAN,
defined by dot1qVlanCurrentEgressPorts. A port may not defined by dot1qVlanCurrentEgressPorts. A port may not
be added in this set if it is already a member of the be added in this set if it is already a member of the
set of ports in dot1qForwardAllForbiddenPorts. The set of ports in dot1qForwardAllForbiddenPorts. The
default value is a string of ones of appropriate length, default value is a string of ones of appropriate length,
to indicate the standard behaviour of using basic to indicate the standard behaviour of using basic
filtering services, i.e. forward all multicasts to all filtering services, i.e., forward all multicasts to all
ports. ports.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
::= { dot1qForwardAllEntry 2 } ::= { dot1qForwardAllEntry 2 }
dot1qForwardAllForbiddenPorts OBJECT-TYPE dot1qForwardAllForbiddenPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 58, line 38 skipping to change at page 54, line 47
reinitializations of the management system." reinitializations of the management system."
::= { dot1qForwardAllEntry 3 } ::= { dot1qForwardAllEntry 3 }
dot1qForwardUnregisteredTable OBJECT-TYPE dot1qForwardUnregisteredTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing forwarding information for each "A table containing forwarding information for each
VLAN, specifying the set of ports to which forwarding of VLAN, specifying the set of ports to which forwarding of
multicast group-addressed frames for which there is no multicast group-addressed frames for which no
more specific forwarding information applies. This is more specific forwarding information applies. This is
configured statically by management and determined configured statically by management and determined
dynamically by GMRP. An entry appears in this table for dynamically by GMRP. An entry appears in this table for
all VLANs that are currently instantiated." all VLANs that are currently instantiated."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.2, 12.7.7" "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7"
::= { dot1qTp 5 } ::= { dot1qTp 5 }
dot1qForwardUnregisteredEntry OBJECT-TYPE dot1qForwardUnregisteredEntry OBJECT-TYPE
SYNTAX Dot1qForwardUnregisteredEntry SYNTAX Dot1qForwardUnregisteredEntry
skipping to change at page 60, line 46 skipping to change at page 56, line 51
SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing filtering information for Unicast "A table containing filtering information for Unicast
MAC addresses for each Filtering Database, configured MAC addresses for each Filtering Database, configured
into the device by (local or network) management into the device by (local or network) management
specifying the set of ports to which frames received specifying the set of ports to which frames received
from specific ports and containing specific unicast from specific ports and containing specific unicast
destination addresses are allowed to be forwarded. A destination addresses are allowed to be forwarded. A
value of zero in this table as the port number from value of zero in this table (as the port number from
which frames with a specific destination address are which frames with a specific destination address are
received, is used to specify all ports for which there received) is used to specify all ports for which there
is no specific entry in this table for that particular is no specific entry in this table for that particular
destination address. Entries are valid for unicast destination address. Entries are valid for unicast
addresses only." addresses only."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7, "IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1" ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 1 } ::= { dot1qStatic 1 }
dot1qStaticUnicastEntry OBJECT-TYPE dot1qStaticUnicastEntry OBJECT-TYPE
SYNTAX Dot1qStaticUnicastEntry SYNTAX Dot1qStaticUnicastEntry
skipping to change at page 62, line 10 skipping to change at page 58, line 10
"The destination MAC address in a frame to which this "The destination MAC address in a frame to which this
entry's filtering information applies. This object must entry's filtering information applies. This object must
take the value of a unicast address." take the value of a unicast address."
::= { dot1qStaticUnicastEntry 1 } ::= { dot1qStaticUnicastEntry 1 }
dot1qStaticUnicastReceivePort OBJECT-TYPE dot1qStaticUnicastReceivePort OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Either the value '0', or the port number of the port "Either the value '0' or the port number of the port
from which a frame must be received in order for this from which a frame must be received in order for this
entry's filtering information to apply. A value of zero entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the indicates that this entry applies on all ports of the
device for which there is no other applicable entry." device for which there is no other applicable entry."
::= { dot1qStaticUnicastEntry 2 } ::= { dot1qStaticUnicastEntry 2 }
dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports for which a frame with a specific "The set of ports for which a frame with a specific
unicast address will be flooded in the event that it unicast address will be flooded in the event that it
has not been learned. It also specifies the set of has not been learned. It also specifies the set of
ports a specific unicast address may be dynamically ports on which a specific unicast address may be dynamically
learnt on. The dot1qTpFdbTable will have an equivalent learned. The dot1qTpFdbTable will have an equivalent
entry with a dot1qTpFdbPort value of '0' until this entry with a dot1qTpFdbPort value of '0' until this
address has been learnt, when it will be updated with address has been learned, at which point it will be updated
the port the address has been seen on. This only with the port the address has been seen on. This only
applies to ports that are members of the VLAN, defined applies to ports that are members of the VLAN, defined
by dot1qVlanCurrentEgressPorts. The default value of by dot1qVlanCurrentEgressPorts. The default value of
this object is a string of ones of appropriate length. this object is a string of ones of appropriate length.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5" "IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5"
::= { dot1qStaticUnicastEntry 3 } ::= { dot1qStaticUnicastEntry 3 }
skipping to change at page 63, line 5 skipping to change at page 58, line 52
other(1), other(1),
invalid(2), invalid(2),
permanent(3), permanent(3),
deleteOnReset(4), deleteOnReset(4),
deleteOnTimeout(5) deleteOnTimeout(5)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry. "This object indicates the status of this entry.
other(1) - this entry is currently in use but other(1) - this entry is currently in use, but
the conditions under which it will remain the conditions under which it will remain
so differ from the following values. so differ from the following values.
invalid(2) - writing this value to the object invalid(2) - writing this value to the object
removes the corresponding entry. removes the corresponding entry.
permanent(3) - this entry is currently in use permanent(3) - this entry is currently in use
and will remain so after the next reset of and will remain so after the next reset of
the bridge. the bridge.
deleteOnReset(4) - this entry is currently in deleteOnReset(4) - this entry is currently in
use and will remain so until the next use and will remain so until the next
reset of the bridge. reset of the bridge.
skipping to change at page 63, line 35 skipping to change at page 59, line 33
SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing filtering information for Multicast "A table containing filtering information for Multicast
and Broadcast MAC addresses for each VLAN, configured and Broadcast MAC addresses for each VLAN, configured
into the device by (local or network) management into the device by (local or network) management
specifying the set of ports to which frames received specifying the set of ports to which frames received
from specific ports and containing specific Multicast from specific ports and containing specific Multicast
and Broadcast destination addresses are allowed to be and Broadcast destination addresses are allowed to be
forwarded. A value of zero in this table as the port forwarded. A value of zero in this table (as the port
number from which frames with a specific destination number from which frames with a specific destination
address are received, is used to specify all ports for address are received) is used to specify all ports for
which there is no specific entry in this table for that which there is no specific entry in this table for that
particular destination address. Entries are valid for particular destination address. Entries are valid for
Multicast and Broadcast addresses only." Multicast and Broadcast addresses only."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7, "IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1" ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 2 } ::= { dot1qStatic 2 }
dot1qStaticMulticastEntry OBJECT-TYPE dot1qStaticMulticastEntry OBJECT-TYPE
SYNTAX Dot1qStaticMulticastEntry SYNTAX Dot1qStaticMulticastEntry
skipping to change at page 64, line 46 skipping to change at page 60, line 42
"The destination MAC address in a frame to which this "The destination MAC address in a frame to which this
entry's filtering information applies. This object must entry's filtering information applies. This object must
take the value of a Multicast or Broadcast address." take the value of a Multicast or Broadcast address."
::= { dot1qStaticMulticastEntry 1 } ::= { dot1qStaticMulticastEntry 1 }
dot1qStaticMulticastReceivePort OBJECT-TYPE dot1qStaticMulticastReceivePort OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Either the value '0', or the port number of the port "Either the value '0' or the port number of the port
from which a frame must be received in order for this from which a frame must be received in order for this
entry's filtering information to apply. A value of zero entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the indicates that this entry applies on all ports of the
device for which there is no other applicable entry." device for which there is no other applicable entry."
::= { dot1qStaticMulticastEntry 2 } ::= { dot1qStaticMulticastEntry 2 }
dot1qStaticMulticastStaticEgressPorts OBJECT-TYPE dot1qStaticMulticastStaticEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports to which frames received from a "The set of ports to which frames received from a
specific port and destined for a specific Multicast or specific port and destined for a specific Multicast or
Broadcast MAC address must be forwarded, regardless of Broadcast MAC address must be forwarded, regardless of
any dynamic information e.g. from GMRP. A port may not any dynamic information, e.g., from GMRP. A port may not
be added in this set if it is already a member of the be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastForbiddenEgressPorts. set of ports in dot1qStaticMulticastForbiddenEgressPorts.
The default value of this object is a string of ones of The default value of this object is a string of ones of
appropriate length. appropriate length.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
::= { dot1qStaticMulticastEntry 3 } ::= { dot1qStaticMulticastEntry 3 }
dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports to which frames received from a "The set of ports to which frames received from a
specific port and destined for a specific Multicast or specific port and destined for a specific Multicast or
Broadcast MAC address must not be forwarded, regardless Broadcast MAC address must not be forwarded, regardless
of any dynamic information e.g. from GMRP. A port may of any dynamic information, e.g., from GMRP. A port may
not be added in this set if it is already a member of the not be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastStaticEgressPorts. set of ports in dot1qStaticMulticastStaticEgressPorts.
The default value of this object is a string of zeros of The default value of this object is a string of zeros of
appropriate length. appropriate length.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
::= { dot1qStaticMulticastEntry 4 } ::= { dot1qStaticMulticastEntry 4 }
dot1qStaticMulticastStatus OBJECT-TYPE dot1qStaticMulticastStatus OBJECT-TYPE
skipping to change at page 66, line 9 skipping to change at page 61, line 49
other(1), other(1),
invalid(2), invalid(2),
permanent(3), permanent(3),
deleteOnReset(4), deleteOnReset(4),
deleteOnTimeout(5) deleteOnTimeout(5)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry. "This object indicates the status of this entry.
other(1) - this entry is currently in use but other(1) - this entry is currently in use, but
the conditions under which it will remain the conditions under which it will remain
so differ from the following values. so differ from the following values.
invalid(2) - writing this value to the object invalid(2) - writing this value to the object
removes the corresponding entry. removes the corresponding entry.
permanent(3) - this entry is currently in use permanent(3) - this entry is currently in use
and will remain so after the next reset of and will remain so after the next reset of
the bridge. the bridge.
deleteOnReset(4) - this entry is currently in deleteOnReset(4) - this entry is currently in
use and will remain so until the next use and will remain so until the next
reset of the bridge. reset of the bridge.
deleteOnTimeout(5) - this entry is currently in deleteOnTimeout(5) - this entry is currently in
use and will remain so until it is aged out. use and will remain so until it is aged out.
skipping to change at page 68, line 27 skipping to change at page 64, line 15
management, in dot1qVlanStaticTable. Allocation of this management, in dot1qVlanStaticTable. Allocation of this
value follows the learning constraints defined for this value follows the learning constraints defined for this
VLAN in dot1qLearningConstraintsTable." VLAN in dot1qLearningConstraintsTable."
::= { dot1qVlanCurrentEntry 3 } ::= { dot1qVlanCurrentEntry 3 }
dot1qVlanCurrentEgressPorts OBJECT-TYPE dot1qVlanCurrentEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports that are transmitting traffic for
this VLAN as either tagged or untagged frames." this VLAN as either tagged or untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanCurrentEntry 4 } ::= { dot1qVlanCurrentEntry 4 }
dot1qVlanCurrentUntaggedPorts OBJECT-TYPE dot1qVlanCurrentUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports that are transmitting traffic for
this VLAN as untagged frames." this VLAN as untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanCurrentEntry 5 } ::= { dot1qVlanCurrentEntry 5 }
dot1qVlanStatus OBJECT-TYPE dot1qVlanStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
permanent(2), permanent(2),
dynamicGvrp(3) dynamicGvrp(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry. "This object indicates the status of this entry.
other(1) - this entry is currently in use but the other(1) - this entry is currently in use, but the
conditions under which it will remain so differ conditions under which it will remain so differ
from the following values. from the following values.
permanent(2) - this entry, corresponding to an entry permanent(2) - this entry, corresponding to an entry
in dot1qVlanStaticTable, is currently in use and in dot1qVlanStaticTable, is currently in use and
will remain so after the next reset of the will remain so after the next reset of the
device. The port lists for this entry include device. The port lists for this entry include
ports from the equivalent dot1qVlanStaticTable ports from the equivalent dot1qVlanStaticTable
entry and ports learnt dynamically. entry and ports learned dynamically.
dynamicGvrp(3) - this entry is currently in use dynamicGvrp(3) - this entry is currently in use
and will remain so until removed by GVRP. There and will remain so until removed by GVRP. There
is no static entry for this VLAN and it will be is no static entry for this VLAN, and it will be
removed when the last port leaves the VLAN." removed when the last port leaves the VLAN."
::= { dot1qVlanCurrentEntry 6 } ::= { dot1qVlanCurrentEntry 6 }
dot1qVlanCreationTime OBJECT-TYPE dot1qVlanCreationTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this VLAN was created." "The value of sysUpTime when this VLAN was created."
::= { dot1qVlanCurrentEntry 7 } ::= { dot1qVlanCurrentEntry 7 }
skipping to change at page 70, line 40 skipping to change at page 66, line 24
to identify the VLAN." to identify the VLAN."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 1 } ::= { dot1qVlanStaticEntry 1 }
dot1qVlanStaticEgressPorts OBJECT-TYPE dot1qVlanStaticEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are permanently assigned to the "The set of ports that are permanently assigned to the
egress list for this VLAN by management. Changes to a egress list for this VLAN by management. Changes to a
bit in this object affect the per-port per-VLAN bit in this object affect the per-port, per-VLAN
Registrar control for Registration Fixed for the Registrar control for Registration Fixed for the
relevant GVRP state machine on each port. A port may relevant GVRP state machine on each port. A port may
not be added in this set if it is already a member of not be added in this set if it is already a member of
the set of ports in dot1qVlanForbiddenEgressPorts. The the set of ports in dot1qVlanForbiddenEgressPorts. The
default value of this object is a string of zeros of default value of this object is a string of zeros of
appropriate length, indicating not fixed." appropriate length, indicating not fixed."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 2 } ::= { dot1qVlanStaticEntry 2 }
dot1qVlanForbiddenEgressPorts OBJECT-TYPE dot1qVlanForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are prohibited by management "The set of ports that are prohibited by management
from being included in the egress list for this VLAN. from being included in the egress list for this VLAN.
Changes to this object that cause a port to be included Changes to this object that cause a port to be included
or excluded affect the per-port per-VLAN Registrar or excluded affect the per-port, per-VLAN Registrar
control for Registration Forbidden for the relevant GVRP control for Registration Forbidden for the relevant GVRP
state machine on each port. A port may not be added in state machine on each port. A port may not be added in
this set if it is already a member of the set of ports this set if it is already a member of the set of ports
in dot1qVlanStaticEgressPorts. The default value of in dot1qVlanStaticEgressPorts. The default value of
this object is a string of zeros of appropriate length, this object is a string of zeros of appropriate length,
excluding all ports from the forbidden set." excluding all ports from the forbidden set."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 3 } ::= { dot1qVlanStaticEntry 3 }
dot1qVlanStaticUntaggedPorts OBJECT-TYPE dot1qVlanStaticUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which should transmit egress packets "The set of ports that should transmit egress packets
for this VLAN as untagged. The default value of this for this VLAN as untagged. The default value of this
object for the default VLAN (dot1qVlanIndex = 1) is a string object for the default VLAN (dot1qVlanIndex = 1) is a string
of appropriate length including all ports. There is no of appropriate length including all ports. There is no
specified default for other VLANs. If a device agent cannot specified default for other VLANs. If a device agent cannot
support the set of ports being set then it will reject the support the set of ports being set, then it will reject the
set operation with an error. An example might be if a set operation with an error. For example, a
manager attempts to set more than one VLAN to be untagged manager might attempt to set more than one VLAN to be untagged
on egress where the device does not support this IEEE 802.1Q on egress where the device does not support this IEEE 802.1Q
option." option."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 4 } ::= { dot1qVlanStaticEntry 4 }
dot1qVlanStaticRowStatus OBJECT-TYPE dot1qVlanStaticRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 72, line 16 skipping to change at page 67, line 44
dot1qNextFreeLocalVlanIndex OBJECT-TYPE dot1qNextFreeLocalVlanIndex OBJECT-TYPE
SYNTAX Integer32 (0|4096..2147483647) SYNTAX Integer32 (0|4096..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The next available value for dot1qVlanIndex of a local "The next available value for dot1qVlanIndex of a local
VLAN entry in dot1qVlanStaticTable. This will report VLAN entry in dot1qVlanStaticTable. This will report
values >=4096 if a new Local VLAN may be created or else values >=4096 if a new Local VLAN may be created or else
the value 0 if this is not possible. the value 0 if this is not possible.
A row creation operation in this table for an entry with a local A row creation operation in this table for an entry with a local
VlanIndex value may fail if the current value of this object VlanIndex value may fail if the current value of this object
is not used as the index. Even if the value read is used, is not used as the index. Even if the value read is used,
there is no guarantee that it will still be the valid index there is no guarantee that it will still be the valid index
when the create operation is attempted - another manager may when the create operation is attempted; another manager may
have already got in during the intervening time interval. have already got in during the intervening time interval.
In this case, dot1qNextFreeLocalVlanIndex should be re-read In this case, dot1qNextFreeLocalVlanIndex should be re-read
and the creation re-tried with the new value. and the creation re-tried with the new value.
This value will automatically change when the current value is This value will automatically change when the current value is
used to create a new row." used to create a new row."
::= { dot1qVlan 4 } ::= { dot1qVlan 4 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Port Configuration Table -- The VLAN Port Configuration Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qPortVlanTable OBJECT-TYPE dot1qPortVlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanEntry SYNTAX SEQUENCE OF Dot1qPortVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port control and status "A table containing per-port control and status
information for VLAN configuration in the device." information for VLAN configuration in the device."
::= { dot1qVlan 5 } ::= { dot1qVlan 5 }
dot1qPortVlanEntry OBJECT-TYPE dot1qPortVlanEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanEntry SYNTAX Dot1qPortVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information controlling VLAN configuration for a port "Information controlling VLAN configuration for a port
on the device. This is indexed by dot1dBasePort." on the device. This is indexed by dot1dBasePort."
skipping to change at page 73, line 29 skipping to change at page 69, line 8
MacAddress, MacAddress,
dot1qPortRestrictedVlanRegistration dot1qPortRestrictedVlanRegistration
TruthValue TruthValue
} }
dot1qPvid OBJECT-TYPE dot1qPvid OBJECT-TYPE
SYNTAX VlanIndex SYNTAX VlanIndex
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PVID, the VLAN ID assigned to untagged frames or "The PVID, the VLAN-ID assigned to untagged frames or
Priority-Tagged frames received on this port. Priority-Tagged frames received on this port.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1" "IEEE 802.1Q/D11 Section 12.10.1.1"
DEFVAL { 1 } DEFVAL { 1 }
::= { dot1qPortVlanEntry 1 } ::= { dot1qPortVlanEntry 1 }
dot1qPortAcceptableFrameTypes OBJECT-TYPE dot1qPortAcceptableFrameTypes OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
admitAll(1), admitAll(1),
admitOnlyVlanTagged(2) admitOnlyVlanTagged(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this is admitOnlyVlanTagged(2) the device will "When this is admitOnlyVlanTagged(2), the device will
discard untagged frames or Priority-Tagged frames discard untagged frames or Priority-Tagged frames
received on this port. When admitAll(1), untagged received on this port. When admitAll(1), untagged
frames or Priority-Tagged frames received on this port frames or Priority-Tagged frames received on this port
will be accepted and assigned to a VID based on the will be accepted and assigned to a VID based on the
PVID and VID Set for this port. PVID and VID Set for this port.
This control does not affect VLAN independent BPDU This control does not affect VLAN-independent Bridge
frames, such as GVRP and STP. It does affect VLAN Protocol Data Unit (BPDU) frames, such as GVRP and
Spanning Tree Protocol (STP). It does affect VLAN-
dependent BPDU frames, such as GMRP. dependent BPDU frames, such as GMRP.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.3" "IEEE 802.1Q/D11 Section 12.10.1.3"
DEFVAL { admitAll } DEFVAL { admitAll }
::= { dot1qPortVlanEntry 2 } ::= { dot1qPortVlanEntry 2 }
dot1qPortIngressFiltering OBJECT-TYPE dot1qPortIngressFiltering OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this is true(1) the device will discard incoming "When this is true(1), the device will discard incoming
frames for VLANs which do not include this Port in its frames for VLANs that do not include this Port in its
Member set. When false(2), the port will accept all Member set. When false(2), the port will accept all
incoming frames. incoming frames.
This control does not affect VLAN independent BPDU This control does not affect VLAN-independent BPDU
frames, such as GVRP and STP. It does affect VLAN frames, such as GVRP and STP. It does affect VLAN-
dependent BPDU frames, such as GMRP. dependent BPDU frames, such as GMRP.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.4" "IEEE 802.1Q/D11 Section 12.10.1.4"
DEFVAL { false } DEFVAL { false }
::= { dot1qPortVlanEntry 3 } ::= { dot1qPortVlanEntry 3 }
dot1qPortGvrpStatus OBJECT-TYPE dot1qPortGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of GVRP operation on this port. The value "The state of GVRP operation on this port. The value
enabled(1) indicates that GVRP is enabled on this port, enabled(1) indicates that GVRP is enabled on this port,
as long as dot1qGvrpStatus is also enabled for this as long as dot1qGvrpStatus is also enabled for this
device. When disabled(2) but dot1qGvrpStatus is still device. When disabled(2) but dot1qGvrpStatus is still
enabled for the device, GVRP is disabled on this port: enabled for the device, GVRP is disabled on this port:
any GVRP packets received will be silently discarded, and
any GVRP packets received will be silently discarded and
no GVRP registrations will be propagated from other no GVRP registrations will be propagated from other
ports. This object affects all GVRP Applicant and ports. This object affects all GVRP Applicant and
Registrar state machines on this port. A transition Registrar state machines on this port. A transition
from disabled(2) to enabled(1) will cause a reset of all from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on this port. GVRP state machines on this port.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qPortVlanEntry 4 } ::= { dot1qPortVlanEntry 4 }
skipping to change at page 76, line 21 skipping to change at page 71, line 43
dot1qPortVlanStatisticsTable OBJECT-TYPE dot1qPortVlanStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per-port, per-VLAN statistics for "A table containing per-port, per-VLAN statistics for
traffic received. Separate objects are provided for both the traffic received. Separate objects are provided for both the
most-significant and least-significant bits of statistics most-significant and least-significant bits of statistics
counters for ports that are associated with this transparent counters for ports that are associated with this transparent
bridge. The most-significant bit objects are only required on bridge. The most-significant bit objects are only required on
high capacity interfaces, as defined in the conformance clauses high-capacity interfaces, as defined in the conformance clauses
for these objects. This mechanism is provided as a way to read for these objects. This mechanism is provided as a way to read
64-bit counters for agents which support only SNMPv1. 64-bit counters for agents that support only SNMPv1.
Note that the reporting of most-significant and least- Note that the reporting of most-significant and least-
significant counter bits separately runs the risk of missing significant counter bits separately runs the risk of missing
an overflow of the lower bits in the interval between sampling. an overflow of the lower bits in the interval between sampling.
The manager must be aware of this possibility, even within the The manager must be aware of this possibility, even within the
same varbindlist, when interpreting the results of a request or same varbindlist, when interpreting the results of a request or
asynchronous notification." asynchronous notification."
::= { dot1qVlan 6 } ::= { dot1qVlan 6 }
dot1qPortVlanStatisticsEntry OBJECT-TYPE dot1qPortVlanStatisticsEntry OBJECT-TYPE
skipping to change at page 77, line 18 skipping to change at page 72, line 38
dot1qTpVlanPortInOverflowDiscards dot1qTpVlanPortInOverflowDiscards
Counter32 Counter32
} }
dot1qTpVlanPortInFrames OBJECT-TYPE dot1qTpVlanPortInFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames received by this port from "The number of valid frames received by this port from
its segment which were classified as belonging to this its segment that were classified as belonging to this
VLAN. Note that a frame received on this port is VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a counted by this object if and only if it is for a
protocol being processed by the local forwarding process protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)." (e.g., GMRP, but not GVRP or STP."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanStatisticsEntry 1 } ::= { dot1qPortVlanStatisticsEntry 1 }
dot1qTpVlanPortOutFrames OBJECT-TYPE dot1qTpVlanPortOutFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames transmitted by this port to "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated VLAN. This includes bridge management frames originated
by this device which are classified as belonging to this by this device that are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g., GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanStatisticsEntry 2 } ::= { dot1qPortVlanStatisticsEntry 2 }
dot1qTpVlanPortInDiscards OBJECT-TYPE dot1qTpVlanPortInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames received by this port from "The number of valid frames received by this port from
its segment which were classified as belonging to this its segment that were classified as belonging to this
VLAN which were discarded due to VLAN related reasons. VLAN and that were discarded due to VLAN-related reasons.
Specifically, the IEEE 802.1Q counters for Discard Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering." Inbound and Discard on Ingress Filtering."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3" "IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 3 } ::= { dot1qPortVlanStatisticsEntry 3 }
dot1qTpVlanPortInOverflowFrames OBJECT-TYPE dot1qTpVlanPortInOverflowFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 78, line 49 skipping to change at page 74, line 19
dot1qTpVlanPortInDiscards counter has overflowed." dot1qTpVlanPortInDiscards counter has overflowed."
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 6 } ::= { dot1qPortVlanStatisticsEntry 6 }
dot1qPortVlanHCStatisticsTable OBJECT-TYPE dot1qPortVlanHCStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port, per VLAN statistics for "A table containing per-port, per-VLAN statistics for
traffic on high capacity interfaces." traffic on high-capacity interfaces."
::= { dot1qVlan 7 } ::= { dot1qVlan 7 }
dot1qPortVlanHCStatisticsEntry OBJECT-TYPE dot1qPortVlanHCStatisticsEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanHCStatisticsEntry SYNTAX Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Traffic statistics for a VLAN on a high capacity "Traffic statistics for a VLAN on a high-capacity
interface." interface."
INDEX { dot1dBasePort, dot1qVlanIndex } INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanHCStatisticsTable 1 } ::= { dot1qPortVlanHCStatisticsTable 1 }
Dot1qPortVlanHCStatisticsEntry ::= Dot1qPortVlanHCStatisticsEntry ::=
SEQUENCE { SEQUENCE {
dot1qTpVlanPortHCInFrames dot1qTpVlanPortHCInFrames
Counter64, Counter64,
dot1qTpVlanPortHCOutFrames dot1qTpVlanPortHCOutFrames
Counter64, Counter64,
dot1qTpVlanPortHCInDiscards dot1qTpVlanPortHCInDiscards
Counter64 Counter64
} }
dot1qTpVlanPortHCInFrames OBJECT-TYPE dot1qTpVlanPortHCInFrames OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames received by this port from "The number of valid frames received by this port from
its segment which were classified as belonging to this its segment that were classified as belonging to this
VLAN. Note that a frame received on this port is VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a counted by this object if and only if it is for a
protocol being processed by the local forwarding process protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)." (e.g., GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanHCStatisticsEntry 1 } ::= { dot1qPortVlanHCStatisticsEntry 1 }
dot1qTpVlanPortHCOutFrames OBJECT-TYPE dot1qTpVlanPortHCOutFrames OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames transmitted by this port to "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated VLAN. This includes bridge management frames originated
by this device which are classified as belonging to this by this device that are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g., GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanHCStatisticsEntry 2 } ::= { dot1qPortVlanHCStatisticsEntry 2 }
dot1qTpVlanPortHCInDiscards OBJECT-TYPE dot1qTpVlanPortHCInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames received by this port from "The number of valid frames received by this port from
its segment which were classified as belonging to this its segment that were classified as belonging to this
VLAN which were discarded due to VLAN related reasons. VLAN and that were discarded due to VLAN-related reasons.
Specifically, the IEEE 802.1Q counters for Discard Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering." Inbound and Discard on Ingress Filtering."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3" "IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanHCStatisticsEntry 3 } ::= { dot1qPortVlanHCStatisticsEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Learning Constraints Table -- The VLAN Learning Constraints Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 81, line 46 skipping to change at page 77, line 9
dot1qConstraintType OBJECT-TYPE dot1qConstraintType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
independent(1), independent(1),
shared(2) shared(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of constraint this entry defines. "The type of constraint this entry defines.
independent(1) - the VLAN, dot1qConstraintVlan, independent(1) - the VLAN, dot1qConstraintVlan,
uses an independent filtering database from all uses a filtering database independent from all
other VLANs in the same set, defined by other VLANs in the same set, defined by
dot1qConstraintSet. dot1qConstraintSet.
shared(2) - the VLAN, dot1qConstraintVlan, shares shared(2) - the VLAN, dot1qConstraintVlan, shares
the same filtering database as all other VLANs the same filtering database as all other VLANs
in the same set, defined by dot1qConstraintSet." in the same set, defined by dot1qConstraintSet."
::= { dot1qLearningConstraintsEntry 3 } ::= { dot1qLearningConstraintsEntry 3 }
dot1qConstraintStatus OBJECT-TYPE dot1qConstraintStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 84, line 24 skipping to change at page 79, line 30
"The identification of the protocol above the data-link "The identification of the protocol above the data-link
layer in a Protocol Template. Depending on the layer in a Protocol Template. Depending on the
frame type, the octet string will have one of the frame type, the octet string will have one of the
following values: following values:
For 'ethernet', 'rfc1042' and 'snap8021H', For 'ethernet', 'rfc1042' and 'snap8021H',
this is the 16-bit (2-octet) IEEE 802.3 Type Field. this is the 16-bit (2-octet) IEEE 802.3 Type Field.
For 'snapOther', For 'snapOther',
this is the 40-bit (5-octet) PID. this is the 40-bit (5-octet) PID.
For 'llcOther', For 'llcOther',
this is the 2-octet IEEE 802.2 LSAP pair: this is the 2-octet IEEE 802.2 Link Service Access
first octet for DSAP and second octet for SSAP." Point (LSAP) pair: first octet for Destination Service
Access Point (DSAP) and second octet for Source Service
Access Point (SSAP)."
REFERENCE REFERENCE
"IEEE 802.1v clause 8.6.2" "IEEE 802.1v clause 8.6.2"
::= { dot1vProtocolGroupEntry 2 } ::= { dot1vProtocolGroupEntry 2 }
dot1vProtocolGroupId OBJECT-TYPE dot1vProtocolGroupId OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a group of protocols that are associated "Represents a group of protocols that are associated
skipping to change at page 86, line 42 skipping to change at page 81, line 46
qBridgeBaseGroup OBJECT-GROUP qBridgeBaseGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanVersionNumber, dot1qVlanVersionNumber,
dot1qMaxVlanId, dot1qMaxVlanId,
dot1qMaxSupportedVlans, dot1qMaxSupportedVlans,
dot1qNumVlans, dot1qNumVlans,
dot1qGvrpStatus dot1qGvrpStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing device level control "A collection of objects providing device-level control
and status information for the Virtual LAN bridge and status information for the Virtual LAN bridge
services." services."
::= { qBridgeGroups 1 } ::= { qBridgeGroups 1 }
qBridgeFdbUnicastGroup OBJECT-GROUP qBridgeFdbUnicastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qFdbDynamicCount, dot1qFdbDynamicCount,
dot1qTpFdbPort, dot1qTpFdbPort,
dot1qTpFdbStatus dot1qTpFdbStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
unicast addresses, learnt dynamically or statically unicast addresses, learned dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 2 } ::= { qBridgeGroups 2 }
qBridgeFdbMulticastGroup OBJECT-GROUP qBridgeFdbMulticastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpGroupEgressPorts, dot1qTpGroupEgressPorts,
dot1qTpGroupLearnt dot1qTpGroupLearnt
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
multicast addresses, learnt dynamically or statically multicast addresses, learned dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 3 } ::= { qBridgeGroups 3 }
qBridgeServiceRequirementsGroup OBJECT-GROUP qBridgeServiceRequirementsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qForwardAllPorts, dot1qForwardAllPorts,
dot1qForwardAllStaticPorts, dot1qForwardAllStaticPorts,
dot1qForwardAllForbiddenPorts, dot1qForwardAllForbiddenPorts,
dot1qForwardUnregisteredPorts, dot1qForwardUnregisteredPorts,
dot1qForwardUnregisteredStaticPorts, dot1qForwardUnregisteredStaticPorts,
dot1qForwardUnregisteredForbiddenPorts dot1qForwardUnregisteredForbiddenPorts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
service requirements, learnt dynamically or statically service requirements, learned dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 4 } ::= { qBridgeGroups 4 }
qBridgeFdbStaticGroup OBJECT-GROUP qBridgeFdbStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qStaticUnicastAllowedToGoTo, dot1qStaticUnicastAllowedToGoTo,
dot1qStaticUnicastStatus, dot1qStaticUnicastStatus,
dot1qStaticMulticastStaticEgressPorts, dot1qStaticMulticastStaticEgressPorts,
dot1qStaticMulticastForbiddenEgressPorts, dot1qStaticMulticastForbiddenEgressPorts,
dot1qStaticMulticastStatus dot1qStaticMulticastStatus
skipping to change at page 89, line 6 skipping to change at page 84, line 4
OBJECTS { OBJECTS {
dot1qPvid, dot1qPvid,
dot1qPortAcceptableFrameTypes, dot1qPortAcceptableFrameTypes,
dot1qPortIngressFiltering, dot1qPortIngressFiltering,
dot1qPortGvrpStatus, dot1qPortGvrpStatus,
dot1qPortGvrpFailedRegistrations, dot1qPortGvrpFailedRegistrations,
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing port level VLAN "A collection of objects providing port-level VLAN
control and status information for all ports." control and status information for all ports."
::= { qBridgeGroups 8 } ::= { qBridgeGroups 8 }
qBridgeVlanStatisticsGroup OBJECT-GROUP qBridgeVlanStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpVlanPortInFrames, dot1qTpVlanPortInFrames,
dot1qTpVlanPortOutFrames, dot1qTpVlanPortOutFrames,
dot1qTpVlanPortInDiscards dot1qTpVlanPortInDiscards
} }
STATUS current STATUS current
skipping to change at page 89, line 33 skipping to change at page 84, line 31
qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpVlanPortInOverflowFrames, dot1qTpVlanPortInOverflowFrames,
dot1qTpVlanPortOutOverflowFrames, dot1qTpVlanPortOutOverflowFrames,
dot1qTpVlanPortInOverflowDiscards dot1qTpVlanPortInOverflowDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing overflow counters for "A collection of objects providing overflow counters for
per-port packet statistics for all VLANs currently configured per-port packet statistics for all VLANs currently configured
on this device for high capacity interfaces, defined as those on this device for high-capacity interfaces, defined as those
that have the value of the corresponding instance of that have the value of the corresponding instance of
ifSpeed greater than 650,000,000 bits/second." ifSpeed greater than 650,000,000 bits/second."
::= { qBridgeGroups 10 } ::= { qBridgeGroups 10 }
qBridgeVlanHCStatisticsGroup OBJECT-GROUP qBridgeVlanHCStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpVlanPortHCInFrames, dot1qTpVlanPortHCInFrames,
dot1qTpVlanPortHCOutFrames, dot1qTpVlanPortHCOutFrames,
dot1qTpVlanPortHCInDiscards dot1qTpVlanPortHCInDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per-port packet "A collection of objects providing per-port packet
statistics for all VLANs currently configured on this statistics for all VLANs currently configured on this
device for high capacity interfaces, defined as those device for high-capacity interfaces, defined as those
that have the value of the corresponding instance of that have the value of the corresponding instance of
ifSpeed greater than 650,000,000 bits/second." ifSpeed greater than 650,000,000 bits/second."
::= { qBridgeGroups 11 } ::= { qBridgeGroups 11 }
qBridgeLearningConstraintsGroup OBJECT-GROUP qBridgeLearningConstraintsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qConstraintType, dot1qConstraintType,
dot1qConstraintStatus dot1qConstraintStatus
} }
STATUS current STATUS current
skipping to change at page 90, line 26 skipping to change at page 85, line 22
::= { qBridgeGroups 12 } ::= { qBridgeGroups 12 }
qBridgeLearningConstraintDefaultGroup OBJECT-GROUP qBridgeLearningConstraintDefaultGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qConstraintSetDefault, dot1qConstraintSetDefault,
dot1qConstraintTypeDefault dot1qConstraintTypeDefault
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the default Filtering "A collection of objects defining the default Filtering
Database constraints for VLANs which have no specific Database constraints for VLANs that have no specific
constraints defined." constraints defined."
::= { qBridgeGroups 13 } ::= { qBridgeGroups 13 }
qBridgeClassificationDeviceGroup OBJECT-GROUP qBridgeClassificationDeviceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1vProtocolGroupId, dot1vProtocolGroupId,
dot1vProtocolGroupRowStatus dot1vProtocolGroupRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 91, line 17 skipping to change at page 86, line 10
dot1qPvid, dot1qPvid,
dot1qPortAcceptableFrameTypes, dot1qPortAcceptableFrameTypes,
dot1qPortIngressFiltering, dot1qPortIngressFiltering,
dot1qPortGvrpStatus, dot1qPortGvrpStatus,
dot1qPortGvrpFailedRegistrations, dot1qPortGvrpFailedRegistrations,
dot1qPortGvrpLastPduOrigin, dot1qPortGvrpLastPduOrigin,
dot1qPortRestrictedVlanRegistration dot1qPortRestrictedVlanRegistration
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing port level VLAN "A collection of objects providing port-level VLAN
control and status information for all ports." control and status information for all ports."
::= { qBridgeGroups 16 } ::= { qBridgeGroups 16 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- compliance statements -- compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
qBridgeCompliance MODULE-COMPLIANCE qBridgeCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for device support of Virtual "The compliance statement for device support of Virtual
LAN Bridge services. LAN Bridge services.
RFC2674 was silent about the expected persistence of the RFC2674 was silent about the expected persistence of the
read-write objects in this MIB module. Applications MUST read-write objects in this MIB module. Applications MUST
NOT assume that the values of the read-write objects are NOT assume that the values of the read-write objects are
persistent across reinitializations of the management persistent across reinitializations of the management
system, and MUST NOT assume that the values are not system and MUST NOT assume that the values are not
persistent across reinitializations of the management persistent across reinitializations of the management
system." system."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
qBridgeBaseGroup, qBridgeBaseGroup,
qBridgeVlanGroup, qBridgeVlanGroup,
qBridgeVlanStaticGroup, qBridgeVlanStaticGroup,
qBridgePortGroup qBridgePortGroup
} }
skipping to change at page 92, line 29 skipping to change at page 87, line 22
GROUP qBridgeVlanStatisticsGroup GROUP qBridgeVlanStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support." implementation cost associated with its support."
GROUP qBridgeVlanStatisticsOverflowGroup GROUP qBridgeVlanStatisticsOverflowGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support. It is most implementation cost associated with its support. It is most
relevant for high capacity interfaces where the SNMP agent relevant for high-capacity interfaces where the SNMP agent
supports only SNMPv1." supports only SNMPv1."
GROUP qBridgeVlanHCStatisticsGroup GROUP qBridgeVlanHCStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support. It is most implementation cost associated with its support. It is most
relevant for high capacity interfaces." relevant for high-capacity interfaces."
GROUP qBridgeLearningConstraintsGroup GROUP qBridgeLearningConstraintsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices implementing "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the VLAN Learning (SVL) modes of operation of the
filtering database, as defined by IEEE 802.1Q." filtering database, as defined by IEEE 802.1Q."
GROUP qBridgeLearningConstraintDefaultGroup GROUP qBridgeLearningConstraintDefaultGroup
DESCRIPTION DESCRIPTION
skipping to change at page 94, line 36 skipping to change at page 89, line 24
GROUP qBridgeVlanStatisticsGroup GROUP qBridgeVlanStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support." implementation cost associated with its support."
GROUP qBridgeVlanStatisticsOverflowGroup GROUP qBridgeVlanStatisticsOverflowGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support. It is most implementation cost associated with its support. It is most
relevant for high capacity interfaces where the SNMP agent relevant for high-capacity interfaces where the SNMP agent
supports only SNMPv1." supports only SNMPv1."
GROUP qBridgeVlanHCStatisticsGroup GROUP qBridgeVlanHCStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional as there may be significant "This group is optional as there may be significant
implementation cost associated with its support. It is most implementation cost associated with its support. It is most
relevant for high capacity interfaces." relevant for high-capacity interfaces."
GROUP qBridgeLearningConstraintsGroup GROUP qBridgeLearningConstraintsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices implementing "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the VLAN Learning (SVL) modes of operation of the
filtering database, as defined by IEEE 802.1Q." filtering database, as defined by IEEE 802.1Q."
GROUP qBridgeLearningConstraintDefaultGroup GROUP qBridgeLearningConstraintDefaultGroup
DESCRIPTION DESCRIPTION
skipping to change at page 97, line 5 skipping to change at page 91, line 5
OBJECT dot1vProtocolGroupRowStatus OBJECT dot1vProtocolGroupRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required as this is an optional "Write access is not required as this is an optional
capability in IEEE 802.1v." capability in IEEE 802.1v."
::= { qBridgeCompliances 2 } ::= { qBridgeCompliances 2 }
END END
6. Acknowledgments 6. Acknowledgements
Much of the groundwork for this document was performed by the IEEE Much of the groundwork for this document was performed by the IEEE
802.1 working group during the definition of the IEEE 802.1D updates 802.1 working group during the definition of the IEEE 802.1D updates
[802.1D] and IEEE 802.1Q [802.1Q]. [802.1D] and IEEE 802.1Q [802.1Q].
The authors wish to thank the members of the Bridge Working Group, The authors wish to thank the members of the Bridge Working Group,
and David Harrington, Anders SW Christensen, Andrew Smith, Paul and David Harrington, Anders SW Christensen, Andrew Smith, Paul
Langille, Anil Rijhsinghani, and Keith McCloghrie in particular for Langille, Anil Rijhsinghani, and Keith McCloghrie in particular for
their comments and suggestions which improved this effort. their comments and suggestions, which improved this effort.
Editing for the final draft was done by David Levi. Editing for the final version was done by David Levi.
The new textual conventions related to VLAN-IDs were produced as a The new textual conventions related to VLAN-IDs were produced as a
result of a review of the use of VLAN-ID in several MIB modules. result of a review of the use of VLAN-ID in several MIB modules.
Further investigation found that VLAN-ID objects were defined in a Further investigation found that VLAN-ID objects were defined in a
few other MIB modules. The editor would like to thank all who few other MIB modules. The editor would like to thank all who
contributed to the discussion which resulted in these new textual contributed to the discussion that resulted in these new textual
conventions. Specifically Bert Wijnen, Les Bell, Andrew Smith, Mike conventions. Specifically, Bert Wijnen, Les Bell, Andrew Smith, Mike
Heard, Randy Presuhn, Dan Romascanu, Eduardo Cardona, Tom Petch, Heard, Randy Presuhn, Dan Romascanu, Eduardo Cardona, Tom Petch,
Juergen Schoenwaelder, Richard Woundy, Tony Jeffree and William Juergen Schoenwaelder, Richard Woundy, Tony Jeffree, and William
Murwin. We also received input and feedback from IEEE confirming Murwin. We also received input and feedback from IEEE confirming
that the values 0 and 4095 are not used for identifying a specific that the values 0 and 4095 are not used for identifying a specific
VLAN-ID and so can be used to represent none or a wildcard (see VLAN-ID and so can be used to represent none or a wildcard (see
Appendix A). Appendix A).
7. IANA Considerations 7. Security Considerations
There are no special considerations for IANA related to this draft.
The MIB modules in this document are updates to MIB modules with
previously assigned IANA identifiers.
8. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These tables and objects and their network operations. These tables and objects and their
sensitivity/vulnerability are described below. sensitivity/vulnerability are described below.
The following tables and objects in the P-BRIDGE-MIB can be The following tables and objects in the P-BRIDGE-MIB can be
skipping to change at page 100, line 5 skipping to change at page 93, line 23
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. Normative References 8. Normative References
[BRIDGE-MIB] Norseth, K., and E. Bell, editors "Definitions of [BRIDGE-MIB] Norseth, K. and E. Bell, "Definitions of Managed Objects
Managed Objects for Bridges", RFC 1493bis, February 2005. for Bridges", RFC 4188, September 2005.
-- NOTE to RFC Ed.: please replace 1493bis with actual RFC [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
number, update the reference and remove this note "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Structure of Management "Textual Conventions for SMIv2", STD 58, RFC 2579, April
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Textual Conventions for "Conformance Statements for SMIv2", STD 58, RFC 2580,
SMIv2", STD 58, RFC 2579, April 1999. 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.
[RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A., and
McCloghrie, "Definitions of Managed Objects for Bridges K. McCloghrie, "Definitions of Managed Objects for
with Traffic Classes, Multicast Filtering and Virtual LAN Bridges with Traffic Classes, Multicast Filtering and
Extensions", RFC 2674, August 1999. Virtual LAN Extensions", RFC 2674, August 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3418] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
"Management Information Base (MIB) for the Simple Network Simple Network Management Protocol (SNMP)", STD 62, RFC
Management Protocol (SNMP)", STD 62, RFC 3418, March 1991. 3418, December 2002.
[802.1D] "Information technology - Telecommunications and [802.1D] "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications -
3: Media Access Control (MAC) Bridges: Revision. This is Part 3: Media Access Control (MAC) Bridges: Revision.
a revision of ISO/IEC 10038: 1993, 802.1j-1992 and This is a revision of ISO/IEC 10038: 1993, 802.1j-1992
802.6k-1992. It incorporates P802.11c, P802.1p and and 802.6k-1992. It incorporates P802.11c, P802.1p and
P802.12e." ISO/IEC 15802-3: 1998. P802.12e." ISO/IEC 15802-3: 1998.
[802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and [802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and
Metropolitan Area Networks: Virtual Bridged Local Area Metropolitan Area Networks: Virtual Bridged Local Area
Networks", 2003. Networks", 2003.
[802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D)
Standard for Information technology - Telecommunications IEEE Standard for Information technology -
and information exchange between systems - Local and Telecommunications and information exchange between
metropolitan area networks - Common specifications - Part systems - Local and metropolitan area networks - Common
3: Media Access Control (MAC) Bridges: Technical and specifications - Part 3: Media Access Control (MAC)
Editorial Corrections". Bridges: Technical and Editorial Corrections".
[802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q) IEEE [802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q)
Standard for Local and metropolitan area networks - Virtual IEEE Standard for Local and metropolitan area networks -
Bridged Local Area Networks - Amendment 1: Technical and Virtual Bridged Local Area Networks - Amendment 1:
Editorial Corrections". Technical and Editorial Corrections".
[802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE [802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q)
Standards for Local and Metropolitan Area Networks: Virtual IEEE Standards for Local and Metropolitan Area Networks:
Bridged Local Area Networks--Amendment 2: VLAN Virtual Bridged Local Area Networks--Amendment 2: VLAN
Classification by Protocol and Port". Classification by Protocol and Port".
10. Informative References 9. Informative References
[RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K.
McCloghrie, "Definitions of Managed Objects for Bridges", McCloghrie, "Definitions of Managed Objects for
RFC 1493, July 1993. Bridges", RFC 1493, July 1993.
[I-D.ietf-ipcdn-qos-mib] Patrick, M. and W. Murwin, "Data Over Cable [RFC4323] Patrick, M. and W. Murwin, "Data Over Cable System
System Interface Specification Quality of Service Interface Specification Quality of Service Management
Management Information Base (DOCSIS-QOS MIB)", draft-ietf- Information Base (DOCSIS-QOS MIB)", RFC 4323, January
ipcdn-qos-mib (work in progress), February 2005. 2006.
-- NOTE to RFC Editor: please replace with appropriate RFC [RFC4149] Kalbfleisch, C., Cole, R., and D. Romascanu, "Definition
reference. of Managed Objects for Synthetic Sources for Performance
Monitoring Algorithms", RFC 4149, August 2005.
[I-D.ietf-rmonmib-sspm-mib] Kalbfleisch, C., Cole, R. and D. Romascanu, [RFC2613] Waterman, R., Lahaye, B., Romascanu, D., and S.
"Definition of Managed Objects for Synthetic Sources for Waldbusser, "Remote Network Monitoring MIB Extensions
Performance Monitoring Algorithms.", draft-ietf-rmonmib- for Switched Networks Version 1.0", RFC 2613, June 1999.
sspm-mib-12 (work in progress), June 2004.
-- NOTE to RFC Editor: please replace with appropriate RFC [RFC3318] Sahita, R., Hahn, S., Chan, K., and K. McCloghrie,
reference. "Framework Policy Information Base", RFC 3318, March
2003.
[RFC2613] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Remote Network Monitoring MIB Extensions for Switched "Introduction and Applicability Statements for
Networks Version 1.0", RFC 2613, June 1999. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3318] Sahita, R., Hahn, S., Chan, K. and K. McCloghrie, Appendix A. Email from Tony Jeffrey from IEEE
"Framework Policy Information Base", RFC 3318, March 2003.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, -----Original Message-----
"Introduction and Applicability Statements for Internet- From: Tony Jeffree [mailto:tony@jeffree.co.uk]
Standard Management Framework", RFC 3410, December 2002. Sent: Friday, 6th of June 2003 17:16
To: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Subject: RE: VLAn ID
11. Contact Information Bert et al -
We have concluded that the use of 4095 as a wildcard is acceptable
to 802.1, and we will make any necessary changes to 802.1Q in due
course to relax the current stated restriction. However, we need
to know whether that is all that needs to be done to 802.1Q - i.e.,
is there any need to change our definitions of the managed objects
in the document (Clause 12) to reflect the interpretation of 4095
as a wildcard, or is this simply an issue for the SNMP machinery
to handle?
Regards,
Tony
Authors' Adresses
David Levi David Levi
Nortel Networks Nortel Networks
4655 Great America Parkway 4655 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Phone: +1 865 686 0432 Phone: +1 865 686 0432
Email: dlevi@nortel.com EMail: dlevi@nortel.com
David Harrington David Harrington
Effective Software Effective Software
50 Harding Rd. 50 Harding Rd.
Portsmouth, NH 03801 Portsmouth, NH 03801
USA USA
Phone: +1 603 436 8634 Phone: +1 603 436 8634
Email: ietfdbh@comcast.net EMail: ietfdbh@comcast.net
Vivian Ngai Vivian Ngai
Salt lake City, UT Salt lake City, UT
USA USA
Email: vivian_ngai@acm.org EMail: vivian_ngai@acm.org
Les Bell Les Bell
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
EMail: elbell@ntlworld.com EMail: elbell@ntlworld.com
Andrew Smith Andrew Smith
Beijing Harbour Networks Beijing Harbour Networks
Jiuling Building Jiuling Building
21 North Xisanhuan Ave. 21 North Xisanhuan Ave.
Beijing, 100089 Beijing, 100089
PRC PRC
Fax: +1 415 345 1827 Fax: +1 415 345 1827
EMail: ah_smith@acm.org EMail: ah_smith@acm.org
Paul Langille Paul Langille
Newbridge Networks Newbridge Networks
5 Corporate Drive 5 Corporate Drive
Andover, MA 01810 Andover, MA 01810
USA USA
Phone: +1 978 691 4665 Phone: +1 978 691 4665
EMail: langille@newbridge.com EMail: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
skipping to change at page 104, line 28 skipping to change at page 98, line 18
USA USA
Phone: +1 978 691 4665 Phone: +1 978 691 4665
EMail: langille@newbridge.com EMail: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Accton Technology Corporation Accton Technology Corporation
5 Mount Royal Ave 5 Mount Royal Ave
Marlboro, MA 01752 Marlboro, MA 01752
USA USA
Email: anil@accton.com EMail: anil@accton.com
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 408 526 5260 Phone: +1 408 526 5260
EMail: kzm@cisco.com EMail: kzm@cisco.com
Appendix A. Email from Tony Jeffrey from IEEE Full Copyright Statement
-----Original Message-----
From: Tony Jeffree [mailto:tony@jeffree.co.uk]
Sent: Friday, 6th of June 2003 17:16
To: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Subject: RE: VLAn ID
Bert et al -
We have concluded that the use of 4095 as a wildcard is acceptable
to 802.1, and we will make any necessary changes to 802.1Q in due
course to relax the current stated restriction. However, we need
to know whether that is all that needs to be done to 802.1Q - i.e.,
is there any need to change our definitions of the managed objects
in the document (Clause 12) to reflect the interpretation of 4095
as a wildcard, or is this simply an issue for the SNMP machinery
to handle?
Regards,
Tony
Copyright Statement Copyright (C) The Internet Society (2006).
Copyright (C) The Internet Society (2005). This document is subject This document is subject to the rights, licenses and restrictions
to the rights, licenses and restrictions contained in BCP 78, and contained in BCP 78, and except as set forth therein, the authors
except as set forth therein, the authors retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Disclaimer of Validity Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 213 change blocks. 
435 lines changed or deleted 406 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/