Today's Behave agenda includes DNS.
Behave AGENDA
SESSION TWO
THURSDAY, 09:00-11:30
...
9:55 NAT64 (Marcelo
Bagnulo, 25)
draft-bagnulo-behave-nat64
10:20 DNS64 (Marcelo
Bagnulo, 20)
draft
In your previous mail you wrote:
So they are aware that this is broken. Let's hope that this type of
service discovery through a fraction DNS root doesn't make its way
into the final standard.
=> I agree but what you propose to do? There will be a double session
of behave WG tomorrow a
On Thu, Nov 20, 2008 at 12:14:45PM +0100, Florian Weimer wrote:
> I came across the following in some IPv6-related draft and thought I'd
> share it.
>
> |3.1. Using DNS to Learn IPv6 Prefix and Length
> |
> | In order for an IPv6 host to determine if a NAT64 is present on its
> | network, it
On Nov 20, 2008, at 5:14 AM, Florian Weimer wrote:
So they are aware that this is broken. Let's hope that this type of
service discovery through a fraction DNS root doesn't make its way
into the final standard.
Use MDNS?
___
DNSOP mailing list
DNSOP
>> So they are aware that this is broken. Let's hope that this type of
>> service discovery through a fraction DNS root doesn't make its way
>> into the final standard.
>
> would they complain if the roots actually provided an authoritative
> answer (other than NXDOMAIN) at some point
I came across the following in some IPv6-related draft and thought I'd
share it.
|3.1. Using DNS to Learn IPv6 Prefix and Length
|
| In order for an IPv6 host to determine if a NAT64 is present on its
| network, it sends a DNS query. Because a host doesn't always know
| its network's defau