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

Marcos Sanz/Denic <sanz@denic.de> Mon, 28 January 2008 11:18 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 1JJS00-0007Cg-BC; Mon, 28 Jan 2008 06:18:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJRzz-0007Cb-9B for crisp@ietf.org; Mon, 28 Jan 2008 06:17:59 -0500
Received: from smtp.denic.de ([81.91.161.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJRzx-0005KS-NB for crisp@ietf.org; Mon, 28 Jan 2008 06:17:59 -0500
Received: from notes.rz.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp id 1JJRzw-0000oR-Rx; Mon, 28 Jan 2008 12:17:56 +0100
In-Reply-To: <01aa01c85ebc$6f3e36f0$4dbaa4d0$@net>
To: ctaswell@telegenetics.net
Subject: Re: [Crisp] Questions re adoption and future of IRIS protocol and IRIS dependent services
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
From: Marcos Sanz/Denic <sanz@denic.de>
Message-ID: <OF0EB78500.FE64481E-ONC12573DE.003CFAE7-C12573DE.003E0E55@notes.denic.de>
Date: Mon, 28 Jan 2008 12:17:50 +0100
X-MIMETrack: Serialize by Router on notes/Denic at 28.01.2008 12:17:56, Serialize complete at 28.01.2008 12:17:56
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: crisp@ietf.org
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

Carl,

> COMMERCIAL IMPLEMENTATIONS: Marcos Sanz reports that DENIC will make
> available

For the records this will be no "commercial" implementation. You can call 
it "closed" implementation, if you want.

> 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?

As I said, this is a DCHK implementation (RFC number not known yet) over 
LWZ transport (RFC 4993).

> This inquiry regards solely the status of RFC 3982 and the fact that the
> formal XML syntax for dreg1 does not validate. Specifically, XML 
validation
> checkers return errors that map to lines beginning with the element
> 'dreg:endsWith'.

RFC errata is to be reported as follows:
http://www.rfc-editor.org/how_to_report.html

Andy or I will gladly verify any errors in the schemata.

> (1) For active members of the CRISP WG, what is the current 
recommendation
> for use of a corrected revision for dreg?

Implement RFC 3982 plus verified errata.

Best regards,
Marcos

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