Re: [DNSOP] [Ext] Favor: Weigh in on draft-ietf-ipsecme-split-dns?

Joe Abley <jabley@hopcount.ca> Mon, 26 November 2018 18:38 UTC

Return-Path: <jabley@hopcount.ca>
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 DB53F130FFC for <dnsop@ietfa.amsl.com>; Mon, 26 Nov 2018 10:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 vnJvZBCfK_wp for <dnsop@ietfa.amsl.com>; Mon, 26 Nov 2018 10:38:02 -0800 (PST)
Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (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 EB60A130FF4 for <dnsop@ietf.org>; Mon, 26 Nov 2018 10:38:01 -0800 (PST)
Received: by mail-yw1-xc2c.google.com with SMTP id d190so7968245ywd.12 for <dnsop@ietf.org>; Mon, 26 Nov 2018 10:38:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KTchK52UPiL3xrX+1rqof9yBDXfSRfU4AP5bmxMKTrg=; b=JOw2g2uDhpinGVdW1/CkRM4MhndhkKj2IDkeLLcWROMjDEG1dUodVpO7P8Q0U4duif ztBTk1dSohvHSwDZnFLrJA8CrQZ1UK95dAisth/WOuTmGUDTO9uF/JLF+zckvWwluYrP mFnWLhYSpD3KXkkyuV8JPKtp+UL1vOcEYqyDY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KTchK52UPiL3xrX+1rqof9yBDXfSRfU4AP5bmxMKTrg=; b=tVZouejOB6mDppcBUT8EkRkVRgS6wqZzQvmIGvrA1uPYEbxO7uEpyFpt4sZjsCT0wu sFULNhZ2J0PCcfSOtpvL86ce71oa748b6cBNivW3wxIPq3YTEpmB8iCjjXHZshyvGPHO 9JS0fBukxu1VeZc/a3q5VfuNRkunBoVcjmRsjXgCufTcB/8DRgLSFKzd/MYaDO6Tzhmq JYGZ4/l6qtFazkvMtdxj6vs/+SgZ1rRpegDNdcKCduMU3nae0Uycd4uZZtWlfFFtxGND irvJ9OSXSOJTClyztpYtE/0a6ZsmZ+u0cXJdlcjK5ePD/poIhAAPvQFHdSVWZFUg1Xfx blwA==
X-Gm-Message-State: AGRZ1gKFXqPvLCfOdQnXFefBTscXqw0PM1RBEwsIUDkQ727sTX08N6sE KpOyXKZVgkF+/+1/Ugm5jLUJ6A==
X-Google-Smtp-Source: AJdET5fhgHXdEWl8G9gGm7mLyjkkNIytrE5R0t5YnZtX6xVDIkTBB4vETsc1Ee9WhoaOTZCQn89LcQ==
X-Received: by 2002:a81:f88:: with SMTP id 130mr30367967ywp.332.1543257481074; Mon, 26 Nov 2018 10:38:01 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:3:b57d:f87e:cba0:7789? (node-131dv5luxtjoaugryh.ipv6.teksavvy.com. [2607:f2c0:101:3:b57d:f87e:cba0:7789]) by smtp.gmail.com with ESMTPSA id k187sm268605ywf.71.2018.11.26.10.37.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Nov 2018 10:37:59 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <9DBE5370-BEA4-48CE-B9FB-356ED1CCC1E7@icann.org>
Date: Mon, 26 Nov 2018 13:37:56 -0500
Cc: Warren Kumari <warren@kumari.net>, dnsop <dnsop@ietf.org>, "draft-ietf-ipsecme-split-dns.all@ietf.org" <draft-ietf-ipsecme-split-dns.all@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BF05F65-E13D-4FCD-B52C-EFE4D89D38A3@hopcount.ca>
References: <CAHw9_iL6CpLf6h_ysWEjvNjzaU2TPk-SyVGzLs_J9Yk_5A4OmA@mail.gmail.com> <9DBE5370-BEA4-48CE-B9FB-356ED1CCC1E7@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wynV8fOGjq7vS7hDrXmjUc6-5nw>
Subject: Re: [DNSOP] [Ext] Favor: Weigh in on draft-ietf-ipsecme-split-dns?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 26 Nov 2018 18:38:11 -0000

On 26 Nov 2018, at 13:28, Paul Hoffman <paul.hoffman@icann.org>; wrote:

> On Nov 26, 2018, at 8:17 AM, Warren Kumari <warren@kumari.net>; wrote:
>> As you can guess from the name, VPNs-R-Us is sketchy
> 
> If you trust a VPN operator, you trust the VPN operator. What the rest of your message is asking is "can I partially trust the VPN operator to do X but not Y, and have all that be explicit?".

I think you can trust a VPN provider to make iPlayer work when you're not in the UK, or to get a better menu of television on Netflix, or to obscure the fact that you like to visit webpages that might get you a letter from the MPAA, but it could well be a stretch to say that you trust them not to subvert the DNS when you visit Paypal. The average end-user doesn't know what DNS is, never mind DNSSEC.


Joe