Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf

"John Levine" <johnl@taugh.com> Fri, 06 July 2018 16:35 UTC

Return-Path: <johnl@iecc.com>
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 3EDEB13107A for <dnsop@ietfa.amsl.com>; Fri, 6 Jul 2018 09:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=gcimvw6o; dkim=pass (1536-bit key) header.d=taugh.com header.b=Y2HUufah
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 4nUhQCkhLWW5 for <dnsop@ietfa.amsl.com>; Fri, 6 Jul 2018 09:35:33 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E5293131070 for <dnsop@ietf.org>; Fri, 6 Jul 2018 09:35:32 -0700 (PDT)
Received: (qmail 11075 invoked from network); 6 Jul 2018 16:35:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=2b38.5b3f9a54.k1807; bh=NyGmQObsn9DdNyt6xJ6wQBgnhhPnTpPMlwRuZl2Sd6c=; b=gcimvw6oUY2Mp15+Z3wO0JBhFZYdnIcGa6vpuv4J70E45CofgqwGg3HOPCCRsIIgzWRS2qtcpuB8eUiooNpgDC5WaxS0gGH09A7jjbfjTjCrJOTHEu+Fxi5jOhf29jCZbyOHSFYILYmy83IwZRIQ2luJSY1FsUQtBAqUJLG6DnT5c7i2o4xlX3EGugsNpJ4of8dpF3KSXizUPv42fF+3F6eL8OVZ0V6lPzJwpQCAvAIt7aTJByHlzAp3p3b3cJgm
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=2b38.5b3f9a54.k1807; bh=NyGmQObsn9DdNyt6xJ6wQBgnhhPnTpPMlwRuZl2Sd6c=; b=Y2HUufahGs9K+n73RhkILZUdQbGpXoE2vE54+CuFZ15xokCbO/8SimsX5k8vmtrU4hxR1EU04LBAhtXxOAST3kpw3HqRdr2LlE3oOxZF7b5fggCiyHZq/TwBUe5dWqbvaPII2dDIf7J5hfy0O9tutVOFa1Rp4rWB8rXB2FuV4K+Di5Bm3mfvKCHJ8dVMgLpwQZjnj/NWTTS/nBBWplReROT3fMvKnnIQjjT2im7Fz+ASbOXXzQ+PooTC/SymhIst
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 06 Jul 2018 16:35:31 -0000
Received: by ary.qy (Postfix, from userid 501) id 7D34528E7D43; Fri, 6 Jul 2018 12:35:30 -0400 (EDT)
Date: 6 Jul 2018 12:35:30 -0400
Message-Id: <20180706163531.7D34528E7D43@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <349edb95-48ff-41a2-4cda-1c9ed44f7c63@bbiw.net>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qZjzink1HSmaEmRYK9cLjDQ-z6k>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-attrleaf
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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, 06 Jul 2018 16:35:36 -0000

In article <349edb95-48ff-41a2-4cda-1c9ed44f7c63@bbiw.net> you write:
>> Editorial: I would prefer all occurrences of "right-most" to be
>> replaced by "most general", to emphasize that it is not the position
>> which matters, it is the closeness to the root.
>
>So let's start by making sure we're seeking the same goal:  reader 
>comprehension.  While I can imagine there is phrasing that is better 
>than right-most, to achieve that comprehension, I believe 'most general' 
>isn't it.  My impression has been that 'right-most' is the most common 
>phrasing people have used over the years.

I'm with Dave here.  The current language seems easy to understand,
right-most and top.

R's,
John

Translator's note: change this to "left most" when translated
to Arabic or Hebrew.