The Swedish Internet Foundation

eric.skoglund@internetstiftelsen.se

DENIC

kaempf@denic.de

This document describes an Extensible Provisioning Protocol (EPP) extension for setting and managing a registry lock on a domain object. About This Document This note is to be removed before publishing as an RFC. Status information for this document may be found at . Source for this draft and an issue tracker can be found at .

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 () () 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 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 CDS/CSYNC scanner. The removal of a registry lock is a manual, operational procedure and is not covered 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 Registry lock can be activated when a domain is created with a <regLock:create> extension, or on an existing domain by adding its first registry lock contact with <regLock:update>. The server MUST respond with result code 1001 as defined in section 3 of and await the required authorizations. A server MUST send a poll message when the request is approved, rejected, or times out. Example poll message indicating success: S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1301"> S: <msg lang="en-US"> S: Command completed successfully; ack to dequeue S: </msg> S: </result> S: <msgQ id="201" count="1"> S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <msg>Setting registry lock on domain succeeded.</msg> S: </msgQ> S: <resData> S: <regLock:pollInfo S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:domain>example.com</regLock:domain> S: <regLock:operation S: outcome="approved">create</regLock:operation> S: <regLock:svTRID>12345-XYZ</regLock:svTRID> S: <regLock:approvedBy> S: <regLock:contact> S: <regLock:id>rl1001</regLock:id> S: </regLock:contact> S: </regLock:approvedBy> S: </regLock:pollInfo> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp> If authorization times out, the poll data identifies the outcome as timedOut. Example poll message indicating timeout: S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1301"> S: <msg lang="en-US"> S: Command completed successfully; ack to dequeue S: </msg> S: </result> S: <msgQ id="201" count="1"> S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <msg>Setting registry lock on domain timed out.</msg> S: </msgQ> S: <resData> S: <regLock:pollInfo S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:domain>example.com</regLock:domain> S: <regLock:operation S: outcome="timedOut">create</regLock:operation> S: <regLock:svTRID>12345-XYZ</regLock:svTRID> S: </regLock:pollInfo> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp>

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 with result code 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. A server MUST send a poll message when the transform is approved, rejected, or times out. Example poll message indicating success: S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1301"> S: <msg lang="en-US"> S: Command completed successfully; ack to dequeue S: </msg> S: </result> S: <msgQ id="201" count="1"> S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <msg>Update of locked domain succeeded.</msg> S: </msgQ> S: <resData> S: <regLock:pollInfo S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:domain>example.com</regLock:domain> S: <regLock:operation S: outcome="approved">update</regLock:operation> S: <regLock:svTRID>12345-XYZ</regLock:svTRID> S: <regLock:approvedBy> S: <regLock:contact> S: <regLock:id>rl1001</regLock:id> S: </regLock:contact> S: </regLock:approvedBy> S: </regLock:pollInfo> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp> If a lock contact rejects a transform, the poll data identifies the outcome as rejected. Example poll message indicating rejection: S:<?xml version="1.0" encoding="UTF-8"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S: <response> S: <result code="1301"> S: <msg lang="en-US"> S: Command completed successfully; ack to dequeue S: </msg> S: </result> S: <msgQ id="201" count="1"> S: <qDate>2013-10-22T14:25:57.0Z</qDate> S: <msg>Update of locked domain was rejected.</msg> S: </msgQ> S: <resData> S: <regLock:pollInfo S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:domain>example.com</regLock:domain> S: <regLock:operation S: outcome="rejected">update</regLock:operation> S: <regLock:svTRID>12345-XYZ</regLock:svTRID> S: </regLock:pollInfo> S: </resData> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54321-XYZ</svTRID> S: </trID> S: </response> S:</epp>

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

The <regLock:policy> element The <regLock:policy> element in a create command, and the <regLock:policyData> element in an update command or info response, contain the following elements:

• One OPTIONAL <regLock:timeout> element that sets the authorization deadline. Its value is a positive integer followed by s, m, h, or d for seconds, minutes, hours, or days. A server MAY restrict the allowed values.
• One OPTIONAL <regLock:quorum> element that contains a positive integer setting the number of registry lock contacts that MUST authorize a change. A server MAY restrict the number of registry lock contacts a domain can have.

At least one policy value MUST be supplied when <regLock:policyData> is included in a <regLock:chg> element. The server applies its policy for any value omitted by the client. The quorum MUST NOT exceed the number of registry lock contacts on the domain after the command is applied.

The <regLock:contact> element The <regLock:contact> element contains the following elements:

• <regLock:id> 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.

A <regLock:contact> in <regLock:rem> or <regLock:approvedBy> contains only <regLock:id>. A <regLock:contact> in <regLock:chg>/<regLock:contactData> MUST also contain <regLock:method>.

Well known <regLock:method> values The following <regLock:method> values have well-known definitions. A server MAY allow other values:

• 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.

The <regLock:pollInfo> element A poll response uses <regLock:pollInfo> in <resData>. It identifies the domain, the server transaction ID of the original request, and an operation of create or update. The operation's outcome attribute is approved, rejected, or timedOut. An OPTIONAL <regLock:approvedBy> element lists the contacts that approved the request, each by ID. The EPP <msgQ> text is informational; clients use the outcome attribute to distinguish results.

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. The <regLock:infData> element contains optional <regLock:policyData>, required <regLock:contactData> with one or more contacts, and optional <regLock:updateData> for the one pending request allowed on a locked domain. Each pending contact has a status of pending, approved, or rejected. An example <info> response for a domain object with no pending updates: S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <domain:infData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</domain:name> S: <domain:roid>EXAMPLE1-REP</domain:roid> S: <domain:status s="ok"/> S: <domain:registrant>jd1234</domain:registrant> S: <domain:contact type="admin">sh8013</domain:contact> S: <domain:contact type="tech">sh8013</domain:contact> S: <domain:ns> S: <domain:hostObj>ns1.example.com</domain:hostObj> S: <domain:hostObj>ns2.example.com</domain:hostObj> S: </domain:ns> S: <domain:host>ns1.example.com</domain:host> S: <domain:host>ns2.example.com</domain:host> S: <domain:clID>ClientX</domain:clID> S: <domain:crID>ClientY</domain:crID> S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate> S: <domain:upID>ClientX</domain:upID> S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate> S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate> S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate> S: <domain:authInfo> S: <domain:pw>2fooBAR</domain:pw> S: </domain:authInfo> S: </domain:infData> S: </resData> S: <extension> S: <regLock:infData S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:policyData> S: <regLock:timeout>1h</regLock:timeout> S: <regLock:quorum>2</regLock:quorum> S: </regLock:policyData> S: <regLock:contactData> S: <regLock:contact> S: <regLock:id>rl1001</regLock:id> S: <regLock:method>email</regLock:method> S: </regLock:contact> S: <regLock:contact> S: <regLock:id>rl1002</regLock:id> S: <regLock:method>email</regLock:method> S: </regLock:contact> S: </regLock:contactData> S: </regLock:infData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S:</epp> An example <info> response for a domain with pending updates: S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> S: <response> S: <result code="1000"> S: <msg>Command completed successfully</msg> S: </result> S: <resData> S: <domain:infData S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: <domain:name>example.com</domain:name> S: <domain:roid>EXAMPLE1-REP</domain:roid> S: <domain:status s="ok"/> S: <domain:registrant>jd1234</domain:registrant> S: <domain:contact type="admin">sh8013</domain:contact> S: <domain:contact type="tech">sh8013</domain:contact> S: <domain:ns> S: <domain:hostObj>ns1.example.com</domain:hostObj> S: <domain:hostObj>ns2.example.com</domain:hostObj> S: </domain:ns> S: <domain:host>ns1.example.com</domain:host> S: <domain:host>ns2.example.com</domain:host> S: <domain:clID>ClientX</domain:clID> S: <domain:crID>ClientY</domain:crID> S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate> S: <domain:upID>ClientX</domain:upID> S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate> S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate> S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate> S: <domain:authInfo> S: <domain:pw>2fooBAR</domain:pw> S: </domain:authInfo> S: </domain:infData> S: </resData> S: <extension> S: <regLock:infData S: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> S: <regLock:policyData> S: <regLock:timeout>1h</regLock:timeout> S: <regLock:quorum>2</regLock:quorum> S: </regLock:policyData> S: <regLock:contactData> S: <regLock:contact> S: <regLock:id>rl1001</regLock:id> S: <regLock:method>email</regLock:method> S: </regLock:contact> S: <regLock:contact> S: <regLock:id>rl1002</regLock:id> S: <regLock:method>email</regLock:method> S: </regLock:contact> S: </regLock:contactData> S: <regLock:updateData> S: <regLock:update> S: <regLock:svTRID>12345-XYZ</regLock:svTRID> S: <regLock:contact status="approved"> S: <regLock:id>rl1001</regLock:id> S: </regLock:contact> S: <regLock:contact status="pending"> S: <regLock:id>rl1002</regLock:id> S: </regLock:contact> S: </regLock:update> S: </regLock:updateData> S: </regLock:infData> S: </extension> S: <trID> S: <clTRID>ABC-12345</clTRID> S: <svTRID>54322-XYZ</svTRID> S: </trID> S: </response> S:</epp>

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. A <regLock:create> element contains an OPTIONAL <regLock:policy> and a required <regLock:contacts> element with one or more contacts. C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <create> C: <domain:create C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: <domain:registrant>jd1234</domain:registrant> C: <domain:contact type="admin">sh8013</domain:contact> C: <domain:contact type="tech">sh8013</domain:contact> C: <domain:authInfo> C: <domain:pw>2fooBAR</domain:pw> C: </domain:authInfo> C: </domain:create> C: </create> C: <extension> C: <regLock:create C: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> C: <regLock:policy> C: <regLock:timeout>1h</regLock:timeout> C: </regLock:policy> C: <regLock:contacts> C: <regLock:contact> C: <regLock:id>rl1001</regLock:id> C: <regLock:method>email</regLock:method> C: </regLock:contact> C: </regLock:contacts> C: </regLock:create> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp>

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 receives 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 receives 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. To change data defined by this extension, the EPP <update> command MUST contain <regLock:update> within <extension>. It contains one or more of <regLock:add>, <regLock:rem>, and <regLock:chg>, each at most once. <regLock:add> and <regLock:rem> contain one or more <regLock:contact> elements. Adding the first registry lock contact to an existing domain activates its lock. Removing the last registry lock contact MUST be rejected; removal of the lock remains a manual procedure. <regLock:chg> contains <regLock:policyData> to change one or both policy values, <regLock:contactData> to change the authorization method of one or more existing contacts, or both in either order. Each contact method change identifies the contact by <regLock:id> and supplies its new <regLock:method>. An example update command changing policy data: C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> C: <command> C: <update> C: <domain:update C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: </domain:update> C: </update> C: <extension> C: <regLock:update C: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> C: <regLock:chg> C: <regLock:policyData> C: <regLock:timeout>3h</regLock:timeout> C: </regLock:policyData> C: </regLock:chg> C: </regLock:update> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp> An example update command adding and removing registry lock contacts: C:<?xml version="1.0" encoding="UTF-8" standalone="no"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> C: <command> C: <update> C: <domain:update C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: </domain:update> C: </update> C: <extension> C: <regLock:update C: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> C: <regLock:add> C: <regLock:contact> C: <regLock:id>rl1003</regLock:id> C: <regLock:method>email</regLock:method> C: </regLock:contact> C: <regLock:contact> C: <regLock:id>rl1004</regLock:id> C: <regLock:method>email</regLock:method> C: </regLock:contact> C: </regLock:add> C: <regLock:rem> C: <regLock:contact> C: <regLock:id>rl1001</regLock:id> C: </regLock:contact> C: </regLock:rem> C: </regLock:update> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp> An example update command activating registry lock on an existing domain: C:<?xml version="1.0" encoding="UTF-8"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <domain:update C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: </domain:update> C: </update> C: <extension> C: <regLock:update C: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> C: <regLock:add> C: <regLock:contact> C: <regLock:id>rl1001</regLock:id> C: <regLock:method>email</regLock:method> C: </regLock:contact> C: </regLock:add> C: <regLock:chg> C: <regLock:policyData> C: <regLock:timeout>1h</regLock:timeout> C: <regLock:quorum>1</regLock:quorum> C: </regLock:policyData> C: </regLock:chg> C: </regLock:update> C: </extension> C: <clTRID>ABC-12345</clTRID> C: </command> C:</epp> An example update command changing a lock contact's authorization method: C:<?xml version="1.0" encoding="UTF-8"?> C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> C: <command> C: <update> C: <domain:update C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> C: <domain:name>example.com</domain:name> C: </domain:update> C: </update> C: <extension> C: <regLock:update C: xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0"> C: <regLock:chg> C: <regLock:contactData> C: <regLock:contact> C: <regLock:id>rl1001</regLock:id> C: <regLock:method>phone</regLock:method> C: </regLock:contact> C: </regLock:contactData> C: </regLock:chg> C: </regLock:update> C: </extension> C: <clTRID>ABC-12346</clTRID> C: </command> C:</epp>

Formal Syntax The following XML Schema defines the registry lock extension namespace.

<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:regLock="urn:ietf:params:xml:ns:regLock-1.0" targetNamespace="urn:ietf:params:xml:ns:regLock-1.0" elementFormDefault="qualified"> <annotation> <documentation> Extensible Provisioning Protocol v1.0 registry lock extension schema. </documentation> </annotation> <!-- Child elements of EPP commands. --> <element name="create" type="regLock:createType"/> <element name="update" type="regLock:updateType"/> <!-- Child elements of EPP responses. --> <element name="infData" type="regLock:infDataType"/> <element name="pollInfo" type="regLock:pollInfoType"/> <simpleType name="identifierType"> <restriction base="token"> <minLength value="1"/> </restriction> </simpleType> <simpleType name="timeoutType"> <restriction base="token"> <pattern value="[1-9][0-9]*(s|m|h|d)"/> </restriction> </simpleType> <simpleType name="operationNameType"> <restriction base="token"> <enumeration value="create"/> <enumeration value="update"/> </restriction> </simpleType> <simpleType name="outcomeType"> <restriction base="token"> <enumeration value="approved"/> <enumeration value="rejected"/> <enumeration value="timedOut"/> </restriction> </simpleType> <simpleType name="approvalStatusType"> <restriction base="token"> <enumeration value="pending"/> <enumeration value="approved"/> <enumeration value="rejected"/> </restriction> </simpleType> <complexType name="policyType"> <sequence> <element name="timeout" type="regLock:timeoutType" minOccurs="0"/> <element name="quorum" type="positiveInteger" minOccurs="0"/> </sequence> </complexType> <!-- A policy change must contain at least one value. --> <complexType name="policyChangeType"> <choice> <sequence> <element name="timeout" type="regLock:timeoutType"/> <element name="quorum" type="positiveInteger" minOccurs="0"/> </sequence> <element name="quorum" type="positiveInteger"/> </choice> </complexType> <complexType name="contactType"> <sequence> <element name="id" type="regLock:identifierType"/> <element name="method" type="regLock:identifierType" minOccurs="0"/> </sequence> </complexType> <complexType name="idOnlyContactType"> <sequence> <element name="id" type="regLock:identifierType"/> </sequence> </complexType> <complexType name="contactChangeType"> <sequence> <element name="id" type="regLock:identifierType"/> <element name="method" type="regLock:identifierType"/> </sequence> </complexType> <complexType name="contactsType"> <sequence> <element name="contact" type="regLock:contactType" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="idOnlyContactsType"> <sequence> <element name="contact" type="regLock:idOnlyContactType" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="contactChangesType"> <sequence> <element name="contact" type="regLock:contactChangeType" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="createType"> <sequence> <element name="policy" type="regLock:policyType" minOccurs="0"/> <element name="contacts" type="regLock:contactsType"/> </sequence> </complexType> <complexType name="changeType"> <choice> <sequence> <element name="policyData" type="regLock:policyChangeType"/> <element name="contactData" type="regLock:contactChangesType" minOccurs="0"/> </sequence> <sequence> <element name="contactData" type="regLock:contactChangesType"/> <element name="policyData" type="regLock:policyChangeType" minOccurs="0"/> </sequence> </choice> </complexType> <!-- Require at least one section, each at most once, in any order. --> <complexType name="updateType"> <choice> <sequence> <element name="add" type="regLock:contactsType"/> <choice minOccurs="0"> <sequence> <element name="rem" type="regLock:idOnlyContactsType"/> <element name="chg" type="regLock:changeType" minOccurs="0"/> </sequence> <sequence> <element name="chg" type="regLock:changeType"/> <element name="rem" type="regLock:idOnlyContactsType" minOccurs="0"/> </sequence> </choice> </sequence> <sequence> <element name="rem" type="regLock:idOnlyContactsType"/> <choice minOccurs="0"> <sequence> <element name="add" type="regLock:contactsType"/> <element name="chg" type="regLock:changeType" minOccurs="0"/> </sequence> <sequence> <element name="chg" type="regLock:changeType"/> <element name="add" type="regLock:contactsType" minOccurs="0"/> </sequence> </choice> </sequence> <sequence> <element name="chg" type="regLock:changeType"/> <choice minOccurs="0"> <sequence> <element name="add" type="regLock:contactsType"/> <element name="rem" type="regLock:idOnlyContactsType" minOccurs="0"/> </sequence> <sequence> <element name="rem" type="regLock:idOnlyContactsType"/> <element name="add" type="regLock:contactsType" minOccurs="0"/> </sequence> </choice> </sequence> </choice> </complexType> <complexType name="pendingContactType"> <sequence> <element name="id" type="regLock:identifierType"/> </sequence> <attribute name="status" type="regLock:approvalStatusType" use="required"/> </complexType> <complexType name="pendingUpdateType"> <sequence> <element name="svTRID" type="regLock:identifierType"/> <element name="contact" type="regLock:pendingContactType" maxOccurs="unbounded"/> </sequence> </complexType> <complexType name="updateDataType"> <sequence> <element name="update" type="regLock:pendingUpdateType"/> </sequence> </complexType> <complexType name="infDataType"> <sequence> <element name="policyData" type="regLock:policyType" minOccurs="0"/> <element name="contactData" type="regLock:contactsType"/> <element name="updateData" type="regLock:updateDataType" minOccurs="0"/> </sequence> </complexType> <complexType name="operationType"> <simpleContent> <extension base="regLock:operationNameType"> <attribute name="outcome" type="regLock:outcomeType" use="required"/> </extension> </simpleContent> </complexType> <complexType name="pollInfoType"> <sequence> <element name="domain" type="regLock:identifierType"/> <element name="operation" type="regLock:operationType"/> <element name="svTRID" type="regLock:identifierType"/> <element name="approvedBy" type="regLock:idOnlyContactsType" minOccurs="0"/> </sequence> </complexType> </schema>

Security Considerations The security considerations for EPP , its domain mapping , and its contact mapping apply to this extension. Registry lock relies on the authentication, confidentiality, and integrity protections of EPP and its transport. It does not replace those protections. The contact authorization mechanisms are outside the scope of this specification. Their security determines whether registry lock provides effective protection against a compromised registrar account. Approval needs to identify the domain, the original transaction, and the exact requested changes. Reusing an approval for a different request, or accepting an approval after the authorization deadline, could permit unauthorized changes. Changes to registry lock contacts, their authorization methods, and the quorum policy require the same protection as other changes to a locked domain. Otherwise, an attacker could replace the contacts or reduce the quorum before requesting a domain change. Manual lock removal and any registry policy that bypasses authorization are also part of the security boundary and need appropriate authentication and audit controls. Contact identifiers and approval status can reveal information about the people responsible for a domain. Access to this information needs to be limited to authorized clients. Pending requests and repeated authorization notifications can also be used to exhaust resources or overwhelm contacts; implementations need suitable limits on these activities.

IANA Considerations This document requests registration of the following namespace and schema URIs in the IETF XML Registry, following the procedures in .

XML Namespace

• URI: urn:ietf:params:xml:ns:regLock-1.0
• Registrant Contact: IESG
• XML: None. This URI identifies an XML namespace.

XML Schema

• URI: urn:ietf:params:xml:schema:regLock-1.0
• Registrant Contact: IESG
• XML: The schema in .

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. This document describes an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes RFC 4930. [STANDARDS-TRACK] This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. This document obsoletes RFC 4931. [STANDARDS-TRACK] This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 4933. [STANDARDS-TRACK]