draft-ietf-adslmib-gbond-mib-06.txt   draft-ietf-adslmib-gbond-mib-07.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: September 15, 2011 ECI Telecom Expires: November 27, 2011 ECI Telecom
March 14, 2011 May 26, 2011
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-06.txt draft-ietf-adslmib-gbond-mib-07.txt
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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on September 15, 2011. This Internet-Draft will expire on November 27, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 7 4.1.2. xDSL Bonding . . . . . . . . . . . . . . . . . . . . . 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. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules . . . 11
4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11 4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 11
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 12
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 . . . . . . . . . . . 17 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 60
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.1. Normative References . . . . . . . . . . . . . . . . . . . 62 10.1. Normative References . . . . . . . . . . . . . . . . . . . 62
10.2. Informative References . . . . . . . . . . . . . . . . . . 63 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
skipping to change at page 4, line 28 skipping to change at page 4, line 28
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 document specifies a Structure of Management Information (SMI). This document specifies a
MIB module that is compliant to the SMIv2, which is described in STD MIB module that is compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [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", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this 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 [TR-159], defining a management model and Framework for xDSL Bonding [TR-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. Relationship 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
skipping to change at page 7, line 40 skipping to change at page 7, line 40
The GBOND-MIB module allows a Network Management application to query The GBOND-MIB module allows a Network Management application to query
Bonding capability and enable/disable it if supported. Note that Bonding capability and enable/disable it if supported. Note that
enabling Bonding effectively turns on fragmentation and re-assembly, enabling Bonding effectively turns on fragmentation and re-assembly,
even on a single-BCE port. even 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), via [G.994.1] handshake respective aggregation groups (GBS), via [G.994.1] handshake (G.hs)
protocol. This information can then be used to detect copper protocol. This information can then be used to detect copper
misconnections or for an automatic assignment of the local BCEs into misconnections or for an automatic assignment of the local BCEs into
aggregation groups instead of a fixed pre-configuration. aggregation groups 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. results.
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
skipping to change at page 10, line 42 skipping to change at page 10, line 42
The following table summarizes G.Bond specific interpretations for The following table summarizes G.Bond specific interpretations for
some of the ifTable objects specified by the mandatory some of the ifTable objects specified by the mandatory
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 are 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 | g9981, g9982 or g9982 for the ATM, Ethernet or |
| | TDIM GBS respectively, shdsl(169) for G.SHDSL | | | TDIM GBS respectively, shdsl(169) for G.SHDSL |
| | BCE, 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 |
skipping to change at page 14, line 5 skipping to change at page 14, line 5
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupThreshLowDownRate | gBondThreshLowDnRate | | aGroupThreshLowDownRate | gBondThreshLowDnRate |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable | | aGroupLowRateCrossingEnable | gBondLowRateCrossingEnable |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLowUpRateCrossing | gBondLowUpRateCrossing | | nGroupLowUpRateCrossing | gBondLowUpRateCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLowDownRateCrossing | gBondLowDnRateCrossing | | nGroupLowDownRateCrossing | gBondLowDnRateCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupLinkUpDownEnable | _EdNote: Currently IF-MIB | | aGroupLinkUpDownEnable | _Note: Currently IF-MIB does |
| | doesn't provide a control for | | | not provide a control object |
| | the linkUp/linkDown | | | for the linkUp/linkDown |
| | notifications. Can we define a | | | notifications._ |
| | control in one MIB module while |
| | the notifications are in |
| | another?_ |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLinkUp | linkDown (IF-MIB) | | nGroupLinkUp | linkDown (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupLinkDown | linkUp (IF-MIB) | | nGroupLinkDown | linkUp (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oBondingGroup - PM Package | | | oBondingGroup - PM Package | |
| (Optional) | | | (Optional) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfES | gBondPerfES | | aGroupPerfES | gBondPerfES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
skipping to change at page 15, line 4 skipping to change at page 14, line 49
| aGroupPerfThreshold15MinSES | gBondPerfThereshold15MinSES | | aGroupPerfThreshold15MinSES | gBondPerfThereshold15MinSES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfThreshold15MinUAS | gBondPerfThereshold15MinUAS | | aGroupPerfThreshold15MinUAS | gBondPerfThereshold15MinUAS |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupPerfTca15MinES | gBondPerfTca15MinESCrossing | | nGroupPerfTca15MinES | gBondPerfTca15MinESCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupPerfTca15MinSES | gBondPerfTca15MinSESCrossing | | nGroupPerfTca15MinSES | gBondPerfTca15MinSESCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nGroupPerfTca15MinUAS | gBondPerfTca15MinUASCrossing | | nGroupPerfTca15MinUAS | gBondPerfTca15MinUASCrossing |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
+---------------------------------+---------------------------------+
| aGroupPerf1DayValidIntervals | gBondPerf1DayValidIntervals | | aGroupPerf1DayValidIntervals | gBondPerf1DayValidIntervals |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerf1DayInvalidIntervals | gBondPerf1DayInvalidIntervals | | aGroupPerf1DayInvalidIntervals | gBondPerf1DayInvalidIntervals |
+---------------------------------+---------------------------------+
| aGroupPerfCurr1DayTimeElapsed | gBondPerfCurr1DayTimeElapsed | | aGroupPerfCurr1DayTimeElapsed | gBondPerfCurr1DayTimeElapsed |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfCurr1DayES | gBondPerf1DayIntervalES | | aGroupPerfCurr1DayES | gBondPerf1DayIntervalES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfCurr1DaySES | gBondPerf1DayIntervalSES | | aGroupPerfCurr1DaySES | gBondPerf1DayIntervalSES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfCurr1DayUAS | gBondPerf1DayIntervalUAS | | aGroupPerfCurr1DayUAS | gBondPerf1DayIntervalUAS |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerfThreshold1DayES | gBondPerfThreshold1DayES | | aGroupPerfThreshold1DayES | gBondPerfThreshold1DayES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
skipping to change at page 16, line 4 skipping to change at page 15, line 46
| aGroupPerf1DayIntervalValid | gBondPerf1DayIntervalValid | | aGroupPerf1DayIntervalValid | gBondPerf1DayIntervalValid |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerf1DayIntervalMoniSecs | gBondPerf1DayIntervalMoniTime | | aGroupPerf1DayIntervalMoniSecs | gBondPerf1DayIntervalMoniTime |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerf1DayIntervalES | gBondPerf1DayIntervalES | | aGroupPerf1DayIntervalES | gBondPerf1DayIntervalES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerf1DayIntervalSES | gBondPerf1DayIntervalSES | | aGroupPerf1DayIntervalSES | gBondPerf1DayIntervalSES |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aGroupPerf1DayIntervalUAS | gBondPerf1DayIntervalUAS | | aGroupPerf1DayIntervalUAS | gBondPerf1DayIntervalUAS |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
+---------------------------------+---------------------------------+
| oLine - Basic Package | | | oLine - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineID | ifIndex (IF-MIB) | | aLineID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineType | ifType (IF-MIB) | | aLineType | ifType (IF-MIB) |
+---------------------------------+---------------------------------+
| aLineOperState | ifOperStatus (IF-MIB) | | aLineOperState | ifOperStatus (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) | | aLineStatus | *dsl*CurrStatus (*DSL-LINE-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineEnd | *dsl*Side (*DSL-LINE-MIB) | | aLineEnd | *dsl*Side (*DSL-LINE-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineAdminState | ifAdminStatus (IF-MIB) | | aLineAdminState | ifAdminStatus (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode | | aLineRemoteDiscoveryCode | gBondBceRemoteDiscoveryCode |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aLineUpDownEnable | _EdNote: Currently IF-MIB | | aLineUpDownEnable | _Note: Currently IF-MIB does |
| | doesn't provide a control for | | | not provide a control object |
| | the linkUp/linkDown | | | for the linkUp/linkDown |
| | notifications. Can we define a | | | notifications._ |
| | control in one MIB module while |
| | the notifications are in |
| | another?_ |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nLineUp | linkUp (IF-MIB) | | nLineUp | linkUp (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| nLineDown | linkDown (IF-MIB) | | nLineDown | linkDown (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oChannel - Basic Package | | | oChannel - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aChannelID | ifIndex (IF-MIB) | | aChannelID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
skipping to change at page 17, line 41 skipping to change at page 17, line 30
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 "201103140000Z" -- Mar 14, 2011 LAST-UPDATED "201105260000Z" -- May 26, 2011
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 19, line 20 skipping to change at page 19, line 10
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 (2011). Copyright (C) The IETF Trust (2011).
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 "201103140000Z" -- Mar 14, 2011 REVISION "201105260000Z" -- May 26, 2011
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 62, line 7 skipping to change at page 61, line 46
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.
8. IANA Considerations 8. IANA Considerations
Three new values of IANAifType: g9981, g9982 and g9982 SHALL be Three new values of IANAifType: g9981, g9982 and g9983 SHALL be
defined by the IANA [1] in the IANAifType-MIB module defined by the IANA [1] in the IANAifType-MIB module
[IANAifType-MIB], before this document is published as an RFC. [IANAifType-MIB], before this document is 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.
9. Acknowledgments 9. Acknowledgments
This document was produced by the [ADSLMIB] working group. This document was produced by the [ADSLMIB] working group.
skipping to change at page 64, line 31 skipping to change at page 64, line 21
[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., "ATM-based xDSL Bonded [I-D.ietf-adslmib-gbond-atm-mib] Beili, E., "ATM-based xDSL Bonded
Interfaces MIB", draft-ietf- Interfaces MIB", draft-ietf-
adslmib-gbond-atm-mib-03 (work in adslmib-gbond-atm-mib-04 (work in
progress), March 2011. progress), May 2011.
[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-03 (work in adslmib-gbond-eth-mib-04 (work in
progress), March 2011. progress), May 2011.
[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-05 (work in adslmib-gbond-tdim-mib-06 (work in
progress), March 2011. progress), May 2011.
[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",
 End of changes. 20 change blocks. 
37 lines changed or deleted 28 lines changed or added

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