Paul Vixie <p...@redbarn.org> wrote: > On Monday, 15 June 2020 17:58:42 UTC Tim Wicinski wrote: > > > > or since domains are cheap, why not buy a new domain, and use that for the > > namespace? > > that makes internet viral, and private communications require global > allocations for no necessary reason. the above quite describes centralization > for the sake of centralization. nothing should be centralized unless there's > no other way to do what needs doing. > > reserving a corner of the namespace for decentralized operations makes sense.
There are perhaps three contexts that you might want a private namespace: * enterprisey setups * home setups * splendid isolation For both the enterprise and home case, you're probably going to want to do things beyond the DNS that are much easier if you're part of a global namespace - TLS certs are probably the main one. For the enterprise case, getting a suitable domain is normal. For the home case, it would make sense for manufacturers of home gateways / access points to allocate a per-customer subdomain. Then you can have IPv6 prefix delegation and managed access to your devices at home without everything being proxied via some cloud server. (I can dream?) For splendid isolation, you're already committing to setting up your own CA and distributing keys, so you can probably set up your own fake root zone and whatever else. I don't think it's something that should be encouraged as a standard thing to do, though. How could it be made to work usefully for non-technical home users? Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ Lands End to St Davids Head including the Bristol Channel: Variable 2 to 4. Slight in west, smooth in east. Showers, thundery at times. Good, occasionally poor. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
