re: Re: IETF IPCDN Signaling MIB - Draft 3 - Last Call fo r Comments
Beacham Gordon-CGB005 <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <D5A7E45D575DD61180130002A5DB377C06528B90@ca25exm01> |
Regarding statements (3) and (5): Perhaps it would be better to eliminate the regional terms (i.e., North America), and instead use the term L package to refer to the core functionality (as defined by CableLabs/PacketCable) and E package to refer to extensions over and above the core package (defined in support of international requirements). The standards provide guidance on what to signal to use, and it is up to the operator and vendor to define what is required based on local requirements. Remember, in the international market there is a hybrid need. For example, some operators use the L package and require E package extensions. >(3) pktcSigDevStandardRingCadence and pktcSigDevRingSplashCadence >>> snip >(5) Mapping NCS signal requests (tones, rings) to MIB objects >>> snip Gordon Beacham Digital Core Gateways, BCS Motorola, Inc. 858-404-2335 [email protected]