>What I'm asking is how the octet sequences provided by the URI RR RFC >are decoded into the sequences of URI characters used by the URI RFC. >Is there a generic way to do this, or does it depend on the specific >protocol (e.g., HTTP), or is it left up to the application?
As far as I can see, RFC 3986 defines URIs as sequences of ASCII characters. In the few places where they mention non-ASCII material, it says to represent them as percent encoded UTF-8, so it's still all ASCII. Can you give an example of URI RDATA where it would make sense to interpret it other than as ASCII? I suppose to be perfectly clear we might either say "percent encode everything" or we might say "unencoded UTF-8 is allowed." They're both unambigious, and I expect most parsers can handle both. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
