[dnsext] rfc6195bis registration template clarification

Alfred Hönes <ah@TR-Sys.de> Mon, 23 April 2012 18:39 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 C5A4221F85CF; Mon, 23 Apr 2012 11:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1335206344; bh=/Mg9guvJdtNTyjxo4/uuzzAyvOwnu4O2jMH5M4r/LEs=; h=From:Message-Id:To:Date:Mime-Version:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=J+DOA636ITUJfYNFMZm5T879zzU13G8jS+BLQDd0zXyLofU9hUhXMFO7FKnQZTb/O Fpb+lclEYVK6EWzhdrz4JAv4OuPIZ3hjwkbe6UEXozjdHLnoka1mKH0JuKFepDCSSr 439UB1US0jedb5iCN3RNRMbmLaoURoJ2V59uxn/Q=
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 05B4B21F85CF for <dnsext@ietfa.amsl.com>; Mon, 23 Apr 2012 11:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.008
X-Spam-Level:
X-Spam-Status: No, score=-97.008 tagged_above=-999 required=5 tests=[AWL=-0.859, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, 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 TS+R402Z-RSF for <dnsext@ietfa.amsl.com>; Mon, 23 Apr 2012 11:39:03 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by ietfa.amsl.com (Postfix) with ESMTP id BBA5421F85C0 for <dnsext@ietf.org>; Mon, 23 Apr 2012 11:39:02 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA126956265; Mon, 23 Apr 2012 20:37:45 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id UAA01660; Mon, 23 Apr 2012 20:37:43 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201204231837.UAA01660@TR-Sys.de>
To: d3e3e3@gmail.com
Date: Mon, 23 Apr 2012 20:37:43 +0200
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Cc: dnsext@ietf.org
Subject: [dnsext] rfc6195bis registration template clarification
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

I tried to figure out whether the rfc1995bis-ixfr draft needs
to undergo the RRtype Expert Review per RFC 6195[bis].

It looks like that review only pertains to Data and Meta-RRtypes,
(and the draft -- targeting Standards Track -- needs IETF review),
but the registration policy table for RRtypes (entry for range
128-255) could be misunderstood to indicate otherwise.

When looking at the registration template in RFC 6195[bis],
I missed a structured opportunity for the applicant to indicate
whether the application is for a Data RR or Meta-RR, which would
be significant for IANA to select a proper numerical range in the
assignment process.

So I suggest to amend clause B. of the template in Appendix A of
the rfc6195bis I-D as follows:

OLD:

|  B. Submission Type:
|     [ ] New RRTYPE
|     [ ] Modification to existing RRTYPE

NEW:

|  B. Submission Type:
|     [ ] New RRTYPE
|     [ ] Modification to existing RRTYPE
|
|     Kind of RRTYPE:
|     [ ] Data RR
|     [ ] Meta-RR

As an alternative, a new numbered item might be inserted; that
would cause the need to renumber the exicsting items, which perhaps
is less desirable for backwards compatibility with RFC 6195.
A third alternative would be using item numbers "B.1." and "B.2.".

Best regards,
 Alfred.

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