Le 28 sept. 2011 à 23:16, Cameron Byrne a écrit : ...
>>
>> It can't determine the public IP address and port of a mapping on the
>> NAT64 (CGN), and it can't create a mapping on the NAT64 (CGN) -- because
>> the CGN is going to make a dynamic mapping when it sees a UDP, TCP,
>> or ICMP packet from the subscriber.
>
> I don't see it matters
> +1 ... since the alternative is that apps that require ipv4 sockets and pass ipv4 literals are stranded on ipv6 only networks. Running code on the n900 shows that nat464 provides real user and network benefit
"So far so good" as result of an experiment, is per se a positive result, but it doesn't prove that there won't be problems in the future.
Running-code validation tests cannot be a reason to stop analyzing where problems might be likely to appear.
Regards, RD
|
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf