The Cost of Application Development with NATs
draft-chown-cost-of-nat-00

Document Type Expired Internet-Draft (individual)
Author Tim Chown 
Last updated 2006-06-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-chown-cost-of-nat-00.txt

Abstract

The deployment of IP Network Address Translators (NATs) for IPv4 has become very pervasive in the last 10-12 years. The original goal of NAT was to conserve IP address space, but the technology has now become very popular in home and SOHO type networks, as well as many larger organisations, for a variety of reasons. At the same time, the introduction of NAT adds a cost for application and service developers. This document presents a brief overview of the history of NAT, alongside a list of ongoing work related to NAT workarounds for current IETF protocol designs. The document intends to present a neutral view of the cost of NAT for discussion in the IETF and wider community.

Authors

Tim Chown (tjc@ecs.soton.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)