Re: [BEHAVE] Next for draft-ietf-behave-nat64-discovery-heuristic-00.txt

Thank you, we shall reference that document.

On the query frequency, we could state also that the DNS64 discovery is to be performed only on-demand, e.g. as result of API call and not pre-emptively.

	Teemu

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of ext Andrew Sullivan
> Sent: 30. toukokuuta 2011 15:05
> To: behave@ietf.org
> Subject: Re: [BEHAVE] Next for draft-ietf-behave-nat64-discovery-heuristic-
> 00.txt
> 
> On Mon, May 30, 2011 at 11:56:04AM +0000, teemu.savolainen@nokia.com
> wrote:
> 
> > 4) Define that the synthesizing DNS64 must handle AAAA query for the
> > well-known FQDN as for any other FQDN that does not have AAAA record
> > (=synthesize response normally). However, A DNS server that does not
> > implement AAAA synthesis (DNS64 function) could directly respond
> > NXDOMAIN for the query instead of forwarding the (in that case
> > pointless) query towards root?
> 
> That would be nice.  See
> http://tools.ietf.org/html/draft-ietf-dnsop-default-local-zones-15
> (which is, I think, about to be published).
> 
> (Just for the record, any contribution I make to this effort doesn't mean I think
> it's a good idea.  I think it's a bad idea, but it's apparently the bad idea that
> people are going to implement anyway.  So I'd like it to be least bad.  It's still a
> bad idea.)
> 
> A
> 
> --
> Andrew Sullivan
> ajs@crankycanuck.ca
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave