IETF Logo Mail Archive

Re: [dnsext] draft-mohan-dns-query-xml-00.txt

Jakob Schlyter <jakob@kirei.se> Thu, 29 September 2011 21:18 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 1A19D21F8ED1; Thu, 29 Sep 2011 14:18:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1317331130; bh=H91TSx8KgusjFOJzdo8LR21UVHEJDWlUZsCXyMGAzho=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=jMTeK09LkFfPoGt2oiSb+JFWiGNFGPjGs+w5YQ/6rLiCvgwRKT7GAQHDbivQqOry7 or0VqlmefbRZq5CHpqwH27E05/MA8PPhVdlrsjRZ+Q4Xzjax4cIDchYyhejCBFuGOd bWjWxOFIFimgCcBLZet2r8tf822UUQmYM+JF/r60=
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 5CC3B21F8EC5 for <dnsext@ietfa.amsl.com>; Thu, 29 Sep 2011 14:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level:
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
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 gCVbXOyJ7V1Q for <dnsext@ietfa.amsl.com>; Thu, 29 Sep 2011 14:18:47 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id BD85621F8EB1 for <dnsext@ietf.org>; Thu, 29 Sep 2011 14:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=VeXw0/9lXBrBw0CvlK6qWwC0RmwDkSYv0YNgG6HPwr8=; b=nKQWyudRIWdffPUWH48p3vi9cuFV4o1MuB9bOvOY/Qpxc/rPvLfVJ/xRGixi7LE3EyKGcBnMoMKX3 oJJoKjXpKjKj9iYlbhoOgb2Xw45AqDZTF8g1nLnaN3tNmc6S6EaA3uCZTbAEkkQWDMsMuBY0xKiirK cEN/+qNbw1Tz/h5c=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Thu, 29 Sep 2011 23:21:35 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1244.3)
From: Jakob Schlyter <jakob@kirei.se>
In-Reply-To: <CACU5sDnBx5AijEgFXKNPjtcVdtBnBJamsn-f_ye0Jm3TQq0mvw@mail.gmail.com>
Date: Thu, 29 Sep 2011 23:21:34 +0200
Message-Id: <0394FB3B-6C2B-4D47-B1FA-AA54B7EB1053@kirei.se>
References: <CACU5sDnBx5AijEgFXKNPjtcVdtBnBJamsn-f_ye0Jm3TQq0mvw@mail.gmail.com>
To: Mohan Parthasarathy <suruti94@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Paul Vixie <vixie@isc.org>, dnsext@ietf.org
Subject: Re: [dnsext] draft-mohan-dns-query-xml-00.txt
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

On 28 sep 2011, at 20:24, Mohan Parthasarathy wrote:

> DNSSEC validation is stub resolver is dependent on DNSSEC-aware CPEs,
> recursive servers etc. Here is a draft that we submitted yesterday to
> address this problem.

First, let me say I think this an interesting proposal and I'm looking following this work.

I would prefer a RESTful API where the response data format is dependent on the HTTP accept headers. Using such an API, one could receive various formats, e.g., XML, JSON or plain old DNS wire format. A DNS client in Javascript would probably like JSON, a libresolv-like DNS library would like wire format and someone else (although I fail to see who) might prefer XML.

Regarding the XML format (if one is used), I agree with Ted Hardie on the namespace issue, and like to add a request for some XML schema definition (xsd, relax ng, relax ng compact, ...).

Also, I second the request for a DNSSEC chain mode.

	jakob

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

v2.8.7 | Report a Bug | By Email