In message <[email protected]>, Stephane Bortzmeyer writes: > On Fri, Sep 21, 2012 at 06:32:01PM -0700, > David Conrad <[email protected]> wrote > a message of 27 lines which said: > > > I understand and sympathize with this point of view, however, as a > > counter-example: wildcards in .COM were outside of the root zone, > > was that also none of ICANN's business? > > In a way, .COM is special: it is by far the largest TLD and for many > people the reference TLD. One can probably argue that it has a form of > dominance on the market that calls for special rules. > > But in the case of wildcards in .COM, there was another reason: they > did not exist at the beginning and people were used to a .COM without > wildcards. Adding them later broke this assumption and created a lot > of problems. On the other hand, wildcards in .MUSEUM were never a big > cause of uproar because .MUSEUM had wildcards from the beginning.
And hierachical hostnames are defined as having *interior* periods and the world moved from a flat namespace to a hierachical namespace 2 decades ago. Leaving simple names for private use. This includes "localhost" which is private use. Just because the DNS software did not prevent A, AAAA and MX records being added does not mean that adding them was right. Adding A, AAAA and MX record or using equivalent mechanisms to top level labels is taking away the use of simple labels from everyone else. Mark > _______________________________________________ > dns-operations mailing list > [email protected] > https://lists.dns-oarc.net/mailman/listinfo/dns-operations > dns-jobs mailing list > https://lists.dns-oarc.net/mailman/listinfo/dns-jobs -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
