ANSI SCTE 165-05:2019 pdf download.IPCablecom 1.5-Part 5: MTA Device Provisioning.
The scope of this document is limited to the provisioning of an IPCablecom 1.5 ernbeddcd-MTA device by a single provisioning and network management provider. An attempt has been made to provide enough detail to enable vendors to build an ernbeddcd-MTA device that is interoperable in an IPCablecom 1.5 network configuration. This document defines the provisioning of MTA components of the embedded MTA device (unless stated otherwise).
1.3 Requirements and Conventions
Throughout this document, 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.
Other text is descriptive or explanatory.
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
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.
[1] IETF RFC 2131, DHCP: Dynamic Host Configuration Protocol, March 1997.
[2] ANSI/SCTE 165-07 2019, IPCablecom 1.5 Part 7: MTA MIB.
[3] ANSI/SCTE 165-08 2019, lPCablecom 1.5 Part 8: Signaling MIB.
[4] ANSI/SCTE 165-03 2016, lPCablecom 1.5 Part 3: Network-Based Call Signaling Protocol.
[5] ANSI/SCTE 165-10 2009, IPCablecom 1.5 Part 10: Security.
[6] ANSI/SCTE 23-01 2019. DOCSIS 1.1 Part 1: Radio Frequency Interface.
[7] IETF RFC 3413/STDOO62, Simple Network Management Protocol (SNMP) Applications, December 2002.
[8] IETF RFC 3414/STDOO62, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3), December 2002.
[9] IETF RFC 341 5/STDOO62, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), December 2002.
[10] IETF RFC 3396. Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4), November 2002.ANSI SCTE 165-05 pdf download.