Issues with NAT-PT DNS ALG in RFC2766
draft-durand-v6ops-natpt-dns-alg-issues-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alain Durand | ||
| Last updated | 2003-02-24 | ||
| 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
Recent discussions on the need to translate or not between IPv4 and IPv6 have brought a better understanding on the impact of tools like NAT-PT [NAT-PT]. Several problems have been identified around the DNS ALG functionality. An alternative solution that does not require this DNS ALG for connections initiated by the IPv6 side has been proposed. This memo aims at analyzing the pros and cons of both solutions in that case. Connections initiated by the IPv4 side would always require the help of a DNS-ALG and thus are not covered by this memo.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)