On Tue, Sep 05, 2017 at 06:09:06AM +0200, Walter H. <walte...@mathemainzel.info> wrote a message of 20 lines which said:
> I see it exact this, and it would be fair to prevent future bugs with > defining one or two FAKE TLDs (e.g. .corp, .lan) for exact this use > case; Why does it need to be a TLD (see all the discussions here about Special Use Domain Names, .alt, .alt.arpa, etc)? Why not lan.mycompany.com? > - there isn't really a uniqness as requirement As I said before, and explained, you're wrong here, since you don't take merging and acquisition into account. > - a public WHOIS grabbing for these domains needn't also be given; With a subdomain of your Second Level Domain, no need for WHOIS (or RDAP). But I agree that ICANN rules for the .corp TLDs are stupid. If McDonald's register .MCDONALDS, why do they need delegation and public social info for the SLD? _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
