On 11 Sep 2012, at 02:41, james woodyatt j...@apple.com wrote:
Really? How has the architecture team managed to overlook the obvious
problem that homenets with interior routing domains comprising multiple
networks cannot use either mDNS or LLMNR, which are confined to link-local
On 11/09/2012 08:19, Ray Bellis wrote:
...
So the point of the original email was to test that first assumption - i.e.
what services don't (or can't) work in-home without a local unicast DNS zone.
Excuse my ignorance, but if a LAN has both mDNS and DNS available,
what happens when an app calls
On 11/09/2012 14:11, Simon Perreault wrote:
Le 2012-09-11 05:17, Brian E Carpenter a écrit :
Excuse my ignorance, but if a LAN has both mDNS and DNS available,
what happens when an app calls getnameinfo() ?
Current situation is: implementation-dependant.
In fact, getnameinfo() is not
On 09/11/2012 12:19 AM, Ray Bellis wrote:
I shall attempt to clarify.
Iff all in-home services can be reached (whilst in-home) by mDNS-like protocols then we
do not need an in-home unicast DNS zone.
To reach those same services from _outside_ the home does of course need them
to exist in the
On 09/11/2012 09:01 AM, Ted Lemon wrote:
There are a couple of options being pursued in the DHC working group; the DHCP
address registration process would be an obvious mechanism for leveraging DHCP
to populate the DNS. The idea here is that you do RA+SLAAC, or RA+CGA, and
then you contact
On Sep 11, 2012, at 12:24 PM, Michael Thomas m...@mtcc.com wrote:
Maybe somebody can educated me, but isn't it a bit dangerous to use
an auto-configured address as a way to contact a host? If I change out my
ethernet hardware, for example, my auto-conf address would normally
change too, right?
On Tue, Sep 11, 2012 at 06:52:16AM -0700, Michael Thomas wrote:
So no, let's not start from an assumption that it's an mDNS world in the
home. I'd say let's start from the opposite assumption that it's a normal
DNS world inside the home where mDNS is a way to auto-populate a
DNS repository in
On Tue, Sep 11, 2012 at 12:37:30PM -0400, Ted Lemon wrote:
No. Things change. All that's required to deal with this is that the
underlying protocol support it. The DHCP DUID identification system
does support this kind of change, as long as the actual device doesn't
change. If the
On Sep 11, 2012, at 11:07 , Evan Hunt e...@isc.org wrote:
This does raise a point, though: Dynamic DNS doesn't have an expiration
mechanism. [...] My home zone is cluttered up with the names of a couple of
dozen laptops and ipods belonging to neighbors and visitors over the past
year.
I recommend reading section 5 of Understanding Apple's Back-to-My-Mac
Service [RFC
6281], which gives a brief summary of how this problem is effectively and
reliably
managed in that system. There you will find references to the following truly
under-loved technical specifications:
In message 504f65c7.4010...@mtcc.com
Michael Thomas writes:
On 09/11/2012 09:01 AM, Ted Lemon wrote:
There are a couple of options being pursued in the DHC working
group; the DHCP address registration process would be an obvious
mechanism for leveraging DHCP to populate the DNS. The
In message 20120911180743.gd15...@isc.org
Evan Hunt writes:
On Tue, Sep 11, 2012 at 12:37:30PM -0400, Ted Lemon wrote:
No. Things change. All that's required to deal with this is that the
underlying protocol support it. The DHCP DUID identification system
does support this kind of
12 matches
Mail list logo
