Just to clarify all this for you David.
The request is made, and an email is sent to the current admin
contact.
The default is a nack at this point, and unless the Admin contact
explictly approves it, the transfer will not go through.
That's why this is basically a none issue.
This is different from a "losing registrar" notification, where the
default is ack unless it is blocked.
Tuesday, Tuesday, August 14, 2001, 7:07:08 AM, Charles Daminato wrote:
> David...
RSP->>RSP transfer works exactly the same as a regular transfer.
> Notification is sent to the current Administrative contact for
> authorization, but also to the losing and gaining RSP gets an email ONLY if
> they have this configured. Transfers TO an RSP happen when the Admin
> approves (or when transfer times out), Transfers FROM an RSP happen as soon
> as the request is made, and when the Admin accepts/rejects the transfer.
> All these are "on/off" (default is off).
> Losing RSP has no role, just gets notification (you'd like to know when a
> customer leaves so you can stop bugging them, or find out what went wrong,
> or even sue them for the billions they still owe you).
> So:
> Order comes in. Email goes to Admin (optionally losing RSP). Admin
> approves/rejects.
> Approves: Optional messages to gaining and losing RSPs
> Rejects: Optional messages to gaining and losing RSPs
> If the order times out, email goes to order maker, and optionally gaining
> RSP.
> Tada!
> Charles Daminato
> OpenSRS Product Manager
> Tucows Inc. - [EMAIL PROTECTED]
>> -----Original Message-----
>> From: David Harris [mailto:[EMAIL PROTECTED]]
>> Sent: August 14, 2001 9:57 AM
>> To: Charles Daminato; Loren Stocker
>> Cc: [EMAIL PROTECTED]
>> Subject: RE: Transfer Fraud: Who are these losers!!!!
>>
>>
>>
>> Charles Daminato wrote:
>> > I've read the comments on this thread and will be discussing this
>> > internally to see what will be done. Please expect something today or
>> > tomorrow from myself or our Compliance department.
>>
>> Chuck,
>>
>> Could you also please post to the list the actual steps and authorizations
>> required for an RSP <-> RSP transfer?
>>
>> >From what I understand of this thread, it appears that RSP's are getting
>> notified of RSP<->RSP transfer requests that didn't come from the domain
>> name owner. I also understand that OpenSRS is sending an approval
>> e-mail to
>> the administrative e-mail contact. So, perhaps I'm not understanding
>> something here.. I would expect that OpenSRS would require the transfer to
>> be approved by the administrative e-mail contact before doing *ANYTHING*,
>> since until the transfer is approved it's not known to be valid.
>> Perhaps the
>> problem is simply that you are notifying RSP's before you have received
>> approval from the administrative e-mail contact.
>>
>> I don't think any RSP's (either gaining or loosing) want to have
>> any role in
>> the authentication process. It's too messy to implement and
>> leaves room for
>> abuse or negligence or mistakes. The authentication process should be
>> totally implemented by and internal to OpenSRS, just as with
>> registrar<->registrar transfers.
>>
>> But then, since I don't know the exact details of the transfer
>> process (and
>> it appears to be somewhat different than the registrar<->registrar
>> transfers), I'd appreciate your posting the actual steps and
>> authorizations
>> required for an RSP<->RSP transfer to get everyone on the same page. This
>> should lead to some more insightful discussion and recommendations on the
>> list
>>
>> Thank you!
>>
>> David
>>
>>
>>
--
Best regards,
William X Walsh <[EMAIL PROTECTED]>
Userfriendly.com Domains
The most advanced domain lookup tool on the net
DNS Services from $1.65/mo
