draft-ietf-adslmib-gbond-mib-00.txt   draft-ietf-adslmib-gbond-mib-01.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Intended status: Standards Track M. Morgenstern Intended status: Standards Track M. Morgenstern
Expires: August 28, 2007 ECI Telecom Expires: May 21, 2008 ECI Telecom
N. Nair N. Nair
Wipro Technologies Wipro Technologies
February 24, 2007 November 18, 2007
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-00.txt draft-ietf-adslmib-gbond-mib-01.txt
Status of this Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 28, 2007. This Internet-Draft will expire on May 21, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines Management Information Base (MIB) module for This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP-based internets.
This document proposes an extension to the Interfaces Group MIB with This document proposes an extension to the Interfaces Group MIB with
a set of common objects for managing multi-pair bonded Digital a set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
G.998.1, G.998.2 and G.998.3. The MIB modules specific to each 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 bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and
GBOND-TDIM-MIB respectively. GBOND-TDIM-MIB respectively.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 4 2. The Internet-Standard Management Framework . . . . . . . . . . 4
3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 4
4. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4
4.1. Relation to Interfaces Group MIB module . . . . . . . . . 5 4.1. Relationship to Interfaces Group MIB module . . . . . . . 5
4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5 4.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 5
4.1.2. G.Bond Aggregation Function (GAF) . . . . . . . . . . 7 4.1.2. G.Bond Aggregation Function (GAF) . . . . . . . . . . 7
4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 4.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9 4.1.4. G.Bond ports initialization . . . . . . . . . . . . . 9
4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
4.2. Relation to xDSL MIB modules . . . . . . . . . . . . . . . 11 4.2. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11
4.3. Mapping of DSL Forum WT-157 Managed Objects . . . . . . . 11 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
5. xDSL multi-pair bonding MIB Definitions . . . . . . . . . . . 12 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 5.2. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 13
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 33
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
9.1. Normative References . . . . . . . . . . . . . . . . . . . 29 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 35
9.2. Informative References . . . . . . . . . . . . . . . . . . 30 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 10.1. Normative References . . . . . . . . . . . . . . . . . . . 35
Intellectual Property and Copyright Statements . . . . . . . . . . 33 10.2. Informative References . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
The xDSL Multi-Pair Bonding, allows a service provider to provide The xDSL Multi-Pair Bonding, allows a service provider to provide
high bandwidth services to business and residential customers over high bandwidth services to business and residential customers over
multiple xDSL lines, with greater speed and resiliency, than the multiple xDSL lines, with greater speed and resiliency, than the
service over a single xDSL line, bridging the gap between xDSL and service over a single xDSL line, bridging the gap between xDSL and
fiber-based transport. fiber-based transport.
There are three xDSL Multi-Pair Bonding schemes, also known under There are three xDSL Multi-Pair Bonding schemes, also known under
skipping to change at page 3, line 39 skipping to change at page 3, line 39
carrying an Ethernet stream. This specification can be viewed as carrying an Ethernet stream. This specification can be viewed as
IEEE 802.3-2005 [802.3] Clause 61 Physical Medium Entity (PME) IEEE 802.3-2005 [802.3] Clause 61 Physical Medium Entity (PME)
Aggregation, generalized to work over any xDSL technology. Aggregation, generalized to work over any xDSL technology.
(2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL and (2Base-TL and 10Pass-TS interfaces defined by IEEE use G.SHDSL and
VDSL technology respectively). VDSL technology respectively).
o The Multi-pair bonding using time-division inverse multiplexing o The Multi-pair bonding using time-division inverse multiplexing
(TDIM), specified in ITU-T G.998.3 recommendation [G.998.3], which (TDIM), specified in ITU-T G.998.3 recommendation [G.998.3], which
defines a method for bonding (or aggregating) of multiple xDSL defines a method for bonding (or aggregating) of multiple xDSL
lines into a single bi-directional logical link carrying a mix of lines into a single bi-directional logical link carrying a mix of
various traffic streams (e.g. Ethernet, ATM, TDM). various traffic streams (e.g., Ethernet, ATM, TDM).
Architecturally all three bonding schemes define a new "bonded" Architecturally all three bonding schemes define a new "bonded"
Transport Protocol Specific - Transmission Convergence (TPS-TC) sub- Transport Protocol Specific - Transmission Convergence (TPS-TC) sub-
layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC layer, stacked above multiple ATM-TC, Ethernet/PTM-TC or STM-TC
(clear channel) sub-layers for the ATM, Ethernet or TDIM bonding (clear channel) sub-layers for the ATM, Ethernet or TDIM bonding
respectively. Each underlying TPS-TC sub-layer represents a protocol respectively. Each underlying TPS-TC sub-layer represents a protocol
specific gamma-interface to an xDSL line or an individual bearer specific gamma-interface to an xDSL line or an individual bearer
channel of an xDSL line. Bonding of multiple bearer channels in the channel of an xDSL line. Bonding of multiple bearer channels in the
same xDSL line is not allowed. same xDSL line is not allowed.
skipping to change at page 4, line 22 skipping to change at page 4, line 22
2. The Internet-Standard Management Framework 2. 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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This document specifies a
module that is compliant to the SMIv2, which is described in STD 58, MIB module that is compliant to the SMIv2, which is described in STD
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
[RFC2580]. 2580 [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. The DSL Forum Management Framework for xDSL Bonding 3. The DSL Forum Management Framework for xDSL Bonding
This document makes use of the DSL Forum technical report Management This document makes use of the DSL Forum technical report Management
Framework for xDSL Bonding [WT-157], defining a management model and Framework for xDSL Bonding [WT-159], defining a management model and
a hierarchy of management objects for the bonded xDSL interfaces. a hierarchy of management objects for the bonded xDSL interfaces.
4. Relation to other MIB modules 4. Relationship to Other MIB modules
This section outlines the relationship of the MIB modules defined in This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs. this document with other MIB modules described in the relevant RFCs.
Specifically, the following MIB modules are discussed: Interfaces Specifically, the following MIB modules are discussed: Interfaces
Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB) Group MIB (IF-MIB), Inverse Stack Table MIB (IF-INVERTED-STACK-MIB)
Interface Stack Capability MIB (IF-CAP-STACK-MIB), G.Bond scheme Interface Stack Capability MIB (IF-CAP-STACK-MIB), G.Bond scheme
specific modules: G.Bond/ATM (GBOND-ATM-MIB), G.Bond/Ethernet (GBOND- 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 ETH-MIB) and G.Bond/TDIM (GBOND-TDIM-MIB), and DSL specific MIB
modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL
(HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE- (HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE-
MIB). MIB).
4.1. Relation to Interfaces Group MIB module 4.1. Relationship to Interfaces Group MIB module
A bonded xDSL port is a stacked (a.k.a. aggregated or bonded) A bonded xDSL port is a stacked (a.k.a. aggregated or bonded)
interface and as such is managed using generic interface management interface and as such is managed using generic interface management
objects defined in the IF-MIB [RFC2863]. objects defined in the IF-MIB [RFC2863].
The stack management, i.e. actual connection of the sub-layers to the The stack management, i.e., actual connection of the sub-layers to
top layer interface, is done via the ifStackTable, as defined in the the top layer interface, is done via the ifStackTable, as defined in
IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the the IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in
IF-INVERTED-STACK-MIB [RFC2864]. the IF-INVERTED-STACK-MIB [RFC2864].
The ifCapStackTable and its inverse ifInvCapStackTable defined in the The ifCapStackTable and its inverse ifInvCapStackTable defined in the
IF-CAP-STACK-MIB [I-D.ietf-hubmib-efm-cu-mib], extend the stack IF-CAP-STACK-MIB [RFC5066], extend the stack management with an
management with an ability to describe possible connections or cross- ability to describe possible connections or cross-connect capability,
connect capability, when a flexible cross-connect matrix is present when a flexible cross-connect matrix is present between the interface
between the interface layers. layers.
4.1.1. Layering Model 4.1.1. Layering Model
A G.Bond interface can aggregate up to 32 channel sub-layers, with A G.Bond interface can aggregate up to 32 channel sub-layers, with
each channel representing an xDSL line or an xDSL bearer channel. each channel representing an xDSL line or an xDSL bearer channel.
For the purpose of brevity we will refer to the bonded interface as 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 Generic Bonded Sub-layer (GBS) and to the channel sub-layer as
Bonding Channel Entity (BCE). Bonding Channel Entity (BCE).
A generic G.Bond device can have a number of GBS ports, each A generic G.Bond device can have a number of GBS ports, each
connected to a particular upper layer (e.g. Media Access Control connected to a particular upper layer (e.g., Media Access Control
(MAC) interface for G.998.2 scheme), while simultaneously cross- (MAC) interface for G.998.2 scheme), while simultaneously cross-
connected to a number of underlying BCEs, with a single GBS per BCE connected to a number of underlying BCEs, with a single GBS per BCE
relationship. relationship.
A GBS port is represented in the Interface table (ifTable) as a A GBS port is represented in the Interface table (ifTable) as a
separate interface with an ifType of g9981, g9982 or g9983 for a separate interface with an ifType of 'gBond'.
particular bonding scheme.
Each BCE in the aggregated GBS port is represented in the ifTable as Each BCE in the aggregated GBS port is represented in the ifTable as
a separate interface with an ifType relevant to a particular xDSL a separate interface with an ifType relevant to a particular xDSL
technology, e.g. shdsl(169) or vdsl(97). The ifType values are technology, e.g., shdsl(169) or vdsl(97). The ifType values are
defined in [IANAifType-MIB]. defined in [IANAifType-MIB].
The following figure shows the layering diagram and corresponding use The following figure shows the layering diagram and corresponding use
of ifTable for the bonded xDSL interfaces: of ifTable for the bonded xDSL interfaces:
.-----------------------------. - .-----------------------------. -
| GBS | ^ 1 ifEntry | GBS | ^ 1 ifEntry
| (TPS-TC) | v ifType: g9981, g9982 or g9983 | (TPS-TC) | v ifType: gBond
+-----------------+---+-------+ - +-----------------+---+-------+ -
| TPS-TC \ | | | ^ | TPS-TC \ | | | ^
+---------\ | | | | +---------\ | | | |
| PMS-TC )BCE 1 |...| BCE N | ) N ifEntry (N=1..32) | PMS-TC )BCE 1 |...| BCE N | ) N ifEntry (N=1..32)
+---------/ | | | | ifType: adsl(94), shdsl(169), +---------/ | | | | ifType: adsl(94), shdsl(169),
| PMD / | | | v vdsl(97), etc. | PMD / | | | v vdsl(97), etc.
'-----------------+---+-------' - '-----------------+---+-------' -
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
GBS - Generic Bonded Sub-layer GBS - Generic Bonded Sub-layer
skipping to change at page 6, line 37 skipping to change at page 6, line 37
The ifStackTable is indexed by the ifIndex values of the aggregated The ifStackTable is indexed by the ifIndex values of the aggregated
G.Bond port (GBS) and the BCEs connected to it. ifStackTable allows a G.Bond port (GBS) and the BCEs connected to it. ifStackTable allows a
Network Management application to determine which BCEs are connected Network Management application to determine which BCEs are connected
to a particular GBS and change connections (if supported by the to a particular GBS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which GBS runs on top of a particular BCE. determine which GBS runs on top of a particular BCE.
The ifCapStackTable defined in the IF-CAP-STACK-MIB module, specifies The ifCapStackTable defined in the IF-CAP-STACK-MIB module, specifies
for each higher-layer interface (e.g. GBS port) a list of lower- for each higher-layer interface (e.g., GBS port) a list of lower-
layer interfaces (e.g. BCEs), which can possibly be cross-connected layer interfaces (e.g., BCEs), which can possibly be cross-connected
to that higher-layer interface, determined by the cross-connect to that higher-layer interface, determined by the cross-connect
capability of the device. This table, modeled after ifStackTable, is capability of the device. This table, modeled after ifStackTable, is
read only, reflecting current cross-connect capability of a stacked read only, reflecting current cross-connect capability of a stacked
interface, which can be dynamic in some implementations (e.g. if xDSL interface, which can be dynamic in some implementations (e.g., if
lines are located on a pluggable module and the module is pulled xDSL lines are located on a pluggable module and the module is pulled
out). Note that BCE availability per GBS, described by out). Note that BCE availability per GBS, described by
ifCapStackTable, can be constrained by other parameters, for example ifCapStackTable, can be constrained by other parameters, for example
by aggregation capacity of a GBS or by the BCE in question being 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 already connected to another GBS. So, in order to ensure that a
particular BCE can be connected to the GBS, all respective parameters particular BCE can be connected to the GBS, all respective parameters
(e.g. ifCapStackTable, ifStackTable and gBondCapacity) SHALL be (e.g., ifCapStackTable, ifStackTable and gBondCapacity) SHALL be
inspected. inspected.
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
describes which higher-layer interfaces (e.g. GBS ports) can describes which higher-layer interfaces (e.g., GBS ports) can
possibly be connected to a particular lower-layer interface (e.g. possibly be connected to a particular lower-layer interface (e.g.,
BCE), providing inverted mapping of ifCapStackTable. While it BCE), providing inverted mapping of ifCapStackTable. While it
contains no additional information beyond that already contained in contains no additional information beyond that already contained in
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface. connected to run on top of a particular interface.
4.1.2. G.Bond Aggregation Function (GAF) 4.1.2. G.Bond Aggregation Function (GAF)
skipping to change at page 7, line 35 skipping to change at page 7, line 35
The GBOND-MIB module allows a Network Management application to query The GBOND-MIB module allows a Network Management application to query
GAF capability and enable/disable it if supported. Note that GAF capability and enable/disable it if supported. Note that
enabling GAF effectively turns on fragmentation and re-assembly, even enabling GAF effectively turns on fragmentation and re-assembly, even
on a single-BCE port. on a single-BCE port.
4.1.3. Discovery Operation 4.1.3. Discovery Operation
The G.Bond ports may optionally support discovery operation, whereby The G.Bond ports may optionally support discovery operation, whereby
BCEs, during initialization, exchange information about their BCEs, during initialization, exchange information about their
respective aggregation groups (GBS). This information can then be respective aggregation groups (GBS), via xDSL handshake protocol.
used to detect copper misconnections or for an automatic assignment This information can then be used to detect copper misconnections or
of the local BCEs into aggregation groups instead of a fixed pre- for an automatic assignment of the local BCEs into aggregation groups
configuration. instead of a fixed pre-configuration.
The MIB module defined in this document allow a Network Management The MIB module defined in this document allow a Network Management
application to control G.Bond Discovery mechanism and query its application to control G.Bond Discovery mechanism and query its
results. Note that the Discovery mechanism can work only if GAF is results. Note that the Discovery mechanism can work only if GAF is
supported and enabled. supported and enabled.
Two tables are used by the G.Bond Discovery mechanism: ifStackTable Two tables are used by the G.Bond Discovery mechanism: ifStackTable
and ifCapStackTable. The following pseudo-code gives an example of and ifCapStackTable. The following pseudo-code gives an example of
the Discovery and automatic BCE assignment for a generic multi-GBS the Discovery and automatic BCE assignment for a generic multi-GBS
G.Bond device, located at Central Office (CO), using objects defined G.Bond device, located at Central Office (CO), using objects defined
skipping to change at page 8, line 12 skipping to change at page 8, line 12
automatic BCE assignment is only shown here for the purposes of the automatic BCE assignment is only shown here for the purposes of the
example. Fixed BCE pre-assignment, manual assignment or auto- example. Fixed BCE pre-assignment, manual assignment or auto-
assignment using an alternative internal algorithm may be chosen by a assignment using an alternative internal algorithm may be chosen by a
particular implementation]: particular implementation]:
// Go over all GBS ports in the CO device // Go over all GBS ports in the CO device
FOREACH gbs[i] IN CO_device FOREACH gbs[i] IN CO_device
{ // Perform discovery and auto-assignment on GBS ports { // Perform discovery and auto-assignment on GBS ports
// with room for more Channels // with room for more Channels
IF ( gbs[i].NumBCEs < gbs[i].BondCapacity ) IF ( gbs[i].NumBCEs < gbs[i].BondCapacity )
{ dc = gbs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per GBS { // Assign a unique 6-octets local discovery code to the GBS
// e.g., MAC address
dc = gbs[i].DiscoveryCode = MAC[i];
// Go over all disconnected Channels, which can // Go over all disconnected Channels, which can
// pottentially be connected to the GBS // pottentially be connected to the GBS
FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND FOREACH bce[j] IN ifCapStackTable[gbs[i]] AND
NOT ifInvStackTable[bce[j]] // not connected NOT IN ifStackTable[gbs[i]] // not connected
{ // Try to grab the remote RT_device, by writing the value { // Try to grab the remote RT_device, by writing the value
// of the local 6 Byte discovery code to the remote // of the local 6 Byte discovery code to the remote
// discovery code register (via handshake mechanism). // discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it // This operation is atomic Set-if-Clear action, i.e., it
// would succeed only if the remote discovery register was // would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get // zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the BCE // operation to see if the RT_device, attached via the BCE
// is indeed marked as being the CO_device peer. // is indeed marked as being the CO_device peer.
bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear bce[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = bce[j].RemoteDiscoveryCode; // Get r = bce[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity) IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity)
{ // Remote RT_device connected via BCE[j] is/was a peer { // Remote RT_device connected via BCE[j] is/was a peer
// for GBS[i] and there room for another BCE in the // for GBS[i] and there room for another BCE in the
// GBS[i] aggregation group (max. Bonding capacity is // GBS[i] aggregation group (max. Bonding capacity is
// not reached yet). // not reached yet).
// Connect this BCE to the GBS (via ifStackTable, // Connect this BCE to the GBS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is // ifInvStackTable being inverse of ifStackTable is
// updated automatically) // updated automatically, i.e., gbs[i] is auto-added
// to ifInvStackTable[bce[j]])
ADD bce[j] TO ifStackTable[gbs[i]]; ADD bce[j] TO ifStackTable[gbs[i]];
// gbs[i] is auto-added to ifInvStackTable[bce[j]]
gbs[i].NumBCEs = gbs[i].NumBCEs + 1; gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
// Discover all other disconnected BCEs, // Discover all other disconnected BCEs,
// attached to the same RT_device and connect them to // attached to the same RT_device and connect them to
// the GBS provided there is enough room for more BCEs. // the GBS provided there is enough room for more BCEs.
FOREACH bce[k] IN ifCapStackTable[gbs[i]] and FOREACH bce[k] IN ifCapStackTable[gbs[i]] and
NOT ifInvStackTable[bce[k]] NOT IN ifStackTable[gbs[i]]
{ r = bce[k].RemoteDiscoveryCode; // Get { // Get Remote Discovery Code from the BCE to see if
IF ( r == dc AND // it belongs to a connected RT_device "grabbed" by
gbs[i].NumBCEs < gbs[i].BondCapacity) // the CO_device.
{ ADD bce[k] TO ifStackTable[gbs[i]]; r = bce[k].RemoteDiscoveryCode;
// gbs[i] is added TO ifInvStackTable[bce[k]] IF ( r == dc AND gbs[i].NumBCEs < gbs[i].BondCapacity)
{ // Physically connect the BCE to the GBS
// (gbs[i] is auto-added TO ifInvStackTable[bce[k]])
ADD bce[k] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1; gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
} }
} }
} }
// At this point we have discovered all local BCEs which // At this point we have discovered all local BCEs which
// are physically connected to the same remote RT_device // are physically connected to the same remote RT_device
// and connected them to GBS[i]. Go to the next GBS. // and connected them to GBS[i]. Go to the next GBS.
BREAK; BREAK;
} }
} }
skipping to change at page 9, line 30 skipping to change at page 9, line 35
connection to succeed. In fact, a dynamic BCE addition (and removal) connection to succeed. In fact, a dynamic BCE addition (and removal)
MAY be implemented with an available BCE being initialized first (by MAY be implemented with an available BCE being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally setting its ifAdminStatus to 'up') and then added to an operationally
'up' GBS port, by modifying a respective ifStackTable (and respective 'up' GBS port, by modifying a respective ifStackTable (and respective
ifInvStackTable) entry. ifInvStackTable) entry.
It is RECOMMENDED that a removal of the last operationally 'up' BCE It is RECOMMENDED that a removal of the last operationally 'up' BCE
from an operationally 'up' GBS would be rejected by the from an operationally 'up' GBS would be rejected by the
implementation, as this action would completely drop the link. implementation, as this action would completely drop the link.
In addition to the standard handshake-based discovery described
above, [G.998.2] defines an optional frame-based discovery and pair
management. These frame-based methods are discussed in
[I-D.ietf-adslmib-gbond-eth-mib].
4.1.4. G.Bond ports initialization 4.1.4. G.Bond ports initialization
G.Bond ports being built on top of xDSL technology, require a lengthy G.Bond ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise on 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 the line is too high, that 'training' process may fail to achieve a
specific target rate with required characteristics. specific target rate with required characteristics.
skipping to change at page 10, line 31 skipping to change at page 10, line 41
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | G.Bond interpretation | | IF-MIB object | G.Bond interpretation |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each BCE and each GBS | | ifIndex | Interface index. Note that each BCE and each GBS |
| | in the G.Bond PHY MUST have a unique index, as | | | in the G.Bond PHY MUST have a unique index, as |
| | there some GBS and BCE specific attributes | | | there some GBS and BCE specific attributes |
| | accessible only on the GBS or BCE level. | | | accessible only on the GBS or BCE level. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifType | g9981, g9982 or g9982 for the ATM, Ethernet or | | ifType | gBond(TBD) for GBS, shdsl(169) for G.SHDSL BCE, |
| | TDIM GBS respectively, shdsl(169) for G.SHDSL | | | vdsl(97) for VDSL BCE etc. |
| | BCE, vdsl(97) for VDSL BCE etc. | +---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the BCE. For the GBS it | | ifSpeed | Operating data rate for the BCE. For the GBS it |
| | is the sum of the current operating data rates of | | | is the sum of the current operating data rates of |
| | all BCEs in the aggregation group, without the | | | all BCEs in the aggregation group, without the |
| | encapsulation overhead and G.Bond overhead, but | | | encapsulation overhead and G.Bond overhead, but |
| | accounting for the Inter-Frame Gaps (IFG). When a | | | accounting for the Inter-Frame Gaps (IFG). When a |
| | GBS or a BCE is operating in an assymetrical | | | GBS or a BCE is operating in an assymetrical |
| | fashion (upstream data rate differs from the | | | fashion (upstream data rate differs from the |
| | downstream one) the lowest of the values is | | | downstream one) the lowest of the values is |
| | shown. | | | shown. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a | | ifAdminStatus | Setting this object to 'up' instructs a |
| | particular GBS (with all BCEs connected to it) or | | | particular GBS (with all BCEs connected to it) or |
| | a BCE to start initialization process | | | a BCE to start initialization process |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+
| ifOperStatus | a relevant *Status object from a particular line | | ifOperStatus | a relevant *Status object from a particular line |
| | MIB supplements the 'down' value of ifOperStatus | | | MIB supplements the 'down' value of ifOperStatus |
| | for BCEs. | | | for BCEs. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1: G.Bond interpretation of IF-MIB objects Table 1: G.Bond interpretation of IF-MIB objects
4.2. Relation to xDSL MIB modules 4.2. Relationship to xDSL MIB modules
Each xDSL technology is described in a relevant xDSL line MIB module: 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 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 [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 [RFC3728] for VDSL or VDSL2-LINE-MIB [I-D.ietf-adslmib-vdsl2-mib] for
VDSL2. VDSL2.
These MIBs are used to manage individual xDSL lines/channels (BCEs). These MIBs are used to manage individual xDSL lines/channels (BCEs).
4.3. Mapping of DSL Forum WT-157 Managed Objects 5. MIB Structure
5.1. Overview
5.2. Mapping of DSL Forum WT-159 Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [WT-157] and managed objects defined in this (attributes) defined in [WT-159] and managed objects defined in this
document and in associated MIB modules, i.e., the IF-MIB [RFC2863]. document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| G.Bond Managed Object | Corresponding SNMP | | G.Bond Managed Object | Corresponding SNMP Object |
| | Object | +-----------------------------+-------------------------------------+
+----------------------------------------+--------------------------+ | oBondingGroup - Basic | |
| oBondingGroup - Basic Package | | | Package (Mandatory) | |
| (Mandatory) | | +-----------------------------+-------------------------------------+
+----------------------------------------+--------------------------+
| aGroupID | ifIndex (IF-MIB) | | aGroupID | ifIndex (IF-MIB) |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupBondScheme | ifType (IF-MIB) | | aGroupBondSchemesSupported | gBondSchemesSupported |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupPeerBondScheme | | | aGroupAdminBondScheme | gBondAdminScheme |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupEnd | gBondPhySide | | aGroupOperBondScheme | gBondOperScheme |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupPeerOperBondScheme | gBondPeerOperScheme |
+-----------------------------+-------------------------------------+
| aGroupEnd | gBondPortSide |
+-----------------------------+-------------------------------------+
| aGroupOperState | ifOperStatus (IF-MIB) | | aGroupOperState | ifOperStatus (IF-MIB) |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupAdminState | ifAdminStatus (IF-MIB) | | aGroupAdminState | ifAdminStatus (IF-MIB) |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupStatus | gBondStatus | | aGroupStatus | gBondFltStatus |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupName | ifName (IF-MIB) |
+----------------------------------------+--------------------------+
| aGroupCapacity | gBondCapacity | | aGroupCapacity | gBondCapacity |
+-----------------------------+-------------------------------------+
| aGroupPeerCapacity | gBondPeerCapacity |
+-----------------------------+-------------------------------------+
| aGroupNumChannels | gBondNumBCEs | | aGroupNumChannels | gBondNumBCEs |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupName | ifName (IF-MIB) |
+-----------------------------+-------------------------------------+
| aGroupUpRate | gBondUpDataRate | | aGroupUpRate | gBondUpDataRate |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupDownRate | gBondDownDataRate | | aGroupDownRate | gBondDownDataRate |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupTargetUpRate | gBondTargetUpDataRate | | aGroupTargetUpRate | gBondTargetUpDataRate |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupTargetDownRate | gBondTargetDownDataRate | | aGroupTargetDownRate | gBondTargetDownDataRate |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupCapacity | gBondCapacity | | aGroupCapacity | gBondCapacity |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| TBC... | TBC... | | aGroupPeerCapacity | gBondPeerCapacity |
+----------------------------------------+--------------------------+ +-----------------------------+-------------------------------------+
| aGroupThreshLowUpRate | gBondThreshLowUpRate |
+-----------------------------+-------------------------------------+
| aGroupThreshLowDownRate | gBondThreshLowDownRate |
+-----------------------------+-------------------------------------+
+-----------------------------+-------------------------------------+
| aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable |
+-----------------------------+-------------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+-----------------------------+-------------------------------------+
| nGroupLowDownRateCrossing | gBondLowDownRateCrossing |
+-----------------------------+-------------------------------------+
| aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB doesn't |
| | provide a control for the |
| | linkUp/linkDown notifications. Can |
| | we define a control in one MIB |
| | module while the notifications are |
| | in another?_ |
+-----------------------------+-------------------------------------+
| nGroupLinkUp | linkDown (IF-MIB) |
+-----------------------------+-------------------------------------+
| nGroupLinkDown | linkUp (IF-MIB) |
+-----------------------------+-------------------------------------+
| oLine - Basic Package | |
| (Mandatory) | |
+-----------------------------+-------------------------------------+
| aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode |
+-----------------------------+-------------------------------------+
Table 2: Mapping of WT-157 Managed Objects Table 2: Mapping of WT-159 Managed Objects
5. xDSL multi-pair bonding MIB Definitions 6. xDSL Multi-pair Bonding MIB Definitions
GBOND-MIB DEFINITIONS ::= BEGIN GBOND-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Gauge32, mib-2 Unsigned32, Gauge32, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, PhysAddress
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString ifIndex
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM IF-MIB -- [RFC2863]
ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863
; ;
gBondMIB MODULE-IDENTITY gBondMIB MODULE-IDENTITY
LAST-UPDATED "200702240000Z" -- February 24, 2007 LAST-UPDATED "200711180000Z" -- November 18, 2007
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/adslmib-charter.html http://www.ietf.org/html.charters/adslmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: adslmib@ietf.org General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Menachem Dodge Chair: Menachem Dodge
Postal: ECI Telecom, Ltd. Postal: ECI Telecom, Ltd.
30 Hasivim St., 30 Hasivim St.,
Petach-Tikva 49517 Petach-Tikva 49517
Israel Israel
Tel: +972-3-926-8421 Phone: +972-3-926-8421
E-mail: menachem.dodge@ecitele.com EMail: menachem.dodge@ecitele.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks, Inc. Postal: Actelis Networks, Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Phone: +972-3-924-3491
E-mail: edward.beili@actelis.com" EMail: edward.beili@actelis.com
Editor: Moti Morgenstern
Postal: ECI Telecom
30 Hasivim St.
Petach-Tikva 49517
Israel
Phone: +972-3-926-6258
EMail: moti.morgenstern@ecitele.com
Editor: Narendranath Nair
Posatl: Wipro Technologies
Keonics Electronics City
Bangalore 560 100
India
Phone: +91-80-2852-0408 x85338
EMail: narendranath.nair@wipro.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage the "The objects in this MIB module are used to manage the
multi-pair bonded xDSL Interfaces, defined in ITU-T multi-pair bonded xDSL Interfaces, defined in ITU-T
recommendations G.998.1, G.998.2 and G.998.3. recommendations G.998.1, G.998.2 and G.998.3.
This MIB module MUST be used in conjunction with a bonding This MIB module MUST be used in conjunction with a bonding
scheme specific MIB module, that is, GBOND-ATM-MIB, scheme specific MIB module, that is, GBOND-ATM-MIB,
GBOND-ETH-MIB or GBOND-TDIM-MIB. GBOND-ETH-MIB or GBOND-TDIM-MIB.
The following references are used throughout this MIB module: The following references are used throughout this MIB module:
[G.998.1] refers to: [G.998.1] refers to:
ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding',
January 2005. January 2005.
[G.998.2] refers to: [G.998.2] refers to:
ITU-T Recommendation G.998.1: 'Ethernet-based multi-pair ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
bonding', January 2005. bonding', January 2005.
[G.998.3] refers to: [G.998.3] refers to:
ITU-T Recommendation G.998.1: 'Multi-pair bonding using ITU-T Recommendation G.998.3: 'Multi-pair bonding using
time-division inverse multiplexing', January 2005. time-division inverse multiplexing', January 2005.
[WT-157] refers to: [WT-159] refers to:
DSL Forum Technical Report: 'Management Framework for xDSL DSL Forum Technical Report: 'Management Framework for xDSL
Bonding', January 2007. Bonding', January 2007.
Naming Conventions: Naming Conventions:
BCE - Bonding Channel Entity BCE - Bonding Channel Entity
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sublayer
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
Copyright (C) The Internet Society (2007). This version Copyright (C) The Internet Society (2007). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200702240000Z" -- February 24, 2007 REVISION "200711180000Z" -- November 18, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 ZZZ } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is -- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
-- Sections of the module -- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D -- Structured as recommended by [RFC4181], Appendix D
gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 } gBondObjects OBJECT IDENTIFIER ::= { gBondMIB 1 }
gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 } gBondConformance OBJECT IDENTIFIER ::= { gBondMIB 2 }
-- Groups in the module -- Groups in the module
gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 } gBondPort OBJECT IDENTIFIER ::= { gBondObjects 1 }
gBondBce OBJECT IDENTIFIER ::= { gBondObjects 2 }
-- Textual Conventions -- Textual Conventions
TruthValueOrUnknown ::= TEXTUAL-CONVENTION GBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the TruthValue "This textual convention defines a bitmap of possible ITU-T
convention. The latter defines a boolean value with G.998 (G.Bond) bonding schemes. Currently there are 3 bonding
possible values of true(1) and false(2). This schemes defined: G.998.1, G.998.2 and G.998.3, identified by
extension permits the additional value of unknown(0), which bit values g9981(1), g9982(2) and g9983(3), respectively.
can be returned as a result of GET operation, when an exact An additional value of unknown(0), can be returned as a result
true or false value of the object cannot be determined." of GET operation, when an value of the object cannot be
SYNTAX INTEGER { unknown(0), true(1), false(2) } determined."
SYNTAX BITS {
unknown(0),
g9981(1),
g9982(2),
g9983(3)
}
GBondScheme ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are:
unknown(0) - undefined or unknown
g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernt)
g9983(3) - G.998.3 (G.Bond/TDIM)."
SYNTAX INTEGER {
unknown(0),
g9981(1),
g9982(2),
g9983(3)
}
-- Port Notifications Group -- Port Notifications Group
gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 } gBondPortNotifications OBJECT IDENTIFIER ::= { gBondPort 0 }
gBondLowUpRateCrossing NOTIFICATION-TYPE gBondLowUpRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific GBS -- ifIndex is not needed here since we are under specific GBS
gBondUpDataRate, gBondUpDataRate,
gBondThreshLowUpRate gBondThreshLowUpRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the G.Bond port' upstream "This notification indicates that the G.Bond port' upstream
data rate has reached/dropped below or exceeded the low data rate has reached/dropped below or exceeded the low
upstream rate threshold, specified by gBondThreshLowUpRate. upstream rate threshold, specified by gBondThreshLowUpRate.
This notification MAY be send for the -O subtype ports This notification MAY be sent for the -O subtype ports
while the port is up, on the crossing event in both while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to (rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R normal. This notification is not applicable to the -R
subtypes. subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification, between the detection of the condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and is implemented to prevent simultaneous LinkUp/LinkDown and
gBondLowUpRateCrossing notifications to be sent. gBondLowUpRateCrossing notifications to be sent.
The adaptive nature of the G.Bond technology allows the port The adaptive nature of the G.Bond technology allows the port
to adapt itself to the changes in the copper environment, to adapt itself to the changes in the copper environment,
e.g. an impulse noise, alien crosstalk or a micro-interruption e.g., an impulse noise, alien crosstalk, or a
may temporarily drop one or more BCEs in the aggregation micro-interruption may temporarily drop one or more BCEs in
group, causing a rate degradation of the aggregated G.Bond the aggregation group, causing a rate degradation of the
link. The dropped BCEs would then try to re-initialize, aggregated G.Bond link. The dropped BCEs would then try to
possibly at a lower rate than before, adjusting the rate to re-initialize, possibly at a lower rate than before, adjusting
provide required target SNR margin. the rate to provide required target SNR margin.
Generation of this notification is controlled by the Generation of this notification is controlled by the
gBondLowRateCrossingEnable object." gBondLowRateCrossingEnable object.
This object maps to the WT-159 notification
nGroupLowUpRateCrossing."
REFERENCE
"[WT-159] 5.5.1.24"
::= { gBondPortNotifications 1 } ::= { gBondPortNotifications 1 }
gBondLowDownRateCrossing NOTIFICATION-TYPE gBondLowDownRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific GBS -- ifIndex is not needed here since we are under specific GBS
gBondDownDataRate, gBondDownDataRate,
gBondThreshLowDownRate gBondThreshLowDownRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the G.Bond port' downstream "This notification indicates that the G.Bond port' downstream
data rate has reached/dropped below or exceeded the low data rate has reached/dropped below or exceeded the low
downstream rate threshold, specified by downstream rate threshold, specified by
gBondThreshLowDownRate. gBondThreshLowDownRate.
This notification MAY be send for the -O subtype ports This notification MAY be sent for the -O subtype ports
while the port is up, on the crossing event in both while the port is up, on the crossing event in both
directions: from normal (rate is above the threshold) to low directions: from normal (rate is above the threshold) to low
(rate equals the threshold or below it) and from low to (rate equals the threshold or below it) and from low to
normal. This notification is not applicable to the -R normal. This notification is not applicable to the -R
subtypes. subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification, between the detection of the condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and is implemented to prevent simultaneous LinkUp/LinkDown and
gBondLowDownRateCrossing notifications to be sent. gBondLowDownRateCrossing notifications to be sent.
The adaptive nature of the G.Bond technology allows the port The adaptive nature of the G.Bond technology allows the port
to adapt itself to the changes in the copper environment, to adapt itself to the changes in the copper environment,
e.g. an impulse noise, alien crosstalk or a micro-interruption e.g., an impulse noise, alien crosstalk, or a
may temporarily drop one or more BCEs in the aggregation micro-interruption may temporarily drop one or more BCEs in
group, causing a rate degradation of the aggregated G.Bond the aggregation group, causing a rate degradation of the
link. The dropped BCEs would then try to re-initialize, aggregated G.Bond link. The dropped BCEs would then try to
possibly at a lower rate than before, adjusting the rate to re-initialize, possibly at a lower rate than before,
provide required target SNR margin. adjusting the rate to provide required target SNR margin.
Generation of this notification is controlled by the Generation of this notification is controlled by the
gBondLowRateCrossingEnable object." gBondLowRateCrossingEnable object.
This object maps to the WT-159 notification
nGroupLowUpRateCrossing."
REFERENCE
"[WT-159] 5.5.1.25"
::= { gBondPortNotifications 2} ::= { gBondPortNotifications 2}
-- G.Bond Port (BCS) group -- G.Bond Port (GBS) group
gBondPortConfTable OBJECT-TYPE gBondPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortConfEntry SYNTAX SEQUENCE OF GBondPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of G.Bond GBS ports. Entries in this "Table for Configuration of G.Bond GBS ports. Entries in this
table MUST be maintained in a persistent manner" table MUST be maintained in a persistent manner"
::= { gBondPort 1 } ::= { gBondPort 1 }
skipping to change at page 16, line 46 skipping to change at page 19, line 4
table MUST be maintained in a persistent manner" table MUST be maintained in a persistent manner"
::= { gBondPort 1 } ::= { gBondPort 1 }
gBondPortConfEntry OBJECT-TYPE gBondPortConfEntry OBJECT-TYPE
SYNTAX GBondPortConfEntry SYNTAX GBondPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Configuration table. "An entry in the G.Bond Port Configuration table.
Each entry represents an G.Bond port indexed by the ifIndex. Each entry represents an G.Bond port indexed by the ifIndex.
Note that an G.Bond GBS port runs on top of a single Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex." or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondPortConfTable 1 } ::= { gBondPortConfTable 1 }
GBondPortConfEntry ::= GBondPortConfEntry ::=
SEQUENCE { SEQUENCE {
gBondAdminScheme GBondScheme,
gBondDiscoveryCode PhysAddress, gBondDiscoveryCode PhysAddress,
gBondTargetUpDataRate Unsigned32, gBondTargetUpDataRate Unsigned32,
gBondTargetDownDataRate Unsigned32, gBondTargetDownDataRate Unsigned32,
gBondThreshLowUpRate Unsigned32, gBondThreshLowUpRate Unsigned32,
gBondThreshLowDownRate Unsigned32, gBondThreshLowDownRate Unsigned32,
gBondLowRateCrossingEnable TruthValue gBondLowRateCrossingEnable TruthValue
} }
gBondAdminScheme OBJECT-TYPE
SYNTAX GBondScheme
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A desired bonding scheme for a G.Bond port.
The following values instruct the port to use corresponding
bonding scheme if supported:
g998.1(1) - instructs the port to use G.998.1 bonding
g998.2(2) - instructs the port to use G.998.2 bonding
g998.3(3) - instructs the port to use G.998.3 bonding
Changing of the gBondAdminScheme 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. Attempts to change this object to
an unsupported bonding scheme (see gBondSchemesSupported)
SHALL be rejected (in case of SNMP with the error wrongValue).
This object MUST be maintained in a persistent manner.
This object maps to the WT-159 attribute
aGroupAdminBondScheme."
REFERENCE
"[WT-159] 5.5.1.6"
::= { gBondPortConfEntry 1 }
gBondDiscoveryCode OBJECT-TYPE gBondDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6)) SYNTAX PhysAddress (SIZE(6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Discovery Code of the G.Bond port (GBS). "A Discovery Code of the G.Bond port (GBS).
A unique 6 octet long code used by the Discovery function. A unique 6 octet long code used by the Discovery function.
This object MUST be instantiated for the -O subtype GBS before This object MUST be instantiated for the -O subtype GBS before
writing operations on the gBondRemoteDiscoveryCode writing operations on the gBondBceRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by BCEs (Set_if_Clear and Clear_if_Same) are performed by BCEs
associated with the GBS. associated with the GBS.
The initial value of this object for -R subtype ports after The initial value of this object for -R subtype ports after
reset is all zeroes. For -R subtype ports, the value of this reset is all zeroes. For -R subtype ports, the value of this
object cannot be changed directly. This value may be changed object cannot be changed directly. This value may be changed
as a result of writing operation on the as a result of writing operation on the
gBondRemoteDiscoveryCode object of remote BCE of -O gBondBceRemoteDiscoveryCode object of remote BCE of -O
subtype, connected to one of the local BCEs associated with subtype, connected to one of the local BCEs associated with
the GBS. the GBS.
Discovery MUST be performed when the link is Down. Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected (in case of Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or SNMP with the error inconsistentValue), if the link is Up or
Initializing." Initializing.
This object maps to the WT-159 attribute
aGroupDiscoveryCode."
REFERENCE REFERENCE
"[802.3] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, 61A.2" "[WT-159] 5.5.1.20; [802.3] 61.2.2.8.3, 61.2.2.8.4,
::= { gBondPortConfEntry 1 } 45.2.6.6.1, 45.2.6.8, 61A.2"
::= { gBondPortConfEntry 2 }
gBondTargetUpDataRate OBJECT-TYPE gBondTargetUpDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999) SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired G.Bond port Data Rate in the upstream direction, "A desired G.Bond port Data Rate in the upstream direction,
in Kbps, to be achieved during initialization, under in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective restrictions placed upon the member BCEs by their respective
configuration settings. configuration settings.
This object represents a sum of individual BCE upstream data This object represents a sum of individual BCE upstream data
rates, modified to compensate for fragmentation and rates, modified to compensate for fragmentation and
encapsulation overhead (e.g. for an Ethernet service, the encapsulation overhead (e.g., for an Ethernet service, the
target data rate of 10Mbps SHALL allow lossless transmission target data rate of 10Mbps SHALL allow lossless transmission
of full-duplex 10Mbps Ethernet frame stream with minimal of full-duplex 10Mbps Ethernet frame stream with minimal
inter-frame gap). inter-frame gap).
Note that the target upstream data rate may not be achieved Note that the target upstream data rate may not be achieved
during initialization (e.g. due to unavailability of required during initialization (e.g., due to unavailability of required
BCEs) or the initial bandwidth could deteriorate, so that the BCEs) or the initial bandwidth could deteriorate, so that the
actual upstream data rate (gBondUpDataRate) could be less actual upstream data rate (gBondUpDataRate) could be less
than gBondTargetUpDataRate. than gBondTargetUpDataRate.
The value between 1 and 1000000 indicates that the total The value between 1 and 1000000 indicates that the total
upstream data rate of the G.Bond port after initialization upstream data rate of the G.Bond port after initialization
SHALL be equal to the target data rate or less, if the target SHALL be equal to the target data rate or less, if the target
upstream data rate cannot be achieved under the restrictions upstream data rate cannot be achieved under the restrictions
configured for BCEs. In case the copper environment allows to configured for BCEs. In case the copper environment allows to
achieve higher upstream data rate than that specified by this achieve higher upstream data rate than that specified by this
skipping to change at page 18, line 37 skipping to change at page 21, line 28
restrictions and with desired SNR Margin per BCE. restrictions and with desired SNR Margin per BCE.
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
Changing of the Target Upstream Data Rate MUST be performed Changing of the Target Upstream Data Rate MUST be performed
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue), rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. if the link is Up or Initializing.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner.
::= { gBondPortConfEntry 2 }
This object maps to the WT-159 attribute
aGroupTargetUpRate."
REFERENCE
"[WT-159] 5.5.1.17"
::= { gBondPortConfEntry 3 }
gBondTargetDownDataRate OBJECT-TYPE gBondTargetDownDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999) SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired G.Bond port Data Rate in the downstream direction, "A desired G.Bond port Data Rate in the downstream direction,
in Kbps, to be achieved during initialization, under in Kbps, to be achieved during initialization, under
restrictions placed upon the member BCEs by their respective restrictions placed upon the member BCEs by their respective
configuration settings. configuration settings.
This object represents a sum of individual BCE downstream data This object represents a sum of individual BCE downstream data
rates, modified to compensate for fragmentation and rates, modified to compensate for fragmentation and
encapsulation overhead (e.g. for an Ethernet service, the encapsulation overhead (e.g., for an Ethernet service, the
target data rate of 10Mbps SHALL allow lossless transmission target data rate of 10Mbps SHALL allow lossless transmission
of full-duplex 10Mbps Ethernet frame stream with minimal of full-duplex 10Mbps Ethernet frame stream with minimal
inter-frame gap). inter-frame gap).
Note that the target downstream data rate may not be achieved Note that the target downstream data rate may not be achieved
during initialization (e.g. due to unavailability of required during initialization (e.g., due to unavailability of required
BCEs) or the initial bandwidth could deteriorate, so that the BCEs) or the initial bandwidth could deteriorate, so that the
actual downstream data rate (gBondDownDataRate) could be less actual downstream data rate (gBondDownDataRate) could be less
than gBondTargetDownDataRate. than gBondTargetDownDataRate.
The value between 1 and 1000000 indicates that the total The value between 1 and 1000000 indicates that the total
downstream data rate of the G.Bond port after initialization downstream data rate of the G.Bond port after initialization
SHALL be equal to the target data rate or less, if the target SHALL be equal to the target data rate or less, if the target
downstream data rate cannot be achieved under the restrictions downstream data rate cannot be achieved under the restrictions
configured for BCEs. In case the copper environment allows to configured for BCEs. In case the copper environment allows to
achieve higher downstream data rate than that specified by achieve higher downstream data rate than that specified by
skipping to change at page 19, line 37 skipping to change at page 22, line 32
restrictions and with desired SNR Margin per BCE. restrictions and with desired SNR Margin per BCE.
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
Changing of the Target Downstream Data Rate MUST be performed Changing of the Target Downstream Data Rate MUST be performed
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected (In case of SNMP with the error inconsistentValue), rejected (In case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. if the link is Up or Initializing.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner.
::= { gBondPortConfEntry 3 }
This object maps to the WT-159 attribute
aGroupTargetDownRate."
REFERENCE
"[WT-159] 5.5.1.18"
::= { gBondPortConfEntry 4 }
gBondThreshLowUpRate OBJECT-TYPE gBondThreshLowUpRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000) SYNTAX Unsigned32(1..1000000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the G.Bond port low upstream rate "This object configures the G.Bond port low upstream rate
crossing alarm threshold. When the current value of crossing alarm threshold. When the current value of
gBondUpDataRate for this port reaches/drops below or exceeds gBondUpDataRate for this port reaches/drops below or exceeds
this threshold, an gBondLowUpRateCrossing notification MAY be this threshold, an gBondLowUpRateCrossing notification MAY be
generated if enabled by gBondLowRateCrossingEnable. generated if enabled by gBondLowRateCrossingEnable.
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner.
::= { gBondPortConfEntry 4 }
This object maps to the WT-159 attribute
aGroupthreshLowUpRate."
REFERENCE
"[WT-159] 5.5.1.21"
::= { gBondPortConfEntry 5 }
gBondThreshLowDownRate OBJECT-TYPE gBondThreshLowDownRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000) SYNTAX Unsigned32(1..1000000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the G.Bond port low downstream rate "This object configures the G.Bond port low downstream rate
crossing alarm threshold. When the current value of crossing alarm threshold. When the current value of
gBondDownDataRate for this port reaches/drops below or exceeds gBondDownDataRate for this port reaches/drops below or exceeds
this threshold, an gBondLowDownRateCrossing notification MAY this threshold, an gBondLowDownRateCrossing notification MAY
be generated if enabled by gBondLowRateCrossingEnable. be generated if enabled by gBondLowRateCrossingEnable.
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner.
::= { gBondPortConfEntry 5 }
This object maps to the WT-159 attribute
aGroupThreshDownUpRate."
REFERENCE
"[WT-159] 5.5.1.22"
::= { gBondPortConfEntry 6 }
gBondLowRateCrossingEnable OBJECT-TYPE gBondLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether gBondLowUpRateCrossing and "Indicates whether gBondLowUpRateCrossing and
gBondLowDownRateCrossing notifications should be generated gBondLowDownRateCrossing notifications should be generated
for this interface. for this interface.
Value of true(1) indicates that the notifications are enabled. Value of true(1) indicates that the notifications are enabled.
Value of false(2) indicates that the notifications are Value of false(2) indicates that the notifications are
disabled. disabled.
This object is read-write for the -O subtype G.Bond ports This object is read-write for the -O subtype G.Bond ports
and irrelevant for the -R subtypes. and irrelevant for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner.
::= { gBondPortConfEntry 6 }
This object maps to the WT-159 attribute
aGroupLowRateCrossingEnable."
REFERENCE
"[WT-159] 5.5.1.23"
::= { gBondPortConfEntry 7 }
gBondPortCapabilityTable OBJECT-TYPE gBondPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortCapabilityEntry SYNTAX SEQUENCE OF GBondPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Capabilities of G.Bond Ports. Entries in this table "Table for Capabilities of G.Bond Ports. Entries in this table
MUST be maintained in a persistent manner" MUST be maintained in a persistent manner"
::= { gBondPort 2 } ::= { gBondPort 2 }
skipping to change at page 21, line 23 skipping to change at page 24, line 37
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Capability table. "An entry in the G.Bond Port Capability table.
Each entry represents an G.Bond port indexed by the ifIndex. Each entry represents an G.Bond port indexed by the ifIndex.
Note that a G.Bond GBS port runs on top of a single Note that a G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex." or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondPortCapabilityTable 1 } ::= { gBondPortCapabilityTable 1 }
GBondPortCapabilityEntry ::= GBondPortCapabilityEntry ::=
SEQUENCE { SEQUENCE {
gBondPeerBond TruthValueOrUnknown, gBondSchemesSupported GBondSchemeList,
gBondCapacity Unsigned32, gBondCapacity Unsigned32,
gBondPeerCapacity Unsigned32 gBondPeerCapacity Unsigned32
} }
gBondPeerBond OBJECT-TYPE gBondSchemesSupported OBJECT-TYPE
SYNTAX TruthValueOrUnknown SYNTAX GBondSchemeList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bonding Capability of the G.Bond port (GBS) link partner. "Bonding Capability of the G.Bond port (GBS). This is a
This object has a value of true(1) when the remote GBS read-only bitmap of the possible bonding schemes supported by
supports the same bonding scheme as the local port. the GBS.
A value of false(2) is returned when the remote GBS does not Note that for ports supporting multiple bonding schemes the
support the same bonding scheme. actual administrative scheme is set via gBondAdminScheme
Ports whose peers cannot be reached because of the link object. The current operating bonding scheme is reflected in
state, SHALL return a value if unknown(0). the gBondOperScheme.
This object maps to the WT-157 attribute aGroupPeerBndScheme." This object maps to the WT-159 attribute
aGroupBondSchemesSupported."
REFERENCE REFERENCE
"[WT-157] 5.5.1.3" "[WT-159] 5.5.1.1"
::= { gBondPortCapabilityEntry 1 } ::= { gBondPortCapabilityEntry 1 }
gBondCapacity OBJECT-TYPE gBondCapacity OBJECT-TYPE
SYNTAX Unsigned32 (1..32) SYNTAX Unsigned32 (1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of BCEs that can be aggregated by the local GBS. "Number of BCEs that can be aggregated by the local GBS.
The number of BCEs currently assigned to a particular G.Bond The number of BCEs currently assigned to a particular G.Bond
port (gBondNumBCEs) is never greater than gBondCapacity. port (gBondNumBCEs) is never greater than gBondCapacity.
This object maps to the WT-157 attribute aGroupCapacity." This object maps to the WT-159 attribute aGroupCapacity."
REFERENCE REFERENCE
"[WT-157] 5.5.1.8" "[WT-159] 5.5.1.12"
::= { gBondPortCapabilityEntry 2 } ::= { gBondPortCapabilityEntry 2 }
gBondPeerCapacity OBJECT-TYPE gBondPeerCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32) SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of BCEs that can be aggregated by the peer GBS port. "Number of BCEs that can be aggregated by the peer GBS port.
Value of 0 is returned when peer Bonding Capacity is unknown Value of 0 is returned when peer Bonding Capacity is unknown
(peer cannot be reached). (peer cannot be reached).
This object maps to the WT-157 attribute This object maps to the WT-159 attribute aGroupPeerCapacity."
aGroupRemoteCapacity."
REFERENCE REFERENCE
"[WT-157] 5.5.1.9" "[WT-159] 5.5.1.13"
::= { gBondPortCapabilityEntry 3 } ::= { gBondPortCapabilityEntry 3 }
gBondPortStatusTable OBJECT-TYPE gBondPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortStatusEntry SYNTAX SEQUENCE OF GBondPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of G.Bond "This table provides overall status information of G.Bond
ports, complementing the generic status information from the ports, complementing the generic status information from the
ifTable of IF-MIB. Additional status information about ifTable of IF-MIB. Additional status information about
connected BCEs is available from the relevant line MIBs connected BCEs is available from the relevant line MIBs
This table contains live data from the equipment. As such,
This table contains live data from the equibcent. As such,
it is NOT persistent." it is NOT persistent."
::= { gBondPort 3 } ::= { gBondPort 3 }
gBondPortStatusEntry OBJECT-TYPE gBondPortStatusEntry OBJECT-TYPE
SYNTAX GBondPortStatusEntry SYNTAX GBondPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port Status table. "An entry in the G.Bond Port Status table.
Each entry represents an G.Bond port indexed by the ifIndex. Each entry represents an G.Bond port indexed by the ifIndex.
Note that an G.Bond GBS port runs on top of a single Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex." or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondPortStatusTable 1 } ::= { gBondPortStatusTable 1 }
GBondPortStatusEntry ::= GBondPortStatusEntry ::=
SEQUENCE { SEQUENCE {
gBondOperScheme GBondScheme,
gBondPeerOperScheme GBondScheme,
gBondUpDataRate Gauge32, gBondUpDataRate Gauge32,
gBondDownDataRate Gauge32, gBondDownDataRate Gauge32,
gBondFltStatus BITS, gBondFltStatus BITS,
gBondPortSide INTEGER, gBondPortSide INTEGER,
gBondNumBCEs Unsigned32 gBondNumBCEs Unsigned32
} }
gBondOperScheme OBJECT-TYPE
SYNTAX GBondScheme
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current operating bonding scheme of a G.Bond port.
The possible values are:
g998.1(1) - G.998.1 bonding
g998.2(2) - G.998.2 bonding
g998.3(3) - G.998.3 bonding
This object maps to the WT-159 attribute
aGroupOperBondScheme."
REFERENCE
"[WT-159] 5.5.1.4"
::= { gBondPortStatusEntry 1 }
gBondPeerOperScheme OBJECT-TYPE
SYNTAX GBondScheme
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Curent operating bonding scheme of a G.Bond port link
partner.
The possible values are:
unknown(0) - peer cannot be reached due to the link
state
g998.1(1) - G.998.1 bonding
g998.2(2) - G.998.2 bonding
g998.3(3) - G.998.3 bonding
This object maps to the WT-159 attribute
aGroupPeerOperBondScheme."
REFERENCE
"[WT-159] 5.5.1.5"
::= { gBondPortStatusEntry 2 }
gBondUpDataRate OBJECT-TYPE gBondUpDataRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A current G.Bond port operational Data Rate in the upstream "A current G.Bond port operational Data Rate in the upstream
direction, in bps. direction, in bps.
This object represents an estimation of the sum of individual This object represents an estimation of the sum of individual
BCE upstream data rates, modified to compensate for BCE upstream data rates, modified to compensate for
fragmentation and encapsulation overhead (e.g. for an Ethernet fragmentation and encapsulation overhead (e.g., for an
service, the target data rate of 10Mbps SHALL allow lossless Ethernet service, the target data rate of 10Mbps SHALL allow
transmission of full-duplex 10Mbps Ethernet frame stream with lossless transmission of full-duplex 10Mbps Ethernet frame
minimal inter-frame gap). stream with minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate == Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed." gBondDownDataRate == ifSpeed.
::= { gBondPortStatusEntry 1 }
This object maps to the WT-159 attribute aGroupUpRate."
REFERENCE
"[WT-159] 5.5.1.15"
::= { gBondPortStatusEntry 3 }
gBondDownDataRate OBJECT-TYPE gBondDownDataRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "bps" UNITS "bps"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A current G.Bond port operational Data Rate in the downstream "A current G.Bond port operational Data Rate in the downstream
direction, in bps. direction, in bps.
This object represents an estimation of the sum of individual This object represents an estimation of the sum of individual
BCE downstream data rates, modified to compensate for BCE downstream data rates, modified to compensate for
fragmentation and encapsulation overhead (e.g. for an Ethernet fragmentation and encapsulation overhead (e.g., for an
service, the target data rate of 10Mbps SHALL allow lossless Ethernet service, the target data rate of 10Mbps SHALL allow
transmission of full-duplex 10Mbps Ethernet frame stream with lossless transmission of full-duplex 10Mbps Ethernet frame
minimal inter-frame gap). stream with minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate == Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed." gBondDownDataRate == ifSpeed.
::= { gBondPortStatusEntry 2 }
This object maps to the WT-159 attribute aGroupDownRate."
REFERENCE
"[WT-159] 5.5.1.16"
::= { gBondPortStatusEntry 4 }
gBondFltStatus OBJECT-TYPE gBondFltStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
noPeer(0), noPeer(0),
peerPowerLoss(1), peerPowerLoss(1),
bceSubTypeMismatch(2), peerBondSchemeMismatch(2)
lowRate(3) bceSubTypeMismatch(3),
lowRate(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"G.Bond (GBS) port Fault Status. This is a bitmap of possible "G.Bond (GBS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are: conditions. The various bit positions are:
noPeer - peer PHY cannot be reached (e.g. noPeer - peer GBS cannot be reached (e.g.,
no BCEs attached, all BCEs are Down no BCEs attached, all BCEs are Down
etc.). etc.).
peerPowerLoss - peer PHY has indicated impending unit peerPowerLoss - peer GBS has indicated impending unit
failure due to loss of local power failure due to loss of local power
('Dying Gasp'). ('Dying Gasp').
peerBondSchemeMismatch - operating bonding scheme of a peer
GBS is different from the local one.
bceSubTypeMismatch - local BCEs in the aggregation group bceSubTypeMismatch - local BCEs in the aggregation group
are not of the same sub-type, e.g. are not of the same sub-type, e.g.,
some BCEs in the local device are -O some BCEs in the local device are -O
while others are -R subtype. while others are -R subtype.
lowRate - gBondUpRate/gBondDownRate of the port lowRate - gBondUpRate/gBondDownRate of the port
has reached or dropped below has reached or dropped below
gBondThreshLowUpRate/ gBondThreshLowUpRate/
gBondThreshLowUpRate. gBondThreshLowUpRate.
This object is intended to supplement ifOperStatus object This object is intended to supplement ifOperStatus object
in IF-MIB and ifMauMediaAvailable in MAU-MIB." in IF-MIB and ifMauMediaAvailable in MAU-MIB.
This object maps to the WT-159 attribute aGroupStatus."
REFERENCE REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable" "[WT-159] 5.5.1.9; IF-MIB, ifOperStatus; MAU-MIB,
::= { gBondPortStatusEntry 3 } ifMauMediaAvailable"
::= { gBondPortStatusEntry 5 }
gBondPortSide OBJECT-TYPE gBondPortSide OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
subscriber(1), subscriber(1),
office(2), office(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 25, line 9 skipping to change at page 29, line 31
The value of 'subscriber' indicates the port is designated as The value of 'subscriber' indicates the port is designated as
'-R' subtype (all BCEs assigned to this port are of subtype '-R' subtype (all BCEs assigned to this port are of subtype
'-R'). '-R').
The value of the 'office' indicates that the port is The value of the 'office' indicates that the port is
designated as '-O' subtype (all BCEs assigned to this port are designated as '-O' subtype (all BCEs assigned to this port are
of subtype '-O'). of subtype '-O').
The value of 'unknown' indicates that the port has no assigned The value of 'unknown' indicates that the port has no assigned
BCEs yet or that the assigned BCEs are not of the same side BCEs yet or that the assigned BCEs are not of the same side
(subTypeBCEMismatch). (subTypeBCEMismatch).
This object maps to the WT-157 attribute aGroupEnd." This object maps to the WT-159 attribute aGroupEnd."
REFERENCE REFERENCE
"[WT-157] 5.5.1.6" "[WT-159] 5.5.1.11"
::= { gBondPortStatusEntry 4 } ::= { gBondPortStatusEntry 6 }
gBondNumBCEs OBJECT-TYPE gBondNumBCEs OBJECT-TYPE
SYNTAX Unsigned32 (0..32) SYNTAX Unsigned32 (0..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of BCEs that is currently aggregated by the local GBS "Number of BCEs that is currently aggregated by the local GBS
(assigned to the G.Bond port using ifStackTable). (assigned to the G.Bond port using ifStackTable).
This number is never greater than gBondCapacity. This number is never greater than gBondCapacity.
This object SHALL be automatically incremented or decremented This object SHALL be automatically incremented or decremented
when a BCE is added or deleted to/from the G.Bond port using when a BCE is added or deleted to/from the G.Bond port using
ifStackTable. ifStackTable.
This object maps to the WT-157 attribute aGroupNumChannels" This object maps to the WT-159 attribute aGroupNumChannels"
REFERENCE REFERENCE
"[WT-157] 5.5.1.9" "[WT-159] 5.5.1.14"
::= { gBondPortStatusEntry 5 } ::= { gBondPortStatusEntry 7 }
-- The BCE group
gBondBceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondBceConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of G.Bond common aspects for the
Bonding Channel Entity (BCE) ports (modems/channels).
Entries in this table MUST be maintained in a persistent
manner."
::= { gBondBce 1 }
gBondBceConfEntry OBJECT-TYPE
SYNTAX GBondBceConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond BCE Configuration table.
Each entry represents common aspects of a G.Bond BCE port
indexed by the ifIndex. Note that an G.Bond BCE port can be
stacked below a single GBS port, also indexed by ifIndex,
possibly together with other BCE ports if GAF is enabled."
INDEX { ifIndex }
::= { gBondBceConfTable 1 }
GBondBceConfEntry ::=
SEQUENCE {
gBondBceRemoteDiscoveryCode PhysAddress
}
gBondBceRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(0|6))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A Remote Discovery Code of the BCE port at CO.
A 6 octet long Discovery Code of the peer GBS connected via
the BCE.
Reading this object results in a Discovery Get operation.
Setting this object to all zeroes results in a Discovery
Clear_if_Same operation (the value of gBondDiscoveryCode
at the peer GBS SHALL be the same as gBondDiscoveryCode of
the local GBS associated with the BCE for the operation to
succeed).
Writing a non-zero value to this object results in a
Discovery Set_if_Clear operation.
A zero-length octet string SHALL be returned on an attempt to
read this object when GAF aggregation is not enabled.
This object is irrelevant in BCE-R port subtypes (CPE side):
in this case a zero length octet string SHALL be returned on
an attempt to read this object, writing to this object SHALL
be rejected.
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.
This object maps to the WT-159 attribute
aLineRemoteDiscoveryCode."
REFERENCE
"[WT-159] 5.5.6.7"
::= { gBondBceConfEntry 1 }
-- --
-- Conformance Statements -- Conformance Statements
-- --
gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 } gBondGroups OBJECT IDENTIFIER ::= { gBondConformance 1 }
gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 } gBondCompliances OBJECT IDENTIFIER ::= { gBondConformance 2 }
-- Object Groups -- Object Groups
gBondBasicGroup OBJECT-GROUP gBondBasicGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondOperScheme,
gBondUpDataRate, gBondUpDataRate,
gBondDownDataRate, gBondDownDataRate,
gBondTargetUpDataRate, gBondTargetUpDataRate,
gBondTargetDownDataRate, gBondTargetDownDataRate,
gBondOperScheme,
gBondCapacity, gBondCapacity,
gBondNumBCEs, gBondNumBCEs,
gBondPortSide, gBondPortSide,
gBondFltStatus gBondFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects representing management information "A collection of objects representing management information
common to all types of G.Bond ports." common to all types of G.Bond ports."
::= { gBondGroups 1 } ::= { gBondGroups 1 }
skipping to change at page 26, line 10 skipping to change at page 32, line 4
gBondCapacity, gBondCapacity,
gBondNumBCEs, gBondNumBCEs,
gBondPortSide, gBondPortSide,
gBondFltStatus gBondFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects representing management information "A collection of objects representing management information
common to all types of G.Bond ports." common to all types of G.Bond ports."
::= { gBondGroups 1 } ::= { gBondGroups 1 }
gBondDiscoveryGroup OBJECT-GROUP gBondDiscoveryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondPeerBond, gBondPeerOperScheme,
gBondPeerCapacity, gBondPeerCapacity,
gBondDiscoveryCode, gBondDiscoveryCode,
gBondRemoteDiscoveryCode gBondBceRemoteDiscoveryCode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting OPTIONAL G.Bond discovery "A collection of objects supporting OPTIONAL G.Bond discovery
in G.Bond ports." in G.Bond ports."
::= { gBondGroups 2 } ::= { gBondGroups 2 }
gBondMultiSchemeGroup OBJECT-GROUP
OBJECTS {
gBondSchemeSupported,
gBondAdminScheme
}
STATUS current
DESCRIPTION
"A collection of objects providing OPTIONAL management
information for G.Bond ports supporting multiple bonding
schemes."
::= { gBondGroups 3 }
gBondAlarmConfGroup OBJECT-GROUP gBondAlarmConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondThreshLowUpRate, gBondThreshLowUpRate,
gBondThreshLowDownRate, gBondThreshLowDownRate,
gBondLowRateCrossingEnable, gBondLowRateCrossingEnable
gBondBceDeviceFaultEnable,
gBondBceConfigInitFailEnable,
gBondBceProtocolInitFailEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for configuration of alarm "A collection of objects required for configuration of alarm
thresholds and notifications in G.Bond ports." thresholds and notifications in G.Bond ports."
::= { gBondGroups 5 } ::= { gBondGroups 4 }
gBondNotificationGroup NOTIFICATION-GROUP gBondNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
gBondLowUpRateCrossing, gBondLowUpRateCrossing,
gBondLowDownRateCrossing gBondLowDownRateCrossing
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant conditions "This group supports notifications of significant conditions
associated with G.Bond ports." associated with G.Bond ports."
::= { gBondGroups 6 } ::= { gBondGroups 5 }
-- Compliance Statements -- Compliance Statements
gBondCompliance MODULE-COMPLIANCE gBondCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for G.Bond interfaces. "The compliance statement for G.Bond interfaces.
Compliance with the following external compliance statements Compliance with the following external compliance statements
is REQUIRED: is REQUIRED:
MIB Module Compliance Statement MIB Module Compliance Statement
---------- -------------------- ---------- --------------------
IF-MIB ifCompliance3 IF-MIB ifCompliance3
skipping to change at page 27, line 31 skipping to change at page 33, line 33
IF-INVERTED-STACK-MIB ifInvCompliance IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance" IF-CAP-STACK-MIB ifCapStackCompliance"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gBondBasicGroup, gBondBasicGroup,
gBondAlarmConfGroup, gBondAlarmConfGroup,
gBondNotificationGroup gBondNotificationGroup
} }
GROUP gBondDiscoveryGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting G.Bond Discovery function."
GROUP gBondMultiSchemeGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting multiple bonding schemes."
::= { gBondCompliances 1 } ::= { gBondCompliances 1 }
END END
6. Security Considerations 7. Security Considerations
There is a number of managed objects defined in the GBOND-MIB module 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 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 are writeable only when the link is Down. Writing to these
objects can have potentially disruptive effects on network operation, objects can have potentially disruptive effects on network operation,
for example: for example:
o Changing of gBondPAFAdminState to enabled MAY lead to a potential o Changing of gBondAdminScheme MAY lead to a potential locking of
locking of the link, if the peer device does not support bonding. the link, if the peer device does not support desired bonding
scheme.
o Changing of gBondPAFDiscoveryCode, before the discovery operation, o Changing of gBondDiscoveryCode, before the discovery operation,
MAY lead to a wrongful discovery, for example when two CO ports MAY lead to a wrongful discovery, for example when two CO ports
are connected to the same multi-channel RT port, while both CO are connected to the same multi-channel RT port, while both CO
ports have the same Discovery register value. ports have the same Discovery register value.
o Changing GBS configuration parameters (e.g. profile of a GBS via o Changing GBS configuration parameters (e.g., profile of a GBS via
gBondAdminProfile) MAY lead to anything from link quality and rate gBondAdminProfile) MAY lead to anything from link quality and rate
degradation to a complete link initialization failure, as ability degradation to a complete link initialization failure, as ability
of an G.Bond port to support a particular configuration depends on of an G.Bond port to support a particular configuration depends on
the copper environment. the copper environment.
o Activation of a specific line/channel can cause a severe o Activation of a specific line/channel can cause a severe
degradation of service for another G.Bond port, whose channel(s) degradation of service for another G.Bond port, whose channel(s)
MAY be affected by the cross-talk from the newly activated MAY be affected by the cross-talk from the newly activated
channel. channel.
skipping to change at page 29, line 9 skipping to change at page 35, line 20
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.
7. IANA Considerations 8. IANA Considerations
Three new values of IANAifType: g9981, g9982, g9983 SHALL be defined A new IANAifType value of 'gBond' SHALL be defined by the IANA [1] in
by the IANA [1] in the IANAifType-MIB module [IANAifType-MIB], before the IANAifType-MIB module [IANAifType-MIB], before this document is
this document is published as an RFC. published as an RFC.
Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL Additionally, an object identifier for gBondMIB MODULE-IDENTITY SHALL
be allocated by IANA in the MIB-2 transmission sub-tree, before this be allocated by IANA in the MIB-2 transmission sub-tree, before this
document is published. document is published.
8. Acknowledgments 9. Acknowledgments
This document was produced by the IETF ADSL MIB Working Group [2]. This document was produced by the [ADSLMIB] working group.
9. References 10. References
9.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in
Requirement Levels", BCP 14, RFC 2119, March 1997. RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119,
March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Ed., Perkins, D.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Ed., and J. Schoenwaelder, Ed.,
Management Information Version 2 (SMIv2)", STD 58, "Structure of Management
RFC 2578, April 1999. Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Ed., Perkins, D.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Ed., and J. Schoenwaelder, Ed.,
Conventions for SMIv2", STD 58, RFC 2579, April 1999. "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and
"Conformance Statements for SMIv2", STD 58, RFC 2580, J. Schoenwaelder, "Conformance
April 1999. Statements for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2863] McCloghrie, K. and F. Kastenholz,
"Introduction and Applicability Statements for Internet- "The Interfaces Group MIB",
Standard Management Framework", RFC 3410, December 2002. RFC 2863, June 2000.
9.2. Informative References [WT-159] Morgenstern, M., Beili, E., and N.
Nair, "Management Framework for
xDSL Bonding", DSL Forum technical
report WT-159, Nov 2007.
[802.3] IEEE, "IEEE Standard for Information technology - 10.2. Informative References
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 [802.3] IEEE, "IEEE Standard for
(SHDSL) transceivers", ITU-T Recommendation G.991.2, Information technology -
December 2003. 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.993.1] ITU-T, "Very High speed Digital Subscriber Line [ADSLMIB] IETF, "ADSL MIB (adslmib)
transceivers", ITU-T Recommendation G.993.1, June 2004. Charter", <http://www.ietf.org/
html.charters/
adslmib-charter.html>.
[G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T [G.991.2] ITU-T, "Single-pair High-speed
Recommendation G.998.1, January 2005. Digital Subscriber Line (SHDSL)
transceivers", ITU-T
Recommendation G.991.2,
December 2003, <http://
www.itu.int/rec/T-REC-G.991.2/en>.
[G.998.2] ITU-T, "Ethernet-based multi-pair bonding", ITU-T [G.993.1] ITU-T, "Very High speed Digital
Recommendation G.998.2, January 2005. Subscriber Line transceivers",
ITU-T Recommendation G.993.1,
June 2004, <http://www.itu.int/
rec/T-REC-G.993.1/en>.
[G.998.3] ITU-T, "Multi-pair bonding using time-division inverse [G.998.1] ITU-T, "ATM-based multi-pair
multiplexing", ITU-T Recommendation G.998.3, January 2005. bonding", ITU-T
Recommendation G.998.1,
January 2005, <http://www.itu.int/
rec/T-REC-G.998.1/en>.
[I-D.ietf-adslmib-gbond-atm-mib] [G.998.2] ITU-T, "Ethernet-based multi-pair
Morgenstern, M. and N. Nair, "ATM-based xDSL Bonded bonding", ITU-T
Interfaces MIB", draft-ietf-adslmib-gbond-atm-mib-00 (work Recommendation G.998.2,
in progress), February 2007. January 2005, <http://www.itu.int/
rec/T-REC-G.998.2/en>.
[I-D.ietf-adslmib-gbond-eth-mib] [G.998.3] ITU-T, "Multi-pair bonding using
Beili, E. and M. Morgenstern, "Ethernet-based xDSL Bonded time-division inverse
Interfaces MIB", draft-ietf-adslmib-gbond-eth-mib-00 (work multiplexing", ITU-T
in progress), February 2007. Recommendation G.998.3,
January 2005, <http://www.itu.int/
rec/T-REC-G.998.3/en>.
[I-D.ietf-adslmib-gbond-tdim-mib] [I-D.ietf-adslmib-gbond-atm-mib] Morgenstern, M. and N. Nair, "ATM-
Beili, E. and N. Nair, "TDIM-based xDSL Bonded Interfaces based xDSL Bonded Interfaces MIB",
MIB", draft-ietf-adslmib-gbond-tdim-mib-00 (work in draft-ietf-adslmib-gbond-atm-mib-
progress), February 2006. 01 (work in progress),
November 2007.
[I-D.ietf-adslmib-vsl2-mib] [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern,
Morgenstern, M., "Definitions of Managed Objects for Very "Ethernet-based xDSL Bonded
High Speed Digital Subscriber Line 2 (VDSL2)", Interfaces MIB", draft-ietf-
draft-ietf-adslmib-vdsl2-01 (work in progress), adslmib-gbond-eth-mib-01 (work in
August 2006. progress), November 2007.
[I-D.ietf-hubmib-efm-cu-mib] [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E. and N. Nair, "TDIM-based
Beili, E., "Ethernet in the First Mile Copper (EFMCu) xDSL Bonded Interfaces MIB", draft
Interfaces MIB", draft-ietf-hubmib-efm-cu-mib-07 (work in -ietf-adslmib-gbond-tdim-mib-01
progress), February 2007. (work in progress), November 2006.
[I-D.ietf-hubmib-rfc3636bis] [I-D.ietf-adslmib-vdsl2-mib] Morgenstern, M., Baillie, S., and
Beili, E., "Definitions of Managed Objects for IEEE 802.3 U. Bonollo, "Definitions of
Medium Attachment Units (MAUs)", Managed Objects for Very High
draft-ietf-hubmib-rfc3636bis-05 (work in progress), Speed Digital Subscriber Line 2
July 2006. (VDSL2)",
draft-ietf-adslmib-vdsl2-03 (work
in progress), October 2007.
[IANAifType-MIB] [IANAifType-MIB] Internet Assigned Numbers
Internet Assigned Numbers Authority (IANA), "IANAifType Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition", <h
http://www.iana.org/assignments/ianaiftype-mib. ttp://www.iana.org/assignments/
ianaiftype-mib>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2864] McCloghrie, K. and G. Hanson, "The
MIB", RFC 2863, June 2000. Inverted Stack Table Extension to
the Interfaces Group MIB",
RFC 2864, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC3410] Case, J., Mundy, R., Partain, D.,
Extension to the Interfaces Group MIB", RFC 2864, and B. Stewart, "Introduction and
June 2000. Applicability Statements for
Internet-Standard Management
Framework", RFC 3410,
December 2002.
[RFC3440] Ly, F. and G. Bathrick, "Definitions of Extension Managed [RFC3440] Ly, F. and G. Bathrick,
Objects for Asymmetric Digital Subscriber Lines", "Definitions of Extension Managed
RFC 3440, December 2002. Objects for Asymmetric Digital
Subscriber Lines", RFC 3440,
December 2002.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed
Ethernet-like Interface Types", RFC 3635, September 2003. Objects for the Ethernet-like
Interface Types", RFC 3635,
September 2003.
[RFC3728] Ray, B. and R. Abbi, "Definitions of Managed Objects for [RFC3728] Ray, B. and R. Abbi, "Definitions
Very High Speed Digital Subscriber Lines (VDSL)", of Managed Objects for Very High
RFC 3728, February 2004. Speed Digital Subscriber Lines
(VDSL)", RFC 3728, February 2004.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed [RFC4181] Heard, C., "Guidelines for Authors
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and and Reviewers of MIB Documents",
Single-Pair High-Speed Digital Subscriber Line (SHDSL) BCP 111, RFC 4181, September 2005.
Lines", RFC 4319, December 2005.
[RFC4706] Morgenstern, M., Dodge, M., Baillie, S., and U. Bonollo, [RFC4319] Sikes, C., Ray, B., and R. Abbi,
"Definitions of Managed Objects for Asymmetric Digital "Definitions of Managed Objects
Subscriber Line 2 (ADSL2)", RFC 4706, November 2006. for High Bit-Rate DSL - 2nd
generation (HDSL2) and Single-Pair
High-Speed Digital Subscriber Line
(SHDSL) Lines", RFC 4319,
December 2005.
[WT-157] Morgenstern, M., Beili, E., and N. Nair, "Management [RFC4706] Morgenstern, M., Dodge, M.,
Framework for xDSL Bonding", DSL Forum technical Baillie, S., and U. Bonollo,
report WT-157, Jan 2006. "Definitions of Managed Objects
for Asymmetric Digital Subscriber
Line 2 (ADSL2)", RFC 4706,
November 2006.
[af-phy-0086] [RFC4836] Beili, E., "Definitions of Managed
ATM Forum, "Inverse Multiplexing for ATM (IMA) Objects for IEEE 802.3 Medium
Specification Version 1.1", ATM Forum specification af- Attachment Units (MAUs)",
pfy-0086.001, March 1999. RFC 4836, April 2007.
[RFC5066] Beili, E., "Ethernet in the First
Mile Copper (EFMCu) Interfaces
MIB", RFC 5066, November 2007.
[af-phy-0086] ATM Forum, "Inverse Multiplexing
for ATM (IMA) Specification
Version 1.1", ATM Forum
specification af-pfy-0086.001,
March 1999.
URIs URIs
[1] <http://www.iana.org/> [1] <http://www.iana.org/>
[2] <http://www.ietf.org/html.charters/adslmib-charter.html>
Authors' Addresses Authors' Addresses
Edward Beili Edward Beili
Actelis Networks Actelis Networks
25 Bazel St. 25 Bazel St.
Petach-Tikva 49103 Petach-Tikva 49103
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
Email: edward.beili@actelis.com EMail: edward.beili@actelis.com
Moti Morgenstern Moti Morgenstern
ECI Telecom ECI Telecom
30 Hasivim St. 30 Hasivim St.
Petach-Tikva 49517 Petach-Tikva 49517
Israel Israel
Phone: +972-3-926-6258 Phone: +972-3-926-6258
Email: moti.morgenstern@ecitele.com EMail: moti.morgenstern@ecitele.com
Narendranath Nair Narendranath Nair
Wipro Technologies Wipro Technologies
Keonics Electronics City Keonics Electronics City
Bangalore 560 100 Bangalore 560 100
India India
Phone: +91-80-2852-0408 x85338 Phone: +91-80-2852-0408 x85338
Email: narendranath.nair@wipro.com EMail: narendranath.nair@wipro.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and 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
skipping to change at page 33, line 45 skipping to change at page 41, line 45
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 this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
 End of changes. 171 change blocks. 
332 lines changed or deleted 675 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/