Juliusz Chroboczek wrote:
how DNS can be bootstrapped and parent domains delegated to a Homenet
Border Router.
I think we're speaking about different things. You're speaking about
exporting the naming of the Homenet into the ISP (the single ISP, sigh)
and from there into the global DNS, while we're speaking about having
naming *within* the Homenet.
I'm speaking about naming for all potential flows: within homenet, from
the Internet into homenet, out of homenet into the Internet, with
devices moving across the border or remaining static. I've seen enough
instances in corporate networks to know that all of these are relevant
(e.g. when a sleeping device is taken home and then wakes up).
In short -- the ability within the Homenet to do
scp backup-20150827.tar mylaptop.home:backup/
And what happens if you have a regular back up process e.g. rsync that
you want to work no matter where the (server) device is?
and having it work no matter which link the laptop happens to be connected
to.
I'd add whether it was connected to Homenet or the Internet.
I definitely want to be able to have host naming within the Homenet. On
the other hand, I'm not sure if I want my Homenet to be exported to the
global DNS, and if I were to do so,
So maybe we need two (disjoint) name spaces. (Separate from the
discussion about which protocol is used to resolve them)
I certainly wouldn't want a protocol
that forces me to do that through my ISP (the single ISP, sigh).
We've talked about the "single ISP issue" before offline. The draft
mentioned defines the the relationship between one ISP and one homenet.
There's nothing in the draft that forces use of this mechanism for all
names used in the Homenet. There's nothing in that draft that says this
is the only name space on the Homenet. I also don't think it's realistic
to assume that a second ISP will host namespace with addresses from
another ISP. e.g. device1.ips1.net is also resolvable via DNS servers of
isp2.net.
On the other hand the draft does not (yet) specify how to handle the
case of a Homenet connected to multiple ISPs. I don't think that's
particularly problematic, and this is what we should be discussing now.
E.g. If there's a host called "device1", two Homenet border routers
could independently register device1's IPv6 address derived from the
prefix associated with their ISP(s) in the relevant ISP's name space.
i.e. device1.isp1.net creates an AAAA record and PTRv6 for device1
associated with the GUA prefix delegated from IPS1, and device1.isp2.net
creates an AAAA record and PTRv6 record for device1 associated with the
GUA prefix delegated from ISP2; and then having a DNS domain search list
communicated to all end hosts via DHCPv6 or containing both isp1.net and
isp2.net, so when an app resolves the name "device1" via DNS it receives
both AAAA records (from different servers).
There's also nothing yet to say that "device1" could not also resolve to
a site local IPv6 address via mDNS.
So in short: I'm thinking Homenet might need multiple name spaces,
multiple name registration and resolution protocols, multiple servers;
each tightly bound to the relevant (delegated) address scope and
(delegated) top level domain.
-- Juliusz
--
regards,
RayH
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
