Re: [DNSOP] DNS privacy and AS 112: the case of home.arpa

Joe Abley <jabley@hopcount.ca> Thu, 14 December 2017 00:31 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 8E521124B18 for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 16:31:27 -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 cBJe_zqxSCpd for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 16:31:26 -0800 (PST)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 10B5A1200F1 for <dnsop@ietf.org>; Wed, 13 Dec 2017 16:31:26 -0800 (PST)
Received: by mail-it0-x22b.google.com with SMTP id t1so7240415ite.5 for <dnsop@ietf.org>; Wed, 13 Dec 2017 16:31:26 -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=MK/AL29EpMWVblqLBt42WHzuzH0RduJQpYQcUIfZlGU=; b=DkmX6UaKp1Nh5SGzVPV4FxIGDti/AOniAC9FN5ONNW/7OCEvW6G32/E9N0SQvy85UB 0APCiJWEOyJKe59ECKdt4QZ8l3ds8IoktKDXZjk8ZctlObf0ihZ6sPW3446noFKMnBS7 wfkfM/BVLuXDAGxNMJNnwq33qENYfMvfnLwUc=
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=MK/AL29EpMWVblqLBt42WHzuzH0RduJQpYQcUIfZlGU=; b=E8qjyGi0jFANOBqcdhEx2hn22Ogulv8mPIinW5IdCkEK/jLo6e0UO4odbxDOMCdiwT hHuzO0Yw5IyOzPbe7LM/sjHe+NE2QuOw+nuVlvPE0befMeS69U6r1uokSLtAi93972yc dvDZgZq1Zjj8o85KtXb3P5WSIB7O81mPjT2Py2D+ukC5BGebz+PwoUX6xqKSHFvlXbh3 ZdBLbiOYIXdERlpdqr2OLgPOhwgDEe7g92BluW4ehNWyLXnZdcZicSj6wch8WaD99fQ0 sFxrOQCQIBHUFcWQAmowpWlqq8tU3MYBW+I06TFBMctjXaMc76j9uJbX4DEXKpk2PlM/ ALGA==
X-Gm-Message-State: AKGB3mL391zpWEOl0oZVzHybWODd+iiCAn7qp28TD+xW5IHXy5ShTpuN vhSqQQRKahXzyohe0/JbzXQP5w==
X-Google-Smtp-Source: ACJfBovgITTIb/2owda+Vnl54jLeqg1xjb8W8x0BZbwaLBgzX7DR3ztSm0oZb2w9gIqNGOY/B9W8kw==
X-Received: by 10.36.175.19 with SMTP id t19mr1062886ite.67.1513211485314; Wed, 13 Dec 2017 16:31:25 -0800 (PST)
Received: from [199.212.90.109] (23-233-21-69.cpe.pppoe.ca. [23.233.21.69]) by smtp.gmail.com with ESMTPSA id s73sm80952ioe.47.2017.12.13.16.31.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Dec 2017 16:31:23 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (15C114)
In-Reply-To: <23CF8A88-F530-426D-A6A9-4B80AF28D603@fugue.com>
Date: Wed, 13 Dec 2017 19:31:22 -0500
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dnsop@ietf.org, Paul Vixie <paul@redbarn.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <09515131-DD1B-4FC9-90F6-C088173857BA@hopcount.ca>
References: <20171211090051.qjoruin7nkdjsnvd@nic.fr> <5A2E4B7C.50509@redbarn.org> <20171211091800.wonjnvhl3xrx6r4s@nic.fr> <118C37A8-0DEF-460B-8A79-AAE470D3CED8@hopcount.ca> <1B37BBA1-D141-441A-855E-1ACFF2DC15BD@fugue.com> <EC253232-3713-426E-9300-20AE38C8BE4F@hopcount.ca> <23CF8A88-F530-426D-A6A9-4B80AF28D603@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1haD8lW-rOTggKhUaY5njblaMek>
Subject: Re: [DNSOP] DNS privacy and AS 112: the case of home.arpa
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 14 Dec 2017 00:31:27 -0000

Hi Ted,

> On Dec 13, 2017, at 17:14, Ted Lemon <mellon@fugue.com> wrote:
> 
> Can you point to the actual ambiguity?   The reason we said "one or more black hole servers" was to leave it up to the operator of .arpa to decide which black hole servers and how many of them.   That was a deliberate choice, not an omission.

The ambiguity is (for example) that "point to" is not a well-defined phrase, given that we have two documented ways of doing this in the AS112 project, and neither is "black hole server" which from the examples seems it refers to servers made available from the AS112 project, but which examples surely are non-normative.

This no doubt sounds pedantic to many, but I think (a) that a certain precision is warranted in directions to the IANA and (b) given that the obvious interpretation is not possible to implement accurately (the problems with new delegations to the original AS112 servers having been well documented) ambiguity is in fact *required* in order for anything to happen here.


Joe