On Fri, Oct 21, 2022 at 2:31 PM Paul Hoffman <paul.hoff...@icann.org> wrote:
> >> .alt will be treated like any other pseudo-TLD regardless of the > context. > > > > Sorry, I don't understand. I believe "pseudo-TLD" here means "a name > that resolves to NXDOMAIN". > > It is defined in this very document as "A label that appears in a > fully-qualified domain name in the position of a TLD, but which is not part > of the global DNS." > > > Most URI schemes are pretty clear about what happens in this case: the > resource cannot be accessed. > > That seems like the right thing for them to specify. > > >> If you think that URIs that have names that are not part of the global > DNS should be treated differently by URI consumers, by all means write a > draft about it. > > > > This is not about "global DNS" vs. some view of the DNS. > > It really is. See the definition in the draft. Firstly, I don't think it makes sense to define "DNS context" as limited to the IANA root. I would prefer a term like "non-IANA-root context". Secondly, the draft contradicts itself. For example, it says ".alt is always used to denote names that are to be resolved by non-DNS protocols". But surely one can speak to non-IANA DNS roots using the DNS protocol? 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.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
