1、 International Telecommunication Union ITU-T J.170TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2005) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom security specification Recommendation ITU-T J.170 Rec. ITU-T J.170 (
2、11/2005) i Recommendation ITU-T J.170 IPCablecom security specification Summary This Recommendation defines authentication, access control, signalling and media content integrity, confidentiality, and non-repudiation security services for each of the network element interfaces. IPCablecom security s
3、pans the entire IPCablecom architecture. The IPCablecom architectural framework Recommendation (ITU-T Rec. J.160) defines the overall IPCablecom architecture, as well as the system elements, interfaces, and functional requirements for the entire IPCablecom network. Source Recommendation ITU-T J.170
4、was approved on 29 November 2005 by ITU-T Study Group 9 (2005-2008) under Recommendation ITU-T A.8 procedures. ii Rec. ITU-T J.170 (11/2005) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communica
5、tion technologies (ICTs). 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 Wo
6、rld 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. I
7、n 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 reco
8、gnized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The w
9、ords “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility th
10、at 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 Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommenda
11、tion 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 Recommendation. However, implementers are cautioned that this may not represent the latest information and
12、are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T J.170 (11/2005) iii CONTENTS Page 1 Scope and
13、 introduction . 1 1.1 Scope 1 1.2 Introduction 1 2 References. 2 2.1 Normative references 2 2.2 Informative references 3 3 Terms and definitions . 4 4 Abbreviations, acronyms and conventions . 5 4.1 Abbreviations and acronyms 5 4.2 Conventions 8 5 Architectural overview of IPCablecom security. 9 5.1
14、 IPCablecom reference architecture . 9 5.2 Threats 13 5.3 Security architecture . 19 6 Security mechanisms 26 6.1 IPsec . 26 6.2 Internet Key Exchange (IKE) . 28 6.3 SNMPv3 . 30 6.4 Kerberos/PKINIT . 31 6.5 Kerberized key management 55 6.6 End-to-end security for RTP 76 6.7 End-to-end security for R
15、TCP 76 6.8 BPI+ 77 6.9 TLS . 78 7 Security profile . 80 7.1 Device and service provisioning 81 7.2 Quality of Service (QoS) signalling . 93 7.3 Billing system interfaces 95 7.4 Call signalling . 97 7.5 PSTN Gateway interface 104 7.6 Media stream 106 7.7 Audio Server services . 126 7.8 Electronic sur
16、veillance interfaces . 129 7.9 CMS provisioning 133 8 IPCablecom certificates 134 8.1 Generic structure 134 8.2 Certificate trust hierarchy . 135 iv Rec. ITU-T J.170 (11/2005) Page 9 Cryptographic algorithms . 145 9.1 AES . 145 9.2 DES . 145 9.3 Block termination . 146 9.4 RSA signature . 151 9.5 HM
17、AC-SHA-1 . 151 9.6 Key derivation 151 9.7 The MMH-MAC 152 9.8 Random number generation . 154 10 Physical security . 154 10.1 Protection for MTA key storage . 154 10.2 MTA key encapsulation . 157 11 Secure software upgrade . 157 Annex A Oakley groups 158 Annex B Kerberos Network Authentication Servic
18、e 159 Annex C PKINIT specification . 159 Appendix I IPCablecom administration guidelines and best practices . 160 I.1 Routine CMS service key refresh . 160 Appendix II Example of MMH algorithm implementation 161 Rec. ITU-T J.170 (11/2005) 1 Recommendation ITU-T J.170 IPCablecom security specificatio
19、n 1 Scope and introduction 1.1 Scope Authentication, access control, signalling and media content integrity, confidentiality, and non-repudiation security services must be provided as defined herein for each of the network element interfaces. IPCablecom security spans the entire IPCablecom architect
20、ure. The IPCablecom architectural framework Recommendation (ITU-T Rec. J.160) defines the overall IPCablecom architecture, as well as the system elements, interfaces, and functional requirements for the entire IPCablecom network. 1.2 Introduction 1.2.1 Goals This Recommendation describes the securit
21、y relationships between the elements on the IPCablecom network. The general goals of this IPCablecom network security Recommendation and any implementations that encompass the requirements defined herein should be: Secure network communications: The IPCablecom network security must define a security
22、 architecture, methods, algorithms and protocols that meet the stated security service requirement. All media packets and all sensitive signalling communication across the network must be safe from eavesdropping. Unauthorized message modification, insertion, deletion and replays anywhere in the netw
23、ork must be easily detectable and must not affect proper network operation. Reasonable cost: The IPCablecom network security must define security methods, algorithms and protocols that meet the stated security service requirements such that a reasonable implementation can be manifested with reasonab
24、le cost and implementation complexity. Network element interoperability: All of the security services for any of the IPCablecom network elements must interoperate with the security services for all of the other IPCablecom network elements. Multiple vendors may implement each of the IPCablecom networ
25、k elements as well as multiple vendors for a single IPCablecom network element. Extensibility: The IPCablecom security architecture, methods, algorithms and protocols must provide a framework into which new security methods and algorithms may be incorporated as necessary. 1.2.2 Assumptions The follo
26、wing assumptions are made relative to the current scope of the IPCablecom security Recommendation: Embedded Media Terminal Adaptors (MTAs) are within the current scope. Stand-alone MTAs will be addressed in later phases and security issues for stand-alone MTAs are thus for future study. Network Call
27、 Signalling (NCS) is the only call signalling method, on the access network, addressed in this Recommendation. This version of the IPCablecom security Recommendation specifies security for a single administrative domain and the communications between domains. 2 Rec. ITU-T J.170 (11/2005) Security fo
28、r chained RADIUS servers is not currently in the scope. This Recommendation also does not include requirements for associated security operational issues (e.g., site security), back-office or inter/intra back-office security, service authorization policies or secure database handling. Record Keeping
29、 Servers (RKS), Network Management Systems, File Transfer Protocol (FTP) servers and Dynamic Host Configuration Protocol (DHCP) servers are all considered to be unique to any service providers implementation and are beyond the scope of this Recommendation. 2 References 2.1 Normative references The f
30、ollowing ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this R
31、ecommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does
32、not give it, as a stand-alone document, the status of a Recommendation. Recommendation ITU-T J.112 (1998), Transmission systems for interactive cable television services. Recommendation ITU-T J.122 (2002), Second-generation transmission systems for interactive cable television services IP cable mode
33、ms. Recommendation ITU-T J.125 (2004), Link privacy for cable modem implementations. Recommendation ITU-T J.126 (2004), Embedded Cable Modem device specification. Recommendation ITU-T J.162 (2005), Network call signalling protocol for the delivery of time-critical services over cable television netw
34、orks using cable modems. Recommendation ITU-T J.166 (2005), IPCablecom Management Information Base (MIB) framework. Recommendation ITU-T J.167 (2005), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modem
35、s. Recommendation ITU-T X.509 (2000) | ISO/IEC 9594-8:2001, Information technology Open Systems Interconnection The Directory: Public-key and attribute certificate frameworks. Recommendation ITU-T X.690 (2002) | ISO/IEC 8825-1:2002, Information technology ASN.1 encoding rules: Specification of Basic
36、 Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications. IETF RFC 1890 (1996), RTP Profile for Audio and Video Conferences with Minimal Control. IETF RFC 2104 (1997), HMAC: Keyed-Hashing
37、for Message Authentication. IETF RFC 2246 (1999), The TLS Protocol Version 1.0. IETF RFC 2367 (1998), PF_KEY Key Management API, Version 2. IETF RFC 2401 (1998), Security Architecture for the Internet Protocol. Rec. ITU-T J.170 (11/2005) 3 IETF RFC 2403 (1998), The Use of HMAC-MD5-96 within ESP and
38、AH. IETF RFC 2404 (1998), The Use of HMAC-SHA-1-96 within ESP and AH. IETF RFC 2406 (1998), IP Encapsulating Security Payload (ESP). IETF RFC 2407 (1998), The Internet IP Security Domain of Interpretation for ISAKMP. IETF RFC 2409 (1998), The Internet Key Exchange (IKE). IETF RFC 2437 (1998), PKCS#1
39、: RSA Cryptography Specification Version 2.0. IETF RFC 2451 (1998), The ESP CBC-Mode Cipher Algorithms. IETF RFC 2459 (1999), Internet X.509 Public Key Infrastructure Certificate and CRL Profile. IETF RFC 2630 (1999), Cryptographic Message Syntax. IETF RFC 3261 (2002), SIP: Session Initiation Protoc
40、ol. IETF RFC 3412 (2002), Message Processing and Dispatching for the Simple Network Management Protocol (SNMP). IETF RFC 3414 (2002), User-based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3). IETF RFC 4120 (2005), The Kerberos Network Authentication Service (V
41、5). IETF RFC 4556 (2006), Public Key Cryptography for Initial Authentication in Kerberos (PKINIJ). FIPS PUB 81 (1980), DES Modes of Operation. FIPS PUB 180-1 (1995), Secure Hash Algorithm (SHS). FIPS PUB 197 (2001), Advanced Encryption Standard (AES). 2.2 Informative references Recommendation ITU-T
42、J.160 (2005), Architectural framework for the delivery of time-critical services over cable television networks using cable modems. Recommendation ITU-T J.161 (2001), Audio codec requirements for the provision of bidirectional audio service over cable television networks using cable modems. Recommen
43、dation ITU-T J.163 (2005), Dynamic quality of service for the provision of real-time services over cable television networks using cable modems. Recommendation ITU-T J.164 (2005), Event message requirements for the support of real-time services over cable television networks using cable modems. Reco
44、mmendation ITU-T J.171.x (2005), IPCablecom Trunking Gateway Control Protocol (TGCP). Recommendation ITU-T J.175 (2002), Audio server protocol. Recommendation ITU-T J.178 (2005), IPCablecom CMS to CMS signalling. FIPS PUB 140-1 (1994), Security Requirements for Cryptographic Modules. IETF RFC 1750 (
45、1994), Randomness Recommendations for Security. IETF RFC 2327 (1998), SDP: Session Description Protocol. IETF RFC 2782 (2000), A DNS RR for specifying the location of services (DNS SRV). 4 Rec. ITU-T J.170 (11/2005) IETF RFC 3268 (2002), Advanced Encryption Standard (AES) Ciphersuites for Transport
46、Layer Security (TLS). HALEVI S., KRAWCZYK H.: MMH: Software Message Authentication in the Gbit/Second Rates, Proceedings of the 4th Workshop on Fast Software Encryption, Vol. 1267 Springer-Verloag, pp. 172-189, 1970. KILIAN J., ROGAWAY P.: How to Protect DES Against Exhaustive Key Search, Edited ver
47、sion presented at Proceedings of Crypto 96, July 1997. SCHNEIER B.: Applied Cryptography, John Wiley also known as a MIC. MAC Media Access Control. It is a sublayer of the Data Link Layer. It normally runs directly over the physical layer. MD5 Message Digest 5 MG Media Gateway MGC Media Gateway Cont
48、roller MGCP Media Gateway Control Protocol MIB Management Information Base MMH Multilinear Modular Hash MSB Most Significant Bit MTA Media Terminal Adapter NCS Network Call Signalling NVRAM Non-Volatile Random Access Memory OID Object Identification OSS Operations Support Systems. The back-office so
49、ftware used for configuration, performance, fault, accounting, and security management. PKCS Public Key Cryptography Standards PKI Public Key Infrastructure. A process for issuing public key certificates, which includes standards, Certification Authorities, communication between authorities and protocols for managing certification processes. PKCROSS Utilizes PKINIT for establishing the inter-realm keys and associated inter-realm
