IETF Logo Mail Archive

Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?

Paul Vixie <vixie@tisf.net> Wed, 23 December 2015 05:15 UTC

Return-Path: <vixie@tisf.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636FE1AC41D for <dnsop@ietfa.amsl.com>; Tue, 22 Dec 2015 21:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 4jf9yRZ1z8_h for <dnsop@ietfa.amsl.com>; Tue, 22 Dec 2015 21:15:31 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51F861AC41C for <dnsop@ietf.org>; Tue, 22 Dec 2015 21:15:31 -0800 (PST)
Received: from linux-85bq.suse (unknown [24.104.150.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 7CE1E13B5E; Wed, 23 Dec 2015 05:15:36 +0000 (UTC)
From: Paul Vixie <vixie@tisf.net>
To: dnsop@ietf.org
Date: Tue, 22 Dec 2015 21:15:31 -0800
Message-ID: <3040894.aPaWt5ExKr@linux-85bq.suse>
Organization: TISF
User-Agent: KMail/4.14.10 (Linux/4.1.13-5-default; KDE/4.14.10; x86_64; ; )
In-Reply-To: <CAKr6gn2yNB-S7Uk=Sx_=iHUUFQDqRxhrVznRP3GNswkyWvBgxw@mail.gmail.com>
References: <20151217020754.6915b71c@pallas.home.time-travellers.org> <4909572.yk9lYxXkhq@linux-85bq.suse> <CAKr6gn2yNB-S7Uk=Sx_=iHUUFQDqRxhrVznRP3GNswkyWvBgxw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart2751736.bVOrN2szQb"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/ZOabbtVP5QIsPQkdnzAVxgtXaoA>
Cc: George Michaelson <ggm@algebras.org>
Subject: Re: [DNSOP] Should we try to work on DNS over HTTP in dnsop?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 23 Dec 2015 05:15:32 -0000

On Wednesday, December 23, 2015 03:13:04 PM George Michaelson wrote:
> I'd be interested in the cache effects. If the TTL is mapped into cache
> age, then there is potential for CDN distribution to work more better
> gooder.

for that, you need a RESTful/JSON interface. the method+URI is a cache key.

-- 
P. Vixie

v2.23.0 | Report a Bug | By Email