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

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 03 October 2011 17: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 57BD721F8C28; Mon, 3 Oct 2011 10:18:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1317662306; bh=GYoPTM3xcllRA4K/cxLNGTOyjnJ1fXFoCV6OB+qJCwk=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=mTqLyPQHQekhfFgzxtiPES2UMcSOSBGtY5YdQP4kORfhIk1IhROmxHx3NEAxPRkQm gB08K4pwmEIHpwJKmS6oeyjzhZ5VOEjz3p1S+9NPPU+7q+MpzvUeazlZZLiT/eDtoC 7m+Ua9h4AN94obqJAkB70j05p7bMpY+l3pzRw1hM=
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 3BE4D21F8C22 for <dnsext@ietfa.amsl.com>; Mon, 3 Oct 2011 10:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level:
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, 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 4JtwKGJwhnGB for <dnsext@ietfa.amsl.com>; Mon, 3 Oct 2011 10:18:24 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5A721F8B56 for <dnsext@ietf.org>; Mon, 3 Oct 2011 10:18:16 -0700 (PDT)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p93HLIPs004215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsext@ietf.org>; Mon, 3 Oct 2011 10:21:19 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1244.3)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <201110031713.20103.vixie@isc.org>
Date: Mon, 3 Oct 2011 10:21:19 -0700
Message-Id: <54E677EE-0720-4220-9FB8-17EDE978E904@vpnc.org>
References: <CACU5sDnBx5AijEgFXKNPjtcVdtBnBJamsn-f_ye0Jm3TQq0mvw@mail.gmail.com> <201110010458.26859.vixie@isc.org> <8F26AB69-C5BD-47BD-B3F4-6D840E419A23@verisign.com> <201110031713.20103.vixie@isc.org>
To: DNSEXT Working Group <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
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 Oct 3, 2011, at 10:13 AM, Paul Vixie wrote:

> On Monday, October 03, 2011 15:54:24 Wessels, Duane wrote:
>> On Sep 30, 2011, at 9:58 PM, Paul Vixie wrote:
>>> my observation is, we should not be using GET at all, nor should we be
>>> encoding the query into the URI.  We should use POST and our request body
>> 
>> I have a slight preference for GET over POST.  I find GET simpler to
>> implement (maybe code size isn't a concern) and probably more likely
>> to get through.  OTOH I also like that POST has the content-length
>> header.
> 
> what's your view of the need to someday express UPDATE, and to include future 
> extensions to QUERY (like more stuff in the additional section)?  if those 
> seem like worthwhile goals, then we really need to put the request into the 
> body rather than into the URI or into the http headers.  that calls for POST.

+1. The slight increase in programming difficulty of using POST vs. GET buys you a huge amount of flexibility in queries. It's not just about cache-prevention.

--Paul Hoffman

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