On 31.8.2015, at 14.42, Ray Hunter (v6ops) <[email protected]> wrote: > Also DND SD (RFC 6763) states "Address-based Domain Enumeration queries are > performed using names under the IPv6 reverse-mapping tree" which is under the > direct control of the individual upstream ISPs. > > So, what are people expecting to happen here? > ISP's to cooperate with independent name services when sending a DHCPv6 > delegation of a namespace e.g. a party like DYNDNS? So the Homenet learns > everything via one neatly packaged DHCPv6 exchange with each upstream > provider? > Multiple upstream DNS services that need to be updated? > Overlapping namespaces? > Multiple namespace delegation via multiple mechanisms? e.g. Homenet learns > the reverse tree from the upstream ISP (via DHCPv6), and forward delegation > (glue records) are entered via the domain registrar via http or something > else?
I am not very fond of idea of having to push anything to ISP for my _home_ network to work _within home_. Looking at IPv4, my 10.* address resolution is not provided by the ISP; sure, with IPv6 that is possible, but I don’t think it should be mandatory. That implies DNS server in the home. Whether that is synchornized with ISP side (e.g. hidden master, ISP server actually just having NS records pointing towards home) is a matter for discussion and how that synchronization is established. > Is this what we want for IPv6, or do we have to deal with seeding information > into multiple upstream DNS’s? How does this work when ISP connection is down? > Permitting inbound services and restoring the end to end architecture of the > Internet is a big part of Homenet IMVHO Would be nice to have of course. -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
