IETF Logo Mail Archive

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

Marek Vavruša <mvavrusa@cloudflare.com> Tue, 12 July 2016 04:05 UTC

Return-Path: <mvavrusa@cloudflare.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 9C29012D0D3 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 21:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
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 XPtnISYBjtoG for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 21:05:58 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2240312B00B for <dnsop@ietf.org>; Mon, 11 Jul 2016 21:05:58 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id j17so3635073ywg.0 for <dnsop@ietf.org>; Mon, 11 Jul 2016 21:05:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AfY/UBe41rHC/oJMicPafoRifPmi4Z9RDCw53WwKNvw=; b=Ng05ysUFVTsRfEeyDfooINqfpxWNkOqPCpBgzjgfuXyATidq4yUsqkyzU9GJNlvMm/ um1Sh1kX+WkHqYvUFgKGf0Kmss21L2nNdDqTjseT9+9xG5wUlbryHSJ+QZJf6gLuZ6Mi DuFIWhibulF4nAnPhwcrDyihcSbRf4P1yMjkc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AfY/UBe41rHC/oJMicPafoRifPmi4Z9RDCw53WwKNvw=; b=BPGlB4tMDM/dHfP7ZyTVnvue4ZkHQBzJ7MhyyxEJ6Ha565RsN+bbBswaMtKj37UkI9 nm6eAvls7spCY+Vhnl72+1zDp8JEJwil/3KLEX/OFhaGbqhSnnHr8A4KvXVgnaBiNXJr UCPgAX10LI2VcHdWt3twbONZNAibQCvZuwvcZPtXGT7mzeZrGPa0SYTbWbnq8RIh6Blg UL6IsJhstQebJzAEFIRPm8wvpirfogITNaJKxpQGVs7v8FYCP2lqoz0cWUmKVowFXJy+ EvqIXUxcCTZkBe8LU7WM2Se016rWM2v7JVpyz/AzrFQFDnWgGbVL/AyYMhx6gRTfe/xv TwCQ==
X-Gm-Message-State: ALyK8tI7vsN7P/gX7c5VmqMVmkMaI+bt8zTFN+BX+9mreu9++Z1ltgrUjykVxoB3ij6lqzRBJhuFnqk6KZtdZKYw
X-Received: by 10.37.61.196 with SMTP id k187mr53146yba.11.1468296357441; Mon, 11 Jul 2016 21:05:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.32.137 with HTTP; Mon, 11 Jul 2016 21:05:56 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.11.1607112330450.48246@ary.lan>
References: <em4745d403-8957-4994-9819-47cc8d9e1364@bodybag> <20160712030624.29734.qmail@ary.lan> <CAC=TB124b7G0w48LY4zP6TOqE+xZ3n1Fp4_KMaUTB_ZtCtrzCw@mail.gmail.com> <alpine.OSX.2.11.1607112330450.48246@ary.lan>
From: Marek Vavruša <mvavrusa@cloudflare.com>
Date: Mon, 11 Jul 2016 23:05:56 -0500
Message-ID: <CAC=TB13EzBnfPWEm_iwKO-qcTd8F2isfru7H0FQoZjBXaP37Pw@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/UERHwAM22M4wa1NCVI2fSR7rJ0M>
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 04:05:59 -0000

RFC 7766 is about DNS/TCP not about DNS/HTTP, the order of processing
has to be determined by the wrapping protocol. You would get it for
free if this draft was about TCP over HTTP or HTTP over DNS/TCP, but
it's not.

Marek


On Mon, Jul 11, 2016 at 10:32 PM, John R Levine <johnl@taugh.com> wrote:
>>> 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