Tvurci se nijak netaji tim, ze nektery veci proste fungovat nemusi:
"Although NPTv6 compares favorably to NAT44 in several ways, it does not eliminate all of the achitectural problems associated with IPv4 NAT, as described in [RFC2993]. NPTv6 involves modifying IP headers in transit, so it is not compatible with security mechanisms, such as the IPsec Authentication Header, that provide integrity protection for the IP header. NPTv6 may interfere with the use of application protocols that transmit IP addresses in the application-specific portion of the IP packet."
Jinymi slovy, moc vysoko bych z toho radosti neskakal.
V souvislosti s timto musim upozornit, ze vcera (28.2.2011) vysla dalsi verze draftu draft-mrw-nat66 ve verzi 8. Zatim se tvurci zminovali o dopadu na aplikace pouze okrajove. V nove verzi draftu pribyl pomerne rozsahly odstavec resici otazky dopadu na aplikace (viz. http://tools.ietf.org/rfcdiff?url2=draft-mrw-nat66-08, sekce c. 5).
Obecne lze rici, ze spravne vyporadani se s mechanizmem prekladu prefixu je veci vhodneho navrhu protokolu. Mechanizmus se uz dnes bezne pouziva v IPv4 na mapovani adres do DMZ, kde je provozovani protokolu jako je IPSEC nebo SIP zcela beznou zalezitosti.