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

Commentary: … st label ' , and remove dbound . Fix affiliation . I suggest these before publication . This addresses issue 18 . 
 Yep , these all seem great .
Composition of names -- A name in the global DNS has one or more
labels.  The length of each label is between 0 and 63 octets
inclusive.  In a fully-qualified domain name, the first label is 0
octets long; it is the only label whose length may be 0 octets,
and it is called the "root" or "root label".  A domain name in the
global DNS has a maximum total length of 255 octets in the wire
format; the root represents one octet for this calculation.
Composition of names -- A name in the global DNS has one or more
labels.  The length of each label is between 0 and 63 octets
inclusive.  In a fully-qualified domain name, the first label
(logically speaking) is 0 octets long; it is the only label whose
length may be 0 octets, and it is called the "root" or "root
label".  A domain name in the global DNS has a maximum total
length of 255 octets in the wire format; the root represents one
octet for this calculation.
"A domain that is controlled by a public registry."  (Quoted from
RFC6265, Section 5.3) A common definition for this term is a
domain under which subdomains can be registered, and on which HTTP
cookies (RFC6265) should not be set.  There is no indication in a
domain name whether it is a public suffix; that can only be
determined by outside means.  In fact, both a domain and a
subdomain of that domain can be public suffixes.  At the time this
document is published, the IETF DBOUND Working Group DBOUND is
dealing with issues concerning public suffixes.
"A domain that is controlled by a public registry."  (Quoted from
RFC6265, Section 5.3) A common definition for this term is a
domain under which subdomains can be registered, and on which HTTP
cookies (RFC6265) should not be set.  There is no indication in a
domain name whether it is a public suffix; that can only be
determined by outside means.  In fact, both a domain and a
subdomain of that domain can be public suffixes.
Note that the term "public suffix" is controversial in the DNS
community for many reasons, and may be significantly changed in
the future.  One example of the difficulty of calling a domain a
public suffix is that designation can change over time as the
registration policy for the zone changes, such as the case of the
"uk" TLD around the time this document is published.
Note that the term "public suffix" is controversial in the DNS
community for many reasons, and may be significantly changed in
the future.  One example of the difficulty of calling a domain a
public suffix is that designation can change over time as the
registration policy for the zone changes, such as was the case
with the "uk" TLD in 2014.
For teminology specific to the public DNS root server system, see
RSSAC026.  That document defines terms such as "root server", "root
server operator", and terms that are specific to the way that the
root zone of the public DNS is served.
For terminology specific to the public DNS root server system, see
RSSAC026.  That document defines terms such as "root server", "root
server operator", and terms that are specific to the way that the
root zone of the public DNS is served.
A security-aware recursive name server, security-aware resolver,
or security-aware stub resolver that is applying at least one of
the definitions of validation (above), as appropriate to the
resolution context.  For the same reason that the generic term
"resolver" is sometimes ambiguous and needs to be evaluated in
context (see dns-servers-and-clients), "validating resolver" is a
context-sensitive term.