Re: [Add] What to do in this potential working group

Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 21 August 2019 10:43 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAF21208FF for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 03:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 Ll_SODQSM--E for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 03:43:53 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 6F7B41200B4 for <add@ietf.org>; Wed, 21 Aug 2019 03:43:53 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 4E8206A273; Wed, 21 Aug 2019 12:43:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1566384230; bh=BE2tuD/pzhnEUZaVwYMz/pIDO+371t9rrH1OYuS/Ws8=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From; b=nx1O8VdFg9RAj2aNarZ687E4gGr5Uk9GRTCnSsEgO7xdl7QWFMbsrY3gjoMSrzHJP DXIRzo6TnER5KTh0m1FdR/DgOUCsF4IUexcv24O7qrZt9pfOguyRfjW01cmEt4Na8y fDZ7uL2gh8vR2CazJGp4F+YlagZ9mcXqz7yGSIBppKD7sT8iDRPGgs5GBWP2IpRzIl YyhBKWQYCIdo3tSxYbDDtN5UQJo6bNfzcrb4CDWVKE9XII2qA1QnFSFK20UQBo2AN5 7CC6CsJBbdED+zD3B75mMvsXKknsX87PpWoLigJHMoCIYtVZ1hwb1QlAPK7ovFchxv gy5HN2Q+sg/yQ==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 433853C0434; Wed, 21 Aug 2019 12:43:50 +0200 (CEST)
Date: Wed, 21 Aug 2019 12:43:50 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Reply-To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Jari Arkko <jari.arkko@piuha.net>, add@ietf.org
Message-ID: <1081276693.4678.1566384230225@appsuite-gw1.open-xchange.com>
In-Reply-To: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.2-Rev10
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/lLEzY9guR3wy3ASuvA-LYtEU0NM>
Subject: Re: [Add] What to do in this potential working group
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 10:43:55 -0000


> Il 20 agosto 2019 22:01 Jari Arkko <jari.arkko@piuha.net> ha scritto:
> 
> I’ve been on vacation and doing some other things for the last couple of weeks, and now I’ve been trying to read the mailing list discussions. Not easy!

I am also trying to clear the backlog - still 300+ messages left (though almost half of them seem to come from a single person).

> In any case, to start with the parts that we possibly do agree on, there is at least a beginning of a list of work items. For instance:
> 
> * Improved mechanisms for discovery and selection of encrypted DNS transports
> * Best operational practices for running an encrypted DNS transport service (possibly subdivided for the type of deployment, e.g., ISP or global service)
> * Recommendation for precedence of configuration mechanisms
> * Recommendation that having devices or apps “call home” for every user action to a centralised global service is bad practice and should be avoided

I still think that having an agreed write-up of the issues and/or of the use cases, even without any recommendation on how to deal with them, could also be useful. This was the main subject of the original three drafts presented in Prague.

This said, the elephant in the room is the use of DNS as a control surface. The IETF as a community disagrees on whether this should exist or not, but as Patrik pointed out, many sovereign countries have already decided that a control surface has to exist, and the industry is required to provide it (or go to jail). There are also plenty of cases in which end-users themselves ask the industry to provide similar control features to them.

A clear and final agreement on whether the IETF is ever going to work on providing such a control surface in a standard way (either DNS-based or in some other way that is at least as effective as DNS filtering is today), or whether the part of the industry that is required to provide it should work on it somewhere else, would IMHO make the rest of the discussion much more focused.

-- 
 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy