IETF Logo Mail Archive

Re: [DNSOP] Call for Adoption: draft-crocker-dns-attrleaf

Dave Crocker <dhc@dcrocker.net> Tue, 28 March 2017 20:54 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 6A6A1126E01 for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 13:54:20 -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 HWHN6UQB4aYs for <dnsop@ietfa.amsl.com>; Tue, 28 Mar 2017 13:54:19 -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 11D86126C2F for <dnsop@ietf.org>; Tue, 28 Mar 2017 13:54:19 -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 v2SKuLDr002881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Mar 2017 13:56:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490734582; bh=QpsTEgWYJ8yIrA2kEaCbxsIq2mzrkIPKLPWLis8d4iM=; h=Subject:To:References:From:Cc:Reply-To:Date:In-Reply-To:From; b=IJnyO6bsm1FoawdpZ9G6MCd0g3xB30htBx+f0wtiLT9RGr7DDoOMRUGC3mR2//Ekj 9UXphjIoZ3aZ68DMgvDCkMyXYVv5z6jTHNFvDzcWBLVy278ylEumhUr+ay9hX08icn Yav5YHJggn2fNjQjFLQk5JC5hPhfxExMEIO5zaKo=
To: joel jaeggli <joelja@bogus.com>
References: <3713017b-cbe6-f4fc-c045-074e0f684952@gmail.com> <CAHw9_iK9gJbC=LrAyOMbz_QtKzgaLs1ENri6K9KZAoj7aZM0qA@mail.gmail.com> <58074a8f-10df-f22d-0398-d415a2611d1d@bogus.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Cc: dnsop <dnsop@ietf.org>
Reply-To: dcrocker@bbiw.net
Message-ID: <5ea4c264-9f0a-5a6a-bfac-e6864063890a@dcrocker.net>
Date: Tue, 28 Mar 2017 15:54:05 -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: <58074a8f-10df-f22d-0398-d415a2611d1d@bogus.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3A6W9MzwccaAX7ULG8POBlKQk-o>
Subject: Re: [DNSOP] Call for Adoption: draft-crocker-dns-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:54:20 -0000

On 2/29/2016 5:32 PM, joel jaeggli wrote:
> On 2/29/16 3:12 PM, Warren Kumari wrote:
>   Per [RFC2434], IANA is requested to establish a DNS Underscore Name
>    Registry, for DNS node names that begin with the underscore character
>    (_) and have been specified in any published RFC, or are documented
>    by a specification published by another standards organization.  The
>    contents of each entry are defined in Section 4
>
> So the registry policy I read as specification required given the
> inclusion of 3rd party documents rather than RFC required.  Is that how
> you read it? Should those be subject to expert review?

That's the intent of the text:  Reliable access to a specification 
attached to the registration, but no requirement for much quality 
control on the spec...


> anyway 5226 obsoleted 2434 so I'd probably cite that.

ack. tnx.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email