Negotiated Address Reuse (NAR)
draft-montenegro-aatn-nar-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Gabriel Montenegro | ||
| Last updated | 1999-01-13 | ||
| 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
Network address (and port) translation is a useful technology. However, several shortcomings have been identified (Mobile IP, IPSEC and QOS flows). In these cases, NAT may be complemented by the use of NAR (Negotiated Address Reuse). The negotiation phase in NAR is currently based on SOCKS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)