1、 International Telecommunication Union ITU-T J.800.0TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Multimedia over IP in cable Cable assigned names and numbers Recommendation ITU-T J.800.
2、0 Rec. ITU-T J.800.0 (08/2008) i Recommendation ITU-T J.800.0 Cable assigned names and numbers Summary Recommendation ITU-T J.800.0 describes a set of Cable industry registries and namespaces for Names and Numbers. Numerous protocol fields make use of identifiers with well-known names or number valu
3、es. This Recommendation is a common repository to hold these values. Source Recommendation ITU-T J.800.0 was approved on 22 August 2008 by ITU-T Study Group 9 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T J.800.0 (08/2008) FOREWORD The International Telecommunication Union (ITU
4、) is the United Nations specialized agency in the field of telecommunications, information and communication 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 issu
5、ing Recommendations 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 top
6、ics. The approval of 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
7、 “Administration“ is 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) a
8、nd compliance with the 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 Recommen
9、dation is required of 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 cl
10、aimed 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 Reco
11、mmendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever
12、, without the prior written permission of ITU. Rec. ITU-T J.800.0 (08/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative references 1 2.3 Reference document acquisition. 3 3 Abbreviations and acronyms 3 4 Cable DHCP protocol field registry . 4 4.1 Definition
13、 4 4.2 Format of the DHCPv6 cable vendor-specific information option 4 4.3 Template for defining new DHCPv6 cable vendor-specific information option codes 5 4.4 List of relevant specifications. 6 5 Cable XML registry 6 5.1 Guidelines. 6 5.2 Examples 7 5.3 Registered XML name spaces 7 6 Cable diamete
14、r AVP registry 8 6.1 Application identifiers 8 6.2 Command codes . 8 6.3 Vendor identifier 9 6.4 Attribute-value pair codes 9 6.5 Experimental result codes. 10 6.6 Assignment of the diameter codes and identifiers 10 7 Cable RCP registry . 11 7.1 Definition 11 7.2 Format. 12 7.3 Process for defining
15、and allocating new Receive Channel Profiles . 12 8 Cable ASN.1 Codes registry. 12 8.1 Definition 12 8.2 SMI Network Management Codes . 12 9 Cable Applications Registry. 18 Rec. ITU-T J.800.0 (08/2008) 1 Recommendation ITU-T J.800.0 Cable assigned names and numbers 1 Scope This Recommendation is a se
16、t of Cable industry registries and namespaces for Names and Numbers. Numerous protocol fields make use of identifiers with well-known names or number values, for example, the IETF DHCP protocol and vendor specific option values, the IETF RADIUS and DIAMETER protocols and associated Cable attributes,
17、 etc. To ensure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). For vendor-specific protocol fields
18、 that are defined by Cable industry Recommendations and specifications, or when the use of such protocol identifiers may be common to multiple Cable industry projects and specifications, that role is provided by CableLabs. This Recommendation is a common repository that holds these values. This Reco
19、mmendation uses some of the terminology and guidelines of IETF RFC 2434. The scope of this version of this Recommendation includes: A DHCP registry for protocol fields authoritatively assigned by CableLabs that are in use in eDOCSIS, DOCSIS, IPCable2Home, and IPCablecom, for both IPv4 and DHCPv6. An
20、 XML registry for XML namespaces for DOCSIS and IPCablecom. A DIAMETER registry for IPCablecom. A Receive Channel Profile (RCP) registry for CableLabs-defined Standard-RCPs and Vendor-defined Manufacturer-RCPs that are used in DOCSIS 3.0 and beyond to communicate the receiver capabilities of a cable
21、 modem. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not been applied. 2 References 2.1 Normative references IETF RFC 3588 IETF RFC 3588, Diameter B
22、ase Protocol, September 2003. IETF RFC 2434 IETF RFC 2434/BCP0026, Guidelines for Writing an IANA Considerations Section in RFCs, October 1998. IETF RFC 3315 IETF RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), July 2003. 2.2 Informative references This Recommendation uses the follo
23、wing informative references. CANN DHCP Recommendation ITU-T J.800.1, Cable DHCP Registry. CH CAP-MIB Recommendation ITU-T J.192, A residential gateway to support the delivery of cable data services Annex E.1 IPCable2Home Addressing Portal (CAP) MIB requirement. CH CDP-MIB Recommendation ITU-T J.192,
24、 A residential gateway to support the delivery of cable data services Annex E.2 IPCable2Home DHCP Portal (CDP) MIB requirement. 2 Rec. ITU-T J.800.0 (08/2008) CH CTP-MIB Recommendation ITU-T J.192, A residential gateway to support the delivery of cable data services Annex E.3 IPCable2Home Test Porta
25、l (CTP) MIB requirement. CH PSDEV-MIB Recommendation ITU-T J.192, A residential gateway to support the delivery of cable data services Annex E.4 IPCable2Home Portal Services Device (PSDev) MIB requirement. CH QOS-MIB Recommendation ITU-T J.192, A residential gateway to support the delivery of cable
26、data services Annex E.7 IPCable2Home QoS Portal (CQP) MIB requirement. CH SEC-MIB Recommendation ITU-T J.192, A residential gateway to support the delivery of cable data services Annex E.5 IPCable2Home Security (SEC) MIB requirement. CO CSA-MIB CableOffice Commercial Services Annex MIB Definition, C
27、H-SP-CO-MIB-CSA-C01-060728, July 28, 2006, Cable Television Laboratories, Inc. DOCS TEST DOCSIS Testing MIB Specification, CM-SP-TestMIB-D04-070829, August 29, 2007, Cable Television Laboratories, Inc. DSG ANSI/SCTE 106 2007, DOCSIS Set-top Gateway (DSG) Interface Specification. eDOCSIS Recommendati
28、on ITU-T J.126, Embedded Cable Modem device specification. IANA EN IANAs Enterprise-Numbers: http:/www.iana.org/assignments/enterprise-numbers. IANA AAA IANAs AAA parameters register: ftp:/ftp.iana.org/assignments/aaa-parameters/. L2VPN Recommendation ITU-T J.213, Layer 2 virtual private networks fo
29、r IP cable modem systems. M-OSSI ANSI/SCTE 141 2007, Modular Operations Support System Interface Specification. MIB-BB Recommendation ITU-T J.199, Battery backup for cable-based devices. MIB-CLABDEF Recommendation ITU-T J.800.2 (2008), Cable Definition MIB Specification. MULPI Recommendation ITU-T J
30、.222.2, Third-generation transmission systems for interactive cable television services IP cable modems: MAC and Upper Layer protocols. OC MIB-HOST2.X OpenCable Host Device 2.X MIB Specification, OC-SP-MIB-HOST2.X-I03-071113, November 13, 2007, Cable Television Laboratories, Inc. OSSIv2.0 ANSI/SCTE
31、79-2 2002 DOCSIS 2.0 Data-Over-Cable Service Interface Specifications, Operations Support System Interface Specification. OSSIv3.0 ANSI/SCTE 135-4 2008 DOCSIS 3.0 Operations Support System Interface Specification. Rec. ITU-T J.800.0 (08/2008) 3 PKT 29.229 Recommendation ITU-T J.366.6, Cx/Dx interfac
32、es based on the Diameter protocol specification (3GPP TS-29.229). PKT ACCT Recommendation ITU-T J.363, IPCablecom2 data collection to support accounting. PKT ES-INF PacketCable Electronic Surveillance Intra-Network Functions Specification, PKT-SP-ES-INF-I03-070925, September 25, 2007, Cable Televisi
33、on Laboratories, Inc. PKT ESP ANSI/SCTE 24-13 2006 PacketCable Electronic Surveillance Specification. PKT EUE-DATA Recommendation ITU-T J.370 (2008), IPCablecom2 E-UE Provisioning data Model specification. PKT EVE MIB1.5 Recommendation ITU-T J.166 Annex D, IPCablecom Management Event MIB Specificati
34、on. PKT MIB EXMTA1.5 Recommendation ITU-T J.166 Annex E, IPCablecom MTA Extension MIB Specification. PKT MIB MTA1.5 Recommendation ITU-T J.166 Annex B, IPCablecom MTA MIB Specification. PKT MIB SIG1.5 Recommendation ITU-T J.166 Annex C, IPCablecom 1.5 Signaling MIB Specification. PKT RST-ACCT Recomm
35、endation ITU-T J.460.3 (2008), IPCablecom2 Residential SIP Telephony: usage data recording. PKT-SP-RSTF Recommendation ITU-T J.460.1 (2008), IPCablecom2 Residential SIP Telephony Feature Specification. PKT RST-EUE-PROV Recommendation ITU-T J.369 (2008), IPCablecom2 E-UE Provisioning Framework specif
36、ication. TEI Recommendation ITU-T J.214, Cable modem TDM emulation interface. 2.3 Reference document acquisition Internet Engineering Task Force (IETF) Secretariat, 46000 Center Oak Plaza, Sterling, VA 20166, Phone +1-571-434-3500, Fax +1-571-434-3535, http:/www.ietf.org. Internet Assigned Numbers A
37、uthority (IANA), http:/www.iana.org. Cable Television Laboratories, Inc., 858 Coal Creek Circle, Louisville, CO 80027, Phone +1-303-661-9100; Fax +1-303-661-9199, http:/ . 3 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AVP Attribute-Value Pairs CMTS C
38、able Modem Termination System DHCP Dynamic Host Configuration Protocol DOCSIS Data Over Cable Service Interface Specification DTD Document Type Definition 4 Rec. ITU-T J.800.0 (08/2008) RCC Receive Channel Configurations RCP Receive Channel Profile RST Residential SIP Telephony SMI Structure of Mana
39、gement Information URL Uniform Resource Locator XML Extensible Markup Language XSD XML Schema Definition 4 Cable DHCP protocol field registry 4.1 Definition This Recommendation describes the Cable DHCP registry and defines new name spaces associated with Cable DHCPv4 and DHCPv6 options: Cable projec
40、t codes, Sub-option codes for DHCPv4 options, Cable Vendor-specific Information Option codes for DHCPv6. The Cable Assigned Name and Number authority (CableLabs) has established a registry of values for each of these name spaces which are found in CANN DHCP. 4.2 Format of the DHCPv6 cable vendor-spe
41、cific information option DHCPv6 defines a Vendor-specific Information Option (see the option code OPTION_VENDOR_OPTS in Section 22.17 of IETF RFC 3315). This clause defines the structure or format of the option data for the Cable Vendor-specific Information Option. The format of the DHCPv6 Cable Ven
42、dor-specific Information option is: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_VENDOR_OPTS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | enterprise-number (4491 for Ca
43、bleLabs) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . CableLabs-defined option-data . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ option-code OPTION_VENDOR_OPTS (17) option-len 4 + length of option-data field enterprise-number The CableLabs regi
44、stered Enterprise Number: 4491, as registered with IANA in the Private Enterprise Numbers: http:/www.iana.org/assignments/enterprise-numbers.html Rec. ITU-T J.800.0 (08/2008) 5 CableLabs-defined option-data An object containing one or more CableLabs sub-options The option-data field of the DHCPv6 Ca
45、bleLabs Vendor-specific Information option contains sub-option values. Each sub-option is structured as follows: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CableLabs sub-option-code | sub-option-len | +-+-+-+-+-
46、+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | sub-option-data | | (sub-option-len octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ CableLabs sub-option-code: 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | res |code | sub-option type | +-+-+
47、-+-+-+-+-+-+-+-+-+-+-+-+-+-+ res: reserved for CableLabs, do not use; bits must be zero value. code: identifies the CableLabs project code for this sub-option. The null value for these 3 bits (000) identifies a generic DHCPv6 option that may be common to multiple projects. See the Values for the Cab
48、leLabs Project Codes clause of the Cable DHCP options recommendation for the values of the CableLabs Project Codes for DHCPv6 options. sub-option type: defines the option type. sub-option-len length of sub-option-data field sub-option-data the value of the CableLabs sub-option. 4.3 Template for defining new DHCPv6 cable vendor-specific information option codes Each request (in the form of a contribution to the SG responsible for this Recommendation) for a new definition of a DHCPv6 Cable Vendor-specific Information Option must include: A definition of
