ICANN may not have handed it out yet, and may be on a hold about doing so, but many still expect some resolution to that road block. I certainly do. Making assumptions about icann‘s future behavior on this _policy_ issue is a bad bet. Some questions I still do not understand the answers for - why do you need a TLD? Why won't a SLD work? - why do you need a word from natural language? I know many still maintain the myth that it is a coincidence when a string matches natural language, but many have other used for natural language words. In fact I assume you picked it because of its similarity to a natural world. But why do you need it? - what sort of implementer hard codes name strings in their code? Avri( coincidentally Co-chair ICANN new gTLD Subsequent Procedures working group) Sent from my T-Mobile 4G LTE Device -------- Original message --------From: Mikael Abrahamsson <[email protected]> Date: 7/18/16 15:33 (GMT+01:00) To: Terry Manderson <[email protected]> Cc: HOMENET <[email protected]>, Ray Bellis <[email protected]> Subject: Re: [homenet] RFC 7788 and ".home"
The option 4 mentioned updating RFC7788. It's not clear to me what this update would be. .HOME has not been handed out by ICANN yet, what's the odds that RFC6761 process reserving .HOME for special use would succeed? -- Mikael Abrahamsson email: [email protected] _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
