Re: [Crisp] RFC 5144 up and running
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Crisp] RFC 5144 up and running



Andrew Newton <andy at 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 at ietf.org
https://www.ietf.org/mailman/listinfo/crisp



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.