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

Technical Specification
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)

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

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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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-7 V1.1.1 (2011-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions, symbols and abbreviations . 7
4 Void . 7
5 Requirements . 7
Annex A (informative): Bibliography . 31
History . 32

ETSI
4 ETSI TS 103 161-7 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 7 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";
ETSI
5 ETSI TS 103 161-7 V1.1.1 (2011-10)
Part 20: "Management Event MIB Specification";
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
6 ETSI TS 103 161-7 V1.1.1 (2011-10)
1 Scope
The present document describes the IPCablecom 1.5 MTA MIB requirement.
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 not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[1] IETF RFC 2132 (1997): "DHCP Options and BOOTP Vendor Extensions".
[2] IETF RFC 2616 (1999): "Hypertext Transfer Protocol -- HTTP/1.1".
[3] IETF RFC 3617 (2003): "Uniform Resource Identifier (URI) Scheme and Applicability Statement
for the Trivial File Transfer Protocol (TFTP)".
[4] IETF RFC 3495 (2003): "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs,
Client Configuration".
[5] ETSI TS 103 161-11: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 11: Media Terminal Adapter
(MTA) device provisioning".
[6] ETSI TS 103 161-9: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 9: Security".
[7] ETSI ES 202 488-2: "Access and Terminals (AT); Second Generation Transmission Systems for
Interactive Cable Television Services - IP Cable Modems; Part 2: Radio frequency interface
specification".
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.
Not applicable.
ETSI
7 ETSI TS 103 161-7 V1.1.1 (2011-10)
3 Definitions, symbols and abbreviations
Void.
4 Void
5 Requirements
The IPCablecom MTA MIB must be implemented as defined below, using these references, [1], [2], [3], [4], [5], [6],
and [7].
PKTC-MTA-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Integer32, Counter32,
BITS,IpAddress, NOTIFICATION-TYPE     FROM SNMPv2-SMI
TruthValue, RowStatus, DisplayString,
MacAddress, TEXTUAL-CONVENTION      FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE,
NOTIFICATION-GROUP            FROM SNMPv2-CONF
clabProjPacketCable            FROM CLAB-DEF-MIB
ifIndex                  FROM IF-MIB
SnmpAdminString              FROM SNMP-FRAMEWORK-MIB
sysDescr                 FROM SNMPv2-MIB;

pktcMtaMib MODULE-IDENTITY
LAST-UPDATED  "200501280000Z" -- January 28, 2005
ORGANIZATION  "Packet Cable OSS Group"
CONTACT-INFO
"Sumanth Channabasappa
Postal: Cable Television Laboratories, Inc.
858 Coal Creek Circle
Louisville, Colorado 80027-9750
U.S.A.
Phone: +1 303-661-9100
Fax:  +1 303-661-9199
E-mail: mibs@cablelabs.com"
DESCRIPTION
"This MIB module supplies the basic management objects
for the MTA Device
Acknowledgements:
Angela Lyda      -   Arris Interactive
Chris Melle      -   AT&T Broadband Labs
Sasha Medvinsky    -   Motorola
Roy Spitzer      -   Telogy Networks, Inc.
Rick Vetter      -   Motorola
Eugene Nechamkin   -   BroadCom Corp.
Satish Kumar     -   Texas Instruments
Copyright 1999-2005 Cable Television Laboratories, Inc.
All rights reserved."
REVISION "200501280000Z "
DESCRIPTION
"This revision, published as part of the PacketCable 1.5
MIB MTA Specification I01."
::= { clabProjPacketCable 1 }

-- Textual conventions
X509Certificate ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An X509 digital certificate encoded as an ASN.1 DER object."
SYNTAX OCTET STRING (SIZE (0.4096))
--
-- PacketCable 1.5 only supports Embedded MTAs
--
ETSI
8 ETSI TS 103 161-7 V1.1.1 (2011-10)
--=====================================================================
--
-- The MTA MIB only supports a single provisioning server.
--
--=====================================================================

pktcMtaMibObjects    OBJECT IDENTIFIER ::= { pktcMtaMib 1 }
pktcMtaDevBase     OBJECT IDENTIFIER ::= { pktcMtaMibObjects 1 }
pktcMtaDevServer    OBJECT IDENTIFIER ::= { pktcMtaMibObjects 2 }
pktcMtaDevSecurity   OBJECT IDENTIFIER ::= { pktcMtaMibObjects 3 }

--
-- The following group describes the base objects in the MTA
--
pktcMtaDevResetNow OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"Setting this object to true(1) causes the device to reset.
Reading this object always returns false(2). When
pktcMtaDevResetNow is set to true, the following actions
occur:
1. All connections (if present) are flushed locally
2. All current actions such as ringing immediately
terminate
3. Requests for notifications such as notification based
on digit map recognition are flushed
4. All endpoints are disabled.
5. The provisioning flow is started at step MTA - 1."
::= { pktcMtaDevBase 1 }
pktcMtaDevSerialNumber OBJECT-TYPE
SYNTAX   SnmpAdminString(SIZE (0.128))
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object specifies the manufacturer's serial number
for this MTA. The value of this object must be identical
to the value specified in DHCP option 43 sub-option 4. "
REFERENCE
"PacketCable MTA Device Provisioning Specification;
RFC 2132, DHCP Options and BOOTP Vendor Extensions"
::= { pktcMtaDevBase 2 }
pktcMtaDevHardwareVersion OBJECT-TYPE
SYNTAX   SnmpAdminString(SIZE (0.48))
MAX-ACCESS read-only
STATUS   obsolete
DESCRIPTION
"The manufacturer's hardware version for this MTA."
::= { pktcMtaDevBase 3 }
pktcMtaDevMacAddress  OBJECT-TYPE
SYNTAX   MacAddress
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object specifies the telephony MAC address for
this device. The value of this object must be identical
to the value specified in DHCP option 43 sub-option 11. "
REFERENCE
"PacketCable MTA Device Provisioning Specification;
RFC 2132, DHCP Options and BOOTP Vendor Extensions"
::= { pktcMtaDevBase 4 }
pktcMtaDevFQDN    OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"The Fully Qualified Domain Name for this MTA."
::= { pktcMtaDevBase 5 }
pktcMtaDevEndPntCount   OBJECT-TYPE
SYNTAX    Integer32 (1.255)
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
ETSI
9 ETSI TS 103 161-7 V1.1.1 (2011-10)
"The physical end points for this MTA."
::= { pktcMtaDevBase 6 }
pktcMtaDevEnabled   OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object contains the MTA Admin Status of this device.
If this object is set to 'true', the MTA is
administratively enabled and the MTA must be able to
interact with PacketCable entities such as CMS,
Provisioning Server, KDC, other MTAs and MGs on all
PacketCable interfaces.
If this object is set to 'false', the MTA is
administratively disabled and the MTA must perform the
following actions for all endpoints:
- Shutdown all media sessions if present,
- Shutdown NCS signaling by following the Restart in
Progress procedures in the PacketCable NCS
specification.
Additionally, the MTA must maintain the SNMP Interface for
management. Also, the MTA must not continue Kerberized Key
Management with CMSes until this object is set to 'true'.
Note: MTAs must renew the CMS kerberos tickets according
to the PacketCable Security Specification"
REFERENCE
"PacketCable Security Specification;
PacketCable MTA Device Provisioning Specification"
::= { pktcMtaDevBase 7 }
pktcMtaDevTypeIdentifier   OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This is a copy of the device type identifier used in the
DHCP option 60 exchanged between the MTA and the DHCP
server."
::= { pktcMtaDevBase 8 }
pktcMtaDevProvisioningState   OBJECT-TYPE
SYNTAX   INTEGER {
pass           (1),
inProgress        (2),
failConfigFileError    (3),
passWithWarnings     (4),
passWithIncompleteParsing (5),
failureInternalError   (6),
failOtherReason      (7)
}
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object indicates the completion state of the
MTA device provisioning process.

pass:
If the configuration file could be parsed successfully
and the MTA is able to reflect the same in its
MIB, the MTA must return the value 'pass'.

inProgress:
If the MTA is in the process of being provisioned,
the MTA must return the value 'inProgress'.

failConfigFileError:
If the configuration file was in error due to incorrect
values in the mandatory parameters, the MTA must reject
the configuration file and the MTA must return the value
'failConfigFileError'.
ETSI
10 ETSI TS 103 161-7 V1.1.1 (2011-10)
passWithWarnings:
If the configuration file had proper values for all the
mandatory parameters but has errors in any of the optional
parameters (this includes any vendor specific OIDs which
are incorrect or not known to the MTA), the MTA must
return the value 'passWithWarnings'.

passWithIncompleteParsing:
If the configuration file is valid, but the MTA cannot
reflect the same in its configuration (for example, too
many entries caused memory exhaustion), it must accept
the CMS configuration entries related and the MTA must
return the value 'passWithIncompleteParsing'.

failureInternalError:
If the configuration file cannot be parsed due to an
internal error, the MTA must return the value
'failureInternalError'.
failureOtherReason:
If the MTA cannot accept the configuration file for any
other reason than the ones stated above, the MTA must
return the value 'failureOtherReason'.

When a final SNMP INFORM is sent as part of Step 25 of
the MTA Provisioning process, this parameter is also
included in the final INFORM message."
REFERENCE
"PacketCable MTA Device Provisioning Specification"
::= { pktcMtaDevBase 9 }
pktcMtaDevHttpAccess   OBJECT-TYPE
SYNTAX   TruthValue
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This indicates whether HTTP file access is supported for
MTA configuration file transfer."
::= { pktcMtaDevBase 10 }
pktcMtaDevProvisioningTimer OBJECT-TYPE
SYNTAX   Integer32 (0.30)
UNITS    "minutes"
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object defines the time interval for the
provisioning flow to complete. The MTA must finish
all provisioning operations starting from the moment when
an MTA receives its DHCP ACK and ending at the moment when
the MTA downloads its configuration file (e.g., MTA5 to
MTA23 for Secure Flow) within the period of time set by
this object. Failure to comply with this condition
constitutes the provisioning flow failure. If the
object is set to 0, the MTA must ignore the provisioning
timer condition."
REFERENCE
"PacketCable MTA Device Provisioning Specification."
DEFVAL { 10 }
::= { pktcMtaDevBase 11 }
pktcMtaDevProvisioningCounter OBJECT-TYPE
SYNTAX   Counter32
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object is the count of the number of times the
provisioning cycle has looped through step MTA-1 since
the last reboot."
::= { pktcMtaDevBase 12 }
--
pktcMtaDevErrorOidsTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcMtaDevErrorOidsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"If pktcMtaDevProvisioningState is reported with anything
other than a pass(1) then this table is populated with the
ETSI
11 ETSI TS 103 161-7 V1.1.1 (2011-10)
necessary information, each pertaining to observations of
the configuration file. Even if different parameters
share the same error ( Ex: All Realm Names are invalid ),
all recognized errors must be reported as different
instances."
::= { pktcMtaDevBase 13 }
pktcMtaDevErrorOidsEntry OBJECT-TYPE
SYNTAX PktcMtaDevErrorOidsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This contains the necessary information an MTA must
attempt to provide in case the configuration file
is not parsed and/or accepted in its entirety."
INDEX { pktcMtaDevErrorOidIndex }
::= { pktcMtaDevErrorOidsTable 1 }

PktcMtaDevErrorOidsEntry ::= SEQUENCE {
pktcMtaDevErrorOidIndex      Integer32,
pktcMtaDevErrorOid        SnmpAdminString,
pktcMtaDevErrorGiven       SnmpAdminString,
pktcMtaDevErrorReason       SnmpAdminString
}
pktcMtaDevErrorOidIndex OBJECT-TYPE
SYNTAX Integer32(1.1024)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index to pktcMtaDevErrorOidsEntry.
This is an integer value and will start from the value 1
and be incremented for each error encountered in the
configuration file. The indices need not necessarily
reflect the order of error occurrences in the
configuration file."
::= { pktcMtaDevErrorOidsEntry 1 }

pktcMtaDevErrorOid OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This is the OID associated with the particular error. If
the error was not due to an identifiable OID, then this
can be populated with impartial identifiers, in hexadecimal
or numeric format."
::= { pktcMtaDevErrorOidsEntry 2 }

pktcMtaDevErrorGiven OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"If the error was due to the value associated
with the corresponding pktcMtaDevErrorOid, then this
contains the value of the OID as interpreted by the MTA in
the configuration file provided. If the error was not due
to the value of an OID this must be set to an empty
string. This is provided to eliminate errors due to
misrepresentation/misinterpretation of data."
::= { pktcMtaDevErrorOidsEntry 3 }

pktcMtaDevErrorReason OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This indicates the reason for the error,
as per the MTAs interpretation, in human readable form.
Example include:
VALUE NOT IN RANGE,
VALUE DOES NOT MATCH TYPE
UNSUPPORTED VALUE
LAST 4 BITS must BE SET TO ZERO,
OUT OF MEMORY, CANNOT STORE etc.
This MAY also contain vendor specific errors
for vendor specific OIDS and any proprietary error
ETSI
12 ETSI TS 103 161-7 V1.1.1 (2011-10)
codes/messages which can help diagnose errors
better, in a manner the vendor deems fit."
::= { pktcMtaDevErrorOidsEntry 4 }

pktcMtaDevSwCurrentVers OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the software version currently
operating in the MTA.
The MTA must return a string descriptive of the current
software load. This object should use the syntax defined
by the individual vendor to identify the software version.
The data presented in this object must be identical with
the software version information contained in the sysDescr
MIB Object of the MTA.
The value of this object must be identical to the value
specified in DHCP option 43 sub-option 6."
REFERENCE
"PacketCable MTA Device Provisioning Specification;
RFC 2132, DHCP Options and BOOTP Vendor Extensions"
::= { pktcMtaDevBase 14 }
-- The following group describes server access and parameters used for
-- initial provisioning and bootstrapping.
--
--*********************************************************************
--***************************This object is obsolete*******************
--*********************************************************************

pktcMtaDevServerBootState OBJECT-TYPE
SYNTAX INTEGER {
operational         (1),
disabled           (2),
waitingForDhcpOffer     (3),
waitingForDhcpResponse    (4),
waitingForConfig       (5),
refusedByCmts        (6),
other            (7),
unknown           (8)
}
MAX-ACCESS read-only
STATUS   obsolete
DESCRIPTION
"If operational(1), the device has completed loading and
processing of configuration parameters and the CMTS has
completed the Registration exchange.
If disabled(2) then the device was administratively
disabled, possibly by being refused network access in the
configuration file.
If waitingForDhcpOffer(3) then a DHCP Discover has been
transmitted and no offer has yet been received.
If waitingForDhcpResponse(4) then a DHCP Request has been
transmitted and no response has yet been received.
If waitingForConfig(5) then a request to the config
parameter server has been made and no response received.
If refusedByCmts(6) then the Registration Request/Response
exchange with the CMTS failed. "
REFERENCE
"DOCSIS Radio Frequency Interface Specification"
::= { pktcMtaDevServer 1 }
--*********************************************************************
--***************************This object is obsolete*******************
--*********************************************************************

pktcMtaDevServerDhcp OBJECT-TYPE
SYNTAX   IpAddress
MAX-ACCESS read-only
STATUS   obsolete
DESCRIPTION
"The IP address of the DHCP server that assigned an IP
address to this device. Returns 0.0.0.0 if DHCP was not
used for IP address assignment."
::= { pktcMtaDevServer 2 }
--
pktcMtaDevServerDns1 OBJECT-TYPE
ETSI
13 ETSI TS 103 161-7 V1.1.1 (2011-10)
SYNTAX   IpAddress
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"The IP address of the primary DNS server to be used by the
MTA to resolve the FQDNs and IP addresses."
::= { pktcMtaDevServer 3 }
pktcMtaDevServerDns2 OBJECT-TYPE
SYNTAX   IpAddress
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"The IP address of the Secondary DNS server to be used by
the MTA to resolve the FQDNs and IP addresses. Contains
0.0.0.0 if there is no Secondary DNS server specified for the MTA
for the MTA under consideration."
::= { pktcMtaDevServer 4 }
pktcMtaDevConfigFile OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object specifies the MTA device configuration file
information, including the access method, the server
name and the configuration file name. The value of this
object is the Uniform Resource Locator (URL) of the
configuration file for TFTP or HTTP download.
If this object value is a TFTP URL, it must be formatted
as defined in RFC 3617.
If this object value is an HTTP URL, it must be formatted
as defined in RFC 2616.
If the MTA SNMP Enrollment mechanism is used, then the MTA
must download the file provided by the Provisioning Server
during provisioning via an SNMP SET on this object.
If the MTA SNMP Enrollment mechanism is not used, this
object must contain the URL value corresponding to the
'siaddr' and 'file' fields received in the DHCP ACK to
locate the configuration file:  the 'siaddr' & 'file'
fields represents the host and file of the TFTP URL.
In this case, the MTA must return an
'inconsistentValue' error in response to SNMP SET
operations. The MTA must return a zero-length string if
the server address (host part of the URL) is unknown."
REFERENCE
"RFC 3617, URI Scheme for TFTP; RFC 2616, HTTP 1.1"
::= { pktcMtaDevServer 5 }
pktcMtaDevSnmpEntity OBJECT-TYPE
SYNTAX   SnmpAdminString
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object contains the FQDN of the SNMP entity of the
Provisioning Server. When the MTA SNMP Enrollment
Mechanism is used, this object represents the server the
MTA communicates with, to receive the configuration file
URL from, and, to send the enrollment notification to.
The SNMP entity is also the destination entity for all
the provisioning notifications. It may be also used for
post-provisioning SNMP operations.
During the provisioning phase, this SNMP
entity FQDN is supplied to the MTA via the DHCP option 122
sub-option 3 as defined in RFC 3495."
REFERENCE
"PacketCable MTA Device Provisioning Specification;
RFC 3495, DHCP Option for CableLabs Client Configuration."
::= { pktcMtaDevServer 6 }
pktcMtaDevProvConfigHash OBJECT-TYPE
SYNTAX   OCTET STRING (SIZE(16|20))
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object contains the hash value of the contents of
the config file.
ETSI
14 ETSI TS 103 161-7 V1.1.1 (2011-10)
If the authentication algorithm is MD5, the length is 128
bits. If the authentication algorithm is SHA-1, the length
is 160 bits. The hash calculation must follow
the requirements defined in the PacketCable Security
specification.
When the MTA SNMP Enrollment mechanism is used, this
hash value is calculated and sent to the MTA prior
to sending the config file. This object value is then
provided by the Provisioning server via an SNMP
SET operation.
When the MTA SNMP Enrollment mechanism is not in use, the
hash value is provided in the configuration file itself
and it is also calculated by the MTA. This object value
must represent the hash value calculated by the MTA.
When the MTA SNMP Enrollment mechanism is not in use, the
MTA must reject all SNMP SET operations on this object and
return an 'inconsistentValue' error."
REFERENCE
"PacketCable MTA Device Provisioning Specification;
PacketCable Security Specification."
::= { pktcMtaDevServer 7 }
pktcMtaDevProvConfigKey OBJECT-TYPE
SYNTAX   OCTET STRING (SIZE(0|8))
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object contains the key used to encrypt/decrypt
the configuration file when secure SNMPv3 provisioning
is used.
It is sent to the MTA prior to sending the config file.
If the privacy algorithm is null, the length is 0. If
the privacy algorithm is DES, the length is 64 bits.
This object must not be used in non secure provisioning
mode.
In non secure provisioning modes, the MTA must return an
'inconsistentValue' in response to SNMP SET operations,
and, the MTA must return a 'genErr' error in response to
SNMP GET operations."
::= { pktcMtaDevServer 8 }
pktcMtaDevProvSolicitedKeyTimeout OBJECT-TYPE
SYNTAX   Integer32 (15.600)
UNITS    "seconds"
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"This object defines a Kerberos Key Management timer on the
MTA. It is the time period during which the MTA saves the
nonce and Server Kerberos Principal Identifier to match an
AP Request and its associated AP Reply response from the
Provisioning Server.
After the timeout has been exceeded, the client discards
this (nonce, Server Kerberos Principal Identifier) pair,
after which it will no longer accept a matching AP Reply.
This timer only applies when the Provisioning Server
initiated key management for SNMPv3 (with a
Wake Up message). This object should not be used in non
secure provisioning modes. In non secure provisioning
modes, the MTA must return an 'inconsistentValue' in
response to SNMP SET operations, and the MTA must
return a 'genErr' error in response to SNMP GET
operations."
DEFVAL { 120 }
::= { pktcMtaDevServer 9 }
--=====================================================================
--
-- Unsolicited Key Updates are based on an exponential backoff
-- mechanism with two timers for AS replies. The fast timers have a
-- maximum timer (pktcMtaDevProvUnsolicitedKeyMaxTimeout seconds) and
-- a nominal timer pktcMtaDevProvUnsolicitedKeyNomTimeout seconds)
-- from which the backoff timer determinations are made.
--
--=====================================================================

--=====================================================================
ETSI
15 ETSI TS 103 161-7 V1.1.1 (2011-10)
--
-- Timeouts for unsolicited key management updates are only pertinent
-- before the first SNMPv3 message is sent between the MTA and the
-- Provisioning server and before the configuration file is loaded.
--
--=====================================================================

pktcMtaDevProvUnsolicitedKeyMaxTimeout OBJECT-TYPE

SYNTAX    Integer32 (15.600)
UNITS    "seconds"
MAX-ACCESS  read-only
STATUS    current
DESCRIPTION
"This object defines the timeout value that applies to
an MTA-initiated AP-REQ/REP key management exchange with
the Provisioning Server in SNMPv3 provisioning.
It is the maximum timeout value and it may not be exceeded
in the exponential back-off algorithm. If the DHCP option
code 122 sub-option 5 is provided to the MTA, it overwrites
this value.
In non secure provisioning mode, the MTA must return
a 'genErr' error in response to SNMP GET operations."
REFERENCE
"PacketCable Security Specification"
DEFVAL {600}
::= { pktcMtaDevServer 10 }
pktcMtaDevProvUnsolicitedKeyNomTimeout OBJECT-TYPE
SYNTAX    Integer32 (15.600)
UNITS    "seconds"
MAX-ACCESS  read-only
STATUS    current
DESCRIPTION
"This object defines the starting value of the timeout
for the AP-REQ/REP Backoff and Retry mechanism
with exponential timeout in SNMPv3 provisioning.
If the DHCP option code 122 sub-option 5 is provided
the MTA, it overwrites this value.
In non secure provisioning mode, the MTA must return
a 'genErr' error in response to SNMP GET operations."
REFERENCE
"PacketCable Security Specification"
DEFVAL {30}
::= { pktcMtaDevServer 11 }
pktcMtaDevProvUnsolicitedKeyMeanDev OBJECT-TYPE
SYNTAX   Integer32 (15.600)
UNITS    "seconds"
MAX-ACCESS read-only
STATUS   obsolete
DESCRIPTION
"This is the mean deviation for the round trip delay
timings."
REFERENCE
"PacketCable Security Specification"
::= { pktcMtaDevServer 12 }
pktcMtaDevProvUnsolicitedKeyMaxRetries OBJECT-TYPE

SYNTAX   Integer32 (1.32)
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"This object contains a retry counter that applies to
an MTA-initiated AP-REQ/REP key management exchange with
the Provisioning Server in secure SNMPv3 provisioning.
It is the maximum number of retries before the MTA stops
attempting to establish a Security Association with
Provisioning Server.
If the DHCP option code 122 sub-option 5 is provided to
the MTA, it overwrites this value.
In non secure provisioning mode, the MTA must return
a 'genErr' error in response to SNMP GET operations."
REFERENCE
"PacketCable Security Specification"
DEFVAL {8}
::= { pktcMtaDevServer 13 }
ETSI
16 ETSI TS 103 161-7 V1.1.1 (2011-10)

pktcMtaDevProvKerbRealmName OBJECT-TYPE
SYNTAX   SnmpAdminString (SIZE(1.255))
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"For Secure provisioning this object contains the name of
the associated provisioning Kerberos realm acquired during
the MTA4 provisioning step (DHCP Ack).
Additionally this object value is used as an index
into the pktcMtaDevRealmTable. In which case, the upper
case ASCII representation of the associated Kerberos realm
name must be used by both the Manager (SNMP entity)
and the MTA. The Kerberos realm name for the Provisioning
Server is supplied to the MTA via DHCP option code 122
sub-option 6 as defined in RFC 3495.
For non secure provisioning modes, the value of
this object must contain the value supplied in the DHCP
ACK message (option code 122 sub-option 6)."
REFERENCE
"PacketCable MTA Device Provisioning Specification;
RFC 3495, DHCP Option for CableLabs Client Configuration."
::= { pktcMtaDevServer 14 }
pktcMtaDevProvState OBJECT-TYPE
SYNTAX INTEGER {
operational         (1),
waitingForSnmpSetInfo    (2),
waitingForTftpAddrResponse (3),
waitingForConfigFile    (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object defines the MTA provisioning state.
If the state is:
'operational(1)', the device has completed the loading
and processing of the initialization parameters.

'waitingForSnmpSetInfo(2)', the device is waiting on
its configuration file download access information.
Note that this state is only reported when the MTA
SNMP enrollment mechanism is used.

'waitingForTftpAddrResponse(3)', the device has sent a
DNS request to resolve the server providing the
configuration file and it is awaiting for a response.
Note that this state is only reported when the MTA
SNMP enrollment mechanism is used.

'waitingForConfigFile(4)', the device has sent a
request via TFTP or HTTP for the download of its
configuration file and it is awaiting for a response or
the file download is in progress."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
PacketCable Security Specification"
::= { pktcMtaDevServer 15 }
pktcMtaDevServerDhcp1  OBJECT-TYPE
SYNTAX   IpAddress
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
"The IP address of the primary DHCP server which would cater to the
MTA during its provisioning. Contains 255.255.255.255 if
there was no preference given with respect to the DHCP
servers for MTAprovisioning."
::= { pktcMtaDevServer 16 }
pktcMtaDevServerDhcp2 OBJECT-TYPE
SYNTAX   IpAddress
MAX-ACCESS read-only
STATUS   current
DESCRIPTION   "The IP address of the Secondary DHCP server
which could cater to the MTA during its provisioning.
Contains 0.0.0.0 if there is no specific secondary DHCP
server to be considered during MTA    provisioning."
ETSI
17 ETSI TS 103 161-7 V1.1.1 (2011-10)
::= { pktcMtaDevServer 17 }
pktcMtaDevTimeServer  OBJECT-TYPE
SYNTAX   IpAddress
MAX-ACCESS read-write
STATUS   current
DESCRIPTION
"IP address of the Time Server from which to obtain the
time. Contains 0.0.0.0 if the Time Protocol is not used for
time synchronization."
::= { pktcMtaDevServer 18 }
--
-- The following group describes the security objects in the MTA
--
pktcMtaDevManufacturerCertificate OBJECT-TYPE
SYNTAX   X509Certificate
MAX-ACCESS read-only
STATUS   current
DESCRIPTION
" This object contains the MTA Manufacturer Certificate.
The object value must be the ASN.1 DER encoding of the MTA
manufacturer's X.509 public key certificate. The MTA
Manufacturer Certificate is issued to each MTA
manufacturer and is installed into each MTA at the time of
manufacture or with a secure code download. The specific
requirements related to this certificate are defin
...