Re: [dnsext] WGLC: RFC6195bis IANA guidance
Paul Hoffman <paul.hoffman@vpnc.org> Thu, 05 July 2012 14:55 UTC
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C1C221F86E4 for <dnsext@ietfa.amsl.com>; Thu, 5 Jul 2012 07:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level:
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aFFXPNQcF425 for <dnsext@ietfa.amsl.com>; Thu, 5 Jul 2012 07:55:43 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6C91321F8734 for <dnsext@ietf.org>; Thu, 5 Jul 2012 07:55:39 -0700 (PDT)
Received: from [10.20.30.102] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q65EtogD074592 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsext@ietf.org>; Thu, 5 Jul 2012 07:55:51 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1278)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FD62E4E.4020007@ogud.com>
Date: Thu, 05 Jul 2012 07:55:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B094C1EB-429F-4C92-A447-6B2066A91776@vpnc.org>
References: <4FD62E4E.4020007@ogud.com>
To: DNSEXT Working Group <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1278)
Subject: Re: [dnsext] WGLC: RFC6195bis IANA guidance
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 14:55:44 -0000
On Jun 11, 2012, at 10:43 AM, Olafur Gudmundsson wrote: > This message starts a 2 week WGLC for RFC6195bis ending at midnight UTZ June 28'th 2012. > http://tools.ietf.org/html/draft-ietf-dnsext-rfc6195bis-02 > > This document addresses known flaws in the RFC6195 (see appendix A). > > Please review the document and post a note that you have reviewed the document we need a minimum of 5 reviewers. I apologize for getting to this so late, but I also note that I might be just the fifth reviewer... The document is mostly fine. However, I have one major issue with it: it's not clear what IANA is supposed to do with it. There is a *lot* of text in this document that is repetition of the RFCs, as well as some important historical notes that are not currently in RFCs or in the IANA registry. When this document is finished, is IANA supposed to change each sub-registry to include the text from the relevant section of this RFC? If not, why is that text in this "IANA Considerations" document? I can see a few ways forward here: a) Explicitly tell IANA what additional material from this document should go in each sub-registry b) Tell IANA to put at the top of the registry something like "In order to understand this registry, you need to understand the underlying RFCs and the history of the registries. In order to do that, you should read BCP XXX" with a link to this document My preference is the latter, but people might want the former to make it harder for readers of the registry to miss the relevant stuff. There might be other ideas as well. Two other issues that should be clarified: - Can anyone subscribe to the dns-rrtype-applications@ietf.org mailing list to see the applications come in? It is *not* listed on the page at <http://www.ietf.org/list/nonwg.html>. - At the end of 2.2, what does "as modified by [RFC4020]" mean? Is is supposed to be "as described in [RFC4020]"? --Paul Hoffman
- [dnsext] WGLC: RFC6195bis IANA guidance Olafur Gudmundsson
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Michael Sheldon
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Alfred Hönes
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Dick Franks
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Olafur Gudmundsson
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Alfred Hönes
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Ray Bellis
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Mark Andrews
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Paul Hoffman
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Nicholas Weaver
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Paul Hoffman
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Dick Franks
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Andrew Sullivan
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Michael Sheldon
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Mark Andrews
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Paul Hoffman
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Chris Thompson
- Re: [dnsext] WGLC: RFC6195bis IANA guidance Donald Eastlake