ADSL MIB (adslmib)

Last Modified: 2007-08-29

Additional information is available at tools.ietf.org/wg/adslmib

Chair(s):

  • Michael Sneed <sneedmike@hotmail.com>

  • Menachem Dodge <Menachem.Dodge@ecitele.com>

    Operations and Management Area Director(s):

  • Dan Romascanu <dromasca@avaya.com>
  • Ronald Bonica <rbonica@juniper.net>

    Operations and Management Area Advisor:

  • Dan Romascanu <dromasca@avaya.com>

    Technical Advisor(s):

  • Randy Presuhn <randy_presuhn@mindspring.com>

    Editor(s):

  • Faye Ly <fayely@juniper.net>
  • Greg Bathrick <Greg_Bathrick@pmc-sierra.com>
  • Bob Ray <rray@pesa.com>
  • Rajesh Abbi <Rajesh.Abbi@alcatel.com>
  • Scott Baillie <scott.baillie@nec.com.au>
  • Menachem Dodge <Menachem.Dodge@ecitele.com>
  • Clay Sikes <csikes@zhone.com>
  • Moti Morgenstern <moti.Morgenstern@ecitele.com>
  • Umberto Bonollo <umberto.bonollo@nec.com.au>

    Mailing Lists:

    General Discussion: adslmib@ietf.org
    To Subscribe: https://www1.ietf.org/mailman/listinfo/adslmib
    Archive: http://www.ietf.org/mail-archive/web/adslmib/index.html

    Description of Working Group:

    The working group will define:
    1.  A set of managed objects to be used for management of newer
    versions of Digital Subscriber Line (xDSL) as defined in ITU-T
    Recommendation G.997.1 (02/2006).

    2. 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 ifAvailableStack
    and ifInvAvailableStack tables as defined by the Hubmib WG.

    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.

    The working group will consider the input of the DSL forum and the ITU
    in the definition of these MIBs.

    Goals and Milestones:

    Done  Submit Internet-Draft to cover subscriber equipment
    Done  Meet at Chicago IETF to review Internet-Drafts
    Done  Submit Internet-Draft to IESG for consideration as Proposed Standard.
    Done  Meet at Oslo IETF to review new Internet-Drafts and discuss implementation experience on initial MIB
    Done  Submit supplementary Internet-Draft to IESG for consideration as Proposed Standard.
    Done  Produce Internet-Draft covering HDSL2 management objects.
    Done  Submit updated HDSL2/SHDSL Internet-Draft
    Done  Complete WG last call for HDSL2/SHDSL management objects
    Done  Collect implementation reports for ADSL MIB
    Done  Submit HDSL2/SHDSL MIB to IESG for consideration as Proposed Standard
    Done  Submit initial Internet-Draft VDSL MIB
    Done  Complete WG last call on VDSL MIB
    Done  Submit updated VDSL MIB Internet-Draft
    Done  Submit final VDSL MIB Internet-Draft
    Done  Submit VDSL MIB to IESG for consideration as Proposed Standard
    Done  New WG I-Ds for the LCS MCM and SCM MIB modules
    Done  Initial WG Internet-Draft covering ADSL2 management objects
    Done  Integrate working group changes and produce revised draft
    Done  Complete WG last call on ADSL2 MIB
    Done  Submit ADSL2 MIB to IESG for consideration as Proposed Standard
    Done  Re-charter or close down
    Done  Initial WG Internet-Draft covering VDSL2 management objects
    Done  Inform the ITU-T and DSL Forum that work on the VDSL2 MIB has begun
    Done  Integrate working group changes and produce revised VDSL2 MIB draft
    Done  Post Initial Drafts of all the xDsl Bonding MIB drafts
    Aug 2007  Post Vdsl2 draft version 03
    Aug 2007  Update the four G.Bond documents
    Sep 2007  Post Vdsl2 draft version 04
    Oct 2007  Complete Thorough Working Group Reviews of the Vdsl2draft and produce version 05
    Oct 2007  Complete the work on all the four G.Bond documents
    Nov 2007  Working Group Last Call on all the G. Bond documents
    Dec 2007  Request an early MIB Doctor Review of all G.Bond documents
    Dec 2007  Working Group Last Call for the Vdsl2 document
    Jan 2008  Request an early MIB Doctor Reviews of the Vdsl2 draft
    Jan 2008  Make Corrections to the G.Bond drafts following the review
    Feb 2008  Make Correction to the draft following the review
    Feb 2008  Working Group Last Call for G.Bond documents following corrections
    Mar 2008  Present the four G. Bond documents to the IESG
    Mar 2008  Working Group Last Call for the Vdsl2 document following corrections
    Apr 2008  Present the Vdsl2 document to the IESG

    Internet-Drafts:

    xDSL multi-pair bonding using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIB (57504 bytes)
    ATM-Based xDSL Bonded Interfaces MIB (35424 bytes)
    Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB (45175 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 Single Carrier Modulation (SCM) Line Coding (RFC 4069) (35712 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 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)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.