Hello, --- Scott Allan <[EMAIL PROTECTED]> wrote: > Regardless, it is clear to us that this was not a good judgement > call, and > that we had to do what we could to immediately stop it until we had > more > clearly communicated with our resellers. This was a mistake, and we
Thank you for acknowledging our concerns. I appreciate that you're rethinking things. As for suggestions and feedback, I'd like to reiterate that, in my view, OpenSRS should be openly deleting all "internal" expired names into the pool so that they can be registered by any other registrar. (by "openly", this is meant to prevent insiders from doing deletions at pre-arranged times, to effect a transfer to a specific party). OpenSRS names should go into the 2 pm batch drop. As for "external" expired names, I would hope that OpenSRS would repeat and lobby for its position that was made public in their document at: http://www.byte.org/rc-deletes/ namely that NSI and all other registrars (Register.com included) have an *obligation* to delete expired names in a timely manner at the 2 pm batch drops. Hopefully this is a 'grey area' that can be totally made clear via directives at ICANN. NSI seems to drop names whenever they please, and this should be disallowed too. As for possibilities to create OpenSRS services to go after expired names, as long as all names are going into the delete cycle, OpenSRS should be free to go after names just like other registrars do. A SnapNames or NameWinner-style solution would be fine by me, although there are other business models too. This would let OpenSRS increase the odds of its customers who wish to go after expired names, and make some extra money when it succeeds in catching them. Once again, thanks for listening to our concerns. Sincerely, George Kirikos http://www.kirikos.com/ __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com
