Ben Schwartz <[email protected]> writes: > Rather than placing "alt" in the TLD position, I think it might be better as a > scheme modifier: https+alt://... This is a common pattern for modifications > to > URI schemes (c.f. git+ssh://), and informs the software that this URI is > special > without overloading the DNS namespace.
I suspect many of us would agree that's the best ideal way forward, except that the proponents of the alternate names want their names to be as DNS-like as possible so it works with *all* applications. All new ones may support extensions and URIs, etc. I'm not sure telnet, nntp readers, etc do/will. I don't even know how to enumerate all the places where a domain name is expected (endless GUIs) that don't have an appropriate name space selector option. Certainly a "too bad for you" approach for situations like that, but I suspect that's going against what the alternate name space proponents want: minimal upgrades to existing software [right or wrong as that may be -- no judgment here]. -- Wes Hardaker USC/ISI _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
