Re: [DNSOP] Review of draft-livingood-dns-redirect-00

Paul Wouters <paul@xelerance.com> Thu, 16 July 2009 04:42 UTC

Return-Path: <paul@xelerance.com>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FE243A6ACF for <dnsop@core3.amsl.com>; Wed, 15 Jul 2009 21:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level:
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P65p6xT1UUEc for <dnsop@core3.amsl.com>; Wed, 15 Jul 2009 21:42:29 -0700 (PDT)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 34F233A68F6 for <dnsop@ietf.org>; Wed, 15 Jul 2009 21:42:29 -0700 (PDT)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) by newtla.xelerance.com (Postfix) with ESMTP id B9607C620; Thu, 16 Jul 2009 00:41:34 -0400 (EDT)
Date: Thu, 16 Jul 2009 00:41:34 -0400
From: Paul Wouters <paul@xelerance.com>
To: Mark Andrews <marka@isc.org>
In-Reply-To: <200907160017.n6G0GpEV051995@drugs.dv.isc.org>
Message-ID: <alpine.LFD.1.10.0907160038250.20118@newtla.xelerance.com>
References: <C680B730.EB2C%Jason_Livingood@cable.comcast.com> <alpine.LSU.2.00.0907131506280.30197@hermes-2.csi.cam.ac.uk> <alpine.LFD.1.10.0907131347330.8917@newtla.xelerance.com> <p06240806c681347afdd5@[10.20.30.158]> <alpine.LFD.1.10.0907142351170.30778@newtla.xelerance.com> <p062408adc683d0a46ecb@[10.20.30.158]> <alpine.LFD.1.10.0907151439100.31420@newtla.xelerance.com> <200907160017.n6G0GpEV051995@drugs.dv.isc.org>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Review of draft-livingood-dns-redirect-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 16 Jul 2009 04:42:30 -0000

On Thu, 16 Jul 2009, Mark Andrews wrote:

>> If I use my own validating stub resolver I can't make it to the portal page.
>
> With proper configuration of the validating stub resolver and the
> recursive servers your validating stub resolver are using you should
> be able to make it to the portal page.
>
> I do agree that it makes it more complicated.

With DNS redirection? I can see it with http redirection, but with
my validating resolver, I would only be getting servfails? They
either modify the data and invalidate the signature, or they strip
out the DNSSEC and cause my validating to servfail?

How would this work?

I just wish there was a dhcp option for this. Then we could signal
a landing page, and we could even signal the browser to wait and
not try to reload (and destroy) all my tabs into 20 copies of the
landing page.

Paul