ADSL-MIB WG MEETING

68th IETF Meeting

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

Work Overview

• 2006 • Adsl2 completed.• Re-chartered for Vdsl2.• Re-chartered again for xDSL Bonding.

• 2007 • Complete Vdsl2.• Complete xDSL Bonding.• Re-Charter or Close Down.

Major Achievements 2006-2007

• Adsl2 MIB• February 2006 – August Adsl2 MIB reviews,

corrections and last calls.• November 2006 – RFC 4706.

• Vdsl2 MIB• January 2006 - Re-Charter Vdsl2 MIB.• June – August 2006 – Version 01.• October 2006 – Review.• February 2007 – Version 02

Major Achievements 2006-2007

• G.Bond MIBs• July 2006 Raised on the WG• August – September – Discussions (HubMib).• October 2006 – Re-Charter Approval• February 2006 – Initial Version of the

Common MIB. ATM, ETH and TDIM shortly.

• SHDSL• Errata on RFC 4319.

Relationships to Other Bodies

• DSL Forum– The DSL Forum provides the guidelines for

the work done by our WG.– Many Liaisons between the groups.– Shared editors.

• ITU-T– Liaisons sent to inform the ITU-T of our on-

going work.

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

VDSL2 Line MIB Status

ADSLMIB WGIETF 68 – Prague

March 19-23, 2007

draft-adslmib-vdsl2-02.txt

Introduction• The VDSL2 Line MIB work started last year • Preceding line MIBs:

– RFC 2662 - ADSL– RFC 3276 - SHDSL (obs.)– RFC 3440 - ADSL Line MIB Extension– RFC 3705 - Textual Conventions– RFC 3728 - VDSL– RFC 4069, 4070 – SCM/MCM Extensions (respectively)– RFC 4319 - SHDSL 2nd generation– RFC 4706 - ADSL2

• The VDSL2 Line MIB Is considered the Next Generation MIB.– Covers ADSL and ADSL2 as well as VDSL2

Introduction (cont.)

• Editors – Moti Morgenstern, ECI Telecom Ltd.– Scott Baillie, NEC Australia– Umberto Bonollo, NEC Australia

References

• The VDSL2 Line MIB follows – IETF RFC 4706– ITU-T G.997.1– DSL Forum TR-129

• The requirements are not final– G.997.1 revision 3 was published 6/2006– Proposed changes and an amendment since

then

Revisions so far

• 1st draft (-00) published 1/2006 – Basically demonstrated the framework

• 2nd draft (-01) published 8/2006– Added objects to comply with ITU-T G.997.1– Introduced methods to deal with the high

number of sub-carriers.

• 3rd draft (-02) published 2/2007– Many changes

What is in revision -02?

• 3rd draft (-02) published 2/2007– New textual conventions: Xdsl2Band– New tables for line/signal attenuation and SNR margin measurements:

• xdsl2LineBandTable and xdsl2SCStatusBandTable.

– Sub-Carrier status• xDsl2SCStatusMainTable reverts to (RFC 4706 name):

xDsl2SCStatusTable. • Previously called xDsl2SCStatusTable renamed to

xDsl2SCStatusSegmentTable

– Section 2.9, replaced:• xdsl2LStatusStatusXtur with xdsl2LineStatusXtur and• adsl2LStatusStatusXtuc with xdsl2LineStatusXtuc

– Corrections:• xdsl2SCStatusSnrMargin – ‘XATU-C’ is now ‘XTU-C’

– Implemented most UPBO, DPBO, and RFIBANDS related attributes• Added two Textual Conventions for D/UPBO

What is in revision -02? (cont.)

• 3rd draft (-02) also includes– Changes based on Clay Sikes' 66 comments from

14/10/06:– Among changes

• Corrected wrong text in various positions• ‘vdsl2 7’ replaces ‘vdsl2 8’ in the OBJECT IDENTIFIERs part • Added an explanation in naming convention and in

1st object that mentions PTM and NS • Changed few performance monitoring object names to better

indicate that they are for 15-minutes interval

– The editors agreed with most of the comments. But• Disagreed on adding "running counters“• Disagreed on the use of IMPLIED for profile names• A few comments are pending and will be added in a more

mature revision.

What next?

• Add Attributes (references from ITU-T G.997.1) – Line status

• 7.5.1.2 VDSL2 profile in use

• 7.5.1.3 VDSL2 Limit PSD mask and band plan in use

• 7.5.1.4 VDSL2 US0 PSD mask in use

• 7.5.1.23 Estimated upstream power back-off electrical length (UPBOKLE)

• 7.5.1.30 TRELLISds

• 7.5.1.31 TRELLISus

What next? (cont.)

• Add Attributes (references from ITU-T G.997.1) – Channel Actual Setup

• 7.5.2.4 Actual Impulse Noise Protection (ACTINP)• 7.5.2.5 Impulse Noise Protection reporting Mode

(INPREPORT)• 7.5.2.6.1 Actual Size of Reed-Solomon Codeword (NFEC)• 7.5.2.6.2 Actual Number of Reed-Solomon redundancy Bytes

(RFEC)• 7.5.2.6.3 Actual Number of Bits Per Symbol (LSYMB)• 7.5.2.6.4 Actual Interleaving Depth (INTLVDEPTH)• 7.5.2.6.5 Actual Interleaving Block Length (INTLVBLOCK)• 7.5.2.6.6 Actual Size of Reed-Solomon Codeword (NFEC)• 7.5.2.6.7 Actual Latency Path (LPATH)

• Add Attributes (from ITU-T G.997.1 amendment 1) – Channel Setup

• Maximum delay variation (DVMAX)• Channel Initialization Policy selection (CIPOLICY)

What next? (cont.)

• Editorial Corrections– Correct references

• Attributes inserted into ITU-T G.997.1• Mistakes

– Broken lines– Leftovers– Editor comments

• Acknowledgements– Clay Sikes - Paradyne– John Boyle – Alcatel– Uwe Pauluhn - Infineon

Thank You

moti.morgenstern@ecitele.com

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

GBOND-MIB draft-ietf-adslmib-gbond-mib-00

Edward BeiliActelis Networks

68th IETF – Prague, Czech Republic

20 Mar 2007

Overview

•ITU-T G.998 - xDSL Bonding (G.Bond)–G.988.1 – ATM-based xDSL bonding (IMA+)–G.988.2 – Ethernet-based xDSL bonding

(EFM)–G.988.3 – xDSL bonding using TDIM

•DSL Forum WT-159 – xDSL Bonding Management framework

IETF ADSLMIB Docs Partition

•draft-ietf-adslmib-gbond-mib–Overview, common G.998.x objects, stacking –GBOND-MIB

•draft-ietf-adslmib-gbond-atm-mib–GBOND-ATM-MIB

•draft-ietf-adslmib-gbond-eth-mib–GBOND-ETH-MIB

•draft-ietf-adslmib-gbond-tdim-mib–GBOND-TDIM-MIB

GBOND-MIB: Layering model

BCE – Bonding Channel EntityGBS - Generic Bonded Sub-layer

PMD - Physical Medium DependentTPS-TC - Transport Protocol Specific - Transmission Convergence

PMS-TC - Physical Media Specific - Transmission Convergence

TPS-TCPMS-TC

PMD

GBS

BCE1 BCEN…

ifEntry ifType: g9981, g9982, g9983

ifEntry (N=1..32) ifType: adsl, shdsl, vdsl, etc.

GBOND-MIB: Interface Stacking

•ifStackTable / ifInvStackTable (RW) – actual connectivity of GBS x and BCE y

–ifStackStatus.x.y=active

•ifCapStackTable / ifInvCapStackTable (RO) – potential connectivity of GBS x and

BCE y –ifCapStackStatus.x.y=true

GBOND-MIB: Structure

GBOND-MIB: gBondPortConfTable

•gBondPortConfEntry–gBondDiscoveryCode–gBondTargetUpDataRate–gBondTargetDownDataRate–gBondThreshLowUpDataRate–gBondThreshLowDownDataRate–gBondLowRateCrossingEnable

GBOND-MIB: gBondPortCapabilityTable

•gBondPortCapabilityEntry–gBondPeerBond–gBondCapacity–gBondPeerCapacity

GBOND-MIB: gBondPortStatusTable

•gBondPortStatusEntry–gBondUpDataRate–gBondFltStatus–gBondPortSide–gBondNumBCEs

GBOND-MIB: gBondPortNotifications

•gBondLowUpRateCrossing

•gBondLowDownRateCrossing

Relationship to EFM-CU-MIB

•EFM-CU-MIB: manages all parameters, bonding and Phys. Line related for

2BASE-TL (shdsl-based) and 10PASS-TS (vdsl)

•GBOND-MIB/GBOND-*-MIB: xDSL Line/Channel parameters are managed via

respective xDSL LINE-MIBs

GBOND-TDIM-MIB: Structure

GBOND-TDIM-MIB: gBondTdimPortConfTable

•gBondTdimPortConfEntry–gBondTdimFecAdminState–gBondTdimFecWordSize–gBondTdimFecRedundancySize–gBondTdimFecInterleaverType–gBondTdimFecInterleaverDepth–gBondTdimServiceUpDownEnable

GBOND-TDIM-MIB: gBondTdimPortCapabilityTable

•gBondTdimPortCapabilityEntry–gBondTdimFecMaxWordSize–gBondTdimFecMaxRedundancySize–gBondTdimFecInterleaverTypeSupported–gBondTdimFecMaxInterleaverDepth

GBOND-TDIM-MIB: gBondTdimPortStatusTable

•gBondTdimPortStatusEntry–gBondTdimCrc4Errors–gBondTdimCrc6Errors–gBondTdimCrc8Errors–gBondTdimFltStatus

GBOND-TDIM-MIB: gBondTdimPortNotifications

•gBondTdimServiceUp

•gBondTdimServiceDown

GBOND-TDIM-MIB: gBondTdimServiceTable

•gBondTdimServiceEntry–gBondTdimServiceIndex–gBondTdimServiceType–gBondTdimServiceSize–gBondTdimServiceOperState

GBOND-ATM MIB Status

ADSLMIB WGIETF 68 – Prague

March 19-23, 2007

draft-adslmib-gbond-atm-00.txt

Introduction

•It was decided to define SNMP MIBs for xDSL Bonding last year

•Work was split into 4 drafts:–Common MIB–GBOND-ATM-MIB–GBOND-ETH-MIB–GBOND-TDIM-MIB

•Editors:–Edward Beili–Moti Morgenstern–Narendranath Nair

Overview

•ITU-T G.998 - xDSL Bonding (G.Bond)–G.988.1 – ATM-based xDSL bonding (IMA+)

•DSL Forum WT-159 – xDSL Bonding Management framework

•IETF GBOND-MIB

GBOND-MIB: Structure

GBOND-MIB: gBondPortConfTable

•gBondAtmPortConfEntry–gBondAtmDiffDelayTolerance –gBondAtmDiffDelayToleranceExceededEnabl

e

GBOND-ATM-MIB: gBondAtmPortStatusTable

•gBondAtmStatusEntry

•gBondAtmInLostCells

•gBondAtmFailureReason

•gBondAtmFailureCount

GBOND-MIB: gBondAtmPortNotifications

•gBondAtmDiffDelayToleranceExceeded

Open Issues

•Do we include line parameters in the GBOND-MIB(s)?

•Do we model performance counters viz. 15mins and 24hrs perf counters?

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

G.Bond Informational Document

• As there is some sharing of modules between the ADSLMIB and HUBMIB WGs is there a need for a shared applicability draft explaining how to use the MIBs?

• Is there a need for a G.Bond Ethernet MIB or can the EFM Cu-MIB be used?

Edward Beili’s Response

1. There's no need for a separate document describing MIB usage for bonded copper - GBOND-MIB document is a perfect place for such info.

2. We cannot use the bonding management from EFM-CU-MIB instead of GBOND-ETH-MIB - the EFM-CU-MIB uses different terms and refers to a subset of management objects, talks only about 2BASE-TL and 10-PASS-TS, does not support performance monitoring (if we decide to add them) etc. 

Meeting Agenda

• General Remarks (Chair) 10 minutes.• Vdsl2 MIB (Moti Morgenstern). 30 minutes.• Vdsl2 MIB Discussion. 10 minutes.• G. Bond MIB (Naren). 60 Minutes.• G. Bond MIB Discussion. 15 Minutes.• G. Bond Informational Document. 15 Minutes.• Concluding Remarks (Chair) 10 minutes.

Work Plan for 2007

• Vdsl2• March – April: Work on Version 03• May – June: Thorough Working Group Reviews.• July: Working Group Last Call.• August: MIB Doctor Reviews.• September: Corrections• October: Working Group Last Call• November: Present the document to the IESG.

Work Plan for 2007

• G. Bond • April – Complete all Initial Documents• May – July: Work on all documents.• August – Working Group Last Call.• September – MIB Doctor Reviews.• October – Corrections• November – Working Group Last Call • December - Present the document to the IESG.

• Recharter or ShutDown