On 7/20/16 6:01 AM, Ralph Droms wrote: > >> On Jul 20, 2016, at 11:50 AM 7/20/16, Juliusz Chroboczek >> <[email protected]> wrote: >> >>>> We want something short and memorable. ".co.uk" is short and >>>> memorable. ".univ-paris-diderot.fr" is not. >> >>> Why? This is, I suspect, part of the issue: it seems that we >>> have some assumptions about the use of these names, and I'm not >>> entirely sure what they are. It is not obvious to me that "short >>> and memorable" is a requirement that falls out of section 3.7 of >>> RFC 7368. >> >> I suggest we put this question to the WG. Perhaps the chairs would >> be willing to ask whether the WG would prefer a name that is short >> and memorable, or one that is long and impossible to remember? > > I think there are some important questions to answer first: > > What is the meaning of .home and, precisely, how will names that end > in .home be resolved? > > Where and by whom will this label actually be used? What is the > research to back up the answer? > > Although many people have given me a answer to the first question, > and the answers often include phrases like "it just means..." or > "everybody agrees that..." or "it's obvious...", I don't think I've > seen a citable definition for the intention and semantics of .home; > pointers welcome. > > Without that definition, I don't think I know where and by whom the > label will actually be used. Will it turn out to be like .local, > which, as far as I know, is rarely used anywhere and only ever by a > certain class of expert user. >
If the above holds, I would suggest (only partly in jest) a TLD that contains a certain unicode value that can be visually displayed by an OS... http://apps.timwhitlock.info/unicode/inspect/hex/1F3E0 Regards, Brian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
