[DNSOP] draft-hoffman-dns-terminology-ter-01.txt - some comments

Normen Kowalewski <nbkowalewski@gmx.net> Tue, 23 July 2019 00:38 UTC

Return-Path: <nbkowalewski@gmx.net>
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 84E661200DE for <dnsop@ietfa.amsl.com>; Mon, 22 Jul 2019 17:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 otff7_KChSs6 for <dnsop@ietfa.amsl.com>; Mon, 22 Jul 2019 17:38:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783611200BA for <dnsop@ietf.org>; Mon, 22 Jul 2019 17:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1563842241; bh=hCo2m86LpLgipA+Xj54ESygXxHN1QgV8LDY9DixZ7no=; h=X-UI-Sender-Class:From:Subject:Date:Cc:To; b=PbLVGui2E/ctLAT1/cWasXzoUUD3HUP0exA5UJ4vlKYA/x5cg19UuiPIpsUqXmSUE FE3TI4Pa4iGSkw/nCGto1HiX5i2uMY/UTXmIRVWdP8fWIMzu3yEgAIXVRrvuGElCWt c9InneEarzA8afJTHNfnC2bm5AN+XhoT69x+JQdU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.2.168] ([79.249.146.133]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LwrwO-1iVc4101Oa-016LEy; Tue, 23 Jul 2019 02:37:21 +0200
From: Normen Kowalewski <nbkowalewski@gmx.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Message-Id: <7A996832-AD59-4FA4-A6B9-40B39FDAC3D5@gmx.net>
Date: Tue, 23 Jul 2019 02:37:17 +0200
Cc: DNSOP WG <dnsop@ietf.org>
To: bortzmeyer@nic.fr, paul.hoffman@icann.org
X-Mailer: Apple Mail (2.3445.100.39)
X-Provags-ID: V03:K1:Px6G2G8ZJbdGnEyUbvUzCrbTp7hHIS5bk0n5i3/qlETZatMkTbs MrV4XUTGg2pXErTGaX+r1aZrNoArta33fEGuhwkWjGGVeKUkUCORKGuWDwgACTMaULGrKMy JaTuGnsxFcd+BlqJLbLOfRc+5dX5xjhUS8BkD2XC70agWfCzHa3FVUOnWHzmOHT5QN/QCGR iDZF93t5Zq4CTcPnMSncw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:+72PZisoDWc=:8s+//KEzFQSxZTNbHSW7Bt qt6HkqcW5M4xVP7uL3meZMdiiLL46/NbKo9PhSBjZCqAviP2/o+kSELirbhy+x43R36sfwrdK S/P6Cbi4+TF71qzOQQVm1Dsjew7U+EVSYxyszAmYKa4OInTQXHXhXMaE17uOh31lKoEKgbZ/l 9Murc0Em0iDFKjZKQulrPfyMhf81cTb3KjEd+RZbrJBmexahYMtWTRDDaIpHuXNweCcwih6No UF16nrMYNzlu+xK2U7lF1drbmSRmLTSWgScZXiN+AdHScEvNkvDI0ppWdh0yPN8e3IbMvMStV MWx7Nn9JIZW8dpv7tkPJ/P+qAaecjmJRwiluwExMi5FJzrKnCCq6wfWPELMkkoI5nSIwv8Nvl Ysnf6e63FcqzRDH5VUs5Z+SoAwrJxm904YAh5m/qBXJLKpYXj3HDQ/zEPbh1/cM+s/VFEXLAn ZjVEjWwUyY1ZKEozhXuSMSms/LmIDFwyNMhg/vsDGBrrSR0Evic4x12hToEo7r37asp8BmWjr n7jXpAfr8qfB63VjEWsgB5XuDAyDbTqlYT727iKR4XADBi999nhVyih+0cB/Bel9Md1imAnq4 6xogzLQDHeK2vHMcx7i/3IGlEB7zBxmNUmEx/vHeJWrUjqI68O2apAqvsSKiFnXP8oozWNWDK 2V6kho66l68RCma1WLh1M0uBICcFlkq7GUypbOb0XUjjjlKsJ4oHDcyAcJM+ZbmQVdpuIck5u iy3fStAb1EPdIvKLjcuYRvRDAN4eiCuzkdjBfImUY2rUTsRGZa+fFChLEJyU6bxGAAo/RlQnu QRKDwbO3OvNO835mP+m6qYGiivIycanNAHdfMvGC1jOmQ/wslgP2crZCiBe34v5oys8Z5xnLA gekbgWJbLkzqW7wh1XC+l5h4MDyhMCyeuCD5BgWXIUydKAVkH+yDEDvVrzi/0UHviWIUfNzqj XNAW5DoP4nBoh/RU2zESpIc3gBIxkJo5wFDCuGJid/XvT+hzB938N57wIRdZ7qgk8jx9hzH6X 1jC1qoI6NPX/IqVCv3R8Nwm2W+BUDgYCb0gsEd0FbowQt2bZHKGd0A20vYYCs7iCq5PJ8/9Vx /PEKhIpOJjrs4fLILh+TWqiuR0Yi49GJYhj
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZS7IKypbMJkQTR8uRorUYFeOs5s>
Subject: [DNSOP] draft-hoffman-dns-terminology-ter-01.txt - some comments
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Jul 2019 00:38:04 -0000

Daer Stephane, Paul and DNSOP WG, 

1. it was noted in todays meeting that the the “add" is not based on any underlying rfc, and thus might be somewhat  too vague.
+1 on that

draft-hoffman-dns-terminology-ter-01.txt says:
      Applications Doing DNS (ADD):  Applications that act as stub
      resolvers.  This is in contrast to the way that applications
      traditionally have gotten DNS information, which is to use system
      calls to the operating system on the computer, and have the
      operating system act as the stub resolver.  "Applications Doing
      DNS" is not limited to particular transports: it applies equally
      to DNS-over-TLS, DNS-over-HTTPS, Do53, and future DNS transports.
      ( Temporary note, to be removed before publication as an RFC:
      there is a mailing list discussing Applications Doing DNS at
      https://www.ietf.org/mailman/listinfo/add )

While I agree that “add” today covers discussion around the case described in here, but the reason that it covers it  is because “add” acts as a "catch all bucket" for “various DNS things not well defined”.
If we want to cover the case of an application acts as/embed a stub resolver, we may want to define a term (and draft) that covers exactly that, instead of using the much wider term.
 
I wonder if something meant by "add" today, might have to drop from being meant by “add” tomorrow after that feature becomes a well defined RFC?
Terminology would for me have to be less prone to change its meaning over time.

Thus I  propose to remove “add” from the draft.

2.  Share the notion that not all terms are equally well aligned with the names of their underlying transport. Given that Do53 flows via plain UDP/TCP, one could argue that this just means:  IP is the transport => “DoIP”, but that feels really awkward to me, and why create something new…  so keep is simple and retain Do53, enough people use it already.     

3. And then, as per Geoff "get on with it”, because the other terms are all useful.


BR,

Normen Kowalewski