Hi,
Please find my comments attached. I have used the following documents as
reference during my review:
WT-129
G.997.1 (06/2006)
Regards
Naren
Comments on draft-ietf-adslmib-vdsl2-01
---------------------------------------
1) Organization of xdsl2ProfileLine group looks strange:
xdsl2LineConfTemplateTable has pointers to both line and channel
profile, so in my opinion it is best to keep this outside
xdsl2ProfileLine group.
Proposed structure:
xdsl2Profile
+
|
+--xdsl2ProfileTemplate
| +--xdsl2ProfileConfTemplateTable
|
+--xdsl2LineProfile
| +--xdsl2LineProfileTable
| |
| +--xdsl2LineProfSpecModeTable
|
+--xdsl2ChannelProfile
| +--xdsl2ChannelProfileTable
|
+--xdsl2AlarmConfProfile
| +--xdsl2AlarmConfProfileTable
|
2) xdsl2LConfTemplateTable:
a) RaRatios can be put under channel conf profile itself, any reason
why it is put separately?
3) xdsl2ChannelStatusTable : MIB objects for Actual INP and INP
reporting mode are not modelled.
4) Use consistent abbreviations (as described in RFC4181) - Change
xdsl2LineCnfgTemplate to xdsl2LineConfTemplate; similarly,
xdsl2LineAlarmCnfgTemplate to xdsl2LineAlarmConfTemplate;
5) This is regarding MIN INP for systems using 8.625kHz subcarrier
spacing. In the description of xdsl2ChConfProfMinProtectionXs mention
that for systems using 8.625kHz subcarrier, 1/2 symbol is not valid.
6) Per band Line Attenuation and Per band Signal attenuation are not
modelled.
7)Actual Down/Upstream Signal-To-Noise Ratio mode (sec. 7.5.1.15 and
7.5.1.18 of G.997.1) are not modelled
8) TR-129 (actually WT-129 now, but in letter ballot) can be included in
the reference section.
I know that references are to be re-visited, however, some pointers from
my side:
*) REFERENCE section for xdsl2ChConfProfMaxBerDs,
xdsl2ChConfProfMaxBerUs is not correct. The correct section in G.997.1
is paragraph 7.3.2.6.
*) In the DESCRIPTION section of xdsl2LineCnfgTemplate &
xdsl2LineAlarmCnfgTemplate, the reference to TR-129 is incorrect, there
is no 5.1.1 section in TR-129.
*) REFERENCE section for xdsl2LineStatusPwrMngState refers to 7.5.1.2 of
G.997.1, this is incorrect, the right section is 7.5.1.5
*) REFERENCE section for xdsl2SCStatusSigAtten is not correct. Sec.
7.5.1.9 of G.997.1 refers to per band line attenuation (LATNds)
*) REFERENCE section for xdsl2LineStatusLnAttenDs and
xdsl2LineStatusLnAttenUs are not correct.
Question: Line Attenuation and Signal Attenuation parameters are defined
in G.997 & TR-129 only on a per-band basis. I am of the opinion that
signal and line attenuation should be modelled at the live level too.
How do we handle this?
Minor / Cosmetic comments
-------------------------
In the description of xdsl2LInvSystemVendorId, change 'The ATU System
Vendor ID ...' to 'The XTU system Vendor ID ...'
Page 51, capitalize reference to standard in para 3 -> change '... per
[g.992.5] ...' to '... per [G.992.5] ...'
--
Narendranath Nair
Lead Architect, Network Management,
Wipro Technologies, Keonics Electronics City,
Bangalore - 560 100, India
Tel: +91-80-28520408 Ext. 85338
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.