RE: FW: I-D ACTION:draft-ietf-hubmib-rfc3636bis-05.txt

Mike/Dan,
I've noticed that smilint complains about some index elements in the MAU-MIB being accessible:

rfc3636bis.mib:173: [5] {index-element-accessible} warning: index element `rpMauGroupIndex' of row `rpMauEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:173: [5] {index-element-accessible} warning: index element `rpMauPortIndex' of row `rpMauEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:173: [5] {index-element-accessible} warning: index element `rpMauIndex' of row `rpMauEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:482: [5] {index-element-accessible} warning: index element `ifMauIfIndex' of row `ifMauEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:482: [5] {index-element-accessible} warning: index element `ifMauIndex' of row `ifMauEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:1253: [5] {index-element-accessible} warning: index element `broadMauIfIndex' of row `broadMauBasicEntry' should be not-accessible in SMIv2 MIB
rfc3636bis.mib:1253: [5] {index-element-accessible} warning: index element `broadMauIndex' of row `broadMauBasicEntry' should be not-accessible in SMIv2 MIB

Do you see a reason not to change the MAX-ACCESS clause for these index elements to 'not-accessible'?

Regards,
-E.

-----Original Message-----
From: C. M. Heard [mailto:[email protected]] 
Sent: Thursday, July 27, 2006 15:51
To: Romascanu, Dan (Dan)
Cc: Edward Beili
Subject: Re: FW: [Hubmib] I-D ACTION:draft-ietf-hubmib-rfc3636bis-05.txt 

On Thu, 27 Jul 2006, Romascanu, Dan (Dan) wrote:
> Can you please confirm that you are happy with this version and 
> whether you feel that the document can be submitted to the IESG?

Hello Dan,

Indeed, as far as I am concerned this document is ready to go.  It addresses all the issues I had with -03 and -04.

Mike