Re: [weirds] FW: I-D Action: draft-hollenbeck-dnrd-ap-query-01.txt

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 08 May 2012 13:57 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB0E21F8609 for <weirds@ietfa.amsl.com>; Tue, 8 May 2012 06:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.625
X-Spam-Level:
X-Spam-Status: No, score=-2.625 tagged_above=-999 required=5 tests=[AWL=-0.026, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OE3dCqx+hEnT for <weirds@ietfa.amsl.com>; Tue, 8 May 2012 06:57:51 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id BA8AB21F8607 for <weirds@ietf.org>; Tue, 8 May 2012 06:57:51 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id F2C151ECB41D for <weirds@ietf.org>; Tue, 8 May 2012 13:57:50 +0000 (UTC)
Date: Tue, 08 May 2012 09:57:52 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120508135747.GC10226@mail.yitter.info>
References: <831693C2CDA2E849A7D7A712B24E257F0D5F9630@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <CAJbypPq85Lsc9NQ9bAimTfG2veQUU96SL6s8-D-e09BA_DGbdQ@mail.gmail.com> <4FA8F60F.9090204@centralnic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4FA8F60F.9090204@centralnic.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] FW: I-D Action: draft-hollenbeck-dnrd-ap-query-01.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 13:57:52 -0000

On Tue, May 08, 2012 at 11:31:43AM +0100, Gavin Brown wrote:
> Supporting text/plain provides a migration path in the early stages of
> deployment: clients can be updated to use the new transport protocol
> without also having to also support the new format.

The early arguments in favour of XML, however, were that many browsers
could render it easily.  And anyway, that still seems like a weak
reason.

If you need to support legacy clients, then you'll need to have a
straight whois server because the legacy clients won't know about the
new transport.   Who will go to the work of updating their client to
use the new transport without doing the additional work to get the
benefits of a structured format?  The new transport provides zero
benefit to the client.  It's only the structured data that provides
benefit to the client, so if they're going to update that's what
they're going to want, it seems to me.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com