Re: [Doh] [DNSOP] [dns-privacy] New: draft-bertola-bcp-doh-clients

Eliot Lear <lear@cisco.com> Wed, 13 March 2019 05:04 UTC

Return-Path: <lear@cisco.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051DB130DE3; Tue, 12 Mar 2019 22:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uZddekRXptaw; Tue, 12 Mar 2019 22:04:23 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E1EE130DC9; Tue, 12 Mar 2019 22:04:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6642; q=dns/txt; s=iport; t=1552453462; x=1553663062; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=Y21T41ED/1s9TGHrDFbm0pRGqn1V4ytDkgmG28XAZSs=; b=HuGBLgipm6O0Zi5ZqOj7nzO3WNuu/CvhLuxZFgkQHtUSA9nnOSAXxUmw YN5fUSgXoAVzjC85fOo+nOE5ktzyDwPIp3fOF1iUy59olrNxYeRGEc7Kg qpYZ8o6crXX3WEiS5QQTsHQzpd4II1afAMotuzA0iT/ow3tSd2rQ8CEcC k=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AHAAAQj4hc/xbLJq1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwIBAQEBAQsBgndxEieECoh5jGaSNoV1gXsIAwEBGAE?= =?us-ascii?q?KhEkChFs2Bw0BAQMBAQkBAwJtHAyFSgEBAQMBAQEhSwYFBQsLGCoCAicwBhO?= =?us-ascii?q?DIgGBbQgPr06BLx+FJoRjCgWBLwGBSIl7gX+BOB+CTIMeAQGEazGCJgOMJoR?= =?us-ascii?q?RTJJuCYRbjjoZkz6aYoJuAgQGBQIVgU4CL4FWMxoIGxU7KgGCQT6BU4h7hUA?= =?us-ascii?q?+AzCRQwEB?=
X-IronPort-AV: E=Sophos;i="5.58,473,1544486400"; d="asc'?scan'208,217";a="10707558"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Mar 2019 05:04:19 +0000
Received: from ams3-vpn-dhcp7163.cisco.com (ams3-vpn-dhcp7163.cisco.com [10.61.91.250]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x2D54I3b027990 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Mar 2019 05:04:19 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <0675B05A-54DE-4C07-A014-F8D4C272575E@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_838E1E39-B8CF-4C4F-B893-6B856C6106FB"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 13 Mar 2019 06:04:17 +0100
In-Reply-To: <891d320e-f05e-f926-f74a-7c09c6ed553a@huitema.net>
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>, "doh@ietf.org" <doh@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Christian Huitema <huitema@huitema.net>
References: <1700920918.12557.1552229700654@appsuite.open-xchange.com> <5342244.Q90AZAhhXk@linux-9daj> <a8a31672-40ef-3886-472b-0eca7df15262@cs.tcd.ie> <2356055.DoC3vY7yXE@linux-9daj> <891d320e-f05e-f926-f74a-7c09c6ed553a@huitema.net>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.91.250, ams3-vpn-dhcp7163.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/NzlQ5RcRuo31FDvwMyW9MQq5M7k>
Subject: Re: [Doh] [DNSOP] [dns-privacy] New: draft-bertola-bcp-doh-clients
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 05:04:25 -0000

Gentlemen,

This conversation has gone to the zoo.  What is or is not political doesn’t matter at this stage in the game, and neither is arguing over rights over bits.  If people want to do that I suggest doing so in the HRPC WG and with a draft in hand.  Flaming back and forth without an objective of actually modifying text or developing a work proposal is quite pointless.

What is important is to document the technical ramifications of the changes brought about by DoH.  To move things forward, can we simply go through the drafts in the side meeting, and indicate what administrators might do about any perceived negative effects?  Whether those effects seem negative to you only matters if there is a proposal for the IETF to take on new work to “correct” them.

Eliot

> On 13 Mar 2019, at 03:59, Christian Huitema <huitema@huitema.net> wrote:
> 
> 
> 
> On 3/12/2019 2:11 PM, Paul Vixie wrote:
>>> I don't see why, based on your argument, your concerns
>>> trump his.
>>> 
>>> Can you explain?
>> he's trying to achieve a political aim using technology. that is not the
>> purpose for which the internet engineering task force, or the internet itself,
>> was convened. it is not why our employers pay our travel costs. and it is not
>> why the rest of the world trusts our outputs.
> 
> Sorry, but no. I am vying for network transparency, and I believe that if filtering is to be enforced, it should be controlled by the user. You are claiming that safety mandates giving the network operator full control over name resolution. Both of these positions come from specific visions about how the network should work. Neither is more a political goal than the other.
> 
> -- Christian Huitema
> 
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh