Re: [sunset4] future of dnssec?

Ted Lemon <mellon@fugue.com> Wed, 22 February 2017 14:04 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD99129957 for <sunset4@ietfa.amsl.com>; Wed, 22 Feb 2017 06:04:08 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 PibJEh48E3Dm for <sunset4@ietfa.amsl.com>; Wed, 22 Feb 2017 06:04:07 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 CDF321298BF for <sunset4@ietf.org>; Wed, 22 Feb 2017 06:04:06 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id n21so3013773qta.1 for <sunset4@ietf.org>; Wed, 22 Feb 2017 06:04:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=QSwn9lS/25e/sKfpRZ4HQE7K4vJhB1JDKzkJ2N9kFdA=; b=mUGU6MI6yyEw2ReJ7sbW89rY5HYDcTTaNVpiVdZcrhP8bl3mjKbhdmqd2cXcHD7tf6 CaWDKcrFOkj8sgckoJ2TsNbDinAPlr5R6cXlf33IXGO8vFPDipU26oQnxJKsx2WP9r84 1McfVUtVKLp1vIwEKnqOZJoG+WUqC2sLrstbwD5IYm3+9/Uaie9cWuljA5YXQvkEcKMd SRGEIvsM1NxDMGfMD2CASDz2SBRZ5F5MZO4CBFNh+H8hTfQEJN5FjNhP9yiQ+q6pc0i7 Ap23eNvkvBusrYg06Q7gL/IPRfHROjpnFNRQ1Cp95aHgK/o7xyZ0+Z6vXHDOTOU+SzB1 gaKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=QSwn9lS/25e/sKfpRZ4HQE7K4vJhB1JDKzkJ2N9kFdA=; b=bzt66PSpwHlIRU1nvkPgnGN9oPLzUa60a82VTTg3X3UgfMxv22yhcfA6h4T4CfvNmW QoW4sstMaHd5AcJdchaqR7JRkOoJu0mSkgQtWgYrArKq0N0ttm9ttWtVEl7Fv92vQSjo Zuop1fqMuRrMhAfXIEy8mAa7nIDiJjc70732egBgcM2VhoFVxvnKubv6Lih0VgF/RfgK CCRf6PyjkUeHy4P+n8u9WsrFT9YrwWwB+e3Nbeno7gOsMovnzBNEXUCYeugbyvW+S2bP zq/rPSqXgb5V8CYC03PmgBBbEoVq4v1yQnEFrBZa+hWvEvuADFSXh8zBdi9h7QWenAzH jAZw==
X-Gm-Message-State: AMke39ldVGL1pSGuUQkBLt3JSkleT0/zyOIBxXJnTD+j8U+A5q5SymQkhIkIZOAYJFEiKQ==
X-Received: by 10.237.44.103 with SMTP id f94mr33113370qtd.292.1487772245854; Wed, 22 Feb 2017 06:04:05 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id o190sm706077qkc.65.2017.02.22.06.04.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2017 06:04:04 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B5E8C545-55B9-4ECB-B0C8-C3EEFEECD320@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A1DDE2C9-B1C8-4990-AFB0-B6F033F4ABD4"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 22 Feb 2017 09:04:02 -0500
In-Reply-To: <6536E263028723489CCD5B6821D4B21334D566F0@UK30S005EXS06.EEAD.EEINT.CO.UK>
To: "Heatley, Nick" <nick.heatley@ee.co.uk>
References: <6536E263028723489CCD5B6821D4B21334D566F0@UK30S005EXS06.EEAD.EEINT.CO.UK>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/QckMjDaPWhtQiScxkrr7TzAHTsg>
Cc: "sunset4@ietf.org" <sunset4@ietf.org>
Subject: Re: [sunset4] future of dnssec?
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:04:09 -0000

Nick, the solution to this is to do DNS64 in the validator.   If the validator is a stub resolver, do the DNS64 hack there.   AFAIK the technology to support this already exists.

> On Feb 22, 2017, at 7:23 AM, Heatley, Nick <nick.heatley@ee.co.uk> wrote:
> 
> Post exhaustion, the majority of cellular networks and some public wifi networks will use DNS64.
> DNSSEC and DNS64 do not get along. DNSSEC for “A records only” is broken.
> Is this the reason why all content must go v6?
> Or is the case for DNSSEC still questionable?
> Or do end hosts need to perform DNS64 so “DNSSEC for A records only” can be intact?
>  
> NOTICE AND DISCLAIMER
> This email contains BT information, which may be privileged or confidential. It's meant only for the individual(s) or entity named above. 
> If you're not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. 
> If you've received this email in error, please let me know immediately on the email address above. Thank you.
> 
> We monitor our email system, and may record your emails.
> 
> EE Limited 
> Registered office:Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW
> Registered in England no: 02382161
> 
> EE Limited is a wholly owned subsidiary of:
> 
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no: 1800000
> 
> _______________________________________________
> sunset4 mailing list
> sunset4@ietf.org <mailto:sunset4@ietf.org>
> https://www.ietf.org/mailman/listinfo/sunset4 <https://www.ietf.org/mailman/listinfo/sunset4>