Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)

This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of launch phase extension in a domain name registry. It is typical for domain registries to operate in special modes within certain periods of time to facilitate allocation of domain names for a subset of the zone namespace that becomes available. This document uses the term "launch phase" and the shorter form "launch" to refer to such a period. The EPP domain name mapping is designed for the steady state operation of a registry. During the launch, the interface used at each phase of the launch could be different from what is defined in EPP domain name mapping. for example, registries typically accept multiple applications for a given domain name during the "sunrise" launch phase. In addition, the Trademark Clearinghouse Draft Implementation Model defines a registry interface for the Trademark Claims or "claims" launch phase that includes support for presenting a Trademark Claims Notice to the Registrant. This document proposes an extension to the domain name extension in order to unambiguously manage the various launch phases known.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. "launch-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:launch-1.0". The XML namespace prefix "launch" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.

This extension adds additional elements to the EPP domain name mapping. Only those new elements are described here.

Servers MAY allow multiple applications of a given domain name during its launch phase operations. Upon receiving a request to create a domain name, the server creates an application object corresponding to the request and assigns an application identifier for the application and returns it to the client with the <launch:applicationID> element. In order to facilitate correlation, all subsequent launch operations on the application object MUST be qualified by the previously assigned application identifier using the <launch:applicationID> element.

The server MAY support multiple launch phases sequentially or simultaneously. The <launch:phase> element MUST be included by the client to define the target launch phase of the command. The following launch phase values are defined: Phase when trademark holders can submit registration applications with trademark information that can be validated by the server. Post sunrise phase when non-trademark holders are allowed to register domain names. Trademark claims phase as defined by Trademark Clearinghouse Draft Implementation Model. Post launch phase that is also referred to as "steady state". Servers MAY require additional trademark protection with this phase. A custom server launch phase that is defined using the "name" attribute. For extensibility the <launch:phase> element includes an OPTIONAL "name" attribute that can define a sub-phase or the full name of the phase when the <launch:phase> element has the "custom" value.

A launch application object MAY have a status value. The <launch:status> element is used to convey extended status pertaining to the application object, beyond what is specified in the object mapping for this application object. The following status values are defined using the required "s" attribute: the initial state of a newly-created application object. the application meets relevant registry rules. the application does not validate according to registry rules. the application is pending based on results of an auction. one of two possible end states of an application object; the object corresponding to the application has been provisioned. the other possible end state; the object was not provisioned. A custom status that is defined using the the "name" attribute. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. The OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). For extensibility the <launch:status> element includes an OPTIONAL "name" attribute that can define a sub-status or the full name of the status when the status value is "custom". The server SHOULD NOT use of the "custom" status value. Certain status values MAY be combined. For example, an application can be invalid and rejected. Additionally certain statuses MAY be skipped. For example, an application MAY immediately start at the allocated status or an application MAY skip the pendingAuction status if server does not support an auction. If a <domain:create> processes a request synchronously without the use of an intermediate application, than an Application Identifier is not needed along with the application status.

| rejected | | allocated | | | | | \ / \ / +----+------+ +----+----+ +-------+ +-------+ | | ^ ^ | | | | | +-----------------+ | | | | +---------------------------------+ | | ^ | | | | | +--------+-------+ | | | | | +----------------------->| pendingAuction +------+ | | +----------------+ ]]>

A server MUST support one of four models for validating the trademark information: Use of a mark code by itself to validate that the mark matches the domain name. The code is the "sunrise code" as defined in Trademark Clearinghouse Draft Implementation Model that is validated by the server using its local sunrise code data. This model is supported using the <launch:codeMark> element with just the <launch:code> element. The mark information is passed without any other validation element. The server will use some custom form of validation to validate that the mark information is authentic. This model is supported using the <launch:codeMark> element with just the <launch:mark> element. A code is used along with the mark information by the server to validate the mark utilizing an external party like a Trademark Clearinghouse. The code represents some form of secret that matches the mark information passed. This model is supported using the <launch:codeMark> element with both the <launch:code> and the <launch:mark> element. The mark information is digitally signed as described in the Digital Signature section. The digital signature can be directly validated by the server using the public key of the external party that created the signed mark. This model is supported using the <launch:signedMark> and <launch:signedNotice> elements. More than one <launch:codeMark> element or more than one <launch:signedMark> element MAY be specified. The maximum number of marks per domain name is up to server policy.

The <launch:codeMark> element that is used by the "code", "mark", and "code with mark" validation models has the following child elements: OPTIONAL mark code used to validate the <launch:mark> information or to directly validate the mark against the domain name. The mark code can be a mark specific secret value that the server can verify against a third party or can be directly combined with the domain name to verify against a server code file. OPTIONAL mark information with child elements defined in the Mark section.

The following is an example <launch:codeMark> element with both a <launch:code> and a <launch:mark> element. 49FD46E6C4B45C55D4AC Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld ]]>

A <launch:mark> element describes an applicant's prior right to a given domain name. The child elements of the <launch:mark> element include: an identifier for the mark. This identifier MUST be unique among all marks associated with an application object. The registered trademark text string. This value is free-form text that MAY be mapped to one or more <launch:label> values. Zero or more domain name labels that corresponds to the <launch:name>. Each <launch:label> can match directly to the domain name after adding the parent zone. name of the authority which issued the right (trademark clearinghouse, trademark office, company registration bureau, etc.) the registration number of the right (trademark number, company registration number, etc.) indicates the type of mark being made (trademark, symbol, combined mark, company name, etc.) indicates the applicant's entitlement to the mark (owner, licensee, etc.) the date of registration of the mark the date of expiration of the mark indicates the country in which the mark is valid. This may be a two-character code from indicates the name of a city, state, province or other geographic region in which the mark is valid. Owner information using the Contact elements. Contact for the owner using the Contact element. All of the child elements are OPTIONAL. Server policy may place additional constraints on the format and requirements of such elements.

The contact information contained within the Mark cannot be defined via a contact identifier as defined in the EPP contact mapping since it is contact information defined outside of the server. Some of the contact elements defined in EPP contact mapping are replicated in this extension. The child elements of a contact using either the <launch:owner> or <launch:contact> elements include: identifier of contact that MUST be unique among all contacts of the external third party. name of the individual or role represented by the contact. name of the organization with which the contact is affiliated. address information associated with the contact. the <launch:addr> element contains the following child elements: one, two, or three <launch:street> elements that contain the contact's street address. contact's city contact's state or province contact's country code contact's voice telephone number contact's facsimile telephone number contact's email address All of the child elements are OPTIONAL. Server policy may place additional constraints on the format and requirements of such elements.

Digital signatures can be used by the server to validate either the mark information, when using the signed mark model with the <launch:signedMark> element, or the claims notice with the <launch:signedNotice> element. The digital signatures are handled using an XML Signature around the entire <launch:signedMark> or <launch:signedNotice> elements. Once the digital signature is validated using the appropriate public key, the server can trust all of the information included in the <launch:signedMark> or <launch:signedNotice> elements. It's up to server policy how the public key is transferred. To have the digital signature cover all of the elements of the <launch:signedMark> and <launch:signedNotice> elements, the XML Signature Reference URI is set to "#pointer(..)" and the Transform "http://www.w3.org/2000/09/xmldsig#enveloped-signature" is used. Both of these has the digital signature cover the parent element of the Signature element and to specify that the Signature element is embedded in the parent element.

The child elements of the <launch:signedMark> element include: Signature serial number that that can be compared with a revocation list by the server. Zero or more DNS zones the <launch:signedMark> can be used with. No <launch:zone> element indicates that the <launch:signedMark> can be used within any DNS zone. OPTIONAL date and time that the <launch:signedMark> expires. The server MUST NOT accept a <launch:signedMark> that has expired. No <launch:exDate> element indicates that there is no expiry. Trademark information as defined in the Mark section. XML Signature for the <launch:signedMark>

The following is an example <launch:signedMark> using the XML Signature to sign all of the elements of <launch:signedMark> element. 123456 newtld 2012-08-16T09:00:00.0Z Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld j6lwx3rvEPO0vKtMup4NbeVu8nk= cID8yqvR60QYQVhOpBDUmPiIxplV/fM7lj9RKF+fswSjJAklUrgf2w== ]]>

The child elements of the <launch:signedNotice> element include: Unique notice identifier generated by the third party. The <launch:noticeID> can be compared with a revocation list by the server. Domain name that the claims notice is for. Date and time that the <launch:signedNotice> was created. OPTIONAL date and time that the <launch:signedNotice> expires. The server MUST NOT accept a <launch:signedNotice> that has expired. No <launch:exDate> element indicates that there is no expiry. XML Signature for the <launch:signedNotice>

The following is an example <launch:signedNotice> using the XML Signature to sign all of the elements of <launch:signedNotice> element. 49FD46E6C4B45C55D4AC example.tld 2012-09-07T22:00:00.0Z 2012-09-08T22:00:00.0Z j6lwx3rvEPO0vKtMup4NbeVu8nk= cID8yqvR60QYQVhOpBDUmPiIxplV/fM7lj9RKF+fswSjJAklUrgf2w== ]]>

A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification . The command mappings described here are specifically for use in the Launch Phase Extension. This mapping is designed to be flexible, requiring only a minimum set of required elements. While it is meant to serve several use cases, it does not prescribe any interpretation by the client or server. Such processing is typically highly policy-dependent and therefore specific to implementations. Operations on application objects are done via one or more of the existing EPP verbs defined in the EPP domain name mapping. Registries may choose to support a subset of the operations.

This extension defines additional elements to extend the EPP <check> command and response to be used in conjunction with the EPP domain name mapping. This extension defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks for each domain name passed in the command. Instead of returning whether the domain name is available it will return whether or not at least one matching trademark exists for the domain name. If there is at least one matching trademark that exists for the domain name a <launch:claimKey> element is returned. The value of that the <launch:claimKey> element can be used with a info service of a third party trademark provider like the Trademark Clearinghouse (TMCH) for getting the information needed to generate the trademark claims notice. The third party trademark provider should also return a Signed Notice that can be passed in the extension to the extension to the Create Command for the server to validate that the correct trademark claims notice was presented. The <domain:name> elements in the EPP <check> command of EPP domain name mapping define the domain names to check for matching trademarks. The <launch:check> element contains the following child elements: The phase with the value of "claims" to indicate that this is a Claims Check Command.

Example Claims Check Command using the <check> domain command and the <launch:check> extension to determine if "example1.tld" and "example2.tld" have any matching trademarks. example1.tld example2.tld claims ABC-12345 ]]> If the <check> command has been processed successfully, the EPP <resData> element MUST contains a child <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements: the phase with a value of "claims". One or more <launch:cd> elements that contain the following child elements: Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name. A value of "1" or "true" means that a matching trademark does exist. A value of "0" or "false" means that a matching trademark does not exist. An OPTIONAL claim key that can be passed to a info service of a third party trademark provider like the Trademark Clearinghouse (TMCH) for getting the information needed to generate the trademark claims notice. The <claimKey> is used as the key for the query in place of the domain name to securely query the service without using a well-known value like a domain name.

Example Claims Check Response when no matching trademarks are found for the domain name example1.tld and matching trademarks are found for the domain name example2.tld. Command completed successfully claims example1.tld example2.tld abc123 ABC-12345 54322-XYZ ]]>

This extension defines additional elements to extend the EPP <info> command and response to be used in conjunction with the EPP domain name mapping. There are two forms of the extension to the EPP <info> command that are dependent on the supported launch phases as defined below: The EPP <info> command with the "sunrise" phase is used to retrieve information for a specific "sunrise" application based on an Application Identifier. This form of the EPP <info> extension is referred to as the Sunrise Info Form and is defined in the Sunrise Info Form section. The EPP <info> command with the "landrush" phase is undefined but the form supported is up to server policy. The EPP <info> command with the "claims" phase is used to retrieve the trademark claims information associated with a non-existing domain name that is referred to as the Claims Info Command. The response to the Claims Info Command does not extend the Domain Info Response as defined in EPP domain name mapping. This form of the EPP <info> extension is referred to as the Claims Info Form and defined in the Claims Info Form section. The EPP <info> command with the "open" phase is undefined but the form supported is up to server policy. The EPP <info> command with the "custom" phase is undefined but the form supported is up to server policy.

The Sunrise Info Form of the extension to the EPP domain name mapping gets information on an application created with the <launch:create> using the Application Identifier returned in the <launch:creData> element of the Create Response. A <launch:info> element is sent along with the regular <info> domain command. The <launch:info> element contains the following child elements: The phase during which the application was submitted or is associated with. Server policy defines what phases that are supported for the Sunrise Info Form. the application identifier of the application.

Example <info> domain command with the Sunrise Info Form <launch:info> extension. example.tld sunrise abc123 ABC-12345 ]]> If the query was successful, the server replies with an <launch:infData> element along with the regular EPP <resData>. The <launch:infData> contains the following child elements: the phase during which the application was submitted or is associated with. the application identifier of the returned application. status of the application using one of the supported status values. zero or more <launch:codeMark> elements. The <launch:codeMark> child elements are defined in the <launch:codeMark> element section. zero or more <launch:signedMark> elements. The <launch:signedMark> child elements are defined in the <launch:signedMark> element section.

Example <info> domain response using the Sunrise Info Form <launch:infData> extension with multiple codes. Command completed successfully example.tld EXAMPLE1-REP jd1234 sh8013 sh8013 ClientX ClientY 2012-04-03T22:00:00.0Z 2fooBAR sunrise abc123 49FD46E6C4B45C55D4AC 49FD46E6C4B45C55D4AD 49FD46E6C4B45C55D4AE ABC-12345 54322-XYZ ]]>

Example <info> domain response using the Sunrise Info Form <launch:infData> extension with code and mark information. Command completed successfully exampleone.tld EXAMPLE1-REP jd1234 sh8013 sh8013 ClientX ClientY 2012-04-03T22:00:00.0Z 2fooBAR sunrise abc123 Application rejected due to result of auction. 49FD46E6C4B45C55D4AC Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld ABC-12345 54322-XYZ ]]>

Example <info> domain response using the Sunrise Info Form <launch:infData> extension signed mark information. Command completed successfully exampleone.tld EXAMPLE1-REP jd1234 sh8013 sh8013 ClientX ClientY 2012-04-03T22:00:00.0Z 2fooBAR sunrise abc123 123456 newtld 2012-08-16T09:00:00.0Z Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld j6lwx3rvEPO0vKtMup4NbeVu8nk= cID8yqvR60QYQVhOpBDUmPiIxplV/fM7lj9RKF+fswSjJAklUrgf2w== ABC-12345 54322-XYZ ]]>

The Claims Info Form of the extension to the EPP domain name mapping gets trademark claims information for a non-existing domain name that is referred to as a Claims Info Command. The <launch:info> element contains the following child elements: The phase with the value of "claims" to indicate that this is a Claims Info Command.

Example Claims Info Command using the <info> domain command and the Claims Info Form <launch:info> extension. example.tld claims ABC-12345 ]]> If the query was successful, the server replies with an <launch:infData> element containing the trademark claims information expected to be used by the client to generate the claims notice. The <launch:infData> has the following child elements: the phase with a value of "claims". The information used for the trademark claims notice. The <launch:notice> element has the following child elements: The domain name that the claim notice information is associated with. OPTIONAL element included if there are no trademark claims associated with the <launch:name> OPTIONAL server generated identifier for the claims notice that is passed in the <launch:create> extension of the Create Command. This MUST be included if there is at least one trademark claim associated with the <launch:notice> <launch:name> element. Zero or more <launch:mark> elements containing the trademark information as defined in the Mark section.

Example Claims Info Response when no matching trademark claims are found for the domain name example.tld. Command completed successfully claims example.tld ABC-12345 54322-XYZ ]]>

Example Claims Info Response when two matching trademark claims are found for the domain name exampleone.tld. Command completed successfully claims exampleone.tld 49FD46E6C4B45C55D4AC Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld Example Two example-two exampletwo IP Clearinghouse GE 3933233 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld ABC-12345 54322-XYZ ]]>

There are two forms of the extension to the EPP <create> command that are dependent on the supported launch phases as defined below: The EPP <create> command with the "sunrise" phase is used to submit an application with trademark information that can be verified by the server with the <domain:name> value. The Sunrise Create Form is used for the "sunrise" phase. Optionally, the server can support multiple overlapping applications that are chosen asynchronously with a server generated Application Identifier for later reference. The EPP <create> command with the "landrush" phase is undefined but the form supported is up to server policy. The EPP <create> command with the "claims" phase is used to pass the information that can be used to validate that the claims notice information was retrieved via the Claims Info Command and was accepted by the registrant. The Claims Create Form is used for the "claims" phase. The EPP <create> command with the "open" phase is undefined but the form supported is up to server policy. The EPP <create> command with the "custom" phase is undefined but the form supported is up to server policy.

The Sunrise Create Form of the extension to the EPP domain name mapping includes the verifiable trademark information that the server uses to match against the domain name to authorize the domain create. A server MUST support one of four models in Claim Validation Models for the verifiable trademark information passed by the client. A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element contains the following child elements: The phase the application is associated with. zero or more <launch:codeMark> elements. The <launch:codeMark> child elements are defined in the <launch:codeMark> element section. zero or more <launch:signedMark> elements. The <launch:signedMark> child elements are defined in the <launch:signedMark> element section.

Following is an example <create> domain command using the <launch:create> extension with multiple sunrise codes. example.tld jd1234 sh8013 sh8013 2fooBAR sunrise 49FD46E6C4B45C55D4AC 49FD46E6C4B45C55D4AD 49FD46E6C4B45C55D4AE ABC-12345 ]]>

Following is an example <create> domain command using the <launch:create> extension with a code and mark information. exampleone.tld jd1234 sh8013 sh8013 2fooBAR sunrise 49FD46E6C4B45C55D4AC Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld ABC-12345 ]]>

Following is an example <create> domain command using the <launch:create> extension with signed mark information. example.tld jd1234 sh8013 sh8013 2fooBAR sunrise 123456 newtld example-and-example example Hello IP Clearinghouse GE 3933232 REG-TM-WORD owner 2011-09-09 2013-09-09 AU VIC Example Inc. John Doe Example Inc. 123 Example Dr. Suite 100 Reston VA 20190 US +1.7035555555 +1.7035555556 jdoe@example.tld j6lwx3rvEPO0vKtMup4NbeVu8nk= cID8yqvR60QYQVhOpBDUmPiIxplV/fM7lj9RKF+fswSjJAklUrgf2w== ABC-12345 ]]> If the create was successful, the server MAY reply with the <launch:creData> element along with the regular EPP <resData> to indicate the server generated Application Identifier when multiple applications of a given domain name is supported; otherwise no extension is included with the regular EPP <resData>. The <launch:creData> element contains the following child elements: The phase of the application that mirrors the <launch:phase> element included in the <launch:create>. the application identifier of the application.

An example response when multiple overlapping applications are supported by the server. Command completed successfully example.tld 2010-08-10T15:38:26.623854Z 2012-08-10T15:38:26.623854Z sunrise 2393-9323-E08C-03B1 example:epp:239332 server-8551292e23b ]]>

The Claims Create Form of the extension to the EPP domain name mapping includes the information related to the acceptance of the claims notice that is based on the contents of the Claims Info Response defined in the Claims Info Form section or is based on a signed notice by a trusted third party like the Trademark Clearinghouse (TMCH). A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element contains the following child elements: Must contain the value of "claims" to indicate it is the Claims Create Form Contains the date and time that the claims notice was accepted. Contains the client IP address of the client that accepted the claims notice. Server generated identifier for the claim notice information returned in the <launch:infData> element. The server MUST validate the noticeID either matches the exact claims information returned in the <launch:infData> or the current claims information associated with the domain name. The method of validation is up to server policy. If the launchID does not pass the validation the server MUST return an EPP error result code of 2202. Signed claims notice reference information generated by a trusted third party like the Trademark Clearinghouse (TMCH). The child elements of <signedNotice> are defined in the <launch:signedNotice> element section.

Following is an example <create> domain command using the <launch:create> extension with the trademark claims notice reference information and a <launch:noticeID>. example.tld jd1234 sh8013 sh8013 2fooBAR claims 2012-06-19T09:00:00.0Z 192.0.2.29 49FD46E6C4B45C55D4AC ABC-12345 ]]>

Following is an example <create> domain command using the <launch:create> extension with the signed notice reference information. example.tld jd1234 sh8013 sh8013 2fooBAR claims 2012-06-19T09:00:00.0Z 192.0.2.29 49FD46E6C4B45C55D4AC example.tld 2012-09-07T22:00:00.0Z 2012-09-08T22:00:00.0Z j6lwx3rvEPO0vKtMup4NbeVu8nk= cID8yqvR60QYQVhOpBDUmPiIxplV/fM7lj9RKF+fswSjJAklUrgf2w== ABC-12345 ]]>

This extension defines additional elements to extend the EPP <update> command to be used in conjunction with the domain name mapping. A server that does not support allow multiple applications of a given domain name with a Application Identifier during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients may update an application object by submitting an EPP <update> command along with an <launch:update> element to indicate the application object to be updated. The <launch:update> element contains the following child elements: the phase during which the application was submitted or is associated with. the application identifier for which the client wishes to update. This extension does not define any extension to the response of an <update> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain mapping.

Following is an example <update> domain command with the <launch:update> extension to add and remove a name server of a sunrise application with the application identifier "abc123". example.tld ns2.example.tld ns1.example.tld sunrise abc123 ABC-12345 ]]>

An example response that corresponds to the above command. Command completed successfully example:epp:239333 server-8551292e23c ]]>

This extension defines additional elements to extend the EPP <delete> command to be used in conjunction with the domain name mapping. A server that does not support allow multiple applications of a given domain name with a Application Identifier during its launch phase operations MUST return an EPP error result code of 2102. Registry policies permitting, clients MAY withdraw an application by submitting an EPP <delete> command along with an <launch:delete> element to indicate the application object to be deleted. The <launch:delete> element contains the following child elements: the phase during which the application was submitted or is associated with. the application identifier for which the client wishes to delete. This extension does not define any extension to the response of an <delete> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain mapping.

Following is an example <delete> domain command with the <launch:delete> extension. example.tld sunrise abc123 ABC-12345 ]]>

An example response that corresponds to the above command. Command completed successfully example:epp:239334 server-8551292e23d ]]>

This extension does not define any extension to the EPP <renew> command or response described in the EPP domain name mapping.

This extension does not define any extension to the EPP <transfer> command or response described in the EPP domain name mapping.

An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Extensible Provisioning Protocol v1.0 domain name extension schema for the launch phase processing. END]]>

[to be filled in]

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . Registration request for the extension namespace: URI: urn:ietf:params:xml:ns:launch-1.0 Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. Registration request for the extension XML schema: URI: urn:ietf:params:xml:schema:launch-1.0

The mapping extensions described in this document do not provide any security services beyond those described by EPP, the EPP domain name mapping, and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. Updates to, and deletion of an application object must be restricted to clients authorized to perform the said operation on the object. As information contained within an application, or even the mere fact that an application exists may be confidential. Any attempt to operate on an application object by an unauthorized client MUST be rejected with an EPP 2303 (object does not exist) or an appropriate auhorization error. Server policy may allow <info> operation with filtered output by clients other than the sponsoring client, in which case the <domain:infData> and <launch:infData> response SHOULD be filtered to include only fields that are publicly accessible.