Hi, According to RFC 7553 §4.5, the Target field in URI RDATA is a "sequence of octets":
The RDATA for a URI RR consists of a 2-octet Priority field, a 2-octet Weight field, and a variable-length Target field. Priority and Weight are unsigned integers in network byte order. The remaining data in the RDATA contains the Target field. The Target field contains the URI as a sequence of octets (without the enclosing double-quote characters used in the presentation format). There doesn't seem to be any further information about how the sequence of octets is encoded or decoded. According to RFC 3986 §2, The URI syntax provides a method of encoding data, presumably for the sake of identifying a resource, as a sequence of characters. The URI characters are, in turn, frequently encoded as octets for transport or presentation. This specification does not mandate any particular character encoding for mapping between URI characters and the octets used to store or transmit those characters. When a URI appears in a protocol element, the character encoding is defined by that protocol; without such a definition, a URI is assumed to be in the same character encoding as the surrounding text. What character encoding should be used when decoding the Target field of a URI RR? It seems to me that the protocol transmitting the octets hasn't defined the encoding of the octets (it just says that there's a sequence of them) and that there's no "surrounding text" in a DNS wire format message that can inform the decoder either. Thanks! -- Robert Edmonds _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
