Subject: [ipcdn] Additional AD review: draft-ietf-ipcdn-bpiplus-mib-13.txt

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Tue, 27 Jul 2004 12:31:57 +0200

Some quick notes, Here we go:

1. SMICng tells me:
    W: f(ipcdnbpi2.mi2), (3142,17) Duplicate item "docsBpi2CmtsIpMulticastAddressType"
       in compliances list for module "DOCS-IETF-BPI2-MIB"
    W: f(ipcdnbpi2.mi2), (3152,17) Duplicate item "docsBpi2CmtsIpMulticastAddress"
       in compliances list for module "DOCS-IETF-BPI2-MIB"
   Seems you duplicated something.

2.      docsBpi2CmtsIpMulticastMapControl  OBJECT-TYPE
           SYNTAX         RowStatus
           MAX-ACCESS     read-create
           STATUS         current
           DESCRIPTION
                "This object controls and reflects the IP multicast
           address mapping entry.  There is no restriction on the
           ability to change values in this row while the row is
           active.  Inactive rows need not
           A created row can be timed out." set to active only after the
           Corresponding instances of docsBpi2CmtsIpMulticastAddress,
           docsBpi2CmtsIpMulticastMask, docsBpi2CmtsIpMulticastSAId
           and docsBpi2CmtsIpMulticastSAType have all been set,
           otherwise the status of this object is 'notReady'.

           There is no restriction on the ability to change values in
           this row while the row is active."
           ::= { docsBpi2CmtsIpMulticastMapEntry 14 }

    Last sentence in DESCRIPTION clause is duplicate of 2nd sentence.
    Are you sure value is 'notReady' in that case? Could be notInService
    too, no? Why specify it. I.e. I would remove
           otherwise the status of this object is 'notReady'

3.      docsBpi2CmtsIpMulticastMapStorageType     OBJECT-TYPE
           SYNTAX         StorageType
           MAX-ACCESS     read-only
           STATUS         current
           DESCRIPTION
                "The storage type for this conceptual row."

   You must (according to RFC 2579) add txt to stat which (if any) writable
   objects MUST be writeable even for permanent entries. See 2579 fo details.

_______________________________________________
IPCDN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ipcdn