1
Scope
2 References
3 Terms and definitions
4 Abbreviations
5 Introduction
5.1 Service goals
5.2 Specification goals
5.3 IPCablecom reference architecture
5.4 Components and interfaces
5.4.1 MTA
5.4.2 Provisioning Server
5.4.3 Telephony Syslog server
5.4.4 MTA to DHCP server
5.4.5 MTA to Provisioning Application
5.4.6 MTA to CMS
5.4.7 MTA to Security Server (TGS)
5.4.8 MTA and configuration data file access
5.4.9 DHCP extensions for MTA Provisioning
6 Provisioning overview
6.1 Device provisioning
6.2 Endpoint provisioning
6.3 Provisioning state transitions
7 Provisioning flows
7.1 Backoff, retries and time-outs
7.2 Embedded-MTA power-on
initialization flows
7.3 Post initialization incremental provisioning
7.3.1 Synchronization of provisioning attributes with configuration file
7.3.2 Enabling services on an MTA endpoint
7.3.3 Disabling services on an MTA endpoint
7.3.4 Modifying services on an MTA endpoint
7.4 MTA replacement
7.5 Temporary signal loss
8
DHCP options
8.1 Code 177: IPCablecom servers option
8.1.1 Service Provider's DHCP Server Address (sub-option 1 and sub-option 2)
8.1.2 Service Provider's SNMP Entity Address (sub-option 3)
8.1.3 DNS system (sub-option 4 and sub-option 5)
8.2 Code
60: Vendor Client Identifier
9
MTA Provisionable Attributes
9.1 MTA configuration file name
9.2 MTA configuration file
9.2.1 Device level configuration data
9.2.2 Device Level Service Data
9.2.3
Per-Endpoint Configuration Data
10 MTA device capabilities
Bibliography