Original text:
record is called the "RDATA", and the authoritative answer bit is often called "the AA flag" or "the AA bit".  The most commonly-used rough definition is that the QNAME is a field in the Question section of a query.  "A standard query specifies a target domain name (QNAME), query type (QTYPE), and sequence of a specific transaction.  (Definition from RFC6891, Section 6.1.1) It is used by EDNS. <del> The domain name where a RR is found (RFC1034, Section 3.6).  Often appears in the term "owner name". </del>  DNS documents, including the definitions here, often refer to the fields in the RDATA of an SOA resource record by field name. "A DNS server that implements DNS over TLS RFC7858 and may optionally implement DNS over DTLS RFC8094."  (Quoted from <del> RFC8310, Section 2) </del>  7. CNAME Canonical name Child  Class independent Closest encloser Closest provable encloser

Reviewer comments:
I like the additional wording. I'll add it and take the question to the chairs to take to the WG.
Good catch on "DNS over TLS" -> "DNS over HTTPS". I didn't go with "DNS Queries over HTTPS" because it doesn't really describe the protocol.
Simple mistake: "DNS over TLS" should be "DNS over HTTPS" at line 1040. Or "DNS Queries over HTTPS" may be better because it is a draft name.If we're going to add class here, then I think (1) we need to go back to the WG and (2) we need to add something: "In practice, the class for nearly every query is IN. There are some queries for CH, but they are usually for the purposes of information about the server itself rather than for a different type of address" I wrote a doc some time ago attempting to deprecate class, because of the way it keeps popping up as though it is viable.

Revised text:
record is called the "RDATA", and the authoritative answer bit is often called "the AA flag" or "the AA bit". <ins> A class "identifies a protocol family or instance of a protocol" (Quoted from RFC1034, Section 3.6).  "The DNS tags all data with a class as well as the type, so that we can allow parallel use of different formats for data of type address."  (Quoted from RFC1034, Section 2.2).  In practice, the class for nearly every query is "IN".  There are some queries for "CH", but they are usually for the purposes of information about the server itself rather than for a different type of address. </ins> The most commonly-used rough definition is that the QNAME is a field in the Question section of a query.  "A standard query specifies a target domain name (QNAME), query type (QTYPE), and sequence of a specific transaction.  (Definition from RFC6891, Section 6.1.1) It is used by EDNS.  <ins> "The domain name where a RR is found" (Quoted from RFC1034, Section 3.6).  Often appears in the term "owner name". </ins> DNS documents, including the definitions here, often refer to the fields in the RDATA of an SOA resource record by field name. "A DNS server that implements DNS over TLS RFC7858 and may optionally implement DNS over DTLS RFC8094."  (Quoted from  <ins> RFC8310, Section 2) Other types of DNS servers might also be considerd privacy-enabling, such as those running DNS over HTTPS I-D.ietf-doh-dns-over-https. </ins> 7. CNAME Canonical name Child <ins> Class </ins> Class independent Closest encloser Closest provable encloser