jm wrote: > on 9/13/06 8:21 PM, Andrew McCallum at [EMAIL PROTECTED] wrote: > > >> This actually spawned an interesting discussion here today with Paul and >> others because of the recent migration of COM/NET from RRP to EPP. >> >> The old RRP expiration status of "REGISTRAR-HOLD" would also prevent >> transfers, but no so for domains on clientHold -- that's the job of >> another status called clientTransferPhohibited. So if a domain doesn't >> have clientTransferProhibited (or serverProhibited) then you can whisk >> it away. >> > > Hi Andrew, > > Who/what determines the status, clientHold & clientTransferPhohibited. > > Does this relate to locked domains? clientHold generally only appears when the domain expires (it's what takes it out of the zones) but can also pop up if someone lists one nameserver (don't think this applies to COM/NET yet) or if there's a Invalid WHOIS dispute raised against it. The clientTransferProhibited status is generally also paired with clientUpdateProhibited, and the two together are the equivalent of the "REGISTRAR-LOCK". The clientUpdateProhibited part prevents DNS changes, and for other EPP registries like INFO/BIZ will also prevent other contact/status changes. Essentially the only ones who apply the locks are Registrants, Resellers or Compliance.
Just a curiosity some may have seen: There's also clientDeleteProhibited, which _does not_ stop transfers, but it's more like a safety latch you have to remove before hurting yourself. - andrewm _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
