draft-ietf-adslmib-gbond-mib-03.txt   draft-ietf-adslmib-gbond-mib-04.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: November 21, 2009 ECI Telecom Expires: November 29, 2010 ECI Telecom
May 20, 2009 May 28, 2010
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-03.txt draft-ietf-adslmib-gbond-mib-04.txt
Abstract
This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP-based internets.
This document proposes an extension to the Interfaces Group MIB with
a set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
G.998.1, G.998.2 and G.998.3. The MIB modules specific to each
bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and
GBOND-TDIM-MIB respectively.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 This Internet-Draft will expire on November 29, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 21, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This document defines Management Information Base (MIB) module for described in the Simplified BSD License.
use with network management protocols in TCP/IP-based internets.
This document proposes an extension to the Interfaces Group MIB with
a set of common objects for managing multi-pair bonded Digital
Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations
G.998.1, G.998.2 and G.998.3. The MIB modules specific to each
bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and
GBOND-TDIM-MIB respectively.
Table of Contents 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. Relationship to Other MIB modules . . . . . . . . . . . . . . 4 4. Relationship to Other MIB modules . . . . . . . . . . . . . . 4
4.1. Relationship 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. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7 4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 2, line 33 skipping to change at page 2, line 30
4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 4.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
4.2. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11 4.2. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 12 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 12
5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 12 5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 12
6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 16 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 60
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 61 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.1. Normative References . . . . . . . . . . . . . . . . . . . 61 10.1. Normative References . . . . . . . . . . . . . . . . . . . 62
10.2. Informative References . . . . . . . . . . . . . . . . . . 62 10.2. Informative References . . . . . . . . . . . . . . . . . . 63
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 11, line 31 skipping to change at page 11, line 31
| | for BCEs. | | | for BCEs. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1: G.Bond interpretation of IF-MIB objects Table 1: G.Bond interpretation of IF-MIB objects
4.2. Relationship 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-vdsl2-mib] for [RFC3728] for VDSL or VDSL2-LINE-MIB [RFC5650] 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).
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
The main management objects defined in the GBOND-MIB module are split The main management objects defined in the GBOND-MIB module are split
into 2 groups: into 2 groups, structured as recommended by RFC 4181 [RFC4181]:
o gBondPort - containing objects for configuration, capabilities, o gBondPort - containing objects for configuration, capabilities,
status and notifications, common to all G.Bond ports (GBS). status, historical performance monitoring and notifications,
common to all G.Bond ports (GBS).
o gBondBce - containing a single common object for configuration of o gBondBce - containing a single common object for configuration of
the remote discovery code per BCE. Note that the rest of the the remote discovery code per BCE. Note that the rest of the
objects for BCE configuration, capabilities, status and objects for BCE configuration, capabilities, status and
notifications, is located in relevant xDSL line MIB modules as notifications, is located in relevant xDSL line MIB modules as
well as in the bonding scheme specific MIB modules. well as in the bonding scheme specific MIB modules.
5.2. Performance Monitoring 5.2. Performance Monitoring
The OPTIONAL performance monitoring counters, thresholds and history The OPTIONAL performance monitoring counters, thresholds and history
buckets (interval-counters) defined in [TR-159] are implemented using buckets (interval-counters) defined in [TR-159] are implemented using
the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705]. the textual conventions defined in the HC-PerfHist-TC-MIB [RFC3705].
The HC-PerfHist-TC-MIB defines 64-bit versions of the textual The HC-PerfHist-TC-MIB defines 64-bit versions of the textual
conventions found in PerfHist-TC-MIB [RFC3593]. conventions found in PerfHist-TC-MIB [RFC3593].
The agent SHOULD align the beginning of each interval to a fifteen The agent SHOULD align the beginning of each interval to a fifteen
minute boundary of a wall clock. Likewise, the beginning of each one minute boundary of a wall clock. Likewise, the beginning of each one
day intervals SHOULD be aligned with the start of a day. day intervals SHOULD be aligned with the start of a day.
Counters are not reset when a GBS is reinitialized, only when the Counters are not reset when a GBS is reinitialized, but rather only
agent is reset or reinitialized (or under specific request outside when the agent is reset or reinitialized (or under specific request
the scope of this MIB module). outside the scope of this MIB module).
5.3. Mapping of DSL Forum TR-159 Managed Objects 5.3. Mapping of DSL Forum TR-159 Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [TR-159] and managed objects defined in this (attributes) defined in [TR-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 Object | | G.Bond Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
skipping to change at page 13, line 19 skipping to change at page 13, line 19
| aGroupPeerCapacity | gBondPeerCapacity | | aGroupPeerCapacity | gBondPeerCapacity |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupNumChannels | gBondNumBCEs | | aGroupNumChannels | gBondNumBCEs |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupName | ifName (IF-MIB) | | aGroupName | ifName (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupDiscoveryCode | gBondDiscoveryCode | | aGroupDiscoveryCode | gBondDiscoveryCode |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupUpRate | gBondUpDataRate | | aGroupUpRate | gBondUpDataRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupDownRate | gBondDownDataRate | | aGroupDownRate | gBondDnDataRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupTargetUpRate | gBondTargetUpDataRate | | aGroupTargetUpRate | gBondTargetUpDataRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupTargetDownRate | gBondTargetDownDataRate | | aGroupTargetDownRate | gBondTargetDnDataRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupThreshLowUpRate | gBondThreshLowUpRate | | aGroupThreshLowUpRate | gBondThreshLowUpRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupThreshLowDownRate | gBondThreshLowDownRate | | aGroupThreshLowDownRate | gBondThreshLowDnRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable | | aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing | | nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLowDownRateCrossing | gBondLowDownRateCrossing | | nGroupLowDownRateCrossing | gBondLowDnRateCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB | | aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB |
| | doesn't provide a control for | | | doesn't provide a control for |
| | the linkUp/linkDown | | | the linkUp/linkDown |
| | notifications. Can we define a | | | notifications. Can we define a |
| | control in one MIB module while | | | control in one MIB module while |
| | the notifications are in | | | the notifications are in |
| | another?_ | | | another?_ |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLinkUp | linkDown (IF-MIB) | | nGroupLinkUp | linkDown (IF-MIB) |
skipping to change at page 16, line 17 skipping to change at page 16, line 17
| | the linkUp/linkDown | | | the linkUp/linkDown |
| | notifications. Can we define a | | | notifications. Can we define a |
| | control in one MIB module while | | | control in one MIB module while |
| | the notifications are in | | | the notifications are in |
| | another?_ | | | another?_ |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nLineUp | linkUp (IF-MIB) | | nLineUp | linkUp (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nLineDown | linkDown (IF-MIB) | | nLineDown | linkDown (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oChannel - Basic Package | |
| (Mandatory) | |
+---------------------------------+---------------------------------+
| aChannelID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aChannelGroupID | |
+---------------------------------+---------------------------------+
| aChannelType | ifType (IF-MIB) |
+---------------------------------+---------------------------------+
| aChannelOperState | ifOperStatus (IF-MIB) |
+---------------------------------+---------------------------------+
| aChannelStatus | *dsl*CurrStatus |
| | (*DSL-LINE-MIB), |
| | xdsl2ChStatus*Status |
| | (VDSL2-LINE-MIB) |
+---------------------------------+---------------------------------+
Table 2: Mapping of TR-159 Managed Objects Table 2: Mapping of TR-159 Managed Objects
6. 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, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
skipping to change at page 17, line 8 skipping to change at page 17, line 24
HCPerfIntervalCount, HCPerfIntervalCount,
HCPerfIntervalThreshold, HCPerfIntervalThreshold,
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed, HCPerfTimeElapsed,
HCPerfTotalCount HCPerfTotalCount
FROM HC-PerfHist-TC-MIB -- [RFC3705] FROM HC-PerfHist-TC-MIB -- [RFC3705]
; ;
gBondMIB MODULE-IDENTITY gBondMIB MODULE-IDENTITY
LAST-UPDATED "200905200000Z" -- May 20, 2009 LAST-UPDATED "201005280000Z" -- May 28, 2010
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
skipping to change at page 18, line 37 skipping to change at page 19, line 5
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sublayer
PM - Performance Monitoring PM - Performance Monitoring
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCA - Threshold Crossing Alert TCA - Threshold Crossing Alert
Copyright (C) The IETF Trust (2009). Copyright (C) The IETF Trust (2009).
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "200905200000Z" -- May 20, 2009 REVISION "201005280000Z" -- May 28, 2010
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.
skipping to change at page 21, line 11 skipping to change at page 21, line 26
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 TR-159 notification This object maps to the TR-159 notification
nGroupLowUpRateCrossing." nGroupLowUpRateCrossing."
REFERENCE REFERENCE
"[TR-159] 5.5.1.24" "[TR-159] 5.5.1.24"
::= { gBondPortNotifications 1 } ::= { gBondPortNotifications 1 }
gBondLowDownRateCrossing NOTIFICATION-TYPE gBondLowDnRateCrossing 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, gBondDnDataRate,
gBondThreshLowDownRate gBondThreshLowDnRate
} }
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. gBondThreshLowDnRate.
This notification MAY be sent 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. gBondLowDnRateCrossing 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 e.g., an impulse noise, alien crosstalk, or a
micro-interruption may temporarily drop one or more BCEs in micro-interruption may temporarily drop one or more BCEs in
the aggregation group, causing a rate degradation of the the aggregation group, causing a rate degradation of the
aggregated G.Bond link. The dropped BCEs would then try to aggregated G.Bond link. The dropped BCEs would then try to
re-initialize, possibly at a lower rate than before, re-initialize, possibly at a lower rate than before,
adjusting the rate to provide required target SNR margin. adjusting the rate to provide required target SNR margin.
skipping to change at page 25, line 16 skipping to change at page 25, line 31
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, gBondAdminScheme GBondScheme,
gBondPeerAdminScheme GBondScheme, gBondPeerAdminScheme GBondScheme,
gBondDiscoveryCode PhysAddress, gBondDiscoveryCode PhysAddress,
gBondTargetUpDataRate Unsigned32, gBondTargetUpDataRate Unsigned32,
gBondTargetDownDataRate Unsigned32, gBondTargetDnDataRate Unsigned32,
gBondThreshLowUpRate Unsigned32, gBondThreshLowUpRate Unsigned32,
gBondThreshLowDownRate Unsigned32, gBondThreshLowDnRate Unsigned32,
gBondLowRateCrossingEnable TruthValue, gBondLowRateCrossingEnable TruthValue,
gBondPerfTcaConfProfile SnmpAdminString, gBondPerfTcaConfProfile SnmpAdminString,
gBondPerfTcaEnable TruthValue gBondPerfTcaEnable TruthValue
} }
gBondAdminScheme OBJECT-TYPE gBondAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 28, line 21 skipping to change at page 28, line 37
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.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupTargetUpRate." aGroupTargetUpRate."
REFERENCE REFERENCE
"[TR-159] 5.5.1.17" "[TR-159] 5.5.1.17"
::= { gBondPortConfEntry 4 } ::= { gBondPortConfEntry 4 }
gBondTargetDownDataRate OBJECT-TYPE gBondTargetDnDataRate OBJECT-TYPE
SYNTAX Unsigned32(0|1..10000000) SYNTAX Unsigned32(0|1..10000000)
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 (gBondDnDataRate) could be less
than gBondTargetDownDataRate. than gBondTargetDnDataRate.
The value is limited above by 10 Gbps, to accomodate very The value is limited above by 10 Gbps, to accomodate very
high speed bonded xDSL interfaces (e.g. 32 x 100Mbps). high speed bonded xDSL interfaces (e.g. 32 x 100Mbps).
The value between 1 and 10000000 indicates that the total The value between 1 and 10000000 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 29, line 51 skipping to change at page 30, line 20
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.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupthreshLowUpRate." aGroupthreshLowUpRate."
REFERENCE REFERENCE
"[TR-159] 5.5.1.21" "[TR-159] 5.5.1.21"
::= { gBondPortConfEntry 6 } ::= { gBondPortConfEntry 6 }
gBondThreshLowDownRate OBJECT-TYPE gBondThreshLowDnRate OBJECT-TYPE
SYNTAX Unsigned32(1..10000000) SYNTAX Unsigned32(1..10000000)
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 gBondDnDataRate for this port reaches/drops below or exceeds
this threshold, an gBondLowDownRateCrossing notification MAY this threshold, an gBondLowDnRateCrossing 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.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupThreshDownUpRate." aGroupThreshDownUpRate."
REFERENCE REFERENCE
"[TR-159] 5.5.1.22" "[TR-159] 5.5.1.22"
::= { gBondPortConfEntry 7 } ::= { gBondPortConfEntry 7 }
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 gBondLowDnRateCrossing 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.
skipping to change at page 34, line 30 skipping to change at page 34, line 44
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, gBondOperScheme GBondScheme,
gBondPeerOperScheme GBondScheme, gBondPeerOperScheme GBondScheme,
gBondUpDataRate Gauge32, gBondUpDataRate Gauge32,
gBondDownDataRate Gauge32, gBondDnDataRate Gauge32,
gBondFltStatus BITS, gBondFltStatus BITS,
gBondPortSide INTEGER, gBondPortSide INTEGER,
gBondNumBCEs Unsigned32 gBondNumBCEs Unsigned32
} }
gBondOperScheme OBJECT-TYPE gBondOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 41 skipping to change at page 36, line 8
"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 fragmentation and encapsulation overhead (e.g., for an
Ethernet service, the target data rate of 10Mbps SHALL allow Ethernet service, the target data rate of 10Mbps SHALL allow
lossless transmission of full-duplex 10Mbps Ethernet frame lossless transmission of full-duplex 10Mbps Ethernet frame
stream with minimal inter-frame gap). stream with minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate == Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed. gBondDnDataRate == ifSpeed.
This object maps to the TR-159 attribute aGroupUpRate." This object maps to the TR-159 attribute aGroupUpRate."
REFERENCE REFERENCE
"[TR-159] 5.5.1.15" "[TR-159] 5.5.1.15"
::= { gBondPortStatusEntry 3 } ::= { gBondPortStatusEntry 3 }
gBondDownDataRate OBJECT-TYPE gBondDnDataRate 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 fragmentation and encapsulation overhead (e.g., for an
Ethernet service, the target data rate of 10Mbps SHALL allow Ethernet service, the target data rate of 10Mbps SHALL allow
lossless transmission of full-duplex 10Mbps Ethernet frame lossless transmission of full-duplex 10Mbps Ethernet frame
stream with minimal inter-frame gap). stream with minimal inter-frame gap).
Note that for symmetrical interfaces gBondUpDataRate == Note that for symmetrical interfaces gBondUpDataRate ==
gBondDownDataRate == ifSpeed. gBondDnDataRate == ifSpeed.
This object maps to the TR-159 attribute aGroupDownRate." This object maps to the TR-159 attribute aGroupDownRate."
REFERENCE REFERENCE
"[TR-159] 5.5.1.16" "[TR-159] 5.5.1.16"
::= { gBondPortStatusEntry 4 } ::= { gBondPortStatusEntry 4 }
gBondFltStatus OBJECT-TYPE gBondFltStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
noPeer(0), noPeer(0),
peerPowerLoss(1), peerPowerLoss(1),
skipping to change at page 36, line 47 skipping to change at page 37, line 17
etc.). etc.).
peerPowerLoss - peer GBS 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 peerBondSchemeMismatch - operating bonding scheme of a peer
GBS is different from the local one. 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/gBondDnRate 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 TR-159 attribute aGroupStatus." This object maps to the TR-159 attribute aGroupStatus."
REFERENCE REFERENCE
"[TR-159] 5.5.1.9; IF-MIB, ifOperStatus; MAU-MIB, "[TR-159] 5.5.1.9; IF-MIB, ifOperStatus; MAU-MIB,
skipping to change at page 38, line 18 skipping to change at page 38, line 34
-- Performance Monitoring group -- Performance Monitoring group
gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 } gBondPortPM OBJECT IDENTIFIER ::= { gBondPort 4 }
gBondPortPerfCurrTable OBJECT-TYPE gBondPortPerfCurrTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPerfCurrEntry SYNTAX SEQUENCE OF GBondPortPerfCurrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains current Performance Monitoring information "This table contains current Performance Monitoring (PM)
for GBS ports. This table contains live data from the equipment information for a GBS port. This table contains live data from
and as such is NOT persistent." the equipment and as such is NOT persistent."
::= { gBondPortPM 1 } ::= { gBondPortPM 1 }
gBondPortPerfCurrEntry OBJECT-TYPE gBondPortPerfCurrEntry OBJECT-TYPE
SYNTAX GBondPortPerfCurrEntry SYNTAX GBondPortPerfCurrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port PM table. "An entry in the G.Bond Port PM 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
skipping to change at page 44, line 22 skipping to change at page 44, line 39
::= { gBondPortPerfCurrEntry 15 } ::= { gBondPortPerfCurrEntry 15 }
-- PM history: 15-min buckets -- PM history: 15-min buckets
gBondPortPerf15MinTable OBJECT-TYPE gBondPortPerf15MinTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPerf15MinEntry SYNTAX SEQUENCE OF GBondPortPerf15MinEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains historical 15-minute buckets of Performance "This table contains historical 15-minute buckets of Performance
Monitoring information for a GBS port (a raw for each 15-minute Monitoring information for a GBS port (a row for each 15-minute
interval, up to 96 intervals). interval, up to 96 intervals).
Entries in this table MUST be maintained in a persistent manner." Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 2 } ::= { gBondPortPM 2 }
gBondPortPerf15MinEntry OBJECT-TYPE gBondPortPerf15MinEntry OBJECT-TYPE
SYNTAX GBondPortPerf15MinEntry SYNTAX GBondPortPerf15MinEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port historical 15-minute PM table. "An entry in the G.Bond Port historical 15-minute PM table.
skipping to change at page 46, line 50 skipping to change at page 47, line 19
::= { gBondPortPerf15MinEntry 6 } ::= { gBondPortPerf15MinEntry 6 }
-- PM history: 1-day buckets -- PM history: 1-day buckets
gBondPortPerf1DayTable OBJECT-TYPE gBondPortPerf1DayTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondPortPerf1DayEntry SYNTAX SEQUENCE OF GBondPortPerf1DayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains historical 1-day buckets of Performance "This table contains historical 1-day buckets of Performance
Monitoring information for a GBS port (a raw for each 1-day Monitoring information for a GBS port (a row for each 1-day
interval, up to 7 intervals). interval, up to 7 intervals).
Entries in this table MUST be maintained in a persistent manner." Entries in this table MUST be maintained in a persistent manner."
::= { gBondPortPM 3 } ::= { gBondPortPM 3 }
gBondPortPerf1DayEntry OBJECT-TYPE gBondPortPerf1DayEntry OBJECT-TYPE
SYNTAX GBondPortPerf1DayEntry SYNTAX GBondPortPerf1DayEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond Port historical 1-day PM table. "An entry in the G.Bond Port historical 1-day PM table.
Each entry represents performance monitoring data for a GBS port, Each entry represents performance monitoring data for a GBS port,
skipping to change at page 55, line 19 skipping to change at page 55, line 35
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, gBondOperScheme,
gBondUpDataRate, gBondUpDataRate,
gBondDownDataRate, gBondDnDataRate,
gBondTargetUpDataRate, gBondTargetUpDataRate,
gBondTargetDownDataRate, gBondTargetDnDataRate,
gBondOperScheme, 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."
skipping to change at page 56, line 16 skipping to change at page 56, line 31
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing OPTIONAL management "A collection of objects providing OPTIONAL management
information for G.Bond ports supporting multiple bonding information for G.Bond ports supporting multiple bonding
schemes." schemes."
::= { gBondGroups 3 } ::= { gBondGroups 3 }
gBondTcaConfGroup OBJECT-GROUP gBondTcaConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondThreshLowUpRate, gBondThreshLowUpRate,
gBondThreshLowDownRate, gBondThreshLowDnRate,
gBondLowRateCrossingEnable gBondLowRateCrossingEnable
} }
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 4 } ::= { gBondGroups 4 }
gBondTcaNotificationGroup NOTIFICATION-GROUP gBondTcaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
gBondLowUpRateCrossing, gBondLowUpRateCrossing,
gBondLowDownRateCrossing gBondLowDnRateCrossing
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant conditions "This group supports notifications of significant conditions
(non-PM threshold crossing alerts) associated with G.Bond ports." (non-PM threshold crossing alerts) associated with G.Bond ports."
::= { gBondGroups 5 } ::= { gBondGroups 5 }
gBondPerfCurrGroup OBJECT-GROUP gBondPerfCurrGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondPerfES, gBondPerfES,
skipping to change at page 63, line 44 skipping to change at page 64, line 7
January 2005, <http://www.itu.int/ January 2005, <http://www.itu.int/
rec/T-REC-G.998.2/en>. rec/T-REC-G.998.2/en>.
[G.998.3] ITU-T, "Multi-pair bonding using [G.998.3] ITU-T, "Multi-pair bonding using
time-division inverse time-division inverse
multiplexing", ITU-T multiplexing", ITU-T
Recommendation G.998.3, Recommendation G.998.3,
January 2005, <http://www.itu.int/ January 2005, <http://www.itu.int/
rec/T-REC-G.998.3/en>. rec/T-REC-G.998.3/en>.
[I-D.ietf-adslmib-gbond-atm-mib] Beili, E. and M. Morgenstern, [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded
"ATM-based xDSL Bonded Interfaces Interfaces MIB", draft-ietf-
MIB", draft-ietf-adslmib-gbond- adslmib-gbond-atm-mib-01 (work in
atm-mib-02 (work in progress), progress), May 2010.
May 2009.
[I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern, [I-D.ietf-adslmib-gbond-eth-mib] Beili, E. and M. Morgenstern,
"Ethernet-based xDSL Bonded "Ethernet-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-eth-mib-02 (work in adslmib-gbond-eth-mib-02 (work in
progress), May 2009. progress), May 2010.
[I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded [I-D.ietf-adslmib-gbond-tdim-mib] Beili, E., "TDIM-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-tdim-mib-02 (work in adslmib-gbond-tdim-mib-03 (work in
progress), May 2009. progress), May 2010.
[I-D.ietf-adslmib-vdsl2-mib] Morgenstern, M., Baillie, S., and
U. Bonollo, "Definitions of
Managed Objects for Very High
Speed Digital Subscriber Line 2
(VDSL2)",
draft-ietf-adslmib-vdsl2-07 (work
in progress), May 2009.
[IANAifType-MIB] Internet Assigned Numbers [IANAifType-MIB] Internet Assigned Numbers
Authority (IANA), "IANAifType Authority (IANA), "IANAifType
Textual Convention definition", <h Textual Convention definition", <h
ttp://www.iana.org/assignments/ ttp://www.iana.org/assignments/
ianaiftype-mib>. ianaiftype-mib>.
[RFC2864] McCloghrie, K. and G. Hanson, "The [RFC2864] McCloghrie, K. and G. Hanson, "The
Inverted Stack Table Extension to Inverted Stack Table Extension to
the Interfaces Group MIB", the Interfaces Group MIB",
skipping to change at page 65, line 36 skipping to change at page 65, line 38
[RFC4836] Beili, E., "Definitions of Managed [RFC4836] Beili, E., "Definitions of Managed
Objects for IEEE 802.3 Medium Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", Attachment Units (MAUs)",
RFC 4836, April 2007. RFC 4836, April 2007.
[RFC5066] Beili, E., "Ethernet in the First [RFC5066] Beili, E., "Ethernet in the First
Mile Copper (EFMCu) Interfaces Mile Copper (EFMCu) Interfaces
MIB", RFC 5066, November 2007. MIB", RFC 5066, November 2007.
[RFC5650] Morgenstern, M., Baillie, S., and
U. Bonollo, "Definitions of
Managed Objects for Very High
Speed Digital Subscriber Line 2
(VDSL2)", RFC 5650,
September 2009.
[af-phy-0086] ATM Forum, "Inverse Multiplexing [af-phy-0086] ATM Forum, "Inverse Multiplexing
for ATM (IMA) Specification for ATM (IMA) Specification
Version 1.1", ATM Forum Version 1.1", ATM Forum
specification af-pfy-0086.001, specification af-pfy-0086.001,
March 1999. March 1999.
URIs URIs
[1] <http://www.iana.org/> [1] <http://www.iana.org/>
 End of changes. 47 change blocks. 
92 lines changed or deleted 102 lines changed or added

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