IETF Logo Mail Archive

Re: [DNSOP] attrleaf

Dave Crocker <dhc@dcrocker.net> Tue, 28 March 2017 20:39 UTC

Return-Path: <dhc@dcrocker.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 B5713129629 for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 13:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.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 RkWmeZRvyd6g for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 13:39:29 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 5439D129A0A for <dnsop@ietf.org>; Tue, 28 Mar 2017 13:39:28 -0700 (PDT)
Received: from [31.133.139.104] (dhcp-8968.meeting.ietf.org [31.133.139.104] (may be forged)) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2SKfVPv002664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 13:41:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490733692; bh=T6MBJDqX6YlvN0xJD6PCvgM3js59tYrWeKCSNOXJllI=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=qopx59eAFwUk1QTyAlLztM5ru+LnBW6MQkzVnthDFsscFEx0y1PxGPH781aX5Rzdm X0lcSKpWlf8AajyzgMIrZVqPweDcgAc9iZsh1Yv+PbeOLYdAGyykgDEPqSCOjyHLR+ BX9y61JL4cjr0tZXaKIMtbMSO2aHTYhvP/970o4Y=
To: Paul Vixie <paul@redbarn.org>, John R Levine <johnl@taugh.com>
References: <20170328183740.2502.qmail@ary.lan> <58DAB425.8060100@redbarn.org> <alpine.OSX.2.20.1703281422420.4385@dhcp-80f1.meeting.ietf.org> <58DABB6F.1060208@redbarn.org>
Cc: dnsop@ietf.org
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <bfd27623-2d7f-d388-de57-f7ff4efdd802@dcrocker.net>
Date: Tue, 28 Mar 2017 15:39:15 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <58DABB6F.1060208@redbarn.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/2uD2YCXiQgxctzbIh3USIbTedww>
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 20:39:31 -0000

On 3/28/2017 2:37 PM, Paul Vixie wrote:
> if someone wants a new _ name entered into a registry, and if they plan
> to use it in a way that creates a sub-hierarchy, they should be advised
> not to follow SRV's example, and in my opinion, the example that ought
> to be set for them would be what SRV (and DS) ought to have done, as
> described up-thread.


If there were an Information RFC providing such guidance, I could 
imagine a helpful reference to it being provided in a document like 
attrleaf...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.30.2 | Report a Bug | By Email | System Status