[DNSOP] whois: the protocol that can't be killed even though it must

Jim Reid <jim@rfc1035.com> Sun, 21 November 2010 22:55 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 869553A6AB4 for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 14:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOEEWUaSsKA0 for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 14:55:19 -0800 (PST)
Received: from hutch.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) by core3.amsl.com (Postfix) with ESMTP id 53F8A3A6A0F for <dnsop@ietf.org>; Sun, 21 Nov 2010 14:55:19 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jim) by hutch.rfc1035.com (Postfix) with ESMTPSA id C654415420A1; Sun, 21 Nov 2010 22:56:07 +0000 (GMT)
Message-Id: <68E21DFE-A5BF-46C9-BD5C-A211E4093795@rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
To: Patrik Fältström <patrik@frobbit.se>
In-Reply-To: <9F6A0D8D-95AF-4494-9BAB-E836377F6C8F@frobbit.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sun, 21 Nov 2010 22:56:07 +0000
References: <4ce93a4b3be59@circleid.com> <41856.1290360792@nsa.vix.com> <20101121174157.GA13950@shinkuro.com> <F9A9B3B6-934F-48EC-8CCA-3F32A77D0760@insensate.co.uk> <C8475C54-8EAF-48F4-B941-998FF94E9389@shinkuro.com> <9F6A0D8D-95AF-4494-9BAB-E836377F6C8F@frobbit.se>
X-Mailer: Apple Mail (2.936)
Cc: Andrew Sullivan <ajs@shinkuro.com>, "dnsop@ietf.org" <dnsop@ietf.org>, Lawrence Conroy <lconroy@insensate.co.uk>
Subject: [DNSOP] whois: the protocol that can't be killed even though it must
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Nov 2010 22:55:20 -0000

On 21 Nov 2010, at 22:20, Patrik Fältström wrote:

> Noone is asking strong enough to get correct data from the whois  
> service. Instead, ICANN is asking to have the whois protocol  
> available, and on top of that money is spent on anonymous  
> registration (2nd hand registration) etc.
>
> So as long as that is what people ask for, you will not see iris.

I'm not sure anyone is actually asking for the current horror story  
that is whois. We've just hit a stalemate in this trench warfare where  
no progress can ever be made because everyone has settled for the  
status quo: the least worst option that the majority of players will  
grudgingly accept.

>> That there's no uptake seems to me to be an indication that  
>> registries don't want additional costs.
>
> Registries do only implement what people ask for.

Or what they're compelled to implement. In theory ICANN could get  
every gTLD to use IRIS overnight by the stroke of a pen. It's just a  
teeny change to the registry contracts, right? :-)