Network Working Group E. Beili
Internet-Draft Actelis Networks
Intended status: Standards Track M. Morgenstern
Expires: August 28, 2007 ECI Telecom
N. Nair
Wipro Technologies
February 24, 2007
xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-00.txt
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
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 28, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP based internets.
This document proposes an extension to the Interfaces Group MIB with
a set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
Beili, et al. Expires August 28, 2007 [Page 1]
Internet-Draft G.Bond MIB February 2007
G.998.1, G.998.2 and G.998.3. The MIB modules specific to each
bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and
GBOND-TDIM-MIB respectively.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 4
3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4
4. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
4.1. Relation to Interfaces Group MIB module . . . . . . . . . 5
4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5
4.1.2. G.Bond Aggregation Function (GAF) . . . . . . . . . . 7
4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9
4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
4.2. Relation to xDSL MIB modules . . . . . . . . . . . . . . . 11
4.3. Mapping of DSL Forum WT-157 Managed Objects . . . . . . . 11
5. xDSL multi-pair bonding MIB Definitions . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . . . 33
Beili, et al. Expires August 28, 2007 [Page 2]
Internet-Draft G.Bond MIB February 2007
1. Introduction
The xDSL Multi-Pair Bonding, allows a service provider to provide
high bandwidth services to business and residential customers over
multiple xDSL lines, with greater speed and resiliency, than the
service over a single xDSL line, bridging the gap between xDSL and
fiber-based transport.
There are three xDSL Multi-Pair Bonding schemes, also known under
collective name G.Bond:
o The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1
recommendation [G.998.1], which defines a method for bonding (or
aggregating) of multiple xDSL lines (or individual bearer channels
in multiple xDSL lines) into a single bi-directional logical link
carrying an ATM stream. This specification can be viewed as an
evolution of the legacy Inverse Multiplexing over ATM (IMA)
technology [af-phy-0086], applied to xDSL with variable rates on
each line/bearer channel.
o The Ethernet-Based Multi-Pair Bonding, specified in ITU-T G.998.2
recommendation [G.998.2], which defines a method for bonding (or
aggregating) of multiple xDSL lines (or individual bearer channels
in multiple xDSL lines) into a single bi-directional logical link
carrying an Ethernet stream. This specification can be viewed as
IEEE 802.3-2005 [802.3] Clause 61 Physical Medium Entity (PME)
Aggregation, generalized to work over any xDSL technology.
(2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL and
VDSL technology respectively).
o The Multi-pair bonding using time-division inverse multiplexing
(TDIM), specified in ITU-T G.998.3 recommendation [G.998.3], which
defines a method for bonding (or aggregating) of multiple xDSL
lines into a single bi-directional logical link carrying a mix of
various traffic streams (e.g. Ethernet, ATM, TDM).
Architecturally all three bonding schemes define a new "bonded"
Transport Protocol Specific - Transmission Convergence (TPS-TC) sub-
layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC
(clear channel) sub-layers for the ATM, Ethernet or TDIM bonding
respectively. Each underlying TPS-TC sub-layer represents a protocol
specific gamma-interface to an xDSL line or an individual bearer
channel of an xDSL line. Bonding of multiple bearer channels in the
same xDSL line is not allowed.
All schemes allow bonding of up to 32 individual line/channel sub-
layers with variable rates, providing common functionality for the
configuration, initialization, operation and monitoring of the bonded
Beili, et al. Expires August 28, 2007 [Page 3]
Internet-Draft G.Bond MIB February 2007
link.
This document defines a MIB module common to all 3 schemes.
Additional managed objects, specific to each bonding technology, are
defined in GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib], GBOND-ETH-
MIB [I-D.ietf-adslmib-gbond-eth-mib] and GBOND-TDIM-MIB
[I-D.ietf-adslmib-gbond-tdim-mib] modules.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. The DSL Forum Management Framework for xDSL Bonding
This document makes use of the DSL Forum technical report Management
Framework for xDSL Bonding [WT-157], defining a management model and
a hierarchy of management objects for the bonded xDSL interfaces.
4. Relation to other MIB modules
This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs.
Specifically, the following MIB modules are discussed: Interfaces
Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB)
Interface Stack Capability MIB (IF-CAP-STACK-MIB), G.Bond scheme
specific modules: G.Bond/ATM (GBOND-ATM-MIB), G.Bond/Ethernet (GBOND-
ETH-MIB) and G.Bond/TDIM (GBOND-TDIM-MIB), and DSL specific MIB
modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL
(HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE-
MIB).
Beili, et al. Expires August 28, 2007 [Page 4]
Internet-Draft G.Bond MIB February 2007
4.1. Relation to Interfaces Group MIB module
A bonded xDSL port is a stacked (a.k.a. aggregated or bonded)
interface and as such is managed using generic interface management
objects defined in the IF-MIB [RFC2863].
The stack management, i.e. actual connection of the sub-layers to the
top layer interface, is done via the ifStackTable, as defined in the
IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the
IF-INVERTED-STACK-MIB [RFC2864].
The ifCapStackTable and its inverse ifInvCapStackTable defined in the
IF-CAP-STACK-MIB [I-D.ietf-hubmib-efm-cu-mib], extend the stack
management with an ability to describe possible connections or cross-
connect capability, when a flexible cross-connect matrix is present
between the interface layers.
4.1.1. Layering Model
A G.Bond interface can aggregate up to 32 channel sub-layers, with
each channel representing an xDSL line or an xDSL bearer channel.
For the purpose of brevity we will refer to the bonded interface as
Generic Bonded Sub-layer (GBS) and to the channel sub-layer as
Bonding Channel Entity (BCE).
A generic G.Bond device can have a number of GBS ports, each
connected to a particular upper layer (e.g. Media Access Control
(MAC) interface for G.998.2 scheme), while simultaneously cross-
connected to a number of underlying BCEs, with a single GBS per BCE
relationship.
A GBS port is represented in the Interface table (ifTable) as a
separate interface with an ifType of g9981, g9982 or g9983 for a
particular bonding scheme.
Each BCE in the aggregated GBS port is represented in the ifTable as
a separate interface with an ifType relevant to a particular xDSL
technology, e.g. shdsl(169) or vdsl(97). The ifType values are
defined in [IANAifType-MIB].
Beili, et al. Expires August 28, 2007 [Page 5]
Internet-Draft G.Bond MIB February 2007
The following figure shows the layering diagram and corresponding use
of ifTable for the bonded xDSL interfaces:
.-----------------------------. -
| GBS | ^ 1 ifEntry
| (TPS-TC) | v ifType: g9981, g9982 or g9983
+-----------------+---+-------+ -
| TPS-TC \ | | | ^
+---------\ | | | |
| PMS-TC )BCE 1 |...| BCE N | ) N ifEntry (N=1..32)
+---------/ | | | | ifType: adsl(94), shdsl(169),
| PMD / | | | v vdsl(97), etc.
'-----------------+---+-------' -
BCE - Bonding Channel Entity
GBS - Generic Bonded Sub-layer
PMD - Physical Medium Dependent
TPS-TC - Transport Protocol Specific - Transmission Convergence
PMS-TC - Physical Media Specific - Transmission Convergence
Figure 1: Use of ifTable for bonded xDSL interfaces
The ifStackTable is indexed by the ifIndex values of the aggregated
G.Bond port (GBS) and the BCEs connected to it. ifStackTable allows a
Network Management application to determine which BCEs are connected
to a particular GBS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby
determine which GBS runs on top of a particular BCE.
The ifCapStackTable defined in the IF-CAP-STACK-MIB module, specifies
for each higher-layer interface (e.g. GBS port) a list of lower-
layer interfaces (e.g. BCEs), which can possibly be cross-connected
to that higher-layer interface, determined by the cross-connect
capability of the device. This table, modeled after ifStackTable, is
read only, reflecting current cross-connect capability of a stacked
interface, which can be dynamic in some implementations (e.g. if xDSL
lines are located on a pluggable module and the module is pulled
out). Note that BCE availability per GBS, described by
ifCapStackTable, can be constrained by other parameters, for example
by aggregation capacity of a GBS or by the BCE in question being
already connected to another GBS. So, in order to ensure that a
particular BCE can be connected to the GBS, all respective parameters
(e.g. ifCapStackTable, ifStackTable and gBondCapacity) SHALL be
inspected.
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
Beili, et al. Expires August 28, 2007 [Page 6]
Internet-Draft G.Bond MIB February 2007
describes which higher-layer interfaces (e.g. GBS ports) can
possibly be connected to a particular lower-layer interface (e.g.
BCE), providing inverted mapping of ifCapStackTable. While it
contains no additional information beyond that already contained in
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface.
4.1.2. G.Bond Aggregation Function (GAF)
The G.Bond Aggregation Function (GAF) allows a number of BCEs to be
aggregated onto a GBS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple BCEs and assembling the
original frames at the remote GBS port. GAF is OPTIONAL, meaning
that a device with a single BCE MAY perform fragmentation and re-
assembly if this function is supported by the device. Note however
that the agent is REQUIRED to report on the GAF capability for all
types of G.Bond ports (ATM, Ethernet and TDIM).
The GBOND-MIB module allows a Network Management application to query
GAF capability and enable/disable it if supported. Note that
enabling GAF effectively turns on fragmentation and re-assembly, even
on a single-BCE port.
4.1.3. Discovery Operation
The G.Bond ports may optionally support discovery operation, whereby
BCEs, during initialization, exchange information about their
respective aggregation groups (GBS). This information can then be
used to detect copper misconnections or for an automatic assignment
of the local BCEs into aggregation groups instead of a fixed pre-
configuration.
The MIB module defined in this document allow a Network Management
application to control G.Bond Discovery mechanism and query its
results. Note that the Discovery mechanism can work only if GAF is
supported and enabled.
Two tables are used by the G.Bond Discovery mechanism: ifStackTable
and ifCapStackTable. The following pseudo-code gives an example of
the Discovery and automatic BCE assignment for a generic multi-GBS
G.Bond device, located at Central Office (CO), using objects defined
in this MIB module, IF-CAP-STACK-MIB and IF-MIB modules [Note that
automatic BCE assignment is only shown here for the purposes of the
example. Fixed BCE pre-assignment, manual assignment or auto-
Beili, et al. Expires August 28, 2007 [Page 7]
Internet-Draft G.Bond MIB February 2007
assignment using an alternative internal algorithm may be chosen by a
particular implementation]:
// Go over all GBS ports in the CO device
FOREACH gbs[i] IN CO_device
{ // Perform discovery and auto-assignment on GBS ports
// with room for more Channels
IF ( gbs[i].NumBCEs < gbs[i].BondCapacity )
{ dc = gbs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per GBS
// Go over all disconnected Channels, which can
// pottentially be connected to the GBS
FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND
NOT ifInvStackTable[bce[j]] // not connected
{ // Try to grab the remote RT_device, by writing the value
// of the local 6 Byte discovery code to the remote
// discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it
// would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the BCE
// is indeed marked as being the CO_device peer.
bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = bce[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity)
{ // Remote RT_device connected via BCE[j] is/was a peer
// for GBS[i] and there room for another BCE in the
// GBS[i] aggregation group (max. Bonding capacity is
// not reached yet).
// Connect this BCE to the GBS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is
// updated automatically)
ADD bce[j] TO ifStackTable[gbs[i]];
// gbs[i] is auto-added to ifInvStackTable[bce[j]]
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
// Discover all other disconnected BCEs,
// attached to the same RT_device and connect them to
// the GBS provided there is enough room for more BCEs.
FOREACH bce[k] IN ifCapStackTable[gbs[i]] and
NOT ifInvStackTable[bce[k]]
{ r = bce[k].RemoteDiscoveryCode; // Get
IF ( r == dc AND
gbs[i].NumBCEs < gbs[i].BondCapacity)
{ ADD bce[k] TO ifStackTable[gbs[i]];
// gbs[i] is added TO ifInvStackTable[bce[k]]
gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
}
}
}
Beili, et al. Expires August 28, 2007 [Page 8]
Internet-Draft G.Bond MIB February 2007
// At this point we have discovered all local BCEs which
// are physically connected to the same remote RT_device
// and connected them to GBS[i]. Go to the next GBS.
BREAK;
}
}
}
An SNMP Agent for a G.Bond device builds ifCapStackTable and its
inverse ifInvCapStackTable on device initialiation, according to the
cross-connect capabilities of the device.
Adding a BCE to the ifStackTable row for a specific GBS, involves
actual connection of the BCE to the GBS.
Note that GBS port does not have to be operationally 'down' for the
connection to succeed. In fact, a dynamic BCE addition (and removal)
MAY be implemented with an available BCE being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally
'up' GBS port, by modifying a respective ifStackTable (and respective
ifInvStackTable) entry.
It is RECOMMENDED that a removal of the last operationally 'up' BCE
from an operationally 'up' GBS would be rejected by the
implementation, as this action would completely drop the link.
4.1.4. G.Bond ports initialization
G.Bond ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise on
the line is too high, that 'training' process may fail to achieve a
specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state
of a GBS with all the BCEs connected to it or of an individual BCE
port. Setting this object to 'up' instructs a particular GBS or a
BCE to start initialization process, which may take tens of seconds
for G.Bond ports. The ifOperStatus object shows the operational
state of an interface (extended by ifMauMediaAvailable object from
MAU-MIB for GBS and *Status object from a relevant line MIB for BCE
interfaces).
A disconnected BCE may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the GBS
initializes all BCEs connected to that particular GBS. Note that in
Beili, et al. Expires August 28, 2007 [Page 9]
Internet-Draft G.Bond MIB February 2007
case of bonding some interfaces may fail to initialize while others
succeed. The GBS is considered operationally 'up' if at least one
bonded BCE is operationally 'up'. When all BCEs connected to the GBS
are 'down' the GBS SHALL be considered operationally
'lowerLayerDown'. The GBS SHALL be considered operationally
'notPresent' if it is not connected to any BCE. The GBS/BCE
interface SHALL remain operationally 'down' during initialization.
4.1.5. Usage of ifTable
Both BCE and GBS interfaces are managed using interface specific
management objects defined in the GBOND-MIB module and generic
interface objects from the ifTable of IF-MIB, with all management
table entries referenced by the interface index ifIndex.
The following table summarizes G.Bond specific interpretations for
some of the ifTable objects specified by the mandatory
ifGeneralInformationGroup:
+---------------+---------------------------------------------------+
| IF-MIB object | G.Bond interpretation |
+---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each BCE and each GBS |
| | in the G.Bond PHY MUST have a unique index, as |
| | there some GBS and BCE specific attributes |
| | accessible only on the GBS or BCE level. |
+---------------+---------------------------------------------------+
| ifType | g9981, g9982 or g9982 for the ATM, Ethernet or |
| | TDIM GBS respectively, shdsl(169) for G.SHDSL |
| | BCE, vdsl(97) for VDSL BCE etc. |
+---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the BCE. For the GBS it |
| | is the sum of the current operating data rates of |
| | all BCEs in the aggregation group, without the |
| | encapsulation overhead and G.Bond overhead, but |
| | accounting for the Inter-Frame Gaps (IFG). When a |
| | GBS or a BCE is operating in an assymetrical |
| | fashion (upstream data rate differs from the |
| | downstream one) the lowest of the values is |
| | shown. |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a |
| | particular GBS (with all BCEs connected to it) or |
| | a BCE to start initialization process |
+---------------+---------------------------------------------------+
Beili, et al. Expires August 28, 2007 [Page 10]
Internet-Draft G.Bond MIB February 2007
+---------------+---------------------------------------------------+
| ifOperStatus | a relevant *Status object from a particular line |
| | MIB supplements the 'down' value of ifOperStatus |
| | for BCEs. |
+---------------+---------------------------------------------------+
Table 1: G.Bond interpretation of IF-MIB objects
4.2. Relation to xDSL MIB modules
Each xDSL technology is described in a relevant xDSL line MIB module:
e.g. HDSL2-SHDSL-LINE-MIB [RFC4319] for G.SHDSL, ADSL-LINE-EXT-MIB
[RFC3440] for ADSL, ADSL2-LINE-MIB [RFC4706] for ADSL2, VDSL-LINE-MIB
[RFC3728] for VDSL or VDSL2-LINE-MIB [I-D.ietf-adslmib-vsl2-mib] for
VDSL2.
These MIBs are used to manage individual xDSL lines/channels (BCEs).
4.3. Mapping of DSL Forum WT-157 Managed Objects
This section contains the mapping between relevant managed objects
(attributes) defined in [WT-157] and managed objects defined in this
document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
+----------------------------------------+--------------------------+
| G.Bond Managed Object | Corresponding SNMP |
| | Object |
+----------------------------------------+--------------------------+
| oBondingGroup - Basic Package | |
| (Mandatory) | |
+----------------------------------------+--------------------------+
| aGroupID | ifIndex (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupBondScheme | ifType (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupPeerBondScheme | |
+----------------------------------------+--------------------------+
| aGroupEnd | gBondPhySide |
+----------------------------------------+--------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupStatus | gBondStatus |
+----------------------------------------+--------------------------+
| aGroupName | ifName (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupCapacity | gBondCapacity |
Beili, et al. Expires August 28, 2007 [Page 11]
Internet-Draft G.Bond MIB February 2007
| aGroupNumChannels | gBondNumBCEs |
+----------------------------------------+--------------------------+
| aGroupUpRate | gBondUpDataRate |
+----------------------------------------+--------------------------+
| aGroupDownRate | gBondDownDataRate |
+----------------------------------------+--------------------------+
| aGroupTargetUpRate | gBondTargetUpDataRate |
+----------------------------------------+--------------------------+
| aGroupTargetDownRate | gBondTargetDownDataRate |
+----------------------------------------+--------------------------+
| aGroupCapacity | gBondCapacity |
+----------------------------------------+--------------------------+
| TBC... | TBC... |
+----------------------------------------+--------------------------+
Table 2: Mapping of WT-157 Managed Objects
5. xDSL multi-pair bonding MIB Definitions
GBOND-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, Gauge32, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863
;
gBondMIB MODULE-IDENTITY
LAST-UPDATED "200702240000Z" -- February 24, 2007
ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/adslmib-charter.html
Mailing Lists:
General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address
Beili, et al. Expires August 28, 2007 [Page 12]
Internet-Draft G.Bond MIB February 2007
Chair: Menachem Dodge
Postal: ECI Telecom, Ltd.
30 Hasivim St.,
Petach-Tikva 49517
Israel
Tel: +972-3-926-8421
E-mail: menachem.dodge@ecitele.com
Editor: Edward Beili
Postal: Actelis Networks, Inc.
25 Bazel St., P.O.B. 10173
Petach-Tikva 10173
Israel
Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com"
DESCRIPTION
"The objects in this MIB module are used to manage the
multi-pair bonded xDSL Interfaces, defined in ITU-T
recommendations G.998.1, G.998.2 and G.998.3.
This MIB module MUST be used in conjunction with a bonding
scheme specific MIB module, that is, GBOND-ATM-MIB,
GBOND-ETH-MIB or GBOND-TDIM-MIB.
The following references are used throughout this MIB module:
[G.998.1] refers to:
ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding',
January 2005.
[G.998.2] refers to:
ITU-T Recommendation G.998.1: 'Ethernet-based multi-pair
bonding', January 2005.
[G.998.3] refers to:
ITU-T Recommendation G.998.1: 'Multi-pair bonding using
time-division inverse multiplexing', January 2005.
[WT-157] refers to:
DSL Forum Technical Report: 'Management Framework for xDSL
Bonding', January 2007.
Naming Conventions:
BCE - Bonding Channel Entity
CO - Central Office
CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer
Beili, et al. Expires August 28, 2007 [Page 13]
Internet-Draft G.Bond MIB February 2007
SNR - Signal to Noise Ratio
Copyright (C) The Internet Society (2007). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200702240000Z" -- February 24, 2007
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note
::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note.
-- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D
gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 }
gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 }
-- Groups in the module
gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 }
-- Textual Conventions
TruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with
possible values of true(1) and false(2). This
extension permits the additional value of unknown(0), which
can be returned as a result of GET operation, when an exact
true or false value of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }
-- Port Notifications Group
gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 }
gBondLowUpRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here since we are under specific GBS
Beili, et al. Expires August 28, 2007 [Page 14]
Internet-Draft G.Bond MIB February 2007
gBondUpDataRate,
gBondThreshLowUpRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port' upstream
data rate has reached/dropped below or exceeded the low
upstream rate threshold, specified by gBondThreshLowUpRate.
This notification MAY be send for the -O subtype ports
while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R
subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and
gBondLowUpRateCrossing notifications to be sent.
The adaptive nature of the G.Bond technology allows the port
to adapt itself to the changes in the copper environment,
e.g. an impulse noise, alien crosstalk or a micro-interruption
may temporarily drop one or more BCEs in the aggregation
group, causing a rate degradation of the aggregated G.Bond
link. The dropped BCEs would then try to re-initialize,
possibly at a lower rate than before, adjusting the rate to
provide required target SNR margin.
Generation of this notification is controlled by the
gBondLowRateCrossingEnable object."
::= { gBondPortNotifications 1 }
gBondLowDownRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here since we are under specific GBS
gBondDownDataRate,
gBondThreshLowDownRate
}
STATUS current
DESCRIPTION
"This notification indicates that the G.Bond port' downstream
data rate has reached/dropped below or exceeded the low
downstream rate threshold, specified by
gBondThreshLowDownRate.
This notification MAY be send for the -O subtype ports
Beili, et al. Expires August 28, 2007 [Page 15]
Internet-Draft G.Bond MIB February 2007
while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R
subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and
gBondLowDownRateCrossing notifications to be sent.
The adaptive nature of the G.Bond technology allows the port
to adapt itself to the changes in the copper environment,
e.g. an impulse noise, alien crosstalk or a micro-interruption
may temporarily drop one or more BCEs in the aggregation
group, causing a rate degradation of the aggregated G.Bond
link. The dropped BCEs would then try to re-initialize,
possibly at a lower rate than before, adjusting the rate to
provide required target SNR margin.
Generation of this notification is controlled by the
gBondLowRateCrossingEnable object."
::= { gBondPortNotifications 2}
-- G.Bond Port (BCS) group
gBondPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of G.Bond GBS ports. Entries in this
table MUST be maintained in a persistent manner"
::= { gBondPort 1 }
gBondPortConfEntry OBJECT-TYPE
SYNTAX GBondPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Configuration table.
Each entry represents an G.Bond port indexed by the ifIndex.
Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { gBondPortConfTable 1 }
GBondPortConfEntry ::=
Beili, et al. Expires August 28, 2007 [Page 16]
Internet-Draft G.Bond MIB February 2007
SEQUENCE {
gBondDiscoveryCode PhysAddress,
gBondTargetUpDataRate Unsigned32,
gBondTargetDownDataRate Unsigned32,
gBondThreshLowUpRate Unsigned32,
gBondThreshLowDownRate Unsigned32,
gBondLowRateCrossingEnable TruthValue
}
gBondDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A Discovery Code of the G.Bond port (GBS).
A unique 6 octet long code used by the Discovery function.
This object MUST be instantiated for the -O subtype GBS before
writing operations on the gBondRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by BCEs
associated with the GBS.
The initial value of this object for -R subtype ports after
reset is all zeroes. For -R subtype ports, the value of this
object cannot be changed directly. This value may be changed
as a result of writing operation on the
gBondRemoteDiscoveryCode object of remote BCE of -O
subtype, connected to one of the local BCEs associated with
the GBS.
Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or
Initializing."
REFERENCE
"[802.3] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, 61A.2"
::= { gBondPortConfEntry 1 }
gBondTargetUpDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A desired G.Bond port Data Rate in the upstream direction,
in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective
configuration settings.
This object represents a sum of individual BCE upstream data
rates, modified to compensate for fragmentation and
Beili, et al. Expires August 28, 2007 [Page 17]
Internet-Draft G.Bond MIB February 2007
encapsulation overhead (e.g. for an Ethernet service, the
target data rate of 10Mbps SHALL allow lossless transmission
of full-duplex 10Mbps Ethernet frame stream with minimal
inter-frame gap).
Note that the target upstream data rate may not be achieved
during initialization (e.g. due to unavailability of required
BCEs) or the initial bandwidth could deteriorate, so that the
actual upstream data rate (gBondUpDataRate) could be less
than gBondTargetUpDataRate.
The value between 1 and 1000000 indicates that the total
upstream data rate of the G.Bond port after initialization
SHALL be equal to the target data rate or less, if the target
upstream data rate cannot be achieved under the restrictions
configured for BCEs. In case the copper environment allows to
achieve higher upstream data rate than that specified by this
object, the excess capability SHALL be either converted to
additional SNR margin or reclaimed by minimizing transmit
power.
The value of 9999999 means that the target data rate is not
fixed and SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin per BCE.
This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes.
Changing of the Target Upstream Data Rate MUST be performed
when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing.
This object MUST be maintained in a persistent manner."
::= { gBondPortConfEntry 2 }
gBondTargetDownDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A desired G.Bond port Data Rate in the downstream direction,
in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective
configuration settings.
This object represents a sum of individual BCE downstream data
rates, modified to compensate for fragmentation and
Beili, et al. Expires August 28, 2007 [Page 18]
Internet-Draft G.Bond MIB February 2007
encapsulation overhead (e.g. for an Ethernet service, the
target data rate of 10Mbps SHALL allow lossless transmission
of full-duplex 10Mbps Ethernet frame stream with minimal
inter-frame gap).
Note that the target downstream data rate may not be achieved
during initialization (e.g. due to unavailability of required
BCEs) or the initial bandwidth could deteriorate, so that the
actual downstream data rate (gBondDownDataRate) could be less
than gBondTargetDownDataRate.
The value between 1 and 1000000 indicates that the total
downstream data rate of the G.Bond port after initialization
SHALL be equal to the target data rate or less, if the target
downstream data rate cannot be achieved under the restrictions
configured for BCEs. In case the copper environment allows to
achieve higher downstream data rate than that specified by
this object, the excess capability SHALL be either converted
to additional SNR margin or reclaimed by minimizing transmit
power.
The value of 9999999 means that the target data rate is not
fixed and SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin per BCE.
This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes.
Changing of the Target Downstream Data Rate MUST be performed
when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing.
This object MUST be maintained in a persistent manner."
::= { gBondPortConfEntry 3 }
gBondThreshLowUpRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object configures the G.Bond port low upstream rate
crossing alarm threshold. When the current value of
gBondUpDataRate for this port reaches/drops below or exceeds
this threshold, an gBondLowUpRateCrossing notification MAY be
generated if enabled by gBondLowRateCrossingEnable.
Beili, et al. Expires August 28, 2007 [Page 19]
Internet-Draft G.Bond MIB February 2007
This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner."
::= { gBondPortConfEntry 4 }
gBondThreshLowDownRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object configures the G.Bond port low downstream rate
crossing alarm threshold. When the current value of
gBondDownDataRate for this port reaches/drops below or exceeds
this threshold, an gBondLowDownRateCrossing notification MAY
be generated if enabled by gBondLowRateCrossingEnable.
This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner."
::= { gBondPortConfEntry 5 }
gBondLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether gBondLowUpRateCrossing and
gBondLowDownRateCrossing notifications should be generated
for this interface.
Value of true(1) indicates that the notifications are enabled.
Value of false(2) indicates that the notifications are
disabled.
This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner."
::= { gBondPortConfEntry 6 }
gBondPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
Beili, et al. Expires August 28, 2007 [Page 20]
Internet-Draft G.Bond MIB February 2007
DESCRIPTION
"Table for Capabilities of G.Bond Ports. Entries in this table
MUST be maintained in a persistent manner"
::= { gBondPort 2 }
gBondPortCapabilityEntry OBJECT-TYPE
SYNTAX GBondPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Capability table.
Each entry represents an G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { gBondPortCapabilityTable 1 }
GBondPortCapabilityEntry ::=
SEQUENCE {
gBondPeerBond TruthValueOrUnknown,
gBondCapacity Unsigned32,
gBondPeerCapacity Unsigned32
}
gBondPeerBond OBJECT-TYPE
SYNTAX TruthValueOrUnknown
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Bonding Capability of the G.Bond port (GBS) link partner.
This object has a value of true(1) when the remote GBS
supports the same bonding scheme as the local port.
A value of false(2) is returned when the remote GBS does not
support the same bonding scheme.
Ports whose peers cannot be reached because of the link
state, SHALL return a value if unknown(0).
This object maps to the WT-157 attribute aGroupPeerBndScheme."
REFERENCE
"[WT-157] 5.5.1.3"
::= { gBondPortCapabilityEntry 1 }
gBondCapacity OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of BCEs that can be aggregated by the local GBS.
Beili, et al. Expires August 28, 2007 [Page 21]
Internet-Draft G.Bond MIB February 2007
The number of BCEs currently assigned to a particular G.Bond
port (gBondNumBCEs) is never greater than gBondCapacity.
This object maps to the WT-157 attribute aGroupCapacity."
REFERENCE
"[WT-157] 5.5.1.8"
::= { gBondPortCapabilityEntry 2 }
gBondPeerCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of BCEs that can be aggregated by the peer GBS port.
Value of 0 is returned when peer Bonding Capacity is unknown
(peer cannot be reached).
This object maps to the WT-157 attribute
aGroupRemoteCapacity."
REFERENCE
"[WT-157] 5.5.1.9"
::= { gBondPortCapabilityEntry 3 }
gBondPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides overall status information of G.Bond
ports, complementing the generic status information from the
ifTable of IF-MIB. Additional status information about
connected BCEs is available from the relevant line MIBs
This table contains live data from the equibcent. As such,
it is NOT persistent."
::= { gBondPort 3 }
gBondPortStatusEntry OBJECT-TYPE
SYNTAX GBondPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond Port Status table.
Each entry represents an G.Bond port indexed by the ifIndex.
Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
Beili, et al. Expires August 28, 2007 [Page 22]
Internet-Draft G.Bond MIB February 2007
::= { gBondPortStatusTable 1 }
GBondPortStatusEntry ::=
SEQUENCE {
gBondUpDataRate Gauge32,
gBondDownDataRate Gauge32,
gBondFltStatus BITS,
gBondPortSide INTEGER,
gBondNumBCEs Unsigned32
}
gBondUpDataRate OBJECT-TYPE
SYNTAX Gauge32
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A current G.Bond port operational Data Rate in the upstream
direction, in bps.
This object represents an estimation of the sum of individual
BCE upstream data rates, modified to compensate for
fragmentation and encapsulation overhead (e.g. for an Ethernet
service, the target data rate of 10Mbps SHALL allow lossless
transmission of full-duplex 10Mbps Ethernet frame stream with
minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed."
::= { gBondPortStatusEntry 1 }
gBondDownDataRate OBJECT-TYPE
SYNTAX Gauge32
UNITS "bps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A current G.Bond port operational Data Rate in the downstream
direction, in bps.
This object represents an estimation of the sum of individual
BCE downstream data rates, modified to compensate for
fragmentation and encapsulation overhead (e.g. for an Ethernet
service, the target data rate of 10Mbps SHALL allow lossless
transmission of full-duplex 10Mbps Ethernet frame stream with
minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed."
::= { gBondPortStatusEntry 2 }
Beili, et al. Expires August 28, 2007 [Page 23]
Internet-Draft G.Bond MIB February 2007
gBondFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
bceSubTypeMismatch(2),
lowRate(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond (GBS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are:
noPeer - peer PHY cannot be reached (e.g.
no BCEs attached, all BCEs are Down
etc.).
peerPowerLoss - peer PHY has indicated impending unit
failure due to loss of local power
('Dying Gasp').
bceSubTypeMismatch - local BCEs in the aggregation group
are not of the same sub-type, e.g.
some BCEs in the local device are -O
while others are -R subtype.
lowRate - gBondUpRate/gBondDownRate of the port
has reached or dropped below
gBondThreshLowUpRate/
gBondThreshLowUpRate.
This object is intended to supplement ifOperStatus object
in IF-MIB and ifMauMediaAvailable in MAU-MIB."
REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable"
::= { gBondPortStatusEntry 3 }
gBondPortSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"G.Bond port mode of operation (subtype).
The value of 'subscriber' indicates the port is designated as
'-R' subtype (all BCEs assigned to this port are of subtype
'-R').
The value of the 'office' indicates that the port is
designated as '-O' subtype (all BCEs assigned to this port are
Beili, et al. Expires August 28, 2007 [Page 24]
Internet-Draft G.Bond MIB February 2007
of subtype '-O').
The value of 'unknown' indicates that the port has no assigned
BCEs yet or that the assigned BCEs are not of the same side
(subTypeBCEMismatch).
This object maps to the WT-157 attribute aGroupEnd."
REFERENCE
"[WT-157] 5.5.1.6"
::= { gBondPortStatusEntry 4 }
gBondNumBCEs OBJECT-TYPE
SYNTAX Unsigned32 (0..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of BCEs that is currently aggregated by the local GBS
(assigned to the G.Bond port using ifStackTable).
This number is never greater than gBondCapacity.
This object SHALL be automatically incremented or decremented
when a BCE is added or deleted to/from the G.Bond port using
ifStackTable.
This object maps to the WT-157 attribute aGroupNumChannels"
REFERENCE
"[WT-157] 5.5.1.9"
::= { gBondPortStatusEntry 5 }
--
-- Conformance Statements
--
gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 }
gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 }
-- Object Groups
gBondBasicGroup OBJECT-GROUP
OBJECTS {
gBondUpDataRate,
gBondDownDataRate,
gBondTargetUpDataRate,
gBondTargetDownDataRate,
gBondCapacity,
gBondNumBCEs,
gBondPortSide,
gBondFltStatus
Beili, et al. Expires August 28, 2007 [Page 25]
Internet-Draft G.Bond MIB February 2007
}
STATUS current
DESCRIPTION
"A collection of objects representing management information
common to all types of G.Bond ports."
::= { gBondGroups 1 }
gBondDiscoveryGroup OBJECT-GROUP
OBJECTS {
gBondPeerBond,
gBondPeerCapacity,
gBondDiscoveryCode,
gBondRemoteDiscoveryCode
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL G.Bond discovery
in G.Bond ports."
::= { gBondGroups 2 }
gBondAlarmConfGroup OBJECT-GROUP
OBJECTS {
gBondThreshLowUpRate,
gBondThreshLowDownRate,
gBondLowRateCrossingEnable,
gBondBceDeviceFaultEnable,
gBondBceConfigInitFailEnable,
gBondBceProtocolInitFailEnable
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of alarm
thresholds and notifications in G.Bond ports."
::= { gBondGroups 5 }
gBondNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gBondLowUpRateCrossing,
gBondLowDownRateCrossing
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
associated with G.Bond ports."
::= { gBondGroups 6 }
-- Compliance Statements
Beili, et al. Expires August 28, 2007 [Page 26]
Internet-Draft G.Bond MIB February 2007
gBondCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for G.Bond interfaces.
Compliance with the following external compliance statements
is REQUIRED:
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
Compliance with the following external compliance statements
is OPTIONAL for implementations supporting bonding with
flexible cross-connect between the GBS and BCE ports:
MIB Module Compliance Statement
---------- --------------------
IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance"
MODULE -- this module
MANDATORY-GROUPS {
gBondBasicGroup,
gBondAlarmConfGroup,
gBondNotificationGroup
}
::= { gBondCompliances 1 }
END
6. Security Considerations
There is a number of managed objects defined in the GBOND-MIB module
that have a MAX-ACCESS clause of read-write or read-create. Most
objects are writeable only when the link is Down. Writing to these
objects can have potentially disruptive effects on network operation,
for example:
o Changing of gBondPAFAdminState to enabled MAY lead to a potential
locking of the link, if the peer device does not support bonding.
o Changing of gBondPAFDiscoveryCode, before the discovery operation,
MAY lead to a wrongful discovery, for example when two CO ports
are connected to the same multi-channel RT port, while both CO
ports have the same Discovery register value.
Beili, et al. Expires August 28, 2007 [Page 27]
Internet-Draft G.Bond MIB February 2007
o Changing GBS configuration parameters (e.g. profile of a GBS via
gBondAdminProfile) MAY lead to anything from link quality and rate
degradation to a complete link initialization failure, as ability
of an G.Bond port to support a particular configuration depends on
the copper environment.
o Activation of a specific line/channel can cause a severe
degradation of service for another G.Bond port, whose channel(s)
MAY be affected by the cross-talk from the newly activated
channel.
o Removal of a channel from an operationally 'up' G.Bond port,
aggregating several channels, MAY cause port's rate degradation
The user of the GBOND-MIB module must therefore be aware that support
for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations.
The readable objects in the GBOND-MIB module (i.e., those with MAX-
ACCESS other than not-accessible) may be considered sensitive in some
environments since, collectively, they provide information about the
performance of network interfaces and can reveal some aspects of
their configuration. In particular, since a bonded xDSL port can be
comprised of multiple Unshielded Twisted Pair (UTP) voice grade
copper, located in the same bundle with other pairs belonging to
another operator/customer, it is theoretically possible to evasdrop
to a G.Bond transmission, simply by "listening" to a cross-talk from
the bonded pairs, especially if the parameters of the G.Bond link in
question are known.
In such environments it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
Beili, et al. Expires August 28, 2007 [Page 28]
Internet-Draft G.Bond MIB February 2007
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations
Three new values of IANAifType: g9981, g9982, g9983 SHALL be defined
by the IANA [1] in the IANAifType-MIB module [IANAifType-MIB], before
this document is published as an RFC.
Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL
be allocated by IANA in the MIB-2 transmission sub-tree, before this
document is published.
8. Acknowledgments
This document was produced by the IETF ADSL MIB Working Group [2].
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Beili, et al. Expires August 28, 2007 [Page 29]
Internet-Draft G.Bond MIB February 2007
9.2. Informative References
[802.3] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications", IEEE Std 802.3-2005, December 2005.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.
[G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T
Recommendation G.998.1, January 2005.
[G.998.2] ITU-T, "Ethernet-based multi-pair bonding", ITU-T
Recommendation G.998.2, January 2005.
[G.998.3] ITU-T, "Multi-pair bonding using time-division inverse
multiplexing", ITU-T Recommendation G.998.3, January 2005.
[I-D.ietf-adslmib-gbond-atm-mib]
Morgenstern, M. and N. Nair, "ATM-based xDSL Bonded
Interfaces MIB", draft-ietf-adslmib-gbond-atm-mib-00 (work
in progress), February 2007.
[I-D.ietf-adslmib-gbond-eth-mib]
Beili, E. and M. Morgenstern, "Ethernet-based xDSL Bonded
Interfaces MIB", draft-ietf-adslmib-gbond-eth-mib-00 (work
in progress), February 2007.
[I-D.ietf-adslmib-gbond-tdim-mib]
Beili, E. and N. Nair, "TDIM-based xDSL Bonded Interfaces
MIB", draft-ietf-adslmib-gbond-tdim-mib-00 (work in
progress), February 2006.
[I-D.ietf-adslmib-vsl2-mib]
Morgenstern, M., "Definitions of Managed Objects for Very
High Speed Digital Subscriber Line 2 (VDSL2)",
draft-ietf-adslmib-vdsl2-01 (work in progress),
August 2006.
[I-D.ietf-hubmib-efm-cu-mib]
Beili, E., "Ethernet in the First Mile Copper (EFMCu)
Beili, et al. Expires August 28, 2007 [Page 30]
Internet-Draft G.Bond MIB February 2007
Interfaces MIB", draft-ietf-hubmib-efm-cu-mib-07 (work in
progress), February 2007.
[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-05 (work in progress),
July 2006.
[IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864,
June 2000.
[RFC3440] Ly, F. and G. Bathrick, "Definitions of Extension Managed
Objects for Asymmetric Digital Subscriber Lines",
RFC 3440, December 2002.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for
Very High Speed Digital Subscriber Lines (VDSL)",
RFC 3728, February 2004.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005.
[RFC4706] Morgenstern, M., Dodge, M., Baillie, S., and U. Bonollo,
"Definitions of Managed Objects for Asymmetric Digital
Subscriber Line 2 (ADSL2)", RFC 4706, November 2006.
[WT-157] Morgenstern, M., Beili, E., and N. Nair, "Management
Framework for xDSL Bonding", DSL Forum technical
report WT-157, Jan 2006.
[af-phy-0086]
ATM Forum, "Inverse Multiplexing for ATM (IMA)
Specification Version 1.1", ATM Forum specification af-
Beili, et al. Expires August 28, 2007 [Page 31]
Internet-Draft G.Bond MIB February 2007
pfy-0086.001, March 1999.
URIs
[1] <http://www.iana.org/>
[2] <http://www.ietf.org/html.charters/adslmib-charter.html>
Authors' Addresses
Edward Beili
Actelis Networks
25 Bazel St.
Petach-Tikva 49103
Israel
Phone: +972-3-924-3491
Email: edward.beili@actelis.com
Moti Morgenstern
ECI Telecom
30 Hasivim St.
Petach-Tikva 49517
Israel
Phone: +972-3-926-6258
Email: moti.morgenstern@ecitele.com
Narendranath Nair
Wipro Technologies
Keonics Electronics City
Bangalore 560 100
India
Phone: +91-80-2852-0408 x85338
Email: narendranath.nair@wipro.com
Beili, et al. Expires August 28, 2007 [Page 32]
Internet-Draft G.Bond MIB February 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
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
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Beili, et al. Expires August 28, 2007 [Page 33]
