1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
|
<pre>Internet Engineering Task Force (IETF) H. Singh
Request for Comments: 7084 W. Beebee
Obsoletes: <a href="./rfc6204">6204</a> Cisco Systems, Inc.
Category: Informational C. Donley
ISSN: 2070-1721 CableLabs
B. Stark
AT&T
November 2013
<span class="h1">Basic Requirements for IPv6 Customer Edge Routers</span>
Abstract
This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. The document also covers IP transition
technologies. Two transition technologies in <a href="./rfc5969">RFC 5969</a>'s IPv6 Rapid
Deployment on IPv4 Infrastructures (6rd) and <a href="./rfc6333">RFC 6333</a>'s Dual-Stack
Lite (DS-Lite) are covered in the document. The document obsoletes
<a href="./rfc6204">RFC 6204</a>.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7084">http://www.rfc-editor.org/info/rfc7084</a>.
<span class="grey">Singh, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Architecture ....................................................<a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Current IPv4 End-User Network Architecture .................<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. IPv6 End-User Network Architecture .........................<a href="#page-5">5</a>
<a href="#section-3.2.1">3.2.1</a>. Local Communication .................................<a href="#page-7">7</a>
<a href="#section-4">4</a>. Requirements ....................................................<a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. General Requirements .......................................<a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. WAN-Side Configuration .....................................<a href="#page-8">8</a>
<a href="#section-4.3">4.3</a>. LAN-Side Configuration ....................................<a href="#page-12">12</a>
<a href="#section-4.4">4.4</a>. Transition Technologies Support ...........................<a href="#page-14">14</a>
<a href="#section-4.4.1">4.4.1</a>. 6rd ................................................<a href="#page-14">14</a>
<a href="#section-4.4.2">4.4.2</a>. Dual-Stack Lite (DS-Lite) ..........................<a href="#page-15">15</a>
<a href="#section-4.5">4.5</a>. Security Considerations ...................................<a href="#page-16">16</a>
<a href="#section-5">5</a>. Acknowledgements ...............................................<a href="#page-17">17</a>
<a href="#section-6">6</a>. Contributors ...................................................<a href="#page-17">17</a>
<a href="#section-7">7</a>. References .....................................................<a href="#page-18">18</a>
<a href="#section-7.1">7.1</a>. Normative References ......................................<a href="#page-18">18</a>
<a href="#section-7.2">7.2</a>. Informative References ....................................<a href="#page-20">20</a>
<span class="grey">Singh, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines basic IPv6 features for a residential or small-
office router, referred to as an "IPv6 CE router", in order to
establish an industry baseline for features to be implemented on such
a router.
These routers typically also support IPv4.
Mixed environments of dual-stack hosts and IPv6-only hosts (behind
the CE router) can be more complex if the IPv6-only devices are using
a translator to access IPv4 servers [<a href="./rfc6144" title=""Framework for IPv4/IPv6 Translation"">RFC6144</a>]. Support for such
mixed environments is not in scope of this document.
This document specifies how an IPv6 CE router automatically
provisions its WAN interface, acquires address space for provisioning
of its LAN interfaces, and fetches other configuration information
from the service provider network. Automatic provisioning of more
complex topology than a single router with multiple LAN interfaces is
out of scope for this document.
See [<a href="./rfc4779" title=""ISP IPv6 Deployment Scenarios in Broadband Access Networks"">RFC4779</a>] for a discussion of options available for deploying
IPv6 in service provider access networks.
The document also covers the IP transition technologies that were
available at the time this document was written. Two transition
technologies in 6rd [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>] and DS-Lite [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] are covered in
the document.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
Take careful note: Unlike other IETF documents, the key words "MUST",
"MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are not used as
described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. This document uses these keywords
not strictly for the purpose of interoperability, but rather for the
purpose of establishing industry-common baseline functionality. As
such, the document points to several other specifications (preferable
in RFC or stable form) to provide additional guidance to implementers
regarding any protocol implementation required to produce a
successful CE router that interoperates successfully with a
particular subset of currently deploying and planned common IPv6
access networks.
<span class="grey">Singh, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
End-User Network one or more links attached to the IPv6 CE
router that connect IPv6 hosts.
IPv6 Customer Edge Router a node intended for home or small-office
use that forwards IPv6 packets not
explicitly addressed to itself. The IPv6
CE router connects the end-user network to
a service provider network.
IPv6 Host any device implementing an IPv6 stack
receiving IPv6 connectivity through the
IPv6 CE router.
LAN Interface an IPv6 CE router's attachment to a link in
the end-user network. Examples are
Ethernet (simple or bridged), 802.11
wireless, or other LAN technologies. An
IPv6 CE router may have one or more
network-layer LAN interfaces.
Service Provider an entity that provides access to the
Internet. In this document, a service
provider specifically offers Internet
access using IPv6, and it may also offer
IPv4 Internet access. The service provider
can provide such access over a variety of
different transport methods such as DSL,
cable, wireless, and others.
WAN Interface an IPv6 CE router's attachment to a link
used to provide connectivity to the service
provider network; example link technologies
include Ethernet (simple or bridged), PPP
links, Frame Relay, or ATM networks, as
well as Internet-layer (or higher-layer)
"tunnels", such as tunnels over IPv4 or
IPv6 itself.
<span class="grey">Singh, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Architecture</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Current IPv4 End-User Network Architecture</span>
An end-user network will likely support both IPv4 and IPv6. It is
not expected that an end user will change their existing network
topology with the introduction of IPv6. There are some differences
in how IPv6 works and is provisioned; these differences have
implications for the network architecture. A typical IPv4 end-user
network consists of a "plug and play" router with NAT functionality
and a single link behind it, connected to the service provider
network.
A typical IPv4 NAT deployment by default blocks all incoming
connections. Opening of ports is typically allowed using a Universal
Plug and Play Internet Gateway Device (UPnP IGD) [<a href="#ref-UPnP-IGD" title=""InternetGatewayDevice:2 Device Template Version 1.01"">UPnP-IGD</a>] or some
other firewall control protocol.
Another consequence of using private address space in the end-user
network is that it provides stable addressing; that is, it never
changes even when you change service providers, and the addresses are
always there even when the WAN interface is down or the customer edge
router has not yet been provisioned.
Many existing routers support dynamic routing (which learns routes
from other routers), and advanced end-users can build arbitrary,
complex networks using manual configuration of address prefixes
combined with a dynamic routing protocol.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. IPv6 End-User Network Architecture</span>
The end-user network architecture for IPv6 should provide equivalent
or better capabilities and functionality than the current IPv4
architecture.
<span class="grey">Singh, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
The end-user network is a stub network. Figure 1 illustrates the
model topology for the end-user network.
+-------+-------+ \
| Service | \
| Provider | | Service
| Router | | Provider
+-------+-------+ | Network
| /
| Customer /
| Internet Connection /
|
+------+--------+ \
| IPv6 | \
| Customer Edge | \
| Router | /
+---+-------+-+-+ /
Network A | | Network B | End-User
---+-------------+----+- --+--+-------------+--- | Network(s)
| | | | \
+----+-----+ +-----+----+ +----+-----+ +-----+----+ \
|IPv6 Host | |IPv6 Host | | IPv6 Host| |IPv6 Host | /
| | | | | | | | /
+----------+ +-----+----+ +----------+ +----------+ /
Figure 1: An Example of a Typical End-User Network
This architecture describes the:
o Basic capabilities of an IPv6 CE router
o Provisioning of the WAN interface connecting to the service
provider
o Provisioning of the LAN interfaces
For IPv6 multicast traffic, the IPv6 CE router may act as a Multicast
Listener Discovery (MLD) proxy [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] and may support a dynamic
multicast routing protocol.
The IPv6 CE router may be manually configured in an arbitrary
topology with a dynamic routing protocol. Automatic provisioning and
configuration are described for a single IPv6 CE router only.
<span class="grey">Singh, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Local Communication</span>
Link-local IPv6 addresses are used by hosts communicating on a single
link. Unique Local IPv6 Unicast Addresses (ULAs) [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>] are used
by hosts communicating within the end-user network across multiple
links, but without requiring the application to use a globally
routable address. The IPv6 CE router defaults to acting as the
demarcation point between two networks by providing a ULA boundary, a
multicast zone boundary, and ingress and egress traffic filters.
At the time of this writing, several host implementations do not
handle the case where they have an IPv6 address configured and no
IPv6 connectivity, either because the address itself has a limited
topological reachability (e.g., ULA) or because the IPv6 CE router is
not connected to the IPv6 network on its WAN interface. To support
host implementations that do not handle multihoming in a multi-prefix
environment [<a href="#ref-MULTIHOMING-WITHOUT-NAT">MULTIHOMING-WITHOUT-NAT</a>], the IPv6 CE router should not,
as detailed in the requirements below, advertise itself as a default
router on the LAN interface(s) when it does not have IPv6
connectivity on the WAN interface or when it is not provisioned with
IPv6 addresses. For local IPv6 communication, the mechanisms
specified in [<a href="./rfc4191" title=""Default Router Preferences and More-Specific Routes"">RFC4191</a>] are used.
ULA addressing is useful where the IPv6 CE router has multiple LAN
interfaces with hosts that need to communicate with each other. If
the IPv6 CE router has only a single LAN interface (IPv6 link), then
link-local addressing can be used instead.
Coexistence with IPv4 requires any IPv6 CE router(s) on the LAN to
conform to these recommendations, especially requirements ULA-5 and
L-4 below.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Requirements</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General Requirements</span>
The IPv6 CE router is responsible for implementing IPv6 routing; that
is, the IPv6 CE router must look up the IPv6 destination address in
its routing table to decide to which interface it should send the
packet.
In this role, the IPv6 CE router is responsible for ensuring that
traffic using its ULA addressing does not go out the WAN interface
and does not originate from the WAN interface.
<span class="grey">Singh, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
G-1: An IPv6 CE router is an IPv6 node according to the IPv6 Node
Requirements specification [<a href="./rfc6434" title=""IPv6 Node Requirements"">RFC6434</a>].
G-2: The IPv6 CE router MUST implement ICMPv6 according to
[<a href="./rfc4443" title=""Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"">RFC4443</a>]. In particular, point-to-point links MUST be handled
as described in <a href="./rfc4443#section-3.1">Section 3.1 of [RFC4443]</a>.
G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between
its LAN interface(s) and its WAN interface until the router has
successfully completed the IPv6 address and the delegated
prefix acquisition process.
G-4: By default, an IPv6 CE router that has no default router(s) on
its WAN interface MUST NOT advertise itself as an IPv6 default
router on its LAN interfaces. That is, the "Router Lifetime"
field is set to zero in all Router Advertisement messages it
originates [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
G-5: By default, if the IPv6 CE router is an advertising router and
loses its IPv6 default router(s) and/or detects loss of
connectivity on the WAN interface, it MUST explicitly
invalidate itself as an IPv6 default router on each of its
advertising interfaces by immediately transmitting one or more
Router Advertisement messages with the "Router Lifetime" field
set to zero [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. WAN-Side Configuration</span>
The IPv6 CE router will need to support connectivity to one or more
access network architectures. This document describes an IPv6 CE
router that is not specific to any particular architecture or service
provider and that supports all commonly used architectures.
IPv6 Neighbor Discovery and DHCPv6 protocols operate over any type of
IPv6-supported link layer, and there is no need for a link-layer-
specific configuration protocol for IPv6 network-layer configuration
options as in, e.g., PPP IP Control Protocol (IPCP) for IPv4. This
section makes the assumption that the same mechanism will work for
any link layer, be it Ethernet, the Data Over Cable Service Interface
Specification (DOCSIS), PPP, or others.
<span class="grey">Singh, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
WAN-side requirements:
W-1: When the router is attached to the WAN interface link, it MUST
act as an IPv6 host for the purposes of stateless [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>] or
stateful [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] interface address assignment.
W-2: The IPv6 CE router MUST generate a link-local address and
finish Duplicate Address Detection according to [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>] prior
to sending any Router Solicitations on the interface. The
source address used in the subsequent Router Solicitation MUST
be the link-local address on the WAN interface.
W-3: Absent other routing information, the IPv6 CE router MUST use
Router Discovery as specified in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] to discover a
default router(s) and install a default route(s) in its routing
table with the discovered router's address as the next hop.
W-4: The router MUST act as a requesting router for the purposes of
DHCPv6 prefix delegation ([<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>]).
W-5: The IPv6 CE router MUST use a persistent DHCP Unique Identifier
(DUID) for DHCPv6 messages. The DUID MUST NOT change between
network-interface resets or IPv6 CE router reboots.
W-6: The WAN interface of the CE router SHOULD support a Port
Control Protocol (PCP) client as specified in [<a href="./rfc6887" title=""Port Control Protocol (PCP)"">RFC6887</a>] for use
by applications on the CE router. The PCP client SHOULD follow
the procedure specified in <a href="./rfc6887#section-8.1">Section 8.1 of [RFC6887]</a> to discover
its PCP server. This document takes no position on whether
such functionality is enabled by default or mechanisms by which
users would configure the functionality. Handling PCP requests
from PCP clients in the LAN side of the CE router is out of
scope.
Link-layer requirements:
WLL-1: If the WAN interface supports Ethernet encapsulation, then
the IPv6 CE router MUST support IPv6 over Ethernet [<a href="./rfc2464" title=""Transmission of IPv6 Packets over Ethernet Networks"">RFC2464</a>].
WLL-2: If the WAN interface supports PPP encapsulation, the IPv6 CE
router MUST support IPv6 over PPP [<a href="./rfc5072" title=""IP Version 6 over PPP"">RFC5072</a>].
WLL-3: If the WAN interface supports PPP encapsulation, in a dual-
stack environment with IPCP and IPV6CP running over one PPP
logical channel, the Network Control Protocols (NCPs) MUST be
treated as independent of each other and start and terminate
independently.
<span class="grey">Singh, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
Address assignment requirements:
WAA-1: The IPv6 CE router MUST support Stateless Address
Autoconfiguration (SLAAC) [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>].
WAA-2: The IPv6 CE router MUST follow the recommendations in
<a href="./rfc5942#section-4">Section 4 of [RFC5942]</a>, and in particular the handling of
the L flag in the Router Advertisement Prefix Information
option.
WAA-3: The IPv6 CE router MUST support DHCPv6 [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] client
behavior.
WAA-4: The IPv6 CE router MUST be able to support the following
DHCPv6 options: Identity Association for Non-temporary
Address (IA_NA), Reconfigure Accept [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>], and
DNS_SERVERS [<a href="./rfc3646" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3646</a>]. The IPv6 CE router SHOULD be able to
support the DNS Search List (DNSSL) option as specified in
[<a href="./rfc3646" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3646</a>].
WAA-5: The IPv6 CE router SHOULD implement the Network Time
Protocol (NTP) as specified in [<a href="./rfc5905" title=""Network Time Protocol Version 4: Protocol and Algorithms Specification"">RFC5905</a>] to provide a time
reference common to the service provider for other
protocols, such as DHCPv6, to use. If the CE router
implements NTP, it requests the NTP Server DHCPv6 option
[<a href="./rfc5908" title=""Network Time Protocol (NTP) Server Option for DHCPv6"">RFC5908</a>] and uses the received list of servers as primary
time reference, unless explicitly configured otherwise. LAN
side support of NTP is out of scope for this document.
WAA-6: If the IPv6 CE router receives a Router Advertisement
message (described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]) with the M flag set to 1,
the IPv6 CE router MUST do DHCPv6 address assignment
(request an IA_NA option).
WAA-7: If the IPv6 CE router does not acquire a global IPv6
address(es) from either SLAAC or DHCPv6, then it MUST create
a global IPv6 address(es) from its delegated prefix(es) and
configure those on one of its internal virtual network
interfaces, unless configured to require a global IPv6
address on the WAN interface.
WAA-8: The CE router MUST support the SOL_MAX_RT option [<a href="./rfc7083" title=""Modification to Default Values of SOL_MAX_RT and INF_MAX_RT"">RFC7083</a>]
and request the SOL_MAX_RT option in an Option Request
Option (ORO).
<span class="grey">Singh, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
WAA-9: As a router, the IPv6 CE router MUST follow the weak host
(Weak End System) model [<a href="./rfc1122" title=""Requirements for Internet Hosts - Communication Layers"">RFC1122</a>]. When originating packets
from an interface, it will use a source address from another
one of its interfaces if the outgoing interface does not
have an address of suitable scope.
WAA-10: The IPv6 CE router SHOULD implement the Information Refresh
Time option and associated client behavior as specified in
[<a href="./rfc4242" title=""Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC4242</a>].
Prefix delegation requirements:
WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation
requesting router behavior as specified in [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>]
(Identity Association for Prefix Delegation (IA_PD) option).
WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating
router the size of the prefix it requires. If so, it MUST
ask for a prefix large enough to assign one /64 for each of
its interfaces, rounded up to the nearest nibble, and SHOULD
be configurable to ask for more.
WPD-3: The IPv6 CE router MUST be prepared to accept a delegated
prefix size different from what is given in the hint. If the
delegated prefix is too small to address all of its
interfaces, the IPv6 CE router SHOULD log a system management
error. [<a href="./rfc6177" title=""IPv6 Address Assignment to End Sites"">RFC6177</a>] covers the recommendations for service
providers for prefix allocation sizes.
WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix
delegation when either the M or O flags are set to 1 in a
received Router Advertisement (RA) message. Behavior of the
CE router to use DHCPv6 prefix delegation when the CE router
has not received any RA or received an RA with the M and the
O bits set to zero is out of scope for this document.
WPD-5: Any packet received by the CE router with a destination
address in the prefix(es) delegated to the CE router but not
in the set of prefixes assigned by the CE router to the LAN
must be dropped. In other words, the next hop for the
prefix(es) delegated to the CE router should be the null
destination. This is necessary to prevent forwarding loops
when some addresses covered by the aggregate are not
reachable [<a href="./rfc4632" title=""Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan"">RFC4632</a>].
<span class="grey">Singh, et al. Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
(a) The IPv6 CE router SHOULD send an ICMPv6 Destination
Unreachable message in accordance with <a href="./rfc4443#section-3.1">Section 3.1 of
[RFC4443]</a> back to the source of the packet, if the packet is
to be dropped due to this rule.
WPD-6: If the IPv6 CE router requests both an IA_NA and an IA_PD
option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
Advertise/Reply messages, even if the message does not
contain any addresses, unless configured to only obtain its
WAN IPv6 address via DHCPv6; see [<a href="#ref-DHCPv6-STATEFUL-ISSUES">DHCPv6-STATEFUL-ISSUES</a>].
WPD-7: By default, an IPv6 CE router MUST NOT initiate any dynamic
routing protocol on its WAN interface.
WPD-8: The IPv6 CE router SHOULD support the [<a href="./rfc6603" title=""Prefix Exclude Option for DHCPv6-based Prefix Delegation"">RFC6603</a>] Prefix
Exclude option.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. LAN-Side Configuration</span>
The IPv6 CE router distributes configuration information obtained
during WAN interface provisioning to IPv6 hosts and assists IPv6
hosts in obtaining IPv6 addresses. It also supports connectivity of
these devices in the absence of any working WAN interface.
An IPv6 CE router is expected to support an IPv6 end-user network and
IPv6 hosts that exhibit the following characteristics:
1. Link-local addresses may be insufficient for allowing IPv6
applications to communicate with each other in the end-user
network. The IPv6 CE router will need to enable this
communication by providing globally scoped unicast addresses or
ULAs [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>], whether or not WAN connectivity exists.
2. IPv6 hosts should be capable of using SLAAC and may be capable of
using DHCPv6 for acquiring their addresses.
3. IPv6 hosts may use DHCPv6 for other configuration information,
such as the DNS_SERVERS option for acquiring DNS information.
Unless otherwise specified, the following requirements apply to the
IPv6 CE router's LAN interfaces only.
ULA requirements:
ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA
prefix [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>].
<span class="grey">Singh, et al. Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
ULA-2: An IPv6 CE router with a ULA prefix MUST maintain this prefix
consistently across reboots.
ULA-3: The value of the ULA prefix SHOULD be configurable.
ULA-4: By default, the IPv6 CE router MUST act as a site border
router according to <a href="./rfc4193#section-4.3">Section 4.3 of [RFC4193]</a> and filter
packets with local IPv6 source or destination addresses
accordingly.
ULA-5: An IPv6 CE router MUST NOT advertise itself as a default
router with a Router Lifetime greater than zero whenever all
of its configured and delegated prefixes are ULA prefixes.
LAN requirements:
L-1: The IPv6 CE router MUST support router behavior according to
Neighbor Discovery for IPv6 [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
L-2: The IPv6 CE router MUST assign a separate /64 from its
delegated prefix(es) (and ULA prefix if configured to provide
ULA addressing) for each of its LAN interfaces.
L-3: An IPv6 CE router MUST advertise itself as a router for the
delegated prefix(es) (and ULA prefix if configured to provide
ULA addressing) using the "Route Information Option" specified
in <a href="./rfc4191#section-2.3">Section 2.3 of [RFC4191]</a>. This advertisement is
independent of having or not having IPv6 connectivity on the
WAN interface.
L-4: An IPv6 CE router MUST NOT advertise itself as a default
router with a Router Lifetime [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] greater than zero if
it has no prefixes configured or delegated to it.
L-5: The IPv6 CE router MUST make each LAN interface an advertising
interface according to [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
L-6: In Router Advertisement messages ([<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]), the Prefix
Information option's A and L flags MUST be set to 1 by
default.
L-7: The A and L flags' ([<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]) settings SHOULD be user
configurable.
L-8: The IPv6 CE router MUST support a DHCPv6 server capable of
IPv6 address assignment according to [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] OR a stateless
DHCPv6 server according to [<a href="./rfc3736" title=""Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6"">RFC3736</a>] on its LAN interfaces.
<span class="grey">Singh, et al. Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
L-9: Unless the IPv6 CE router is configured to support the DHCPv6
IA_NA option, it SHOULD set the M flag to zero and the O flag
to 1 in its Router Advertisement messages [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>].
L-10: The IPv6 CE router MUST support providing DNS information in
the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [<a href="./rfc3646" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3646</a>].
L-11: The IPv6 CE router MUST support providing DNS information in
the Router Advertisement Recursive DNS Server (RDNSS) and DNS
Search List options. Both options are specified in [<a href="./rfc6106" title=""IPv6 Router Advertisement Options for DNS Configuration"">RFC6106</a>].
L-12: The IPv6 CE router SHOULD make available a subset of DHCPv6
options (as listed in <a href="./rfc3736#section-5.3">Section 5.3 of [RFC3736]</a>) received from
the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
server.
L-13: If the delegated prefix changes, i.e., the current prefix is
replaced with a new prefix without any overlapping time
period, then the IPv6 CE router MUST immediately advertise the
old prefix with a Preferred Lifetime of zero and a Valid
Lifetime of either a) zero or b) the lower of the current
Valid Lifetime and two hours (which must be decremented in
real time) in a Router Advertisement message as described in
<a href="#section-5.5.3">Section 5.5.3</a>, (e) of [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>].
L-14: The IPv6 CE router MUST send an ICMPv6 Destination Unreachable
message, code 5 (Source address failed ingress/egress policy)
for packets forwarded to it that use an address from a prefix
that has been invalidated.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Transition Technologies Support</span>
<span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>. 6rd</span>
6rd [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>] specifies an automatic tunneling mechanism tailored to
advance deployment of IPv6 to end users via a service provider's IPv4
network infrastructure. Key aspects include automatic IPv6 prefix
delegation to sites, stateless operation, simple provisioning, and
service that is equivalent to native IPv6 at the sites that are
served by the mechanism. It is expected that such traffic is
forwarded over the CE router's native IPv4 WAN interface and not
encapsulated in another tunnel.
The CE router SHOULD support 6rd functionality. If 6rd is supported,
it MUST be implemented according to [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]. The following CE
Requirements also apply:
<span class="grey">Singh, et al. Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
6rd requirements:
6RD-1: The IPv6 CE router MUST support 6rd configuration via the 6rd
DHCPv4 Option 212. If the CE router has obtained an IPv4
network address through some other means such as PPP, it
SHOULD use the DHCPINFORM request message [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] to
request the 6rd DHCPv4 Option. The IPv6 CE router MAY use
other mechanisms to configure 6rd parameters. Such
mechanisms are outside the scope of this document.
6RD-2: If the IPv6 CE router is capable of automated configuration
of IPv4 through IPCP (i.e., over a PPP connection), it MUST
support user-entered configuration of 6rd.
6RD-3: If the CE router supports configuration mechanisms other than
the 6rd DHCPv4 Option 212 (user-entered, TR-069 [<a href="#ref-TR-069" title=""CPE WAN Management Protocol"">TR-069</a>],
etc.), the CE router MUST support 6rd in "hub and spoke"
mode. 6rd in "hub and spoke" requires all IPv6 traffic to go
to the 6rd Border Relay. In effect, this requirement removes
the "direct connect to 6rd" route defined in <a href="./rfc5969#section-7.1.1">Section 7.1.1 of
[RFC5969]</a>.
6RD-4: A CE router MUST allow 6rd and native IPv6 WAN interfaces to
be active alone as well as simultaneously in order to support
coexistence of the two technologies during an incremental
migration period such as a migration from 6rd to native IPv6.
6RD-5: Each packet sent on a 6rd or native WAN interface MUST be
directed such that its source IP address is derived from the
delegated prefix associated with the particular interface
from which the packet is being sent (<a href="./rfc3704#section-4.3">Section 4.3 of
[RFC3704]</a>).
6RD-6: The CE router MUST allow different as well as identical
delegated prefixes to be configured via each (6rd or native)
WAN interface.
6RD-7: In the event that forwarding rules produce a tie between 6rd
and native IPv6, by default, the IPv6 CE router MUST prefer
native IPv6.
<span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>. Dual-Stack Lite (DS-Lite)</span>
Dual-Stack Lite [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] enables both continued support for IPv4
services and incentives for the deployment of IPv6. It also
de-couples IPv6 deployment in the service provider network from the
rest of the Internet, making incremental deployment easier. Dual-
Stack Lite enables a broadband service provider to share IPv4
<span class="grey">Singh, et al. Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
addresses among customers by combining two well-known technologies:
IP in IP (IPv4-in-IPv6) and Network Address Translation (NAT). It is
expected that DS-Lite traffic is forwarded over the CE router's
native IPv6 WAN interface, and not encapsulated in another tunnel.
The IPv6 CE router SHOULD implement DS-Lite functionality. If
DS-Lite is supported, it MUST be implemented according to [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>].
This document takes no position on simultaneous operation of Dual-
Stack Lite and native IPv4. The following CE router requirements
also apply:
WAN requirements:
DLW-1: The CE router MUST support configuration of DS-Lite via the
DS-Lite DHCPv6 option [<a href="./rfc6334" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite"">RFC6334</a>]. The IPv6 CE router MAY use
other mechanisms to configure DS-Lite parameters. Such
mechanisms are outside the scope of this document.
DLW-2: The IPv6 CE router MUST NOT perform IPv4 Network Address
Translation (NAT) on IPv4 traffic encapsulated using DS-Lite.
DLW-3: If the IPv6 CE router is configured with an IPv4 address on
its WAN interface, then the IPv6 CE router SHOULD disable the
DS-Lite Basic Bridging BroadBand (B4) element.
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Security Considerations</span>
It is considered a best practice to filter obviously malicious
traffic (e.g., spoofed packets, "Martian" addresses, etc.). Thus,
the IPv6 CE router ought to support basic stateless egress and
ingress filters. The CE router is also expected to offer mechanisms
to filter traffic entering the customer network; however, the method
by which vendors implement configurable packet filtering is beyond
the scope of this document.
Security requirements:
S-1: The IPv6 CE router SHOULD support [<a href="./rfc6092" title=""Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service"">RFC6092</a>]. In particular,
the IPv6 CE router SHOULD support functionality sufficient for
implementing the set of recommendations in <a href="./rfc6092#section-4">[RFC6092],
Section 4</a>. This document takes no position on whether such
functionality is enabled by default or mechanisms by which
users would configure it.
<span class="grey">Singh, et al. Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
S-2: The IPv6 CE router SHOULD support ingress filtering in
accordance with <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a> [<a href="./rfc2827" title=""Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing"">RFC2827</a>]. Note that this requirement
was downgraded from a MUST from <a href="./rfc6204">RFC 6204</a> due to the difficulty
of implementation in the CE router and the feature's redundancy
with upstream router ingress filtering.
S-3: If the IPv6 CE router firewall is configured to filter incoming
tunneled data, the firewall SHOULD provide the capability to
filter decapsulated packets from a tunnel.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
Thanks to the following people (in alphabetical order) for their
guidance and feedback:
Mikael Abrahamsson, Tore Anderson, Merete Asak, Rajiv Asati, Scott
Beuker, Mohamed Boucadair, Rex Bullinger, Brian Carpenter, Tassos
Chatzithomaoglou, Lorenzo Colitti, Remi Denis-Courmont, Gert Doering,
Alain Durand, Katsunori Fukuoka, Brian Haberman, Tony Hain, Thomas
Herbst, Ray Hunter, Joel Jaeggli, Kevin Johns, Erik Kline, Stephen
Kramer, Victor Kuarsingh, Francois-Xavier Le Bail, Arifumi Matsumoto,
David Miles, Shin Miyakawa, Jean-Francois Mule, Michael Newbery,
Carlos Pignataro, John Pomeroy, Antonio Querubin, Daniel Roesen,
Hiroki Sato, Teemu Savolainen, Matt Schmitt, David Thaler, Mark
Townsley, Sean Turner, Bernie Volz, Dan Wing, Timothy Winters, James
Woodyatt, Carl Wuyts, and Cor Zwart.
This document is based in part on CableLabs' eRouter specification.
The authors wish to acknowledge the additional contributors from the
eRouter team:
Ben Bekele, Amol Bhagwat, Ralph Brown, Eduardo Cardona, Margo Dolas,
Toerless Eckert, Doc Evans, Roger Fish, Michelle Kuska, Diego
Mazzola, John McQueen, Harsh Parandekar, Michael Patrick, Saifur
Rahman, Lakshmi Raman, Ryan Ross, Ron da Silva, Madhu Sudan, Dan
Torbet, and Greg White.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Contributors</span>
The following people have participated as co-authors or provided
substantial contributions to this document: Ralph Droms, Kirk
Erichsen, Fred Baker, Jason Weil, Lee Howard, Jean-Francois Tremblay,
Yiu Lee, John Jason Brzozowski, and Heather Kirksey. Thanks to Ole
Troan for editorship in the original <a href="./rfc6204">RFC 6204</a> document.
<span class="grey">Singh, et al. Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC1122">RFC1122</a>] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>, October 1989.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a>
<a href="./rfc2131">2131</a>, March 1997.
[<a id="ref-RFC2464">RFC2464</a>] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", <a href="./rfc2464">RFC 2464</a>, December 1998.
[<a id="ref-RFC2827">RFC2827</a>] Ferguson, P. and D. Senie, "Network Ingress Filtering:
Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a>, <a href="./rfc2827">RFC 2827</a>, May 2000.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
[<a id="ref-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>,
December 2003.
[<a id="ref-RFC3646">RFC3646</a>] Droms, R., "DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)", <a href="./rfc3646">RFC 3646</a>,
December 2003.
[<a id="ref-RFC3704">RFC3704</a>] Baker, F. and P. Savola, "Ingress Filtering for Multihomed
Networks", <a href="https://www.rfc-editor.org/bcp/bcp84">BCP 84</a>, <a href="./rfc3704">RFC 3704</a>, March 2004.
[<a id="ref-RFC3736">RFC3736</a>] Droms, R., "Stateless Dynamic Host Configuration Protocol
(DHCP) Service for IPv6", <a href="./rfc3736">RFC 3736</a>, April 2004.
[<a id="ref-RFC4191">RFC4191</a>] Draves, R. and D. Thaler, "Default Router Preferences and
More-Specific Routes", <a href="./rfc4191">RFC 4191</a>, November 2005.
[<a id="ref-RFC4193">RFC4193</a>] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", <a href="./rfc4193">RFC 4193</a>, October 2005.
[<a id="ref-RFC4242">RFC4242</a>] Venaas, S., Chown, T., and B. Volz, "Information Refresh
Time Option for Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc4242">RFC 4242</a>, November 2005.
<span class="grey">Singh, et al. Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
[<a id="ref-RFC4443">RFC4443</a>] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", <a href="./rfc4443">RFC 4443</a>, March 2006.
[<a id="ref-RFC4605">RFC4605</a>] Fenner, B., He, H., Haberman, B., and H. Sandick,
"Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding
("IGMP/MLD Proxying")", <a href="./rfc4605">RFC 4605</a>, August 2006.
[<a id="ref-RFC4632">RFC4632</a>] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation
Plan", <a href="https://www.rfc-editor.org/bcp/bcp122">BCP 122</a>, <a href="./rfc4632">RFC 4632</a>, August 2006.
[<a id="ref-RFC4779">RFC4779</a>] Asadullah, S., Ahmed, A., Popoviciu, C., Savola, P., and
J. Palet, "ISP IPv6 Deployment Scenarios in Broadband
Access Networks", <a href="./rfc4779">RFC 4779</a>, January 2007.
[<a id="ref-RFC4861">RFC4861</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>,
September 2007.
[<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007.
[<a id="ref-RFC5072">RFC5072</a>] Varada, S., Haskins, D., and E. Allen, "IP Version 6 over
PPP", <a href="./rfc5072">RFC 5072</a>, September 2007.
[<a id="ref-RFC5905">RFC5905</a>] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network
Time Protocol Version 4: Protocol and Algorithms
Specification", <a href="./rfc5905">RFC 5905</a>, June 2010.
[<a id="ref-RFC5908">RFC5908</a>] Gayraud, R. and B. Lourdelet, "Network Time Protocol (NTP)
Server Option for DHCPv6", <a href="./rfc5908">RFC 5908</a>, June 2010.
[<a id="ref-RFC5942">RFC5942</a>] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet
Model: The Relationship between Links and Subnet
Prefixes", <a href="./rfc5942">RFC 5942</a>, July 2010.
[<a id="ref-RFC5969">RFC5969</a>] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4
Infrastructures (6rd) -- Protocol Specification", <a href="./rfc5969">RFC</a>
<a href="./rfc5969">5969</a>, August 2010.
[<a id="ref-RFC6092">RFC6092</a>] Woodyatt, J., "Recommended Simple Security Capabilities in
Customer Premises Equipment (CPE) for Providing
Residential IPv6 Internet Service", <a href="./rfc6092">RFC 6092</a>, January
2011.
<span class="grey">Singh, et al. Informational [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
[<a id="ref-RFC6106">RFC6106</a>] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
"IPv6 Router Advertisement Options for DNS Configuration",
<a href="./rfc6106">RFC 6106</a>, November 2010.
[<a id="ref-RFC6177">RFC6177</a>] Narten, T., Huston, G., and L. Roberts, "IPv6 Address
Assignment to End Sites", <a href="https://www.rfc-editor.org/bcp/bcp157">BCP 157</a>, <a href="./rfc6177">RFC 6177</a>, March 2011.
[<a id="ref-RFC6333">RFC6333</a>] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4
Exhaustion", <a href="./rfc6333">RFC 6333</a>, August 2011.
[<a id="ref-RFC6334">RFC6334</a>] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite",
<a href="./rfc6334">RFC 6334</a>, August 2011.
[<a id="ref-RFC6434">RFC6434</a>] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node
Requirements", <a href="./rfc6434">RFC 6434</a>, December 2011.
[<a id="ref-RFC6603">RFC6603</a>] Korhonen, J., Savolainen, T., Krishnan, S., and O. Troan,
"Prefix Exclude Option for DHCPv6-based Prefix
Delegation", <a href="./rfc6603">RFC 6603</a>, May 2012.
[<a id="ref-RFC6887">RFC6887</a>] Wing, D., Cheshire, S., Boucadair, M., Penno, R., and P.
Selkirk, "Port Control Protocol (PCP)", <a href="./rfc6887">RFC 6887</a>, April
2013.
[<a id="ref-RFC7083">RFC7083</a>] Droms, R., "Modification to Default Values of SOL_MAX_RT
and INF_MAX_RT", <a href="./rfc7083">RFC 7083</a>, November 2013.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-DHCPv6-STATEFUL-ISSUES">DHCPv6-STATEFUL-ISSUES</a>]
Troan, O. and B. Volz, "Issues with multiple stateful
DHCPv6 options", Work in Progress, May 2013.
[<a id="ref-MULTIHOMING-WITHOUT-NAT">MULTIHOMING-WITHOUT-NAT</a>]
Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T.,
and D. Wing, "IPv6 Multihoming without Network Address
Translation", Work in Progress, December 2010.
[<a id="ref-RFC6144">RFC6144</a>] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", <a href="./rfc6144">RFC 6144</a>, April 2011.
[<a id="ref-TR-069">TR-069</a>] Broadband Forum, "CPE WAN Management Protocol", TR-069
Amendment 4, July 2011,
<<a href="http://www.broadband-forum.org/technical/trlist.php">http://www.broadband-forum.org/technical/trlist.php</a>>.
<span class="grey">Singh, et al. Informational [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7084">RFC 7084</a> IPv6 CE Router Requirements November 2013</span>
[<a id="ref-UPnP-IGD">UPnP-IGD</a>] UPnP Forum, , "InternetGatewayDevice:2 Device Template
Version 1.01", December 2010,
<<a href="http://upnp.org/specs/gw/igd2/">http://upnp.org/specs/gw/igd2/</a>>.
Authors' Addresses
Hemant Singh
Cisco Systems, Inc.
1414 Massachusetts Ave.
Boxborough, MA 01719
USA
Phone: +1 978 936 1622
EMail: shemant@cisco.com
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a>
Wes Beebee
Cisco Systems, Inc.
1414 Massachusetts Ave.
Boxborough, MA 01719
USA
Phone: +1 978 936 2030
EMail: wbeebee@cisco.com
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a>
Chris Donley
CableLabs
858 Coal Creek Circle
Louisville, CO 80027
USA
EMail: c.donley@cablelabs.com
Barbara Stark
AT&T
1057 Lenox Park Blvd. NE
Atlanta, GA 30319
USA
EMail: barbara.stark@att.com
Singh, et al. Informational [Page 21]
</pre>
|
