IETF Logo Mail Archive

Re: [weirds] New Version Notification for draft-sheng-weirds-icann-rws-dnrd-01.txt

"John R. Levine" <johnl@iecc.com> Wed, 21 March 2012 18:16 UTC

Return-Path: <johnl@iecc.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 E90EF21E809D for <weirds@ietfa.amsl.com>; Wed, 21 Mar 2012 11:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level:
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 esGQc4prbkuf for <weirds@ietfa.amsl.com>; Wed, 21 Mar 2012 11:16:29 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE6121E8097 for <weirds@ietf.org>; Wed, 21 Mar 2012 11:16:29 -0700 (PDT)
Received: (qmail 58669 invoked from network); 21 Mar 2012 18:16:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=e52c.4f6a1afb.k1203; bh=bExFB8OJe+x8Nwjtezn2d0nwNhZyiK77DNvm7+S9Peg=; b=Sq9G2zX24n7n0wIxrCVZQvIIfDBHWhmjS8zLLHi6ddaTzIXIUDokGCN6mi+GQxIKCARfUdRYzQsiAQfauwcUnNIaCbuyD1ikSZu4cpiP+6SIc6fYx3UOumgnIGdByN0OazHMvmS2y2tUzVITu140QisAhps5PTfzQtupewja2Rc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 21 Mar 2012 18:16:05 -0000
Date: Wed, 21 Mar 2012 19:16:21 +0100
Message-ID: <alpine.BSF.2.00.1203211904310.2294@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: Francisco Obispo <fobispo@isc.org>
In-Reply-To: <0A5D71D7-73D3-4736-8FEC-D0252B1263C0@isc.org>
References: <20120321084728.13258.qmail@joyce.lan> <A0D1B000-BF94-4ABC-9187-100FF6FD035B@isc.org> <9CE1C82A-3EED-47EA-B39B-E2EC1D660598@lacnic.net> <0A5D71D7-73D3-4736-8FEC-D0252B1263C0@isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-343745351-1332353787=:2294"
Cc: weirds@ietf.org
Subject: Re: [weirds] New Version Notification for draft-sheng-weirds-icann-rws-dnrd-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: Wed, 21 Mar 2012 18:16:30 -0000

> The only difference with XML and JSON validation, is that for the latter, you have to do the checks by hand…

If that's the only way you know to validate results, OK, but my plan is to 
write test harnesses to debug the results, like I do for all my other 
client server stuff, regardless of what the encoding is.

> But the beauty of RESTful, is the fact that we can have multiple 
> response formats coexisting.

It's hard to imagine that the IESG would ever accept something with 
multiple response formats, so there's no need to argue about this.

R's,
John

v2.23.0 | Report a Bug | By Email