ITU-T J 218-2007 Cable modem IPv4 and IPv6 eRouter specification (Study Group 9)《电缆调制解调器网际网路通讯协定第四版(IPv4 )和网际网路通讯协定第六版(IPv6)路由器规范 9号研究组》.pdf

《ITU-T J 218-2007 Cable modem IPv4 and IPv6 eRouter specification (Study Group 9)《电缆调制解调器网际网路通讯协定第四版(IPv4 )和网际网路通讯协定第六版(IPv6)路由器规范 9号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T J 218-2007 Cable modem IPv4 and IPv6 eRouter specification (Study Group 9)《电缆调制解调器网际网路通讯协定第四版(IPv4 )和网际网路通讯协定第六版(IPv6)路由器规范 9号研究组》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T J.218TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2007) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Interactive systems for digital television distribution Cable modem IPv4 and IPv6 eRouter

2、specification ITU-T Recommendation J.218 ITU-T Rec. J.218 (07/2007) i ITU-T Recommendation J.218 Cable modem IPv4 and IPv6 eRouter specification Summary ITU-T Recommendation J.218 defines a core set of features that enables multiple subscriber devices to gain access to operator-provided high speed d

3、ata service using DOCSIS. This core set of features allows for both IPv4 and IPv6 enabled devices to gain connectivity to the Internet. The eRouter is specified as an embedded service/application functional entity (eSAFE) device as defined in ITU-T Recommendation J.126 that is implemented in conjunc

4、tion with a DOCSIS cable modem device. The core set of features defined in this Recommendation includes the ability to provision multiple CPE devices, a description of how to forward data to and from CPE devices and also the ability to forward IP multicast traffic to CPE devices. Source ITU-T Recomm

5、endation J.218 was approved on 29 July 2007 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.218 (07/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information

6、 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 issuing Recommendations on them with a view to standardizing telecommunications on a worldwide

7、 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 ITU-T Recommendations is covered by the procedure laid down in WTSA R

8、esolution 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 used for conciseness to indicate both a telecommunication administrat

9、ion 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 the Recommendation is achieved when all of these mandatory provisions a

10、re 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 of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the p

11、ossibility 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 Property Rights, whether asserted by ITU members or others outside of t

12、he 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, implementers are cautioned that this may not represent the latest inf

13、ormation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.218 (07/2007) iii CONTENTS Pag

14、e 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative references 3 2.3 Reference acquisition . 3 3 Terms and definitions . 3 4 Abbreviations, acronyms and conventions. 3 4.1 Abbreviations and acronyms 3 4.2 Conventions 5 5 Theory of operation 5 6 eRouter initialization 7 7 IPv4 prov

15、isioning . 8 7.1 DHCPv4 fields used by the eRouter. 9 7.2 Router DHCPv4 server sub-element 10 8 IPv6 provisioning . 11 8.1 Link-local address acquisition 12 8.2 Router discovery. 12 8.3 IPv6 address and other configuration parameters acquisition 12 8.4 Use of T1 and T2 timers. 14 8.5 IPv6 provisioni

16、ng of CPE devices 14 8.6 DHCPv6 requirements for eRouter 15 9 IPv4 data forwarding and NAPT operation 15 9.1 Introduction 15 9.2 System description 16 9.3 IPv4 router 17 9.4 NAPT 19 9.5 ARP 21 9.6 IPv4 multicast. 21 10 IPv6 data forwarding 25 10.1 Overview 25 10.2 System description 26 10.3 IPv6 mul

17、ticast. 27 11 Quality of service 31 11.1 Downstream quality of service operation. 31 11.2 Upstream quality of service operation 31 Annex A SNMP MIB objects supported by the eRouter 32 A.1 eRouter interface numbering 32 iv ITU-T Rec. J.218 (07/2007) Page Annex B Configuration of eRouter operational p

18、arameters . 33 B.1 eRouter SNMP configuration. 33 B.2 eCM Proxy mechanism for configuration of eRouter 38 B.3 eRouter configuration encodings 39 Annex C DHCP option definitions . 43 C.1 The DHCPv4 eRouter container option . 43 C.2 DHCPv6 options. 43 ITU-T Rec. J.218 (07/2007) 1 ITU-T Recommendation

19、J.218 Cable modem IPv4 and IPv6 eRouter specification 1 Scope This Recommendation defines a core set of features that enables multiple subscriber devices to gain access to operator-provided high speed data service using DOCSIS. This core set of features allows for both IPv4 and IPv6 enabled devices

20、to gain connectivity to the Internet. The eRouter is specified as an embedded service/application functional entity (eSAFE) device as defined in ITU-T J.126 that is implemented in conjunction with a DOCSIS Cable Modem device. The core set of features defined in this Recommendation includes the abili

21、ty to provision multiple CPE devices, a description of how to forward data to and from CPE devices and also the ability to forward IP multicast traffic to CPE devices. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source

22、 material; as such, the usual style of ITU-T recommendations has not been applied. 2 References 2.1 Normative references The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of pub

23、lication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of

24、the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T J.126 ITU-T Recommendation J.126 (2007), Embedded cable modem device specification. ITU-T J.222.

25、2 ITU-T Recommendation J.222.2 (2007), Third-generation transmission systems for interactive cable television services IP cable modems: MAC and upper layer protocols. ITU-T J.222.3 ITU-T Recommendation J.222.3 (2007), Third-generation transmission systems for interactive cable television services IP

26、 cable modems: security services. IETF RFC 792 IETF RFC 792 (1981), Internet Control Message Protocol DARPA Internet Program Protocol Specification. IETF RFC 826 IETF RFC 826 (1982), An Ethernet Address Resolution Protocol, or Converting Network Protocol Addresses to 48.bit Ethernet Address for Tran

27、smission on Ethernet Hardware. IETF RFC 868 IETF RFC 868 (1983), Time Protocol. IETF RFC 1122 IETF RFC 1122 (1989), Requirements for Internet Hosts Communication Layers. IETF RFC 1812 IETF RFC 1812 (1995), Requirements for IP Version 4 Routers. IETF RFC 1918 IETF RFC 1918 (1996), Address Allocation

28、for Private Internets. 2 ITU-T Rec. J.218 (07/2007) IETF RFC 2131 IETF RFC 2131 (1997), Dynamic Host Configuration Protocol. IETF RFC 2132 IETF RFC 2132 (1997), DHCP Options and BOOTP Vendor Extensions. IETF RFC 2461 IETF RFC 2461 (1998), Neighbor Discovery for IP Version 6 (IPv6). IETF RFC 2462 IET

29、F RFC 2462 (1998), IPv6 Stateless Address Autoconfiguration. IETF RFC 2463 IETF RFC 2463 (1998), Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. IETF RFC 2710 IETF RFC 2710 (1999), Multicast Listener Discovery (MLD) for IPv6. IETF RFC 3022 IETF RF

30、C 3022 (2001), Traditional IP Network Address Translator (Traditional NAT). IETF RFC 3203 IETF RFC 3203 (2001), DHCP reconfigure extension. IETF RFC 3315 IETF RFC 3315 (2003), Dynamic Host Configuration Protocol for IPv6 (DHCPv6). IETF RFC 3319 IETF RFC 3319 (2003), Dynamic Host Configuration Protoc

31、ol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers. IETF RFC 3376 IETF RFC 3376 (2002), Internet Group Management Protocol, Version 3. IETF RFC 3412 IETF RFC 3412 (2002), Message Processing and Dispatching for the Simple Network Management Protocol (SNMP). IETF RFC 3413 IETF RFC 3413

32、(2002), Simple Network Management Protocol (SNMP) Applications. IETF RFC 3415 IETF RFC 3415 (2002), View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP). IETF RFC 3417 IETF RFC 3417 (2002), Transport Mappings for the Simple Network Management Protocol (SNMP). IETF

33、 RFC 3419 IETF RFC 3419 (2002), Textual Conventions for Transport Addresses. IETF RFC 3489 IETF RFC 3489 (2003), STUN Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs). IETF RFC 3513 IETF RFC 3513 (2003), Internet Protocol Version 6 (IPv6) Addressing Archite

34、cture. IETF RFC 3584 IETF RFC 3584 (2003), Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework. IETF RFC 3633 IETF RFC 3633 (2003), IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6. IETF RFC 3646 IETF RFC 3646 (200

35、3), DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6). IETF RFC 3736 IETF RFC 3736 (2004), Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6. IETF RFC 3810 IETF RFC 3810 (2004), Multicast Listener Discovery Version 2 (MLDv2) for IPv6. IETF RFC 40

36、75 IETF RFC 4075 (2005), Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6. IETF RFC 4242 IETF RFC 4242 (2005), Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6). ITU-T Rec. J.218 (07/2007) 3 IETF RFC 4293 IETF RFC 4293 (2006), Management Inf

37、ormation Base for the Internet Protocol (IP). IETF RFC 4361 IETF RFC 4361 (2006), Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4). 2.2 Informative references This Recommendation uses the following informative references: OSSIv3.0 DOCSIS Operations Suppo

38、rt System Interface Specification, CM-SP-OSSIv3.0-I02-070223, February 23, 2007, Cable Television Laboratories, Inc. CANN DHCP CableLabs DHCP Options Registry Specification, CL-SP-CANN-DHCP-Reg-I01-061117, November 17, 2006, Cable Television Laboratories, Inc. 2.3 Reference acquisition Cable Televis

39、ion Laboratories, Inc., 858 Coal Creek Circle, Louisville, CO 80027; Phone +1 303-661-9100; Fax: +1 303-661-9199; Internet: http:/ IETF Standards, Internet Engineering Task Force (IETF) Secretariat c/o Corporation for National Research Initiatives, 1895 Preston White Drive, Suite 100, Reston, VA 201

40、91-5434, Phone: +1 703-620-8990, Fax: +1 703-620-9071, Internet: http:/www.ietf.org/ 3 Terms and definitions This Recommendation defines the following terms: 3.1 customer-facing interface: An eRouter interface used for connecting CPE devices. 3.2 customer-facing IP interface: An IP interface connect

41、ed to the eRouter which is not necessarily mapped one-to-one with the number of customer-facing ports on the eRouter. 3.3 customer-facing logical IP interface: A logical interface connected to the eRouter which is not necessarily mapped one-to-one with the number of customer-facing ports on the eRou

42、ter. 3.4 eDOCSIS: Embedding another functional device within a cable modem. 3.5 eRouter: An eSAFE device that is implemented in conjunction with the DOCSIS embedded cable modem. 3.6 multicast subscription database: A simple table of entries for the IPv4 or IPv6 multicast group membership information

43、 maintained by the eRouter on respective interfaces. Implementation details for storage of records is completely vendor-defined. 3.7 operator-facing interface: The eRouter interface which is connected to the embedded cable modem. 3.8 operator-facing IP interface: IP interface that is connected to th

44、e embedded cable modem and is provisioning with an IP address provided by the operator. 4 Abbreviations, acronyms and conventions 4.1 Abbreviations and acronyms This Recommendation defines the following abbreviations: ALG Application Level Gateway ARP Address Resolution Protocol ASN.1 Abstract Synta

45、x Notation One 4 ITU-T Rec. J.218 (07/2007) CPE Customer Premises Equipment CM Cable Modem DAD Duplicate Address Detection DNS Domain Name System DUID DHCP Unique Identifier EAE Early Authentication and Encryption eSAFE embedded Service/Application Functional Entity EUI Extended Unique Identifier FT

46、P File Transfer Protocol ID Identifier IP Internet Protocol IRT Initial Retransmission Time LAN Local Area Network MAC Media Access Control MIB Management Information Base MLD Multicast Listener Discovery MRC Maximum Retransmission Count MRD Maximum Retransmission Duration MRT Maximum Retransmission

47、 Time NAT Network Address Translation NAPT Network Address Port Translation ND Neighbour Discovery OID Object ID OUI Organization Unique Identifier RA Router Advertisement RD Router Discovery SIP Session Initiation Protocol SLAAC Stateless Address Autoconfiguration TCP Transmission Control Protocol

48、TLV Type/Length/Value TTL Time To Live UDP User Datagram Protocol WAN Wide Area Network ITU-T Rec. J.218 (07/2007) 5 4.2 Conventions Throughout this Recommendation, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ This word means

49、that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendation. “SHOULD“ This word means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ This phrase means that there may exist valid reasons in particular circumstances w