Re: [Add] [Ext] antitrust implications of IETF resolver discovery protocol work

Tony Rutkowski <rutkowski.tony@gmail.com> Tue, 24 March 2020 01:21 UTC

Return-Path: <rutkowski.tony@gmail.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 220EC3A0F6D for <add@ietfa.amsl.com>; Mon, 23 Mar 2020 18:21:39 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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=gmail.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 figZ_XO_RpET for <add@ietfa.amsl.com>; Mon, 23 Mar 2020 18:21:37 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 BCAB53A0F70 for <Add@ietf.org>; Mon, 23 Mar 2020 18:21:36 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id c145so17674814qke.12 for <Add@ietf.org>; Mon, 23 Mar 2020 18:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:cc:message-id:date:user-agent:mime-version :content-language; bh=zbLodocoO2wmpxkQKRAo/W0GyKukotvqo9M6wVTOcrg=; b=g7RYQ/i0QtikHea+HdmHo5C6N174ei6LcnToYR8vHZ/xcky1Q9VzP1g4LlC07yaHr8 3iWxBCiTcaKaQfSbQVlffcbF7d7Ey5leN5WvjvupU1o9QAS97tfZEAurirJCUrNnkOqM puSO0JLYAlA2T5gdTsYfXTZHLhZgKcQjrq5F2NaxtSoMD4uxIO+HjbcnvTJG+ND8PhPy 0GAWmrBmH2FewyIWO3bS2eyU06G0Cd8QvC63B1bsPilkk8EAOKOfaOxh4PiSLwh0EGzT T4kj899jeNC7Rh0a87wfaJA2v05tXB2XPvOS6pcDT9E8whh5rztyn1BW0rnhOUaqI7cS F4zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:cc:message-id:date:user-agent :mime-version:content-language; bh=zbLodocoO2wmpxkQKRAo/W0GyKukotvqo9M6wVTOcrg=; b=g87H4bh/sjPlOZa+5RHBoVxBKQyJJYnWfUH9i6BNyRRDuH3NxKbb695/Wxr0tsi3Xj ksQGV9yp4jwfeiBEkK6aM85US1R4keAYgycGBozAd/VK2QJMX6Otg8CZ7CusyAhQHsoZ fOSY+AJJJFqfiH12lU0/dfOqIzPy29nzyjvo0AnxLzeNv+PUKNsy7mW6ljEv17buAOgA 875CTBDhruNrMxei7Q3WBd33GX6dYUUEYlqlSAHzoEdKe3txLIC3uAFQv/tpNYUGAap7 djl03oDAtcQlBJ4jzQNj2Bf7RyoVx1eqjbbw/G9JZqrBD9NxVxIxJgaaQhZN4hP7CCGi ocWA==
X-Gm-Message-State: ANhLgQ2mON6CptGiGt+iBebf4wmhlcsFv+PMn9Ay6o2R67pwCyHg8Jnr AvMThxZrySDY29gbR6DmdFA=
X-Google-Smtp-Source: ADFU+vsX7KgMNePgtawy2/Ak32EFid3UmsfIzpFY1KT+KOOSB59snn65zN4z08MgKNXhy5vXV3DwVQ==
X-Received: by 2002:a37:cc5:: with SMTP id 188mr24614361qkm.161.1585012895565; Mon, 23 Mar 2020 18:21:35 -0700 (PDT)
Received: from [192.168.1.53] (pool-70-106-222-98.clppva.fios.verizon.net. [70.106.222.98]) by smtp.gmail.com with ESMTPSA id f71sm12359220qke.57.2020.03.23.18.21.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Mar 2020 18:21:35 -0700 (PDT)
To: Add@ietf.org
From: Tony Rutkowski <rutkowski.tony@gmail.com>
Cc: Robert Kahn <rkahn@cnri.reston.va.us>, Paul Hoffman <paul.hoffman@icann.org>
Message-ID: <5c9880d8-d03c-d28f-08b8-5f704270ed56@gmail.com>
Date: Mon, 23 Mar 2020 21:21:34 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------B1BC11A4B2D5AF324E893E94"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/cmNjZHpIQtn9Z6_YcGcIEtfj-xU>
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 01:21:39 -0000

Hi Paul,

Indeed they have.  That's the point, they are similar.  Bob can speak as 
to the similarities and why The Handle System might be better here, or a 
competitive alternative.

This kind of work in the past has usually had some kind of 
governmental/intergovernmental aegis for antitrust protection. Here, it 
appears there is arguably significant potential exposure.  Just 
suggesting an antitrust analysis is appropriate, as well as some care as 
to the anti competitive effects.

--tony

>
>       Re: [Add] [Ext] antitrust implications of IETF resolver
>       discovery protocol work
>
> Paul Hoffman <paul.hoffman@icann.org>Tuegt;Tue, 24 March 2020 00:22 UTCShow 
> header <https://mailarchive.ietf.org/arch/browse/add/?#>
>
> On Mar 23, 2020, at 5:17 PM, Tony Rutkowski<rutkowski.tony@gmail.com>  <mailto:&lt;rutkowski.tony@gmail.com&gt;>  wrote:
> > 
> > Has anyone done an analysis of the antitrust implications of this work under an IETF aegis?  Has the IETF Trust bought off on this?
>
> Not that has reported to this group.
>
> > The work here is similar that undertaken for The Handle System, and the CNRI work in ITU to develop X.1255 and related treaty instrument resolutions.
>
> In what way is it "similar"? Various ways of doing discovery have been done for over 30 years.
>
> --Paul Hoffman