Short term NAT requirements for UDP based peer-to-peer applications
draft-huitema-natreq4udp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Huitema | ||
| Last updated | 2001-02-19 | ||
| RFC stream | (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
During the next few years, as the IPv4 address space moves toward exhaustion, it is likely that the deployment of NAT will accelerate. This draft presents the requirements that NAT devices must meet in order to enable use of UDP by peer-to-peer applications. The requirement can be summed up by the need to avoid gratuitous filtering and too short timers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)