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. 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, referred to as a launch application. A launch registration is used to refer to a registration made during a launch phase when the server uses a first-come-first-serve model. Even in a first-come-first-serve model additional steps and information might be required to support a launch phase, like the passing of trademark information on a create. In addition, the Proposed Trademark Claims 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. "signedMark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:signedMark-1.0". 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". 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 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 with steps taken to address a large volume of initial registrations. Trademark claims phase 1 as defined by Trademark Clearinghouse model of displaying a full, detailed claims notice to clients for domain names that match trademarks. Trademark claims phase 2 as defined by Trademark Clearinghouse model of displaying a short, educational claims notice to clients for domain names that match trademarks that opt into the service. 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. For example, the "claims1" launch phase could have two sub-phases that include "landrush" and "open".

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 "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. 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 it's 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 <launch:mark> information. The mark code can be a mark specific secret value that the server can verify against a third party. 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 <launch:mark> element. 49FD46E6C4B45C55D4AC Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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 <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 child elements of the <mark: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 <mark:label> values. Zero or more domain name labels that corresponds to the <mark:name>. Each <mark: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 applicant's entitlement to the mark (owner, licensee, etc.) zero or more Nice Classification class numbers as defined in the Nice List of Classes indicates the applicant's entitlement to the mark (owner, licensee, etc.) the date of registration / application of the mark the date the mark becomes effective 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 <mark:owner> or <mark:contact> elements include: 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 <mark:addr> element contains the following child elements: zero to three <mark: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 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 digital signatures are handled using an XML Signature around the entire <smd:signedMark> element. The <smd:encodedSignedMark> element includes an encoded form of the <smd:signedMark> element like the use of "base64" encoding. Once the digital signature is validated using the appropriate public key, the server can trust all of the information included in the <smd:signedMark> element. It's up to server policy how the public key is transferred. To have the digital signature cover all of the elements of the <smd:signedMark> element, the XML Signature IDREF URI is set to the "id" attribute value of the <smd:signedMark> element and the Transform "http://www.w3.org/2000/09/xmldsig#enveloped-signature" is used. The digital signature covers the <smd:signedMark> element and the Signature element is embedded in the <smd:signedMark> element.

The <smd:signedMark> is the fragment of XML that is digitally signed using XML Signature. The <smd:signedMark> includes a required "id" attribute of type XSD ID for use with an IDREF URI from the Signature element. The child elements of the <smd:signedMark> element include: Signature serial number that that can be compared with a revocation list by the server. OPTIONAL date and time that the <smd:signedMark> expires. The server MUST NOT accept a <smd:signedMark> that has expired. No <smd:exDate> element indicates that there is no expiry. Trademark information as defined in the Mark section. XML Signature for the <smd:signedMark>. Use of a namespace prefix, like "dsig", is recommended for the "http://www.w3.org/TR/xmldsig-core/" elements.

The following is an example <smd:signedMark> using the XML Signature to sign all of the elements of <smd:signedMark> element. 123456 newtld 2012-08-16T09:00:00.0Z Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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 6651T5s9GZgQOxifdCFmDfSIoUc= Gm7RnEb6jcijKcgmwEmxJ6j1L0vt2wFyXv3oKc9 a4b8nMOKdec8S3tG2hSx/NZa0RFHvx5zMsH/M jmxzrTBbl5d7W8Qql5VsW4XanSjJ+UgILs9k6XgVtZE2EvffMLBiL4xbCJM48ew RYRY7lVEzoNms91pmm3U5IlNRNjU/YFqZ1pXhhrhyhPjSi9Uon8FnAJaiBEfHcj G6815IJV/9RT+MTXri7i0s82CqIS4wDGbGpyZAs7/kDY3A3upqSOwTtrFSCFX1F +Craec72lBB/dKJHxmoVkbIO5KQhqIOd+E+h2kguE++RHKa4xoBIeyTgWqpWcLu MoFpM+GxwFcpSA== ]]>

The <smd:encodedSignedMark> element contains an encoded form of the digitally signed <smd:signedMark> element, described in , with the encoding defined by the "encoding" attribute with the default "encoding" value of "base64". The "base64" encoded text of the <smd:encodedSignedMark> element MUST conform to .

The following is an example an <smd:encodedSignedMark> element that uses the default "base64" for encoding a <smd:signedMark> element. D94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c21kOnN pZ25lZE1hcmsgeG1sbnM6c21kPSJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zO nNpZ25lZE1hcmstMS4wIiBpZD0ic2lnbmVkTWFyayI-PHNtZDpzZXJpYWw -MTIzNDU2PC9zbWQ6c2VyaWFsPjxzbWQ6ZXhEYXRlPjIwMTItMTEtMjlUM Tg6MTY6NTQuMDg4MFo8L3NtZDpleERhdGU-PG1hcms6bWFyayB4bWxuczp tYXJrPSJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOm1hcmstMS4wIj48bWFya zpuYW1lPkV4YW1wbGUgT25lPC9tYXJrOm5hbWU-PG1hcms6bGFiZWw-ZXh hbXBsZS1vbmU8L21hcms6bGFiZWw-PG1hcms6bGFiZWw-ZXhhbXBsZW9uZ TwvbWFyazpsYWJlbD48bWFyazppc3N1ZXI-SVAgQ2xlYXJpbmdob3VzZTw vbWFyazppc3N1ZXI-PG1hcms6bnVtYmVyPkdFIDM5MzMyMzI8L21hcms6b nVtYmVyPjxtYXJrOm51bWJlcj5vd25lcjwvbWFyazpudW1iZXI-PG1hcms 6cmVnRGF0ZT4yMDEyLTExLTI5VDE4OjE2OjU0LjA3NDZaPC9tYXJrOnJlZ 0RhdGU-PG1hcms6ZXhEYXRlPjIwMTItMTEtMjlUMTg6MTY6NTQuMDc0Nlo 8L21hcms6ZXhEYXRlPjxtYXJrOmNvdW50cnk-QVU8L21hcms6Y291bnRye T48bWFyazpyZWdpb24-VklDPC9tYXJrOnJlZ2lvbj48L21hcms6bWFyaz4 8ZHNpZzpTaWduYXR1cmUgeG1sbnM6ZHNpZz0iaHR0cDovL3d3dy53My5vc mcvMjAwMC8wOS94bWxkc2lnIyI-PGRzaWc6U2lnbmVkSW5mbz48ZHNpZzp DYW5vbmljYWxpemF0aW9uTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3d y53My5vcmcvVFIvMjAwMS9SRUMteG1sLWMxNG4tMjAwMTAzMTUjV2l0aEN vbW1lbnRzIi8-PGRzaWc6U2lnbmF0dXJlTWV0aG9kIEFsZ29yaXRobT0ia HR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnI3JzYS1zaGExIi8 -PGRzaWc6UmVmZXJlbmNlIFVSST0iI3NpZ25lZE1hcmsiPjxkc2lnOlRyY W5zZm9ybXM-PGRzaWc6VHJhbnNmb3JtIEFsZ29yaXRobT0iaHR0cDovL3d 3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnI2VudmVsb3BlZC1zaWduYXR1c mUiLz48L2RzaWc6VHJhbnNmb3Jtcz48ZHNpZzpEaWdlc3RNZXRob2QgQWx nb3JpdGhtPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3htbGRzaWcjc 2hhMSIvPjxkc2lnOkRpZ2VzdFZhbHVlPktIdVFrdFdUMnRYbXg4Y2ZWd2N vZ0JSUm5oRT08L2RzaWc6RGlnZXN0VmFsdWU-PC9kc2lnOlJlZmVyZW5jZ T48L2RzaWc6U2lnbmVkSW5mbz48ZHNpZzpTaWduYXR1cmVWYWx1ZT5RdWk 2d2xLVUlRcHMxS2N6ajhUaTVuNTBjaTVDc2pML2k2YjBwS0Z2NG16ZENhc WpWcXVvVDFiSzJCZnhKNG0rbXJiOWxLeFlrVnNFCnB4QnloSG5KSHpSMXV 1MG1NMmt4VURyWkVCc0dpV3FuaHMzQVBxOTJBcVdGZHZnUmV6ZHcycmNVb Vg3dGJyeWNGM3ZDMEJmRUg4RHoKb2FIUFRQb24xTUxObzF5bGtYTDA5bWJ qTHVhRlJSS3Z2UCs4djQ1VFJXRmkrbVJ0akJvMGg4blFiNTNtR2lKaU1Oe kFDaDBtK3pFeAp2bmxEUmRpdWJFZVVWbG9LV2dMY1BiSkd4QmFWL1gvQjQ vRnVRbXEzclcxaXNZOUlEYzA3U3ZheEZ0a1l4emVra25GQkNCSWNibXFTC nlOckMvOEp4Y2RRSHN0TUZWc1Z2SjdWUFJqS2VZM0RLcUwrTGhRPT08L2R zaWc6U2lnbmF0dXJlVmFsdWU-PC9kc2lnOlNpZ25hdHVyZT48L3NtZDpza WduZWRNYXJrPg ]]>

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, in the specified launch phase, for each domain name passed in the command. The availability check information defined in the EPP domain name mapping MUST NOT be returned for the Claims Check Command. 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. 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 an 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 unique notice identifier that can 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: The phase with the value of "claims1" or "claims2" to indicate it as a Claims Check Command. The "claims1" Claims Check Command will match the <domain:name> against the full list of trademark labels and the "claims2" Claims Check Command will match the <domain:name> against the list of trademark labels that opted into the "claims2" launch phase.

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 during the "claims1" launch phase. example1.tld example2.tld claims1 ABC-12345 ]]>

Example Claims Check Command using the <check> domain command and the <launch:check> extension to determine if "example3.tld" and "example4.tld" have any matching trademarks that opted into the "claims2" launch phase. example3.tld example4.tld claims2 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 "claims1" or "claims2" that matches the associated Claims Check Command <launch:phase>. 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 for the claims launch phase. A value of "0" or "false" means that a matching trademark does not exist. An OPTIONAL claim key that MAY be passed to an 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 <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.

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 for the "claims1" launch phase. Command completed successfully claims1 example1.tld example2.tld abc123 ABC-12345 54322-XYZ ]]>

Example Claims Check Response when no matching trademarks are found for the domain name example3.tld and matching trademarks are found for the domain name example4.tld for the "claims2" launch phase. Command completed successfully claims2 example3.tld example4.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. 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 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 example.tld and application identifier "abc123". example.tld sunrise abc123 ABC-12345 ]]>

Example <info> domain command with the <launch:info> extension to retrieve information for the sunrise registration for example.tld. example.tld sunrise 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 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. The <mark:mark> child elements are defined in the <mark:mark> element section.

Example <info> domain response using the <launch:infData> extension with the mark information. Command completed successfully example.tld EXAMPLE1-REP jd1234 sh8013 sh8013 ClientX ClientY 2012-04-03T22:00:00.0Z 2fooBAR sunrise abc123 Hello IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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" launch phase is used to submit an 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. 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" launch phase is undefined but the form supported is up to server policy. The EPP <create> command with the "claims1" launch phase is used to pass the information associated with the presentation and acceptance of the "claims1" claims notice. The Claims Create Form is used for the "claims1" launch phase. The EPP <create> command with the "claims2" launch phase is used to pass the information associated with the presentation of the "claims1" claims notice. The Claims Create Form is used for the "claims2" launch phase. The EPP <create> command with the "open" launch phase is undefined but the form supported is up to server policy. 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 contains the following child elements: The launch phase for the create like the "sunrise" 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.

Following is an example <create> domain command using the <launch:create> extension, following the "code" validation model, 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, following the "mark" validation model, with the mark information. exampleone.tld jd1234 sh8013 sh8013 2fooBAR sunrise Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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, following the "code with mark" validation model, with a code and mark information. example.tld jd1234 sh8013 sh8013 2fooBAR sunrise 49FD46E6C4B45C55D4AC Hello IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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, following the "signed mark" validation model, with the signed mark information. exampleone.tld jd1234 sh8013 sh8013 2fooBAR sunrise 123456 2012-08-16T09:00:00.0Z Example One example-one exampleone IP Clearinghouse GE 3933232 REG-TM-WORD 1 owner 2011-09-09 2011-10-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 6651T5s9GZgQOxifdCFmDfSIoUc= Gm7RnEb6jcijKcgmwEmxJ6j1L0vt2wFyXv3oKc9a4b8nMOKdec8S3tG2hSx /NZa0RFHvx5zMsH/MjmxzrTBbl5d7W8Qql5VsW4XanSjJ+UgILs9k6XgVtZ E2EvffMLBiL4xbCJM48ewRYRY7lVEzoNms91pmm3U5IlNRNjU/YFqZ1pXhh rhyhPjSi9Uon8FnAJaiBEfHcjG6815IJV/9RT+MTXri7i0s82CqIS4wDGbG pyZAs7/kDY3A3upqSOwTtrFSCFX1F+Craec72lBB/dKJHxmoVkbIO5KQhqI Od+E+h2kguE++RHKa4xoBIeyTgWqpWcLuMoFpM+GxwFcpSA== ABC-12345 ]]>

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. exampleone.tld jd1234 sh8013 sh8013 2fooBAR sunrise D94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c21kOnNpZ25 lZE1hcmsgeG1sbnM6c21kPSJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOnNpZ25lZ E1hcmstMS4wIiBpZD0ic2lnbmVkTWFyayI-PHNtZDpzZXJpYWw-MTIzNDU2PC9 zbWQ6c2VyaWFsPjxzbWQ6ZXhEYXRlPjIwMTItMTEtMjlUMTg6MTY6NTQuMDg4M Fo8L3NtZDpleERhdGU-PG1hcms6bWFyayB4bWxuczptYXJrPSJ1cm46aWV0Zjp wYXJhbXM6eG1sOm5zOm1hcmstMS4wIj48bWFyazpuYW1lPkV4YW1wbGUgT25lP C9tYXJrOm5hbWU-PG1hcms6bGFiZWw-ZXhhbXBsZS1vbmU8L21hcms6bGFiZWw -PG1hcms6bGFiZWw-ZXhhbXBsZW9uZTwvbWFyazpsYWJlbD48bWFyazppc3N1Z XI-SVAgQ2xlYXJpbmdob3VzZTwvbWFyazppc3N1ZXI-PG1hcms6bnVtYmVyPkd FIDM5MzMyMzI8L21hcms6bnVtYmVyPjxtYXJrOm51bWJlcj5vd25lcjwvbWFya zpudW1iZXI-PG1hcms6cmVnRGF0ZT4yMDEyLTExLTI5VDE4OjE2OjU0LjA3NDZ aPC9tYXJrOnJlZ0RhdGU-PG1hcms6ZXhEYXRlPjIwMTItMTEtMjlUMTg6MTY6N TQuMDc0Nlo8L21hcms6ZXhEYXRlPjxtYXJrOmNvdW50cnk-QVU8L21hcms6Y29 1bnRyeT48bWFyazpyZWdpb24-VklDPC9tYXJrOnJlZ2lvbj48L21hcms6bWFya z48ZHNpZzpTaWduYXR1cmUgeG1sbnM6ZHNpZz0iaHR0cDovL3d3dy53My5vcmc vMjAwMC8wOS94bWxkc2lnIyI-PGRzaWc6U2lnbmVkSW5mbz48ZHNpZzpDYW5vb mljYWxpemF0aW9uTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmc vVFIvMjAwMS9SRUMteG1sLWMxNG4tMjAwMTAzMTUjV2l0aENvbW1lbnRzIi8-P GRzaWc6U2lnbmF0dXJlTWV0aG9kIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5 vcmcvMjAwMC8wOS94bWxkc2lnI3JzYS1zaGExIi8-PGRzaWc6UmVmZXJlbmNlI FVSST0iI3NpZ25lZE1hcmsiPjxkc2lnOlRyYW5zZm9ybXM-PGRzaWc6VHJhbnN mb3JtIEFsZ29yaXRobT0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc 2lnI2VudmVsb3BlZC1zaWduYXR1cmUiLz48L2RzaWc6VHJhbnNmb3Jtcz48ZHN pZzpEaWdlc3RNZXRob2QgQWxnb3JpdGhtPSJodHRwOi8vd3d3LnczLm9yZy8yM DAwLzA5L3htbGRzaWcjc2hhMSIvPjxkc2lnOkRpZ2VzdFZhbHVlPktIdVFrdFd UMnRYbXg4Y2ZWd2NvZ0JSUm5oRT08L2RzaWc6RGlnZXN0VmFsdWU-PC9kc2lnO lJlZmVyZW5jZT48L2RzaWc6U2lnbmVkSW5mbz48ZHNpZzpTaWduYXR1cmVWYWx 1ZT5RdWk2d2xLVUlRcHMxS2N6ajhUaTVuNTBjaTVDc2pML2k2YjBwS0Z2NG16Z ENhcWpWcXVvVDFiSzJCZnhKNG0rbXJiOWxLeFlrVnNFCnB4QnloSG5KSHpSMXV 1MG1NMmt4VURyWkVCc0dpV3FuaHMzQVBxOTJBcVdGZHZnUmV6ZHcycmNVbVg3d GJyeWNGM3ZDMEJmRUg4RHoKb2FIUFRQb24xTUxObzF5bGtYTDA5bWJqTHVhRlJ SS3Z2UCs4djQ1VFJXRmkrbVJ0akJvMGg4blFiNTNtR2lKaU1OekFDaDBtK3pFe Ap2bmxEUmRpdWJFZVVWbG9LV2dMY1BiSkd4QmFWL1gvQjQvRnVRbXEzclcxaXN ZOUlEYzA3U3ZheEZ0a1l4emVra25GQkNCSWNibXFTCnlOckMvOEp4Y2RRSHN0T UZWc1Z2SjdWUFJqS2VZM0RLcUwrTGhRPT08L2RzaWc6U2lnbmF0dXJlVmFsdWU -PC9kc2lnOlNpZ25hdHVyZT48L3NtZDpzaWduZWRNYXJrPg 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 for the "claims1" launch phase and the display of the claims notice for the "claims2" launch phase. 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 "claims1" or "claim2" to indicate the claims launch phase. Unique notice identifier generated by the source of the claims notice information like the Claims Notice Information Service (CNIS). Contains the date and time that the claims notice was displayed or accepted. Contains the source information of the client that was displayed or that accepted the claims notice like the client IP address.

Following is an example <create> domain command using the <launch:create> extension with the <launch:notice> information for the "claims1" claims launch phase. example.tld jd1234 sh8013 sh8013 2fooBAR claims1 49FD46E6C4B45C55D4AC 2012-06-19T09:00:00.0Z 192.0.2.29 ABC-12345 ]]> This extension does not define any extension to the response of an <create> domain command for the Claims Create Form. After processing the command, the server replies with a standard EPP response as defined in the EPP domain mapping.

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

Three schemas are presented here. The first schema is the EPP Launch Phase Mapping schema. The second schema is a dependent schema for the Signed Mark. The third schema is a dependent schema for the Mark. 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]]>

Schema for representing a Signed Mark, also referred to as Signed Mark Data (SMD), that includes digitally signed trademark information. END]]>

Schema for representing a Trademark, also referred to as Mark. END]]>

[to be filled in]

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.

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . Three URI assignments have been registered by the IANA. 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 Signed mark namespace: URI: urn:ietf:params:xml:ns:signedMark-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 Mark namespace: URI: urn:ietf:params:xml:ns:mark-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification.

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.