Re: [v4v6interim] Single namespace

[Fred Baker <[e-mail]>]

On Oct 1, 2008, at 2:30 PM, [e-mail] wrote:
>> It gets a AAAA request from some host, sends a request for an A  
>> record
>> (perhaps o itself), gets the A record response, generates a AAAA
>> record from it, and sends that as a reply to the original request.
>
> 	so the DNS64 app is configured in the endsystems as the
> 	caching nameserver for the domain.  in that case, there is
> 	an operational question or  two.

not sure how that works in a real domain. IVI and NAT64 configure it  
in the common server.

>>> If this is a plausable explaination, then I would posit that the
>>> creation of
>>> DNS64 is injecting a MITM vector that is unreasonable.
>>
>> Any form of translation is a MITM vector. If you find translation
>> unreasonable, then yes you will find that vector unreasonable. If you
>> find translation necessary, I don't think you can avoid the
>> possibility that the translator is a MITM vector.
>
> 	right - but keeping the translation at the network layer instead
> 	of the application layer reduces complexity.

arg.

you're doing DNS name translation at the network layer?

You sound like my marketing people.

> 	translateable is not an artifact of the DNS, thats properly the
> 	perview of a NAT.

and you found this in a document that described a NAT.

I'm lost.
_______________________________________________
v4v6interim mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/v4v6interim