>
> Is ICANN actually going to come up with a set of guidelines
> . ?
Yes - the report has some guidelines.
The plan is to make these guidelines easily available to suppliers that
provide domain name services.
Making them enforceable will take longer, and will be done if the
guidelines
This usually takes 5 days, although a losing reigstrar can
explicitly confirm a transfer.
>
> I also would like to confirm who is responsible for denying
> transfer request if LOCK is present.
The registry does this.
Regards,
Bruce Tonkin
Hello Mark,
> That's what happened last weekend: Martin Hannigan and I got
> the ball rolling on Sunday morning about 1000 EST. Our 24x7
> customer service department contacted Dotster and Melbourne
> IT. Melbourne IT changed the panix.com name servers back to
> their original settings and
> >
> > Accountability. Responsibility.
>
> I agree with you on this 100%. ICANN needs to enforce there
> current policies.
I agree too.
> Look at totalnic/pacnames. They have been
> refusing transfer requests years now until very very recent.
> What has ICANN done about all those co
Hello William,
>
> We know how to do 3-way handshakes. Rather a fundamental of
> the Internet. So quickly folks forget
>
> We knew in advance that the VRSN/NetSol/whatever protocol was
> terrible, and that the ICANN policy change was not going to
> be helpful.
The ICANN policy change
> However, that still looks to me like "Users can only ask that
> domains be locked." Unless you are claiming that users can
> send the lock request directly to the registry, and monitor
> its status.
Only a registrar can send commands directly the registry.
Different registrars offer dif
When a registrar sends a transfer request to the registry operator (and
the name is not on Registrar LOCK), the registry operator sends a
confirmation email to both the losing and gaining registrar.
Here is the copy of the email Melbourne IT received.
Regards,
Bruce Tonkin
From [EMAIL
Hello William,
>
> Stop blaming the victim! Stop blaming anybody else.
>
I at no stage have blamed the victim. In fact I am sincerely sorry for
the damage caused to panix.com.
The transfer should NEVER have been initiated. Melbourne IT has
consistently acknowledged the error.
I have ho
The information we have so far, indicates that it was not on Registrar
LOCK at the registry at the time of the transfer.
Regards,
Bruce Tonkin
Hello John,
>
> It appears that "REGISTRAR LOCK" has interesting
> per-registrar implementation variations which do not always
> put the domain holder's interests first. While the registry
> does not, per se, have a direct business interest with the
> domain holder, it should be possible to
Hello Thor,
> >
> > (5) The registry will send a message to the losing registrar
> > confirming that a transfer has been initiated.
>
> Can you confirm or deny whether this actually happened in the
> case of the panix.com transfer?
I don't have any direct visibility over this.
I have asked V
Hello William,
Thanks for your suggestions.
Comments below.
>
> I would propose the following:
>
> 1. Keep existing model but make it "SHOULD" for old registrar
> to inform
>of upcoming transfer (I still don't understand how that failed in
>panix.com case BTW, because I'm pretty cer
Hello Eric,
Thanks for your descriptions from an operator and web-hosting company
perspective.
Essentially different customers have different needs. Some that value
price higher than reliability/security are likely to want to easily move
names around depending on renewal prices and the prices o
Hello Brandon,
Thanks for your feedback.
>
> My experience has been that getting auth_info (which criminal
> staff would have access to) from bad registrars is almost
> impossible, with registrar-LOCK too they have enough control
> to negate the gain in being able to pull a domain to a new
Hello Alexei,
>
> Problem - you are talking about changing registrar, but in
> reality you describe changing of domain owner.
Yes you are right in that often a number of domain name variables change
at around the same time.
>
> Why (what for) is it allowed to transfer from one registrar
>
s are
available for all registrars at the registry.
I am interested to hear what members of the NANOG list believe would be
a better transfers process.
Regards,
Bruce Tonkin
is unrelated to a lock that can be placed on the name in
the registry.
Note that different registries have different locking mechanisms.
Regards,
Bruce Tonkin
Hello All,
>
> Melbourne IT restored the nameservers and contact details
> associated with this name first thing this morning (Monday in
> Melbourne, Australia).
>
> We are arranging with the previous registrar (Dotster) to
> have the name transferred back.
As an update, the transfer back
er of external
people have access to the right contacts at Melbourne IT to fast track
serious issues.
Regards,
Bruce Tonkin
Chief Technology Officer
Melbourne IT
led to the problem in
the first place. This will take longer, due to the various timezones
and parties involved. In this case one of the parties was an ISP in the
United Kingdom, which is a reseller of Melbourne IT.
Regards,
Bruce Tonkin
Chief Technology Officer
Melbourne IT
20 matches
Mail list logo