Re: [Crisp] Questions re current status of IRIS schemas and IRIS clients and servers

Andrei Robachevsky <andrei@ripe.net> Thu, 24 January 2008 13:53 UTC

Return-path: <crisp-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI2WK-0003Vz-0H; Thu, 24 Jan 2008 08:53:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI2WI-0003Vq-Mh for crisp@ietf.org; Thu, 24 Jan 2008 08:53:30 -0500
Received: from postboy.ripe.net ([193.0.19.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI2WG-00059K-U7 for crisp@ietf.org; Thu, 24 Jan 2008 08:53:30 -0500
Received: by postboy.ripe.net (Postfix, from userid 4008) id B54956A1D9; Thu, 24 Jan 2008 14:53:27 +0100 (CET)
Received: from herring.ripe.net (herring.ripe.net [193.0.1.203]) by postboy.ripe.net (Postfix) with ESMTP id AED466A264; Thu, 24 Jan 2008 14:50:24 +0100 (CET)
Received: from guest-wv-19.ripe.net (gw.office.nsrp.ripe.net [193.0.1.126]) by herring.ripe.net (Postfix) with ESMTP id 8D56C2F583; Thu, 24 Jan 2008 14:50:24 +0100 (CET)
Message-ID: <4798970C.2030805@ripe.net>
Date: Thu, 24 Jan 2008 14:47:56 +0100
From: Andrei Robachevsky <andrei@ripe.net>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: ctaswell@telegenetics.net
Subject: Re: [Crisp] Questions re current status of IRIS schemas and IRIS clients and servers
References: <001c01c85d25$7a5e4270$6f1ac750$@net>
In-Reply-To: <001c01c85d25$7a5e4270$6f1ac750$@net>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level:
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.126328 / -4.4
X-RIPE-Signature: c9a621cbdc86fce33dadcb5dd3b0b599
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: crisp@ietf.org, andy@hxr.us, iris@lists.verisignlabs.com, 'David Blacka' <davidb@verisign.com>
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Errors-To: crisp-bounces@ietf.org

Hi Carl,

Carl Taswell wrote on 22-01-2008 19:34:
> I'm beginning implementation work on a project originally designed to be
> built using IRIS. But I understand from David Blacka at Verisign that the
> IRIS client server prototypes implemented and hosted at Verisign Labs are no
> longer supported. I am left wondering whether there are any active projects
> currently underway for development of IRIS clients and servers, either open
> source, academic university, or commercial at any organization. 
> 

A few years ago we at the RIPE NCC set up a prototype of the IRIS 
server, based on VeriSign code. It provides live allocation data from 
the RIPE Database. There was a client developed, you may find some more 
information here:

http://www.ripe.net/db/iris-pilot/

The project is not active. At the moment there is little interest from 
the community and we are not doing any further development in this area.

Andrei


> I would appreciate hearing word from anybody about currently supported
> active projects of any kind for the implementation of IRIS clients and
> servers. Also, I would like to know if anybody has written a Microsoft WCF
> binding for any of the IRIS transport protocols so that they can be accessed
> in software development projects using Microsoft Visual Studio?
> 
> Finally, I have a number of questions regarding the IRIS *.xsd schemas
> themselves of which the two most important are:
> 
> 1) dreg.xsd refers to dreg2 but I am unclear about the status of dreg2
> because I know that at one time it was a draft, but it does not appear to
> have progressed to an RFC. Could somebody please clarify any plans for
> dreg2?
> 
> 2) There appears to be a fair amount of code common to more than one schema
> such as the code concerning contacts in both areg.xsd and dreg.xsd. Was
> there an explicit reason for this structure? Has there been any discussion
> of refactoring the code to improve modularity so that the various registry
> types (areg, dreg, etc) refer to the same separate schema that concerns
> items such as contacts that are common to all the different registry types?
> 
> Thanks much for any information,
> 
> CT
> 
> -------------------------
> Carl Taswell
> Cel: 916-616-4939
> Tel: 949-481-3121
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Crisp mailing list
> Crisp@ietf.org
> https://www1.ietf.org/mailman/listinfo/crisp

_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp