Indeed so. Have you read draft-ietf-v6ops-natpt-to-exprmntl-03.txt? The Abstract says:
This document discusses issues with the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These issues are sufficiently serious that recommending RFC 2766 as a general purpose transition mechanism is no longer desirable, and this document recommends that the IETF should reclassify RFC 2766 from Standards Track to Experimental status
You should think very carefully before spending a lot of time on this work. Regards, Elwyn Brian E Carpenter wrote:
One of the many reasons for killing NAT-PT. Brian haofeng Zhang wrote:Dear all, I have a problem regarding to NAT-PT and ALG. In the RFC2766(NAT-PT spec), nat-pt box cooperates with ALG to deal withsome application carrying IP addresses in payload. But for the operation of nat-box box, how can the box differentiate which kind of traffic needs to be processed by ALG and others needn't? Or the nat-pt box just send all trafficto ALG module and leave the differentiation problem to ALG?I don't find the clarification in the spec. So if answer is the latter, doesit means a big waste of device resource? After all, usually only the signaling traffic needs to be processed by ALG. So any kind of help is appreciated. -- Best regards, Zhang haofeng