Re: [DNSOP] dnsxml - A standard XML representation of DNS data

Tim Wicinski <tim.wicinski@teamaol.com> Wed, 31 July 2013 06:05 UTC

Return-Path: <tim.wicinski@teamaol.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7470221F9F70 for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 23:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 EQ387+mTN1BF for <dnsop@ietfa.amsl.com>; Tue, 30 Jul 2013 23:05:47 -0700 (PDT)
Received: from omr-m07.mx.aol.com (omr-m07.mx.aol.com [64.12.143.81]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5EA21F9F6C for <dnsop@ietf.org>; Tue, 30 Jul 2013 23:05:47 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-m07.mx.aol.com (Outbound Mail Relay) with ESMTP id 7EFD370000097; Wed, 31 Jul 2013 02:05:44 -0400 (EDT)
Received: from tjw.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Wed, 31 Jul 2013 02:05:44 -0400
Message-ID: <51F8A937.5060007@teamaol.com>
Date: Wed, 31 Jul 2013 08:05:43 +0200
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Jay Daley <jay@nzrs.net.nz>, dnsop WG <dnsop@ietf.org>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
In-Reply-To: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.8.193]
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2013 06:05:51 -0000

Jay

Couple of things here:  It's a little last minute to throw it onto the 
agenda, and we'll need to have some of that discussion. Second, there is 
another document floating out there on rDNS 
http://tools.ietf.org/html/draft-manderson-rdns-xml-01

I would suspect that we'll need to break down how each one document 
affects the other (are the complimentary or overlapping, etc.).  Then 
there is the entire "if XML is the answer in 2013, what really is the 
question?" question.

If you're in town, I've been hunkered down in the Terminal Room 
hammering on several different things.

tim

On 7/31/13 2:05 AM, Jay Daley wrote:
> Hi All
>
> The title says it all.  I would be interested in your views and any support that might exist for this.  Apologies but I have yet to see how this fits with Stephane's work on a JSON representation of DNS as this has taken quite a few years to write.
>
> cheers
> Jay
>
>
> A new version of I-D, draft-daley-dnsxml-00.txt
> has been successfully submitted by Jay Daley and posted to the
> IETF repository.
>
> Filename:	 draft-daley-dnsxml
> Revision:	 00
> Title:		 dnsxml - A standard XML representation of DNS data
> Creation date:	 2013-07-31
> Group:		 Individual Submission
> Number of pages: 54
> URL:             http://www.ietf.org/internet-drafts/draft-daley-dnsxml-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-daley-dnsxml
> Htmlized:        http://tools.ietf.org/html/draft-daley-dnsxml-00
>
>
> Abstract:
>    This memo describes a syntax for encoding DNS Resource Records in
>    XML, and a schema to define that syntax written in XML Schema.  It
>    can be used to represent all DNS RDATA.  This can be used by diverse
>    applications as a common format.
>
>    DNS Resource Records are represented as XML elements with the name of
>    the element taken from the mnemonic used to represent the DNS
>    Resource Record in presentation format.  The RDATA is represented as
>    XML attributes or content of the element.  The attribute names are
>    taken from the RDATA field names specified in the normative RFC.
>