RE: RE: RE: IETF IPCDN Signaling MIB - Draft 3 - Last Cal lfor Comments [NEW ISSUE Caller ID Ranges]
Beacham Gordon-CGB005 <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <D5A7E45D575DD61180130002A5DB377C06528C3C@ca25exm01> |
After taking a quick look at 300 659, I note the lower bound for the T4 parameter for the pktcSigDevCIDFskAfterDTAS object is 45 ms not 50 ms. Clearly, there is nothing broken regarding the MIB definition for these objects. In fact, the change proposed for pktcSigDevCIDFskAfterDTAS would cause an MTA to be unable to meet lower bound for the 300 659 timing specification noted above. I recommend leaving the range for these objects as 0, as presently defined in the MIB and indicating that the object range meets or exceeds the ranges in the 300 659 specification. The later specification should be the definitive guide for any pass/fail test criteria. >New issues that we feel need to be accommodated in the draft-03. >Issue #6 - ranges for some values need to be changed >a) pktcSigDevCIDFskAfterRing - minimum should be 50 (not 0) >b) pktcSigDevCIDFskAfterDTAS - minimum should be 50 (not 0) >c) pktcSigDevCIDRingAfterFSK - minimum should be 50 (not 0) >d) pktcSigDevCIDDTASAfterLR - minimum should be 50 (not 0) >e) pktcSigDevVmwiDTASAfterLR - minimum should be 50 (not 0) Gordon Beacham Digital Core Gateways, BCS Motorola, Inc. 858-404-2335 [email protected]