IETF Logo Mail Archive

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

Mohan Parthasarathy <suruti94@gmail.com> Wed, 28 September 2011 23:54 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 362F411E8157; Wed, 28 Sep 2011 16:54:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1317254092; bh=rnGaW+M7ca0kqLfe4qV6usRsIuHp/8p4k6viCmIrutA=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:From:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=UtbPHM7a1lJfI1ZQKIF9kDGhCgKc+9y0ZOs5BHKZFSEaZM/3EZGDAUl5oZgh4mowk 9WA5ZzrpPL43ifQ1I4c0wf8kbt5vw3wrfMODUc+Jegvb3cTkDHuMv7krBTN01QL3LL w8Zp270erk/w9gEvpi2TW5i3f8GI/3msPMFLDELM=
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 BDF2D11E8157 for <dnsext@ietfa.amsl.com>; Wed, 28 Sep 2011 16:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 FxMfx4BTg0yp for <dnsext@ietfa.amsl.com>; Wed, 28 Sep 2011 16:54:49 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6313211E80DA for <dnsext@ietf.org>; Wed, 28 Sep 2011 16:54:49 -0700 (PDT)
Received: by iaby26 with SMTP id y26so58792iab.31 for <dnsext@ietf.org>; Wed, 28 Sep 2011 16:57:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eWmob5Wd7xkB4tvcUxRxeBnJ+K22BqGvwj7QOg+Ncq0=; b=UoMRhF/oQhGjNTIw99beEsybLCGGOBu4bre5ReNixgeFuqO9CktzJcvCN6i/OpvT6+ mFMcdwdRQ14Je7jiHgpT1AgzHtt3vbFZfgNmADO1uPyr5pcx5y675j5a3R7II1MPmqTo 7dtStZyBCA0t5P/yvnCgujEOviqBHVUFLebz8=
MIME-Version: 1.0
Received: by 10.68.209.37 with SMTP id mj5mr47100755pbc.123.1317254258744; Wed, 28 Sep 2011 16:57:38 -0700 (PDT)
Received: by 10.68.46.200 with HTTP; Wed, 28 Sep 2011 16:57:38 -0700 (PDT)
In-Reply-To: <CAMbvoaK4fYg8r9JigO9gGf66EUxF-oYC5Bk5TnWmy9=zmUs-KA@mail.gmail.com>
References: <CACU5sDnBx5AijEgFXKNPjtcVdtBnBJamsn-f_ye0Jm3TQq0mvw@mail.gmail.com> <CAMbvoaK4fYg8r9JigO9gGf66EUxF-oYC5Bk5TnWmy9=zmUs-KA@mail.gmail.com>
Date: Wed, 28 Sep 2011 16:57:38 -0700
Message-ID: <CACU5sDmdzt-hO4mqOvPw5PrTP3oWB3ADDh4JkpNoKdMrJ4wcFA@mail.gmail.com>
From: Mohan Parthasarathy <suruti94@gmail.com>
To: Wilmer van der Gaast <wilmer@google.com>
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 Wed, Sep 28, 2011 at 3:10 PM, Wilmer van der Gaast <wilmer@google.com> wrote:
> On 28 September 2011 11:24, Mohan Parthasarathy <suruti94@gmail.com> wrote:
>>
>> Please send your comments/feedback to the list.
>>
> Two things off the top of my head after quickly reading this:
>
> A) Is it necessary to hardcode the /dns_service path? IMHO it would be
> nice to allow the use of base URLs instead, in case for some reason
> /dns_service can't be used on a host. Also, this lets the user choose
> if s/he wants to talk to a DNS service with/without DNSSEC validation
> for example (or opt out from things like ISP DNS "monetisation" in a
> nicer way).
>

If we can avoid hardcoding that would be nice. I am not sure I
understand your proposal. Could you clarify ? The initial thought is
that it would be nice to access it in a standard way but I do see the
issues you noted above.


> B) Nit, but why not convert the booleans in responses from
> <xx>value</xx> into <xx/> if it's 1 and <xx/> being absent if it's 0?
>

Is this a standard approach ? Or it saves bytes ?

thanks,
mohan

>
>
> Cheers,
>
> --
> Wilmer van der Gaast, Traffic SRE/Google Public DNS team.
> Google Ireland.
>
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext

v2.8.7 | Report a Bug | By Email