Home>ANSI standards list>ANSI SCTE 165-21 pdf free download

ANSI SCTE 165-21 pdf free download

ANSI SCTE 165-21 pdf free download.IPCablecom 1.5 Part 21: Signaling Extension MIB.
2 REFERENCES
The following documents contain provisions which, through reference in this text, constitute provisions of this standard. At the time of Subcommittee approval, the editions indicated were valid. All documents are subject to revision, and while parties to agreement based on this standard are encouraged to investigate the possibility of applying the most recent editions of the documents listed below, they are reminded that newer editions of those documents might not be compatible with the referenced version.
2.1 Normative References
[1] ANSI/SCTE 165-05 2016, IPCablecom 1.5 Part 5: MTA Device Provisioning.
[2] IETF STD 62, Simple Network Management Protocol Version 3 (SNMPv3), December 2002.
[3] IETF RFC 2669, Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems.
[4] ANSI/SCTE 23-03 2010, DOCSIS 1.1 Part 3: Operations Support System Interface
[5] 1ETF STD 5, Internet Protocol, September 1981.
[6] IETF RFC 2011, SNMPv2 Management Information Base for the Internet Protocol using SMIv2, November
1996.
[7] IETF RFC 2863, The Interfaces Group MIB, June 2000.
[8] ANSI/SCTE 107 2009, Embedded Cable Modem Devices
[9] CableLabs Definition MIB Specification, CL-SP-MIB-CLABDEF-I1 1-1603 17, March 17, 2016, Cable Television Laboratories, inc.
[10] ANSI/SCTE 79-02 2016. DOCSIS 2.0, Operations Support System interface.
[11] ANSI/SCTE 167-07 2016, IPCablecom 1.5 Part 7: MTA MIB.
[121 ANSI/SCTE 165-08 2016. IPCablecom 1.5 Part 8: Signaling MIB.
[131 ANSI/SCTE 165-06 2016, IPCablecom 1.5 Part 6: MIBs Framework Specification.
[14] IETF RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Signals, May 2000.
[15] ANSI/SCTE 165-02 2016. IPCablecom 1.5 Part 2: Audio/Video Codecs.
116] ANSI/SCTE 165-03 2016. IPCablecom 1.5 Part 3: Network-Based Call Signaling Protocol.
2.2 Informative References
In order to claim compliance with this standard, it is necessary to conform to the following standards and other works as indicated, in addition to the other requirements of this standard. intellectual property rights may he required to implement these references.
[17] Data-Over-Cable Service Interface Specifications, Cable Modem to Customer Premise Equipment Interface Specification, CMCI, CM-SP-CMCI-C0l -081 104, November 4, 2008, Cable Television Laboratories, Inc.
[18]IETF RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP), December
2002.
[19] IETF RFC 2579, Textual Conventions for SMIv2, April 1999.
[20] 1ETF RFC 3410, introduction and Applicability Statements for Internet-Standard Management Framework, December 2002.
“This MIB Object allows the Service Provider to choose a suitable policy for Loop Voltage behavior on MTAS . Unless overridden by the operator, the MTA MUST use the default value specified in the definition of this MIB Ob ject . The MTA MUST adhere to PacketCable signal ing requi rements, such as the NCS open loop voltage requi rement, i rrespective of any chosen pol icy . For MTAS that need to remove 1oop voltage during the MTA initialization phase, in contradiction to a chosen policy, such a loop voltage removal period MUST NOT exceed 1000ms . The MTA MUST retain the value of this MIB Object across hard reboots or soft resets (for a definition of the terms , please refer to [1]) 。 This MIB object specifies four policies. An informative illustration of the E-MTA behavior with different policies is presented in Appendix A. Provisioned line is an MTA Endpoint that has been provided with valid per-line configuration data either via the configuration file (during provisioning) or the SNMP management interface.This policy is similar to Policy 1,except for the ability to recognize events like cable cuts (due to malicious activities, or otherwise) . The following requi rements apply to policies 3 and 4: 一upon the onset of a re-initialization due to a soft reset the MTA MUST continue to maintain the existing policy and state on provisioned 1 ines, unless overridden by a policy or the provisioning process specifies otherwise 一once the provisioning process is completed with the value of the MIB Ob ject pktcMtaDevP rovisioningState set to a value of ‘pass (1) ‘,’ passWithWarnings(4)’or ‘ pa ssWithIncompleteParsing(5) ‘,the MTA MUST apply the chosen policy to all the provisioned lines.ANSI SCTE 165-21 pdf download.

                       

Related Standards

Categories