[DNSOP] my comments on draft-ietf-dnsop-terminology-bis

Paul Vixie <paul@redbarn.org> Fri, 14 April 2017 19:07 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE28512954B for <dnsop@ietfa.amsl.com>; Fri, 14 Apr 2017 12:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxnPk25fEOVv for <dnsop@ietfa.amsl.com>; Fri, 14 Apr 2017 12:07:12 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E049F12946D for <dnsop@ietf.org>; Fri, 14 Apr 2017 12:07:12 -0700 (PDT)
Received: from [192.168.2.98] (unknown [78.180.239.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 4CF8561F9E for <dnsop@ietf.org>; Fri, 14 Apr 2017 19:07:10 +0000 (UTC)
Message-ID: <58F11DDA.9040307@redbarn.org>
Date: Fri, 14 Apr 2017 12:07:06 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.12 (Windows/20170323)
MIME-Version: 1.0
To: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mAc3po9h933I0KCWoVJm4AnC8bI>
Subject: [DNSOP] my comments on draft-ietf-dnsop-terminology-bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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, 14 Apr 2017 19:07:14 -0000

in the current dns terminology rfc, it editorializes and is inaccurate
by understatement and overstatement concerning the "passive dns" term. i
suggest the following edits, should you decide to retain this text
rather than copy from the COF i-d or from florian's original work:

   Passive DNS:  A mechanism to collect large amounts of DNS data by
      storing DNS responses from servers.  Some of these systems also
      collect the DNS queries associated with the responses; this can
      raise privacy issues.  Passive DNS databases can be used to answer
      historical questions about DNS zones such as which records were
      available for them at what times in the past.  Passive DNS
      databases allow searching of the stored records on keys other than
      just the name, such as "find all names which have A records of a
      particular value".

s/large amounts of//
s/responses/transactions/
s/servers/name servers/
s/; this can raise privacy issues/; done correctly, this raises no
privacy issues/
s/records/answers/
s/available for them/witnessed/
s/the name/the name and type/

-- 
P Vixie