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

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 02 April 2012 01:15 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 77A9C11E8085; Sun, 1 Apr 2012 18:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1333329358; bh=GSkPtPD7/IaSke8JS4CNLIE+m7VGHIepdXJlKT3j8MY=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=o5/pF8zTm1vwWrJ+xGxS1QPMNxM4UXmnHCLbddZmwQyW8cS7OVikvqyq/CEPWTaPU bK6u2srlV0MQ3XbTVfFi9kDDx16n04YALh/3mG3ve7WeSdG9sW7rX0kKVKFxE7mzVw rWhRfYSYNkajUPVHn5eQ+X/oVNCREy/tsGhwRdjE=
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 A9E9111E8085 for <dnsext@ietfa.amsl.com>; Sun, 1 Apr 2012 18:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level:
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 WugZxJYYRjmo for <dnsext@ietfa.amsl.com>; Sun, 1 Apr 2012 18:15:57 -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 30C9521F8705 for <dnsext@ietf.org>; Sun, 1 Apr 2012 18:15:57 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q321Fsfp041679 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 1 Apr 2012 18:15:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1257)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <alpine.BSF.2.00.1203272004400.25094@fledge.watson.org>
Date: Sun, 01 Apr 2012 18:15:54 -0700
Message-Id: <37562023-C8FE-4EE4-A752-2F646B495BA5@vpnc.org>
References: <20120327084731.30282.35216.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1203272004400.25094@fledge.watson.org>
To: Samuel Weiler <weiler@watson.org>
X-Mailer: Apple Mail (2.1257)
Cc: dnsext@ietf.org
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On Mar 27, 2012, at 5:12 PM, Samuel Weiler wrote:

> 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.


This is an issue for the IAB, who is in charge of the IETF's relationship with IANA. If IANA is not meeting a requirement of an RFC, they should be told to do so a bit more forcefully. We should not have to revert to a less descriptive registry.

--Paul Hoffman

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