Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt

"Paul Hoffman" <> Wed, 30 August 2017 13:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4D0BD133298 for <>; Wed, 30 Aug 2017 06:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RmYgZLHuAo3M for <>; Wed, 30 Aug 2017 06:32:52 -0700 (PDT)
Received: from (Opus1.Proper.COM []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E1B8E133296 for <>; Wed, 30 Aug 2017 06:32:51 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.15.2/8.14.9) with ESMTPSA id v7UDVmoZ014356 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <>; Wed, 30 Aug 2017 06:31:49 -0700 (MST) (envelope-from
X-Authentication-Warning: Host [] claimed to be []
From: Paul Hoffman <>
Date: Wed, 30 Aug 2017 06:32:53 -0700
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <>
Subject: Re: [DNSOP] Definition of QNAME (Was: I-D Action: draft-ietf-dnsop-terminology-bis-06.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 30 Aug 2017 13:32:54 -0000

On 29 Aug 2017, at 20:08, Andrew Sullivan wrote:

> Speaking as one of the presumed editors of post-7719 -- one who is,
> so-presumed, supposed to sort this problem out -- I hope it's ok to
> state _very strongly_ that I appreciate the extensive discussion of
> this issue.  I think this is very much one of the kinds of knotty
> terminological problems that has created enormous difficulty for
> people approaching the DNS for the first time.  Not only are terms
> hard to understand; but when you come across them, they seem to be
> slippery.
> At the same time, and taking off my editor hat for the moment, I am
> quite uncomfortable having a terminology document (which is what this
> thread is about) make the term not-slippery.  It _is_ slippery in the
> reference documents.  I don't think it helps us to try to settle those
> disputes.  I think 7719-bis can do two things:
>     1.  Document, as clearly as possible, the nature of the ambiguity.
>     This thread has helped, but I bet (I haven't checked with my
>     co-editors) that a ¶ well-worked-out on the list (not necessarily
>     the WG please note) would be welcome.
>     2.  Define, as clearly as possible and using new terms, the
>     distinctions in question and provide names for them.  These could
>     be, of course, names not previously known.
> I emphasise again that clarity of definitions is, at least for me, 
> quite important, so ambiguous examples are super valuable.  Thanks!

As another co-editor of 7719-bis, I strongly concur with Andrew. I have 
been flagging all the messages in this thread and waiting for it to 
peter out before suggesting wording. If someone who is invested in this 
thread can propose text for 1 and 2, that would help because then others 
who are invested in the thread can comment and we can get good wording 
before the editors try.

--Paul Hoffman