draft-ietf-adslmib-adsl2-06.txt

Hello all,

I've just submitted the -06 version to the internet-drafts. It should
appear in the next few
days on the IETF draft site.

Most of the changes in this version result from Bert's comments and I
want to thank (again) Bert for his work on this document.
Here is the list of changes compared to -05 version:

1) Removed Bob Ray’s name from the co-chair and put Menachem’s name
instead.

2) Corrected a mistake in the description of
adsl2LineAlarmConfTemplateTable

3) In MODULE-IDENTITY of the TC and the MIB separated between the request
from IANA and the request addressed to the RFC editor.

4) In few locations where the ‘l3toL0’ state of PMSF is described it was
given
by mistake the value ‘1’. The value ‘0’ is based on G.997.1 paragraph
7.3.1.1.3.

5) Renumbered the possible vales of Adsl2PowerMngState TC to start with
‘1’.

6) Replaced the word ‘downstream’ with ‘upstream’ in Adsl2ScMaskUs

7) In adsl2LineCnfgTemplate corrected Adsl2ConfTemplatesTable to
adsl2LineConfTemplateTable.

8) In adsl2LineStatusLastStateDs/Us  removed part of the description which
already appears
in the Adsl2LastTransmittedState TC.

9) In Adsl2LastTransmittedState changed the term ‘counted’ to ‘numbered’.

10) In adsl2LineStatusAtuc and  adsl2LineStatusAtur  removed the list of
values
 which already appears in the TC.

11) In the following objects the syntax was changed in order to reflect the
valid range of measured
values for the object as well as special values that may indicate a
measurement is out-of-range
or unavailable. The indication of ‘all ones’ is no longer used, as it is
sometimes falls inside
the range of ‘normal values’:
-     adsl2LineStatusLnAttenDs
-     adsl2LineStatusLnAttenUs
-     adsl2LineStatusSigAttenDs
-     adsl2LineStatusSigAttenUs
-     adsl2LineStatusSnrMarginDs
-     adsl2LineStatusSnrMarginUs
-     adsl2LineStatusActPsdDs
-     adsl2LineStatusActPsdUs
-     adsl2LineStatusActAtpDs
-     adsl2LineStatusActAtpUs
-     adsl2SCStatusLnAtten
-     adsl2SCStatusSigAtten
-     adsl2SCStatusSnrMargin

12) In the following configuration objects the syntax was changed in order
to reflect the valid range
 of values for the object as well as a special value that indicates ‘no
limit’
-     adsl2LConfProfMaxSnrmDs
-     adsl2LConfProfMaxSnrmUs
-     adsl2LConfProfMaxAggRxPwrUs

13) In adsl2ChStatusAtmStatus  and adsl2ChStatusPtmStatus replaced
‘NoFailure’ with ‘NoDefect’.

14) In adsl2LineStatusInitResult changed ‘NoFailure’ to ‘NoFail’.

15) In few objects replaced the term ‘byte’ with ‘octet’
-     adsl2SCStatusSnr
-     adsl2SCStatusBitsAlloc

16) The adsl2LInvG994VendorId  and adsl2LInvSystemVendorId  have constant
size of 8 octets.
Other objects in the same table (e.g., adsl2LInvVersionNumber and
adsl2LInvSerialNumber ) have
 variable size and may even report an empty string because they contain
vendor specific information.

17) Changed the syntax of adsl2LInvSelfTestResult to Unsigned32. Also
performed a slight change
 in the description.

18) Changed the occurrences of  ‘rainit’ to ‘raInit’ in Adsl2RaMode TC.

19) Changed the occurrences of  ‘DynamicRa’ to ‘dynamicRa‘ in
-     adsl2LConfProfRaUsNrmDs
-     adsl2LConfProfRaUsNrmUs
-     adsl2LConfProfRaUsTimeDs
-     adsl2LConfProfRaUsTimeUs
-     adsl2LConfProfRaDsNrmDs
-     adsl2LconfProfRaDsNrmUs
-     adsl2LConfProfRaDsTimeDs
-     adsl2LConfProfRaDsTimeUs
-     adsl2ChConfProfMinResDataRateDs
-     adsl2ChConfProfMinResDataRateUs

20) As Bert suggested, the read-only tables (i.e., mainly status and PM
tables) will not include
an explicit reference to the (non) persistence behavior of the objects they
contain. This change
 affects the line status, channel status and inventory tables as well as
the line PM and channel PM tables.

21) Replaced '&' with '&amp' in MODULE-IDENTITY sections of ADSL2-LINE-MIB
and ADSL2-LINE-TC-MIB.

22) Replaced '&' with '&amp' in Normative References section.

23) Changed MAX-ACCESS of adsl2SCStatusRowStatus to read-create.

24) Changed the description of adsl2SCStatusRowStatus.

25) Updated the description of adsl2SCStatusTable.

***************************************************************************************************************************
One comment that Bert issued was not accepted.
The PM history, according to the current design, includes also invalid
intervals marked as invalid.
The editors explained (to Bert) that even partial intervals can include
useful information for the
operator, especially when we added a managed object that provides tells the
actual duration
of the monitoring interval
***************************************************************************************************************************


Best Regards,
Moti Morgenstern

_______________________________________________
Adslmib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/adslmib