Re: [Driu] [Doh] [DNSOP] Resolverless DNS Side Meeting in Montreal

Dave Lawrence <tale@dd.org> Tue, 10 July 2018 17:43 UTC

Return-Path: <tale@dd.org>
X-Original-To: driu@ietfa.amsl.com
Delivered-To: driu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CDE4130E2A; Tue, 10 Jul 2018 10:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ijkJQZp9F8T7; Tue, 10 Jul 2018 10:43:40 -0700 (PDT)
Received: from gro.dd.org (gro.dd.org [207.136.192.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E600E130E25; Tue, 10 Jul 2018 10:43:39 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id 475DB47A1C; Tue, 10 Jul 2018 13:43:38 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23364.61514.267429.409048@gro.dd.org>
Date: Tue, 10 Jul 2018 13:43:38 -0400
From: Dave Lawrence <tale@dd.org>
To: Paul Vixie <paul@redbarn.org>
Cc: Patrick McManus <pmcmanus@mozilla.com>, DoH WG <doh@ietf.org>, driu@ietf.org, Ben Schwartz <bemasc@google.com>, dnsop <dnsop@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, Daniel Kahn Gillmor <dkg@aclu.org>
In-Reply-To: <5B447154.5010307@redbarn.org>
References: <CAOdDvNp0S5-aEzy4ziqVvL1Kd+V79nD49_Zuo1dLoThXYP7nFg@mail.gmail.com> <5B447154.5010307@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/tAhzH9xkO5nn53bAfUtgH4LzVxs>
X-Mailman-Approved-At: Tue, 10 Jul 2018 11:07:08 -0700
Subject: Re: [Driu] [Doh] [DNSOP] Resolverless DNS Side Meeting in Montreal
X-BeenThere: driu@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "DNS Resolver Identification and Use \(DRIU\)." <driu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/driu>, <mailto:driu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/driu/>
List-Post: <mailto:driu@ietf.org>
List-Help: <mailto:driu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/driu>, <mailto:driu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 17:43:42 -0000

Paul Vixie writes:
> > For example www.example.com <http://www.example.com> pushes you a AAAA
> > record for img1.example.com <http://img1.example.com>. Should you use
> > it?
> 
> no. sibling names might be delegation points. kashpureff taught us this 
> in 1996 or so, and kaminsky reinforced that lesson in 2008.
> 
> > What if it is for img1.img-example.com <http://img1.img-example.com>?
> 
> certainly not.

In the large I agree with you, but I think there's more to it than
that.  If it pushed me DNSSEC records that I could verify myself from
my own configured trust anchor, why can't I trust them then?