Re: [dnsext] Advice sought on DNS file format for new RRs

Andrew Sullivan <ajs@shinkuro.com> Fri, 19 November 2010 12:40 UTC

Return-Path: <ajs@shinkuro.com>
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 EA9FA28C0E4 for <dnsext@core3.amsl.com>; Fri, 19 Nov 2010 04:40:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.645
X-Spam-Level:
X-Spam-Status: No, score=-102.645 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5ZKsvvjuPM7n for <dnsext@core3.amsl.com>; Fri, 19 Nov 2010 04:40:41 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 28C3228C0DF for <dnsext@ietf.org>; Fri, 19 Nov 2010 04:40:41 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 085D71ECB426 for <dnsext@ietf.org>; Fri, 19 Nov 2010 12:41:29 +0000 (UTC)
Date: Fri, 19 Nov 2010 07:41:28 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsext@ietf.org
Message-ID: <20101119124127.GB8050@shinkuro.com>
References: <AANLkTimBPLaFZQSbx8W7Dwy0r9SzHsrV-rA9yQU83sZw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTimBPLaFZQSbx8W7Dwy0r9SzHsrV-rA9yQU83sZw@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [dnsext] Advice sought on DNS file format for new RRs
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Fri, 19 Nov 2010 12:40:42 -0000

On Thu, Nov 18, 2010 at 04:53:44PM -0500, Phillip Hallam-Baker wrote:
> Now I can convert this to EBNF as well as the next person. But I am trying
> to think round the question of maintaining DNS servers. I have a subfield
> encoding here with three different variations on the data type. Is this
> acceptable?

I'm trying to understand the motivation.  Why not use three different
RRTYPEs?

I haven't thought about it very hard, but my first reaction is that
this RRTYPE is not going to be eligible for assignment by expert
review.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.