Re: [DNSOP] attrleaf

"John R Levine" <johnl@taugh.com> Tue, 28 March 2017 19:25 UTC

Return-Path: <johnl@taugh.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 822EF1293E3 for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 12:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=TCw95F8R; dkim=pass (1536-bit key) header.d=taugh.com header.b=HJUo6ied
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 tMWIBP-P8PO1 for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 12:25:43 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44199129481 for <dnsop@ietf.org>; Tue, 28 Mar 2017 12:25:43 -0700 (PDT)
Received: (qmail 25218 invoked from network); 28 Mar 2017 19:25:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6280.58dab8b6.k1703; bh=2JEBwJzAd6gYTl0V6JvADjUW73z0se54iKd/5BB2V6o=; b=TCw95F8RcPGYLkG/bjLCl2zqqFTQUgS+JgwsLWZWNA+Xr+dQHcnRtnWMYHrQ0dqS4MkRqKuWA9mGYEwTlDNqP9ZTe7TBM+lYbzzJhss8ls4mpslyfk1mGk41ccGHSkUmRRRxgN/7wslswdRIWKe+wta8ThG8gFvr5sq266Xpjc3+7c3j04ywXzLjpv6lgc2fVw6QCMnqmrAgshScMYbsfk2kFMH6qeJCpEmJvYC8PRUtOzdvW9tQVGp2mY6PdvxK
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6280.58dab8b6.k1703; bh=2JEBwJzAd6gYTl0V6JvADjUW73z0se54iKd/5BB2V6o=; b=HJUo6iedhA6I0QrWsejBW7EsZ+Txcjt+x0Rc6COCXyQBn+kV+onFqNANlYKj+4leBQOzKqQRs/VdnfiN2Z9l1eKpV5UaTQkKDKiHBL7NYEweUf+SSw3kRv7tMZt3O/kpbpuMfyovcn/v9qZmc+pVfqIxadacb/TgUbBtS1tW0BrQ0VjqemfgmXfDX2wuAabOxl858sz/L/wcR/GHneBf5XOY06CTx6Hqh0FOZdocO7zUjVVAf/D+moDetgwlOtl+
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 28 Mar 2017 19:25:42 -0000
Date: 28 Mar 2017 14:25:40 -0500
Message-ID: <alpine.OSX.2.20.1703281422420.4385@dhcp-80f1.meeting.ietf.org>
From: "John R Levine" <johnl@taugh.com>
To: "Paul Vixie" <paul@redbarn.org>
Cc: dnsop@ietf.org
In-Reply-To: <58DAB425.8060100@redbarn.org>
References: <20170328183740.2502.qmail@ary.lan> <58DAB425.8060100@redbarn.org>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Wrg6hA8u_eI5aOwE6IcO-DvUHbk>
Subject: Re: [DNSOP] attrleaf
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: Tue, 28 Mar 2017 19:25:46 -0000

>> ...  It's not offering advice that
>> underscore names are wonderful, it's recognizing the ones that are in
>> use now.
>
> as you wrote above, it's also saying "how to add new names". i'd like
> our advice in this regard to be considered excellent.

It's only providing the mechanics to add a name to the registry, same as 
is in every other RFC that defines a registry.  It's not policy advice on 
using them in protocols.  If you want to write Underscore Prefixes 
Considered Harmful, that's fine, but it's a different document.

R's,
John