On 28.8.2015, at 11.09, Henning Rogge <[email protected]> wrote: > On Fri, Aug 28, 2015 at 9:49 AM, Markus Stenberg <[email protected]> > wrote: >> On 28.8.2015, at 10.02, Henning Rogge <[email protected]> wrote: >>> So what IS the proposed solution for a decentralized HNCP configured >>> homenet to share local "configured" DNS names with the rest of the >>> homenet? >> >> For sharing in general, there are two methods (as far as HNCP goes); >> >> - publish a DNS Delegated Zone TLV that points to a (local or remote) DNS >> server that responds for that zone. > central server sounds bad for “distributed network".
There isn’t uniqueness constraint on those TLVs, so you could have multiple. That would work already OOTB. You could relatively easily define primary server auto-election mechanism and then e.g. do AXFRs between them. >> - publish Node Name TLVs for individual nodes (won’t scale forever, but >> possibly enough). > That could work... still, if every DNCP node publishes a DNS name for > the node (and maybe another one for a few locally attached non-DNCP > hosts) this would increase the size of the DNCP database a little bit. > Wasn’t there a size limit for the database (or was it per node?)? Per node, so not probably that big issue. Especially as you can create infinite number of fake nodes anyway if you feel like it (c.f. the older DNCP drafts’ fragmentation scheme that was removed due to lack of implementation / correctness validation). Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
