ETSI TS 103 161-11 V1.1.1 (2011-10)

Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 11: Media Terminal Adapter (MTA) device provisioning

DTS/ATTM-003011-11

General Information

• Status: Published
• Publication Date: 26-Oct-2011
• Technical Committee: ATTM AT3 - Integrated broadband cable and television networks
• Current Stage: 12 - Completion
• Due Date: 31-Oct-2011
• Completion Date: 27-Oct-2011

Standards Content (Sample)

Technical Specification
Access, Terminals, Transmission and Multiplexing (ATTM);
Integrated Broadband Cable and Television Networks;
IPCablecom 1.5;
Part 11: Media terminal adapter (MTA) device provisioning

2 ETSI TS 103 161-11 V1.1.1 (2011-10)

Reference
DTS/ATTM-003011-11
Keywords
access, broadband, cable, IP, multimedia, PSTN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2011.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners. ®
GSM and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 161-11 V1.1.1 (2011-10)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Introduction . 8
1.1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 10
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 11
4 Void . 12
5 Background . 12
5.1 Service Goals . 12
5.2 Document Goals . 12
5.3 IPCablecom Reference Architecture . 13
5.4 Components and Interfaces . 14
5.4.1 MTA . 14
5.4.1.1 MTA Security Requirements . 15
5.4.1.2 MTA SNMP Requirements . 15
5.4.2 Provisioning Server. 15
5.4.3 MTA to Telephony Syslog Server . 16
5.4.4 MTA to DHCP Server . 16
5.4.5 MTA to Provisioning Application . 16
5.4.6 MTA to CMS . 17
5.4.7 MTA to Security Server (KDC) . 17
5.4.8 MTA and Configuration Data File Access . 17 ®
5.4.9 DOCSIS extensions for MTA Provisioning . 17
6 Provisioning Overview . 18
6.1 Device Provisioning . 18
6.2 Endpoint Provisioning . 18
6.3 Secure Flow Provisioning State Transitions . 18
6.4 Basic and Hybrid Flow Provisioning State Transitions . 19
7 Provisioning Flows . 20
7.1 Backoff, Retries, and Timeouts . 21
7.2 Embedded-MTA Power-On Initialization Flow (Secure Flow) . 22
7.2.1 Embedded-MTA Secure Power-on Initialization Flow (IPv4 eCM) . 22
7.2.2 Embedded-MTA Secure Power-on Initialization Flow (IPv6 eCM) . 28
7.3 Embedded-MTA Power-On Initialization Flow (Basic Flow) . 30
7.4 Embedded-MTA Power-On Initialization Flow (Hybrid Flow). . 31
7.5 Endpoint Provisioning Completion Notifications . 33
7.6 Post Initialization Incremental Provisioning . 34
7.6.1 Synchronization of Provisioning Attributes with Configuration File . 34
7.6.2 Adding/Enabling Telephony Services on an MTA Endpoint . 34
7.6.3 Deleting/Disabling Telephony Services on an MTA Endpoint. 35
7.6.4 Modifying Telephony Services on an MTA Endpoint . 36
7.7 Reflecting the State of the Endpoint Interface in the ifTable . 36
7.8 Provisioning of the Signalling Communication Path Between the MTA and CMS . 37
7.9 MTA Replacement . 37
7.10 Temporary Signal Loss . 37
7.11 MTA Hard Reboot/Soft Reset scenarios. . 37
8 DHCP Options . 37
ETSI
4 ETSI TS 103 161-11 V1.1.1 (2011-10) ®
8.1 DHCP Option 122: CableLabs Client Configuration Option . 38
8.1.1 Service Provider's DHCP Address (sub-option 1 and 2) . 39
8.1.2 Service Provider's Provisioning Entity Address (sub-option 3) . 39
8.1.3 AS-REQ/REP Exchange Backoff and Retry for SNMPv3 Key Management (sub-option 4) . 39
8.1.4 AP-REQ/REP Kerberized Provisioning Backoff and Retry (sub-option 5) . 40
8.1.5 Kerberos Realm of SNMP Entity (sub-option 6) . 40
8.1.5.1 SNMPv3 Key Establishment . 41
8.1.6 Ticket Granting Server Usage (sub-option 7) . 41
8.1.7 Provisioning Timer (sub-option 8) . 41
8.1.8 Security Ticket Invalidation (sub-option 9) . 41
8.2 DHCP Option 60: Vendor Client Identifier . 42
8.3 DHCP Options 12 and 15 . 42
8.4 DHCP Option 6 . 42
8.5 DHCP Option 43 . 42
8.6 DHCP OPTION 1 . 44
8.7 DHCP OPTION 3 . 44
8.8 DHCP OPTION CL_V4_PACKETCABLE_MIB_ENV_OPTION . 44
9 MTA Provisionable Attributes . 44
9.1 MTA Configuration File . 45
9.1.1 Device Level Configuration Data . 49
9.1.2 Device Level Service Data. 50
9.1.3 Per-Endpoint Configuration Data . 52
9.1.4 Per-Realm Configuration Data . 54
9.1.5 Per-CMS Configuration Data . 55
9.1.6 Exclusion of MIB objects in configuration File . 56
10 MTA Device Capabilities . 56
10.1 IPCablecom Version. 57
10.2 Number Of Telephony Endpoints . 57
10.3 TGT Support . 57
10.4 HTTP Download File Access Method Support . 57
10.5 MTA-24 Event SYSLOG Notification Support . 57
10.6 NCS Service Flow Support . 58
10.7 Primary Line Support . 58
10.8 Vendor Specific TLV Type(s) . 58
10.9 NVRAM Ticket/Ticket Information Storage Support . 58
10.10 Provisioning Event Reporting Support . 58
10.11 Supported CODEC(s) . 58
10.12 Silence Suppression Support . 59
10.13 Echo Cancellation Support . 59
10.14 RSVP Support . 59
10.15 UGS-AD Support . 59
10.16 MTA's "ifIndex" starting number in "ifTable" . 59
10.17 Provisioning Flow Logging Support . 60
10.18 Supported Provisioning Flows . 60
10.19 T38 Version Support . 60
10.20 T38 Error Correction Support . 61
10.21 RFC 2833 DTMF Support . 61
10.22 Voice Metrics Support . 61
10.23 Device MIB Support . 61
10.23.1 Issuing Organization Assignments . 62 ®
10.23.2 Representing CableLabs MIBs . 62
10.23.3 Representing IETF MIBs . 62
10.23.4 Example . 62
10.24 Multiple Grants Per Interval Support . 63
10.25 V.152 Support . 63
11 TLV-38 SNMP Notification Receiver Specification . 63
11.1 Sub-TLVs of TLV-38 . 63
11.1.1 SNMP Notification Receiver IP Address . 63
11.1.2 SNMP Notification Receiver UDP Port Number . 64
11.1.3 SNMP Notification Receiver Type . 64
ETSI
5 ETSI TS 103 161-11 V1.1.1 (2011-10)
11.1.4 SNMP Notification Receiver Timeout . 64
11.1.5 SNMP Notification Receiver Retries . 64
11.1.6 SNMP Notification Receiver Filtering Parameters . 64
11.1.7 SNMPv3 Notification Receiver Security Name . 65
11.2 Mapping of TLV fields into SNMP Tables . 65
11.2.1 Mapping of TLV fields into created SNMP Table rows . 65
11.2.1.1 snmpNotifyTable . 66
11.2.1.2 snmpTargetAddrTable . 66
11.2.1.3 snmpTargetAddrExtTable . 66
11.2.1.4 snmpTargetParamsTable . 67
11.2.1.5 snmpNotifyFilterProfileTable . 67
11.2.1.6 snmpNotifyFilterTable . 67
11.2.1.7 snmpCommunityTable . 67
11.2.1.8 usmUserTable . 68
11.2.1.9 vacmSecurityToGroupTable . 69
11.2.1.10 VacmAccessTable . 69
11.2.1.11 vacmViewTreeFamilyTable . 69
11.3 TLV38 and TLV11 Configuration Example . 70
11.3.1 TLV-38 Example . 70
11.3.2 Content of the SNMP framework tables after processing of the above example TLV38s. 70
12 SNMPv2c Management Requirements . 72
12.1 SNMPV2c Co-existence mode tables content created by MTA after MTA-4 for Hybrid and Basic
Flows. . 73
12.2 SNMP Default entries for SNMPv2c Access . 73
13 Service interruption impact reporting and other enhanced features support . 75 ®
13.1 eDOCSIS Requirements support . 75
13.1.1 Impact Analysis and Reporting Requirements: . 75
13.1.1.1 Impact Analysis . 76
13.1.1.2 Supported Impact Levels and Reporting . 76
13.2 IPCablecom Extension MIB . 76
13.2.1 MTA MIB Extension . 76
13.2.2 Signalling MIB Extension . 76
13.3 Battery Backup MIBS . 76
13.4 Syslog MIBS . 76
13.5 Foreign Potential Detection . 76
Annex A (informative): SNMPv2c co-existence Configuration Example - Template for service
providers . 77
Annex B (informative): Bibliography . 78
History . 79

ETSI
6 ETSI TS 103 161-11 V1.1.1 (2011-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission
and Multiplexing (ATTM).
The present document is part 11 of a multi-part IPCablecom 1.5 deliverable covering the Digital Broadband Cable
Access to the Public Telecommunications Network; IP Multimedia Time Critical Services, as identified below:
Part 1: "Overview";
Part 2: "Architectural framework for the delivery of time critical services over Cable Television Networks using
Cable Modems";
Part 3: "Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Television
Networks using Cable Modems";
Part 4: "Network Call Signalling Protocol";
Part 5: "Dynamic Quality of Service for the Provision of Real Time Services over Cable Television Networks
using Cable Modems";
Part 6: "Event Message Specification";
Part 7: "Media Terminal Adapter (MTA Management Information Base (MIB)";
Part 8: "Network Call Signalling (NCS) MIB Requirements";
Part 9: "Security";
Part 10: "Management Information Base (MIB) Framework";
Part 11: "Media terminal adapter (MTA) device provisioning";
Part 12: "Management Event Mechanism";
Part 13: "Trunking Gateway Control Protocol - MGCP option";
Part 14: "Embedded MTA Analog Interface and Powering Specification"
Part 15: "Analog Trunking for PBX Specification";
Part 16: "Signalling for Call Management Server";
Part 17: "CMS Subscriber Provisioning Specification";
Part 18: "Media Terminal Adapter Extension MIB";
Part 19: "IPCablecom Audio Server Protocol Specification - MGCP option";
Part 20: "Management Event MIB Specification";
ETSI
7 ETSI TS 103 161-11 V1.1.1 (2011-10)
Part 21: "Signalling Extension MIB Specification".
NOTE 1: Additional parts may be proposed and will be added to the list in future versions.
NOTE 2: The choice of a multi-part format for this deliverable is to facilitate maintenance and future
enhancements.
ETSI
8 ETSI TS 103 161-11 V1.1.1 (2011-10)
1 Introduction
The present document describes the IPCablecom 1.5 embedded-MTA device initialization and provisioning. The
present document is issued to facilitate design and field-testing leading to manufacturability and interoperability of
conforming hardware and software by multiple vendors.
1.1 Scope
The scope of the present document is limited to the provisioning of a IPCablecom 1.5 embedded-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 embedded-MTA device that is interoperable in an IPCablecom 1.5 network configuration. The
present document defines the provisioning of MTA components of the embedded MTA device (unless stated
otherwise).
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] IETF RFC 2131: "DHCP: Dynamic Host Configuration Protocol", March 1997.
[2] ETSI TS 103 161-7: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 7: Media Terminal Adapter
(MTA) Management Information Base (MIB)".
[3] ETSI TS 103 161-8: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 8: Network Call Signalling
(NCS) MIB Requirements".
[4] ETSI TS 103 161-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5 Part 4: Network Call Signalling
Protocol".
[5] ETSI TS 103 161-9: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 9: Security".
[6] ETSI ES 201 488: "Access and Terminals (AT); Data Over Cable Systems".
[7] IETF RFC 3413/STD0062: "Simple Network Management Protocol (SNMP) Applications",
December 2002.
[8] IETF RFC 3414/STD0062: "User-based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3)", December 2002.
[9] IETF RFC 3415/STD0062: "View-based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", December 2002.
ETSI
9 ETSI TS 103 161-11 V1.1.1 (2011-10)
[10] IETF RFC 3396: "Encoding Long Options in the Dynamic Host Configuration Protocol
(DHCPv4)", November 2002.
[11] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions", March 1997.
[12] ANSI/SCTE 107 2009: "Embedded Cable Modem Devices".
[13] ETSI TS 103 161-20: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 20: Management Event MIB
Specification".
[14] ETSI TS 103 161-12: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5 Part 12: Management Event
Mechanism".
[15] ETSI TS 103 161-21: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 21: Signalling Extension MIB
Specification".
[16] ETSI TS 103 161-18: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5 Part 18: Media Terminal Adapter
Extension MIB". ®
[17] Cable Television Laboratories, Inc. (CL-SP-MIB-BB-I04-100608):"CableLabs Battery Backup
MIB Specification", June 8, 2010.
[18] ETSI EN 302 878-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Third
Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; ®
Part 4: MAC and Upper Layer Protocols; DOCSIS 3.0". ®
[19] Cable Television Laboratories, Inc. (CL-SP-CANN-DHCP-Reg-I06-110210): "CableLabs ' DHCP
Options Registry Specification", February 10, 2011,
[20] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", July 2003.
[21] IETF RFC 4682: "Multimedia Terminal Adapter (MTA) Management Information Base for
PacketCable- and IPCablecom-Compliant Devices", December 2006.
[22] IETF RFC 5098: "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters
(MTAs)", February 2008.
[23] IETF RFC 5428: "Management Event Management Information Base (MIB) for PacketCable- and
IPCablecom-Compliant Devices", April 2009.
[24] IETF RFC 2863: "The Interfaces Group MIB", June 2000.
[25] IETF RFC 2833: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals ",
May 2000.
[26] IETF RFC 3495: "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client
Configuration", March 2003.
[27] IETF RFC 3412/STD0062: "Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)", December 2002. ®
[28] ANSI/SCTE 23-3: 2010, DOCSIS 1.1 Part 3: "Operations Support System Interface".
[29] ETSI TS 103 161-10: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5 Part 10: Management Information
Base (MIB) Framework"
[30] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1".
[31] IETF RFC 3617: "Uniform Resource Identifier (URI) Scheme and Applicability Statement for the
Trivial File Transfer Protocol (TFTP)".
ETSI
10 ETSI TS 103 161-11 V1.1.1 (2011-10)
[32] IETF RFC 3584: "Coexistence between Version 1, Version 2, and Version 3 of the
Internet-standard Network Management Framework", August 2003.
[33] IETF RFC 3611: "RTP Control Protocol Extended Reports (RTCP XR)", November 2003.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area. ®
[i.1] Cable Television Laboratories, Inc. (CL-SP-MIB-CLABDEF-I09-110210): "CableLabs
Definition MIB Specification", February 10, 2011.
[i.2] ETSI TS 103 161-2: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5 Part 2: Architectural framework for
the delivery of time critical services over Cable Television Networks using Cable Modems".
[i.3] IETF RFC 3410: "Introduction and Applicability Statements for Internet-Standard Management
Framework", December 2002.
[i.4] IETF RFC 3411: "An Architecture for Describing Simple Network Management Protocol (SNMP)
Management Frameworks", December 2002.
[i.5] IETF RFC 2475: "An Architecture for Differentiated Services", December 1998.
[i.6] ETSI TS 103 161-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 3: Audio Codec Requirements
for the Provision of Bi-Directional Audio Service over Cable Television Networks using Cable
Modems".
[i.7] ETSI TS 103 161-5: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 5: Dynamic Quality of Service
for the Provision of Real Time Services over Cable Television Networks using Cable Modems".
[i.8] IETF RFC 3594: "PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs
Client Configuration (CCC) Option", September 2003.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
authentication: process of verifying the claimed identity of an entity to another entity ®
Cable Modem Termination System (CMTS): device at a cable headend which implements the DOCSIS RFI MAC
protocol and connects to CMs over an HFC network
embedded MTA: single node that contains both an MTA and a cable modem
encryption key: key used in a cryptographic algorithm to translate the plaintext to ciphertext
encryption: method used to translate plaintext into ciphertext
endpoint: terminal, Gateway or Multipoint Conference Unit (MCU)
Hybrid Fibre/Coaxial (HFC): broadband bi-directional shared media transmission system using fibre trunks between
the headend and the fibre nodes, and coaxial distribution from the fibre nodes to the customer locations
Kerberos: secret-key network authentication protocol that uses a choice of cryptographic algorithms for encryption and
a centralized key database for authentication
ETSI
11 ETSI TS 103 161-11 V1.1.1 (2011-10)
key: mathematical value input into the selected cryptographic algorithm
Media Access Control (MAC): sublayer of the Data Link Layer that normally runs directly over the physical layer
Message Digest 5 (MD5): one-way hash algorithm that maps variable length plaintext into fixed-length (16 byte)
ciphertext
Multimedia Terminal Adapter (MTA): interface between a physical voice device, a network interface, CODECs, and
all signalling and encapsulation functions required for VoIP transport, class features signalling, and QoS signalling
network management: functions related to the management of data across the network ®
Standalone MTA (S-MTA): single node that contains an MTA and a non-DOCSIS MAC (e.g. ethernet)
Type of Service (TOS): 8-bit field of every IP version 4 packet; in a DiffServ domain, the TOS byte is treated as the
DiffServ Code Point, or DSCP
User Datagram Protocol (UDP): connectionless protocol built upon Internet Protocol (IP)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply: ®
CM DOCSIS Cable Modem
CMS Call Management Server
CMTS Cable Modem Termination System
CODEC COder-DECoder
CSR Customer Service Representative
DE Default
DES Data Encryption Standard
DHCP Dynamic Host Configuration Protocol
DNS Domain Name Service ®
DOCSIS Data-Over-Cable Service Interface Specifications
DSC Dynamic Service Change
DSCP DiffServ Code Point
DTMF Dual-tone Multi Frequency (tones)
E-MTA Embedded MTA
ETSI European Telecommunications Standards Institute
FQDN Fully Qualified Domain Name
HFC Hybrid Fiber/Coaxial
HTTP HyperText Transfer Protocol
IETF Internet Engineering Task Force
IP Internet Protocol
IPsec Internet Protocol Security
ISDN Integrated Services Digital Network
KDC Key Distribution Centre
MAC Media Access Control
MD5 Message Digest 5
MIB Management Information Base
MSB Most Significant Bit
MTA Multimedia Terminal Adapter
MWD Maximum Waiting Delay
NCS Network Call Signalling
NVRAM Non-Volatile Random Access Memory
OID Object Identification
PSTN Public Switched Telephone Network ®
RFI The DOCSIS Radio Frequency Interface specification
RTO Retransmission Timeout
S-MTA Standalone MTA
SNMP Simple Network Management Protocol
TFTP Trivial File Transfer Protocol
TGS Ticket Granting Server A sub-system of the KDC used to grant Kerberos tickets
ETSI
12 ETSI TS 103 161-11 V1.1.1 (2011-10) ®
TLV Type-Length-Value A tuple within a DOCSIS configuration file
TOS Type of Service
UDP User Datagram Protocol
4 Void
5 Background
5.1 Service Goals
Cable operators are interested in deploying high-speed data communications systems on cable television systems. Cable
operators have prepared a series of interface documents that will permit the early definition, design, development, and
deployment of packet data over cable systems on an uniform, consistent, open, non-proprietary, multi-vendor
interoperable basis. The intended service enables voice communications, video, and data services based on
bi-directional transfer of Internet protocol (IP) traffic, between the cable system headend and customer locations, over
an all-coaxial or hybrid-fibre/coax (HFC) cable network, defined by the data over cable service interface document
® ®
(DOCSIS ) standard. This is shown in simplified form in figure 1. It is to be noted that the term "DOCSIS " in the ®
present document is understood to refer to DOCSIS version 1.1 or later, unless explicitly specified otherwise. ®
Implementations of eCMs will refer to the corresponding DOCSIS versions and associated requirements in the present ®
document and DOCSIS documents for compliance.
Cable Modem
Wide-Area Termination
Network System
Cable
CMTS (CMTS)
CM Customer Premises
Network Cable Modem
Network Side
Equipment Interface Customer
(CM)
Interface
Premises
Equipment
Transparent IP Traffic Through the System

Figure 1: Transparent IP Traffic Through the Data-Over-Cable System
The transmission path over the cable system is realized at the headend by a cable modem termination system (CMTS),
and at each customer location by a cable modem (CM). The intent is for operators to transfer IP traffic transparently
between these interfaces.
5.2 Document Goals
The goal of the present document is to meet and to satisfy cable member companies, IPCablecom business and technical
requirements.
Requirements relevant to device provisioning are:
• A single physical device (e.g. embedded-MTA) will be completely provisioned and managed by a single
business entity. This provider may establish business relationships with additional providers for services such
as data, voice communications, and other services. ®
• To provision an E-MTA, both the DOCSIS and IPCablecom 1.5 provisioning steps must be performed. The
eMTA must have its own IP address, different from the IP Address(es) of the eCM. The eMTA must also have
its own MAC address, different from the MAC address of the eCM. Furthermore, the E-MTA must in be able
to operate in environments where the eMTA IP address may be in the same, or different subnet as the eCM.
ETSI
13 ETSI TS 103 161-11 V1.1.1 (2011-10)
• IPCablecom requires a unique FQDN for the MTA-component in the embedded-MTA. This FQDN must be
included in the DHCP OFFER and DHCP ACK messages to the MTA-component. IPCablecom makes no
additional FQDN requirements on the CM component in the embedded-MTA beyond those required by ®
DOCSIS . Mapping of the FQDN to IP address must be configured in the network DNS server and be
available to the rest of the network.
• IPCablecom 1.5 embedded-MTA provisioning must use DHCP Option-12 and Option-15 to deliver the MTA
FQDN to the E-MTA.
• IPCablecom 1.5 embedded-MTA provisioning must support two separate configuration files, a ®
DOCSIS -specified configuration file for the CM component, and a IPCablecom-specified configuration file
for the MTA component.
• The embedded-MTA is outside the IPCablecom network trust boundary as defined in the IPCablecom
Architecture Specification [i.2]. ®
• IPCablecom 1.5 E-MTA must support DOCSIS software download as defined in the corresponding eCM
® ®
DOCSIS Specification. A single DOCSIS software download must be used to upgrade software for both the
eCM and the eMTA.
• IPCablecom 1.5 must support use of SNMPv2c co-existence for network management operations for devices
provisioned under the Basic Flow or the Hybrid Flow and SNMPv3/v2 co-existence for network management
operations when the device is provisioned under the Secure Flow. ®
• IPCablecom 1.5 embedded-MTA provisioning minimizes the impact to DOCSIS devices (CM and CMTS) in
the network.
• Standard server solutions (TFTP, SNMP, DNS, etc.) are preferable. It is understood that an application layer
may be required on top of these protocols to coordinate IPCablecom 1.5 embedded-MTA provisioning. ®
• Where appropriate, the DOCSIS management protocols are supported (for example SNMP).
5.3 IPCablecom Reference Architecture
Figure 2 shows the reference architecture for the IPCablecom 1.5 Network. Refer to the IPCablecom Architecture
Specification [i.2] for more detailed information on this reference architecture.
ETSI
...