>-----Original Message-----
>From: Jim Archer [mailto:jim@archer.net]
>Sent: Wednesday, May 02, 2001 12:08 AM
>To: Hollenbeck, Scott; rrp@verisign-grs.com
>Subject: Another RRP test server bug...
>
>
>Hi Scott...
>
>I think I found another RRP test server bug in the 1.1.0a
>toolkit. Again, I
>verified this behavior using a SSH client and typing the
>commands manually.
>
>When using the CHECK command, I do this:
>
>CHECK
>ENTITYNAME:DOMAIN
>DOMAINNAME:ARCHER^INVALID.COM
>.
>
>The server returns:
>
>505 Invalid attribute value syntax
>
>The spec on page 26 if RFC 2832 v 1.1.0 says it should be a 541 for an
>invalid domain name. I can make it return 541 like this:
>
>CHECK
>ENTITYNAME:DOMAIN
>DOMAINNAME:ARCHER^INVALID
>.
>
>Note the lack of the .COM after the domain name. It seems this should
>return 505 for invalid command attribute syntax.
>
>Is this a bug, or does the actual registry do this? Maybe its
>an error in the RFC? My error?
Your error -- "ARCHER^INVALID.COM" is syntactically invalid because of the
"^", but it's structurally a valid domain name for the server because it
consists of two labels of proper length and one of them is "COM". Yes, our
registry implementation deals with these errors in the same way.
<Scott/>
---------
See http://www.verisign-grs.net/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Wed May 02 2001 - 07:09:21 EDT