hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.2.6 EoLT | If EoLT is included any deviations towards Annex C shall be transparently reported and motivated. For appropriate reporting format refer to Annex F, Table F.8. |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.2.3 LCI results | For LCI the following items shall be reported transparently: total use of primary energy, electricity, land use, and fresh water. NOTE: The Cumulative Energy Demand method is appropriate to express Primary Energy Usage. Additionally, results for elementary flows according to Annex E, Table E.1 could be transparently re... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.3 Network | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.3.1 Total result | For each environmental impact category studied, a diagram corresponding to Figure 12 shall be reported for the corresponding category indicator result. Operating lifetime is important also for Networks, but is associated with the lifetime of the different nodes, which shall be reported together in accordance with Annex... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.4 Services | |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 6.4.1 Total result | For each impact category studied, a diagram corresponding to Figures 14a or 14b shall be reported for the corresponding category indicator result. Operating lifetime is important also for Services, but it is associated with the lifetime of the different nodes, which shall be reported together in accordance with Table F... |
8bc4acbc9d988dc49eb399307393de04 | 103 199 | 7 Critical review | Any critical review shall be performed according to the requirements in ISO 14040 [1] and ISO 14044 [2] and in the present document. ETSI ETSI TS 103 199 V1.1.1 (2011-11) 46 Annex A (normative): Generic processes Table A.1 defines the generic processes (G1 to G7) to be included if applicable in LCAs for ICT Equipment, ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 config... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 ar... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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; P... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 16... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 3 Definitions and abbreviations | |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 net... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 Serv... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 4 Void | |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5 Background | |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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-... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 es... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 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 ETSI TS 103 161-11 V1.1.1 (2011-10) 14 Managed IP Network PSTN Call Management Server ( CMS ) Media Gateway Controller ( M... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4 Components and Interfaces | Figure 3 represents the components and interfaces discussed in the present document. DHCP Server Provisioning Server DNS Server SYSLOG Server MSO KDC TFTP or HTTP Server Embedded- MTA pkt-p1 pkt-p2 pkt-p3 pkt-p4 pkt-p5 pkt-p6 Figure 3: IPCablecom Provisioning Interfaces |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.1 MTA | The MTA must conform to the following requirements during the provisioning sequence. ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 15 |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.1.1 MTA Security Requirements | The MTA must conform to the following security requirements during the Secure Flow provisioning sequence: • The MTA device MIB is structured to represent the assignment of MTA endpoints to a CMS. For more information on the security association between an MTA and a CMS refer to [5]. • CMS Kerberos Principal Name is not... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.1.2 MTA SNMP Requirements | The MTA must conform to the following SNMPv3 requirements during the Secure Flow provisioning sequence: • MTA SNMPv3 security is separate and distinct from DOCSIS® SNMPv3 security. USM security information (authentication and privacy keys, and other USM table entries) is setup separately. • SNMPv3 initialization must b... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.2 Provisioning Server | The Provisioning Server is made up of the following components: • Provisioning Application - The Provisioning Application is responsible for coordinating the embedded-MTA provisioning process. This application has an associated SNMP Entity. ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 16 • Provisioning SNMP Entity - The pr... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.3 MTA to Telephony Syslog Server | The IPCablecom MTAs must implement Management Event Mechanism as per [14], which includes the support for Syslog server. The IPCablecom MTAs must also implement all the IPCablecom Provisioning Management Events described in Annex A of [14]. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.4 MTA to DHCP Server | This interface identifies specific requirements in the DHCP server and the client for IP assignment during the MTA initialization process. • Both the DHCP server and the embedded-MTA must support DHCP option code 6, 7, 12, 15, 43, 60 and DHCP option code 122 (defined in [11]). Option code 12 (Host Name) and 15 (Domain ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.5 MTA to Provisioning Application | This interface identifies specific requirements for the Provisioning Application to satisfy MTA initialization and registration. The Provisioning Application requirements are: • The MTA must generate a correlation ID - an arbitrary value that will be exchanged as part of the device capability data to the Provisioning A... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.6 MTA to CMS | Signalling is the main interface between the MTA and the CMS. Refer to the IPCablecom Signalling Specification [4] for a detailed description of the interface. The CMS must accept signalling and bearer channel requests from a MTA that has an active security association. The CMS must not accept signalling and bearer cha... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.7 MTA to Security Server (KDC) | The interface between the MTA and the Key Distribution Center (KDC) must conform to the IPCablecom Security Specification [5]. AP-REQ/REP exchange back off and retry mechanism of the Kerberized SNMPv3 key negotiation defined in [5] is controlled by the values delivered by DHCP Option 122 sub-option 5 (see clause 8.1.4)... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.8 MTA and Configuration Data File Access | The present document allows for more than one access method to download the configuration data file to the MTA. • The MTA must support the TFTP access method for downloading the MTA configuration data file. • The MTA may support HTTP access method for downloading the MTA configuration data file. • The Provisioning Serv... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 5.4.9 DOCSIS® extensions for MTA Provisioning | The present document requires that the following additions to DOCSIS® flows for MTA auto-provisioning be supported: • eCMs that can obtain IP configuration information from multiple DHCP servers must use the primary DHCP server - designated to provide the eCM configuration information - for obtaining IPCablecom specifi... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 6 Provisioning Overview | Provisioning is a subset of configuration management control. The provisioning aspects include, but are not limited to, defining configurable data attributes, managing defined attribute values, resource initialization and registration, managing resource software, and configuration data reporting. The resource (also ref... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 6.1 Device Provisioning | Device provisioning is the process by which an embedded-MTA device is configured to support voice communications service. Device provisioning involves the MTA obtaining its IP configuration required for basic network connectivity, announcing itself to the network, and downloading of its configuration data from its prov... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 6.2 Endpoint Provisioning | Endpoint provisioning is when a provisioned MTA authenticates itself to the CMS, and establishes a security association with that server. This allows subsequent call signalling to be protected under the established security association. The MTA must follow the requirements defined in the IPCablecom Security Specificati... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 6.3 Secure Flow Provisioning State Transitions | Figure 4 represents logical device states and the possible transitions across these logical states. This representation is for illustrative purposes only, and is not meant to imply a specific implementation. The following MTA state transitions do not specify the number of retry attempts or retry time out values. ETSI E... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 6.4 Basic and Hybrid Flow Provisioning State Transitions | Figure 5 represents logical device states and the possible transitions across these logical states. This representation is for illustrative purposes only, and is not meant to imply a specific implementation. The following MTA state transitions do not specify the number of retry attempts or retry time out values. ETSI E... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7 Provisioning Flows | An IPCablecom MTA is provisioned via one of three provisioning flows: • The Secure Flow supports Kerberos mutual authentication between the MTA and the provisioning system, as well as Kerberized SNMPv3 messaging. The Secure Flow must be supported by IPCablecom MTAs and the Provisioning Applications. • The Basic Flows a... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.1 Backoff, Retries, and Timeouts | Backoff mechanisms help the network to throttle device registration during a typical or mass registration condition when the MTA client requests are not serviced within the protocol specified timeout values. The details of provisioning behaviour under mass-registration is beyond the scope of IPCablecom 1.5, however thi... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.2 Embedded-MTA Power-On Initialization Flow (Secure Flow) | Following is the mandatory message flow that the embedded-MTA device must follow during power-on initialization (unless stated explicitly otherwise). It is understood that these flows do not imply implementation or limit functionality. Although these flows show the MTA configuration file download from a TFTP Server, th... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.2.1 Embedded-MTA Secure Power-on Initialization Flow (IPv4 eCM) | Flow CM / MTA CMTS DOCSIS DHCP DOCSIS TFTP DOCSIS ToD Prov Server PKT DHCP PKT DNS PKT TFTP MSO KDC SYSLOG Start w ith DOCSIS Initialization/Registration CM-1 DHCP Broadcast Discover (Request Option Code 122) CM-2 DHCP Offer (Option Code 122 w / telephony service provider's DHCP server address) CM-3 DHCP Request CM-4 D... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.2.2 Embedded-MTA Secure Power-on Initialization Flow (IPv6 eCM) | Flow CM / MTA CMTS DOCSIS DHCP DOCSIS TFTP DOCSIS ToD Prov Server PKT DHCP PKT DNS PKT TFTP MSO KDC SYSLOG Start w ith DOCSIS Initialization/Registration CM1v6 DHCPv6 SOLICIT (w /IPv6 CL Option Code CL_OPTION_ORO(1) w ith CL_OPTION_CCC) CM2v6 DHCPv6 ADVERTISE (w /DHCPv6 OPTION_VENDOR_OPTS(17) including the CL Option Co... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.3 Embedded-MTA Power-On Initialization Flow (Basic Flow) | The Basic MTA provisioning flow is very similar to the DOCSIS® CM provisioning flow Flow CM / MTA CMTS DOCSIS DHCP DOCSIS TFTP DOCSIS ToD Prov Server PKT DHCP PKT DNS PKT TFTP MSO KDC SYSLOG B-MTA-22 Telephony config file request B-MTA-23 Telephony config file B-MTA-24 MTA send telephony service provider SYSLOG a notif... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.4 Embedded-MTA Power-On Initialization Flow (Hybrid Flow). | The Hybrid Provisioning Flow (Hybrid Flow) is essentially the Secure Flow with Kerberos exchanges removed and SNMPv2c substituted for SNMPv3. The SNMPv2c community name, used in the SNMP INFORM messages sent by the MTA in steps H-MTA15 and H-MTA25 below, must have a value "private" (taken without the quotation marks). ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.5 Endpoint Provisioning Completion Notifications | After the MTA has been provisioned successfully regardless of the selected provisioning flow, the MTA will set up the necessary security association for the related CMS configured realms (KDCs). The MTA NCS signalling software will initiate the establishment of the IPsec security association to the configured CMS clust... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.6 Post Initialization Incremental Provisioning | This clause describes the flows allowing the Provisioning Application to perform incremental provisioning of individual voice communications endpoints after the MTA has been initialized. Post-Initialization incremental provisioning may involve communication with a Customer Service Representative (CSR). |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.6.1 Synchronization of Provisioning Attributes with Configuration File | Incremental provisioning includes adding, deleting and modifying subscriber services on one or more endpoints of the embedded-MTA. Services on an MTA endpoint must be modified using SNMP via the MTA MIB ([2] and [21]). The back office applications should support a "flow-through" provisioning mechanism that synchronizes... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.6.2 Adding/Enabling Telephony Services on an MTA Endpoint | The Telephony Services may be added and/or enabled on an MTA endpoint. Telephony Services may be added to MTA endpoints that have not been previously provisioned. Whenever such an MTA endpoint is added/enabled: • The MTA must have been provisioned with the 'device level' configuration data via the configuration file (a... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.6.3 Deleting/Disabling Telephony Services on an MTA Endpoint | Provisioned and enabled Telephony Services can be disabled (taken out of service) or deleted if required using SNMP via the MTA MIB ([2] and [21]), and the Signalling MIB ([15] and [22]), on a per-endpoint basis. Whenever a telephony service is desired to be deleted on an endpoint, the authorized SNMP Management Statio... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.6.4 Modifying Telephony Services on an MTA Endpoint | Telephony Services may be modified on a currently provisioned 'MTA Endpoint'. This is accomplished using SNMP via the MTA MIB ([2] and [21]), and the Signalling MIB ([3] and [22]) on a per-endpoint basis. If such a modification to an endpoint changes the CMS association (pktcNcsEndPntConfigCallAgentId) and/or the port ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.7 Reflecting the State of the Endpoint Interface in the ifTable | The operational state of each 'MTA Endpoint' is reflected in the "ifOperStatus" MIB Object of the MTA. This is influenced by the following conditions: • The corresponding administrative status for the endpoint, reflected in the "ifAdminStatus" table. • The state of the telephony service assigned to the corresponding en... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.9 MTA Replacement | IPCablecom 1.5 has no requirement to specify MTA replacement procedures. However, the provisioning sequence flows detailed within the present document provide sufficient coverage and flexibility to support replacement. In fact, the initialization sequence for a replacement MTA could be the same as the original MTA's fi... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.10 Temporary Signal Loss | If the eCM (in an E-MTA) resets due to any Rf condition (for example Temporary Rf loss), then the associated IPCablecom eMTA must also reset. NOTE This will impact calls in progress. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 7.11 MTA Hard Reboot/Soft Reset scenarios. | Hard Reboot is defined as a 'power cycle' of the entire E-MTA device. Soft Reset is defined as an 'SNMP reset' of the eMTA, an SNMP reset of the eCM, i.e. CM1 or CM1v6 (resulting in the reset of the associated eMTA) or an Rf condition that results in a reset of the eCM (resulting in the reset of the associated eMTA). T... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8 DHCP Options | DHCP ([1] and [20]) is used to obtain the IP configuration data for both the eCM and the eMTA. For IPv4 addressing mode, if the total number of octets in any DHCP option exceeds 255 octets, then the MTA must follow [10] to split the DHCP message in to multiple sub messages. ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 38 D... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1 DHCP Option 122: CableLabs® Client Configuration Option | DHCP option code 122 is the RFCed replacement for the former option 177 (which was intended as a temporary code). CM and MTA must not request option 177 in their DHCP DISCOVER or REQUEST message in option 55 (parameter request list). In the case that a CM or MTA requests both options 122 and 177: • The provisioning ser... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.1 Service Provider's DHCP Address (sub-option 1 and 2) | The Service Provider's DHCP Server Addresses identify the DHCP servers that a DHCP OFFER will be accepted from in order to obtain an MTA-unique IP address for a given service provider's network administrative domain. The encoding of these sub-options is defined in [26]. Sub-option 1 must be included in the DHCP OFFER/A... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.2 Service Provider's Provisioning Entity Address (sub-option 3) | The Service Provider's Provisioning Entity Address is the network address of the provisioning server for a given voice service provider's network administrative domain. The encoding of this sub-option is defined in [26]. This address must be configured as an FQDN only. An FQDN value of 0.0.0.0 in sub-option 3 of a vali... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.5 Kerberos Realm of SNMP Entity (sub-option 6) | In conjunction with the Provisioning Entity Address, the Kerberos Realm is used as a means of contacting a SNMP Entity in the provisioning realm. The realm name is used to perform a DNS SRV lookup for the realm's KDC. The DHCP option 122 sub-option 6 must be included in the DHCP OFFER to the MTA. For the Secure Flow, t... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.5.1 SNMPv3 Key Establishment | The SNMPv3 Key Establishment is applicable for Secure Flow only. The AP Request/AP Reply described in figure 6 the accompanying flow description, and the Security Specification are used by the MTA in the initial provisioning phase to establish keys with the SNMPv3 USM User "MTA-Prov-xx:xx:xx:xx:xx:xx". Where xx:xx:xx:x... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.6 Ticket Granting Server Usage (sub-option 7) | The MTA must use the DHCP option 122 sub option 7 if supplied for the provisioning kerberized key management in Secure Flow only. This sub-option contains a Boolean, which when true, indicates that the MTA should get its TGT (ticket granting ticket). Sub-option 7 may be included in the DHCP OFFER/ACK to the MTA. The en... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.7 Provisioning Timer (sub-option 8) | Sub-option 8 defines the value to be used for the provisioning timer. Sub-option 8 may be included in the DHCP OFFER/ACK to the MTA. The encoding of this sub-option is defined in [26]. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.1.8 Security Ticket Invalidation (sub-option 9) | Sub-option 9 contains a bit mask that directs the MTA to invalidate specific application server security tickets. Sub-option 9 may be included in the DHCP OFFER/ACK to the MTA. The encoding of this sub-option is defined in [i.8]. ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 42 |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.2 DHCP Option 60: Vendor Client Identifier | Option code 60 contains a string identifying Capabilities of the MTA. The MTA must send the following ASCII Coded String in DHCP Option code 60: "pktc1.5:xxxxxx". Where xxxxxx must be an ASCII representation of the hexadecimal encoding of the MTA TLV Encoded Capabilities, as defined in clause 10. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.3 DHCP Options 12 and 15 | MTA FQDN must be sent to the E-MTA in Option-12 and Option-15. Option-12 must contain "Host Name" part of the FQDN, and the Option-15 must contain "Domain Name" part of the FQDN. For example, if MTA FQDN is "mta1.pclab.com", then Option-12 will contain "mta1" and Option-15 will contain "pclab.com". |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.4 DHCP Option 6 | DHCP Option 6 must be used to provide the MTA with its list of DNS server addresses. Option 6 must contain at least one DNS server address. Option 6 may contain a secondary DNS server address. If this option contains more than two DNS servers, the MTA must use the first two addresses. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.5 DHCP Option 43 | The MTA must send the DHCP Option 43 in the DHCP DISCOVER and DHCP REQUEST for the Secure, Hybrid and Basic Flows. DHCP Option 43 contains the number of sub-options defined to provide the MTA device specific information to the back-office systems. The DHCP option 43 sub-options 1 through 10, 31 and 32 are specified by ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.6 DHCP OPTION 1 | DHCP Option 1 is defined in [11]. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 8.7 DHCP OPTION 3 | DHCP Option 3 is defined in [11]. 8.8 DHCP OPTION CL_V4_PACKETCABLE_MIB_ENV_OPTION The Provisioning Server can provide the option 'CL_V4_PACKETCABLE_MIB_ENV_OPTION' within the DHCP OFFER and ACK messages to indicate preference of the MIB module for MTAs implementing both the IPCablecom and IETF MIBs. The following requ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9 MTA Provisionable Attributes | This clause includes the list of attributes and their associated properties used in device provisioning. All of the provisionable attributes specified in this clause may be updated via the MTA configuration data file, or on a per-attribute basis using SNMP. IPCablecom 1.5 requires that a MTA configuration data file mus... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1 MTA Configuration File | This clause explains the format and contents of an MTA configuration file. This file contains a series of "type length and value" (TLV) parameters. Each TLV parameter in the configuration file describes an MTA or endpoint attribute. The configuration data file includes TLVs that have read-write, read only, and no MIB a... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.1 Device Level Configuration Data | Refer to the MTA MIB ([2] and [21]) for more detailed information concerning these attributes and their default values. • The MTA Manufacturer Certificate validates the MTA Device Certificate. Table 12 Attribute Syntax Configuration Access SNMP Access MIB File Object Comments Telephony Config File Start Integer W, requ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.2 Device Level Service Data | Refer to the MTA MIB ([2] and [21]) the SIGNALLING MIB ([3] and [22]) the NCS Call Signalling spec [4], and RFC 2475 [i.5] for more detailed information concerning these attributes and their default values. Table 13 Attribute Syntax Configuration Access SNMP Access MIB File Object pktcDevEvSysloComments NCS Default Cal... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.3 Per-Endpoint Configuration Data | Refer to the SIGNALLING MIB ([3] and [22]), the NCS spec [4], the security spec [5] and the MTA MIB ([2] and [21]) for more detailed information concerning these attributes and their default values. MTA sends KDC the MTA/CMS certificate, MTA's FQDN, CMS-ID. The KDC returns the MTA a "Kerberos Ticket" that says "this MT... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.4 Per-Realm Configuration Data | Refer to the MTA MIB ([2] and [21]) for more detailed information concerning these attributes and their default values. Refer to the Security spec [5] for more information on the use of Kerberos realms. There must be at least one conceptual row in the pktcMtaDevRealmTable to establish service upon completion of configu... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.5 Per-CMS Configuration Data | Refer to the MTA MIB ([2] and [21]) for more detailed information concerning these attributes and their default values. There must be at least one conceptual row in the pktcDevCmsTable to establish service upon completion of configuration. These configuration parameters are optional in the config file, but if included ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 9.1.6 Exclusion of MIB objects in configuration File | The following MIB objects must not be sent in the configuration file since the values of these object can be either set only by the MTA or by DHCP options during provisioning. If an MTA receives the following MIB objects in its configuration file, the MTA must ignore the object and report "passWithWarnings" and populat... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10 MTA Device Capabilities | MTA Capabilities string is supplied to the Provisioning Server in Option code 60 (Vendor Class Identifier) to allow the Back-Office to differentiate between MTAs during the Provisioning Process. Use of Capabilities information by the Provisioning Application is optional. ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 57 Capa... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.1 IPCablecom Version | This TLV of subtype 5.1 (IPCablecom Version) must be supplied in the Capabilities String. Type Length Values Comment Default Value 5.1 1 0 IPCablecom 1.0 NONE 1 IPCablecom 1.5 |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.2 Number Of Telephony Endpoints | This TLV of subtype 5.2 (Number of telephony Endpoints) must be supplied in the Capabilities String. Type Length Values Comment Default 5.2 1 n Number of endpoints NONE |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.3 TGT Support | Type Length Value Comment Default Value 5.3 1 0 0: No 0 1 1: Yes |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.4 HTTP Download File Access Method Support | Type Length Value Comment Default Value 5.4 1 0 0: No 0 1 1: Yes |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.5 MTA-24 Event SYSLOG Notification Support | Type Length Value Comment Default Value 5.5 1 0 0: No 1 1 1: Yes ETSI ETSI TS 103 161-11 V1.1.1 (2011-10) 58 |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.6 NCS Service Flow Support | Type Length Value Comment Default Value 5.6 1 Undefined Reserved for future use Undefined Sub Type 5.6 which was previously used to indicate support for NCS Service Flow functionality, is currently undefined and reserved for future usage. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.7 Primary Line Support | Type Length Value Comment Default Value 5.7 1 0 0: No 0 1 1: Yes |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.8 Vendor Specific TLV Type(s) | This TLV can be supplied in the Capabilities String if an MTA requires a specific processing of the Vendor Specific TLV Type(s). Type Length Value Comment Default Value 5.8 n {seq-of-bytes}: One type per byte 43 per byte Sub Type 5.8 which was previously used to indicate vendor specific TLV support by MTAs is currently... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 10.9 NVRAM Ticket/Ticket Information Storage Support | Type Length Value Comment Default Value 5.9 1 0 0: No 1 1 1: Yes 10.10 Provisioning Event Reporting Support Type Length Value Comment Default Value 5.10 1 0 0: No 1 1 1: Yes 10.11 Supported CODEC(s) This TLV must be supplied in the Capabilities String. Type Length Value Comment Default Value 5.11 n {seq-of-bytes} one I... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11 TLV-38 SNMP Notification Receiver Specification | This IPCablecom TLV 38 specifies one or more Network Management Stations that must receive notifications from the MTA (MTA25 or H-MTA25 or B-MTA25 and post-provisioning, if required). If TLV38 and its sub-TLVs defined in this clause contains incorrect value in 'Length' field, the MTA must reject the configuration file ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1 Sub-TLVs of TLV-38 | |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.1 SNMP Notification Receiver IP Address | This sub-TLV specifies the IP address of the notification receiver. Type Length Value 38.1 4 4 bytes of an IPv4 address in network byte order If TLV 38 is present in the configuration file and the sub-TLV 38.1 is absent, the MTA must ignore TLV-38 and proceed with further processing of the configuration file and must r... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.2 SNMP Notification Receiver UDP Port Number | This sub-TLV specifies the Port number on the notification receiver to receive the notifications. Type Length Value 38.2 2 UDP Port Number If TLV 38 is present and the sub-TLV 38.2 is absent, then a default value of 162 must be used. |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.3 SNMP Notification Receiver Type | This sub-TLV specifies the SNMP Notification Receiver Type; it is the type of SNMP notifications the MTA must send to the associated SNMP Notification Receiver. Type Length Value 38.3 2 1: SNMPv1 trap in an SNMPv1 packet 2: SNMP v2c trap in an SNMP v2c packet 3: SNMP INFORM in an SNMP v2c packet 4: SNMP trap in an SNMP... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.4 SNMP Notification Receiver Timeout | This sub-TLV specifies the wait time before a retry is attempted when the sender of an SNMP INFORM fails to receive an acknowledgement. Note that the number of retries is defined in sub-TLV 38.5. Type Length Value 38.4 2 Time in milliseconds If TLV 38 is present in the configuration file and the sub-TLV 38.4 is absent,... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.5 SNMP Notification Receiver Retries | This sub-TLV specifies the maximum number of times the MTA must retry sending an SNMP INFORM message if an acknowledgement is not received. Note that the wait time before each retry is defined by sub-TLV 38.4. Type Length Value 38.5 2 Number of retries If not present, the MTA must use a default value of 3. The maximum ... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.6 SNMP Notification Receiver Filtering Parameters | This sub-TLV specifies the filtering scheme for notifications and contains the root OID of the MIB sub-tree that defines the notifications to be sent to the Notification Receiver. The MTA must filter notifications being sent to the SNMP manager specified in sub-TLV 38.1 using the information provided. If this sub-TLV i... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.1.7 SNMPv3 Notification Receiver Security Name | This sub-TLV specifies the SNMPv3 Security Name to use when sending an SNMPv3 Notification. This sub-TLV is only being used if MTA supports TLV 38.3 (Notification Receiver Type) types 4 and 5. The MTA must ignore this sub-TLV 38.7 if a Notification Receiver Type (sub-TLV 38.3) other than 4 or 5 is received in the confi... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.2 Mapping of TLV fields into SNMP Tables | The following clauses detail the MTA configuration file TLV-38 "IPCablecom SNMP Notification Receiver" mapping onto SNMP functional tables. Upon receiving each TLV 38 value, the MTA must make entries to the following tables in order to cause the desired SNMP TRAP or INFORM transmission: snmpNotifyTable, snmpTargetAddrT... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.2.1 Mapping of TLV fields into created SNMP Table rows | The tables in this clause show how the fields from the Configuration file TLV element (the tags in angle brackets <>) are placed into the SNMP tables. The correspondence between the tags and the sub-TLVs themselves is as shown below: <IP Address> TLV 38.1 <Port> TLV 38.2 <Trap type> TLV 38.3 <Timeout> TLV 38.4 <Retries... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.2.1.1 snmpNotifyTable | If TLV38 elements are present and irrespective of the number of elements the MTA must create two rows with fixed values as described in table 17. Table 17: snmpNotifyTable snmpNotifyTable (RFC 3413 [7], SNMP-NOTIFICATION-MIB) First Row Second Row Column Name (* = Part of Index) Column Value Column Value * snmpNotifyNam... |
c5fafa22b9567003076494de2ee4736e | 103 161-11 | 11.2.1.2 snmpTargetAddrTable | For each TLV38 element in the configuration file, the MTA must create one row according to table 18. Table 18: snmpTargetAddrTable snmpTargetAddrTable (RFC 3413 [7], SNMP-TARGET-MIB) New Row Column Name (* = Part of Index) Column Value * snmpTargetAddrName "@mtaconfig_n" Where n ranges from 0 to m-1 where m is the numb... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.