Registry Lock Extension for the Extensible Provisioning Protocol (EPP)

Introduction A registry lock secures a domain from any unauthorized changes to it on the registry level as opposed to the registrar level. It is targeted primarily at high value, business critical domains, where holders value the benefits of the increased security of business-critical domains over the risks of unauthorized or unwanted changes to their domains. This document describes an EPP extension to the domain object mapping () that allows a sponsoring client to manage registry locked domains automatically.

Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. In this document's examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in these examples are provided only to illustrate element relationships and are not required features of this protocol.

Registry Lock Many registries provide registrants for a way to add protection to their domains by locking them at the registry level. By locking a domain a registrant ensures that any changes (except for renewing the domain) are verified by the registry before going into effect. As of yet there have been no standardized process for for a registry lock and registries that provide it have come up with different processes, most including some level of manual intervention. While a domain that has registry lock enabled on it needs authorization for any changes made to it a registry MAY allow changes bypassing the authorization via automated DNSSEC provisioning, for example using a CDSS/CSYNC scanner. The removal of a registry lock is a manual, operational procedure and is not coveredd in this specification. In this document, we define an EPP extension that enables registries and registrars to further automate the registry lock process.

Registry Lock Contact A registry lock contact is a contact connected to a domain object that is able to authorize changes to the object. A domain MAY have multiple registry lock contacts, in which case changes MAY need to be authorized by multiple registry lock contacts. A server MAY restrict the maximum number of registry lock contacts connected to a domain.

Status Values for Locked Domains Once a registry lock has been applied on a domain object the object MUST have the serverDeleteProhibited status value set on it. While a transform request is pending authorization, the serverPendingUpdate status MUST be set on the domain.

Adding a registry lock to a domain When a registry lock is set on a domain a server MUST respond with a result code oc 1001 as defined in section 3 of . A server must then await for authorization as set out by the registry lock contact parameters provided. If the command is authorized within the specified deadline a server MUST send a poll message indicating the successfull transform. Example poll message indicating success:

S: S: S: S: S: Command completed successfully; ack to dequeue S: S: S: S: 2013-10-22T14:25:57.0Z S: Setting registry lock on domain succeeded. S: S: S: S: example.com S: update S: 12345-XYZ S: S: S: rl01 S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: ]]> If a transform is not authorized within the deadline a server MUST send a poll message indicating the failure of the transform. Example poll message indicating failure:

S: S: S: S: S: Command completed successfully; ack to dequeue S: S: S: S: 2013-10-22T14:25:57.0Z S: Update of locked domain failed. S: S: S: S: example.com S: update S: 12345-XYZ S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: ]]>

Handling changes to an associated contact object Updates to a contact object that is associated as a registry lock contact for a domain object MUST be rejected. If an update command for a contact object associated with a locked domain is processed successfully, a server MUST respond with a result code of 2305 as defined in section 3 of .

Handling changes to a locked domain If an update command for a locked domain is processed successfully, a server MUST respond with a result code of 1001 as defined in section 3 of , to indicate that the transform is awaiting authorization to be completed. If a transform command is authorized within the specified deadline a server MUST send a poll message indicating the successfull transform. Example poll message indicating success:

S: S: S: S: S: Command completed successfully; ack to dequeue S: S: S: S: 2013-10-22T14:25:57.0Z S: Update of locked domain succeeded. S: S: S: S: example.com S: update S: 12345-XYZ S: S: S: rl01 S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: ]]> If a transform is not authorized within the deadline a server MUST send a poll message indicating the failure of the transform. Example poll message indicating failure:

Extension Elements This extension adds additional elements to the EPP domain mapping.

The <regLock:policy> element The <regLock:policy> element contains the following elements: One OPTIONAL <regLock:timeout> element that contains the timeout for which after any <domain:update> operation will fail. A server MAY restrict the allowed values. One OPTIONAL <regLock:quorom> element that contains a positive non-zero integer that sets the number of registy lock contacts that MUST authorize the domain changes for it to be approved. A server MAY restrict the number of registry lock contacts a domain object can have.

The <regLock:contact> element The <regLock:contact> element contains the following elements: <regLock:contactID> the contact identifier. An OPTIONAL <regLock:method> the method used by the registry lock contact to authorize changes. A server MAY restrict the allowed values.

Well known <regLock:method> values A server MAY allow any value for the <regLock:method> element the following values have a well known definition: email - The contact will receive an email with further instructions. text - The contact will receive a text message with further instructions. letter - The contact will receive a postal letter with further instructions. phone - The contact will receive a phone call with further instructions. token - The contact will be provided means to send a token to the server for authorizing changes.

EPP Command Mapping

EPP Query Commands

EPP <check> Command This extension does not add any elements to the EPP <check> command or <check> response described in the EPP domain mapping .

EPP <info> Command This extension does not add any elements to the EPP <info> command described in the EPP domain mapping . However, additional elements are defined for the <info> response. An example <info> response for a domain object with no pending updates:

S: S: S: S: Command completed successfully S: S: S: S: example.com S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: S: ns1.example.com S: ns2.example.com S: S: ns1.example.com S: ns2.example.com S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: S: 1h S: 2 S: S: S: S: rl1001 S: email S: S: S: rl1002 S: email S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: ]]> An example <info> response for a domain with pending updates:

S: S: S: S: Command completed successfully S: S: S: S: example.com S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: S: ns1.example.com S: ns2.example.com S: S: ns1.example.com S: ns2.example.com S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: S: 1h S: 2 S: S: S: S: rl1001 S: email S: S: S: rl1002 S: email S: S: S: S: S: foo S: rl1001 S: rl1002 S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: ]]>

EPP <transfer> Command This extension does not add any elements to the EPP <transfer> command or <transfer> responses as described in the EPP domain mapping .

EPP Transform Commands EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.

EPP <create> Command This extension defines additional elements for the EPP <create> command described in the EPP domain mapping . No additional elements are defined for the EPP <create> response.

C: C: C: C: C: allocation.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: C: 1h C: C: C: C: rc101 C: email C: C: C: C: C: ABC-12345 C: C: ]]>

EPP <delete> Command

Domain Objects This extension does not define any additional elements to the EPP <delete> command or <delete> responses described in the EPP domain mapping . However if a server recieves a <delete> command for a domain object with registry lock set it MUST be rejected.

Contact Objects This extension does not define any additional elements to the EPP <delete> command or <delete> responses described in the EPP contact mapping . However if a server recieves a <delete> command for a contact object associated as a registry lock contact with a domain object it MUST be rejected.

EPP <renew> Command This extension does not define any additional elements to the EPP <renew> command or <renew> responses described in the EPP domain mapping .

EPP <transfer> Command This extension does not define any additional elements to the EPP <transfer> command or <transfer> responses described in the EPP domain mapping .

EPP <update> Command This extension defines additional elements for the EPP <update> command described in the EPP domain mapping . No additional elements are defined for the EPP <update> response. The EPP <update> command provides a transform operation that allows a client to modify the attributes of a domain object. In addition to the EPP command elements described in the EPP domain mapping, the command MUST contain an <extension> element, and the <extension> element MUST contain a child <regLock:update> element that identifies the extension namespace if the client wants to update the domain object with data defined in this extension. The <regLock:update> element contains a <regLock:add> to add registry lock contacts to a domain, a <regLock:rem> to remove registry lock contacts from a domain, or a <regLock:chg> element to change policy information or a registry lock contacts authorization method. At least one <regLock:add>, <regLock:rem>, or <regLock:chg> element MUST be provided. A <regLock:add> or <regLock:rem> MUST only contain <regLock:contact> elements as child elements. An example update command changing policy data:

C: C: C: C: C: example.com C: C: C: C: C: C: C: 3h C: C: C: C: C: ABC-12345 C: C: ]]> An example update command adding and removing registry lock contacts:

C: C: C: C: C: example.com C: C: C: C: C: C: C: rl1003 C: email C: C: C: rl1004 C: email C: C: C: C: C: rl1001 C: C: C: C: C: ABC-12345 C: C: ]]>

Formal Syntax