ITU-T J 168-2001 IPCablecom media terminal adapter (MTA) MIB requirements (Study Group 9)《IPCablecom媒体终端适配器(MTA)MIB要求 系列J 有线广播电视网络与电视和声音节目及其他媒介的传输》.pdf

《ITU-T J 168-2001 IPCablecom media terminal adapter (MTA) MIB requirements (Study Group 9)《IPCablecom媒体终端适配器(MTA)MIB要求 系列J 有线广播电视网络与电视和声音节目及其他媒介的传输》.pdf》由会员分享，可在线阅读，更多相关《ITU-T J 168-2001 IPCablecom media terminal adapter (MTA) MIB requirements (Study Group 9)《IPCablecom媒体终端适配器(MTA)MIB要求 系列J 有线广播电视网络与电视和声音节目及其他媒介的传输》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T J.168TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2001) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom media terminal adapter (MTA) MIB requirements ITU-T Recommendation J

2、.168 (Formerly CCITT Recommendation) ITU-T J-SERIES RECOMMENDATIONS CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS General Recommendations J.1J.9 General specifications for analogue sound-programme transmission J.10J.19 Performance characteristics of anal

3、ogue sound-programme circuits J.20J.29 Equipment and lines used for analogue sound-programme circuits J.30J.39 Digital encoders for analogue sound-programme signals J.40J.49 Digital transmission of sound-programme signals J.50J.59 Circuits for analogue television transmission J.60J.69 Analogue telev

4、ision transmission over metallic lines and interconnection with radio-relay links J.70J.79 Digital transmission of television signals J.80J.89 Ancillary digital services for television transmission J.90J.99 Operational requirements and methods for television transmission J.100J.109 Interactive syste

5、ms for digital television distribution J.110J.129 Transport of MPEG-2 signals on packetised networks J.130J.139 Measurement of the quality of service J.140J.149 Digital television distribution through local subscriber networks J.150J.159 IPCablecom J.160J.179 Miscellaneous J.180J.199 Application for

6、 Interactive Digital Television J.200J.209 For further details, please refer to the list of ITU-T Recommendations. ITU-T J.168 (03/2001) i ITU-T Recommendation J.168 IPCablecom media terminal adapter (MTA) MIB requirements Summary This Recommendation describes IPCablecoms Media Terminal Adapter (MTA

7、) MIB requirements. Source ITU-T Recommendation J.168 was prepared by ITU-T Study Group 9 (2001-2004) and approved under the WTSA Resolution 1 procedure on 9 March 2001. ii ITU-T J.168 (03/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the

8、field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The

9、 World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1

10、. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a r

11、ecognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed

12、 Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommend

13、ation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2002 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechan

14、ical, including photocopying and microfilm, without permission in writing from ITU. ITU-T J.168 (03/2001) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative references. 1 3 Terms and definitions 2 4 Abbreviations 2 5 Requirements 2 ITU-T J.168 (03/2001) 1 ITU-T Re

15、commendation J.168 IPCablecom media terminal adapter (MTA) MIB requirements 1 Scope This Recommendation describes IPCablecom MTA MIB requirement. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of t

16、his Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revisions; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations an

17、d other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. 2.1 Normative references ITU-T J.162 (2001), Network call signalling protocol for the delivery of time-critical services over cable television networks using cable modems. ITU-T J.166 (2001),

18、 IPCablecom management information base (MIB) framework. ITU-T J.167 (2001), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems. ITU-T J.170 (Draft), IPCablecom security specification. ITU-T X.680 (19

19、97), Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.681 (1997), Information technology Abstract Syntax Notation One (ASN.1): Information object specification. ITU-T X.682 (1997), Information technology Abstract Syntax Notation One (ASN.1): Const

20、raint specification. ITU-T X.683 (1997), Information technology Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications. ITU-T X.690 (1997), Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguish

21、ed Encoding Rules (DER). 2.2 Informative references ITU-T J.160 (Draft), Architectural framework for the delivery of time-critical services over cable television networks using cable modems. IETF RFC 2571 (1999), An Architecture for Describing SNMP Management Frameworks. IETF RFC 2572 (1999), Messag

22、e Processing and Dispatching for the Simple Network Management Protocol. IETF RFC 2573 (1999), SNMP Applications. IETF RFC 2574 (1999), User-based Security Model (USM) for version 3 of the Simple Network ManagementProtocol (SNMPv3). 2 ITU-T J.168 (03/2001) 3 Terms and definitions This Recommendation

23、 defines the following terms: 3.1 cable modem: A cable modem is a layer-two termination device that terminates the customer end of the J.112 connection. 3.2 IPCablecom: An ITU-T project that includes an architecture and a series of Recommendations that enable the delivery of real time services (such

24、 as telephony) over the cable television networks using Cable Modems. 3.3 Management Information Base (MIB): the specification of information in a manner that allows standard access through a network management protocol. 3.4 MUST: The term “MUST“ or “MUST NOT“ is used as a convention in the present

25、Recommendation to denote an absolutely mandatory aspect of this Recommendation. 4 Abbreviations This Recommendation uses the following abbreviations: MIB Management Information Base MTA Media Terminal Adaptor 5 Requirements This clause defines the mandatory syntax of the IPCablecom MTA MIB. It follo

26、ws the IETF Simple Network Management Protocol (SNMP) for defining the managed objects. The MIB is organized as follows: MTA device objects; MTA security objects; objects used for initial provisioning and bootstrapping; objects used for event reporting to syslog, trap, local local The syntax is give

27、n below. PKTC-MTA-MIB DEFINITIONS := BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,Integer32,Unsigned32,Counter32,NOTIFICATION-TYPEFROM SNMPv2-SMITruthValue, DisplayString, DateAndTime, RowStatusFROM SNMPv2-TCOBJECT-GROUP,MODULE-COMPLIANCEFROM SNMPv2-CONFclabProjIPCablecomFROM CLAB-DEF-MIBifIndexFROM IF-M

28、IBdocsDevSwCurrentVersFROM DOCS-CABLE-DEVICE-MIB; - version 8ITU-T J.168 (03/2001) 3 pktcMtaMib MODULE-IDENTITYLAST-UPDATED “9912010000Z“ - December 1, 1999ORGANIZATION “IPCablecom OSS Group“CONTACT-INFO“Roy SpitzerPostal: Telogy Networks, Inc.20250 Century Blvd.Germantown, MD 20855U.S.A.Phone: +1 3

29、01-515-6531Fax: +1 301-515-7954E-mail: “DESCRIPTION“This MIB module supplies the basic management objectsfor the MTA Device.“:= clabProjPacketCable 1 - Textual conventionsX509Certificate := TEXTUAL-CONVENTIONSTATUS currentDESCRIPTION“An X509 digital certificate encoded as an ASN.1 DERobject.“SYNTAX

30、OCTET STRING (SIZE (04096)- IPCablecom supports embedded MTA only- IPCablecom requires SNMPv3-pktcMtaMibObjects OBJECT IDENTIFIER := pktcMtaMib 1 pktcMtaDevBase OBJECT IDENTIFIER := pktcMtaMibObjects 1 pktcMtaDevServer OBJECT IDENTIFIER := pktcMtaMibObjects 2 pktcMtaDevSecurity OBJECT IDENTIFIER :=

31、pktcMtaMibObjects 3 pktcMtaDevEvent OBJECT IDENTIFIER := pktcMtaMibObjects 4 - The following group describes the base objects in the MTA-pktcMtaDevResetNow OBJECT-TYPESYNTAX TruthValueMAX-ACCESS read-writeSTATUS currentDESCRIPTION“Setting this object to true(1) causes the device to reset.Reading thi

32、s object always returns false(2).“:= pktcMtaDevBase 1 pktcMtaDevSerialNumber OBJECT-TYPESYNTAX DisplayString (SIZE (0128)MAX-ACCESS read-onlySTATUS currentDESCRIPTION“The manufacturers serial number for this MTA.“:= pktcMtaDevBase 2 4 ITU-T J.168 (03/2001) pktcMtaDevHardwareVersion OBJECT-TYPESYNTAX

33、 DisplayString (SIZE (048)MAX-ACCESS read-onlySTATUS currentDESCRIPTION“The manufacturers hardware version for this MTA.“:= pktcMtaDevBase 3 pktcMtaDevMacAddress OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION“The telephony MAC address for this device.“:= pktcMtaDevBase 4

34、 pktcMtaDevFQDN OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-writeSTATUS currentDESCRIPTION“The Fully Qualified Domain Name for this MTA.“:= pktcMtaDevBase 5 pktcMtaDevEndPntCount OBJECT-TYPESYNTAX INTEGER (1255)MAX-ACCESS read-onlySTATUS currentDESCRIPTION“The physical end points for this MTA.“:=

35、 pktcMtaDevBase 6 pktcMtaDevEnabled OBJECT-TYPESYNTAX TruthValueMAX-ACCESS read-writeSTATUS currentDESCRIPTION“The MTA Admin Status of this device, where True(1) meansthe voice feature is enabled and false(2) indicates thatit is disabled.“:= pktcMtaDevBase 7 pktcMtaDevTypeIdentifier OBJECT-TYPESYNTA

36、X DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION“This is a copy of the device type identifier used in theDHCP option 60 exchanged between the MTA and the DHCP server.“:= pktcMtaDevBase 8 pktcMtaDevProvisioningState OBJECT-TYPESYNTAX INTEGERpass(1),inProgress(2),fail(3)MAX-ACCESS read-onl

37、ySTATUS currentITU-T J.168 (03/2001) 5 DESCRIPTION“This object indicates the completion state of theprovisioning process. Pass or Fail states occur after processingof the config file is completed. InProgress occurs from boottime until config file processing is complete. Fail state requiresmanual int

38、ervention.“:= pktcMtaDevBase 9 pktcMtaDevHttpAccess OBJECT-TYPESYNTAX TruthValueMAX-ACCESS read-onlySTATUS currentDESCRIPTION“This indicates whether HTTP file access is supported forMTA configuration file transfer.“:= pktcMtaDevBase 10 - The following group describes the security objects in the MTA-

39、pktcMtaDevManufacturerCertificate OBJECT-TYPESYNTAX X509CertificateMAX-ACCESS read-onlySTATUS currentDESCRIPTION“ASN.1 DER encoding of the MTA Manufacturers X.509 public-keycertificate, called MTA Manufacturer Certificate. It is issued to eachMTA manufacturer and is installed into each MTA either in

40、 the factoryor with a code download. The provisioning server cannot update thiscertificate.“:= pktcMtaDevSecurity 1 pktcMtaDevCertificate OBJECT-TYPESYNTAX X509CertificateMAX-ACCESS read-onlySTATUS currentDESCRIPTION“ASN.1 DER encoding of the MTAs X.509 public-key certificateissued by the manufactur

41、er and installed into the embedded-MTA inthe factory. This certificate, called MTA Device Certificate, containsthe MTAs MAC address. It cannot be updated by the provisioningserver.“:= pktcMtaDevSecurity 2 pktcMtaDevSignature OBJECT-TYPESYNTAX OCTET STRING (SIZE (0256)MAX-ACCESS read-onlySTATUS curre

42、ntDESCRIPTION“A unique signature created by the MTA for each SNMP Informor SNMP Trap or SNMP GetResponse message exchanged prior toenabling SNMPv3 security ASN.1 encoded Digital signature inthe Cryptographic message syntax (includes nonce).“:= pktcMtaDevSecurity 3 6 ITU-T J.168 (03/2001) pktcMtaDevC

43、orrelationId OBJECT-TYPESYNTAX Integer32MAX-ACCESS read-onlySTATUS currentDESCRIPTION“Random value generated by the MTA for use in registrationauthorization. It is for use only in the MTA initializationmessages and for MTA configuration file download.“:= pktcMtaDevSecurity 4 pktcMtaDevSecurityTable

44、OBJECT-TYPESYNTAX SEQUENCE OF PktcMtaDevSecurityEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION“Contains per endpoint security information.“:= pktcMtaDevSecurity 5 pktcMtaDevSecurityEntry OBJECT-TYPESYNTAX PktcMtaDevSecurityEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION“List of secu

45、rity attributes for a single IPCablecomendpoint interface associated with ifType(104).“INDEX ifIndex := pktcMtaDevSecurityTable 1 PktcMtaDevSecurityEntry := SEQUENCE pktcMtaDevServProviderCertificate OCTET STRING,pktcMtaDevTelephonyCertificate OCTET STRING,pktcMtaDevKerberosRealm OCTET STRING,pktcMt

46、aDevKerbPrincipalName DisplayString,pktcMtaDevServGracePeriod Integer32,pktcMtaDevLocalSystemCertificate OCTET STRING,pktcMtaDevKeyMgmtTimeout1 Integer32,pktcMtaDevKeyMgmtTimeout2 Integer32pktcMtaDevServProviderCertificate OBJECT-TYPESYNTAX X509CertificateMAX-ACCESS read-writeSTATUS currentDESCRIPTI

47、ON“ASN.1 DER encoding of the Telephony Service Providers X.509public-key certificate, called Service Provider Certificate. It servesas the root of the intra-domain trust hierarchy. Each MTA isconfigured with this certificate so that it can authenticate KDCsowned by the same service provider. The pro

48、visioning server needsthe ability to update this certificate in the MTAs via both SNMP andconfiguration files.“:= pktcMtaDevSecurityEntry 1 ITU-T J.168 (03/2001) 7 pktcMtaDevTelephonyCertificate OBJECT-TYPESYNTAX X509CertificateMAX-ACCESS read-writeSTATUS currentDESCRIPTION“ASN.1 DER encoding of the

49、 MTAs X.509 public-key certificateissued by the Service Provider with either the Service Provider CA ora Local System CA. This certificate, called MTA TelephonyCertificate, contains the same public key as the MTA DeviceCertificate issued by the manufacturer. It is used to authenticate theidentity of the MTA to the TGS (during PKINIT exchanges). Theprovisioning server needs the abil