IETF Logo Mail Archive

Re: [DNSOP] Call for Adoption: draft-song-dns-wireformat-http

"John R Levine" <johnl@taugh.com> Tue, 12 July 2016 03:32 UTC

Return-Path: <johnl@taugh.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 2AEBE12D0D9 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 20:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=CtcXiJl0; dkim=pass (1536-bit key) header.d=taugh.com header.b=RqdyyuDi
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8G93QBXzn-NB for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 20:32:53 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE8C812B075 for <dnsop@ietf.org>; Mon, 11 Jul 2016 20:32:52 -0700 (PDT)
Received: (qmail 52843 invoked from network); 12 Jul 2016 03:32:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=ce6a.578464e3.k1607; bh=miM5+HRy1syuTWJq29/gY4jmocF81xtDDc2KSGB3SgM=; b=CtcXiJl0q+3nrncjF9EZ61lwMv7a4fP3a8nF4cCQ+UuR2NBjMUkWQUboBI8onAO+DTWGZtCWy/gSCU+hCsmqobp8ItncSDfkCbOfIxjvBqnLPJasYuzQN5rZuLgeewGzX5DnvumuVnTrOcurxiEiFv9OdcS8Ieig+S+BQh0C4VyjbttiUNg9s6Yz9dgDQepe+3Ptje1JXh4RpHZ6OlXG4QgGHaDHk3B2M2lsLIcvCUf0qQVeM7vntoB2PAlzgt0r
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=ce6a.578464e3.k1607; bh=miM5+HRy1syuTWJq29/gY4jmocF81xtDDc2KSGB3SgM=; b=RqdyyuDivwVGLH4zOQjiRIAkeDcfq5z6hMiom9SFaSv7IgZb0N9hSgcdcp9t5OnOcnD5Dgp7ggWVMCrJVWD0Qqp6QDuTrxiS3/8Dm/C+HolKpckLiJowtsQB2LZGgY8lrK4eKsBZmfaVdCPlaRs1hPT9tVti2hnMm2x6eF2Aiw9GNiZtqPOyypO0OJb9hhd2TTOIB0pcxxGgK0B/g+02KKeevbmU2Gl5oo6wXQR5/Xn1LOhi0SgiGT98jhtsCxI3
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 12 Jul 2016 03:32:51 -0000
Date: Mon, 11 Jul 2016 23:32:51 -0400
Message-ID: <alpine.OSX.2.11.1607112330450.48246@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Marek Vavruša <mvavrusa@cloudflare.com>
In-Reply-To: <CAC=TB124b7G0w48LY4zP6TOqE+xZ3n1Fp4_KMaUTB_ZtCtrzCw@mail.gmail.com>
References: <em4745d403-8957-4994-9819-47cc8d9e1364@bodybag> <20160712030624.29734.qmail@ary.lan> <CAC=TB124b7G0w48LY4zP6TOqE+xZ3n1Fp4_KMaUTB_ZtCtrzCw@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SJNzEL30R9r16Tfb1N9hMKTynlI>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for Adoption: draft-song-dns-wireformat-http
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 12 Jul 2016 03:32:54 -0000

>> Don't you get this automatically if it's treated as a TCP DNS
>> connection?  You stuff a bunch of requests down the pipe, and you get
>> back a bunch of responses.
>> See RFC 7766.

> You get queueing for free, but not pipelining and out-of-order
> responses, that has to be defined.

RFC 7766 says you should get pipelining and out-of-order responses on TCP 
DNS.  Take a look.

Even if the underlying DNS server that the proxy is using can't do it, any 
newly written proxy should provide TCP DNS the way 7766 says it should.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.30.2 | Report a Bug | By Email | System Status