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:39 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 28EC612D094 for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 20:39:58 -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=XNb7cNrX; dkim=pass (1536-bit key) header.d=taugh.com header.b=EKDHISu9
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 0mhgSQUDc6co for <dnsop@ietfa.amsl.com>; Mon, 11 Jul 2016 20:39:57 -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 F284812B059 for <dnsop@ietf.org>; Mon, 11 Jul 2016 20:39:56 -0700 (PDT)
Received: (qmail 54078 invoked from network); 12 Jul 2016 03:39:55 -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=d33d.5784668b.k1607; bh=mjmzgGT4aBBBG0MN2EhFxKPujjuQtlZNgjMO2HrVxMo=; b=XNb7cNrX/H5y4utkY8Q3mF7SMDMEwl2Qa2Hn36Oy3Hp+fBdw+B99O2CKMbiAVykic0Ptxu4ulL2L8crfMxuIl0ywz9npkbbMBV35nltOdxfKR1oPhatV4KmAXOuzgQYNAVD9d6VopaIW0KAT/GK4VaJsIWe+yPoFwNMwBGR3xnx09qcjNXtulxbWGfugT1Xlp4IJUOxWnDZYiXTaALHwWrY9iT3MLdPN6tJiK1H8gEsWJ08H178WxFG2zN1IRLIx
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=d33d.5784668b.k1607; bh=mjmzgGT4aBBBG0MN2EhFxKPujjuQtlZNgjMO2HrVxMo=; b=EKDHISu9ai8fTdUPfKGvfGoa93HHPe9nFeDTOIsIMve5IT2yvzJfISbUPxBeemvY5UJEGAmMpDjiEZ71nw81y0M/IZR4+Tu1PeZPT9cdaC4VmHsjzzIPQH4RTZJdgdjFRp0/afTzuc5FYO99d1XOahOraYQerqz+FGfYxqgcA2s1cmDdw5PgxdFrpDgePvWjE5dVN6UXc/UrlwHHgZO5Es53vSO/UVltmb2gdsQ5Rpffnh3ulVqdh2nxVuxWFWvo
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:39:55 -0000
Date: Mon, 11 Jul 2016 23:39:55 -0400
Message-ID: <alpine.OSX.2.11.1607112336330.48266@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Adrien de Croy <adrien@qbik.com>
In-Reply-To: <emb8d27236-31f5-4f14-ab78-4f26f9db49e2@bodybag>
References: <emb8d27236-31f5-4f14-ab78-4f26f9db49e2@bodybag>
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/9wm1FuBwmlZuIylny2dYAtTrLec>
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:39:58 -0000

> for a web to DNS proxy to decide to send a reply back, it would need to 
> consider it complete?
>
> Or are you proposing that the http server would start streaming back the 
> payload as it received the (possibly out of order) replies?

I was thinking that the proxy would get all the queries from the DNS 
request, deal with them however it wants, maybe stuff them to a nearby DNS 
cache with TCP if it pipelines properly, or split them up into separate 
requests if it doesn't, then collect the responses and send them back when 
it has them, which I guess would constitute streaming.  RFC 7766 says that 
out-of-order is fine.

I suppose with http/2 we get two-way streaming more or less for free.

R's,
John

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