[DNSOP] Re: [v6ops] Re: Re: Re: Re: Re: Moving DNS64 (RFC6147) to Internet Standard

[Philip Homburg <[e-mail]>]

>    I don't have a complete list, but here is a start. Let's assume
>    a host that relies on DNS64 to obtain IPv4 connectivity. What
>    doesn't work in that case:  1) An IPv4 literal
> 
>    This is not a DNS64 issue, it is NAT64, that's why we invented
>    464XLAT.
> 
>    2) Any kind of local DNSSEC validation, either in the stub
>    resolver or in
>      a local DNS forwarder.
> 
>    This is incorrect if you properly configure the DNS64 server

I think we are talking at cross purposes.

I see DNS64 as part of a solution of providing an application with IPv4
access through NAT64. And I seen DNS64 failing at that.

In case 1), we have 464XLAT because DNS64 doesn't work in that case.
In case 2) DNS64 does not prevent DNSSEC validation. But at the same time
it no longer assists the application with IPv4 access through NAT64.

So by and large DNS64 fails at its fundamental purpose. And when we fix these
issues, like you mentioned, using 464XLAT, then the need for DNS64 goes away.

So in a very limited scope DNS64 may be of help. In my opinion, the confusion
DNS64 creates by pretending that A records are AAAA records causes more
harm than the limited benefit we get. This is simply not a protocol
that should be Internet Standard.