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

Paul Wouters <paul@nohats.ca> Tue, 27 November 2018 00:59 UTC

Return-Path: <paul@nohats.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 89C2C1310AC for <dnsop@ietfa.amsl.com>; Mon, 26 Nov 2018 16:59:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.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 t1OZp3WymfPz for <dnsop@ietfa.amsl.com>; Mon, 26 Nov 2018 16:59:24 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD623131092 for <dnsop@ietf.org>; Mon, 26 Nov 2018 16:59:23 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 433lmS3NtCzMCW for <dnsop@ietf.org>; Tue, 27 Nov 2018 01:59:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1543280360; bh=zphuQSW2n2l/O+8abX+vDJSfATRObVzo5vMrzOoqFxk=; h=From:Date:Subject:References:In-Reply-To:To; b=odEfMSazzz+dMt5oZqeELm6EpQYTO5ijeXGQtunZlGq8sXd6VsfRqqJ3yrob1HJ9L rBEMIZ1xHsa+q1mzF4CJwuNGY4lMavBJ8LpRJH2PM8l3slszs7+v8Ip8f85hYZubOH EygFagB7TV3E71IyPVqac4c7OtQH4B1v7uSwoiWk=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id bc78lFbhQAIi for <dnsop@ietf.org>; Tue, 27 Nov 2018 01:59:19 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <dnsop@ietf.org>; Tue, 27 Nov 2018 01:59:18 +0100 (CET)
Received: from [192.168.1.24] (node-ano.pool-118-173.dynamic.totbb.net [118.173.53.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id CE8193A3788 for <dnsop@ietf.org>; Mon, 26 Nov 2018 19:59:12 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca CE8193A3788
From: Paul Wouters <paul@nohats.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Tue, 27 Nov 2018 07:59:04 +0700
Message-Id: <B00FCC13-587A-4E33-8BC9-D708EB6B4399@nohats.ca>
References: <CAHw9_iL6CpLf6h_ysWEjvNjzaU2TPk-SyVGzLs_J9Yk_5A4OmA@mail.gmail.com> <9DBE5370-BEA4-48CE-B9FB-356ED1CCC1E7@icann.org> <CAPt1N1m1NoJoBPWJ5L96WwjrF6QEzB93pRxZpaHJxoBMpxtVRw@mail.gmail.com> <B4F27495-AA1E-44B3-B0DE-C228E0EDC84C@icann.org>
In-Reply-To: <B4F27495-AA1E-44B3-B0DE-C228E0EDC84C@icann.org>
To: dnsop@ietf.org
X-Mailer: iPhone Mail (16A405)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yhYjOLVZEzvO3KSlQhUY2h-3iEc>
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: Tue, 27 Nov 2018 00:59:27 -0000

This discussion would be better if people took warren’s example and then read the draft before commenting.

I will watch the discussion before responding further.

Thanks

Paul

Sent from mobile device

> On Nov 27, 2018, at 01:43, Paul Hoffman <paul.hoffman@icann.org>; wrote:
> 
>> On Nov 26, 2018, at 10:36 AM, Ted Lemon <mellon@fugue.com>; wrote:
>> On Mon, Nov 26, 2018 at 1:29 PM Paul Hoffman <paul.hoffman@icann.org>; wrote:
>> Once you are inside a network (the N in VPN), it's "my network, my policy" all over again.
>> 
>> Can you unpack what you mean by this?   I assume you don't mean that we should provide a mechanism whereby network operators can automatically override DNSSEC trust anchors! 
> 
> For names that are only available within a trusted network, yes I really mean that. 
> 
> --Paul Hoffman
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop