RE: [ipcdn] pktcSigDevToneWholeToneRepeatCount description indraft-07 of the Signaling MIB

["Eugene Nechamkin" <enechamkin at broadcom.com>]

> |             If the pktcSigDevToneType is set to either of the values
> |             callWaiting1 or callWaiting4, then the value of the
> |             pktcSigDevToneWholeToneRepeatCount object has no
> |             effect on the tone."

Though this approach addresses one concern on how the value in this
object affects the tone generation functionality of the MTA, it does not
address the SNMP behavior of the MTA, and also does not provide for the
unamigous feedback to the NMS.

The following might address all of those:

             If the pktcSigDevToneType is set to any of the values
             callWaiting1, callWaiting2, callWaiting3 or callWaiting4,
             then the value of the pktcSigDevToneWholeToneRepeatCount
             object has no effect on the tone. In this case, the MTA 
             MUST return "noSuchInstance" for all SNMP SET operations, 
             and "noError" for all SNMP GET operations on
             pktcSigDevToneWholeToneRepeatCount object.

Eugene.

-----Original Message-----
From: ipcdn-bounces at ietf.org [mailto:ipcdn-bounces at ietf.org] On Behalf
Of David De Reu
Sent: Thursday, January 20, 2005 12:41 AM
To: ipcdn at ietf.org
Subject: RE: [ipcdn] pktcSigDevToneWholeToneRepeatCount description
indraft-07 of the Signaling MIB

Hi all,

> ...
> This can be messy to implement correctly, particularly when one 
> considers how getNext and getBulk work.  As an alternative, I'd
suggest:
> 
> |             If the pktcSigDevToneType is set to either of the values
> |             callWaiting1 or callWaiting4, then the value of the
> |             pktcSigDevToneWholeToneRepeatCount object has no
> |             effect on the tone."

Sounds like a good idea. Just one little thing: this applies to
callWaiting1-4, which includes ...2 and ...3. Being a little explicit
doesn't harm, so:

             If the pktcSigDevToneType is set to either of the values
             callWaiting1, callWaiting2, callWaiting3 or callWaiting4,
             then the value of the pktcSigDevToneWholeToneRepeatCount
             object has no effect on the tone.

>From an SNMP point of view, would this wording require that the MTA
has to store the value, without using it, or does this allow the MTA not
even to store a new value?


Regards,

David





_______________________________________________
IPCDN mailing list
IPCDN at ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn



_______________________________________________
IPCDN mailing list
IPCDN at ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn