> - why do you need a TLD? Why won't a SLD work? We want something short and memorable. ".co.uk" is short and memorable. ".univ-paris-diderot.fr" is not.
> - why do you need a word from natural language? We want something short and memorable. ".home" is short and memorable. ".in-addr.arpa" is not. > - what sort of implementer hard codes name strings in their code? I do. This group is designing a set of protocols that are meant to enable an intelligent layman to deploy a well-designed (no NAT) local area network. We use a number of techniques, such as highly refined distributed consensus algorithms, but also defaulting to standardised values where flexibility is not needed or not desirable. In the particular case of the choice of the top-level domain, there is agreement in this WG that having a standardised default is more robust, more predictable, and easier to understand than using a distributed consensus algorithm. As to how this is implemented (hard-wired in the code or learned from a configuration file that is shipped with standard-compliant defaults) -- with all due respect, that is none of your business. -- Juliusz _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
