Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps

[Mark Andrews <[e-mail]>]

In message <[e-mail]>, Francisco O
bispo writes:
> > On May 26, 2015, at 1:07 PM, John Levine <[e-mail]> wrote:
> >
> >> I believe the delegation of HOME/CORP/MAIL provides with more benefit
> >> than risks, there
> >> will be more companies/homes and mail users happy because their names
> >> resolve from
> >> everywhere, they can validate with DNSSEC, they can opt who can
> >> connect to their
> >> networks and no longer require domain hacks to get their users to go
> >> to the right
> >> places.
> >
> > There are probably tens of thousands of people who have a device with
> > the local name PRINTER.HOME.  I must be dim, because I cannnot imagine
> > any way that any possible set of DNS records in the root or a TLD
> > would allow that name to "resolve from everywhere" in a way other than
> > perhaps one that sent an enormous amount of people's printouts to one
> > printer somewhere.
> >
> > Could you clarify how it's supposed to work?
> >
>
> I would certainly like to have: obispo.home, be a real FQDN, so I can
> name my home devices, printer.obispo.home, etc.

In reality it would be printer.obispo72.home or something like that
99.999% of registrants after a year or so.  Only those that jump
at the very begining would get their family name.  .home wouldn't
be like .com where you are choosing a name for a business and part
of that process is finding something that is unique and that you
like in the DNS.  You already have a name.

And Australia actually has a model for how to link individuals /
families / homes into the dns.

name.<othername>.id.au

id is for individual.
<othername> is a meaningless label designed to deal with human name
collisions.

andrews.wattle.id.au (the master is currently broken) is just as
easy for me to remember as andrews.home and has the advantage that
lots of other andrewses can get a andrews.something.id.au name and
be on a equal footing.

wattle.id.au is also a free registry run on a volunteer basis.

Basically .home is too high in the heirarchy for this sort of
individual / family use.  There are too many collisions of names.

.home.ctld is also too high which is why a third level was added.

Mark

> If I go to a hotel around the world and I need to print in my printer at
> home, I should be able to do it, I shouldn’t be “hacking” my way around
> that. In a v6 world, this is going to be common practice, the fact that
> we have limitations on how we use our home networks today does not mean
> that those same restrictions will exist in the future.
>
> Perhaps the approach is (if identified as a problem), to have
> printer.home be on a controlled interruption list for a while, so people
> can identify and fix their setups.  I don’t know, but the approach where
> we ban the whole TLD from ever existing because of few that misconfigured
> their naming, doesn’t seem reasonable to me. (few compared to the rest of
> the world who will be connected in the future).
>
> Should we also add a .BELKIN TLD?, there are tons of devices that use it
> (to name a few), what if in 10 years someone decides to create .FOOBARBAZ
> are we going to add it to the list later?,
>
> We need a better view/picture of the whole DNS ecosystem, we should not
> be making assertions based on a 24 hour sample of 1 day of root server
> traffic, let put more effort into strategy for the long term and not be
> so tactical about these specific use cases.
>
> Regards,
>
>
> Francisco Obispo
> CTO - Registry Operations
> ____________________________
>
>  <http://www.uniregistry.com/>
> 2161 San Joaquin Hills Road
> Newport Beach, CA 92660
>
> Office [phone] x4202
> [e-mail]

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]