Editing Network address translation (section)

==NAT in IPv6==
Network address translation is not commonly used in [[IPv6]] because one of the design goals of IPv6 is to restore end-to-end network connectivity.<ref>{{cite web|author=Iljitsch van Beijnum |url=https://arstechnica.com/uncategorized/2008/07/after-staunch-resistance-nat-may-come-to-ipv6-after-all/ |title=After staunch resistance, NAT may come to IPv6 after all |website=Ars Technica |date=2008-07-23 |access-date=2014-04-24}}</ref> The large addressing space of IPv6 obviates the need to conserve addresses and every device can be given a unique globally routable address. Use of [[unique local address]]es in combination with [[IPv6-to-IPv6 Network Prefix Translation|network prefix translation]] can achieve results similar to NAT.

The large addressing space of IPv6 can still be defeated depending on the actual prefix length given by the carrier. It is not uncommon to be handed a /64 prefix – the smallest recommended subnet – for an entire home network, requiring a variety of techniques to be used to manually subdivide the range for all devices to remain reachable.<ref>{{Cite web |last=Dupont |first=Kasper |date=Aug 18, 2015 |title=subnet - IPv6 subnetting a /64 - what will break, and how to work around it? |url=https://serverfault.com/questions/714890/ipv6-subnetting-a-64-what-will-break-and-how-to-work-around-it |access-date=2023-04-20 |website=Server Fault |language=en}}</ref> Even actual IPv6-to-IPv6 NAT, NAT66, can turn out useful at times: the APNIC blog outlines a case where the author was only provided a single address (/128).<ref>{{Cite web |last=Cilloni |first=Marco |date=2018-02-01 |title=NAT66: The good, the bad, the ugly |url=https://blog.apnic.net/2018/02/02/nat66-good-bad-ugly/ |access-date=2023-04-20 |website=APNIC Blog |language=en-US}}</ref>