The Cost of Application Development with NATs
draft-chown-cost-of-nat-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tim Chown | ||
| Last updated | 2006-06-22 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)