ETSI ES 203 386 V1.1.1 (2017-08)

ETSI STANDARD
Integrated broadband cable
telecommunication networks (CABLE);
Embedded Router
2 ETSI ES 203 386 V1.1.1 (2017-08)

Reference
DES/CABLE-00009
Keywords
CABLE, DOCSIS, IPv4, IPv6, MODEM, router

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - 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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may 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 print, 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 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 reproduced 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 restriction extend to reproduction in all media.

© ETSI 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
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
3 ETSI ES 203 386 V1.1.1 (2017-08)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 11
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 14
4 Theory of operation . 16
4.0 General . 16
4.1 eDOCSIS eRouter and TR-069 architecture . 18
4.2 eRouter device management. 19
4.3 Service discovery . 19
4.3.0 General . 19
4.3.1 mDNS (multicast Domain Name System) . 20
4.3.2 UPnP (Universal Plug and Play) . 21
4.4 CER-ID (Customer Edge Router - Identification) . 21
5 eRouter initialization . 22
5.0 eRouter modes . 22
5.1 Network Time Protocol . 23
5.2 DNS proxy forwarding . 24
6 IPv4 provisioning . 24
6.0 General . 24
6.1 DHCPv4 fields used by the eRouter . 26
6.2 eRouter interface addressing using Link ID . 27
6.3 Router DHCPv4 server Sub-element . 28
6.3.1 DHCPv4 server function goals . 28
6.3.2 DHCPv4 server function system description . 28
6.3.3 DHCPv4 server function requirements . 28
6.4 Operator-facing IPv4 address release behavior . 30
6.5 Customer-facing IPv4 address release behavior . 30
7 Operator-facing IPv6 provisioning . 30
7.0 General . 30
7.1 Obtain link-local address . 31
7.2 Perform router discovery . 31
7.3 Obtain IPv6 address and other configuration parameters . 31
7.4 Use of T1 and T2 timers . 34
7.5 Customer-facing IPv6 provisioning of CPE devices . 34
7.5.0 Initial provisioning . 34
7.5.1 Additional customer-facing IP interfaces enabled after initial provisioning . 37
7.5.2 SLAAC requirements for eRouter . 37
7.5.2.0 General . 37
7.5.2.1 Local configuration of SLAAC options . 37
7.5.3 DHCPv6 requirements for eRouter . 37
7.5.3.0 General . 37
7.5.3.1 Local configuration of DHCPv6 options. 39
7.5.4 Prefix changes . 39
7.6 Operator-facing IPv6 address release behavior . 39
7.7 Customer-facing IPv6 address release behavior . 39
7.8 CER-ID requirements . 40
ETSI
4 ETSI ES 203 386 V1.1.1 (2017-08)
8 IPv4 data forwarding and NAPT operation . 40
8.0 Applicability . 40
8.1 Introduction . 40
8.1.1 Assumptions . 40
8.1.2 Overview . 40
8.2 System description . 41
8.3 IPv4 router . 42
8.3.0 Overview . 42
8.3.1 Dual IP protocol and Link ID enabled mode IPv4 routing . 43
8.4 NAPT . 44
8.4.0 General . 44
8.4.1 Dynamically triggered NAPT translation . 44
8.4.2 Application Layer Gateways (ALGs) . 45
8.4.2.0 General . 45
8.4.2.1 ICMP error message ALG . 45
8.4.2.2 FTP ALG . 45
8.4.3 Multicast NAPT . 45
8.5 ARP . 45
8.6 IPv4 multicast . 46
8.6.0 General . 46
8.6.1 IGMP proxying . 46
8.6.1.0 Operation . 46
8.6.1.1 IPv4 group membership database . 47
8.6.2 IPv4 multicast forwarding . 47
8.6.3 IPv4 multicast forwarding example . 48
8.7 IPv4/IPv6 co-existence technologies . 49
8.7.0 General . 49
8.7.1 Dual-stack Lite operation . 49
8.7.2 Mapping of Address and Port (MAP) . 49
8.7.2.0 MAP transport modes . 49
8.7.2.1 MAP-E or MAP-T configuration via DHCP . 50
8.7.2.2 MAP-E or MAP-T configuration via TLV202.11 . 50
8.7.3 Packet fragmentation . 50
9 IPv6 data forwarding . 51
9.0 Applicability . 51
9.1 Introduction . 51
9.1.1 Assumptions . 51
9.1.2 Overview . 51
9.2 System description . 52
9.3 IPv6 multicast . 53
9.3.0 General . 53
9.3.1 MLD proxying . 54
9.3.2 IPv6 group membership database . 55
9.3.3 IPv6 multicast forwarding . 55
9.3.4 IPv6 multicast forwarding example . 55
10 Quality of Service . 57
10.0 General requirements . 57
10.1 Downstream Quality of Service operation . 57
10.2 Upstream Quality of Service operation . 57
11 eRouter management . 57
11.0 General requirements . 57
11.1 eRouter SNMP management interface requirements. 58
11.2 eRouter TR-069 management interface requirements . 58
11.2.0 General requirements . 58
11.2.1 ACS discovery . 58
11.2.1.1 eRouter TR-069 management server configuration file TLV encapsulation . 58
11.2.1.2 TR-069 management server DHCP requirements . 58
11.2.2 ACS selection . 58
11.2.3 Dynamic ACS update . 58
11.2.4 TR-069 CWMP control and credentials . 58
ETSI
5 ETSI ES 203 386 V1.1.1 (2017-08)
12 Security. 59
13 eRouter tunnel management and configuration . 59
13.1 GRE requirements . 59
Annex A (normative): SNMP MIB objects supported by the eRouter . 60
A.0 List of MIB objects . 60
A.1 eRouter interface numbering . 60
A.2 eRouter ifTable requirements . 61
A.3 eRouter ipNetToPhysicalTable requirements . 63
A.4 CLAB-GRE-MIB . 63
A.5 CLAB-GW-MIB . 63
Annex B (normative): Configuration of eRouter operational parameters . 65
B.1 eRouter SNMP configuration . 65
B.1.1 eRouter SNMP modes of operation . 65
B.1.2 eRouter SNMP access control configuration . 65
B.1.2.1 View-based Access Control Model (VACM) profile . 65
B.1.3 SNMPv1v2c Coexistence Configuration. 65
B.1.3.0 General . 65
B.1.3.1 Mapping SNMPv1v2c Coexistence Configuration . 65
B.1.3.1.0 Overview . 65
B.1.3.1.1 snmpCommunityTable . 66
B.1.3.1.2 snmpTargetAddrTable . 66
B.1.3.1.3 snmpTargetAddrExtTable . 67
B.1.3.1.4 vacmSecurityToGroupTable . 67
B.1.3.1.5 vacmAccessTable . 68
B.1.3.2 Mapping SNMPv3 access view configuration . 68
B.1.3.2.0 Overview . 68
B.1.3.2.1 vacmViewTreeFamilyTable . 69
B.2 SNMP configuration of eRouter . 69
B.3 eCM proxy mechanism for configuration of eRouter . 70
B.4 eRouter configuration encodings . 70
B.4.1 eRouter TLV processing . 70
B.4.2 eRouter initialization mode encoding . 70
B.4.3 TR-069 management server . 71
B.4.3.0 General . 71
B.4.3.1 EnableCWMP . 71
B.4.3.2 URL . 71
B.4.3.3 Username . 71
B.4.3.4 Password . 71
B.4.3.5 ConnectionRequestUsername . 71
B.4.3.6 ConnectionRequestPassword . 72
B.4.3.7 ACS override . 72
B.4.4 eRouter initialization mode override . 72
B.4.5 SNMPv1v2c coexistence configuration . 72
B.4.5.0 General . 72
B.4.5.1 SNMPv1v2c community name . 72
B.4.5.2 SNMPv1v2c transport address access . 73
B.4.5.2.0 General . 73
B.4.5.2.1 SNMPv1v2c transport address . 73
B.4.5.2.2 SNMPv1v2c transport address mask . 73
B.4.5.3 SNMPv1v2c access view type . 73
B.4.5.4 SNMPv1v2c access view name . 73
B.4.6 SNMPv3 access view configuration . 73
B.4.6.0 General . 73
ETSI
6 ETSI ES 203 386 V1.1.1 (2017-08)
B.4.6.1 SNMPv3 access view name . 74
B.4.6.2 SNMPv3 access view subtree . 74
B.4.6.3 SNMPv3 access view mask . 74
B.4.6.4 SNMPv3 access view type . 74
B.4.7 Vendor specific information . 75
B.4.7.0 General . 75
B.4.7.1 Vendor ID encoding. 75
B.4.8 SNMP MIB object . 75
B.4.9 Topology mode encoding . 75
B.4.10 Router Advertisement (RA) transmission interval . 76
B.4.11 IP multicast configuration server . 76
B.4.12 Link ID control . 76
B.5 SNMP soft reset . 76
B.6 Provisioning and operational event messages . 77
Annex C (normative): eRouter initialization mode control interactions . 80
C.1 Valid interactions . 80
C.2 Invalid Cases . 82
Annex D (normative): TR-069 managed objects requirements . 83
D.0 General . 83
D.1 Profiles from TR-181 . 83
D.2 Extensions to TR-181 profiles . 84
D.3 Management interface protocol requirements for GRE . 85
Annex E (normative): Example: Routing with Link ID . 87
E.0 Addressing scheme . 87
E.1 IP MIB route example . 88
Annex F (normative): Section categorizing [49] simple security recommendations . 89
F.1 Summary of simple security requirements . 89
F.2 Critical recommendations. 89
F.3 Important recommendations . 91
F.4 BCP recommendations . 92
F.5 Other recommendations . 94
F.6 Recommendations in conflict with MSO needs . 95
Annex G (normative): eRouter GRE tunnelling architecture . 96
G.0 Architecture and interfaces . 96
G.1 Use case for data traffic flow for both private and public SSIDs . 97
G.1.0 Overview . 97
G.1.1 Private network outbound from the LAN . 98
G.1.2 Private network inbound from the WAN . 98
G.1.3 Community Wi-Fi user outbound via public SSID . 98
G.1.4 Community Wi-Fi user inbound via public SSID . 98
Annex H (informative): Bibliography . 99
Annex I (informative): Change history . 100
History . 101

ETSI
7 ETSI ES 203 386 V1.1.1 (2017-08)
Intellectual Property Rights
Essential patents
IPRs essential or 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 Essential, 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
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 registered 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, 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). ®
"DOCSIS is a registered Trade Mark of Cable Television Laboratories, Inc., and is used in the present 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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
8 ETSI ES 203 386 V1.1.1 (2017-08)
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 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 that is implemented in
conjunction with a DOCSIS cable modem device.
The core 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
References 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 documents 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 documents 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://www.cablelabs.com/MIBs/common/.
[3] Cablelabs Wi-Fi Gateway MIB, CLAB-GW-MIB.
NOTE: Available at http://www.cablelabs.com/MIBs/common/.
[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-MULPIv3.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 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
9 ETSI ES 203 386 V1.1.1 (2017-08)
[13] IETF RFC 1918: "Address Allocation for Private Internets", Y. Rekhter, B. Moskowitz,
D. Karrenberg, G. J. de Groot, E. Lear, February 1996.
[14] IETF RFC 2131: "Dynamic Host Configuration Protocol", R. Droms, March 1997.
[15] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions", S. Alexander, R. Droms,
March 1997.
[16] IETF RFC 2710: "Multicast Listener Discovery (MLD) for IPv6", S. Deering, W. Fenner,
B. Haberman, October 1999.
[17] IETF RFC 2784: "Generic Routing Encapsulation (GRE)", D. Farinacci, T. Li, S. Hanks,
D. Meyer, P. Traina, March 2000.
[18] IETF RFC 2827: "Network Ingress Filtering: Defeating Denial of Service Attacks which employ
IP Source Address Spoofing", P. Ferguson, D. Senie, May 2000.
[19] IETF RFC 2863: "The Interfaces Group MIB", K. McCloghrie, F. Kastenholz, June 2000.
[20] IETF RFC 2890: "Key and Sequence Number Extensions to GRE", G. Dommety,
September 2000.
[21] IETF RFC 3022: "Traditional IP Network Address Translator (Traditional NAT)", P. Srisuresh,
K. Egevang, January 2001.
[22] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", R. Droms, Ed.,
J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney, July 2003.
[23] IETF RFC 3376: "Internet Group Management Protocol, Version 3", B. Cain, S. Deering,
I. Kouvelas, B. Fenner, A. Thyagarajan, October 2002.
[24] IETF RFC 3412: "Message Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", J. Case, D. Harrington, R. Presuhn, B. Wijnen, December 2002.
[25] IETF RFC 3413: "Simple Network Management Protocol (SNMP) Applications", D. Levi,
P. Meyer, B. Stuwart, December 2002.
[26] IETF RFC 3415: "View-based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", B. Wijnen, R. Presuhn, K. McCloghrie, December 2002.
[27] IETF RFC 3417: "Transport Mappings for the Simple Network Management Protocol (SNMP)",
R. Presuhn, December 2002.
[28] IETF RFC 3419: "Textual Conventions for Transport Addresses, M. Daniels", J. Schoenwaelder,
December 2002.
[29] IETF RFC 3584: "Coexistence between Version 1, Version 2, and Version 3 of the Internet-
standard Network Management Framework", R. Frye, D. Levi, S. Routhier, B. Wijnen,
August 2003.
[30] IETF RFC 3633: "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP)
version 6", O. Troan, R. Droms, December 2003.
[31] IETF RFC 3646: "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", R. Droms, December 2003.
[32] IETF RFC 3736: "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6",
R. Droms, April 2004.
[33] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", R. Vida, Ed.,
L. Costa, Ed., June 2004.
[34] IETF RFC 4075: "Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6",
V. Kalusivalingam, Cisco Systems, May 2005.
ETSI
10 ETSI ES 203 386 V1.1.1 (2017-08)
[35] IETF RFC 4191: "Default Router Preferences and More-Specific Routes", R. Draves, D. Thaler,
November 2005.
[36] IETF RFC 4242: "Information Refresh Time Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", S. Venaas, T. Chown, B. Volz, November 2005.
[37] IETF RFC 4291: "IP Version 6 Addressing Architecture", R. Hinden, S. Deering, February 2006.
[38] IETF RFC 4292: "IP Forwarding Table MIB", B. Haberman, April 2006.
[39] IETF RFC 4293: "Management Information Base for the Internet Protocol (IP)", S. Routhier,
(Editor), Bill Fenner, Brian Haberman, Dave Thaler, April 2006.
[40] IETF RFC 4361: "Node-specific Client Identifiers for Dynamic Host Configuration Protocol
Version Four (DHCPv4)", T. Lemon, B. Sommerfeld, February 2006.
[41] IETF RFC 4443: "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6
(IPv6) Specification", A. Conta, S. Deering, M. Gupta, Ed., March 2006.
[42] IETF RFC 4861: "Neighbor Discovery for IP Version 6 (IPv6)", T. Narten, E. Nordmark,
W. Simpson, H. Soliman, September 2007.
[43] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration", S. Thomson, T. Narten, T. Jinmei,
September 2007.
[44] IETF RFC 4884: "Extended ICMP to Support Multi-Part Messages", R. Bonica, D. Gan,
D. Tappan, C. Pignataro, April 2007.
[45] IETF RFC 5389: "Session Traversal Utilities for NAT (STUN)", J. Rosenberg. R, Mahy,
P. Matthews, D. Wing, October 2008.
[46] IETF RFC 5905: "Network Time Protocol version 4: Protocol and Algorithms Specification",
D. Mills, U. Delaware, J. Martin, Ed., J. Burbank, W. Kasc
...

SLOVENSKI STANDARD
01-maj-2018
Integrirana širokopasovna kabelska telekomunikacijska omrežja (CABLE) -
Vgrajeni usmerjevalnik
Integrated broadband cable telecommunication networks (CABLE) - Embedded Router
Ta slovenski standard je istoveten z: ETSI ES 203 386 V1.1.1 (2017-08)
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI STANDARD
Integrated broadband cable
telecommunication networks (CABLE);
Embedded Router
2 ETSI ES 203 386 V1.1.1 (2017-08)

Reference
DES/CABLE-00009
Keywords
CABLE, DOCSIS, IPv4, IPv6, MODEM, router

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - 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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may 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 print, 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 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 reproduced 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 restriction extend to reproduction in all media.

© ETSI 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
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
3 ETSI ES 203 386 V1.1.1 (2017-08)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 11
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 14
4 Theory of operation . 16
4.0 General . 16
4.1 eDOCSIS eRouter and TR-069 architecture . 18
4.2 eRouter device management. 19
4.3 Service discovery . 19
4.3.0 General . 19
4.3.1 mDNS (multicast Domain Name System) . 20
4.3.2 UPnP (Universal Plug and Play) . 21
4.4 CER-ID (Customer Edge Router - Identification) . 21
5 eRouter initialization . 22
5.0 eRouter modes . 22
5.1 Network Time Protocol . 23
5.2 DNS proxy forwarding . 24
6 IPv4 provisioning . 24
6.0 General . 24
6.1 DHCPv4 fields used by the eRouter . 26
6.2 eRouter interface addressing using Link ID . 27
6.3 Router DHCPv4 server Sub-element . 28
6.3.1 DHCPv4 server function goals . 28
6.3.2 DHCPv4 server function system description . 28
6.3.3 DHCPv4 server function requirements . 28
6.4 Operator-facing IPv4 address release behavior . 30
6.5 Customer-facing IPv4 address release behavior . 30
7 Operator-facing IPv6 provisioning . 30
7.0 General . 30
7.1 Obtain link-local address . 31
7.2 Perform router discovery . 31
7.3 Obtain IPv6 address and other configuration parameters . 31
7.4 Use of T1 and T2 timers . 34
7.5 Customer-facing IPv6 provisioning of CPE devices . 34
7.5.0 Initial provisioning . 34
7.5.1 Additional customer-facing IP interfaces enabled after initial provisioning . 37
7.5.2 SLAAC requirements for eRouter . 37
7.5.2.0 General . 37
7.5.2.1 Local configuration of SLAAC options . 37
7.5.3 DHCPv6 requirements for eRouter . 37
7.5.3.0 General . 37
7.5.3.1 Local configuration of DHCPv6 options. 39
7.5.4 Prefix changes . 39
7.6 Operator-facing IPv6 address release behavior . 39
7.7 Customer-facing IPv6 address release behavior . 39
7.8 CER-ID requirements . 40
ETSI
4 ETSI ES 203 386 V1.1.1 (2017-08)
8 IPv4 data forwarding and NAPT operation . 40
8.0 Applicability . 40
8.1 Introduction . 40
8.1.1 Assumptions . 40
8.1.2 Overview . 40
8.2 System description . 41
8.3 IPv4 router . 42
8.3.0 Overview . 42
8.3.1 Dual IP protocol and Link ID enabled mode IPv4 routing . 43
8.4 NAPT . 44
8.4.0 General . 44
8.4.1 Dynamically triggered NAPT translation . 44
8.4.2 Application Layer Gateways (ALGs) . 45
8.4.2.0 General . 45
8.4.2.1 ICMP error message ALG . 45
8.4.2.2 FTP ALG . 45
8.4.3 Multicast NAPT . 45
8.5 ARP . 45
8.6 IPv4 multicast . 46
8.6.0 General . 46
8.6.1 IGMP proxying . 46
8.6.1.0 Operation . 46
8.6.1.1 IPv4 group membership database . 47
8.6.2 IPv4 multicast forwarding . 47
8.6.3 IPv4 multicast forwarding example . 48
8.7 IPv4/IPv6 co-existence technologies . 49
8.7.0 General . 49
8.7.1 Dual-stack Lite operation . 49
8.7.2 Mapping of Address and Port (MAP) . 49
8.7.2.0 MAP transport modes . 49
8.7.2.1 MAP-E or MAP-T configuration via DHCP . 50
8.7.2.2 MAP-E or MAP-T configuration via TLV202.11 . 50
8.7.3 Packet fragmentation . 50
9 IPv6 data forwarding . 51
9.0 Applicability . 51
9.1 Introduction . 51
9.1.1 Assumptions . 51
9.1.2 Overview . 51
9.2 System description . 52
9.3 IPv6 multicast . 53
9.3.0 General . 53
9.3.1 MLD proxying . 54
9.3.2 IPv6 group membership database . 55
9.3.3 IPv6 multicast forwarding . 55
9.3.4 IPv6 multicast forwarding example . 55
10 Quality of Service . 57
10.0 General requirements . 57
10.1 Downstream Quality of Service operation . 57
10.2 Upstream Quality of Service operation . 57
11 eRouter management . 57
11.0 General requirements . 57
11.1 eRouter SNMP management interface requirements. 58
11.2 eRouter TR-069 management interface requirements . 58
11.2.0 General requirements . 58
11.2.1 ACS discovery . 58
11.2.1.1 eRouter TR-069 management server configuration file TLV encapsulation . 58
11.2.1.2 TR-069 management server DHCP requirements . 58
11.2.2 ACS selection . 58
11.2.3 Dynamic ACS update . 58
11.2.4 TR-069 CWMP control and credentials . 58
ETSI
5 ETSI ES 203 386 V1.1.1 (2017-08)
12 Security. 59
13 eRouter tunnel management and configuration . 59
13.1 GRE requirements . 59
Annex A (normative): SNMP MIB objects supported by the eRouter . 60
A.0 List of MIB objects . 60
A.1 eRouter interface numbering . 60
A.2 eRouter ifTable requirements . 61
A.3 eRouter ipNetToPhysicalTable requirements . 63
A.4 CLAB-GRE-MIB . 63
A.5 CLAB-GW-MIB . 63
Annex B (normative): Configuration of eRouter operational parameters . 65
B.1 eRouter SNMP configuration . 65
B.1.1 eRouter SNMP modes of operation . 65
B.1.2 eRouter SNMP access control configuration . 65
B.1.2.1 View-based Access Control Model (VACM) profile . 65
B.1.3 SNMPv1v2c Coexistence Configuration. 65
B.1.3.0 General . 65
B.1.3.1 Mapping SNMPv1v2c Coexistence Configuration . 65
B.1.3.1.0 Overview . 65
B.1.3.1.1 snmpCommunityTable . 66
B.1.3.1.2 snmpTargetAddrTable . 66
B.1.3.1.3 snmpTargetAddrExtTable . 67
B.1.3.1.4 vacmSecurityToGroupTable . 67
B.1.3.1.5 vacmAccessTable . 68
B.1.3.2 Mapping SNMPv3 access view configuration . 68
B.1.3.2.0 Overview . 68
B.1.3.2.1 vacmViewTreeFamilyTable . 69
B.2 SNMP configuration of eRouter . 69
B.3 eCM proxy mechanism for configuration of eRouter . 70
B.4 eRouter configuration encodings . 70
B.4.1 eRouter TLV processing . 70
B.4.2 eRouter initialization mode encoding . 70
B.4.3 TR-069 management server . 71
B.4.3.0 General . 71
B.4.3.1 EnableCWMP . 71
B.4.3.2 URL . 71
B.4.3.3 Username . 71
B.4.3.4 Password . 71
B.4.3.5 ConnectionRequestUsername . 71
B.4.3.6 ConnectionRequestPassword . 72
B.4.3.7 ACS override . 72
B.4.4 eRouter initialization mode override . 72
B.4.5 SNMPv1v2c coexistence configuration . 72
B.4.5.0 General . 72
B.4.5.1 SNMPv1v2c community name . 72
B.4.5.2 SNMPv1v2c transport address access . 73
B.4.5.2.0 General . 73
B.4.5.2.1 SNMPv1v2c transport address . 73
B.4.5.2.2 SNMPv1v2c transport address mask . 73
B.4.5.3 SNMPv1v2c access view type . 73
B.4.5.4 SNMPv1v2c access view name . 73
B.4.6 SNMPv3 access view configuration . 73
B.4.6.0 General . 73
ETSI
6 ETSI ES 203 386 V1.1.1 (2017-08)
B.4.6.1 SNMPv3 access view name . 74
B.4.6.2 SNMPv3 access view subtree . 74
B.4.6.3 SNMPv3 access view mask . 74
B.4.6.4 SNMPv3 access view type . 74
B.4.7 Vendor specific information . 75
B.4.7.0 General . 75
B.4.7.1 Vendor ID encoding. 75
B.4.8 SNMP MIB object . 75
B.4.9 Topology mode encoding . 75
B.4.10 Router Advertisement (RA) transmission interval . 76
B.4.11 IP multicast configuration server . 76
B.4.12 Link ID control . 76
B.5 SNMP soft reset . 76
B.6 Provisioning and operational event messages . 77
Annex C (normative): eRouter initialization mode control interactions . 80
C.1 Valid interactions . 80
C.2 Invalid Cases . 82
Annex D (normative): TR-069 managed objects requirements . 83
D.0 General . 83
D.1 Profiles from TR-181 . 83
D.2 Extensions to TR-181 profiles . 84
D.3 Management interface protocol requirements for GRE . 85
Annex E (normative): Example: Routing with Link ID . 87
E.0 Addressing scheme . 87
E.1 IP MIB route example . 88
Annex F (normative): Section categorizing [49] simple security recommendations . 89
F.1 Summary of simple security requirements . 89
F.2 Critical recommendations. 89
F.3 Important recommendations . 91
F.4 BCP recommendations . 92
F.5 Other recommendations . 94
F.6 Recommendations in conflict with MSO needs . 95
Annex G (normative): eRouter GRE tunnelling architecture . 96
G.0 Architecture and interfaces . 96
G.1 Use case for data traffic flow for both private and public SSIDs . 97
G.1.0 Overview . 97
G.1.1 Private network outbound from the LAN . 98
G.1.2 Private network inbound from the WAN . 98
G.1.3 Community Wi-Fi user outbound via public SSID . 98
G.1.4 Community Wi-Fi user inbound via public SSID . 98
Annex H (informative): Bibliography . 99
Annex I (informative): Change history . 100
History . 101

ETSI
7 ETSI ES 203 386 V1.1.1 (2017-08)
Intellectual Property Rights
Essential patents
IPRs essential or 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 Essential, 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
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 registered 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, 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). ®
"DOCSIS is a registered Trade Mark of Cable Television Laboratories, Inc., and is used in the present 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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
8 ETSI ES 203 386 V1.1.1 (2017-08)
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 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 that is implemented in
conjunction with a DOCSIS cable modem device.
The core 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
References 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 documents 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 documents 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://www.cablelabs.com/MIBs/common/.
[3] Cablelabs Wi-Fi Gateway MIB, CLAB-GW-MIB.
NOTE: Available at http://www.cablelabs.com/MIBs/common/.
[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-MULPIv3.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 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
9 ETSI ES 203 386 V1.1.1 (2017-08)
[13] IETF RFC 1918: "Address Allocation for Private Internets", Y. Rekhter, B. Moskowitz,
D. Karrenberg, G. J. de Groot, E. Lear, February 1996.
[14] IETF RFC 2131: "Dynamic Host Configuration Protocol", R. Droms, March 1997.
[15] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions", S. Alexander, R. Droms,
March 1997.
[16] IETF RFC 2710: "Multicast Listener Discovery (MLD) for IPv6", S. Deering, W. Fenner,
B. Haberman, October 1999.
[17] IETF RFC 2784: "Generic Routing Encapsulation (GRE)", D. Farinacci, T. Li, S. Hanks,
D. Meyer, P. Traina, March 2000.
[18] IETF RFC 2827: "Network Ingress Filtering: Defeating Denial of Service Attacks which employ
IP Source Address Spoofing", P. Ferguson, D. Senie, May 2000.
[19] IETF RFC 2863: "The Interfaces Group MIB", K. McCloghrie, F. Kastenholz, June 2000.
[20] IETF RFC 2890: "Key and Sequence Number Extensions to GRE", G. Dommety,
September 2000.
[21] IETF RFC 3022: "Traditional IP Network Address Translator (Traditional NAT)", P. Srisuresh,
K. Egevang, January 2001.
[22] IETF RFC 3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", R. Droms, Ed.,
J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney, July 2003.
[23] IETF RFC 3376: "Internet Group Management Protocol, Version 3", B. Cain, S. Deering,
I. Kouvelas, B. Fenner, A. Thyagarajan, October 2002.
[24] IETF RFC 3412: "Message Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", J. Case, D. Harrington, R. Presuhn, B. Wijnen, December 2002.
[25] IETF RFC 3413: "Simple Network Management Protocol (SNMP) Applications", D. Levi,
P. Meyer, B. Stuwart, December 2002.
[26] IETF RFC 3415: "View-based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", B. Wijnen, R. Presuhn, K. McCloghrie, December 2002.
[27] IETF RFC 3417: "Transport Mappings for the Simple Network Management Protocol (SNMP)",
R. Presuhn, December 2002.
[28] IETF RFC 3419: "Textual Conventions for Transport Addresses, M. Daniels", J. Schoenwaelder,
December 2002.
[29] IETF RFC 3584: "Coexistence between Version 1, Version 2, and Version 3 of the Internet-
standard Network Management Framework", R. Frye, D. Levi, S. Routhier, B. Wijnen,
August 2003.
[30] IETF RFC 3633: "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP)
version 6", O. Troan, R. Droms, December 2003.
[31] IETF RFC 3646: "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", R. Droms, December 2003.
[32] IETF RFC 3736: "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6",
R. Droms, April 2004.
[33] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", R. Vida, Ed.,
L. Costa, Ed., June 2004.
[34] IETF RFC 4075: "Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6",
V. Kalusivalingam, Cisco Systems, May 2005.
ETSI
10 ETSI ES 203 386 V1.1.1 (2017-08)
[35] IETF RFC 4191: "Default Router Preferences and More-Specific Routes", R. Draves, D. Thaler,
November 2005.
[36] IETF RFC 4242: "Information Refresh Time Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", S. Venaas, T. Chown, B. Volz, November 2005.
[37] IETF RFC 4291: "IP Version 6 Addressing Architecture", R. Hinden, S. Deering, February 2006.
[38] IETF RFC 4292: "IP Forwarding Table MIB", B. Haberman, April 2006.
[39] IETF RFC 4293: "Management Information Base for the Internet Proto
...