Verisign Responds to Wait List Criticism

spooge21 writes: "Verisign published new documents today regarding the proposed Domain Wait List service. The new documents include the revised VeriSign Domain Name Wait list Service Proposal, the VeriSign GRS Responses to Wait List Service Questions and the Wait List Service Justification Document."

Comments

What about improper deletion?

[www.sorehands.com]

I have seen many reports of Network solutions improperly deleting domain names. Then when someone else grabs it, Network solutions says, "Sorry, here is your registration fee back."

How will they correct this? Will they have an incentive to accidently lose registrations?

registration outage

[Perdo]

Un-scheduled domain registration outage. We have disabled the domain tool due to an un-scheduled outage of the .com/.net./org registry. At this time, we have isolated the source of the outage to the CNO registry operator. The expected length of this outage is unknown. We are closely monitoring this situation, and will continue to issue updates as new information becomes available. We apologize for any inconvenience this may cause you.

Shared Registry

[Perdo]

The original Shared Registry System Protocol (version 0.9) was developed by CORE together with Emergent, Inc. in the context of the creation of a registry system suitable for the registration of the anticipated seven new top level domains. Due to the political change, CORE was unable to start the registration of those domains. Instead, CORE got the opportunity to register COM, NET and ORG (CNO) domains via the registry spin-off of Network Solution Inc. As the infrastructure had already been set up and was working, CORE decided to extend the registry system instead of the development of a new system specific to CNO domains. The server system was extended to synchronize its database with NSIRegistry's via the Registry Registrar Protocol (RRP). The payload of the SRSP was modified to conform to the new needs. The development was performed by Computer Service Langenbach GmbH, and the SRSP got the version number 1.0.

This document describes the version 1.1 of the protocol, which is mostly a cosmetic update of the payload and does not introduce much new functionality.