Re: [dnsext] I-D Action: draft-ietf-dnsext-rfc6195bis-00.txt

Samuel Weiler <weiler@watson.org> Wed, 28 March 2012 00:12 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFAF021F852D; Tue, 27 Mar 2012 17:12:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1332893540; bh=RVpj04kqXpTgWZfVjR+grlZQ0juf4gGwqaClHG64IzU=; h=Date:From:To:In-Reply-To:Message-ID:References:MIME-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender; b=mCZ7HHON/ufNsw7kV6A+BSMdo4fhTWA1zQnLHfm+mblF4A2zV/J+07QXsz/WiZqYv s/dxDehXLsm8sObsMRhtqX7KdFJRMzncrtzzV/BCObH9yDYSXzw7DNkgmm1YRU3ITJ 64U5uKBaMLMWLQkg384CwnfHTFNhI+yTk5aVeDWs=
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 D202921F8526 for <dnsext@ietfa.amsl.com>; Tue, 27 Mar 2012 17:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599]
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 IfRUgVGR5R5k for <dnsext@ietfa.amsl.com>; Tue, 27 Mar 2012 17:12:18 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id BCD0D21F8525 for <dnsext@ietf.org>; Tue, 27 Mar 2012 17:12:18 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id q2S0CHqk051825 for <dnsext@ietf.org>; Tue, 27 Mar 2012 20:12:17 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id q2S0CHmk051819 for <dnsext@ietf.org>; Tue, 27 Mar 2012 20:12:17 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Tue, 27 Mar 2012 20:12:17 -0400
From: Samuel Weiler <weiler@watson.org>
To: dnsext@ietf.org
In-Reply-To: <20120327084731.30282.35216.idtracker@ietfa.amsl.com>
Message-ID: <alpine.BSF.2.00.1203272004400.25094@fledge.watson.org>
References: <20120327084731.30282.35216.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Tue, 27 Mar 2012 20:12:17 -0400 (EDT)
Subject: Re: [dnsext] I-D Action: draft-ietf-dnsext-rfc6195bis-00.txt
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

As I said at the microphone in Paris, I would strongly prefer to see 
typecode templates posted publicly in all cases.  I see no need to 
shorten the review period beyond the current three weeks.

Furthermore, as I pointed out on this list on 7 October, IANA seems to 
not be maintaining the archive of templates as requested in both 
RFC5395 and RFC6195.  If we're are going to keep using this template 
system to allocate typecodes, we need that archive.  Absent a 
commitment from IANA to maintain that archive, preferably backed up 
with evidence that they have populated that archive with the old 
templates, I would prefer to see us back out the RFC5395 changes to 
the typecode allocation process and revert to the RFC2929 rules.

-- Sam
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext