[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: <ietf-provreg@cafax.se>
From: "Stuart Marsden" <Stuart.Marsden@poptel.net>
Date: Tue, 6 Aug 2002 17:29:59 +0100
Importance: Normal
In-Reply-To: <8A14612718D5314D8B5DC4BEA17FCE4C05A010@alice.etal>
Sender: owner-ietf-provreg@cafax.se
Subject: Lack of reference client Implementation for EPP 6 / TCP 4

Hi,

Following my posting at the weekend and the lack of a concrete response,
I am concerned that not keeping a client reference implementation for
the current EPP spec available is going to cause problems in the short /
medium term.

My concern is two fold, 

1st it is going to make problem resolution harder in the long run as
registries / registrars up spec and compatibility problems arise.

2nd it helps identify any omissions in the specification. 

I can give a concrete example of the 2nd pt.

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.

I can imagine how EPP implementation politics would act against having a
single reference implementation, however I do believe now all the macho
froth is going / has gone out of the registry business it would be worth
looking at ways to address this.

I guess I feel strongly enough about it, that if necessary dot coop will
do it, otherwise I have nothing to bolt my verification extensions to.

Stuart


Home | Date list | Subject list