Draft: draft-ietf-dnsop-terminology-bis-latest

Commentary: Agree with the first one , although I do n't care which way it comes out from the RFC Editor . For the second one , I have changed the wording to ' An authoritative server is named in the NS ( " name server " ) record in a zone . ' We do n't need to stray into which zone has authoritative data ; the double use of " authoritative " will confuse the reader without helping with the terminology . 
 l 179 , s / octets which / octets that . This has been changed to violate the that / which conventions of the RFC Editor . l844 ( new ) the authoritative name server is named in the parent zone but is not authoritative data there ( NS is authoritative in the child ) . This is discussed elsewhere in the document , and I find this addition confusing . I wo n't hold up pver either of these . The rest looks ok .
An ordered list of zero or more octets and which makes up a
portion of a domain name.  Using graph theory, a label identifies
one node in a portion of the graph of all possible domain names.
An ordered list of zero or more octets that makes up a portion of
a domain name.  Using graph theory, a label identifies one node in
a portion of the graph of all possible domain names.
Administration of names -- Administration is specified by
delegation (see the definition of "delegation" in zones).
Policies for administration of the root zone in the global DNS are
determined by the names operational community, which convenes
itself in the Internet Corporation for Assigned Names and Numbers
(ICANN).  The names operational community selects the IANA
Functions Operator for the global DNS root zone.  At the time this
document is published, that operator is Public Technical
Identifiers (PTI).  The name servers that serve the root zone are
provided by independent root operators.  Other zones in the global
DNS have their own policies for administration.
Administration of names -- Administration is specified by
delegation (see the definition of "delegation" in zones).
Policies for administration of the root zone in the global DNS are
determined by the names operational community, which convenes
itself in the Internet Corporation for Assigned Names and Numbers
(ICANN).  The names operational community selects the IANA
Functions Operator for the global DNS root zone.  At the time this
document is published, that operator is Public Technical
Identifiers (PTI).  (See <https://pti.icann.org/> for more
information about PTI operating the IANA Functions.)  The name
servers that serve the root zone are provided by independent root
operators.  Other zones in the global DNS have their own policies
for administration.
DNS documents, including the definitions here, often refer to the
fields in the RDATA of an SOA resource record by field name.
Those fields are defined in Section 3.3.13 of RFC1035.  The names
(in the order they appear in the SOA RDATA) are MNAME, RNAME,
SERIAL, REFRESH, RETRY, EXPIRE, and MINIMUM.  Note that the
meaning of MINIMUM field is updated in Section 4 of RFC2308; the
new definition is that the MINIMUM field is only "the TTL to be
used for negative responses".  This document tends to use field
names instead of terms that describe the fields.
DNS documents, including the definitions here, often refer to the
fields in the RDATA of an SOA resource record by field name.
"SOA" stands for "start of a zone of authority".  Those fields are
defined in Section 3.3.13 of RFC1035.  The names (in the order
they appear in the SOA RDATA) are MNAME, RNAME, SERIAL, REFRESH,
RETRY, EXPIRE, and MINIMUM.  Note that the meaning of MINIMUM
field is updated in Section 4 of RFC2308; the new definition is
that the MINIMUM field is only "the TTL to be used for negative
responses".  This document tends to use field names instead of
terms that describe the fields.
"A server that knows the content of a DNS zone from local
knowledge, and thus can answer queries about that zone without
needing to query other servers."  (Quoted from RFC2182,
Section 2.)  It is a system that responds to DNS queries with
information about zones for which it has been configured to answer
with the AA flag in the response header set to 1.  It is a server
that has authority over one or more DNS zones.  Note that it is
possible for an authoritative server to respond to a query without
the parent zone delegating authority to that server.
Authoritative servers also provide "referrals", usually to child
zones delegated from them; these referrals have the AA bit set to
0 and come with referral data in the Authority and (if needed) the
Additional sections.
"A server that knows the content of a DNS zone from local
knowledge, and thus can answer queries about that zone without
needing to query other servers."  (Quoted from RFC2182,
Section 2.)  An authoritative server is named in the NS ("name
server") record in a zone.  It is a system that responds to DNS
queries with information about zones for which it has been
configured to answer with the AA flag in the response header set
to 1.  It is a server that has authority over one or more DNS
zones.  Note that it is possible for an authoritative server to
respond to a query without the parent zone delegating authority to
that server.  Authoritative servers also provide "referrals",
usually to child zones delegated from them; these referrals have
the AA bit set to 0 and come with referral data in the Authority
and (if needed) the Additional sections.
See "Secondary server".
See secondary server.
See "Primary server".
See primary server.