Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)
draft-ietf-ipcdn-pktc-signaling-15
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 5098.
|
|
---|---|---|---|
Authors | s. kumar, Sumanth Channabasappa , Gordon Beacham | ||
Last updated | 2015-10-14 (Latest revision 2007-08-29) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 5098 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Dan Romascanu | ||
Send notices to | Randy_Presuhn@mindspring.com, RWoundy@broadband.att.com, sumanth@cablelabs.com |
draft-ietf-ipcdn-pktc-signaling-15
quot; DEFVAL { 4 } ::= { pktcSigEndPntConfigEntry 22 } pktcSigEndPntConfigRtoInit OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the initial number of seconds for the retransmission timer." REFERENCE "PacketCable NCS Specification" DEFVAL { 200 } ::= { pktcSigEndPntConfigEntry 23 } pktcSigEndPntConfigLongDurationKeepAlive OBJECT-TYPE SYNTAX Unsigned32 UNITS "minutes" MAX-ACCESS read-create STATUS current DESCRIPTION " Specifies a timeout value in minutes for sending long duration call notification message." REFERENCE "PacketCable NCS Specification" DEFVAL { 60 } ::= { pktcSigEndPntConfigEntry 24 } pktcSigEndPntConfigThist OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " Timeout period in seconds before no response is declared." REFERENCE "PacketCable NCS Specification" DEFVAL { 30 } ::= { pktcSigEndPntConfigEntry 25 } pktcSigEndPntConfigStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create Beacham/Kumar/Channabasappa Expires - January 2008 [Page 59] PacketCable/IPCablecom NCS Signaling MIB August 2007 STATUS current DESCRIPTION " This object contains the Row Status associated with the pktcSigEndPntConfigTable. There are no restrictions or dependencies amidst the columnar objects before this row can be activated or for modifications of the columnar objects when this object is set to a value of 'active(1)." ::= { pktcSigEndPntConfigEntry 26 } pktcSigEndPntConfigCallWaitingMaxRep OBJECT-TYPE SYNTAX Unsigned32 (0..10) MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the default value of the maximum number of repetitions of the call waiting tone that the MTA will play from a single CMS request. The MTA MUST NOT update this object with the information provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message." DEFVAL { 1 } ::= { pktcSigEndPntConfigEntry 27 } pktcSigEndPntConfigCallWaitingDelay OBJECT-TYPE SYNTAX Unsigned32 (1..100) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object contains the delay between repetitions of the call waiting tone that the MTA will play from a single CMS request." DEFVAL { 10 } ::= { pktcSigEndPntConfigEntry 28 } pktcSigEndPntStatusCallIpAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the type of Internet address contained in the MIB Object 'pktcSigEndPntStatusCallIpAddress'. Since pktcSigEndPntStatusCallIpAddress is expected to contain an IP address, a value of dns(16) is disallowed." Beacham/Kumar/Channabasappa Expires - January 2008 [Page 60] PacketCable/IPCablecom NCS Signaling MIB August 2007 ::= { pktcSigEndPntConfigEntry 29 } pktcSigEndPntStatusCallIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION " This MIB Object contains the chosen IP address of the CMS currently being used for the corresponding endpoint. The device determines the IP address by using DNS to resolve the IP address of the CMS from the FQDN stored in the MIB Object 'pktcSigEndPntConfigCallAgentId'. The processes are outlined in the PacketCable NCS and Security specifications, and MUST be followed by the MTA. The IP address type contained in this MIB Object is indicated by pktcSigEndPntStatusCallIpAddressType." REFERENCE "PacketCable NCS Specification; PacketCable Security specification, [PKT-SP-SEC]." ::= { pktcSigEndPntConfigEntry 30 } pktcSigEndPntStatusError OBJECT-TYPE SYNTAX INTEGER { operational (1), noSecurityAssociation (2), disconnected (3) } MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the error status for this interface. The operational status indicates that all operations necessary to put the line in service have occurred, and the CMS has acknowledged the Restart In Progress (RSIP) message successfully. If pktcMtaDevCmsIpsecCtrl is enabled for the associated Call Agent, the noSecurityAssociation status indicates that no Security Association (SA) yet exists for this endpoint. If pktcMtaDevCmsIpsecCtrl is disabled for the associated Call Agent, the noSecurityAssociation status is not applicable and should not be used by the MTA. The disconnected status indicates one of the following two: If pktcMtaDevCmsIpsecCtrl is disabled, then no security association is involved with this endpoint. The NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange. Beacham/Kumar/Channabasappa Expires - January 2008 [Page 61] PacketCable/IPCablecom NCS Signaling MIB August 2007 Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, security Association has been established, and the NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange." ::= { pktcSigEndPntConfigEntry 31 } pktcSigEndPntConfigMinHookFlash OBJECT-TYPE SYNTAX Unsigned32 (20..1550) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the minimum time a line needs to be on hook for a valid hook flash. The value of this object MUST be greater than the value of pktcSigEndPntConfigPulseDialMaxBreakTime. The value of pktcSigEndPntConfigMinHookFlash MUST be less than pktcSigEndPntConfigMaxHookFlash. This object MUST only be set via the MTA configuration during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be greater than the value contained by the MIB Object 'pktcSigEndPntConfigPulseDialMaxMakeTime'." DEFVAL { 300 } ::= { pktcSigEndPntConfigEntry 32 } pktcSigEndPntConfigMaxHookFlash OBJECT-TYPE SYNTAX Unsigned32 (20..1550) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum time a line needs to be on hook for a valid hook flash. The value of pktcSigEndPntConfigMaxHookFlash MUST be greater than pktcSigEndPntConfigMinHookFlash. This object MUST only be set via the MTA configuration during the provisioning process." DEFVAL { 800 } ::= { pktcSigEndPntConfigEntry 33 } pktcSigEndPntConfigPulseDialInterdigitTime OBJECT-TYPE SYNTAX Unsigned32 (100..1500) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the pulse dial inter-digit timeout. This object Beacham/Kumar/Channabasappa Expires - January 2008 [Page 62] PacketCable/IPCablecom NCS Signaling MIB August 2007 MUST only be set via the MTA configuration during the provisioning process." DEFVAL { 100 } ::= { pktcSigEndPntConfigEntry 34 } pktcSigEndPntConfigPulseDialMinMakeTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the minimum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinMakeTime MUST be less than pktcSigEndPntConfigPulseDialMaxMakeTime. This object MUST only be set via the MTA configuration during the provisioning process." DEFVAL { 25 } ::= { pktcSigEndPntConfigEntry 35 } pktcSigEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxMakeTime MUST be greater than pktcSigEndPntConfigPulseDialMinMakeTime. This object MUST only be provided via the configuration file during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be less than the value contained by the MIB Object pktcSigEndPntConfigMinHookFlash." DEFVAL { 55 } ::= { pktcSigEndPntConfigEntry 36 } pktcSigEndPntConfigPulseDialMinBreakTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the minimum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinBreakTime MUST be less than pktcSigEndPntConfigPulseDialMaxBreakTime. This object must only be provided via the configuration file during the provisioning process." DEFVAL { 45 } Beacham/Kumar/Channabasappa Expires - January 2008 [Page 63] PacketCable/IPCablecom NCS Signaling MIB August 2007 ::= { pktcSigEndPntConfigEntry 37 } pktcSigEndPntConfigPulseDialMaxBreakTime OBJECT-TYPE SYNTAX Unsigned32 (20..200) UNITS "Milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " This is the maximum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxBreakTime MUST be greater than pktcSigEndPntConfigPulseDialMinBreakTime. This object MUST only be provided via the configuration file during the provisioning process." DEFVAL { 75 } ::= { pktcSigEndPntConfigEntry 38 } -- -- notification group is for future extension. -- pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 0 } pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 2 } pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } -- -- compliance statements -- pktcSigBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION " The compliance statement for MTAs that implement NCS Signaling." MODULE -- pktcSigMib --- -- Unconditionally mandatory groups for all MTAs --- MANDATORY-GROUPS { pktcSigDeviceGroup, pktcSigEndpointGroup } --- -- Conditionally mandatory groups for MTAs --- Beacham/Kumar/Channabasappa Expires - January 2008 [Page 64] PacketCable/IPCablecom NCS Signaling MIB August 2007 GROUP pktcInternationalGroup DESCRIPTION " This group is mandatory only for MTAs implementing international telephony features." GROUP pktcLLinePackageGroup DESCRIPTION " This group is mandatory only for MTAs implementing the L Line Package" GROUP pktcELinePackageGroup DESCRIPTION " This group is mandatory only for MTAs implementing the E Line Package" ::={ pktcSigCompliances 1 } pktcSigDeviceGroup OBJECT-GROUP OBJECTS { pktcSigDevCodecMax, pktcSigDevEchoCancellation, pktcSigDevSilenceSuppression, pktcSigDevR0Cadence, pktcSigDevR1Cadence, pktcSigDevR2Cadence, pktcSigDevR3Cadence, pktcSigDevR4Cadence, pktcSigDevR5Cadence, pktcSigDevR6Cadence, pktcSigDevR7Cadence, pktcSigDevRgCadence, pktcSigDevRsCadence, pktcSigDefCallSigDscp, pktcSigDefMediaStreamDscp, pktcSigDevVmwiMode, pktcSigCapabilityType, pktcSigCapabilityVersion, pktcSigCapabilityVendorExt, pktcSigDefNcsReceiveUdpPort } STATUS current DESCRIPTION "Group of MIB Objects containing signaling configuration information that is applicable per-device." ::= { pktcSigGroups 1 } Beacham/Kumar/Channabasappa Expires - January 2008 [Page 65] PacketCable/IPCablecom NCS Signaling MIB August 2007 pktcSigEndpointGroup OBJECT-GROUP OBJECTS { pktcSigEndPntConfigCallAgentId, pktcSigEndPntConfigCallAgentUdpPort, pktcSigEndPntConfigPartialDialTO, pktcSigEndPntConfigCriticalDialTO, pktcSigEndPntConfigBusyToneTO, pktcSigEndPntConfigDialToneTO, pktcSigEndPntConfigMessageWaitingTO, pktcSigEndPntConfigOffHookWarnToneTO, pktcSigEndPntConfigRingingTO, pktcSigEndPntConfigRingBackTO, pktcSigEndPntConfigReorderToneTO, pktcSigEndPntConfigStutterDialToneTO, pktcSigEndPntConfigTSMax, pktcSigEndPntConfigMax1, pktcSigEndPntConfigMax2, pktcSigEndPntConfigMax1QEnable, pktcSigEndPntConfigMax2QEnable, pktcSigEndPntConfigMWD, pktcSigEndPntConfigTdinit, pktcSigEndPntConfigTdmin, pktcSigEndPntConfigTdmax, pktcSigEndPntConfigRtoMax, pktcSigEndPntConfigRtoInit, pktcSigEndPntConfigLongDurationKeepAlive, pktcSigEndPntConfigThist, pktcSigEndPntConfigStatus, pktcSigEndPntConfigCallWaitingMaxRep, pktcSigEndPntConfigCallWaitingDelay, pktcSigEndPntStatusCallIpAddressType, pktcSigEndPntStatusCallIpAddress, pktcSigEndPntStatusError } STATUS current DESCRIPTION "Group of MIB Objects containing signaling configuration information that is applicable per-endpoint." ::= { pktcSigGroups 2 } pktcInternationalGroup OBJECT-GROUP OBJECTS { pktcSigEndPntConfigMinHookFlash, pktcSigEndPntConfigMaxHookFlash, pktcSigEndPntConfigPulseDialInterdigitTime, pktcSigEndPntConfigPulseDialMinMakeTime, pktcSigEndPntConfigPulseDialMaxMakeTime, pktcSigEndPntConfigPulseDialMinBreakTime, pktcSigEndPntConfigPulseDialMaxBreakTime, Beacham/Kumar/Channabasappa Expires - January 2008 [Page 66] PacketCable/IPCablecom NCS Signaling MIB August 2007 pktcSigDevRingCadence, pktcSigDevCidSigProtocol, pktcSigDevCidDelayAfterLR, pktcSigDevCidDtmfStartCode, pktcSigDevCidDtmfEndCode, pktcSigDevVmwiSigProtocol, pktcSigDevVmwiDelayAfterLR, pktcSigDevVmwiDtmfStartCode, pktcSigDevVmwiDtmfEndCode, pktcSigDevrpAsDtsDuration, pktcSigDevCidMode, pktcSigDevCidAfterRing, pktcSigDevCidAfterDTAS, pktcSigDevCidAfterRPAS, pktcSigDevRingAfterCID, pktcSigDevCidDTASAfterLR, pktcSigDevVmwiMode, pktcSigDevVmwiAfterDTAS, pktcSigDevVmwiAfterRPAS, pktcSigDevVmwiDTASAfterLR, pktcSigPowerRingFrequency, pktcSigPulseSignalFrequency, pktcSigPulseSignalDbLevel, pktcSigPulseSignalDuration, pktcSigPulseSignalPulseInterval, pktcSigPulseSignalRepeatCount, pktcSigDevToneDbLevel, pktcSigDevToneFreqCounter, pktcSigDevToneWholeToneRepeatCount, pktcSigDevToneSteady, pktcSigDevToneFirstFreqValue, pktcSigDevToneSecondFreqValue, pktcSigDevToneThirdFreqValue, pktcSigDevToneFourthFreqValue, pktcSigDevToneFreqMode, pktcSigDevToneFreqAmpModePrtg, pktcSigDevToneFreqOnDuration, pktcSigDevToneFreqOffDuration, pktcSigDevToneFreqRepeatCount } STATUS current DESCRIPTION " Group of objects that extend the behavior of existing objects to support operations in the widest possible set of international marketplaces. Note that many of these objects represent a superset of behaviors described in other objects within this MIB Module." ::= { pktcSigGroups 3 } Beacham/Kumar/Channabasappa Expires - January 2008 [Page 67] PacketCable/IPCablecom NCS Signaling MIB August 2007 pktcLLinePackageGroup OBJECT-GROUP OBJECTS { pktcSigDevR0Cadence, pktcSigDevR1Cadence, pktcSigDevR2Cadence, pktcSigDevR3Cadence, pktcSigDevR4Cadence, pktcSigDevR5Cadence, pktcSigDevR6Cadence, pktcSigDevR7Cadence, pktcSigDevRgCadence, pktcSigDevRsCadence } STATUS current DESCRIPTION "Group of Objects to support the L Line Package." ::= { pktcSigGroups 4 } pktcELinePackageGroup OBJECT-GROUP OBJECTS { pktcSigDevR0Cadence, pktcSigDevR1Cadence, pktcSigDevR2Cadence, pktcSigDevR3Cadence, pktcSigDevR4Cadence, pktcSigDevR5Cadence, pktcSigDevR6Cadence, pktcSigDevR7Cadence, pktcSigDevRgCadence, pktcSigDevRsCadence, pktcSigPulseSignalFrequency, pktcSigPulseSignalDbLevel, pktcSigPulseSignalDuration, pktcSigPulseSignalPulseInterval, pktcSigPulseSignalRepeatCount, pktcSigDevRingCadence } STATUS current DESCRIPTION "Group of Objects to support the E Line Package." ::= { pktcSigGroups 5 } END 6. Examples This section provides a couple of examples, specifically related to the MIB tables pktcSigDevToneTable and pktcSigDevMultiFreqToneTable. Beacham/Kumar/Channabasappa Expires - January 2008 [Page 68] PacketCable/IPCablecom NCS Signaling MIB August 2007 Example A: Call waiting tone defined per ITU-T E.180: 1) 400 Hz AM modulated by 16 Hz, on for 500ms at -4 dBm 2) 400 Hz AM modulated by 16 Hz, off for 400ms 3) 400 Hz not AM modulated, on for 50 ms at -4 dBm 4) 400 Hz not AM modulated, off for 450 ms 5) 400 Hz not AM modulated, on for 50 ms at -4 dBm 6) 400 Hz not AM modulated, off for 3450 ms 7) 400 Hz not AM modulated, on for 50 ms at -4 dBm 8) 400 Hz not AM modulated, off for 450 ms 9) 400 Hz not AM modulated, on for 50 ms at -4 dBm 10) 400 Hz not AM modulated, off for 3450 ms 11) not repeated, not continuous Assume userDefined1(18) is assigned to this tone: pktcSigDevMultiFreqToneTable: ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count =================================================================== 18 400 16 0 0 1 90 -40 500 400 0 18 400 0 0 0 2 0 -40 50 450 0 18 400 0 0 0 2 0 -40 50 3450 0 18 400 0 0 0 2 0 -40 50 450 0 18 400 0 0 0 2 0 -40 50 3450 0 pktcSigDevToneTable: ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady ============================================================= 18 1 5 0 false(2) The single row of the pktcSigDevToneTable defines one multi- frequency group of five rows (ToneFreqCounter) defined in the pktcSigDevMultiFreqToneTable and instructs the MTA to play this group only once (non-repeatable as ToneRep-Count equals 0). Example B - Congestion Tone - congestion(17): Note: This example of an embedded cadence is based on an operator variation. 1) 400Hz on for 400ms -10 dBm 2) 400Hz off for 350ms 3) 400Hz on for 225ms -4 dBm 4) 400Hz off for 525ms Beacham/Kumar/Channabasappa Expires - January 2008 [Page 69] PacketCable/IPCablecom NCS Signaling MIB August 2007 5) repeat (1) through (4) 5000 times or T0 timeout (which ever is shortest period) pktcSigDevMultiFreqToneTable: ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count =================================================================== 17 400 0 0 0 2 0 -100 400 350 0 17 400 0 0 0 2 0 -40 225 525 0 pktcSigDevToneTable: ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady ============================================================= 17 1 2 5000 false(2) Example C - Call Waiting Tone - callWaiting1(9): 1) 16 Hz is modulated to carry the 400 Hz signal, ModulationRate within 85%, on for 500msec, at -25 dBm or more but less than -14 dBm 2) 16 Hz is modulated to carry the 400 Hz signal, off for 0 ~ 4 secs 3) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less than -14 dBm 4) 400 Hz not modulated, off for 450ms 5) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less than -14 dBm 6) 400 Hz not modulated, off for 3450ms ([4000 - (50+450+50)]) 7) Steps 3 thru 6 are repeated. pktcSigDevMultiFreqToneTable: ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count =================================================================== 9 1 400 16 0 0 1 85 -25 500 1000 0 9 2 400 0 0 0 2 0 -25 50 450 0 9 3 400 0 0 0 2 0 -25 50 3450 0 pktcSigDevToneTable: ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady ============================================================= 9 1 1 0 false(2) 9 2 2 1 false(2) The first row of the pktcSigDevToneTable table instructs the MTA to play one row (ToneFreqCounter) of the pktcSigDevMultiFreqToneTable table only once (non-repeatable as ToneRep-Count equals 0). The second row of the pktcSigDevToneTable table instructs the MTA to Beacham/Kumar/Channabasappa Expires - January 2008 [Page 70] PacketCable/IPCablecom NCS Signaling MIB August 2007 play next two rows (ToneFreqCounter) of the pktcSigDevMultiFreqToneTable table and make this frequency group repeatable (ToneRep-Count is not 0). 7. Acknowledgments The authors would like to thank the members of the IETF IPCDN working group and the CableLabs PacketCable Provisioning focus team for their contributions, comments and suggestions. Specifically, the following individuals are recognized: Angela Lyda Arris Interactive Romascanu, Dan Avaya Chad Griffiths Broadcom Corp. Eugene Nechamkin Broadcom Corp. Jean-Francois Mule CableLabs Matt A. Osman CableLabs Klaus Hermanns Cisco Systems, Inc. Rich Woundy Comcast Corp. Bert Wijnen Alcatel-Lucent Randy Presuhn Mindspring Phillip Freyman Motorola, Inc. Rick Vetter Motorola, Inc. Sasha Medvinsky Motorola, Inc. Wim De Ketelaere tComLabs David De Reu tComLabs Kristof Sercu tComLabs Roy Spitzer Telogy Networks, Inc. Itay Sherman Texas Instruments, Inc. Mauricio Sanchez Texas Instruments, Inc. Shivakumar Thangapandi Texas Instruments, Inc. Mike Heard Consultant The current editor (Sumanth Channabasappa) would like to recognize Phillip Freyman and Eugene Nechamkin for their contributions towards the international objects, and Stephane Bortzmeyer for assistance with the ABNF. The editor also extends appreciation to the IPCDN co-chairs (Jean- Francois Mule, Rich Woundy) and Dan Romascanu for the numerous reviews and valuable comments. Special appreciation is extended to Bert Wijnen, as the MIB doctor, for his ever useful and constructive comments. 8. Security Considerations Beacham/Kumar/Channabasappa Expires - January 2008 [Page 71] PacketCable/IPCablecom NCS Signaling MIB August 2007 There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The following Differentiated Services Code Point (DSCP) and mask objects are used to differentiate between various types of traffic in the service provider network: pktcSigDefCallSigDscp pktcSigDefMediaStreamDscp These objects may contain information that may be sensitive from a business perspective. For example, they may represent a customer's service contract that a service provider chooses to apply to a customer's ingress or egress traffic. If these objects are SET maliciously, it may permit unmarked or inappropriately marked signaling and media traffic to enter the service provider network, resulting in unauthorized levels of service for customers. The following objects determine ring cadence, repeatable characteristics, signal duration, and caller id subscriber line protocol for telephony operation: pktcSigDevR0Cadence pktcSigDevR1Cadence pktcSigDevR2Cadence pktcSigDevR3Cadence pktcSigDevR4Cadence pktcSigDevR5Cadence pktcSigDevR6Cadence pktcSigDevR7Cadence pktcSigDevRgCadence pktcSigDevRsCadence pktcSigDevCidSigProtocol pktcSigDevVmwiSigProtocol pktcSigPulseSignalDuration pktcSigPulseSignalPauseDuration If these objects are SET maliciously, it may result in unwanted operation, or a failure to obtain telephony service from client (MTA) devices. The objects in the pktcSigEndPntConfigTable are used for endpoint signaling. The pktcSigEndPntConfigCallAgentId object contains the name of the call agent, which includes the call agent Fully Qualified Domain Name (FQDN). If this object is SET maliciously, the Beacham/Kumar/Channabasappa Expires - January 2008 [Page 72] PacketCable/IPCablecom NCS Signaling MIB August 2007 MTA will not be able to communicate with the call agent, resulting in a disruption of telephony service. The pktcSigEndPntConfigCallAgentUdpPort object identifies the UDP port for NCS traffic. If this object is SET maliciously, the call agent will not receive NCS traffic from the MTA, also resulting in a disruption of telephony service. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. The most sensitive is pktcSigEndPntStatusCallIpAddress within pktcSigEndPntConfigTable. This information itself may be valuable to would-be attackers. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 9. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER Value ---------- ----------------------- pktcSigMib { mib-2 XXX } Editor's Note (to be removed prior to publication): the IANA is requested to assign a value for XXX under the mib-2 subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace XXX Beacham/Kumar/Channabasappa Expires - January 2008 [Page 73] PacketCable/IPCablecom NCS Signaling MIB August 2007 (here and in the MIB module) with the assigned value and to remove this note. 10. Normative References [PKT-SP-MIB-SIG-1.0] PacketCable(TM) 1.0 Signaling MIB Specification, Issued, PKT-SP-MIB-SIG-I09-050812, August 2005. http://www.packetcable.com/specifications/ http://www.cablelabs.com/specifications/archives/ [PKT-SP-MIB-SIG-1.5] PacketCable(TM) 1.5 Signaling MIB Specification, Issued, PKT-SP-MIB-SIG1.5-I01-050128, January 2005. http://www.packetcable.com/specifications/ http://www.cablelabs.com/specifications/archives/ [PKT-SP-SEC] PacketCable Security Specification, Issued, PKT-SP- SEC-I12-050812, August 2005. http://www.packetcable.com/specifications/ http://www.cablelabs.com/specifications/archives/ [ITU-T-J169] IPCablecom Network Call Signaling (NCS) MIB requirements, J.169, ITU-T, March, 2001. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002. [RFC4001] Daniel, M., Haberman, B., Routhier, S., and Schoenwaelder, J., "Textual Conventions for Internet Network Beacham/Kumar/Channabasappa Expires - January 2008 [Page 74] PacketCable/IPCablecom NCS Signaling MIB August 2007 Addresses", RFC 4001, May 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, December 2002. [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB" ,RFC2863, June 2000. [PKT-SP-CODEC] Packetcable Audio/Video Codecs Specification PKT-SP-CODEC-IO5-040113. [PKT-SP-MGCP] Packetcable Network-Based Call Signaling Protocol Specification PKT-SP-EC-MGCP-I10-040402. [PKT-SP-PROV] Packetcable MTA Device Provisioning Specification PKT-SP-PROV-I10-040730. 11. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control Protocol (MGCP)", RFC 3435, January 2003. [RFC4234] D. Crocker, Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC4234, October 2005. [RFC4682] Nechamkin, E., and Mule J., "Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable and IPCablecom compliant devices", RFC4682, <Date>. [ETSI-TS-101-909-4] ETSI TS 101 909-4:"Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 4: Network Call Signaling Protocol". [ETSI-TS-101-909-9] ETSI TS 101 909-9:"Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 9: IPCablecom Network Call Signalling (NCS) MIB Requirements". [ETSI-EN-300-001] ETSI EN 300-001 V1.5.1 (1998-10):"European Standard (Telecommunications series) Attachments to Public Switched Telephone Network (PSTN); Beacham/Kumar/Channabasappa Expires - January 2008 [Page 75] PacketCable/IPCablecom NCS Signaling MIB August 2007 General technical requirements for equipment connected to an analogue subscriber interface in the PSTN; Chapter 3: Ringing signal characteristics (national deviations are in Table 3.1.1)". [ETSI-EN-300-324-1] ETSI EN 300 324-1 V2.1.1 (2000-04):"V Interfaces at the digital Loop Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface specification". [ETSI-EN-300-659-1] ETSI EN 300 659-1: "Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On hook data transmission". [ITU-T-E.180] ITU-T E.180: "Various Tones Used in National Networks, Supplement 2 to Recommendation E.180". [ETSI-TR-101-183] ETSI TR-101-183: "Public Switched Telephone Network (PSTN) Analogue Ringing Signals". Authors' Addresses Gordon Beacham Motorola, Inc. 6450 Sequence Drive, Bldg. 1 San Diego, CA 92121, USA +1 858-404-2334 gordon.beacham@motorola.com Satish Kumar Mudugere Eswaraiah Texas Instruments India (P) Ltd., Golf view, Wind Tunnel Road Murugesh Palya Bangalore 560 017, INDIA +91 80 5269451 satish.kumar@ti.com Sumanth Channabasappa Cable Television Laboratories, Inc. 858 Coal Creek Circle, Louisville, CO 80027, USA +1 303-661-3307 Sumanth@cablelabs.com Beacham/Kumar/Channabasappa Expires - January 2008 [Page 76] PacketCable/IPCablecom NCS Signaling MIB August 2007 Disclaimer of validity The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE Beacham/Kumar/Channabasappa Expires - January 2008 [Page 77] PacketCable/IPCablecom NCS Signaling MIB August 2007 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Beacham/Kumar/Channabasappa Expires - January 2008 [Page 78]