GBOND-MIB

The objects in this MIB module are used to manage the multi-pair bonded xDSL Interfaces, defined in ITU-T recommendations G.998.1, G.998.2 and G.998.3. This MIB module MUST be used in conjunction with a bonding scheme specific MIB module, that is, G9981-MIB, G9982-MIB or G9983-MIB. The following references are used throughout this MIB module: [G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005. [G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005. [G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005. [TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008. Naming Conventions: BCE - Bonding Channel Entity BTU - Bonding Transmission Unit BTU-C - Bonding Transmission Unit, CO side BTU-R - Bonding Transmission Unit, Remote Terminal (CPE) side CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sublayer PM - Performance Monitoring SNR - Signal to Noise Ratio TCA - Threshold Crossing Alert Copyright (C) The IETF Trust (2012). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices.

MIB content (82 objects)

Informations

Organization
IETF ADSL MIB Working Group
Contact info
WG charter: http://www.ietf.org/html.charters/adslmib-charter.html Mailing Lists: General Discussion: adslmib@ietf.org To Subscribe: adslmib-request@ietf.org In Body: subscribe your_email_address Chair: Menachem Dodge Postal: ECI Telecom, Ltd. 30 Hasivim St., Petach-Tikva 4951169 Israel Phone: +972-3-926-8421 EMail: menachem.dodge@ecitele.com Editor: Edward Beili Postal: Actelis Networks, Inc. 25 Bazel St., P.O.B. 10173 Petach-Tikva 49103 Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com Editor: Moti Morgenstern Postal: ECI Telecom 30 Hasivim St. Petach-Tikva 4951169 Israel Phone: +972-3-926-6258 EMail: moti.morgenstern@ecitele.com

Revisions

2012-03-12 00:00
Initial version, published as RFC XXXX.