Re: [DNSOP] Review of draft-ietf-dnsop-terminology-bis-08

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 18 December 2017 14:11 UTC

Return-Path: <bortzmeyer@nic.fr>
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 AF3BF12895E for <dnsop@ietfa.amsl.com>; Mon, 18 Dec 2017 06:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.01
X-Spam-Level:
X-Spam-Status: No, score=-5.01 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 CoQfg19Asy9Q for <dnsop@ietfa.amsl.com>; Mon, 18 Dec 2017 06:11:14 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C02E12708C for <dnsop@ietf.org>; Mon, 18 Dec 2017 06:11:14 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id E499D28211A; Mon, 18 Dec 2017 15:11:12 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id DE8DA282260; Mon, 18 Dec 2017 15:11:12 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id D73F228211A; Mon, 18 Dec 2017 15:11:12 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id D3D5B642A7A1; Mon, 18 Dec 2017 15:11:12 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id C8168401D4; Mon, 18 Dec 2017 15:11:12 +0100 (CET)
Date: Mon, 18 Dec 2017 15:11:12 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Martin Hoffmann <martin@opennetlabs.com>
Cc: dnsop@ietf.org
Message-ID: <20171218141112.56cxoc5nvt3wlsdf@nic.fr>
References: <20171130133600.447a2904@grisu.home.partim.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20171130133600.447a2904@grisu.home.partim.org>
X-Operating-System: Debian GNU/Linux 9.2
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.098608, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.12.18.140316
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xeJuheM9h8HKnDgV2KfPR6x8F2U>
Subject: Re: [DNSOP] Review of draft-ietf-dnsop-terminology-bis-08
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: Mon, 18 Dec 2017 14:11:16 -0000

On Thu, Nov 30, 2017 at 01:36:00PM +0100,
 Martin Hoffmann <martin@opennetlabs.com> wrote 
 a message of 297 lines which said:

> GLOBAL DNS -- FORMAT OF NAMES
> 
> | Names in the common display format are normally written such that the
> | directionality of the writing system presents labels by decreasing
> | distance from the root (so, in both English and C the first label in
> the | ordered list is right-most; but in Arabic it may be left-most,
> depending | on local conventions).
> 
> The first sentence makes it sound as if right-to-left languages would
> normally write ‘com.example’ which is not the case.

BiDI is complicated enough so I suggest we keep only examples where
the script of the domain name is the same as the parent script. This
way, sentences like "The TLD is at the end" are always true. Writing a
latin domain name in arabic is left as an exercice for the reader :-)

> under these circumstances the name will always be in the ‘usual’
> order.

I challenge this assumption. After all, numbers in arabic are
sometimes big-endian and sometimes little-endian (depending on wether
you are in the Middle-East or in North Africa).

> PRIMING
> 
> This comes a bit suddenly. Maybe it should start with a short
> introduction a la ‘In order to operate in recursive mode, a resolver
> needs to know the address of at least one root server.’

IMHO, the reference to the excellent RFC 8109 is sufficient.

> PASSIVE DNS
> 
> | A mechanism to collect DNS data by storing DNS transactions from name
> | servers.  Some of these systems also collect the DNS queries
> associated | with the responses.
> 
> I don’t think it has been defined yet, but the term ‘transaction’
> commonly refers to a pair of a query and its response (plus possibly
> any re-sent queries or responses due to packet loss). With this in
> mind, the second sentence doesn’t quite make sense.

I agree and I suggest this text:

Passive DNS:  A mechanism to collect DNS data by storing DNS
      responses from name servers.  Some of these systems also
      collect the DNS queries associated with the responses, although
      it raises some privacy concerns.  Passive
      DNS databases can be used to answer historical questions about DNS
      zones such as which values were present at a given time in the
      past, or when a name was spotted first.  Passive DNS databases allow searching of the stored records
      on keys other than just the name and type, such as "find all names
      which have A records of a particular value".

> IN-BAILIWICK
...
> Also, on behalf on non-native speakers, a short explanation of the
> origin of the term would perhaps be nice.

I like the Wiktionary (and it can be copied freely into a RFC):

Etymology
>From bailie (“bailiff”) and wick (“dwelling”), from Old English wīc.

bailiwick (plural bailiwicks)

    The district within which a bailie or bailiff has jurisdiction.

        The Bailiwick of Jersey.

    A person's concern or sphere of operations, their area of skill or authority. 

Synonyms

    (area or subject of authority or involvement): domain, department, jurisdiction, sphere, territory, turf.