Internet Engineering Task Force J. XIE Internet-Draft CONAC Intended status: Informational June 16, 2013 Expires: December 18, 2013 Extensible Provisioning Protocol (EPP) Trademark Mapping draft-xie-epp-trademark-mapping-00 Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of trademark stored in a trademark clearinghouse. Specified in XML, the mapping defines EPP command syntax and semantics as applied to trademark. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 18, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. XIE Expires December 18, 2013 [Page 1] Internet-Draft EPP Trademark Mapping June 2013 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Trademark . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Domain Label . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 4 3.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 4 3.5. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6 3.6. Validity Periods . . . . . . . . . . . . . . . . . . . . 6 3.7. Authorization Information . . . . . . . . . . . . . . . . 6 3.8. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 6 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 10 4.1.3. EPP Query Command . . . . . . . . . . . . 14 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 4.2.1. EPP Command . . . . . . . . . . . . . . . . 17 4.2.2. EPP Command . . . . . . . . . . . . . . . . 20 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 21 4.2.4. EPP Command . . . . . . . . . . . . . . . 23 4.2.5. EPP Command . . . . . . . . . . . . . . . . 25 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29 6. Internationalization Considerations . . . . . . . . . . . . . 39 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 8. Security considerations . . . . . . . . . . . . . . . . . . . 40 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 40 10. Change History . . . . . . . . . . . . . . . . . . . . . . . 40 10.1. draft-xie-epp-trademark-mapping: Version 00 . . . . . . 40 11. Normative References . . . . . . . . . . . . . . . . . . . . 40 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 41 1. Introduction XIE Expires December 18, 2013 [Page 2] Internet-Draft EPP Trademark Mapping June 2013 This document describes a trademark mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This document is specified using the Extensible Markup Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. The EPP core protocol specification [RFC5730] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the trademark mapping described in this document. It is typical for the trademark clearinghouse providers to deal business with the trademark owner, agent or thirdparty. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation. 2. Terminology 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 [RFC2119]. "trademark-1.0" in this document is used as an abbreviation for urn:ietf:params:xml:ns:trademark-1.0. 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 specification. "signedMark-1.0" is used as an abbreviation for "urn:ietf:params:xml:ns:signedMark-1.0" that is defined in [draft- lozano-smd]. 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 [draft-lozano- smd]. 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. 3. Object Attributes XIE Expires December 18, 2013 [Page 3] Internet-Draft EPP Trademark Mapping June 2013 An EPP trademark object has attributes and associated values that can be viewed and modified by the sponsoring client or the server. This section describes each attribute type in detail. The formal syntax for the attribute values described here can be found in the "Formal Syntax" section of this document and in the appropriate normative references. 3.1. Trademark Trademark which is a complex object can take 3 forms: Registered Trademark,Court Validated Marks,Marks protected by statute or treaty. 3.2. Domain Label The domain name without its TLD extension.In this text,the domain label means that the label matches a name of a trademark.The identical matching algorithm is beyond the scope of this document. 3.3. Contact and Client Identifiers All EPP contacts are identified by a server-unique identifier. Contact identifiers are character strings with a specified minimum length, a specified maximum length, and a specified format. Contact identifiers use the "clIDType" client identifier syntax described in [RFC5730]. 3.4. Status Values A Trademark object MUST always have at least one associated status value. Status values can be set only by the client that sponsors a trademark object and by the server on which the object resides. A client can change the status of a trademark object using the EPP command. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. A client MUST NOT alter status values set by the server. A server MAY alter or override status values set by a client, subject to local server policies. The status of an object MAY change as a result of either a client-initiated transform command or an action performed by a server operator. Status values that can be added or removed by a client are prefixed with "client". Corresponding status values that can be added or removed by a server are prefixed with "server". Status values that do not begin with either "client" or "server" are server-managed. Status Value Descriptions: XIE Expires December 18, 2013 [Page 4] Internet-Draft EPP Trademark Mapping June 2013 o clientDeleteProhibited, serverDeleteProhibited. Requests to delete the object MUST be rejected. o clientRenewProhibited, serverRenewProhibited. Requests to renew the object MUST be rejected. o clientTransferProhibited, serverTransferProhibited. Requests to transfer the object MUST be rejected. o clientUpdateProhibited, serverUpdateProhibited. Requests to update the object (other than to remove this status) MUST be rejected. o ok. This is the normal status value for an object that has no pending operations or prohibitions. This value is set and removed by the server as other status values are added or removed. o pendingCreate, pendingDelete, pendingRenew, pendingTransfer, pendingUpdate. A transform command has been processed for the object, but the action has not been completed by the server. Server operators can delay action completion for a variety of reasons, such as to allow for human review or third-party action. A transform command that is processed, but whose requested action is pending, is noted with response code 1001. When the requested action has been completed, the pendingCreate, pendingDelete, pendingRenew, pendingTransfer, or pendingUpdate status value MUST be removed. All clients involved in the transaction MUST be notified using a service message that the action has been completed and that the status of the object has changed. "ok" status MUST NOT be combined with any other status. "pendingDelete" status MUST NOT be combined with either "clientDeleteProhibited" or "serverDeleteProhibited" status. "pendingRenew" status MUST NOT be combined with either "clientRenewProhibited" or "serverRenewProhibited" status. "pendingTransfer" status MUST NOT be combined with either "clientTransferProhibited" or "serverTransferProhibited" status. "pendingUpdate" status MUST NOT be combined with either "clientUpdateProhibited" or "serverUpdateProhibited" status. The pendingCreate, pendingDelete, pendingRenew, pendingTransfer, and pendingUpdate status values MUST NOT be combined with each other. XIE Expires December 18, 2013 [Page 5] Internet-Draft EPP Trademark Mapping June 2013 Other status combinations not expressly prohibited MAY be used. 3.5. Dates and Times Date and time attribute values MUST be represented in Universal Coordinated Time (UTC) using the Gregorian calendar. The extended date-time form using upper case "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time values, as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters. 3.6. Validity Periods A trademark object MAY have a specified validity period. If server policy supports trademark-object validity periods, the validity period is defined when a trademark object is created, and it MAY be extended by the EPP or commands. As a matter of server policy, this specification does not define actions to be taken upon expiration of a trademark object's validity period. Validity periods are measured in years or months with the appropriate units specified using the "unit" attribute. Valid values for the "unit" attribute are "y" for years and "m" for months. The minimum allowable period value is one (1). The maximum allowable value is ninety-nine decimal (99). A server MAY support a lower maximum value. 3.7. Authorization Information Authorization information is associated with trademark objects to facilitate transfer operations. Authorization information is assigned when a trademark object is created, and it might be updated in the future. This specification describes password-based authorization information, though other mechanisms are possible. 3.8. Poll Messaging A trademark Registration MAY be in "pendingCreate" status, the server SHOULD insert poll messages, per [RFC5730]. For the applicable intermediate statuses, the server MUST insert a poll message. The following is an example poll message for a trademark Application that has transitioned to the "pendingCreate" state. S: S: XIE Expires December 18, 2013 [Page 6] Internet-Draft EPP Trademark Mapping June 2013 S: S: S: Command completed successfully; ack to dequeue S: S: S: 2013-04-04T22:01:00.0Z S: Trademark created approved. S: S: S: S: 123456-001 S: example S: 2016-01-21T12:00:00.000Z S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 4. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing trademark via EPP. 4.1. EPP Query Commands EPP provides three commands to retrieve trademark information: to determine if a trademark object can be provisioned within a repository, to retrieve detailed information associated with a trademark object, and to retrieve trademark object transfer status information. 4.1.1. EPP Command The EPP command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the command, as object-provisioning requirements are ultimately a matter of server policy. XIE Expires December 18, 2013 [Page 7] Internet-Draft EPP Trademark Mapping June 2013 In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o One or more element that contains an identifier of the trademark. It usually is the application ID registered in the trademark office. Example command: C: C: C: C: C: C: 123456-001 C: 123456-002 C: 123456-003 C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the trademark namespace. The element contains one or more elements that contain the following child elements: o A element that contains an identifier of the queried trademark object. This element MUST contain an "avail" attribute whose value indicates object availability (can it be provisioned or not) at the moment the command was completed. A value of "1" or "true" means that the object can be provisioned. A value of "0" or "false" means that the object can not be provisioned. XIE Expires December 18, 2013 [Page 8] Internet-Draft EPP Trademark Mapping June 2013 o An OPTIONAL element that MAY be provided when an object cannot be provisioned. If present, this element contains server-specific text to help explain why the object cannot be provisioned. This text MUST be represented in the response language previously negotiated with the client; an OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: 123456-001 S: S: S: 123456-002 S: In use S: S: S: 123456-003 S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. XIE Expires December 18, 2013 [Page 9] Internet-Draft EPP Trademark Mapping June 2013 4.1.2. EPP Command The EPP command is used to retrieve information associated with a trademark object. The response to this command MAY vary depending on the identity of the querying client, use of authorization information, and server policy towards unauthorized clients. If the querying client is the sponsoring client, all available information MUST be returned. If the querying client is not the sponsoring client but the client provides valid authorization information, all available information MUST be returned. If the querying client is not the sponsoring client and the client does not provide valid authorization information, server policy determines which OPTIONAL elements are returned. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains an identifier of the trademark object. o An OPTIONAL element that contains authorization information associated with the trademark object or authorization information associated with the trademark object's holder or associated contacts. An OPTIONAL "roid" attribute MUST be used to identify the holder or contact object if and only if the given authInfo is associated with a holder or contact object, and not the trademark object itself. If this element is not provided or if the authorization information is invalid, server policy determines if the command is rejected or if response information will be returned to the client. Example Response: C: C: C: C: C: C: 123456-01 C: C: C: ABC-12345 C: C: XIE Expires December 18, 2013 [Page 10] Internet-Draft EPP Trademark Mapping June 2013 When an command has been processed successfully, the EPP element MUST contain a child element that identifies the trademark namespace. Elements that are not OPTIONAL MUST be returned; OPTIONAL elements are returned based on client authorization and server policy. The element contains the following child elements: o A element that contains the trademark application ID registered in the trademark office. o A element that contains the Repository Object IDentifier assigned to the trademark object when the object was created. o A element that contains the trademark text string. o Zero or more OPTIONAL elements that contain the current status descriptors associated with the trademark. o One or more OPTIONAL elements that contains the information of the holder of the trademark. An "entitlement" attribute is used to identify the entitlement of the holder, possible values are: owner, assignee and licensee, which defines in [RFC5733]. o If supported by the server, one or more OPTIONAL elements that contain identifiers for the human or organizational social information objects associated with the trademark object. A "type" attribute is used to identify the type of contact, possible values are: owner, agent or thirdparty.This contact object is defined in which defines in [RFC5733]. o A element that contains the two-character code of the jurisdiction where the trademark was registered. This is a two-character code from which defines in [WIPO.ST3]. o Zero or more OPTIONAL elements that contain the Nice Classification class numbers of the trademark. o A element that contains the full description of the goods and services mentioned in the mark registration document. o An OPTIONAL element that contains the date the trademark was applied for. XIE Expires December 18, 2013 [Page 11] Internet-Draft EPP Trademark Mapping June 2013 o A element that contains the trademark registration number registered in the trademark office. o A element that contains the date the trademark was registered. o An OPTIONAL element that contains the expiration date of the trademark. o Zero or more contains the following child elements: o * A elements that contain the domain label corresponding to the trademark name. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the object want to get the sun rise service. A value of "0" or "false" means that the object does not want to get the sun rise service. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the object want to get the claim service. A value of "0" or "false" means that the object does not want to. o A element that contains the identifier of the sponsoring client. o An OPTIONAL element that contains the identifier of the client that created the trademark object. o An OPTIONAL element that contains the date and time of trademark object creation in the trademark clearinghouse. o An OPTIONAL element that contains the date and time identifying the end of the trademark object's registration period. o An OPTIONAL element that contains the identifier of the client that last updated the trademark object. This element MUST NOT be present if the trademark has never been modified. XIE Expires December 18, 2013 [Page 12] Internet-Draft EPP Trademark Mapping June 2013 o An OPTIONAL element that contains the date and time of the most recent trademark-object modification. This element MUST NOT be present if the trademark object has never been modified. o An OPTIONAL element that contains the date and time of the most recent successful trademark-object transfer. This element MUST NOT be provided if the trademark object has never been transferred. o An OPTIONAL element that contains authorization information associated with the trademark object. This element MUST only be returned if the querying client is the current sponsoring client or if the client supplied valid authorization information with the command. Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: 00000712423-1 S: 000000001-abc S: example abc S: S: jd1234 S: sh8013 S: sh8013 S: US S: 35 S: 36 S: Dirigendas et eiusmodi S: featuring infringo in airfare et cartam servicia. S: S: 234235 S: 2009-08-16T09:00:00.0Z S: S: 2015-08-16T09:00:00.0Z S: S: S: exampleabc S: XIE Expires December 18, 2013 [Page 13] Internet-Draft EPP Trademark Mapping June 2013 S: S: S: S: example-abc S: S: S: S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: 2015-08-16T09:00:00.0Z S: ClientX S: 2010-08-16T09:00:00.0Z S: 2010-10-16T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an command cannot be processed for any reason. 4.1.3. EPP Query Command The EPP command provides a query operation that allows a client to determine the real-time status of pending and completed transfer requests. In addition to the standard EPP command elements, the command MUST contain an "op" attribute with value "query", and a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains an identifier of the trademark object. o An OPTIONAL element that contains authorization information associated with the trademark object or authorization information associated with the trademark object's holder or associated contacts. An OPTIONAL "roid" attribute MUST be used to identify the holder or contact object if and only if XIE Expires December 18, 2013 [Page 14] Internet-Draft EPP Trademark Mapping June 2013 the given authInfo is associated with a holder or contact object, and not the trademark object itself. If this element is not provided or if the authorization information is invalid, server policy determines if the command is rejected or if response information will be returned to the client. Example query command: C: C: C: C: C: C: 123456-001 C: C: 2fooBAR C: C: C: C: ABC-12345 C: C: When a query command has been processed successfully, the EPP element MUST contain a child element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object. o A element that contains the state of the most recent transfer request. o A element that contains the identifier of the client that requested the object transfer. o A element that contains the date and time that the transfer was requested. o A element that contains the identifier of the client that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the client that took the indicated action. XIE Expires December 18, 2013 [Page 15] Internet-Draft EPP Trademark Mapping June 2013 o A element that contains the date and time of a required or completed response. For a PENDING request, the value identifies the date and time by which a response is required before an automated response action will be taken by the server. For all other status types, the value identifies the date and time when the request was completed. o An OPTIONAL element that contains the end of the trademark object's validity period if the command caused or causes a change in the validity period. Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: 123456-001 S: pending S: ClientX S: 2010-06-06T22:00:00.0Z S: ClientY S: 2011-06-11T22:00:00.0Z S: 2012-09-08T22:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2. EPP Transform Commands EPP provides five commands to transform trademark objects: to create an instance of a trademark object, to delete an instance of a trademark object, to extend the validity period of a trademark object, to manage trademark object XIE Expires December 18, 2013 [Page 16] Internet-Draft EPP Trademark Mapping June 2013 sponsorship changes, and to change information associated with a trademark object. 4.2.1. EPP Command The EPP command provides a transform operation that allows a client to create a trademark object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the trademark application ID registered in the trademark office. o A element that contains the trademark text string. o An OPTIONAL element that contains the initial registration period of the trademark object. A server MAY define a default initial registration period if not specified by the client. o One or more OPTIONAL elements that contains the information of the holder of the trademark. An "entitlement" attribute is used to identify the entitlement of the holder, possible values are: owner, assignee and licensee. This object is defined in [RFC5733]. o If supported by the server, one or more OPTIONAL elements that contain identifiers for the human or organizational social information objects associated with the trademark object. A "type" attribute is used to identify the type of contact, possible values are: owner, agent or thirdparty.This object is defined in [RFC5733]. o A element that contains the two-character code of the jurisdiction where the trademark was registered. This is a two-character code from [WIPO.ST3]. o Zero or more OPTIONAL elements that contain the Nice Classification class numbers of the trademark. o A element that contains the full description of the goods and services mentioned in the mark registration document. o An OPTIONAL element that contains the date the trademark was applied for. XIE Expires December 18, 2013 [Page 17] Internet-Draft EPP Trademark Mapping June 2013 o A element that contains the trademark registration number registered in the trademark office. o A element that contains the date the trademark was registered. o An OPTIONAL element that contains the expiration date of the trademark. o Zero or more contains the following child elements: o * A elements that contain the domain label corresponding to the trademark name. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the object want to get the sun rise service. A value of "0" or "false" means that the object does not want to get the sun rise service. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the object want to get the claim service. A value of "0" or "false" means that the object does not want to. o An OPTIONAL element that contains authorization information associated with the trademark object. This element MUST only be returned if the querying client is the current sponsoring client or if the client supplied valid authorization information with the command. Example command: C: C: C: C: C: C: 123456-001 C: example abc C: C: jd1234 XIE Expires December 18, 2013 [Page 18] Internet-Draft EPP Trademark Mapping June 2013 C: sh8013 C: sh8013 C: US C: 35 C: 36 C: Dirigendas et eiusmodi C: featuring infringo in airfare et cartam servicia. C: C: 234235 C: 2009-08-16T09:00:00.0Z C: 2015-08-16T09:00:00.0Z C: 5 C: C: exampleabc C: C: C: C: C: example-abc C: C: C: C: C: 2fooBAR C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the tradeamark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object. o A element that contains the date and time of trademark object creation. o An OPTIONAL element that contains the date and time identifying the end of the trademark object's registration period. XIE Expires December 18, 2013 [Page 19] Internet-Draft EPP Trademark Mapping June 2013 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 00000712423-1 S: 1999-04-03T22:00:00.0Z S: 2001-04-03T22:00:00.0Z S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: 4.2.2. EPP Command The EPP command provides a transform operation that allows a client to delete a trademark object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object to be deleted. Example command: C: C: C: C: C: C: 123456-001 C: C: C: ABC-12345 C: XIE Expires December 18, 2013 [Page 20] Internet-Draft EPP Trademark Mapping June 2013 C: When a command has been processed successfully, a server MUST respond with an EPP response with no element. Example response: S: S: S: S: S: Command completed successfully S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.3. EPP Command The EPP command provides a transform operation that allows a client to extend the validity period of a trademark object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object whose validity period is to be extended. o A element that contains the date on which the current validity period ends. This value ensures that repeated commands do not result in multiple, unanticipated successful renewals. o An OPTIONAL element that contains the number of units to be added to the registration period of the trademark object. The number of units available MAY be subject to limits imposed by the server. XIE Expires December 18, 2013 [Page 21] Internet-Draft EPP Trademark Mapping June 2013 Example command: C: C: C: C: C: C: 123456-001 C: 2000-04-03 C: 5 C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object. o An OPTIONAL element that contains the date and time identifying the end of the trademark object's registration period. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 123456-001 S: 2012-04-03T22:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ XIE Expires December 18, 2013 [Page 22] Internet-Draft EPP Trademark Mapping June 2013 S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.4. EPP Command The EPP command provides a transform operation that allows a client to manage requests to transfer the sponsorship of a trademark object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object for which a transfer request is to be created, approved, rejected, or cancelled. o An OPTIONAL element that contains the number of units to be added to the registration period of the trademark object at completion of the transfer process. This element can only be used when a transfer is requested, and it MUST be ignored if used otherwise. The number of units available MAY be subject to limits imposed by the server. o A element that contains authorization information associated with the trademark object or authorization information associated with the trademark object's holder or associated contacts. An OPTIONAL "roid" attribute MUST be used to identify the holder or contact object if and only if the given authInfo is associated with a holder or contact object, and not the trademark object itself. Every EPP command MUST contain an "op" attribute that identifies the transfer operation to be performed. Valid values, definitions, and authorizations for all attribute values are defined in [RFC5730]. Example request command: C: C: C: C: C: C: 123456-001 C: 1 C: C: 2fooBAR C: C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the trademark namespace. The element contains the same child elements defined for a transfer query response. Example Response for an authorized client: S: S: S: S: S: Command completed successfully S: S: S: S: 123456-001 S: pending S: ClientX S: 2010-06-06T22:00:00.0Z S: ClientY S: 2011-06-11T22:00:00.0Z S: 2012-09-08T22:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: XIE Expires December 18, 2013 [Page 24] Internet-Draft EPP Trademark Mapping June 2013 An EPP error response MUST be returned if a command cannot be processed for any reason. 4.2.5. EPP Command The EPP command provides a transform operation that allows a client to modify the attributes of a trademark object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the trademark namespace. The element contains the following child elements: o A element that contains the fully qualified id of the trademark object to be updated. o An OPTIONAL element that contains attribute values to be added to the object. o An OPTIONAL element that contains attribute values to be removed from the object. o An OPTIONAL element that contains object attribute values to be changed. At least one , , or element MUST be provided if the command is not being extended. All of these elements MAY be omitted if an extension is present. The and elements contain the following child elements: o Zero or more contains the following child elements: o * A elements that contain the domain label corresponding to the trademark name. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the object want to get the sun rise service. A value of "0" or "false" means that the object does not want to get the sun rise service. * A element MUST contain an "enable" attribute whose value indicates the intended service of this trademark object. A value of "1" or "true" means that the XIE Expires December 18, 2013 [Page 25] Internet-Draft EPP Trademark Mapping June 2013 object want to get the claim service. A value of "0" or "false" means that the object does not want to. o Zero or more elements that contain the identifiers for contact objects to be associated with or removed from the trademark object. Contact object identifiers MUST be known to the server before the contact object can be associated with the trademark object. o Zero or more elements that contain status values to be applied to or removed from the object. When specifying a value to be removed, only the attribute value is significant; element text is not required to match a value for removal. A element contains the following child elements: o A element that contains the identifier for the human or organizational social information (contact) object to be associated with the trademark object as the object holder. This object identifier MUST be known to the server before the contact object can be associated with the trademark object. An empty element can be used to remove holder information. o A element that contains authorization information associated with the trademark object. This mapping includes a password-based authentication mechanism, but the schema allows new mechanisms to be defined in new schemas. A element can be used within the element to remove authorization information. o A element that contains the trademark text string to be changed. o A element that contains the two-character code of the jurisdiction where the trademark was registered to be changed. o A elements that contain the Nice Classification class numbers of the trademark to be changed. o A element that contains the full description of the goods and services mentioned in the trademark registration document to be changed. o A element that contains the date to be changed which the trademark was applied for . XIE Expires December 18, 2013 [Page 26] Internet-Draft EPP Trademark Mapping June 2013 o A element that contains the trademark registration number to be changed which registered in the trademark office. o A element that contains the date the trademark was registered to be changed. o An OPTIONAL element that contains the expiration date of the trademark to be changed. XIE Expires December 18, 2013 [Page 27] Internet-Draft EPP Trademark Mapping June 2013 Example command: C: C: C: C: C: C: 123456-001 C: C: C: example-one C: C: C: C: mak21 C: C: C: C: C: exampleone C: C: C: C: sh8013 C: C: C: C: sh8013 C: C: 2BARfoo C: C: C: C: C: ABC-12345 C: C: When an command has been processed successfully, a server MUST respond with an EPP response with no element. Example response: S: S: S: XIE Expires December 18, 2013 [Page 28] Internet-Draft EPP Trademark Mapping June 2013 S: S: Command completed successfully S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 5. Formal Syntax Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. An EPP Trademark mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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, XIE Expires December 18, 2013 [Page 29] Internet-Draft EPP Trademark Mapping June 2013 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. BEGIN Extensible Provisioning Protocol v1.0 Trademark Mapping Schema v1.0 XIE Expires December 18, 2013 [Page 31] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 32] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 33] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 34] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 35] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 36] Internet-Draft EPP Trademark Mapping June 2013 XIE Expires December 18, 2013 [Page 38] Internet-Draft EPP Trademark Mapping June 2013 END 6. Internationalization Considerations EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is RECOMMENDED. As the EPP Trademark mapping, the elements, element content described in this document MUST inherit the internationalization conventions used to represent higher-layer and core protocol structures present in an XML instance that includes this extension. Dealing with the IDN variant issues,TBD. 7. IANA Considerations XIE Expires December 18, 2013 [Page 39] Internet-Draft EPP Trademark Mapping June 2013 This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. IANA is requested to assignment the following two URI. Registration request for the trademark namespace: o URI: urn:ietf:params:xml:ns:trademark-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: None. Namespace URI does not represent an XML specification. Registration request for the mark XML schema: o URI: urn:ietf:params:xml:schema:trademark-1.0 o Registrant Contact: See the "Author's Address" section of this document. o XML: See the "Formal Syntax" section of this document. 8. Security considerations The object mapping extension described in this document does not provide any other security services or introduce any additional considerations beyond those described by [RFC5730] or those caused by the protocol layers used by EPP. 9. Acknowledgements The authors especially thank the authors of [RFC5730], [RFC5731] and the authors of [draft-lozano-smd]. 10. Change History TBD 10.1. draft-xie-epp-trademark-mapping: Version 00 o First draft. 11. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. XIE Expires December 18, 2013 [Page 40] Internet-Draft EPP Trademark Mapping June 2013 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, August 2009. [W3C.REC-xml-20040204] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC- xml-20040204", February 2004, . [W3C.REC-xmlschema-1-20041028] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, ""XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC- xmlschema-1-20041028", October 2004, . [W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028", October 2004, . [WIPO.ST3] WIPO, ., "Recommended standard on two-letter codes for the representation of states, other entities and intergovernmental organizations", March 2007. Author's Address Jiagui XIE CONAC Jia 31,North Guangximen, Xibahe, Chaoyang District Beijing, Beijing 100028 China Phone: +86 10 5203 5025 Email: xiejg@conac.cn XIE Expires December 18, 2013 [Page 41]