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

Jim Reid <jim@rfc1035.com> Tue, 24 March 2020 11:54 UTC

Return-Path: <jim@rfc1035.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 CBBA83A0801 for <add@ietfa.amsl.com>; Tue, 24 Mar 2020 04:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level:
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 OYYQcklhuLgc for <add@ietfa.amsl.com>; Tue, 24 Mar 2020 04:54:31 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16AA93A02C1 for <add@ietf.org>; Tue, 24 Mar 2020 04:54:30 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id E9B0024205EA; Tue, 24 Mar 2020 11:54:27 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <a4a2d9aa-bf22-9bbf-365c-06b4a9ccde48@gmail.com>
Date: Tue, 24 Mar 2020 11:54:26 +0000
Cc: add@ietf.org, Robert Kahn <rkahn@cnri.reston.va.us>
Content-Transfer-Encoding: quoted-printable
Message-Id: <67093D18-A0C1-4068-AA54-977F4AD23BC9@rfc1035.com>
References: <a4a2d9aa-bf22-9bbf-365c-06b4a9ccde48@gmail.com>
To: Tony Rutkowski <rutkowski.tony@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Qi40s71-rt2KCIcuqorngIswJ-o>
Subject: Re: [Add] 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:54:33 -0000


> On 24 Mar 2020, at 00:17, 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?

Can you explain why you think there might be anti-trust implications?

> 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.

How? The ADD WG hasn’t even met yet or adopted any documents as WG drafts. So it’s hard to see how there is any basis for your claim.