headers
Romascanu, Dan (Dan | 8 Nov 2011 15:55
Favicon

AD review of draft-ietf-adslmib-gbond-eth-mib-04.txt

Hi,

Please find below the AD review of
draft-ietf-adslmib-gbond-eth-mib-04.txt.
This document is in a good shape, but a new version is needed in order
to clarify and fix some of the issues raised in the review. 

The comments below are marked T (Technical) and E (Editorial)

T1. Running smicng in strict mode results in one error and one warning: 

C:\bw\smicng\work>smicng gbond-eth.inc
E: f(gbond-eth.mi2), (260,15) Default value for "gBondEthAdminCp" must
be a name and not a number
W: f(gbond-eth.mi2), (1825,20) For "gBondEthTcTypesSupported", syntax is
identical

*** 1 error and 1 warning in parsing

T2. In section 5.2: 

   The agent SHOULD align the beginning of each interval to a fifteen
   minute boundary of a wall clock.  Likewise, the beginning of each one
   day intervals SHOULD be aligned with the start of a day.

Where does this requirement come from? If the source is another standard
I suggest to provide  it. What is the rationale? What happens if this
requirement is not / cannot be met because for example the agent does
not have access to a 'wall clock'?
(Continue reading)

Permalink | Reply | 4 comments |
headers
Romascanu, Dan (Dan | 8 Nov 2011 17:45
Favicon

AD review of draft-ietf-adslmib-gbond-atm-mib-04.txt

Hi,

Please find below the AD review of
draft-ietf-adslmib-gbond-atm-mib-04.txt.
This document is in a good shape, but a new version is needed in order
to clarify and fix some of the issues raised in the review. 

The comments below are marked T (Technical) and E (Editorial)

T1. In section 5.2: 

   The agent SHOULD align the beginning of each interval to a fifteen
   minute boundary of a wall clock.  Likewise, the beginning of each one
   day intervals SHOULD be aligned with the start of a day.

Where does this requirement come from? If the source is another standard
I suggest to provide  it. What is the rationale? What happens if this
requirement is not / cannot be met because for example the agent does
not have access to a 'wall clock'?

T2. The tables in this MIB module do not respect the naming convention
recommended in Annex C of RFC 4181: 

   - The descriptor associated with a conceptual table should be of the
     form xxxZzzTable; the descriptor associated with the corresponding
     conceptual row should be of the form xxxZzzEntry; the name of the
     associated SEQUENCE type should be of the form XxxZzzEntry; and the
     descriptors associated with the subordinate columnar objects should
     be of the form xxxZzzSomeotherName.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Romascanu, Dan (Dan | 9 Nov 2011 17:01
Favicon

AD review of draft-ietf-adslmib-gbond-tdim-mib-06.txt

Hi,

Please find below the AD review of
draft-ietf-adslmib-gbond-tdim-mib-06.txt.

This document is in a good shape, but a new version is needed in order
to clarify and fix some of the issues raised in the review. 

The comments below are marked T (Technical) and E (Editorial)

T1. smicng in relaxed checking reports one compilation error: 

C:\bw\smicng\work>smicng gbond-tdim.inc
E: f(gbond-tdim.mi2), (820,4) Row "gBondTdimServiceEntry" may not have
columns with MAX-ACC ESS of read-write if any column is read-create

*** 1 error and 0 warnings in parsing

T2. In section 5.4: 

   The agent SHOULD align the beginning of each interval to a fifteen
   minute boundary of a wall clock.  Likewise, the beginning of each one
   day intervals SHOULD be aligned with the start of a day.

Where does this requirement come from? If the source is another standard
I suggest to provide  it. What is the rationale? What happens if this
requirement is not / cannot be met because for example the agent does
not have access to a 'wall clock'?

T3. In the DESCRIPTION of the GBondTdimServiceIndex TC:
(Continue reading)

Permalink | Reply | 1 comment |

Gmane