Network Address Port Group Translator
draft-meng-behave-napgt-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wei Meng | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| 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
Currently, if an internal server and hosts are behind NAT, they cannot share a global IP address except adding lots of static NAPT rule configuration. Because if a server wants to provide a service by constant port(i.e. HTTP and FTP) , the destination port of packet sent by an external client should not be changed when it crosses NAT. This document specifies a new method to assign NAPT global address and port, aiming to solve the problem that internal servers and hosts cannot share less global IP addresses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)