[DNSOP] Mirja Kühlewind's No Objection on draft-ietf-dnsop-terminology-bis-13: (with COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Fri, 24 August 2018 16:05 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 013E1128CFD; Fri, 24 Aug 2018 09:05:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dnsop-terminology-bis@ietf.org, Suzanne Woolf <suzworldwide@gmail.com>, dnsop-chairs@ietf.org, suzworldwide@gmail.com, dnsop@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153512671800.23080.10672402309953864375.idtracker@ietfa.amsl.com>
Date: Fri, 24 Aug 2018 09:05:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Skj9xGD4rzrcLu7d3KC6Or-iHuA>
Subject: [DNSOP] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-dnsop-terminology-bis-13=3A_=28with_COMMENT=29?=
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2018 16:05:18 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-dnsop-terminology-bis-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-terminology-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm actually not sure if this doc really updates RFC2308 because the two
definitions (Forwarder and QNAME) only say someting like "it is used
differently today" but seem not really to actually update the existing
definitions. I would recommend to either not use the "update" tag or clarify
these definitions.

Thanks for the clarification added based on the TSV-ART review (and thanks
Allison!).

(Potential) nits:
1) OLD:
A set of resource records with the same label, class and
      type, but with different data.  (Definition from [RFC2181])
MAYBE use quotes here at least for the last part of the sentence:
A set of resource records "with the same label, class and
      type, but with different data."  (Definition from [RFC2181])

2) s/Section 4.3.1 of of [RFC1034] /Section 4.3.1 of [RFC1034]/

3) Probably the first sentence should be removed:
"The idea of a primary master is only used by [RFC2136],
      and is considered archaic in other parts of the DNS.

      The idea of a primary master is only used in [RFC1996] and
      [RFC2136]. "

4) Why is there (a) and (b) for the definition of Origin?