2.4.1 ADSL MIB (adslmib)

NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01

Chair(s):

Michael Sneed <mike.sneed@go.ecitele.com>

Operations and Management Area Director(s):

Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>

Operations and Management Area Advisor:

Bert Wijnen <bwijnen@lucent.com>

Technical Advisor(s):

Kaj Tesink <kaj@research.telcordia.com>

Editor(s):

Faye Ly <faye@salira.com>
Greg Bathrick <greg.bathrick@nokia.com>

Mailing Lists:

General Discussion:XDSLMIB@LISTSERV.ECIRALEIGH.COM
To Subscribe: LISTSERV@LISTSERV.ECIRALEIGH.COM
In Body: subscribe/signoff XDSLMIB
Archive: index XDSLMIB/get <archivename>

Description of Working Group:

The working group will define a set of managed objects to be used for management of Very high speed Digital Subscriber Line (VDSL) services as defined by T1E1.4/2000-009R2. It is a goal, though not a requirement, that the resultant MIB be published as an extension to the ADSLMIB. The MIB 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 by the current ADSLMIB and HDSL2/SHDSL MIB, the interfaces MIB, and the AToM MIB.

The working group will consider the input of the DSL forum and the ITU in the definition of this MIB.

In addition, the group will continue to work on the promotion of the ADSLMIB, the ADSL Extension MIB, and the HDSL2/SHDSL MIB through the IETF standards process.

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

Mar 01

  

Submit initial Internet-Draft VDSL MIB

Apr 01

  

Submit Internet-Draft ADSL MIB based on implementations of RFC2662

May 01

  

Submit ADSL MIB to IESG for consideration as Draft Standard

Jun 01

  

Submit updated VDSL MIB Internet-Draft

Aug 01

  

Complete WG last call on VDSL MIB

Aug 01

  

Submit VDSL MIB to IESG for consideration as Proposed Standard

Internet-Drafts:
Request For Comments:

RFC

Status

Title

RFC2662

PS

Definitions of Managed Objects for the ADSL Lines

Current Meeting Report

Meeting Minutes for the ADSL MIB working group, 51st IETF
Wednesday 8 Aug 2001

1. Agenda bashing - by Mike Sneed
2. Document status - by Mike Sneed
- HDSL/SHDSL MIB passed WG last call and internet-draft standard ready
- ADSL 2 MIB passed WG last call but didn't made it to the internet-draft cut off day
- needs to publish the MIB object change
- needs to clarify the profile usage
- needs to publish the security consideration difference

3. VDSL MIB proposal - Bob Roy

3.1 What is the current status of the VDSL standard?

T1E1 standard and ANSI standard
- two standards are 90% compatible
- ANSI should be firmed up by the fall

3.2 Why do we need to consider VDSL MIB in this working group?

Similar to ADSL MIB

Draft-baillie-adslmib-vdsldmt-00.txt (current orphan draft)

What is the guideline for deciding to use 64 or 32 bit counters?
- anything above 20M
- anything may go beyond 20M
- wouldn't it be easier to use 64 bit counter across? Or simply day counter?

VDSL doesn't support RATE adaptation
VDSL requires 64 bit counters
VDSL is sufficiently different from ADSL to justify having it's own MIB

3.3 Conclusion and discussion

Need a separate VDSL MIB
Get the current draft to the list
May have to do a VDSL extension MIB in the future because ANSI/T1E1
Include DMT/CAP in the VDSL MIB (as different to RFC 2662)

4. Action items:

1. Mini WG last call on ADSL extension MIB.
2. Bob do a draft of VDSL MIB and get feedback on the list
3. Mike will submit a new schedule to Bert to update the ADSL Working Group charter

5. Close

Slides

A HREF="slides/adsl-1/index.html" TARGET="BLANK">ADSL to VDSL Management