<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] PIR's RRP implementation
eNom can confirm the incompatability with Verisign's implementation of the
spec.
These (below) are not the only changes, I suspect.
These differences would affect all registrar's systems.
It could create legal problems for us (unable to renew names that are on
hold for example)
unless all registrars change their client code.
I mentioned this as a potential problem on this list and directly to Ram at
Afilias in Shanghai.
I suggest PIR run commands against Verisign's production system in .com and
compare
the output to running the same commands against Afilias's RRP system,
then report to the list with all the differences so we can at least modify
our client code.
It would be better if Afilias just made their verision of RRP the *exact*
same as Verisign's.
Paul
-----Original Message-----
From: Mike Lampson [mailto:lampson@iaregistry.com]
Sent: Tuesday, January 28, 2003 10:48 AM
To: registrars@dnso.org
Subject: [registrars] PIR's RRP implementation
All:
Is anyone else but me having trouble communicating to PIR that their RRP
implementation is not compatible with VeriSign and that this is
unacceptable? Their tech support staff have a tendency to quote the error
code definitions from RFC 2832 which is completely unhelpful.
The latest issue is that "renew" will not work if a domain is on
REGISTRAR-LOCK or REGISTRAR-HOLD. (See RRP log below.)
In addition, they will not allow us to add REGISTRAR-HOLD to a domain that
already has REGISTRAR-LOCK. Again, this is incompatible with VeriSign's RRP
implementation.
Mike Lampson
The Registry at Info Avenue, LLC
lampson@iaregistry.com
>12:13:42 - - RRP client: status<crlf>
>12:13:42 - - RRP client: EntityName:Domain<crlf>
>12:13:42 - - RRP client: DomainName:XXXXXXXXXXXX.ORG<crlf>
>12:13:42 - - RRP client: .<crlf>
>12:13:42 - - RRP server: 200 Command completed successfully<crlf>
>12:13:42 - - RRP server: created by:xxxx-YY<crlf>
>12:13:42 - - RRP server: created date:2001-02-01 00:50:22<crlf>
>12:13:42 - - RRP server: nameserver:dns2.compeng.net<crlf>
>12:13:42 - - RRP server: nameserver:dns1.compeng.net<crlf>
>12:13:42 - - RRP server: registrar:xxxx-YY<crlf>
>12:13:42 - - RRP server: registration expiration date:2003-02-01
00:50:22<crlf>
>12:13:42 - - RRP server: status:REGISTRAR-LOCK<crlf>
>12:13:42 - - RRP server: updated by:xxxx-YY<crlf>
>12:13:42 - - RRP server: updated date:2002-04-19 20:04:01<crlf>
>12:13:42 - - RRP client: renew<crlf>
>12:13:42 - - RRP client: EntityName:Domain<crlf>
>12:13:42 - - RRP client: -Period:1<crlf>
>12:13:42 - - RRP client: -CurrentExpirationYear:2003<crlf>
>12:13:42 - - RRP client: DomainName:XXXXXXXXXXXX.ORG<crlf>
>12:13:42 - - RRP client: .<crlf>
>12:13:43 - - RRP server: 552 Domain status does not allow for
operation<crlf>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|