Re: [Crisp] Questions re adoption and future of IRIS protocol and IRIS dependent services

Sven-Holger Wabnitz <wabnitz@digital-security.com> Tue, 29 January 2008 15:48 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 1JJsh5-00070Z-Gk; Tue, 29 Jan 2008 10:48:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJsh4-0006vz-4B for crisp@ietf.org; Tue, 29 Jan 2008 10:48:14 -0500
Received: from mail.net-design.net ([81.173.201.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJsh2-0003AE-9T for crisp@ietf.org; Tue, 29 Jan 2008 10:48:14 -0500
Received: from backup ([172.29.100.129]) [81.173.201.225] by mail.net-design.net with asmtp (Exim 3.36 #1 (Debian)) id 1JJsgy-0006Qf-00; Tue, 29 Jan 2008 16:48:08 +0100
Message-ID: <479F4A7C.1040002@digital-security.com>
Date: Tue, 29 Jan 2008 16:47:08 +0100
From: Sven-Holger Wabnitz <wabnitz@digital-security.com>
Organization: DSS GmbH
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: ctaswell@telegenetics.net
Subject: Re: [Crisp] Questions re adoption and future of IRIS protocol and IRIS dependent services
References: <01aa01c85ebc$6f3e36f0$4dbaa4d0$@net>
In-Reply-To: <01aa01c85ebc$6f3e36f0$4dbaa4d0$@net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: wabnitz@dominic.de
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

Carl,

Carl Taswell schrieb:
> Implementation of DCHK-type service implies use of IRIS Core (RFC 3981) and
> DREG (RFC 3982). Also, Sven-Holger Wabnitz reports that DomiNIC plans to
> offer IRIS service, but apparently, there is not yet any public announcement
> at their web site at
> 
> http://www.dominic.de/
> 
> since a search there returned no results, and standards implemented in the
> product description do not yet mention any of the IRIS protocols (unless I
> missed something).
> 
> GENERAL QUESTIONS:
> 
> 1) For those of you who have been active in the CRISP Working Group, do you
> remain optimistic, pessimistic, or neutral about the future of the IRIS
> protocol and services?

In general there is an optimistic future for IRIS because of the 
problem of parsing hundreds of different whois formats. However, 
every country has its own privacy protection rules so there might 
be some issues that need to be considered.

> 2) For those of you who are active at registrars, do you expect the rate of
> adoption of the IRIS-dependent services to accelerate or continue at the
> current pace?
> 
> SPECIFIC QUESTIONS:
> 
> 3) Marcos and Sven-Holger, could you please make more explicit the complete
> list of IRIS related RFC standards that your companies will be supporting
> with products or services?

We do not offer a service we offer an independent software 
product. So we claim the top position in terms of technology. 
That's our philosophy with the product DomiNIC. The fact that we 
want to support the interfaces of the major registries and 
registrars with the product indicates that we will support each 
IRIS standard in future.
We discuss also a version for registries with DomiNIC and an open 
source library which we will also use.


Best regards
Sven-Holger

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