1、 International Telecommunication Union ITU-T J.192TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2005) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Cable modems A residential gateway to support the delivery of cable data services ITU-T Re
2、commendation J.192 ITU-T Rec. J.192 (11/2005) i ITU-T Recommendation J.192 A residential gateway to support the delivery of cable data services Summary This Recommendation describes a Residential Gateway by providing a set of IP-based features that may be added to a Cable Modem or incorporated into
3、a standalone device. This will enable cable operators to provide an additional set of enhanced home network-based services to their customers including support for Quality of Service (QoS), device and service discovery, enhanced security, firewall management, home network focused management and prov
4、isioning features, managed network address translation, improved addressing and packet handling and LAN device diagnostics. This Recommendation is based upon the architectural frameworks defined in ITU-T Rec. J.190. This Recommendation represents an enhancement to ITU-T Rec. J.191, retaining a major
5、ity of J.191 functionality as a foundation, and building upon this base to provide additional advanced features. A key design goal for equipment conforming to this Recommendation is interoperability with equipment conforming to ITU-T Rec. J.191. For example, common MIBs are used for the foundational
6、 functionality. As a result, a J.192-based headend may manage a mixed J.191 and J.192 deployment. Source ITU-T Recommendation J.192 was approved on 29 November 2005 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.192 (11/2005) FOREWORD The Internation
7、al Telecommunication Union (ITU) is the United Nations specialized agency in the 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
8、on them with a view to standardizing telecommunications on a worldwide basis. The 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
9、 ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. 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
10、 used for conciseness to indicate both a telecommunication administration and a recognized 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 t
11、he Recommendation is achieved when all of these mandatory provisions are met. The words “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 o
12、f any party. 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 Intellectual P
13、roperty 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 Recommendation. However,
14、 implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2007 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T
15、 Rec. J.192 (11/2005) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 References (normative) 1 2.2 References (informative) 5 3 Definitions 6 4 Abbreviations and conventions. 6 4.1 Abbreviations . 6 4.2 Conventions 9 5 Reference architecture 10 5.1 Logical reference architecture 11 5.2 IPCable2Home
16、functional reference model . 15 5.3 IPCable2Home messaging interface model 20 5.4 IPCable2Home information reference model. 22 5.5 IPCable2Home operational models 25 5.6 Physical interfaces on the Residential Gateway. 27 6 Management tools. 28 6.1 Introduction/Overview . 28 6.2 Management architectu
17、re . 29 6.3 PS logical element IPCable2Home Management Portal (CMP). 31 6.4 PS logical element IPCable2Home Test Portal (CTP). 66 7 Provisioning tools . 71 7.1 Introduction/Overview . 71 7.2 Provisioning architecture 72 7.3 PS logical element DHCP Portal (CDP) . 73 7.4 PS function Bulk Portal Servic
18、es Configuration (BPSC) 100 7.5 PS function Time of Day client. 116 7.6 BP function DHCP client 120 8 Packet handling and address translation. 121 8.1 Introduction/Overview . 121 8.2 Architecture 122 8.3 PS logical element IPCable2Home Address Portal (CAP) . 122 9 Name resolution 139 9.1 Introductio
19、n/Overview . 139 9.2 Architecture 140 9.3 Name resolution requirements 142 iv ITU-T Rec. J.192 (11/2005) Page 10 Quality of Service. 143 10.1 Introduction 143 10.2 QoS architecture . 144 10.3 PS logical sub-element CQP 149 11 Security. 160 11.1 Introduction/Overview . 160 11.2 Security architecture.
20、 161 11.3 PS device authentication infrastructure 164 11.4 Secure management messaging to the PS 180 11.5 CQoS in the PS. 186 11.6 Firewall in the PS . 187 11.7 Additional security MIB objects in the PS. 208 11.8 Secure software download for the PS. 210 11.9 PS configuration file security in DHCP pr
21、ovisioning mode 227 11.10 Physical security. 230 11.11 Cryptographic algorithms. 231 12 Management processes . 231 12.1 Introduction/Overview . 231 12.2 Management tool processes 231 12.3 PS operation 233 12.4 MIB access . 237 13 Provisioning processes 242 13.1 Provisioning modes 243 13.2 Process fo
22、r provisioning the PS for management: DHCP provisioning mode . 246 13.3 Process for provisioning the PS for management: DHCP provisioning mode with HTTP/TLS 251 13.4 Provisioning the PS for management: SNMP provisioning mode . 257 13.5 PS WAN-Data provisioning process 266 13.6 Provisioning process:
23、LAN IP Device in the LAN-Pass realm 268 Annex A MIB objects . 269 Annex B Format and content for event, SYSLOG and SNMP Trap 292 B.1 Trap descriptions 306 Annex C Security threats and preventative measures. 306 Annex D Applications through CAT and firewall 307 D.1 Relationship scenarios 308 D.2 Appl
24、ications requiring firewall policy exclusively 310 D.3 Application requiring firewall policy and an ALG 312 ITU-T Rec. J.192 (11/2005) v Page Annex E MIBs 314 E.1 IPCable2Home Address Portal (CAP) MIB requirement 314 E.2 IPCable2Home DHCP Portal (CDP) MIB requirement. 326 E.3 IPCable2Home Test Porta
25、l (CTP) MIB requirement . 344 E.4 IPCable2Home Portal Services Device (PSDev) MIB requirement 354 E.5 IPCable2Home Security (SEC) MIB requirement . 391 E.6 Cablelabs definition MIB . 419 E.7 IPCable2Home QoS Portal (CQP) MIB requirements. 424 Appendix I Example of UPnP root device description of IPC
26、able2Home PS 437 ITU-T Rec. J.192 (11/2005) 1 ITU-T Recommendation J.192 A residential gateway to support the delivery of cable data services 1 Scope This Recommendation describes a Residential Gateway by providing a set of IP-based features that may be added to a Cable Modem or incorporated into a
27、standalone device. This will enable cable operators to provide an additional set of enhanced home network-based services to their customers including support for Quality of Service (QoS), device and service discovery, enhanced security, firewall management, home network focused management and provis
28、ioning features, managed network address translation, improved addressing and packet handling and LAN device diagnostics. This Recommendation is based upon the architectural frameworks defined in ITU-T Rec. J.190. This Recommendation represents an enhancement to ITU-T Rec. J.191, retaining a majorit
29、y of J.191 functionality as a foundation, and building upon this base to provide additional advanced features. A key design goal for equipment conforming to this Recommendation is interoperability with equipment conforming to ITU-T Rec. J.191. For example, common MIBs are used for the foundational f
30、unctionality. As a result, a J.192-based headend may manage a mixed J.191 and J.192 deployment. The key functionality that this Recommendation defines in addition to that defined by ITU-T Rec. J.191 includes: Device and service discovery for applications and services on the LAN; NAT support for IPSe
31、c VPN clients and home based servers; Standardized firewall configuration language and reporting; Standardized baseline firewall functionality; Simple parental control; Quality of Service for the LAN, managed at the Residential Gateway. Non-normative text referring to UPnP functionality is contained
32、 within this Recommendation as example implementations of home networking QoS and Management, and has been enclosed in brackets and marked as follows: “informative text: “. All text included within these brackets is non-normative. 2 References 2.1 References (normative) The following ITU-T Recommend
33、ations 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 Recommendation are theref
34、ore 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 not give it, as a stand-
35、alone document, the status of a Recommendation. ITU-T Recommendation J.112 Annex B (2004), Data-over-cable service interface specifications: Radio-frequency interface specification. ITU-T Recommendation J.125 (2004), Link privacy for cable modem implementations. ITU-T Recommendation J.126 (2004), Em
36、bedded Cable Modem device specification. 2 ITU-T Rec. J.192 (11/2005) ITU-T Recommendation J.161 (2001), Audio codec requirements for the provision of bidirectional audio service over cable television networks using cable modems. ITU-T Recommendation J.162 (2005), Network call signalling protocol fo
37、r the delivery of time-critical services over cable television networks using cable modems. ITU-T Recommendation J.163 (2005), Dynamic quality of service for the provision of real-time services over cable television networks using cable modems. ITU-T Recommendation J.164 (2005), Event message requir
38、ements for the support of real-time services over cable television networks using cable modems. ITU-T Recommendation J.167 (2005), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems. ITU-T Recommendat
39、ion J.170 (2005), IPCablecom security specification. ITU-T Recommendation J.175 (2005), Audio server protocol. ITU-T Recommendation J.178 (2005), IPCablecom CMS to CMS signalling. ITU-T Recommendation J.191 (2004), IP feature package to enhance cable modems. ITU-T Recommendation X.690 (2002) | ISO/I
40、EC 8825-1:2002, Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). ITU-T Recommendation X.509 (2005) | ISO/IEC 9594-8:2005, Information technology Open Systems Interconnection The Directory:
41、 Public-key and attribute certificate frameworks. ANSI/SCTE 22-1-2002, DOCSIS 1.0, Radio Frequency Interface. ANSI/SCTE 23-3-2005, DOCSIS 1.1 Part 3: Operations Support System Interface. FIPS 140-2 (2001), Security Requirements for Cryptographic Modules, Department of Commerce, NIST. FIPS 180-1 (199
42、5), Secure Hash Algorithm, Department of Commerce, NIST. IANAifType MIB Definitions, http:/www.iana.org/assignments/ianaiftype-mib IEEE 802.11-1999-MIB-D6.2, IEEE 802.11 Management Information Base. IEEE 802.11A-1999, IEEE Standard for Telecommunications and Information Exchange Between Systems LAN/
43、MAN Specific Requirements Part 11: Wireless Medium Access Control (MAC) and physical layer (PHY) specifications: High Speed Physical Layer in the 5 GHz Band, Annex D. IEEE 802.11B/Cor1-2001, Information Technology Telecommunications and Information Exchange Between Systems Local and Metropolitan Net
44、works Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, Amendment 2: Higher Speed Physical Layer (PHY) Extension in the 2.4 GHz band, Corrigendum 1, Annex D. IEEE 802.11D, IEEE Standard for IT. Telecommunications and information exchange
45、 between systems LAN/MAN Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, Amendment 3: Specification for operation in additional regulatory domains, Annex D. ITU-T Rec. J.192 (11/2005) 3 IEEE 802.11G-2003, IEEE Standard for IT. Telecomm
46、unications and information exchange between systems LAN/MAN Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, Amendment 4: Further Higher Data Rate Extension in the 2.4 GHz Band, Annex D. ISO/IEC 8802-2 (ANSI/IEEE Std 802.2):1998, Inform
47、ation technology Telecommunications and information exchange between systems Local and metropolitan area networks Specific requirements Part 2: Logical link control. ISO/IEC 10038 (ANSI/IEEE Std 802.1D):1993, Information technology Telecommunications and information exchange between systems Local ar
48、ea networks Media access control (MAC) bridges. IETF RFC 347 (1972), Echo Process. IETF RFC 768 (1980), User Datagram Protocol (UDP). IETF RFC 791 (MIL STD 1777) (1981), DARPA Internet Program, Protocol Specification. Internet Protocol. IETF RFC 792 (1981), DARPA Internet Program, Protocol Specifica
49、tion. Internet Control Message Protocol (ICMP). IETF RFC 793 (1981), DARPA Internet Program, Protocol Specification. Transmission Control Protocol. IETF RFC 868 (1983), Time Protocol. IETF RFC 919 (1984), Broadcasting Internet Datagrams. IETF RFC 922 (1984), Broadcasting Internet datagrams in the presence of subnets. IETF RFC 1034 (1987), Domain Names Concepts and Facilities. IETF RFC 1035 (1987), Domain Names Implementation and Specifi
