IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Tue, 24 March 2020 00:22 UTC

Return-Path: <paul.hoffman@icann.org>
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 EAC4C3A0E05 for <add@ietfa.amsl.com>; Mon, 23 Mar 2020 17:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 M5a4ipEFMhgk for <add@ietfa.amsl.com>; Mon, 23 Mar 2020 17:22:58 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 7A1583A0DF3 for <add@ietf.org>; Mon, 23 Mar 2020 17:22:58 -0700 (PDT)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa5.dc.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 02O0MqHn027121 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 24 Mar 2020 00:22:53 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 23 Mar 2020 17:22:50 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1497.006; Mon, 23 Mar 2020 17:22:50 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Tony Rutkowski <rutkowski.tony@gmail.com>
CC: "add@ietf.org" <add@ietf.org>, Robert Kahn <rkahn@cnri.reston.va.us>
Thread-Topic: [Ext] [Add] antitrust implications of IETF resolver discovery protocol work
Thread-Index: AQHWAXGUokSZj8V82EOcIlJDJmWZUqhXVykA
Date: Tue, 24 Mar 2020 00:22:50 +0000
Message-ID: <485DA64D-BAF9-4A0D-8666-5A9CC8F8FE53@icann.org>
References: <a4a2d9aa-bf22-9bbf-365c-06b4a9ccde48@gmail.com>
In-Reply-To: <a4a2d9aa-bf22-9bbf-365c-06b4a9ccde48@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_D360CFDA-F495-4D2E-A95A-6702FEFC8086"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.645 definitions=2020-03-23_10:2020-03-23, 2020-03-23 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Amy2OsNwDqwBtoaVMjLLZh0ksEs>
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 00:23:00 -0000

On Mar 23, 2020, at 5:17 PM, Tony Rutkowski <rutkowski.tony@gmail.com> 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

v2.23.0 | Report a Bug | By Email