RE: comments on draft-ietf-ipcdn-pktc-signaling-05.txt (part 4)
"Jean-Francois Mule" <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <[email protected]> |
Some opinions inline. Jean-François Randy wrote: > -----Original Message----- > From: Randy Presuhn [mailto:[email protected]] > Sent: Tuesday, August 03, 2004 2:59 PM > To: [email protected] > Subject: [ipcdn] comments on > draft-ietf-ipcdn-pktc-signaling-05.txt (part 4) > > > Hi - > > More comments on draft-ietf-ipcdn-pktc-signaling-05.txt > based on draft-ietf-ops-mib-review-guidelines-03.txt > > 14) pktcSigDevCodecComboIndex: where does the range > constraint (1..255) come from? There's nothing in the > document to justify that particular upper bound. There is a hardware implication on how many number of vo-codecs an MTA should be capable of supporting. In the packetcable codec spec, we provide some guidance but we think that 255 is much more than what we need (beyond that, the cost of memory on the MTA is most likely going to outweight the benefits). > 16) pktcSigDev*Cadence: wouldn't it be simpler to put these > ten objects into a table? just a thought.... What if we only need one row? > 18) pktcSignalingIndex: where does the range constraint > (1..255) come from? There's nothing in the document to > justify that particular upper bound. It is a reasonable limit.