284:
291:
A simple NAT64 installation may consist of a gateway with two interfaces connected to an IPv4 network and an IPv6 network, respectively. Traffic from the IPv6 network is routed via the gateway which performs all the necessary translations for transferring packets between the two networks. However,
304:
Stateless translation is appropriate when a NAT64 translator is used in front of IPv6-only servers to allow them to be reached by remote IPv4-only clients. Stateful translation is suitable for deployment at the client side or at the service provider, allowing IPv6-only client hosts to reach remote
300:
space; thus, one-to-one address mapping is not possible. The gateway maintains IPv6-to-IPv4 address mapping, which may be established with an automatic algorithm (stateless mapping) or with special and manual translations (stateful mapping) when the first packet from the IPv6 network reaches the
748:
275:(hence the 32-bit address space in the IPv6 network segment), and sends packets to the resulting address. The NAT64 gateway creates a mapping between the IPv6 and the IPv4 addresses, which may be manually configured or determined automatically.
252:(NAT). The NAT64 gateway is a translator between IPv4 and IPv6 protocols, for which function it needs at least one IPv4 address and an IPv6 network segment comprising a 32-bit address space. The "well-known prefix" reserved for this service is
553:
791:
770:
308:
In general, NAT64 is designed to be used when the communication is initiated by IPv6 hosts. Some mechanisms, including static address mapping, exist to allow the inverse scenario.
561:
220:
909:
509:
904:
704:
539:
951:
339:, which uses NAT64, allows use of such protocols over IPv6-only connections. For SIP and FTP, the problem can also be solved using an
271:
An IPv6 client embeds the IPv4 address it wishes to communicate with using the host part of the IPv6 network segment, resulting in an
85:
899:
213:
137:
978:
56:
1004:
206:
638:
466:
412:
830:
194:
189:
142:
75:
961:
316:
311:
Not every type of resource is accessible with NAT64. Protocols that embed IPv4 literal addresses, such as
956:
312:
249:
90:
517:
971:
999:
966:
930:
871:
340:
237:
22:
111:
925:
344:
106:
61:
699:
652:
611:
488:
434:
462:
Stateful NAT64: Network
Address and Protocol Translation from IPv6 Clients to IPv4 Servers
8:
823:
335:
allows IPv6-only clients to access even web pages with IPv4 literals in URLs. However,
41:
839:
603:
480:
426:
402:
642:
593:
470:
416:
173:
80:
887:
331:, MSN, and any other content with IPv4 literals are excluded, but a dual-stacked
132:
655:
632:
614:
583:
491:
460:
446:
437:
406:
808:
993:
816:
607:
484:
430:
147:
127:
861:
297:
293:
866:
672:
400:
647:
634:
Discovering NAT64 IPv6 Prefixes Using the Port
Control Protocol (PCP)
598:
475:
421:
381:
332:
458:
374:
359:
336:
771:"Configuring Stateful NAT64 for Handling IPv4 Address Depletion"
946:
727:
581:
324:
152:
51:
16:
Mechanism to allow IPv6 hosts to communicate with IPv4 servers
368:
328:
168:
856:
842:
677:
589:
245:
241:
66:
46:
36:
585:
464XLAT: Combination of
Stateful and Stateless Translation
892:
320:
283:
459:
M. Bagnulo; P. Matthews; I. van
Beijnum (April 2011).
554:"NAT64 Technology: Connecting IPv6 and IPv4 Networks"
371:via the "Create NAT64 Network" in internet sharing
582:M. Mawatari; M. Kawashima; C. Byrne (April 2013).
405:; M. Bagnulo; M. Boucadair; X. Li (October 2010).
910:Comparison of IPv6 support in common applications
991:
905:Comparison of IPv6 support in operating systems
838:
824:
214:
630:
501:
831:
817:
362:via the jool-tools-netfilter opkg package
221:
207:
646:
597:
474:
420:
292:the translation is not symmetric, as the
278:
900:World IPv6 Day and World IPv6 Launch Day
728:"Tayga- Simple, no-fuss NAT64 for Linux"
408:IPv6 Addressing of IPv4/IPv6 Translators
282:
979:Site Multihoming by IPv6 Intermediation
240:that facilitates communication between
992:
749:"Supporting IPv6 DNS64/NAT64 Networks"
624:
575:
452:
394:
812:
725:
13:
507:
350:
14:
1016:
792:"Understand and Configure NAT64"
784:
763:
741:
719:
700:"package: jool-tools-netfilter"
639:Internet Engineering Task Force
467:Internet Engineering Task Force
413:Internet Engineering Task Force
692:
665:
546:
532:
296:space is much larger than the
1:
510:"NAT64 power and limitations"
387:
347:with the PREFIX64 extension.
1005:IPv6 transition technologies
962:Multicast Listener Discovery
273:IPv4-embedded IPv6 addresses
7:
957:Neighbor Discovery Protocol
540:"NAT64 Address Translation"
250:network address translation
10:
1021:
972:Multicast router discovery
449:.
23:IPv6 transition mechanisms
967:Secure Neighbor Discovery
939:
931:IPv6 transition mechanism
918:
880:
849:
631:M. Boucadair (May 2014).
341:application-level gateway
248:hosts by using a form of
238:IPv6 transition mechanism
926:IPv4 address exhaustion
673:"Introduction to Jool"
288:
279:Principle of operation
345:Port Control Protocol
286:
919:IPv4 to IPv6 topics
726:Lutchansk, Nathan.
661:Proposed Standard.
497:Proposed Standard.
443:Proposed Standard.
289:
42:Lightweight 4over6
987:
986:
940:Related protocols
840:Internet Protocol
520:on 8 January 2014
445:Updates RFC
305:IPv4-only nodes.
231:
230:
1012:
1000:Routing software
833:
826:
819:
810:
809:
803:
802:
800:
798:
788:
782:
781:
779:
777:
767:
761:
760:
758:
756:
751:. March 27, 2017
745:
739:
738:
736:
734:
723:
717:
716:
714:
712:
696:
690:
689:
687:
685:
669:
663:
659:
650:
648:10.17487/RFC7225
628:
622:
618:
601:
599:10.17487/RFC6877
579:
573:
572:
570:
569:
560:. Archived from
550:
544:
543:
536:
530:
529:
527:
525:
516:. Archived from
505:
499:
495:
478:
476:10.17487/RFC6146
456:
450:
441:
424:
422:10.17487/RFC6052
398:
265:
264:
261:
258:
223:
216:
209:
19:
18:
1020:
1019:
1015:
1014:
1013:
1011:
1010:
1009:
990:
989:
988:
983:
935:
914:
888:IPv6 deployment
876:
845:
837:
807:
806:
796:
794:
790:
789:
785:
775:
773:
769:
768:
764:
754:
752:
747:
746:
742:
732:
730:
724:
720:
710:
708:
698:
697:
693:
683:
681:
671:
670:
666:
629:
625:
580:
576:
567:
565:
552:
551:
547:
538:
537:
533:
523:
521:
506:
502:
457:
453:
399:
395:
390:
353:
351:Implementations
301:NAT64 gateway.
287:NAT64 and DNS64
281:
262:
259:
256:
255:
227:
29:Standards Track
17:
12:
11:
5:
1018:
1008:
1007:
1002:
985:
984:
982:
981:
976:
975:
974:
969:
964:
959:
949:
943:
941:
937:
936:
934:
933:
928:
922:
920:
916:
915:
913:
912:
907:
902:
897:
896:
895:
884:
882:
878:
877:
875:
874:
869:
864:
859:
853:
851:
847:
846:
836:
835:
828:
821:
813:
805:
804:
783:
762:
740:
718:
691:
664:
623:
620:Informational.
574:
545:
531:
508:Mavrin, Alex.
500:
451:
392:
391:
389:
386:
385:
384:
378:
377:
372:
366:
363:
357:
352:
349:
280:
277:
229:
228:
226:
225:
218:
211:
203:
200:
199:
198:
197:
192:
184:
183:
179:
178:
177:
176:
171:
163:
162:
158:
157:
156:
155:
150:
145:
140:
135:
130:
122:
121:
117:
116:
115:
114:
109:
101:
100:
96:
95:
94:
93:
88:
83:
78:
69:
64:
59:
54:
49:
44:
39:
31:
30:
26:
25:
15:
9:
6:
4:
3:
2:
1017:
1006:
1003:
1001:
998:
997:
995:
980:
977:
973:
970:
968:
965:
963:
960:
958:
955:
954:
953:
950:
948:
945:
944:
942:
938:
932:
929:
927:
924:
923:
921:
917:
911:
908:
906:
903:
901:
898:
894:
891:
890:
889:
886:
885:
883:
879:
873:
870:
868:
865:
863:
860:
858:
855:
854:
852:
848:
844:
841:
834:
829:
827:
822:
820:
815:
814:
811:
793:
787:
772:
766:
750:
744:
729:
722:
707:
706:
701:
695:
680:
679:
674:
668:
662:
657:
654:
649:
644:
640:
636:
635:
627:
621:
616:
613:
609:
605:
600:
595:
591:
587:
586:
578:
564:on 2020-11-12
563:
559:
555:
549:
541:
535:
519:
515:
511:
504:
498:
493:
490:
486:
482:
477:
472:
468:
464:
463:
455:
448:
444:
439:
436:
432:
428:
423:
418:
414:
410:
409:
404:
397:
393:
383:
380:
379:
376:
373:
370:
367:
364:
361:
358:
355:
354:
348:
346:
342:
338:
334:
330:
326:
322:
318:
314:
309:
306:
302:
299:
295:
285:
276:
274:
269:
267:
266:
251:
247:
243:
239:
235:
224:
219:
217:
212:
210:
205:
204:
202:
201:
196:
193:
191:
188:
187:
186:
185:
181:
180:
175:
172:
170:
167:
166:
165:
164:
160:
159:
154:
151:
149:
148:Public 4over6
146:
144:
141:
139:
136:
134:
131:
129:
128:Tunnel broker
126:
125:
124:
123:
120:Informational
119:
118:
113:
110:
108:
105:
104:
103:
102:
98:
97:
92:
89:
87:
84:
82:
79:
77:
73:
70:
68:
65:
63:
60:
58:
55:
53:
50:
48:
45:
43:
40:
38:
35:
34:
33:
32:
28:
27:
24:
21:
20:
862:IPv6 address
795:. Retrieved
786:
774:. Retrieved
765:
753:. Retrieved
743:
731:. Retrieved
721:
709:. Retrieved
705:OpenWrt wiki
703:
694:
682:. Retrieved
676:
667:
660:
633:
626:
619:
584:
577:
566:. Retrieved
562:the original
557:
548:
534:
522:. Retrieved
518:the original
514:Blog article
513:
503:
496:
461:
454:
442:
407:
396:
310:
307:
303:
298:IPv4 address
294:IPv6 address
290:
272:
270:
254:
253:
233:
232:
99:Experimental
71:
872:Mobile IPv6
867:IPv6 packet
343:, or using
994:Categories
881:Deployment
568:2021-01-12
403:C. Huitema
388:References
182:Deprecated
843:version 6
608:2070-1721
524:6 January
485:2070-1721
431:2070-1721
382:Cisco IOS
333:web proxy
257:64:ff9b::
797:April 4,
776:April 4,
755:April 4,
733:April 4,
711:April 4,
684:April 4,
469:(IETF).
415:(IETF).
401:C. Bao;
375:Junos OS
850:General
365:Tayga
360:OpenWrt
337:464XLAT
195:NAPT-PT
143:464XLAT
57:DS-Lite
952:ICMPv6
947:DHCPv6
606:
483:
429:
325:WebRTC
236:is an
190:NAT-PT
161:Drafts
153:ISATAP
81:Teredo
52:6over4
558:Cisco
369:MacOS
356:Jool
329:Skype
234:NAT64
169:AYIYA
76:DNS64
72:NAT64
857:IPv6
799:2024
778:2024
757:2024
735:2024
713:2024
686:2024
678:Jool
656:7225
615:6877
604:ISSN
590:IETF
526:2014
492:6146
481:ISSN
447:4291
438:6052
427:ISSN
315:and
246:IPv4
244:and
242:IPv6
174:dIVI
86:SIIT
67:6to4
47:6in4
37:4in6
893:6rd
653:RFC
643:doi
612:RFC
594:doi
489:RFC
471:doi
435:RFC
417:doi
321:FTP
317:SDP
313:SIP
138:TRT
133:IVI
112:4rd
107:TSP
91:MAP
62:6rd
996::
702:.
675:.
651:.
641:.
637:.
610:.
602:.
592:.
588:.
556:.
512:.
487:.
479:.
465:.
433:.
425:.
411:.
327:,
323:,
319:,
268:.
263:96
74:/
832:e
825:t
818:v
801:.
780:.
759:.
737:.
715:.
688:.
658:.
645::
617:.
596::
571:.
542:.
528:.
494:.
473::
440:.
419::
260:/
222:e
215:t
208:v
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.