In message <[email protected]>, Ted Lemon writes:
> On Sep 12, 2012, at 9:02 PM, Mark Andrews <[email protected]> wrote:
> > My machines have names.  Those names don't change as I move around
> > the world.  Random DHCP servers at coffee shops DO NOT have the
> > ability to update the DNS entries for those names.  They do have the
> > authority to update the PTR records in in-addr.arpa and ip6.arpa
> > namespaces.
> 
> We're not talking about mobile IP here=97we''re talking about naming in the=
>  homenet.   The technology has existed for over a decade to do what you des=
> cribe with DHCP and DDNS in IPv4, but AFAIK nobody uses it, for two reasons=
> : one, I don't think it actually serves a real need,

More because no one looked at the whole picture and tried to get a
comprehensive solution.  It has multiple moving parts from multiple
vendors.

> and two, it requires g=
> eek skills to set up, which most people don't have.

Which is a UI / product support problem.  The Mac has DNS registration
under Sharing.  It requires manual entry of the TSIG key which
currently has to be entered into the nameserver for each device.
It could be made as simple as BlueTooth associations are.

>   But the second point =
> is really a footnote to the first.

I have laptops that connect to the home net and then go walkabout.
I suspect a large percentage of homes have some equipment that moves
about.  Those laptops still want to do things to the home net
occasionally.  Devices on the home network want to push stuff to
those laptops occasionally.

> There's a draft in the DHC working group for setting up the reverse zone...
> 
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to