Network Address Translation

Network Address Translation
Name	Network Address Translation
Abbreviation	NAT
Introduced	1994
Inventor	Paul Francis
Purpose	IPv4 address conservation, routing, isolation

Contents

Network Address Translation

Network Address Translation is a method used in computer networking to remap one IP address space into another by modifying network address information in IP packet headers while in transit. In the context of Internet Protocol evolution, NAT emerged amid address exhaustion discussions involving Internet Engineering Task Force, Vint Cerf, Jon Postel, and institutions such as Internet Assigned Numbers Authority and IETF Working Group efforts. NAT is widely implemented in consumer devices from vendors like Cisco Systems, Juniper Networks, and Netgear, and its deployment influenced standards debates at Internet Architecture Board and IPv6 adoption discussions involving European Telecommunications Standards Institute.

Overview

NAT translates addresses between a private network and a public network, enabling hosts with private addresses defined by Internet Engineering Task Force RFCs to communicate beyond local routers. Early commercial interest involved companies such as Xerox PARC and research at Bell Labs; operational uptake accelerated with products from 3Com and Linksys. NAT variants interact with application-layer protocols standardized by World Wide Web Consortium, Internet Engineering Task Force, and multimedia work at International Telecommunication Union. The technique affects how services registered with Internet Corporation for Assigned Names and Numbers are reached and has legal and regulatory implications considered by bodies like Federal Communications Commission.

Types include static NAT, dynamic NAT, and port address translation (PAT), sometimes called masquerading in implementations by Linux Foundation distributions and FreeBSD projects. Mechanisms operate per RFCs authored by contributors from Cisco Systems and researchers affiliated with University of California, Berkeley and Stanford University; packet rewriting alters fields in IP headers and interacts with protocols such as Transmission Control Protocol and User Datagram Protocol, and with higher-layer protocols like Session Initiation Protocol and Hypertext Transfer Protocol. Carrier-grade NAT used by ISPs like Comcast and Deutsche Telekom introduces address sharing at scale and implicates numbering plans managed by American Registry for Internet Numbers and RIPE NCC. Middlebox behaviors have been the subject of studies at Massachusetts Institute of Technology, Carnegie Mellon University, and University of Cambridge.

NAT is implemented in consumer gateways produced by D-Link, TP-Link, and AsusTek, in enterprise routers from Cisco Systems and Juniper Networks, and in virtualization platforms such as VMware and KVM. Operating systems including Microsoft Windows, Linux kernel, and FreeBSD provide NAT utilities or firewall integrations originally developed by groups at University of California, Berkeley and projects like Netfilter and PF (packet filter). ISPs deploy NAT variants in networks using provisioning tools influenced by practices from Verizon Communications and AT&T. Deployment choices affect interoperation with directory services developed by The Open Group and authentication frameworks from MIT Kerberos Consortium.

NAT alters end-to-end addressing assumptions central to protocols studied at Stanford University and cryptographic designs from researchers at RSA Security and MIT. NAT provides a form of network isolation used alongside firewalls developed by Palo Alto Networks and intrusion detection work from SANS Institute, but it also complicates deployment of end-to-end security protocols advocated by IETF TLS Working Group and identity systems like OAuth and SAML. Privacy trade-offs are analyzed by academics at University College London and policy groups such as Electronic Frontier Foundation and Center for Democracy & Technology, while law enforcement practices at agencies like FBI and Europol consider NAT’s effects on attribution. Research projects at University of Illinois Urbana-Champaign and ETH Zurich examine NAT traversal techniques used by applications relying on Interactive Connectivity Establishment and peer-to-peer work from BitTorrent authors.

NAT performance depends on hardware from vendors like Broadcom and Intel Corporation for packet processing and on algorithms developed in research by Bell Labs and AT&T Labs Research. Scalability concerns arise in carrier-grade deployments by Telefonica and NTT Communications where stateful translation tables and connection tracking can create bottlenecks referenced in studies at University of Toronto and Princeton University. Load balancing and high-availability designs from F5 Networks and Citrix Systems mitigate single points of failure, while measurements by teams at Akamai Technologies and Google inform optimization strategies. Emerging approaches leverage programmable data planes from Barefoot Networks and standards from Open Networking Foundation.

Standards bodies including Internet Engineering Task Force and International Organization for Standardization document behaviors via RFCs; notable documents were authored with contributions from engineers at Cisco Systems, Juniper Networks, and academics at University of California, Berkeley. Protocol interactions involve Dynamic Host Configuration Protocol for address assignment, Domain Name System for name resolution, and traversal protocols such as Session Traversal Utilities for NAT developed by IETF STUN/TURN/ICE Working Group. Debates about NAT’s role in the transition to IPv6 have involved European Commission technology policy discussions and recommendations by Internet Society. Implementation conformance and interoperability testing are performed at events hosted by Interop and standards interoperability labs operated by ETSI.

Category:Internet protocols