Re: [DNSOP] New draft for consideration:

Joe Abley <> Mon, 25 March 2019 13:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 74C45120478 for <>; Mon, 25 Mar 2019 06:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id u4Vyjw-DTEDE for <>; Mon, 25 Mar 2019 06:37:33 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8716212038C for <>; Mon, 25 Mar 2019 06:37:32 -0700 (PDT)
Received: by with SMTP id m13so6014833lfb.6 for <>; Mon, 25 Mar 2019 06:37:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=SEhUuK0Yq+ttM4f381XMSQ08el92nvyqkIeeKBWgAss=; b=aab74axXcykx8TXKp7ZoRkZjLwE0fIqqRQVxg9WZVhQM4S1C8NV6ntR2zVYV03+uCy Z1qG1P21tRDjgVBEB9xy/AdGJKYzGxkCKEHv/wzBhkNO87ggNKhMjZxa9jOkhqId5E7n C9ybIVlUOgrhkqkXSi2ELKz7bbyhbflqj3jio=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=SEhUuK0Yq+ttM4f381XMSQ08el92nvyqkIeeKBWgAss=; b=sTqDN+GrWYOjmovfvcWZspRvRqthEcTEeNgNUnR5dtb4ETE7GT5/Ygz+so79yX4y0e hL0+vwgO0UE4I+nW8+7an2D+Y6M4xq/+yZhTvPsPGeaASrjwRcN1BI8WXjKWAHeFnSOt lWTx9Eofe7DrvmU3Vd1e7RcHNEhQpmqes5sISvCeLAekXH4M3ArKyQIWeBkHviJlEhl0 D/J9X1Q2KUupWVgXTPSe/aQCWSuvm7nATNnExS0D4oq6eN/kgkCDFLTcpz4qubErWFjN Bj0qeeQ5CfBr9Ax4BrVjZbWbeEu99b2WuOhYn0JkdBnpddlb5o3IUDtlsgNpizcYjMhi JFsQ==
X-Gm-Message-State: APjAAAXdwJ3YOVVyTDyy7jPrF5NQ4G2GmAQDay1Em4TfoGkk+CjwtAfs 8KO59x+eSQp5QE0KnplMXzK78WakoLJi1jqfFZBB2g==
X-Google-Smtp-Source: APXvYqzXK3L+Ic02Sa0HP8kn8MDCEot2HG7ZlipXRiHBJQRDdKBoOJxrl/3r/Qgj4KtUY1orAlFZK0bmiW9L6GaSDEM=
X-Received: by 2002:ac2:495c:: with SMTP id o28mr8325610lfi.16.1553521049386; Mon, 25 Mar 2019 06:37:29 -0700 (PDT)
Received: from unknown named unknown by with HTTPREST; Mon, 25 Mar 2019 06:37:27 -0700
From: Joe Abley <>
Mime-Version: 1.0 (1.0)
References: <>
In-Reply-To: <>
Date: Mon, 25 Mar 2019 06:37:27 -0700
Message-ID: <>
To: Paul Hoffman <>
Cc: dnsop <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [DNSOP] New draft for consideration:
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 25 Mar 2019 13:37:35 -0000

On Mar 24, 2019, at 07:42, Paul Hoffman <> wrote:

> Greetings again. As y'all have seen over the past few weeks, the discussion of where DNS resolution should happen and over what transports has caused some people to use conflicting terms. As a possible solution to the terminology problems, I am proposing a few abbreviations that people can use in these discussions.

I like the idea in general of trying to anticipate and avoid problems
before they happen. However, I wonder in this case whether a lexicon
is going to help.

The problems with the conversation today (I would say) are more
fundamental than terminology. It's long been my observation that
finding a name for something has the potential to suck all the air
from the room. The room we are in is perhaps stuffy enough already.