ADSL MIB (adslmib)Last Modified: 2011-12-09 Additional information is available at tools.ietf.org/wg/adslmib
Chair(s):Operations and Management Area Director(s):
Operations and Management Area Advisor:Editor(s):
Mailing Lists:General Discussion: adslmib@ietf.orgTo Subscribe: https://www.ietf.org/mailman/listinfo/adslmib Archive: http://www.ietf.org/mail-archive/web/adslmib/current/maillist.html Description of Working Group:The working group will define:1. A set of managed objects to handle the bonding of xDSL lines according to the ITU-T Recommendations G.998.1 (ATM), G.998.2 (Ethernet) and G.998.3 (TDIM). A common MIB module will be developed to handle the common objects and three specific MIB modules will be developed to handle the three separate layer-2 technologies. Use will be made of the ifStack and ifInvStack Tables defined in RFC 2863 and RFC 2864 respectively. Use will also be made of the ifCapStack and ifInvCapStack tables as defined in RFC 5066. The Broadband forum TR-159 will be used in the definition of these MIBs. 2. The working group will develop a set of managed objects as an optional extension to RFC 5650 that shall provide an alternative approach, known as the "Vector of Profiles", for the configuration of DSL lines. The Vector of Profiles MIB will be based on the Broadband Forum TR-165 document. The ITU-T G.997.1 will also be considered in the definition of this extension. The MIB modules defined by this group will be generated using SMIv2, will be consistent with the SNMP management framework, and will describe the relationship of the objects defined to existing MIBs such as those described in other work products of this Working Group, the interfaces MIB, the Ethernet MIB modules and the AToM MIB. Goals and Milestones:
Internet-Drafts:xDSL multi-pair bonding (G.Bond) MIB (151174 bytes)xDSL multi-pair bonding using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB (108227 bytes) ATM-Based xDSL Bonded Interfaces MIB (66808 bytes) Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB (104334 bytes) Request For Comments:Definitions of Managed Objects for the ADSL Lines (RFC 2662) (247122 bytes)Definitions of Managed Objects for HDSL2 and SHDSL Lines (RFC 3276) (122991 bytes) obsoleted by RFC 4319 Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines (RFC 3440) (76058 bytes) High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals (RFC 3705) (24158 bytes) Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL) (RFC 3728) (147232 bytes) Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding (RFC 4070) (48561 bytes) Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line Coding (RFC 4069) (35712 bytes) Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines (RFC 4319) (146995 bytes) obsoletes RFC 3276 Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2) (RFC 4706) (347648 bytes) Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2) (RFC 5650) (434687 bytes) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||