Re: [Add] [Ext] antitrust implications of IETF resolver discovery protocol work
Vittorio Bertola <vittorio.bertola@open-xchange.com> Tue, 24 March 2020 11:34 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 2D6033A0933 for <add@ietfa.amsl.com>; Tue, 24 Mar 2020 04:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 aAJHiBFsPmg6 for <add@ietfa.amsl.com>; Tue, 24 Mar 2020 04:33:49 -0700 (PDT)
Received: from mx3.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 1B8AC3A087F for <Add@ietf.org>; Tue, 24 Mar 2020 04:33:44 -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)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPS id 088B76A28C; Tue, 24 Mar 2020 12:33:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1585049621; bh=dt2Bcx/gMEX6PTOQ5vc0XwyJ2npIQugtVm9HGQgmKZ8=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=8gvoHWcaFKwfYFMi3pqWKKHdsAyGdlii36QjUyS8WLy86t5wijVwx6tfxCm88XbJD D5zNSTMjjTJkHMJD738N4s/mJZ5cI40Ejnoxa5lt693o782ic84rLV3mVVb+sTNOzS tY1GzMlIL5G7sikg/PjW9CW172x/Gl8fdWwBQdIw/s42riTyPqKwjy/55BM93UwrUa izf2MQ/2GxgF+40OK/sE4H3bkSKES/aQTiVkn/xt7bMU09xK5sQw1spJN7Q/V8Osz0 eh+YZTgUMyF1jIwG3/mY7+y51o6A+DNHB5SWCJsY2Xlg0fPPrhg7QcDhsnJ+hmkDC8 RGaazsb6PtZ8Q==
Received: from appsuite-dev-gw1.open-xchange.com (appsuite-dev-gw1.open-xchange.com [10.20.30.221]) (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 F0E873C028E; Tue, 24 Mar 2020 12:33:40 +0100 (CET)
Date: Tue, 24 Mar 2020 12:33:40 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: "Add@ietf.org" <Add@ietf.org>
Message-ID: <991386444.3953.1585049620888@appsuite-dev-gw1.open-xchange.com>
In-Reply-To: <A22F29EB-10D0-4636-B5C7-A88378E0A3CE@nbcuni.com>
References: <5c9880d8-d03c-d28f-08b8-5f704270ed56@gmail.com> <A22F29EB-10D0-4636-B5C7-A88378E0A3CE@nbcuni.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_3951_1375223979.1585049620851"
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.4-Rev0
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/uKbyC4AIeL7fFIq00azu8Gs21HM>
Subject: Re: [Add] [Ext] antitrust implications of IETF resolver discovery protocol work
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: Tue, 24 Mar 2020 11:34:01 -0000
> Il 24/03/2020 03:44 Deen, Glenn (NBCUniversal) <glenn.deen@nbcuni.com> ha scritto: > > > What anti trust aspects are being suggested for discovery of dns resolvers and mechanisms to convey resolver information ? > > I don’t see what the possible concerns are. > Actually, antitrust concerns have been raised about deployment models in which discovery is *not* being done, as they attribute to whoever controls the client the ability to also determine or constrain the resolver that is being used, thus giving people with a strong position in the former market also a strong influence on the latter one. Having a discovery mechanism could provide a way to alleviate those concerns, for those that find them reasonable. -- 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
- [Add] antitrust implications of IETF resolver dis… Tony Rutkowski
- Re: [Add] [Ext] antitrust implications of IETF re… Paul Hoffman
- Re: [Add] [Ext] antitrust implications of IETF re… Tony Rutkowski
- Re: [Add] [Ext] antitrust implications of IETF re… Deen, Glenn (NBCUniversal)
- Re: [Add] [Ext] antitrust implications of IETF re… Vittorio Bertola
- Re: [Add] antitrust implications of IETF resolver… Jim Reid
- Re: [Add] [Ext] antitrust implications of IETF re… Jim Reid
- Re: [Add] [Ext] antitrust implications of IETF re… Tony Rutkowski
- Re: [Add] [Ext] antitrust implications of IETF re… Jim Reid
- Re: [Add] [Ext] antitrust implications of IETF re… Deen, Glenn (NBCUniversal)