> Saying that .internal being like every other TLD that already does > not exist today "adds a stumbling block" is absurd. Names that > don't exist don't exist.
Problem is not with names that do not exist. There are many names that do not exist today and pose no problems. The problem starts when a standards track document promotes a name that does not exist for some purposes. That's a situation that requires careful handling. Either by not having such a document in the first place or by making sure that the name that does not exist can be used safely without manual configuration on any end-user device that happens to include a DNSSEC validator. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
