Re: [Crisp] RFC 5144 up and running

Patrick Mevzek <crisp@contact.dotandco.com> Tue, 14 October 2008 16:22 UTC

Return-Path: <crisp-bounces@ietf.org>
X-Original-To: crisp-archive@megatron.ietf.org
Delivered-To: ietfarch-crisp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EA283A68F7; Tue, 14 Oct 2008 09:22:47 -0700 (PDT)
X-Original-To: crisp@core3.amsl.com
Delivered-To: crisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 308463A68F7 for <crisp@core3.amsl.com>; Tue, 14 Oct 2008 09:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPrKSU1eQfup for <crisp@core3.amsl.com>; Tue, 14 Oct 2008 09:22:42 -0700 (PDT)
Received: from triglav.dotandco.com (triglav.dotandco.com [194.242.114.22]) by core3.amsl.com (Postfix) with ESMTP id E4BD93A659A for <crisp@ietf.org>; Tue, 14 Oct 2008 09:22:41 -0700 (PDT)
Received: from triglav.dotandco.com (localhost.localdomain [127.0.0.1]) by triglav.dotandco.com (8.13.8/8.13.8/Debian-3) with ESMTP id m9EGLKdW001004; Tue, 14 Oct 2008 18:21:20 +0200
Received: from localhost (localhost [[UNIX: localhost]]) by triglav.dotandco.com (8.13.8/8.13.8/Submit) id m9EGLHK5001003; Tue, 14 Oct 2008 18:21:17 +0200
X-Authentication-Warning: triglav.dotandco.com: patrick set sender to crisp@contact.dotandco.com using -f
Date: Tue, 14 Oct 2008 18:21:17 +0200
From: Patrick Mevzek <crisp@contact.dotandco.com>
To: Andrew Newton <andy@hxr.us>
Message-ID: <20081014162117.GC5965@home.patoche.org>
References: <OFD3A7721E.F67C1163-ONC12574CF.005904F1-C12574CF.00592811@notes.denic.de> <20081011144833.GF6222@home.patoche.org> <A86BF374-0AC5-4C71-8730-DDEF276F7C3C@hxr.us> <20081014134933.GA5965@home.patoche.org> <F3ED1FD6-8A02-458D-B8AC-28EA218ADC74@hxr.us>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <F3ED1FD6-8A02-458D-B8AC-28EA218ADC74@hxr.us>
Organization: Dot And Co
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-3.0 (triglav.dotandco.com [127.0.0.1]); Tue, 14 Oct 2008 18:21:20 +0200 (CEST)
Cc: crisp@ietf.org
Subject: Re: [Crisp] RFC 5144 up and running
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/crisp>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

Andrew Newton <andy@hxr.us>; 2008-10-14 16:15
> >Nothing planned yet as noone asked for it currently, but extending my
> >toolkit is always something that I'm interested to.
> >However this would be probably not a trivial amount of energy,
> >especially because of the BEEP transport, so this would probably not
> >happen in a near future except if somehow a huge demand arises and/or
> >some registries or other parties is willing to fund this development.
> 
> BEEP is deprecated in preference to XPC (RFC 4992).

Ok, yes I've overlooked that, sorry I'm quite new to CRISP (being
just a longtime lurker). Even better then, as I was never very
comfortable with BEEP (which was also envisioned in the past for EPP,
but dropped).

> I'd be interested  
> to hear your opinion regarding the amount of effort you believe it  
> would take to implement it.

After a quick glance, indeed the XPC part seems a bigger piece than
Areg, but of course it would be useful for many registry types, so
it's a good investment.

For my toolkit, like for LWZ/DCHK I'm not aiming at the beginning for
a full implementation but just the basis to make it interoperable, and
then later on extending it based on feedback and real world usage.
I would say something like one week of work, maybe less if there is
some server I can use to make tests (even with fake data) and people
that can help me and answer my silly questions :-)
But I would not be able to start working on that before ICANN Caïro,
so not before middle of November.

If anyone is interested to help, please let me know here or in
private (my From address is correct asis)

-- 
Patrick Mevzek
Dot and Co <http://www.dotandco.com/> <http://www.dotandco.net/>
_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www.ietf.org/mailman/listinfo/crisp