Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)

Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) VeriSign, Inc.

12061 Bluemont Way Reston VA 20190 US jgould@verisign.com http://www.verisigninc.com

Cloud Registry

Suite 32 Seabridge House 377 Kent St Sydney NSW 2000 AU +61 414 710899 wil@cloudregistry.net http://www.cloudregistry.net

CentralNic Ltd

35-39 Mooregate London England EC2R 6AR GB +44 20 33 88 0600 gavin.brown@centralnic.com https://www.centralnic.com

Applications Internet Engineering Task Force EPP, Sunrise, Landrush, Trademark Clearinghouse, Trademark Claims, domain name registry, launch phase This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry.

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 domain name registrations and applications during the launch of a domain name registry. It is typical for domain registries to operate in special modes during their initial launch to facilitate allocation of domain names, often according to special rules. 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 a launch period, the model in place may be different from what is defined in the EPP domain name mapping. For example, registries often accept multiple applications for the same domain name during the "Sunrise" launch phase, referred to as a Launch Application. A Launch Registration refers to a registration made during a launch phase when the server uses a "first-come, first-served" model. Even in a "first-come, first-served" model, additional steps and information might be required, such as trademark information. In addition, the 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 mapping in order to provide a uniform interface for the management of Launch Applications and Launch Registrations in launch phases.

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. In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. "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. "signedMark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in . The XML namespace prefix "smd" 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. "mark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:mark-1.0" that is defined in . The XML namespace prefix "mark" 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, referred to as a Launch Application, of the same domain name during its launch phase operations. Upon receiving a valid request to create a Launch Application, the server MUST create an application object corresponding to the request, assign an application identifier for the Launch Application, set the pendingCreate status, and return the application identifier to the client with the <launch:applicationID> element. In order to facilitate correlation, all subsequent launch operations on the Launch Application MUST be qualified by the previously assigned application identifier using the <launch:applicationID> element. If the <domain:create> command processes a request synchronously without the use of an intermediate Launch Application, then an application identifier MAY not be needed.

The Validator Identifier is the unique identifier for a Trademark Validator that validates marks and has a repository of validated marks. The OPTIONAL "validatorID" attribute is used to define the Validator Identifier of the Trademark Validator. Registries MAY support more than one Third Party Trademark Validator. The Internet Corporation for Assigned Names and Numbers (ICANN) Trademark Clearinghouse (TMCH) is the default Trademark Validator and is reserved the Validator Identifier of "tmch". If the ICANN TMCH is not used or multiple Trademark Validators are used, the Validator Identifier MUST be defined using the "validatorID" attribute. The Validator Identifier MAY be related to one or more issuer identifiers of the <mark:id> element and the <smd:id> element defined in . Both the Validator Identifier and the Issuer Identifier used MUST be unique. The list of validator identifiers and the relationship to issuer identifiers is out of scope for this document. The Validator Identifier MAY define a non-Trademark Validator that supports a form of claims.

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 server SHOULD validate the phase and MAY validate the sub-phase of the <launch:phase> element against the active phase and OPTIONAL sub-phase of the server on a create command, and return an EPP error result code of 2306 if there is a mismatch. The following launch phase values are defined: The phase during which trademark holders can submit registrations or applications with trademark information that can be validated by the server. A post-Sunrise phase when non-trademark holders are allowed to register domain names with steps taken to address a large volume of initial registrations. The Trademark Claims phase, as defined in the TMCH Functional Specification, in which a Claims Notice must be displayed to a prospective registrant of a domain name that matches trademarks. A post-launch phase that is also referred to as "steady state". Servers MAY require additional trademark protection during 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. For example, the "claims" launch phase could have two sub-phases that include "landrush" and "open". Launch phases MAY overlap to support the "claims" launch phase, defined in the TMCH Functional Specification, and to support a traditional "landrush" launch phase. The overlap of the "claims" and "landrush" launch phases SHOULD be handled by setting "claims" as the <launch:phase> value and setting "landrush" as the sub-phase with the "name" attribute. For example, the <launch:phase> element SHOULD be <launch:phase name="landrush">claims</launch:phase>.

A Launch Application or Launch Registration object MAY have a launch status value. The <launch:status> element is used to convey the launch status pertaining to the object, beyond what is specified in the object mapping. A Launch Application or Launch Registration MUST set the "pendingCreate" status if a launch status is supported and the launch status is not one of the final statuses, including the "allocated" and "rejected" statuses. The following status values are defined using the required "s" attribute: The initial state of a newly-created application or registration object. The application or registration requires validation, but the validation process has not yet completed. The application or registration meets relevant registry rules. The application or registration does not validate according to registry rules. Server policies permitting, it may transition back into "pendingValidation" for revalidation, after modifications are made to ostensibly correct attributes that caused the validation failure. The allocation of the application or registration is pending based on the results of some out-of-band process (for example, an auction). The object corresponding to the application or registration has been provisioned. Is a possible end state of an application or registration object. The application or registration object was not provisioned. Is a possible end state of an application or registration object. A custom status that is defined using 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 the "custom" status value. Status values MAY be skipped. For example, an application or registration MAY immediately start at the "allocated" status or an application or registration MAY skip the "pendingAllocation" status. If the launch phase does not require validation of a request, an application or registration MAY immediately skip to "pendingAllocation".

A Launch Application MUST and a Launch Registration MAY be handled as a domain name of in "pendingCreate" status, with the launch status values defined in . As a Launch Application or Launch Registration transitions between the status values defined in , the server SHOULD insert poll messages, per , for the applicable intermediate statuses, including the "pendingValidation", "validated", "pendingAllocation, and "invalid" statuses, using the <domain:infData> element with the <launch:infData> extension. The <domain:infData> element MAY contain non-mandatory information, like contact and name server information. Also, further extensions that would normally be included in the response of a <domain:info> command, per , MAY be included. For the final statuses, including the "allocated" and "rejected" statuses, the server MUST insert a <domain:panData> poll message, per , with the <launch:infData> extension.

The following is an example poll message for a Launch Application that has transitioned to the "pendingAllocation" state. S: S: S: S: Command completed successfully; ack to dequeue S: S: S: 2013-04-04T22:01:00.0Z S: Application pendingAllocation. S: S: S: S: domain.example S: ... S: S: S: S: S: sunrise S: abc123 S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S:]]>

The following is an example <domain:panData> poll message for an "allocated" Launch Application. S: S: S: S: Command completed successfully; ack to dequeue S: S: S: 2013-04-04T22:01:00.0Z S: Application successfully allocated. S: S: S: S: domain.example S: S: ABC-12345 S: 54321-XYZ S: S: 2013-04-04T22:00:00.0Z S: S: S: S: S: sunrise S: abc123 S: S: S: S: S: BCD-23456 S: 65432-WXY S: S: S:]]>

The following is an example <domain:panData> poll message for an "allocated" Launch Registration. S: S: S: S: Command completed successfully; ack to dequeue S: S: S: 2013-04-04T22:01:00.0Z S: Registration successfully allocated. S: S: S: S: domain.example S: S: ABC-12345 S: 54321-XYZ S: S: 2013-04-04T22:00:00.0Z S: S: S: S: S: sunrise S: S: S: S: S: BCD-23456 S: 65432-WXY S: S: S:]]>

A server MUST support at least one of the following models for validating trademark information: Use of a mark code by itself to validate that the mark matches the domain name. 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 <mark:mark> element. A code is used along with the mark information by the server to validate the mark utilizing an external party. The code represents some form of secret that matches the mark information passed. This model is supported using the <launch:codeMark> element that contains both the <launch:code> and the <mark:mark> elements. 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 using its private key. This model is supported using the <smd:signedMark> and <smd:encodedSignedMark> elements. More than one <launch:codeMark>, <smd:signedMark>, or <smd:encodedSignedMark> 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 <mark:mark> information. The mark code is be a mark-specific secret that the server can verify against a third party. The OPTIONAL "validatorID" attribute is the Validator Identifier whose value indicates which Trademark Validator that the code originated from, with no default value. 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 <mark:mark> element. 49FD46E6C4B45C55D4AC ... ]]>

A <mark:mark> element describes an applicant's prior right to a given domain name that is used with the "mark", "mark with code", and the "signed mark" validation models. The <mark:mark> element is defined in . A new mark format can be supported by creating a new XML schema for the mark that has an element that substitutes for the <mark:abstractMark> element from .

Digital signatures MAY be used by the server to validate either the mark information, when using the "signed mark" validation model with the <smd:signedMark> element or the <smd:encodedSignedMark> element.

The <smd:signedMark> element contains the digitally signed mark information. The <smd:signedMark> element is defined in . A new signed mark format can be supported by creating a new XML schema for the signed mark that has an element that substitutes for the <smd:abstractSignedMark> element from .

The <smd:encodedSignedMark> element contains an encoded form of the digitally signed <smd:signedMark> element. The <smd:encodedSignedMark> element is defined in . A new encoded signed mark format can be supported by creating a new XML schema for the encoded signed mark that has an element that substitutes for the <smd:encodedSignedMark> element from .

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.

There are three forms of the extension to the EPP <check> command: the Claims Check Form, the Availability Check Form, and the Trademark Check Form. The <launch:check> element "type" attribute defines the form, with the value of "claims" for the Claims Check Form, with the value of "avail" for the Availability Check Form, and with the value of "trademark" for the Trademark Check Form. The default value of the "type" attribute is "claims". The forms supported by the server is determined by server policy. The server MUST return an EPP error result code of 2307 if it receives a check form that is not supported.

The Claims Check Form defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command, that requires the use of the "Claims Create Form" on a Domain Create Command. The availability check information defined in the EPP domain name mapping MUST NOT be returned for the Claims Check Command. This form is the default form and MAY be explicitly identified by setting the <launch:check> "type" attribute to "claims". Instead of returning whether the domain name is available, the Claims Check Command will return whether or not at least one matching trademark exists for the domain name, that requires the use of the "Claims Create Form" on a Domain Create Command. If there is at least one matching trademark that exists for the domain name, a <launch:claimKey> element is returned. The client MAY then use the value of the <launch:claimKey> element to obtain information needed to generate the Trademark Claims Notice from Trademark Validator based on the Validator Identifier. The unique notice identifier of the Trademark Claims Notice MUST be passed in the <launch:noticeID> element of the extension to the Create Command. 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: Contains the value of the active launch phase of the server. The server SHOULD validate the value against the active server launch phase.

Example Claims Check command using the <check> domain command and the <launch:check> extension with the "type" explicitly set to "claims", to determine if "domain1.example", "domain2.example", and "domain3.example" require claims notices during the "claims" launch phase: C: C: C: C: C: domain1.example C: domain2.example C: domain3.example C: C: C: C: C: claims C: C: C: ABC-12345 C: C:]]> If the <check> command has been processed successfully, the EPP <response> MUST contain an <extension> <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements: The phase that mirrors the <launch:phase> element included in the <launch:check>. 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 that requires the use of the "Claims Create Form" on a Domain Create Command. A value of "1" (or "true") means that a matching trademark does exist and that the "Claims Create Form" is required on a Domain Create Command. A value of "0" (or "false") means that a matching trademark does not exist or that the "Claims Create Form" is NOT required on a Domain Create Command. Zero or more OPTIONAL claim keys that MAY be passed to a third-party trademark validator such as the Trademark Clearinghouse (TMCH) for querying the information needed to generate a Trademark Claims Notice. The <launch: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. The OPTIONAL "validatorID" attribute is the Validator Identifier whose value indicates which Trademark Validator to query for the Claims Notice information, with the default being the ICANN TMCH. The "validatorID" attribute MAY reference a non-trademark claims clearinghouse identifer to support other forms of claims notices.

Example Claims Check response when a claims notice is not required for the domain name domain1.example, a claims notice is required for the domain name domain2.example in the "tmch", and a claims notice is required for the domain name domain3.example in the "tmch" and "custom-tmch", for the "claims" launch phase: S: S: S: S: Command completed successfully S: S: S: S: claims S: S: domain1.example S: S: S: domain2.example S: S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: S: S: S: domain3.example S: S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: S: S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

The Availability Check Form defines additional elements to extend the EPP <check> command described in the EPP domain name mapping. No additional elements are defined for the EPP <check> response. This form MUST be identified by setting the <launch:check> "type" attribute to "avail". The EPP <check> command is used to determine if an object can be provisioned within a repository. Domain names may be made available only in unique launch phases, whilst remaining unavailable for concurrent launch phases. In addition to the elements expressed in the <domain:check>, the command is extended with the <launch:check> element that contains the following child elements: The launch phase to which domain name availability should be determined.

Example Availability Check Form command using the <check> domain command and the <launch:check> extension with the "type" set to "avail", to determine the availability of two domain names in the "idn-release" custom launch phase: C: C: C: C: C: domain1.example C: domain2.example C: C: C: C: C: custom C: C: C: ABC-12345 C: C:]]> The Availability Check Form does not define any extension to the response of an <check> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping.

The Trademark Check Form defines a new command called the Trademark Check Command that is used to determine whether or not there are any matching trademarks for each domain name passed in the command, independent of the active launch phase of the server and whether the "Claims Create Form" is required on a Domain Create Command. The availability check information defined in the EPP domain name mapping MUST NOT be returned for the Trademark Check Command. This form MUST be identified by setting the <launch:check> "type" attribute to "trademark". Instead of returning whether the domain name is available, the Trademark Check Command 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 client MAY then use the value of the <launch:claimKey> element to obtain Trademark Claims Notice information from Trademark Validator based on the Validator Identifier. 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 does not contain any child elements with the "Trademark Check Form":

Example Trademark Check command using the <check> domain command and the <launch:check> extension with the "type" set to "trademark", to determine if "domain1.example", "domain2.example", and "domain3.example" have any matching trademarks: C: C: C: C: C: domain1.example C: domain2.example C: domain3.example C: C: C: C: C: C: ABC-12345 C: C:]]> If the <check> command has been processed successfully, the EPP <response> MUST contain an <extension> <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements: 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. Zero or more OPTIONAL claim keys that MAY be passed to a third-party trademark validator such as the Trademark Clearinghouse (TMCH) for querying the information needed to generate a Trademark Claims Notice. The <launch: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. The OPTIONAL "validatorID" attribute is the Validator Identifier whose value indicates which Trademark Validator to query for the Claims Notice information, with the default being the ICANN TMCH. The "validatorID" attribute MAY reference a non-trademark claims clearinghouse identifer to support other forms of claims notices.

Example Trademark Check response when no matching trademarks are found for the domain name domain1.example, matching trademarks are found for the domain name domain2.example in the "tmch", matching trademarks are found for domain name domain3.example in the "tmch" and "custom-tmch", for the "claims" launch phase: S: S: S: S: Command completed successfully S: S: S: S: S: domain1.example S: S: S: domain2.example S: S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: S: S: S: domain3.example S: S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001 S: S: S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002 S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

This extension defines additional elements to extend the EPP <info> command and response to be used in conjunction with the EPP domain name mapping. The EPP <info> command is used to retrieve information for a launch phase registration or application. The Application Identifier returned in the <launch:creData> element of the create response is used for retrieving information for a Launch Application. A <launch:info> element is sent along with the regular <info> domain command. The <launch:info> element includes an OPTIONAL "includeMark" boolean attribute, with a default value of "false", to indicate whether or not to include the mark in the response. The <launch:info> element contains the following child elements: The phase during which the application or registration was submitted or is associated with. Server policy defines the phases that are supported. OPTIONAL application identifier of the Launch Application.

Example <info> domain command with the <launch:info> extension to retrieve information for the sunrise application for domain.example and application identifier "abc123": C: C: C: C: C: domain.example C: C: C: C: C: sunrise C: abc123 C: C: C: ABC-12345 C: C:]]>

Example <info> domain command with the <launch:info> extension to retrieve information for the sunrise registration for domain.example: C: C: C: C: C: domain.example C: C: C: C: C: sunrise C: C: C: ABC-12345 C: C:]]> If the query was successful, the server replies with a <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, that matches the associated <info> command <launch:phase>. OPTIONAL Application Identifier of the Launch Application. OPTIONAL status of the Launch Application using one of the supported status values. Zero or more <mark:mark> elements.

Example <info> domain response using the <launch:infData> extension with the mark information: S: S: S: S: Command completed successfully S: S: S: S: domain.example S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: ClientX S: ClientY S: 2012-04-03T22:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: sunrise S: abc123 S: S: S: ... S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S:]]>

There are four forms of the extension to the EPP <create> command that include the Sunrise Create Form, the Claims Create Form, the General Create Form, and the Mixed Create Form. The form is dependent on the supported launch phases as defined below. The EPP <create> command with the "sunrise" launch phase is used to submit a registration with trademark information that can be verified by the server with the <domain:name> value. The Sunrise Create Form is used for the "sunrise" launch phase. The EPP <create> command with the "landrush" launch phase MAY use the General Create Form to explicitly specify the phase and optionally define the expected type of object to create. The EPP <create> command with the "claims" launch phase is used to pass the information associated with the presentation and acceptance of the Claims Notice. The Claims Create Form is used and the General Create Form MAY be used for the "claims" launch phase. The EPP <create> command with the "open" launch phase is undefined but the form supported is up to server policy. Use of the Claims Create Form MAY be used to pass the information associated with the presentation and acceptance of the Claims Notice if required for the domain name. The EPP <create> command with the "custom" launch 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 to verify the trademark information passed by the client. A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element has an OPTIONAL "type" attribute that defines the expected type of object ("application" or "registration") to create. The server SHOULD validate the "type" attribute, when passed, against the type of object that will be created. The <launch:create> element contains the following child elements: The identifier for the launch phase. Zero or more <launch:codeMark> elements. The <launch:codeMark> child elements are defined in the <launch:codeMark> element section. Zero or more <smd:signedMark> elements. The <smd:signedMark> child elements are defined in the <smd:signedMark> element section. Zero or more <smd:encodedSignedMark> elements. The <smd:encodedSignedMark> child elements are defined in the <smd:encodedSignedMark> element section.

The following is an example <create> domain command using the <launch:create> extension, following the "code" validation model, with multiple sunrise codes: C: C: C: C: C: domain.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: sunrise C: C: C: 49FD46E6C4B45C55D4AC C: C: C: 49FD46E6C4B45C55D4AD C: C: C: C: 49FD46E6C4B45C55D4AE C: C: C: C: ABC-12345 C: C:]]>

The following is an example <create> domain command using the <launch:create> extension, following the "mark" validation model, with the mark information: C: C: C: C: C: domainone.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: sunrise C: C: C: ... C: C: C: C: C: ABC-12345 C: C:]]>

The following is an example <create> domain command using the <launch:create> extension, following the "code with mark" validation model, with a code and mark information: C: C: C: C: C: domain.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: sunrise C: C: C: 49FD46E6C4B45C55D4AC C: C: ... C: C: C: C: C: ABC-12345 C: C:]]>

The following is an example <create> domain command using the <launch:create> extension, following the "signed mark" validation model, with the signed mark information for a sunrise application: C: C: C: C: C: domainone.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: sunrise C: C: ... C: C: C: C: ABC-12345 C: C:]]>

The following is an example <create> domain command using the <launch:create> extension, following the "signed mark" validation model, with the base64 encoded signed mark information: C: C: C: C: C: domainone.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: sunrise C: C: ... C: C: C: C: ABC-12345 C: C:]]>

The Claims Create Form of the extension to the EPP domain name mapping includes the information related to the registrant's acceptance of the Claims Notice. A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element has an OPTIONAL "type" attribute that defines the expected type of object ("application" or "registration") to create. The server SHOULD validate the "type" attribute, when passed, against the type of object that will be created. The <launch:create> element contains the following child elements: Contains the value of the active launch phase of the server. The server SHOULD validate the value against the active server launch phase. One or more <launch:notice> elements that contain the following child elements: Unique notice identifier for the Claims Notice. The <launch:noticeID> element has an OPTIONAL "validatorID" attribute is the Validator Identifier whose value indicates which Trademark Validator is the source of the claims notice, with the default being the ICANN TMCH. Expiry of the claims notice. Contains the date and time that the claims notice was accepted.

The following is an example <create> domain command using the <launch:create> extension with the <launch:notice> information for the "tmch" and the "custom-tmch" validators, for the "claims" launch phase: C: C: C: C: C: domain.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: claims C: C: C: 370d0b7c9223372036854775807 C: 2014-06-19T10:00:00.0Z C: C: 2014-06-19T09:00:00.0Z C: C: C: C: C: 470d0b7c9223654313275808 C: 2014-06-19T10:00:00.0Z C: C: 2014-06-19T09:00:30.0Z C: C: C: C: C: ABC-12345 C: C:]]>

The General Create Form of the extension to the EPP domain name mapping includes the launch phase and optionally the object type to create. The OPTIONAL "type" attribute defines the expected type of object ("application" or "registration") to create. The server SHOULD validate the "type" attribute, when passed, against the type of object that will be created. A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element contains the following child elements: Contains the value of the active launch phase of the server. The server SHOULD validate the value against the active server launch phase.

The following is an example <create> domain command using the <launch:create> extension for a "landrush" launch phase application: C: C: C: C: C: domain.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: landrush C: C: C: ABC-12345 C: C:]]>

The Mixed Create Form supports a mix of the create forms, where for example the Sunrise Create Form and the Claims Create Form MAY be supported in a single command by including both the verified trademark information and the information related to the registrant's acceptance of the Claims Notice. The server MAY support the Mixed Create Form. The "custom" launch phase SHOULD be used when using the Mixed Create Form.

The following is an example <create> domain command using the <launch:create> extension, with using a mix of the Sunrise Create Form and the Claims Create Form by including both a mark and a notice: C: C: C: C: C: domainone.example C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: custom C: C: C: ... C: C: C: C: C: 49FD46E6C4B45C55D4AC C: C: 2012-06-19T10:00:10.0Z C: C: 2012-06-19T09:01:30.0Z C: C: C: C: C: ABC-12345 C: C:]]>

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 are 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: S: S: S: S: Command completed successfully; action pending S: S: S: S: domain.example S: 2010-08-10T15:38:26.623854Z S: S: S: S: S: sunrise S: 2393-9323-E08C-03B1 S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: ]]>

This extension defines additional elements to extend the EPP <update> command to be used in conjunction with the domain name mapping. A client MUST NOT pass the extension on an EPP <update> command to a server that does not support launch applications. A server that does not support launch applications during its launch phase MUST return an EPP error result code of 2102 when receiving an EPP <update> command with the extension. Registry policies permitting, clients may update an application object by submitting an EPP <update> command along with a <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.

The 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": C: C: C: C: C: domain.example C: C: C: ns2.domain.example C: C: C: C: C: ns1.domain.example C: C: C: C: C: C: C: sunrise C: abc123 C: C: C: ABC-12345 C: C: ]]> 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 name mapping.

This extension defines additional elements to extend the EPP <delete> command to be used in conjunction with the domain name mapping. A client MUST NOT pass the extension on an EPP <delete> command to a server that does not support launch applications. A server that does not support launch applications during its launch phase MUST return an EPP error result code of 2102 when receiving an EPP <delete> command with the extension. Registry policies permitting, clients MAY withdraw an application by submitting an EPP <delete> command along with a <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.

The following is an example <delete> domain command with the <launch:delete> extension: C: C: C: C: C: domain.example C: C: C: C: C: sunrise C: abc123 C: C: C: ABC-12345 C: C: ]]> This extension does not define any extension to the response of a <delete> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping.

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.

One schema is presented here that is the EPP Launch Phase Mapping schema. 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]]>

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . Registration request for the launch namespace: URI: urn:ietf:params:xml:ns:launch-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the launch XML schema: URI: urn:ietf:params:xml:schema:launch-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document.

The EPP extension described in this document should be registered by the IANA in the EPP Extension Registry described in . The details of the registration are as follows: Name of Extension: "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)" Document status: Standards Track Reference: (insert reference to RFC version of this document) Registrant Name and Email Address: IESG, <iesg@ietf.org> TLDs: Any IPR Disclosure: None Status: Active Notes: None

Note to RFC Editor: Please remove this section and the reference to RFC 6982 before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 6982. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 6982, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Organization: Verisign Inc. Name: Verisign EPP SDK Description: The Verisign EPP SDK includes both a full client implementation and a full server stub implementation of draft-ietf-regext-launchphase. Level of maturity: Production Coverage: All aspects of the protocol are implemented. Licensing: GNU Lesser General Public License Contact: jgould@verisign.com URL: http://www.verisigninc.com/en_US/channel-resources/domain-registry-products/epp-sdks

Organization: Verisign Inc. Name: Verisign Consolidated Top Level Domain (CTLD) Shared Registry System (SRS) Description: The Verisign Consolidated Top Level Domain (CTLD) Shared Registry System (SRS) implements the server-side of draft-ietf-regext-launchphase for a variety of Top Level Domains (TLD's). Level of maturity: Production Coverage: The "signed mark" Mark Validation Model, the Claims Check Form for the EPP <check> Command, the Sunrise and Claims Forms for the EPP <create> Command of Launch Registrations and Launch Applications. For Launch Applications the Poll Messaging, the EPP <info> Command, the EPP <update> Command, and the EPP <delete> Command is covered. Licensing: Proprietary Contact: jgould@verisign.com

Organization: Verisign Inc. Name: Verisign .COM / .NET Shared Registry System (SRS) Description: The Verisign Shared Registry System (SRS) for .COM, .NET and other IDN TLD's implements the server-side of draft-ietf-regext-launchphase. Level of maturity: Operational Test Environment (OTE) Coverage: The "signed mark" Mark Validation Model, the Claims Check Form for the EPP <check> Command, the Sunrise and Claims Forms for the EPP <create> Command of Launch Registrations. Licensing: Proprietary Contact: jgould@verisign.com

Organization: Domain Name Services (Pty) Ltd Name: REngin v3.7 Description: Server side implementation only Level of maturity: Production Coverage: All features from version 12 have been implemented Licensing: Proprietary Licensing with Maintenance Contracts Contact: info@dnservices.co.za URL: https://www.registry.net.za and soon http://dnservices.co.za

Organization: CentralNic Name: RegistryEngine EPP Service Description: Generic high-volume EPP service for gTLDs, ccTLDs and SLDs Level of maturity: Deployed in CentralNic's production environment as well as two other gTLD registry systems, and two ccTLD registry systems. Coverage: Majority of elements including TMCH sunrise, landrush and TM claims as well as sunrise applications validated using codes. Licensing: Proprietary In-House software Contact: epp@centralnic.com URL: https://www.centralnic.com

Organization: Neustar Name: Neustar EPP SDK Description: The Neustar EPP SDK includes client implementation of draft-ietf-regext-launchphase in both Java and C++. Level of maturity: Production Coverage: All aspects of the protocol are implemented. Licensing: GNU Lesser General Public License Contact: trung.tran@neustar.biz

Organization: Stichting Internet Domeinnaamregistratie Nederland (SIDN) Name: gTLD Shared Registry System Description: The gTLD SRS implements the server side of the draft-ietf-regext-launchphase. Level of maturity: (soon) Production Coverage: The following parts of the draft are supported: Signed mark validation model using Digital Signature Claims Check Form Sunrise Create Form Claims Create Form The parts of the document not described here are not implemented. Licensing: Proprietary Contact: rik.ribbers@sidn.nl

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 2201 (authorization error) return code. 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.

The authors wish to acknowledge the efforts of the leading participants of the Community TMCH Model that led to many of the changes to this document, which include Chris Wright, Jeff Neuman, Jeff Eckhaus, and Will Shorter. Special suggestions that have been incorporated into this document were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Michael Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike O'Connell, Bernhard Reutner-Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski.

&RFC2119; &RFC3688; &RFC5730; &RFC5731; &RFC6982; &RFC7451; &RFC7848; &I-D.ietf-regext-tmch-func-spec;

Changed to use camel case for the XML elements. Replaced "cancelled" status to "rejected" status. Added the child elements of the <claim> element. Removed the XML schema and replaced with "[TBD]".

Added support for both the ICANN and ARI/Neustar TMCH models. Changed the namespace URI and prefix to use "launch" instead of "launchphase". Added definition of multiple claim validation models. Added the <launch:signedClaim> and <launch:signedNotice> elements. Added support for Claims Info Command

Removed XSI namespace per Keith Gaughan's suggestion on the provreg list. Added extensibility to the launch:status element and added the pendingAuction status per Trung Tran's feedback on the provreg list. Added support for the Claims Check Command, updated the location and contents of the signedNotice, and replaced most references of Claim to Mark based on the work being done on the ARI/Neustar launch model.

Removed references to the ICANN model. Removed support for the Claims Info Command. Removed use of the signedClaim. Revised the method for referring to the signedClaim from the XML Signature using the IDREF URI. Split the launch-1.0.xsd into three XML schemas including launch-1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd. Split the "claims" launch phase to the "claims1" and "claims2" launch phases. Added support for the encodedSignedMark with base64 encoded signedMark. Changed the elements in the createNoticeType to include the noticeID, timestamp, and the source elements. Added the class and effectiveDate elements to mark.

Removed reference to <smd:zone> in the <smd:signedMark> example. Incorporated feedback from Bernhard Reutner-Fischer on the provreg mail list. Added missing launch XML prefix to applicationIDType reference in the idContainerType of the Launch Schema. Added missing description of the <mark:pc> element in the <mark:addr> element. Updated note on replication of the EPP contact mapping elements in the Mark Contact section.

Removed the definition of the mark-1.0 and signedMark-1.0 and replaced with reference to draft-lozano-smd, that contains the definition for the mark, signed marked, and encoded signed mark. Split the <launch:timestamp> into <launch:generatedDate> and <launch:acceptedDate> based on feedback from Trung Tran. Added the "includeMark" optional attribute to the <launch:info> element to enable the client to request whether or not to include the mark in the info response. Fixed state diagram to remove redundant transition from "invalid" to "rejected"; thanks Klaus Malorny.

Proof-read grammar and spelling. Changed "pendingAuction" status to "pendingAllocation", changed "pending" to "pendingValidation" status, per proposal from Trung Tran and seconded by Rubens Kuhl. Added text related to the use of RFC 5731 pendingCreate to the Application Identifier section. Added the Poll Messaging section to define the use of poll messaging for intermediate state transitions and pending action poll messaging for final state transitions.

Added support for use of the launch statuses and poll messaging for Launch Registrations based on feedback from Sharon Wodjenski and Trung Tran. Incorporated changes based on updates or clarifications in draft-lozano-tmch-func-spec-01, which include: Removed the unused <launch:generatedDate> element. Removed the <launch:source> element. Added the <launch:notAfter> element based on the required <tmNotice:notAfter> element.

Made <choice> element optional in <launch:create> to allow passing just the <launch:phase> in <launch:create> per request from Ben Levac. Added optional "type" attribute in <launch:create> to enable the client to explicitly define the desired type of object (application or registration) to create to all forms of the create extension. Added text that the server SHOULD validate the <launch:phase> element in the Launch Phases section. Add the "General Create Form" to the create command extension to support the request from Ben Levac. Updated the text for the Poll Messaging section based on feedback from Klaus Malorny. Replaced the "claims1" and "claims2" phases with the "claims" phase based on discussion on the provreg list. Added support for a mixed create model (Sunrise Create Model and Claims Create Model), where a trademark (encoded signed mark, etc.) and notice can be passed, based on a request from James Mitchell. Added text for the handling of the overlapping "claims" and "landrush" launch phases. Added support for two check forms (claims check form and availability check form) based on a request from James Mitchell. The availability check form was based on the text in draft-rbp-application-epp-mapping.

Changed noticeIDType from base64Binary to token to be compatible with draft-lozano-tmch-func-spec-05. Changed codeType from base64Binary to token to be more generic. Updated based on feedback from Alexander Mayrhofer, which include: Changed "extension to the domain name extension" to "extension to the domain name mapping". Changed use of 2004 return code to 2306 return code when phase passed mismatches active phase and sub-phase. Changed description of "allocated" and "rejected" statuses. Moved sentence on a synchronous <domain:create> command without the use of an intermediate application, then an Application Identifier MAY not be needed to the Application Identifier section. Restructured the Mark Validation Models section to include the "<launch:codeMark> element" sub-section, the "<mark:mark> element" sub-section, and the Digital Signature sub-section. Changed "Registries may" to "Registries MAY". Changed "extensed" to "extended" in "Availability Check Form" section. Broke the mix of create forms in the "EPP <create> Command" section to a fourth "Mixed Create Form" with its own sub-section. Removed "displayed or" from "displayed or accepted" in the <launch:acceptedDate> description. Replaced "given domain name is supported" with "given domain name are supported" in the "Create Response" section. Changed the reference of 2303 (object does not exist) in the "Security Considerations" section to 2201 (authorization error). Added arrow from "invalid" status to "pendingValidation" status and "pendingAllocation" status to "rejected" status in the State Transition Diagram. Added the "C:" and "S:" example prefixes and related text in the "Conventions Used in This Document" section.

Moved the claims check response <launch:chkData> element under the <extension> element instead of the <resData> element based on the request from Francisco Obispo.

Added support for multiple validator identifiers for claims notices and marks based on a request and text provided by Mike O'Connell. Removed domain:exDate element from example in section 3.3.5 based on a request from Seth Goldman on the provreg list. Added clarifying text for clients not passing the launch extension on update and delete commands to servers that do not support launch applications based on a request from Sharon Wodjenski on the provreg list.

Changed to eppext working group draft by changing draft-tan-epp-launchphase to draft-ietf-eppext-launchphase and by changing references of draft-lozano-tmch-smd to draft-ietf-eppext-tmch-smd.

Removed text associated with support for the combining of status values based on feedback from Patrick Mevzek on the provreg mailing list, discussion on the eppext mailing list, and discussion at the eppext IETF meeting on March 6, 2014.

Changed the <launch:claim> element to be zero or more elements and the <launch:notice> element to be one or more elements in the Claims Create Form. These changes were needed to be able to support more than one concurrent claims services.

Added the "Implementation Status" section based on an action item from the eppext IETF-91 meeting. Moved Section 7 "IANA Considerations" and Section 9 "Security Considerations" before Section 5 "Acknowledgements". Moved "Change Log" Section to end. Updated the text for the Claims Check Form and the Claims Create Form to support checking for the need of the claims notice and passing the claims notice outside of the "claims" phase. Added the new Trademark Check Form to support determining whether or not a trademark exists that matches the domain name independent of whether a claims notice is required on create. This was based on a request from Trung Tran and a discussion on the eppext mailing list.

Amended XML Namespace section of IANA Considerations, added EPP Extension Registry section.

Added a missing comma to the descripton of the <launch:phase> element, based on feedback from Keith Gaughan on the eppext mailing list. Added the SIDN implementation status information. Fixed a few indentation issues in the samples.

Removed duplicate "TMCH Functional Specification" URIs based on feedback from Scott Hollenbeck on the eppext mailing list. Changed references of example?.tld to domain?.example to be consistent with RFC 6761 based on feedback from Scott Hollenbeck on the eppext mailing list. A template was added to section 5 to register the XML schema in addition to the namespace based on feedback from Scott Hollenbeck on the eppext mailing list.

Changed reference of lozano-tmch-func-spec to ietf-eppext-tmch-func-spec.

Changed to regext working group draft by changing draft-ietf-eppext-launchphase to draft-ietf-regext-launchphase and by changing references of draft-ietf-eppext-tmch-func-spec to draft-ietf-regext-tmch-func-spec.

Fixed reference of Claims Check Command to Trademark Check Command in the Trademark Check Form section. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848.