ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

[gnso-irtp-b-jun09] Transcript excerpt

  • To: "Gnso-irtp-b-jun09@xxxxxxxxx" <Gnso-irtp-b-jun09@xxxxxxxxx>
  • Subject: [gnso-irtp-b-jun09] Transcript excerpt
  • From: Marika Konings <marika.konings@xxxxxxxxx>
  • Date: Mon, 29 Mar 2010 03:06:07 -0700

Dear All,

As discussed on last week’s meeting, please find below the relevant parts of 
the transcript relating to Scott’s overview of EPP in relation to lock status. 
To view the complete transcript, please see 

With best regards,



The one related to locking though there are eight, four of which are managed by 
clients which you can translate to mean registrars and four of which are 
managed by the server which you can translate to mean a registry. There's one 
locking status or I'm sorry, two, one for the registrar, one for the registry 
for each of the four transform commands or the commands that can manipulate the 
state of an object. In this case we're talking about a domain name. There are 
transfer prohibited status values, update prohibited status values, renew 
prohibited status values and delete prohibited status values. Depending on 
which of the two parties sets one if the domain is in any one of those states 
the transform operation identified by the command in the status value will be 

So for example if a registrar wants to offer a service that, you know, can be 
used to prevent transfers they can set the transfer prohibited - I'm sorry the 
client transfer prohibited status value and request to transfer the domain will 
be rejected.
Similarly the registry operator can set any one of the four status values to 
prevent (unintelligible) transfer operations from happening. And they can do 
that as part of a value-added service or they can do it for nonpayment or for 
whatever reason their policy deems to be appropriate. Okay there are other 
status values that describe the current state of a domain such as Okay. The 
Okay status is meant to mean that there is nothing - there are no locked values 
and no other status values set.

The other status values are - Client delete prohibited, service delete 
prohibited, client hold server hold, client renew prohibited, server renew 
prohibited, client transfer prohibited, server transfer prohibited, client 
update prohibited, server update prohibited, inactive, okay, pending create, 
pending delete, pending renew, pending transfer, pending update.

...talking about the pending values. Those all exist because there are some 
registry business policies that will allow a client to request one of those 
operations like a renew but for whatever reason the renew does not take effect 
when the command is completed on the server.

So the protocol includes a status value to let you know that a command has been 
received and processed successfully but the actual action has not yet been 
fully implemented.

So those are the pending values. Inactive, it basically means the domain exists 
in the database but does not exist in the zone. This can sometimes happen where 
a domain is registered initially but again for example the registry might have 
to take some out of band authentication steps to determine if a registrant or a 
registrar is authorized to register the name. And for whatever reason it's 
reserved as it cannot be registered by someone else but it has not yet been 
published in the zone.

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy