Re: Pls check and comment: draft-ietf-mboned-msdp-mib-01.txt (Experim ental)

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Tue, Mar 21, 2006 at 05:12:47PM +0100, Wijnen, Bert (Bert) wrote:
> I am reviewing a Experimental draft
>    draft-ietf-mboned-msdp-mib-01.txt
> 
> I wonder if MIB doctors have comment on this doc and/or on
> my evaluation as per below.
> 
> Thanks,
> Bert
> 
> --------- draft evaluation by Bert:
> 
> I see:
> msdpSACacheEntry OBJECT-TYPE
>     SYNTAX     MsdpSACacheEntry
>     MAX-ACCESS not-accessible
>     STATUS     current
>     DESCRIPTION
>            "An entry (conceptual row) representing an MSDP SA
>             advertisement.  The INDEX to this table includes
>             msdpSACacheOriginRP for diagnosing incorrect MSDP
>             advertisements; normally a Group and Source pair would be
>             unique.
> 
>             Row creation is not permitted; msdpSACacheStatus may only be
>             used to delete rows from this table."
> 
> The way to express that last sentence is in the MODULE-COMPLIANCE
> with an entry aka:
> 
>         OBJECT     msdpSACacheStatus
>         SYNTAX     RowStatus { active(1), destroy(6) }
>         DESCRIPTION
>            "Row creation is not permitted; msdpSACacheStatus may only be
>             used to delete rows from this table."

If this conceptual row really cannot be created and always is active
and can only be destroyed, I think the proper thing is to change the
SYNTAX of msdpSACacheStatus:

  msdpSACacheStatus OBJECT-TYPE
      SYNTAX     RowStatus { active(1), destroy(6) }

If there is a chance that some fancy implementation might create such
a conceptual row via SNMP, then the proposed MODULE-COMPLIANCE seems
appropriate. My reading of the descriptions seem to suggest that the
authors do not believe this row ever being populated via SNMP.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany