Re: [dnsext] draft-levine-dnsextlang-02 interop w/ rfc3597[bis]

Tony Finch <dot@dotat.at> Wed, 28 March 2012 16:51 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 8469A21E80DD; Wed, 28 Mar 2012 09:51:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1332953489; bh=EJvSMiR9TTZnQtM4d4xuIUbKaQnfYrdactZabVF18QY=; h=Date:From:To:In-Reply-To:Message-ID:References:MIME-Version:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=HF3/a4WtBxdGsJQ1CvebcJfGcFlc8BngwhQh7Kxo53CUUoH/VTHTwR4Y9nkH0BYXv BcfXBlAXJlnF1OJi5VxmpZ8XQzLB0rcYA60GMfacWld0GNd47H9N/uJa1mQLdoNOrx 9ndfjtBFfWKojW/Cz6eiVWkXY8O3PzEmsyt8/0fU=
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 8B64121E80DD for <dnsext@ietfa.amsl.com>; Wed, 28 Mar 2012 09:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.881
X-Spam-Level:
X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[AWL=-0.482, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
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 Xmf2eIP9eYUA for <dnsext@ietfa.amsl.com>; Wed, 28 Mar 2012 09:51:26 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 49EB521E8091 for <dnsext@ietf.org>; Wed, 28 Mar 2012 09:51:26 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:45330) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1SCw5i-0002N5-pf (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 28 Mar 2012 17:51:22 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1SCw5h-0005w3-Vp (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 28 Mar 2012 17:51:21 +0100
Date: Wed, 28 Mar 2012 17:51:21 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Alfred H?nes <ah@TR-Sys.de>
In-Reply-To: <201203272017.WAA07471@TR-Sys.de>
Message-ID: <alpine.LSU.2.00.1203281717481.24583@hermes-2.csi.cam.ac.uk>
References: <201203272017.WAA07471@TR-Sys.de>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Cc: standards@taugh.com, dnsext@ietf.org
Subject: Re: [dnsext] draft-levine-dnsextlang-02 interop w/ rfc3597[bis]
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

Alfred H?nes <ah@TR-Sys.de> wrote:
>
> But what happens if the implementation supporting Ext'lang and
> having been configured with the friendly format for a specific
> "Unknown RRtype" (as listed in RFC 3597) has operational needs
> to _export_ data to a non-upgraded recipient system, in a specific
> operational environment?

My immediate reaction was to say this is a matter for the configuration of
these systems, but then the question is where this configuration should
live and what form it should take.

I have been working on this proposal from the point of view of making
RR editors extensible, which brings up some related issues: whether RRs of
a particular type are human-editable or whether they should normally be
hidden. This mainly applies to DNSSEC records, so the question is whether
this should be hardcoded or supported by a generic mechanism. (There's a
similar question about name compression, for which John has specified a
generic mechanism but which can also be hardcoded according to the rules
in RFC 3597.) The generic mechanism would basically be per-RRtype
qualifiers (c.f. John's per-RDATA-field qualifiers) which could also be
used to say what format to use in master file exports.

Alternatively John's "AXFR or something similar" covers RFC 3597 generic
format master files - you can use the generic format for all records if
you want.

Another question this raises is whether the /etc/rrtypes file should be a
representation of the IANA RR type registry (like /etc/services and
/etc/protocols) or whether it is more system-specific. I have a
half-finished proposal for attaching descriptive text to RDATA fields for
user interfaces, which implies there will at least be per-language
versions, so perhaps it should be thought of as a per-package
configuration file rather than a fairly static part of the OS.

Any opinions on this vague rambling are welcome :-)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Viking, North Utsire: Northwesterly 5 to 7. Moderate or rough. Rain or
showers. Moderate or good, occasionally poor at first.
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext