Re: Lack of reference client Implementation for EPP 6 / TCP 4

[Daniel Manley <dmanley@tucows.com>]

Tucows has been pretty quiet lately on the SourceForge epp-rtk front. 
 Being the main Tucows developer on this project, I can explain this by 
me being occupied with some other non-domain/registry work.  The other 
main developers, Asbjorn and Vidar, who are from GNR (.name), have 
understandably been busy lately with the recent release of their live 
registry.  

In the past, we've released RTK versions as registries launch with new 
versions of EPP -- those have been .info, .biz and .name.  I see from 
Stuart's email that .coop is up to bat now, and I have also heard 
rumours of some ccTLDs launching with EPP 06/04.  So, we will start the 
development of the next release of the RTKs (Java and C++) for 06/04.

Dan

Hollenbeck, Scott wrote:

>>The new datagram format described in TCP-04 describes the new header,
>>however it is silent out how the record is terminated, however
>>epp-rtk-java expects a <CR><NL> terminator.
>>    
>>
>
>Seems like a bogus requirement to me because as far as I can tell the specs
>are quite clear.  Section 3 of the TCP draft notes that the record is
>terminated with a </epp> element, and Section 4 of the TCP draft says that
>the record contains "the EPP XML instance".  Section 2.1 of the core draft
>also describes the start and end elements.  There's no mention of a <CR><NL>
>terminator anywhere.
>
>Anyway, the idea of a reference implementation is a good one.  Someone just
>has to write, release, and maintain it.
>
>-Scott-
>  
>


-- 
Daniel Manley
Tucows, Inc.
Toronto, Canada
dmanley@tucows.com