Re: [dnsext] Draft of an RRTYPE extension language

George Michaelson <ggm+ietf@apnic.net> Fri, 19 August 2011 05:30 UTC

Return-Path: <ggm+ietf@apnic.net>
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 D4B5711E8090 for <dnsext@ietfa.amsl.com>; Thu, 18 Aug 2011 22:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.733
X-Spam-Level:
X-Spam-Status: No, score=-101.733 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, RELAY_IS_203=0.994, 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 5aKL5UiCw+G1 for <dnsext@ietfa.amsl.com>; Thu, 18 Aug 2011 22:30:04 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 31A5B11E8082 for <dnsext@ietf.org>; Thu, 18 Aug 2011 22:30:04 -0700 (PDT)
Received: from dynamic161.apnic.net (dynamic161.apnic.net [203.119.42.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id A9FC0B675C; Fri, 19 Aug 2011 01:30:59 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="us-ascii"
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <alpine.BSF.2.00.1108190115420.54143@joyce.lan>
Date: Fri, 19 Aug 2011 15:30:59 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <19EAC368-BB0B-4171-9747-1BBD7C7C86F8@apnic.net>
References: <20110819050440.21024.qmail@joyce.lan> <B31D5A73-D2A0-4B60-BE51-4E2F30524A23@apnic.net> <alpine.BSF.2.00.1108190115420.54143@joyce.lan>
To: "John R. Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: dnsext@ietf.org
Subject: Re: [dnsext] Draft of an RRTYPE extension language
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>
X-List-Received-Date: Fri, 19 Aug 2011 05:30:04 -0000

On 19/08/2011, at 3:26 PM, John R. Levine wrote:

>> I wonder if its going to be sufficiently extensible for forseeable requirements. SRV for instance encodes structures like regex() which is 'powerful' (ie complicated)
> 
> SRV is three integers and a domain name.  Do you mean NAPTR?  It includes a regex, but the regex isn't interpreted within the DNS, only by clients, so as far as the DNS is concerned, it's just a string.
> 
> NAPTR:35 I2 I2 S S S N[A]
> 

Yes I meant NAPTR.

And, as you say...

> I should probably emphasize that this isn't supposed to be the FUSRP*. Some RRs require that the DNS server do something new, so if for example we added a BNAME record, it'd be easy enough to describe the syntax, but that wouldn't tell the DNS server about all the new synthesis rules.

its descriptive only, in a structural Octet-level-encoding sense. 

> 
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
> Please consider the environment before reading this e-mail. http://jl.ly
> 
> * - Final Ultimate Solution to the RRTYPE Problem

I really hate use of the words Final and Solution in one sentence. we've both just aquired a huge amount of Baysian for Godwin filters.

-G