[dnsext] [IANA #434639] Re: CAA RRTYPE review - Comments period end Mar 11th

"Amanda Baber via RT" <iana-questions@iana.org> Thu, 10 March 2011 20:09 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C4173A680F for <dnsext@core3.amsl.com>; Thu, 10 Mar 2011 12:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level:
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDxhRfQ6ojvk for <dnsext@core3.amsl.com>; Thu, 10 Mar 2011 12:09:33 -0800 (PST)
Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by core3.amsl.com (Postfix) with ESMTP id 14AD53A67FF for <dnsext@ietf.org>; Thu, 10 Mar 2011 12:09:32 -0800 (PST)
Received: from request1.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id p2AKAUpv007599; Thu, 10 Mar 2011 12:10:50 -0800
Received: from request1.lax.icann.org (localhost.localdomain [127.0.0.1]) by request1.lax.icann.org (8.13.8/8.13.8) with ESMTP id p2AKAUQ9007778; Thu, 10 Mar 2011 20:10:30 GMT
Received: (from apache@localhost) by request1.lax.icann.org (8.13.8/8.13.8/Submit) id p2AKAUiX007775; Thu, 10 Mar 2011 20:10:30 GMT
From: "Amanda Baber via RT" <iana-questions@iana.org>
In-Reply-To: <alpine.BSF.2.00.1103100742001.60284@fledge.watson.org>
References: <RT-Ticket-434639@icann.org> <20110218213453.GB96163@registro.br> <alpine.BSF.2.00.1103100742001.60284@fledge.watson.org>
Message-ID: <rt-3.8.HEAD-7525-1299787830-693.434639-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #434639
Managed-by: RT 3.8.HEAD (http://www.bestpractical.com/rt/)
RT-Originator: amanda.baber@icann.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Thu, 10 Mar 2011 20:10:30 +0000
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Thu, 10 Mar 2011 12:10:50 -0800 (PST)
X-Mailman-Approved-At: Thu, 10 Mar 2011 12:21:42 -0800
Cc: dnsext@ietf.org
Subject: [dnsext] [IANA #434639] Re: CAA RRTYPE review - Comments period end Mar 11th
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: iana-questions@iana.org
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 Mar 2011 20:09:34 -0000

Hi,

> Is it really appropriate to allow a template to create IANA 
> registries?  It does seem odd to me that a template can create an IANA 
> registry when the i-d it cites can't itself create a registry until 
> published as an RFC.  Perhaps IANA should comment on that.

Requests to create registries should be published in an RFC. 

thanks,

Amanda Baber
IANA