1、 ETSI ES 203 386 V1.1.1 (2017-08) Integrated broadband cable telecommunication networks (CABLE); Embedded Router ETSI STANDARD ETSI ETSI ES 203 386 V1.1.1 (2017-08) 2 Reference DES/CABLE-00009 Keywords CABLE, DOCSIS, IPv4, IPv6, MODEM, router ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cede
2、x - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document ma
3、y be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in p
4、rint, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of
5、 this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be rep
6、roduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restrict
7、ion extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partn
8、ers. oneM2M logo is protected for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI ES 203 386 V1.1.1 (2017-08) 3 Contents Intellectual Property Rights 7g3Foreword . 7g3Modal verbs terminology 7g31 Scope 8g32 References 8g32.1 Norm
9、ative references . 8g32.2 Informative references 11g33 Definitions and abbreviations . 12g33.1 Definitions 12g33.2 Abbreviations . 14g34 Theory of operation 16g34.0 General . 16g34.1 eDOCSIS eRouter and TR-069 architecture 18g34.2 eRouter device management. 19g34.3 Service discovery . 19g34.3.0 Gene
10、ral 19g34.3.1 mDNS (multicast Domain Name System) 20g34.3.2 UPnP (Universal Plug and Play) . 21g34.4 CER-ID (Customer Edge Router - Identification) 21g35 eRouter initialization 22g35.0 eRouter modes 22g35.1 Network Time Protocol 23g35.2 DNS proxy forwarding . 24g36 IPv4 provisioning . 24g36.0 Genera
11、l . 24g36.1 DHCPv4 fields used by the eRouter . 26g36.2 eRouter interface addressing using Link ID . 27g36.3 Router DHCPv4 server Sub-element 28g36.3.1 DHCPv4 server function goals . 28g36.3.2 DHCPv4 server function system description 28g36.3.3 DHCPv4 server function requirements . 28g36.4 Operator-
12、facing IPv4 address release behavior 30g36.5 Customer-facing IPv4 address release behavior . 30g37 Operator-facing IPv6 provisioning . 30g37.0 General . 30g37.1 Obtain link-local address 31g37.2 Perform router discovery 31g37.3 Obtain IPv6 address and other configuration parameters . 31g37.4 Use of
13、T1 and T2 timers . 34g37.5 Customer-facing IPv6 provisioning of CPE devices 34g37.5.0 Initial provisioning 34g37.5.1 Additional customer-facing IP interfaces enabled after initial provisioning . 37g37.5.2 SLAAC requirements for eRouter 37g37.5.2.0 General 37g37.5.2.1 Local configuration of SLAAC opt
14、ions 37g37.5.3 DHCPv6 requirements for eRouter . 37g37.5.3.0 General 37g37.5.3.1 Local configuration of DHCPv6 options. 39g37.5.4 Prefix changes . 39g37.6 Operator-facing IPv6 address release behavior 39g37.7 Customer-facing IPv6 address release behavior . 39g37.8 CER-ID requirements . 40g3ETSI ETSI
15、 ES 203 386 V1.1.1 (2017-08) 4 8 IPv4 data forwarding and NAPT operation 40g38.0 Applicability . 40g38.1 Introduction 40g38.1.1 Assumptions . 40g38.1.2 Overview 40g38.2 System description . 41g38.3 IPv4 router 42g38.3.0 Overview 42g38.3.1 Dual IP protocol and Link ID enabled mode IPv4 routing . 43g3
16、8.4 NAPT . 44g38.4.0 General 44g38.4.1 Dynamically triggered NAPT translation . 44g38.4.2 Application Layer Gateways (ALGs) . 45g38.4.2.0 General 45g38.4.2.1 ICMP error message ALG 45g38.4.2.2 FTP ALG 45g38.4.3 Multicast NAPT 45g38.5 ARP 45g38.6 IPv4 multicast . 46g38.6.0 General 46g38.6.1 IGMP prox
17、ying . 46g38.6.1.0 Operation . 46g38.6.1.1 IPv4 group membership database . 47g38.6.2 IPv4 multicast forwarding 47g38.6.3 IPv4 multicast forwarding example 48g38.7 IPv4/IPv6 co-existence technologies 49g38.7.0 General 49g38.7.1 Dual-stack Lite operation 49g38.7.2 Mapping of Address and Port (MAP) .
18、49g38.7.2.0 MAP transport modes . 49g38.7.2.1 MAP-E or MAP-T configuration via DHCP . 50g38.7.2.2 MAP-E or MAP-T configuration via TLV202.11 . 50g38.7.3 Packet fragmentation 50g39 IPv6 data forwarding 51g39.0 Applicability . 51g39.1 Introduction 51g39.1.1 Assumptions . 51g39.1.2 Overview 51g39.2 Sys
19、tem description . 52g39.3 IPv6 multicast . 53g39.3.0 General 53g39.3.1 MLD proxying 54g39.3.2 IPv6 group membership database . 55g39.3.3 IPv6 multicast forwarding 55g39.3.4 IPv6 multicast forwarding example 55g310 Quality of Service . 57g310.0 General requirements . 57g310.1 Downstream Quality of Se
20、rvice operation . 57g310.2 Upstream Quality of Service operation 57g311 eRouter management 57g311.0 General requirements . 57g311.1 eRouter SNMP management interface requirements 58g311.2 eRouter TR-069 management interface requirements 58g311.2.0 General requirements 58g311.2.1 ACS discovery 58g311
21、.2.1.1 eRouter TR-069 management server configuration file TLV encapsulation 58g311.2.1.2 TR-069 management server DHCP requirements . 58g311.2.2 ACS selection . 58g311.2.3 Dynamic ACS update . 58g311.2.4 TR-069 CWMP control and credentials 58g3ETSI ETSI ES 203 386 V1.1.1 (2017-08) 5 12 Security. 59
22、g313 eRouter tunnel management and configuration 59g313.1 GRE requirements 59g3Annex A (normative): SNMP MIB objects supported by the eRouter 60g3A.0 List of MIB objects 60g3A.1 eRouter interface numbering 60g3A.2 eRouter ifTable requirements . 61g3A.3 eRouter ipNetToPhysicalTable requirements . 63g
23、3A.4 CLAB-GRE-MIB . 63g3A.5 CLAB-GW-MIB 63g3Annex B (normative): Configuration of eRouter operational parameters . 65g3B.1 eRouter SNMP configuration . 65g3B.1.1 eRouter SNMP modes of operation 65g3B.1.2 eRouter SNMP access control configuration 65g3B.1.2.1 View-based Access Control Model (VACM) pro
24、file . 65g3B.1.3 SNMPv1v2c Coexistence Configuration 65g3B.1.3.0 General 65g3B.1.3.1 Mapping SNMPv1v2c Coexistence Configuration . 65g3B.1.3.1.0 Overview . 65g3B.1.3.1.1 snmpCommunityTable 66g3B.1.3.1.2 snmpTargetAddrTable 66g3B.1.3.1.3 snmpTargetAddrExtTable . 67g3B.1.3.1.4 vacmSecurityToGroupTable
25、 . 67g3B.1.3.1.5 vacmAccessTable 68g3B.1.3.2 Mapping SNMPv3 access view configuration 68g3B.1.3.2.0 Overview . 68g3B.1.3.2.1 vacmViewTreeFamilyTable 69g3B.2 SNMP configuration of eRouter . 69g3B.3 eCM proxy mechanism for configuration of eRouter 70g3B.4 eRouter configuration encodings 70g3B.4.1 eRou
26、ter TLV processing 70g3B.4.2 eRouter initialization mode encoding . 70g3B.4.3 TR-069 management server . 71g3B.4.3.0 General 71g3B.4.3.1 EnableCWMP . 71g3B.4.3.2 URL 71g3B.4.3.3 Username 71g3B.4.3.4 Password . 71g3B.4.3.5 ConnectionRequestUsername . 71g3B.4.3.6 ConnectionRequestPassword 72g3B.4.3.7
27、ACS override 72g3B.4.4 eRouter initialization mode override 72g3B.4.5 SNMPv1v2c coexistence configuration . 72g3B.4.5.0 General 72g3B.4.5.1 SNMPv1v2c community name . 72g3B.4.5.2 SNMPv1v2c transport address access 73g3B.4.5.2.0 General 73g3B.4.5.2.1 SNMPv1v2c transport address 73g3B.4.5.2.2 SNMPv1v2
28、c transport address mask . 73g3B.4.5.3 SNMPv1v2c access view type 73g3B.4.5.4 SNMPv1v2c access view name 73g3B.4.6 SNMPv3 access view configuration . 73g3B.4.6.0 General 73g3ETSI ETSI ES 203 386 V1.1.1 (2017-08) 6 B.4.6.1 SNMPv3 access view name 74g3B.4.6.2 SNMPv3 access view subtree . 74g3B.4.6.3 S
29、NMPv3 access view mask 74g3B.4.6.4 SNMPv3 access view type 74g3B.4.7 Vendor specific information . 75g3B.4.7.0 General 75g3B.4.7.1 Vendor ID encoding 75g3B.4.8 SNMP MIB object 75g3B.4.9 Topology mode encoding . 75g3B.4.10 Router Advertisement (RA) transmission interval . 76g3B.4.11 IP multicast conf
30、iguration server 76g3B.4.12 Link ID control . 76g3B.5 SNMP soft reset . 76g3B.6 Provisioning and operational event messages 77g3Annex C (normative): eRouter initialization mode control interactions 80g3C.1 Valid interactions . 80g3C.2 Invalid Cases 82g3Annex D (normative): TR-069 managed objects req
31、uirements . 83g3D.0 General . 83g3D.1 Profiles from TR-181 . 83g3D.2 Extensions to TR-181 profiles 84g3D.3 Management interface protocol requirements for GRE . 85g3Annex E (normative): Example: Routing with Link ID . 87g3E.0 Addressing scheme . 87g3E.1 IP MIB route example 88g3Annex F (normative): S
32、ection categorizing 49 simple security recommendations 89g3F.1 Summary of simple security requirements . 89g3F.2 Critical recommendations. 89g3F.3 Important recommendations . 91g3F.4 BCP recommendations . 92g3F.5 Other recommendations . 94g3F.6 Recommendations in conflict with MSO needs . 95g3Annex
33、G (normative): eRouter GRE tunnelling architecture 96g3G.0 Architecture and interfaces . 96g3G.1 Use case for data traffic flow for both private and public SSIDs . 97g3G.1.0 Overview 97g3G.1.1 Private network outbound from the LAN . 98g3G.1.2 Private network inbound from the WAN . 98g3G.1.3 Communit
34、y Wi-Fi user outbound via public SSID 98g3G.1.4 Community Wi-Fi user inbound via public SSID 98g3Annex H (informative): Bibliography . 99g3Annex I (informative): Change history . 100g3History 101g3ETSI ETSI ES 203 386 V1.1.1 (2017-08) 7 Intellectual Property Rights Essential patents IPRs essential o
35、r potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Ess
36、ential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
37、 can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registe
38、red by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products
39、, services or organizations associated with those trademarks. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Integrated broadband cable telecommunication networks (CABLE). “DOCSISis a registered Trade Mark of Cable Television Laboratories, Inc., and is used in the pre
40、sent document with permission“. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of prov
41、isions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 203 386 V1.1.1 (2017-08) 8 1 Scope The present document defines a core set of features that enable multiple subscriber devices to gain access to operator provided high-speed data ser
42、vice 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 that is implemented in conjunction with a DOCSIS cable modem device. The core
43、 set of features defined in the present document 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 and among CPE devices. 2 References 2.1 Normative references Refe
44、rences are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced d
45、ocuments which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced docum
46、ents are necessary for the application of the present document. 1 CableLabs DHCP Options Registry Specification, CL-SP-CANN-DHCP-Reg-I13-160317, March 17, 2016, Cable Television Laboratories, Inc. 2 CableLabs Generic Route Encapsulation MIB, CLAB-GRE-MIB. NOTE: Available at http:/ 3 Cablelabs Wi-Fi
47、Gateway MIB, CLAB-GW-MIB. NOTE: Available at http:/ 4 eDOCSIS Specification, CM-SP-eDOCSIS-I28-150305, March 5, 2015, Cable Television Laboratories, Inc. 5 Universal Plug and Play Architecture Version 1.1, September 12, 2011. 6 DOCSIS MAC and Upper Layer Protocol Interface Specification, CM-SP-MULPI
48、v3.0-I29-151210, December 10, 2015, Cable Television Laboratories, Inc. 7 DOCSIS Operations Support System Interface Specification, CM-SP-OSSIv3.0-I28-151210, December 10, 2015, Cable Television Laboratories, Inc. 8 IETF RFC 792: “Internet Control Message Protocol“, J. Postel, September 1981. 9 IETF
49、 RFC 826: “An Ethernet Address Resolution Protocol“, David C. Plummer, November 1982. 10 IETF RFC 1122: “Requirements for Internet Hosts - Communication Layers“, R. Braden, October, 1989. 11 IETF RFC 1157: “Simple Network Management Protocol (SNMP)“, J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin, Simple Network Management Protocol (SNMP), May 1990. 12 IETF RFC 1812: “Requirements for IP Version 4 Routers“, F. Baker, June 1995. ETSI ETSI ES 203 386 V1.1.1 (2017-08) 9 13 IETF RFC 191
