draft-ietf-adslmib-gbond-mib-09.txt   draft-ietf-adslmib-gbond-mib-10.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 16, 2012 ECI Telecom Expires: September 13, 2012 ECI Telecom
Feb 13, 2012 Mar 12, 2012
xDSL multi-pair bonding (G.Bond) MIB xDSL multi-pair bonding (G.Bond) MIB
draft-ietf-adslmib-gbond-mib-09.txt draft-ietf-adslmib-gbond-mib-10.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 G9981-MIB, G9982-MIB and G9983-MIB
GBOND-TDIM-MIB respectively. respectively.
Status of This Memo Status of This Memo
This Internet-Draft is submitted 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). 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 August 16, 2012. This Internet-Draft will expire on September 13, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 19 skipping to change at page 2, line 19
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
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 . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . 12 4.3. Relationship to xDSL MIB modules . . . . . . . . . . . . . 12
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 . . . . . . . 13 5.3. Mapping of DSL Forum TR-159 Managed Objects . . . . . . . 13
6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17 6. xDSL Multi-pair Bonding MIB Definitions . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 62
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.1. Normative References . . . . . . . . . . . . . . . . . . . 64 10.1. Normative References . . . . . . . . . . . . . . . . . . . 64
10.2. Informative References . . . . . . . . . . . . . . . . . . 65 10.2. Informative References . . . . . . . . . . . . . . . . . . 66
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 4, line 8 skipping to change at page 4, line 8
an xDSL line. Bonding of multiple bearer channels in the same xDSL an xDSL line. Bonding of multiple bearer channels in the same xDSL
line is not allowed. line is not allowed.
All schemes allow bonding of up to 32 individual line/channel sub- All schemes allow bonding of up to 32 individual line/channel sub-
layers with variable rates, providing common functionality for the layers with variable rates, providing common functionality for the
configuration, initialization, operation and monitoring of the bonded configuration, initialization, operation and monitoring of the bonded
link. link.
This document defines a MIB module common to all 3 schemes. This document defines a MIB module common to all 3 schemes.
Additional managed objects, specific to each bonding technology, are Additional managed objects, specific to each bonding technology, are
defined in GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib], GBOND-ETH- defined in G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib], G9982-MIB
MIB [I-D.ietf-adslmib-gbond-eth-mib] and GBOND-TDIM-MIB [I-D.ietf-adslmib-gbond-eth-mib] and G9983-MIB
[I-D.ietf-adslmib-gbond-tdim-mib] modules. [I-D.ietf-adslmib-gbond-tdim-mib] modules.
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
skipping to change at page 4, line 45 skipping to change at page 4, line 45
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
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 (G9981-MIB), G.Bond/Ethernet (G9982-MIB)
ETH-MIB) and G.Bond/TDIM (GBOND-TDIM-MIB), and DSL specific MIB and G.Bond/TDIM (G9983-MIB), and DSL specific MIB modules: ADSL
modules: ADSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL (ADSL-LINE-EXT-MIB), ADSL2 (ADSL2-LINE-MIB), SHDSL (HDSL2-SHDSL-LINE-
(HDSL2-SHDSL-LINE-MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE- MIB), VDSL (VDSL-LINE-MIB) and VDSL2 (VDSL2-LINE-MIB).
MIB).
4.1. Relationship 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 stack management, i.e., actual connection of the sub-layers to
the top layer interface, is done via the ifStackTable, as defined in the top layer interface, is done via the ifStackTable, as defined in
the IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in
skipping to change at page 7, line 24 skipping to change at page 7, line 24
4.1.2. xDSL Bonding 4.1.2. xDSL Bonding
The G.998.x Bonding allows a number of BCEs to be aggregated onto a The G.998.x Bonding allows a number of BCEs to be aggregated onto a
single logical GBS port, by splitting the incoming traffic into single logical GBS port, by splitting the incoming traffic into
multiple streams, transmitting each stream over a specific BCE and multiple streams, transmitting each stream over a specific BCE and
combining the streams at the remote GBS port, preserving the original combining the streams at the remote GBS port, preserving the original
traffic order. traffic order.
The Ethernet frames MAY be fragmented before the transmission and The Ethernet frames MAY be fragmented before the transmission and
reassembled at the remote end to minimize transportation delay. reassembled at the remote end to minimize transportation delay. The
G.998.2 (G.Bond/Ethernet) ports with multiple BCEs MUST perform the
fragmentation and reassembly of the Ethernet frames. However for a
single-BCE G.998.2 ports this function MAY be omitted (a.k.a. bonding
bypass), to minimize fragmentation overhead and additional processing
delay as well as to be able to interoperate with non-G.998 DSL
equipment.
The Bonding is OPTIONAL, meaning that a device with a single BCE MAY The agent is REQUIRED to indicate all supported bonding schemes (ATM,
perform fragmentation and re-assembly if this function is supported Ethernet and TDIM), including OPTIONAL support for the bonding bypass
by the device. The agent is REQUIRED to indicate the Bonding in G.998.2 single-BCE ports.
capability for all types of G.Bond ports (ATM, Ethernet and TDIM).
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 (by setting the value of gBondPortConfAdminScheme
and gBondPortConfAdminScheme objects to any supported bonding scheme
other than 'none') effectively turns on fragmentation and re-assembly
function, even on a single-BCE port. function, 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 (G.hs) 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.
skipping to change at page 11, line 50 skipping to change at page 11, line 50
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1: G.Bond interpretation of IF-MIB objects Table 1: G.Bond interpretation of IF-MIB objects
4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules 4.2. Relationship to G.Bond ATM, ETH and TDIM MIB modules
The MIB module defined in this document is common to all three G.998 The MIB module defined in this document is common to all three G.998
bonding schemes. It MUST be used in conjunction with a bonding bonding schemes. It MUST be used in conjunction with a bonding
scheme-specific MIB module: scheme-specific MIB module:
o GBOND-ATM-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 o G9981-MIB [I-D.ietf-adslmib-gbond-atm-mib] for a G.998.1 bonded
bonded interface. interface.
o GBOND-ETH-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 o G9982-MIB [I-D.ietf-adslmib-gbond-eth-mib] for a G.998.2 bonded
bonded interface. interface.
o GBOND-TDIM-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 o G9983-MIB [I-D.ietf-adslmib-gbond-tdim-mib] for a G.998.3 bonded
bonded interface. interface.
4.3. Relationship to xDSL MIB modules 4.3. 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 [RFC5650] for VDSL2. [RFC3728] for VDSL or VDSL2-LINE-MIB [RFC5650] for VDSL2.
These MIB moduless are used to manage individual xDSL lines/channels These MIB moduless are used to manage individual xDSL lines/channels
(BCEs). (BCEs).
skipping to change at page 13, line 6 skipping to change at page 13, line 6
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.
The rationale behind it is to simplify collection and analysis of the The rationale behind it is to simplify collection and analysis of the
PM from multiple agents by a network management system (NMS) - each PM from multiple agents by a network management system (NMS) - each
PM interval can be "time-stamped" using the gBond*IntervalIndex PM interval can be "time-stamped" using the gBond*IntervalIndex
object, the fact that 1-day interval starts at 00:00 and 15-min object, the fact that 1-day interval starts at 00:00 and 15-min
intervals are aligned with 1/4 hour and the network-wide "wall intervals are aligned with 1/4 hour and the network-wide "wall
clock", typically distributed via NTP or SNTP. If the agent does not clock", typically distributed via NTP or SNTP [RFC5905]. If the
have an access to the wall clock, a local clock can be used. In this agent does not have an access to the wall clock, a local clock can be
case, as well as when coping with multiple time zones, the NMS would used. In this case, as well as when coping with multiple time zones,
have to correlate for the difference between the agent's local clock the NMS would have to correlate for the difference between the
(available for example via hrSystemDate object from HOST-RESOURCES- agent's local clock (available for example via hrSystemDate object
MIB [RFC2790]) and the wall clock. from HOST-RESOURCES-MIB [RFC2790]) and the wall clock.
Counters are not reset when a GBS is reinitialized, but rather only Counters are not reset when a GBS is reinitialized, but rather only
when the agent is reset or reinitialized. when the agent is reset or reinitialized.
Note that the accumulation of certain performance events for a Note that the accumulation of certain performance events for a
monitored entity is inhibited (counting stops) during periods of monitored entity is inhibited (counting stops) during periods of
service unavailability on that monitored entity. The DESCRIPTION service unavailability on that monitored entity. The DESCRIPTION
clause of performance monitoring counters in this MIB module clause of performance monitoring counters in this MIB module
specifies which of the counters are inhibited during periods of specifies which of the counters are inhibited during periods of
service unavailability. service unavailability.
skipping to change at page 18, line 20 skipping to change at page 18, line 20
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 "201202130000Z" -- Feb 13, 2012 LAST-UPDATED "201203120000Z" -- Mar 12, 2012
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 14 skipping to change at page 19, line 14
Phone: +972-3-926-6258 Phone: +972-3-926-6258
EMail: moti.morgenstern@ecitele.com" EMail: moti.morgenstern@ecitele.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, G9981-MIB, G9982-MIB or
GBOND-ETH-MIB or GBOND-TDIM-MIB. G9983-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.2: 'Ethernet-based multi-pair ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
bonding', January 2005. bonding', January 2005.
skipping to change at page 19, line 51 skipping to change at page 19, line 51
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 (2012). Copyright (C) The IETF Trust (2012).
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 "201202130000Z" -- Feb 13, 2012 REVISION "201203120000Z" -- Mar 12, 2012
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
skipping to change at page 20, line 34 skipping to change at page 20, line 34
-- Textual Conventions -- Textual Conventions
GBondSchemeList ::= TEXTUAL-CONVENTION GBondSchemeList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines a bitmap of possible ITU-T "This textual convention defines a bitmap of possible ITU-T
G.998 (G.Bond) bonding schemes. Currently there are 3 bonding G.998 (G.Bond) bonding schemes. Currently there are 3 bonding
schemes defined: G.998.1, G.998.2 and G.998.3, identified by schemes defined: G.998.1, G.998.2 and G.998.3, identified by
bit values g9981(1), g9982(2) and g9983(3), respectively. bit values g9981(1), g9982(2) and g9983(3), respectively.
An additional value of unknown(0), can be returned as a result An additional value of none(0), can be returned as a result
of GET operation, when an value of the object cannot be of GET operation, when an value of the object cannot be
determined, for example a peer GBS cannot be reached or it determined (for example a peer GBS cannot be reached), the port
does not support any kind of bonding." does not support any kind of bonding or when a single-BCE
G.998.2 GBS supports bonding (frame fragmentation/reassembly)
bypass."
SYNTAX BITS { SYNTAX BITS {
unknown(0), none(0),
g9981(1), g9981(1),
g9982(2), g9982(2),
g9983(3) g9983(3)
} }
GBondScheme ::= TEXTUAL-CONVENTION GBondScheme ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines ITU-T G.998 bonding scheme "This textual convention defines ITU-T G.998 bonding scheme
values. Possible values are: values. Possible values are:
unknown(0) - undefined or unknown
none(0) - no bonding (e.g. on single-BCE G.998.2 GBS) or
unknown
g9981(1) - G.998.1 (G.Bond/ATM) g9981(1) - G.998.1 (G.Bond/ATM)
g9982(2) - G.998.2 (G.Bond/Ethernet) g9982(2) - G.998.2 (G.Bond/Ethernet)
g9983(3) - G.998.3 (G.Bond/TDIM)." g9983(3) - G.998.3 (G.Bond/TDIM)."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), none(0),
g9981(1), g9981(1),
g9982(2), g9982(2),
g9983(3) g9983(3)
} }
GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION GBondPm1DayIntervalThreshold ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention defines a range of values that may be "This textual convention defines a range of values that may be
skipping to change at page 27, line 5 skipping to change at page 27, line 7
} }
gBondPortConfAdminScheme OBJECT-TYPE gBondPortConfAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired bonding scheme for a G.Bond GBS port. "A desired bonding scheme for a G.Bond GBS port.
The following values instruct the port to use corresponding The following values instruct the port to use corresponding
bonding scheme if supported: bonding scheme if supported:
none(0) - instructs the port not to use bonding
(only on single-BCE G.998.2 GBS)
g9981(1) - instructs the port to use G.998.1 bonding g9981(1) - instructs the port to use G.998.1 bonding
g9982(2) - instructs the port to use G.998.2 bonding g9982(2) - instructs the port to use G.998.2 bonding
g9983(3) - instructs the port to use G.998.3 bonding g9983(3) - instructs the port to use G.998.3 bonding
Changing of gBondPortConfAdminScheme MUST be performed when the Changing of gBondPortConfAdminScheme MUST be performed when the
link is administratively 'down', as indicated by the link is administratively 'down', as indicated by the
ifAdminStatus object in IF-MIB. ifAdminStatus object in IF-MIB.
Attempts to change this object MUST be rejected (in case of SNMP Attempts to change this object MUST be rejected (in case of SNMP
with the error inconsistentValue), if the link is Up or with the error inconsistentValue), if the link is Up or
Initializing. Attempts to change this object to an unsupported Initializing. Attempts to change this object to an unsupported
bonding scheme (see gBondPortCapSchemesSupported) SHALL be bonding scheme (see gBondPortCapSchemesSupported) SHALL be
rejected (in case of SNMP with the error wrongValue). rejected (in case of SNMP with the error wrongValue).
Setting this object to the value of 'none' must be rejected for
GBS ports with multiple BCEs (with the error inconsistentValue).
This object maps to the TR-159 attribute aGroupAdminBondScheme." This object maps to the TR-159 attribute aGroupAdminBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.6; IF-MIB, ifAdminStatus" "[TR-159] 5.5.1.6; IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 1 } ::= { gBondPortConfEntry 1 }
gBondPortConfPeerAdminScheme OBJECT-TYPE gBondPortConfPeerAdminScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A desired bonding scheme for a peer (link partner) G.Bond "A desired bonding scheme for a peer (link partner) G.Bond
port (GBS). port (GBS).
The following values instruct the peer port to use The following values instruct the peer port to use
corresponding bonding scheme if supported: corresponding bonding scheme if supported:
none(0) - instructs the port not to use bonding
(only on single-BCE G.998.2 GBS)
g9981(1) - instructs the port to use G.998.1 bonding g9981(1) - instructs the port to use G.998.1 bonding
g9982(2) - instructs the port to use G.998.2 bonding g9982(2) - instructs the port to use G.998.2 bonding
g9983(3) - instructs the port to use G.998.3 bonding g9983(3) - instructs the port to use G.998.3 bonding
Changing of this object MUST be performed when the link is Changing of this object MUST be performed when the link is
administratively 'down', as indicated by the ifAdminStatus administratively 'down', as indicated by the ifAdminStatus
object in IF-MIB. object in IF-MIB.
Attempts to change this object MUST be rejected (in case of SNMP Attempts to change this object MUST be rejected (in case of SNMP
with the error inconsistentValue), if the link is Up or with the error inconsistentValue), if the link is Up or
Initializing. Attempts to change this object to an unsupported Initializing. Attempts to change this object to an unsupported
bonding scheme (see gBondPortCapPeerSchemesSupported) SHALL be bonding scheme (see gBondPortCapPeerSchemesSupported) SHALL be
rejected (in case of SNMP with the error wrongValue). rejected (in case of SNMP with the error wrongValue).
Setting this object to the value of 'none' must be rejected for
GBS ports with multiple BCEs (with the error inconsistentValue).
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupPeerAdminBondScheme." aGroupPeerAdminBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.7; IF-MIB, ifAdminStatus" "[TR-159] 5.5.1.7; IF-MIB, ifAdminStatus"
::= { gBondPortConfEntry 2 } ::= { gBondPortConfEntry 2 }
gBondPortConfDiscoveryCode OBJECT-TYPE gBondPortConfDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(6)) SYNTAX PhysAddress (SIZE(6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 33, line 46 skipping to change at page 34, line 9
} }
gBondPortCapSchemesSupported OBJECT-TYPE gBondPortCapSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList SYNTAX GBondSchemeList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bonding Capability of the G.Bond port (GBS). This is a "Bonding Capability of the G.Bond port (GBS). This is a
read-only bitmap of the possible bonding schemes supported by read-only bitmap of the possible bonding schemes supported by
the GBS. The various bit-positions are: the GBS. The various bit-positions are:
none(0) - GBS is capable of bonding bypass on a
single-BCE (G.998.2 only)
g9981(1) - GBS is capable of G.998.1 bonding g9981(1) - GBS is capable of G.998.1 bonding
g9982(2) - GBS is capable of G.998.2 bonding g9982(2) - GBS is capable of G.998.2 bonding
g9983(3) - GBS is capable of G.998.3 bonding g9983(3) - GBS is capable of G.998.3 bonding
Note that for ports supporting multiple bonding schemes the Note that for ports supporting multiple bonding schemes the
actual administrative scheme is set via gBondPortConfAdminScheme actual administrative scheme is set via gBondPortConfAdminScheme
object. The current operating bonding scheme is reflected in object. The current operating bonding scheme is reflected in
the gBondPortStatOperScheme. the gBondPortStatOperScheme.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
skipping to change at page 34, line 21 skipping to change at page 34, line 34
::= { gBondPortCapEntry 1 } ::= { gBondPortCapEntry 1 }
gBondPortCapPeerSchemesSupported OBJECT-TYPE gBondPortCapPeerSchemesSupported OBJECT-TYPE
SYNTAX GBondSchemeList SYNTAX GBondSchemeList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Bonding Capability of the peer G.Bond port (GBS). This is a "Bonding Capability of the peer G.Bond port (GBS). This is a
read-only bitmap of the possible bonding schemes supported by read-only bitmap of the possible bonding schemes supported by
the link partner GBS. The various bit-positions are: the link partner GBS. The various bit-positions are:
unknown(0) - GBS does not support bonding or none(0) - peer GBS does not support bonding or
the peer unit could not be reached. the peer unit could not be reached or
g9981(1) - GBS is capable of G.998.1 bonding peer GBS is capable of bonding bypass on a
g9982(2) - GBS is capable of G.998.2 bonding single-BCE (G.998.2 only)
g9983(3) - GBS is capable of G.998.3 bonding g9981(1) - peer GBS is capable of G.998.1 bonding
g9982(2) - peer GBS is capable of G.998.2 bonding
g9983(3) - peer GBS is capable of G.998.3 bonding
Note that for ports supporting multiple bonding schemes the Note that for ports supporting multiple bonding schemes the
actual administrative scheme is set via actual administrative scheme is set via
gBondPortConfPeerAdminScheme object. The current operating gBondPortConfPeerAdminScheme object. The current operating
bonding scheme is reflected in the gBondPortStatPeerOperScheme. bonding scheme is reflected in the gBondPortStatPeerOperScheme.
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupBondPeerSchemesSupported." aGroupBondPeerSchemesSupported."
REFERENCE REFERENCE
"[TR-159] 5.5.1.3" "[TR-159] 5.5.1.3"
skipping to change at page 36, line 15 skipping to change at page 36, line 30
gBondPortStatNumBCEs Unsigned32 gBondPortStatNumBCEs Unsigned32
} }
gBondPortStatOperScheme OBJECT-TYPE gBondPortStatOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operating bonding scheme of a G.Bond port. "Current operating bonding scheme of a G.Bond port.
The possible values are: The possible values are:
none(0) - bonding bypass on a single-BCE (G.998.2 only)
g9981(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g9982(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g9983(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupOperBondScheme." aGroupOperBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.4" "[TR-159] 5.5.1.4"
::= { gBondPortStatEntry 1 } ::= { gBondPortStatEntry 1 }
gBondPortStatPeerOperScheme OBJECT-TYPE gBondPortStatPeerOperScheme OBJECT-TYPE
SYNTAX GBondScheme SYNTAX GBondScheme
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operating bonding scheme of a G.Bond port link partner. "Current operating bonding scheme of a G.Bond port link partner.
The possible values are: The possible values are:
unknown(0) - peer cannot be reached due to the link state unknown(0) - peer cannot be reached due to the link state or
bonding bypass on a single-BCE (G.998.2 only)
g9981(1) - G.998.1 bonding g9981(1) - G.998.1 bonding
g9982(2) - G.998.2 bonding g9982(2) - G.998.2 bonding
g9983(3) - G.998.3 bonding g9983(3) - G.998.3 bonding
This object maps to the TR-159 attribute This object maps to the TR-159 attribute
aGroupPeerOperBondScheme." aGroupPeerOperBondScheme."
REFERENCE REFERENCE
"[TR-159] 5.5.1.5" "[TR-159] 5.5.1.5"
::= { gBondPortStatEntry 2 } ::= { gBondPortStatEntry 2 }
skipping to change at page 57, line 32 skipping to change at page 57, line 49
-- Object Groups -- Object Groups
gBondBasicGroup OBJECT-GROUP gBondBasicGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondPortStatOperScheme, gBondPortStatOperScheme,
gBondPortStatUpDataRate, gBondPortStatUpDataRate,
gBondPortStatDnDataRate, gBondPortStatDnDataRate,
gBondPortConfTargetUpDataRate, gBondPortConfTargetUpDataRate,
gBondPortConfTargetDnDataRate, gBondPortConfTargetDnDataRate,
gBondPortCapSchemesSupported,
gBondPortCapCapacity, gBondPortCapCapacity,
gBondPortStatNumBCEs, gBondPortStatNumBCEs,
gBondPortStatSide, gBondPortStatSide,
gBondPortStatFltStatus gBondPortStatFltStatus
} }
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 {
gBondPortStatPeerOperScheme, gBondPortStatPeerOperScheme,
gBondPortCapPeerSchemesSupported,
gBondPortCapPeerCapacity, gBondPortCapPeerCapacity,
gBondPortConfDiscoveryCode, gBondPortConfDiscoveryCode,
gBondBceConfRemoteDiscoveryCode gBondBceConfRemoteDiscoveryCode
} }
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 gBondMultiSchemeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gBondPortCapSchemesSupported,
gBondPortCapPeerSchemesSupported,
gBondPortConfAdminScheme, gBondPortConfAdminScheme,
gBondPortConfPeerAdminScheme gBondPortConfPeerAdminScheme
} }
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 }
skipping to change at page 62, line 5 skipping to change at page 62, line 22
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting Performance Monitoring Threshold Crossing Alert supporting Performance Monitoring Threshold Crossing Alert
notifications." notifications."
GROUP gBondPmTcaNotificationGroup GROUP gBondPmTcaNotificationGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting Performance Monitoring Threshold Crossing Alert supporting Performance Monitoring Threshold Crossing Alert
notifications." notifications."
OBJECT gBondPortCapSchemesSupported
SYNTAX GBondSchemeList
DESCRIPTION
"Support for all bonding Schemes types is not required.
However at least one value SHALL be supported"
OBJECT gBondPortCapPeerSchemesSupported
SYNTAX GBondSchemeList
DESCRIPTION
"Support for all bonding Schemes types is not required.
However at least one value SHALL be supported"
::= { gBondCompliances 1 } ::= { gBondCompliances 1 }
END END
7. Security Considerations 7. Security Considerations
There is a number of managed objects defined in this MIB module with There is a number of managed objects defined in this MIB module with
a MAX-ACCESS clause of read-write and/or read-create. Such objects a MAX-ACCESS clause of read-write and/or read-create. Such objects
may be considered sensitive or vulnerable in some network may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
skipping to change at page 64, line 44 skipping to change at page 65, line 24
"The Interfaces Group MIB", "The Interfaces Group MIB",
RFC 2863, June 2000. RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and [RFC3411] Harrington, D., Presuhn, R., and
B. Wijnen, "An Architecture for B. Wijnen, "An Architecture for
Describing Simple Network Describing Simple Network
Management Protocol (SNMP) Management Protocol (SNMP)
Management Frameworks", STD 62, Management Frameworks", STD 62,
RFC 3411, December 2002. RFC 3411, December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen,
"User-based Security Model (USM)
for version 3 of the Simple
Network Management Protocol
(SNMPv3)", STD 62, RFC 3414,
December 2002.
[RFC3705] Ray, B. and R. Abbi, "High [RFC3705] Ray, B. and R. Abbi, "High
Capacity Textual Conventions for Capacity Textual Conventions for
MIB Modules Using Performance MIB Modules Using Performance
History Based on 15 Minute History Based on 15 Minute
Intervals", RFC 3705, Intervals", RFC 3705,
February 2004. February 2004.
[RFC3826] Blumenthal, U., Maino, F., and K.
McCloghrie, "The Advanced
Encryption Standard (AES) Cipher
Algorithm in the SNMP User-based
Security Model", RFC 3826,
June 2004.
[TR-159] Beili, E. and M. Morgenstern, [TR-159] Beili, E. and M. Morgenstern,
"Management Framework for xDSL "Management Framework for xDSL
Bonding", Broadband Forum Bonding", Broadband Forum
technical report TR-159, technical report TR-159,
December 2008. December 2008.
10.2. Informative References 10.2. Informative References
[802.3] IEEE, "IEEE Standard for [802.3] IEEE, "IEEE Standard for
Information technology - Information technology -
skipping to change at page 66, line 20 skipping to change at page 67, line 16
[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-05 (work in adslmib-gbond-atm-mib-06 (work in
progress), Feb 2012. progress), March 2012.
[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-05 (work in adslmib-gbond-eth-mib-06 (work in
progress), February 2012. progress), March 2012.
[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-07 (work in adslmib-gbond-tdim-mib-08 (work in
progress), Feb 2012. progress), March 2012.
[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>.
[RFC2790] Waldbusser, S. and P. Grillo, [RFC2790] Waldbusser, S. and P. Grillo,
"Host Resources MIB", RFC 2790, "Host Resources MIB", RFC 2790,
March 2000. March 2000.
skipping to change at page 67, line 7 skipping to change at page 68, line 5
the Interfaces Group MIB", the Interfaces Group MIB",
RFC 2864, June 2000. RFC 2864, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., [RFC3410] Case, J., Mundy, R., Partain, D.,
and B. Stewart, "Introduction and and B. Stewart, "Introduction and
Applicability Statements for Applicability Statements for
Internet-Standard Management Internet-Standard Management
Framework", RFC 3410, Framework", RFC 3410,
December 2002. December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen,
"User-based Security Model (USM)
for version 3 of the Simple
Network Management Protocol
(SNMPv3)", STD 62, RFC 3414,
December 2002.
[RFC3440] Ly, F. and G. Bathrick, [RFC3440] Ly, F. and G. Bathrick,
"Definitions of Extension Managed "Definitions of Extension Managed
Objects for Asymmetric Digital Objects for Asymmetric Digital
Subscriber Lines", RFC 3440, Subscriber Lines", RFC 3440,
December 2002. December 2002.
[RFC3593] Tesink, K., "Textual Conventions [RFC3593] Tesink, K., "Textual Conventions
for MIB Modules Using Performance for MIB Modules Using Performance
History Based on 15 Minute History Based on 15 Minute
Intervals", RFC 3593, Intervals", RFC 3593,
September 2003. September 2003.
[RFC3728] Ray, B. and R. Abbi, "Definitions [RFC3728] Ray, B. and R. Abbi, "Definitions
of Managed Objects for Very High of Managed Objects for Very High
Speed Digital Subscriber Lines Speed Digital Subscriber Lines
(VDSL)", RFC 3728, February 2004. (VDSL)", RFC 3728, February 2004.
[RFC3826] Blumenthal, U., Maino, F., and K.
McCloghrie, "The Advanced
Encryption Standard (AES) Cipher
Algorithm in the SNMP User-based
Security Model", RFC 3826,
June 2004.
[RFC4181] Heard, C., "Guidelines for Authors [RFC4181] Heard, C., "Guidelines for Authors
and Reviewers of MIB Documents", and Reviewers of MIB Documents",
BCP 111, RFC 4181, September 2005. BCP 111, RFC 4181, September 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, [RFC4319] Sikes, C., Ray, B., and R. Abbi,
"Definitions of Managed Objects "Definitions of Managed Objects
for High Bit-Rate DSL - 2nd for High Bit-Rate DSL - 2nd
generation (HDSL2) and Single-Pair generation (HDSL2) and Single-Pair
High-Speed Digital Subscriber Line High-Speed Digital Subscriber Line
(SHDSL) Lines", RFC 4319, (SHDSL) Lines", RFC 4319,
skipping to change at page 68, line 31 skipping to change at page 69, line 14
Network Management Protocol Network Management Protocol
(SNMP)", RFC 5592, June 2009. (SNMP)", RFC 5592, June 2009.
[RFC5650] Morgenstern, M., Baillie, S., and [RFC5650] Morgenstern, M., Baillie, S., and
U. Bonollo, "Definitions of U. Bonollo, "Definitions of
Managed Objects for Very High Managed Objects for Very High
Speed Digital Subscriber Line 2 Speed Digital Subscriber Line 2
(VDSL2)", RFC 5650, (VDSL2)", RFC 5650,
September 2009. September 2009.
[RFC5905] Mills, D., Martin, J., Burbank,
J., and W. Kasch, "Network Time
Protocol Version 4: Protocol and
Algorithms Specification",
RFC 5905, June 2010.
[RFC6353] Hardaker, W., "Transport Layer [RFC6353] Hardaker, W., "Transport Layer
Security (TLS) Transport Model for Security (TLS) Transport Model for
the Simple Network Management the Simple Network Management
Protocol (SNMP)", RFC 6353, Protocol (SNMP)", RFC 6353,
July 2011. July 2011.
[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,
 End of changes. 44 change blocks. 
73 lines changed or deleted 116 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/