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