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

joel jaeggli <joelja@bogus.com> Mon, 29 February 2016 23:32 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA1D1A007E for <dnsop@ietfa.amsl.com>; Mon, 29 Feb 2016 15:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level:
X-Spam-Status: No, score=-1.306 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_52=0.6, RP_MATCHES_RCVD=-0.006] autolearn=no
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 B-9gNGjOYtjI for <dnsop@ietfa.amsl.com>; Mon, 29 Feb 2016 15:32:05 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 60AEC1A004E for <dnsop@ietf.org>; Mon, 29 Feb 2016 15:32:05 -0800 (PST)
Received: from mb-2.local ([8.18.217.194]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u1TNW2iU038646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 29 Feb 2016 23:32:02 GMT (envelope-from joelja@bogus.com)
To: Warren Kumari <warren@kumari.net>, Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
References: <3713017b-cbe6-f4fc-c045-074e0f684952@gmail.com> <CAHw9_iK9gJbC=LrAyOMbz_QtKzgaLs1ENri6K9KZAoj7aZM0qA@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <58074a8f-10df-f22d-0398-d415a2611d1d@bogus.com>
Date: Mon, 29 Feb 2016 15:32:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAHw9_iK9gJbC=LrAyOMbz_QtKzgaLs1ENri6K9KZAoj7aZM0qA@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="cJjDC2rbjtExeihWP5aV3vmo2jTxCaLng"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/prrFFSRGLXcKBQsIlsp-Hr45Sys>
Subject: Re: [DNSOP] Call for Adoption: draft-crocker-dns-attrleaf
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 29 Feb 2016 23:32:06 -0000

On 2/29/16 3:12 PM, Warren Kumari wrote:
> On Mon, Feb 29, 2016 at 10:40 AM Tim Wicinski <tjw.ietf@gmail.com
> <mailto:tjw.ietf@gmail.com>> wrote:
> 
>     There was some good discussion around this draft when it first appeared,
>     and the initial idea by the author was to run this through the Apps area
>     working group.  The chairs feel it make more sense to run this through
>     DNSOP and we urged the author to allow us the chance to give the working
>     group a try before giving up.
> 
>     *Note: This draft will create an IANA registry for "underscored names".
>     Now 10 years ago, even I would of blanched at such a thought.  But there
>     seems to have come a time where it makes sense to document the
>     morass of these labels and offers some guidance.  The discussion seemed
>     to bear this out.
> 

  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?

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

thanks
joel

> 
> Yeah. Support. 
> 
> I hold it true, whate'er befall;
> I feel it when I sorrow most;
> 'Tis better to have documented this
> Than never to know at all.
>  (apologies to L. AT)
> 
>  
> 
> 
>     This starts a Call for Adoption for "DNS Scoped Data Through
>     '_Underscore' Attribute Leaves"
> 
>     The draft is available here:
>     https://datatracker.ietf.org/doc/draft-crocker-dns-attrleaf/
>     Please review this draft to see if you think it is suitable for adoption
>     by DNSOP, and comments to the list, clearly stating your view.
> 
>     Please also indicate if you are willing to contribute text, review, etc.
> 
> 
> Contribute, review.
> 
> W 
> 
> 
>     This call for adoption ends 14 March 2016.
> 
>     Thanks,
>     tim wicinski
>     DNSOP co-chair
> 
>     _______________________________________________
>     DNSOP mailing list
>     DNSOP@ietf.org <mailto:DNSOP@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dnsop
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>