Mark Andrews wrote:
names which do not terminate in "." (and in some cases, which might not
permit such name termination).
Consider the label "foo.bar", a stub resolver, a recursive resolver, new
TLD "bar", and existing SLD "example.com".
Partially qualified domains and search lists are always dangerous
unless you never use a partial name which matches a tld.
Exactly!
The problem is a "who choses last" problem.
Anyone who is using a partial name, which *then* becomes a new TLD, gets
the surprise results.
And, as the new rules are likely to result in TLDs with more
semantically meaningful values, there is greater
likelihood that such problems will appear.
Especially for TLDs with geographic significance. ".asia" was bad
enough, but what if the various FAA airport codes
get used by the respective airport authorities as new TLDs?
How many operators have infrastructure naming schemes based on FAA
codes? How much chaos might occur if new
TLDs like "CHI", "NYY", "LAX", "SEA", or "YYZ" come into existence?
(Shudder).
That's precisely why it makes sense to think about the partial name
problem, before big problems happen for lots of ISPs.
Brian
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
