-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/05/2015 03:25 PM, David Conrad wrote: > > I think you missed Andrew's point. > *** Thank you David for shedding some light.
> All 6 technologies use a string that looks like a domain name > but isn't intended for use in the DNS. Why does it matter if there is > a '.' in the middle of that string? That is, given the technology is > presumably going to intercept the domain name before it gets sent to a > resolver, why would it not be possible to use (say) BIT.ALT instead > of .BIT? > *** Our next draft will certainly address this point. I would say, like Christian: usability. But for a completely different reason. If it makes sense to delegate a subtree and tell the implementors: "now, for all domains under the .alt DNS subtree, you MUST check what is the correct assignment and resolution strategy for each domain, and you MUST handle the domains accordingly.", then I guess it makes sense to use .bit.alt, and then .cjdns.alt, and .fubar.alt, etc. as long as each SUBDOMAIN will use a different strategy for handling names. On the other hand, if we want to keep a sane base, we'd rather identify, circumscribe and announce the various existing strategies, and hope that future strategies that may or may not appear will have a solid foundation for incorporating their innovative strategy into the global name space. Our group chose the latter. Regards, == hk -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUqy0EXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0 ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg94mQP/2NIS70S8Pf8ZaoXsOy0uMG7 57IL7+0DQSug60NSeZBcSMqEBZsMUdtWA5gnnxTph6nSQaDCDdyGuE8UghhoMSTO nKr8rjUDeCMOGoYOmB5z1ldhJkezz4b1ryRPVqQoClne4aJvnVzLwB5hCeGYVi1B vZAC9BgkctdMMPcTv7lD2nc2cOv0C8qXxAiG9fPT+sTrYoaTm0j47+spyWx73NF9 eJWlpu4/Q6xgNzoShBoGAB/e6+5W1sOTLNMLwQMaSF/Yof54q2Uj+T/JOCLFQx0U e8czocLdhym1dXtEJwW686Q6XZjEGJ8kvfkGjqjChASkhuzD5P5+Wg6DLX6AmmMC Z5kc0ltuZuTKheKbOzoVmL2HAmvW6qwKJgyCcKGFMvVyG0ddcdroylpsQ/F5G9ha Pw+DCIqdti9nPS8x+DSQR9JPsKWGPbZaQ8Su/AWhIr/z2Zw5nbo1iMLcmMmbWuXd rIWYaCd3RPIq0P0tIN6gnCIEXSI5HkH0E+GPxPcapWCZT16Oz9NqBBu85xp9x7aC 4zY5Bj8IeRu9GQy+ilH4EzFMALwu1qm0bXINmPiJlhUBkbMbsT0SJUg2Qx/9lvLm +8Qm7bJm70QT3hsasXTWD8z+5/PD+cFA1zR3CRqYIt5KVYOoeA2YGBdDyaxmKfsT wFGvQzZ1jGSwx82NmA+C =tBlR -----END PGP SIGNATURE----- _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
