ANSI SCTE 165-21-2016 pdf download.Signaling Extension MIB
1.1 Purpose of the Document
New objects that are being introduced beyond IPCablecom 1.0 for Signaling MIBS are being grouped in this document so that the additional changes made can be tracked easily.
1.2 Requirements
Throughout this document, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST” This word means that the item is an absolute requirement of this specification. “MUST NOT” This phrase means that the item is an absolute prohibition of this specification. “SHOULD” This word means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT” This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. “MAY” This word means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item.
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] IETF 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-I11-160317, 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.
[12] ANSI/SCTE 165-08 2016, IPCablecom 1.5 Part 8: Signaling MIB.
[13] 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.
[16] 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 be required to implement these references.
[17] Data-Over-Cable Service Interface Specifications, Cable Modem to Customer Premise Equipment Interface Specification, CMCI, CM-SP-CMCI-C01-081104, 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] IETF RFC 3410, Introduction and Applicability Statements for Internet-Standard Management Framework,December 2002.
[21] IETF RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks, December 2002.
[22] IETF RFC 3412, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP), December 2002.
[23] IETF RFC 2821, Simple Mail Transfer Protocol, April 2001.
[24] SCTE 165-04 2016, IPCablecom 1.5 Part 4: Dynamic Quality-of-Service.
[25] IETF RFC 3594, PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option, September 2003.
[26] IETF RFC 2782, A DNS RR for specifying the location of services (DNS SRV), February 2000.
[27] IETF RFC 3584, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework, August 2003.
[28] ANSI/SCTE 165-15 2016, IPCablecom 1.5 Part 15, Management Event MIB Specification.ANSI SCTE 165-21-2016 pdf download
