STUN-aware NAT
draft-simu-midcom-stun-aware-nat-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adina Simu , Rohan Mahy , Mahadev Somasundaram | ||
| Last updated | 2002-04-11 | ||
| 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
STUN provides an easy way to traverse some types of NATs and it will work satisfactorily in many NAT deployments. To overcome STUN's limitations, one solution is to accept the idea that NATs can change too (and they've been proven to change, an example being the proliferation of IPsec pass-thru NAT devices) and to colocate STUN server functionality on the NAT box itself. Upon receipt of a STUN request, the server colocated within the NAT device allocates addresses and ports, and installs bindings. This allows hosts running the STUN client software to transparently achieve symmetric NAT traversal and to make themselves addressable from the Global Internet.
Authors
Adina Simu
Rohan Mahy
Mahadev Somasundaram
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)