Re: [Pearg] Responding to "Concerns over DNS Blocking" technical error(s)

Vittorio Bertola <vittorio.bertola@open-xchange.com> Fri, 04 August 2023 07:47 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE72C13AE5A for <pearg@ietfa.amsl.com>; Fri, 4 Aug 2023 00:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7FRiCjX46MC for <pearg@ietfa.amsl.com>; Fri, 4 Aug 2023 00:47:05 -0700 (PDT)
Received: from mx3.open-xchange.com (mx3.open-xchange.com [87.191.57.183]) (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 05575C151B1A for <pearg@irtf.org>; Fri, 4 Aug 2023 00:47:04 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id E07596A143; Fri, 4 Aug 2023 09:47:01 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1691135221; bh=S0cuChJaZLfrFc1o48un6Zii1c+nFDD2rHo/fjhnKZo=; h=Date:From:To:In-Reply-To:References:Subject:From; b=t0v4Wd3agR9VeihGJz09ggg/SODb20CTbfKH+Xiqgwvi74JYRQdyw6h4hOcLNOhfK Pv3AiMJ9GIjIhcicHFFSBRlV/4M+WCXnB31EEZ1nwHolSJxO08TDAai3CXsmkRCdOu kb2YnKwD6rbwpbLqhM/Urd6ZtcMKSVqvZbsQ7nEgzu5nqrAtkoiTmtdoGT4S0FS8kc 7tRHNTkIFiAXsMadGXGQOEWY8r8O9O+tV62r0c3He1DQ88BCcl+n1UboMkHChUkISc RFC8k9Z5BazTaGBB8icmk0m8SaJZ1aUVeRMHwoX6Ce8QMlZT1oLbBsyZ8i7Uz6aEhr MihiPqFCtQgvg==
Received: from appsuite-gw1.open-xchange.com ([10.20.28.81]) by imap.open-xchange.com with ESMTPSA id 8KVTNfWszGRVSTQA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>); Fri, 04 Aug 2023 09:47:01 +0200
Date: Fri, 04 Aug 2023 09:47:01 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, "pearg@irtf.org" <pearg@irtf.org>
Message-ID: <1447859971.25968.1691135221841@appsuite-gw1.open-xchange.com>
In-Reply-To: <1FA02373-5569-447B-83FA-112A0FB008A5@ericsson.com>
References: <CAMgphBBYNMqiwg=SkZmh6s8gCfVoFp8zmwHNCiVYzqnBwyzKNA@mail.gmail.com> <1FA02373-5569-447B-83FA-112A0FB008A5@ericsson.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_25966_681562185.1691135221830"
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev49
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/pearg/qHYL72RXeKEK2QcXIAqswMgswWQ>
Subject: Re: [Pearg] Responding to "Concerns over DNS Blocking" technical error(s)
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Aug 2023 07:47:09 -0000

 

> Il 03/08/2023 07:12 PDT Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> ha scritto:
> 
> On your point 2: I agree that DNS filtering or other blocking and filtering techniques are generally problematic. I’m not sure about your point about transparency; you can also design mechanisms to provide feedback about the blocking on other layers; however, if these things get implement is a different question. Still, for this letter it wasn’t the intention discuss blocking and filtering generally but point of the global implication of this proposed regulation. I find that even more problematic because there is always the option for a global/non-regional to not comply with a regulation (and depending on the market condition) not serve a certain service in a certain region anymore, which finally can really “break” the Internet. We don’t see this for DNS (yet) but we already see it e.g. in the regulatory “fights” about news content.
> 
I don't see the problem for the Internet if Google and other non-French resolvers stop serving DNS to France rather than comply with French law. There are hundreds of ISPs in France that provide DNS resolution to their customers, there are many open resolvers, and there will soon be the European public resolver (DNS4EU) which was funded by the Commission exactly to make sure that at least one big scale public resolver remains available in Europe even if all global resolvers went away. DNS is an open standard with many free implementations, so anyone can bring up more resolvers in case of need. Definitely, the Internet won't stop working in France.
 
This is just a business struggle for market shares and I really don't get why the IETF wants to take the side of some companies over others. I think this is not appropriate.
 
Even in general, I don't get the point that if global big tech players do not offer service in a country then this will "break the Internet". For example, Amazon is not offering service to all countries of the world - does this mean that the Internet is "broken"?

--

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