Last Call Review of draft-ietf-dnsop-terminology-bis-11
review-ietf-dnsop-terminology-bis-11-opsdir-lc-romascanu-2018-08-06-00

Please find below the ops-dir review of draft-ietf-dnsop-terminology-bis. I
reviewed version 11 of the document.

This document obsoletes RFC 7719, updating and expanding the range of
definitions for the DNS protocols and systems, bringing it in line with the
current use. From the operator community this is a very important and useful
document, as it provides a one hop reference for the important terms in the
deployment and operation of the DNS. As this is not a new protocol, or an
existing protocol extension, an RFC 5706 review does not apply.

This document is Ready from the OPS-DIR perspective. The comments below could
be addressed to improve clarity, but they are not show-stoppers:

1. One important difference between Informational RFC 7719 and the current
document is its elevation to the status of BCP. There must be good reasons for
this decision (like avoiding downrefs in new work, other), and I believe that
it would be useful to include a short justification, maybe in the Introduction
section, in case the document will be approved and published as a BCP.

2. In section 2:

'An ordered list of zero or more octets and which makes up a
      portion of a domain name.'

This sentence seems to be broken, it is not clear what 'and' relates to.

3. In section 2:

' At the time this
      document is published, that operator is Public Technical
      Identifiers (PTI).'

A reference would be useful.

4. In section 5:

I cannot find a definition of the term 'resource record' itself. I can see RR
as acronym, then a discussion of RRset, etc., but not the term itself. Do I
miss something?

5. I cannot find a definition or expansion of SOA. I can see 'SOA field names',
'SOA resource records', etc. but not just 'SOA'

6. Section 6:

'Master server:  See primary server.

 Primary master: '

Is it 'Primary server' or 'Primary master'?

7. I cannot find a definition for 'NS records'

8. I found the Index to be very useful, and I wish other documents of this size
and complexity (or worse) include such a section.