RFC 7848: Mark and Signed Mark Objects Mapping 中文翻译

URL : https://datatracker.ietf.org/doc/html/rfc7848
标题 : RFC 7848
翻译类型 : 自动生成

Internet Engineering Task Force (IETF)                         G. Lozano
Request for Comments: 7848                                         ICANN
Category: Standards Track                                      June 2016
ISSN: 2070-1721

Internet Engineering Task Force (IETF)                         G. Lozano
Request for Comments: 7848                                         ICANN
Category: Standards Track                                      June 2016
ISSN: 2070-1721

Mark and Signed Mark Objects Mapping

标记和有符号标记对象映射

Abstract

摘要

Domain Name Registries (DNRs) may operate in special modes for certain periods of time, enabling trademark holders to protect their rights during the introduction of a Top-Level Domain (TLD).

域名注册处（DNR）可以在特定时间段内以特殊模式运行，使商标持有人能够在顶级域名（TLD）引入期间保护其权利。

One of those special modes of operation is the Sunrise Period. The Sunrise Period allows trademark holders an advance opportunity to register domain names corresponding to their trademarks before names are generally available to the public.

其中一种特殊的操作模式是日出期。日出期允许商标持有人提前注册与其商标相对应的域名，然后才能向公众公开域名。

This document describes the format of a mark and a digitally signed mark used by trademark holders for registering domain names during the Sunrise Period of generic Top-Level Domains (gTLDs). Three types of Mark objects are defined in this specification: registered trademarks, court-validated marks, and marks protected by statue or treaty.

本文件描述了商标持有人在通用顶级域名（GTLD）的日出期注册域名时使用的标记和数字签名标记的格式。本规范中定义了三种类型的标记对象：注册商标、法院认可的标记和受法律或条约保护的标记。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7848.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7848.

版权公告

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.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Object Description  . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Holder and Contact Objects  . . . . . . . . . . . . . . .   5
     2.2.  Mark  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Signed Mark . . . . . . . . . . . . . . . . . . . . . . .  10
     2.4.  Encoded Signed Mark . . . . . . . . . . . . . . . . . . .  13
   3.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  14
     3.1.  Signed Mark Schema  . . . . . . . . . . . . . . . . . . .  14
     3.2.  Mark Schema . . . . . . . . . . . . . . . . . . . . . . .  15
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  24
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  24
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  24

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Object Description  . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Holder and Contact Objects  . . . . . . . . . . . . . . .   5
     2.2.  Mark  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Signed Mark . . . . . . . . . . . . . . . . . . . . . . .  10
     2.4.  Encoded Signed Mark . . . . . . . . . . . . . . . . . . .  13
   3.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  14
     3.1.  Signed Mark Schema  . . . . . . . . . . . . . . . . . . .  14
     3.2.  Mark Schema . . . . . . . . . . . . . . . . . . . . . . .  15
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  24
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  24
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  24

1. Introduction

1. 介绍

Domain Name Registries (DNRs) may operate in special modes for certain periods of time enabling trademark holders to protect their rights during the introduction of a Top-Level Domain (TLD).

域名注册处（DNR）可以在特定时间段内以特殊模式运作，使商标持有人能够在顶级域名（TLD）引入期间保护其权利。

其中一种特殊的操作模式是日出期。日出期允许商标持有人提前注册与其商标相对应的域名，然后才能向公众公开域名。

This specification was defined as part of the development of the ICANN Trademark Clearinghouse (TMCH). The ICANN TMCH is a global repository for trademark data used by DNRs, registrars, and trademark holders during the registration process of domain names.

本规范被定义为ICANN商标清算所（TMCH）开发的一部分。ICANN TMCH是DNR、注册商和商标持有人在域名注册过程中使用的商标数据的全球存储库。

This document describes a mapping of the common elements found in trademark data. A digitally signed mark format is defined in order to support digital signatures on the mark. Finally, a mapping for encoding the signed mark document is defined.

本文档描述了商标数据中常见元素的映射。为了支持标记上的数字签名，定义了数字签名标记格式。最后，定义了用于编码签名标记文档的映射。

Three types of Mark objects are defined in this specification: registered trademarks, court-validated marks, and marks protected by statue or treaty.

本规范中定义了三种类型的标记对象：注册商标、法院认可的标记和受法律或条约保护的标记。

This specification is intended to be used in the gTLD space, but nothing precludes the use of this format by other entities.

本规范旨在用于gTLD空间，但不排除其他实体使用此格式。

The detailed policy regarding the public key infrastructure (PKI), authorized validators, and other requirements must be defined based on the local policy of the entities using this specification. In the case of gTLDs, the detailed policy regarding the use of this specification is defined in the Rights Protection Mechanism Requirements document (see [ICANN-TMCH]), and the PKI is defined in [TMCH]. Implementations will need to implement such a PKI (or an equivalent) in order for the signatures defined in this document to have any useful semantics.

关于公钥基础设施（PKI）、授权验证器和其他要求的详细策略必须基于使用本规范的实体的本地策略来定义。在gTLDs的情况下，有关使用本规范的详细政策在权利保护机制要求文件（见[ICANN-TMCH]）中定义，PKI在[TMCH]中定义。为了使本文档中定义的签名具有任何有用的语义，实现将需要实现这样的PKI（或等效物）。

The objects specified in this document can be referenced by application protocols like the Extensible Provisioning Protocol (EPP), defined in [RFC5730].

本文档中指定的对象可由应用程序协议引用，如[RFC5730]中定义的可扩展资源调配协议（EPP）。

1.1. Terminology

1.1. 术语

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 [RFC2119].

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。

XML (EXtensible Markup Language) 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.

XML（可扩展标记语言）区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须以所提供的字符大小写进行解释，以便开发一致的实现。

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

“signedMark-1.0”用作“urn:ietf:params:xml:ns:signedMark-1.0”的缩写。使用XML名称空间前缀“smd”，但实现不能依赖于它，而是使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。

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

“mark-1.0”用作“urn:ietf:params:xml:ns:mark-1.0”的缩写。使用XML名称空间前缀“mark”，但实现不能依赖于它，而是使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。

2. Object Description

2. 对象描述

This section defines the Mark and Signed Mark objects. Empty complex element types and abstract elements are defined to support additional definitions using XML schema substitution groups. Support for replacement through the XML schema substitution groups is included in the description of the objects.

本节定义标记和有符号标记对象。定义空的复杂元素类型和抽象元素以支持使用XML模式替换组的其他定义。对象的描述中包含对通过XML模式替换组进行替换的支持。

This section defines some elements as OPTIONAL. If an element is not defined as OPTIONAL, then it MUST be included in the object.

本节将某些元素定义为可选元素。如果元素未定义为可选元素，则必须将其包含在对象中。

The following elements are defined as telephone numbers: <mark:voice>, <mark:fax>, and <smd:voice>. The representation of telephone numbers in this specification is derived from structures defined in [ITU.E164.2005]. Telephone numbers described in this mapping are character strings that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in [ITU.E164.2005], followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number. An optional "x" attribute is provided to note telephone extension information.

以下元素定义为电话号码：<mark:voice>、<mark:fax>和<smd:voice>。本规范中的电话号码表示源自[ITU.E164.2005]中定义的结构。此映射中描述的电话号码是字符串，必须以加号（“+”，ASCII值0x002B）开头，后跟[ITU.E164.2005]中定义的国家代码，后跟点（“.”，ASCII值0x002E），后跟表示电话号码的数字序列。提供了可选的“x”属性来记录电话分机信息。

The following elements are defined as email addresses: <mark:email> and <smd:email>. Email address syntax is defined in [RFC5322].

以下元素定义为电子邮件地址：<mark:email>和<smd:email>。[RFC5322]中定义了电子邮件地址语法。

2.1. Holder and Contact Objects

2.1. 保持器和接触对象

Marks are linked to Holder objects and optionally linked to Contact objects. This section defines the <mark:holder> and <mark:contact> objects.

标记链接到支架对象，也可以选择链接到触点对象。本节定义了<mark:holder>和<mark:contact>对象。

o The child elements of <mark:holder> include:

o <mark:holder>的子元素包括：

* A <mark:name> element that contains the name of the individual holder of the mark. At least one of <mark:name> and <mark:org> MUST be specified, and <mark:name> is OPTIONAL if <mark:org> is specified.

* 一个<mark:name>元素，包含单个标记持有者的名称。必须至少指定<mark:name>和<mark:org>中的一个，如果指定了<mark:org>，则<mark:name>是可选的。

* A <mark:org> element that contains the name of the organization holder of the mark. At least one of <mark:name> and <mark:org> MUST be specified, and <mark:org> is OPTIONAL if <mark:name> is specified.

* 一个<mark:org>元素，包含标记持有者的组织名称。必须至少指定<mark:name>和<mark:org>中的一个，如果指定了<mark:name>，则<mark:org>是可选的。

* A <mark:addr> element that contains the address information of the holder of a mark. A <mark:addr> contains the following child elements:

* 包含标记持有者地址信息的<mark:addr>元素。<mark:addr>包含以下子元素：

+ One, two, or three OPTIONAL <mark:street> elements that contain the holder's street address.

+ 包含持有者街道地址的一个、两个或三个可选<mark:street>元素。

+ A <mark:city> element that contains the holder's city.

+ 包含持有者城市的<mark:city>元素。

+ An OPTIONAL <mark:sp> element that contains the holder's state or province.

+ 包含持有者所在州或省的可选<mark:sp>元素。

+ An OPTIONAL <mark:pc> element that contains the holder's postal code.

+ 包含持有人邮政编码的可选<mark:pc>元素。

+ A <mark:cc> element that contains the holder's country code. This is a two-character code from [ISO3166-2].

+ 包含持有人国家代码的<mark:cc>元素。这是[ISO3166-2]中的两个字符代码。

* An OPTIONAL <mark:voice> element that contains the holder's voice telephone number.

* 可选的<mark:voice>元素，包含持有者的语音电话号码。

* An OPTIONAL <mark:fax> element that contains the holder's facsimile telephone number.

* 包含持有人传真电话号码的可选<mark:fax>元素。

* An OPTIONAL <mark:email> element that contains the email address of the holder.

* 可选的<mark:email>元素，包含持有者的电子邮件地址。

o The child elements of <mark:contact> include:

o <mark:contact>的子元素包括：

* A <mark:name> element that contains the name of the responsible person.

* 包含负责人姓名的<mark:name>元素。

* An OPTIONAL <mark:org> element that contains the name of the organization of the contact.

* 可选的<mark:org>元素，包含联系人组织的名称。

* A <mark:addr> element that contains the address information of the contact. A <mark:addr> contains the following child elements:

* 包含联系人地址信息的<mark:addr>元素。<mark:addr>包含以下子元素：

+ One, two, or three OPTIONAL <mark:street> elements that contain the contact's street address.

+ 包含联系人街道地址的一个、两个或三个可选<mark:street>元素。

+ A <mark:city> element that contains the contact's city.

+ 包含联系人所在城市的<mark:city>元素。

+ An OPTIONAL <mark:sp> element that contains the contact's state or province.

+ 包含联系人所在州或省的可选<mark:sp>元素。

+ An OPTIONAL <mark:pc> element that contains the contact's postal code.

+ 包含联系人邮政编码的可选<mark:pc>元素。

+ A <mark:cc> element that contains the contact's country code. This is a two-character code from [ISO3166-2].

+ 包含联系人国家/地区代码的<mark:cc>元素。这是[ISO3166-2]中的两个字符代码。

* A <mark:voice> element that contains the contact's voice telephone number.

* 包含联系人语音电话号码的<mark:voice>元素。

* An OPTIONAL <mark:fax> element that contains the contact's facsimile telephone number.

* 包含联系人传真电话号码的可选<mark:fax>元素。

* A <mark:email> element that contains the contact's email address.

* 包含联系人电子邮件地址的<mark:email>元素。

2.2. Mark

2.2. 做记号

A <mark:mark> element that describes an applicant's prior right to a given domain name.

描述申请人对给定域名的优先权的<mark:mark>元素。

A <mark:mark> element substitutes for the <mark:abstractMark> abstract element to define a concrete definition of a mark. The <mark:abstractMark> element can be replaced by other mark definitions using the XML schema substitution groups feature.

<mark:mark>元素替换<mark:abstractMark>抽象元素来定义标记的具体定义。<mark:abstractMark>元素可以使用XMLSchema替换组功能由其他标记定义替换。

The child elements of the <mark:mark> element include:

<mark:mark>元素的子元素包括：

One or more <mark:trademark>, <mark:treatyOrStatute>, and <mark:court> elements that contain the detailed information of marks.

包含标记详细信息的一个或多个<mark:trademark>、<mark:treatyorostatute>和<mark:court>元素。

o A <mark:trademark> element that contains the following child elements:

o 包含以下子元素的<mark:trademark>元素：

* A <mark:id> that uniquely identifies a mark in relation to a repository of marks potentially maintained by more than one issuer. A <mark:id> value is a concatenation of the local identifier, followed by a hyphen ("-", ASCII value 0x002D), followed by the issuer identifier.

* 一种<mark:id>，它唯一地标识与可能由多个发行人维护的标记存储库相关的标记。<mark:id>值是本地标识符的串联，后跟连字符（“-”，ASCII值0x002D），后跟颁发者标识符。

* A <mark:markName> element that contains the mark text string.

* 包含标记文本字符串的<mark:markName>元素。

* One or more <mark:holder> elements that contain the information of the holder of the mark. An "entitlement" attribute is used to identify the entitlement of the holder; possible values are "owner", "assignee", and "licensee".

* 包含标记持有者信息的一个或多个<mark:holder>元素。“权利”属性用于标识持有人的权利；可能的值为“所有者”、“受让人”和“被许可人”。

* Zero or more OPTIONAL <mark:contact> elements that contain the information of the representative of the mark registration. A "type" attribute is used to identify the type of contact; possible values are "owner", "agent", or "thirdparty".

* 零个或多个可选<mark:contact>元素，其中包含标记注册代表的信息。“类型”属性用于标识联系人的类型；可能的值为“所有者”、“代理人”或“第三方”。

* A <mark:jurisdiction> element that contains the two-character code of the jurisdiction where the trademark was registered. This is a two-character code from [WIPO.ST3].

* 一个<mark:justitution>元素，包含商标注册所在辖区的两个字符代码。这是来自[WIPO.ST3]的两个字符的代码。

* Zero or more OPTIONAL <mark:class> elements that contain the World Intellectual Property Organization (WIPO) Nice Classification class numbers of the mark as defined in the WIPO Nice Classification [WIPO-NICE-CLASSES].

* 零个或多个可选<mark:class>元素，包含WIPO Nice分类[WIPO-Nice-CLASSES]中定义的商标的世界知识产权组织（WIPO）Nice分类类号。

* Zero or more OPTIONAL <mark:label> elements that contain the A-label form (as defined in [RFC5890]) of the label that corresponds to the <mark:markName>.

* 零个或多个可选<mark:label>元素，这些元素包含与<mark:markName>相对应的标签的A标签形式（如[RFC5890]中所定义）。

* A <mark:goodsAndServices> element that contains the full description of the goods and services from the document certifying the registration of the mark.

* 一个<mark:goodsAndServices>元素，包含证明商标注册的文件中对商品和服务的完整描述。

* An OPTIONAL <mark:apId> element that contains the trademark application ID registered in the trademark office.

* 可选的<mark:apId>元素，包含在商标局注册的商标申请ID。

* An OPTIONAL <mark:apDate> element that contains the date the trademark was applied for.

* 包含商标申请日期的可选<mark:apDate>元素。

* A <mark:regNum> element that contains the trademark registration number registered in the trademark office.

* 包含在商标局注册的商标注册号的<mark:regNum>元素。

* A <mark:regDate> element that contains the date the trademark was registered.

* 包含商标注册日期的<mark:regDate>元素。

* An OPTIONAL <mark:exDate> element that contains the expiration date of the trademark.

* 包含商标有效期的可选<mark:exDate>元素。

o A <mark:treatyOrStatute> element that contains the following child elements:

o 包含以下子元素的<mark:treatyor规约>元素：

* A <mark:id> element; see definition in the <mark:trademark> section above.

* A<mark:id>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:markName> element; see definition in the <mark:trademark> section above.

* A<mark:markName>元素；请参见上文<mark:trademark>一节中的定义。

* One or more <mark:holder> elements; see definition in the <mark:trademark> section above.

* 一个或多个<mark:holder>元件；请参见上文<mark:trademark>一节中的定义。

* Zero or more OPTIONAL <mark:contact> elements; see definition in the <mark:trademark> section above.

* 零个或多个可选<标记：触点>元件；请参见上文<mark:trademark>一节中的定义。

* One or more <mark:protection> elements that contain the countries and region of the country where the mark is protected. The <mark:protection> element contains the following child elements:

* 一个或多个<mark:protection>元素，其中包含标记受保护国家的国家和地区。<mark:protection>元素包含以下子元素：

+ A <mark:cc> element that contains the two-character code of the country in which the mark is protected. This is a two-character code from [ISO3166-2].

+ 一种<mark:cc>元素，包含受保护国家的双字符代码。这是[ISO3166-2]中的两个字符代码。

+ An OPTIONAL <mark:region> element that contains the name of a city, state, province, or other geographic region of <mark:country> in which the mark is protected.

+ 一个可选的<mark:region>元素，包含受保护的<mark:country>的城市、州、省或其他地理区域的名称。

+ Zero or more OPTIONAL <mark:ruling> elements that contain the two-character code of the national territory in which the statute or treaty is applicable. This is a two-character code from [ISO3166-2].

+ 零个或多个可选<mark:ruding>元素，包含适用法规或条约的国家领土的双字符代码。这是[ISO3166-2]中的两个字符代码。

+ Zero or more OPTIONAL <mark:label> elements; see definition in the <mark:trademark> section above.

+ 零个或多个可选<mark:label>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:goodsAndServices> element; see definition in the <mark:trademark> section above.

* A<mark:goodsAndServices>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:refNum> element that contains the serial number of the mark.

* 包含标记序列号的<mark:refNum>元素。

* A <mark:proDate> element that contains the date of protection of the mark.

* 包含标记保护日期的<mark:proDate>元素。

* A <mark:title> element that contains the title of the treaty or statute.

* 包含条约或法规标题的<mark:title>元素。

* A <mark:execDate> element that contains the execution date of the treaty or statute.

* 包含条约或法规的执行日期的<mark:execDate>元素。

o A <mark:court> element that contains the following child elements:

o 包含以下子元素的<mark:court>元素：

* A <mark:id> element; see definition in the <mark:trademark> section above.

* A<mark:id>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:markName> element; see definition in the <mark:trademark> section above.

* A<mark:markName>元素；请参见上文<mark:trademark>一节中的定义。

* One or more <mark:holder> elements; see definition in the <mark:trademark> section above.

* 一个或多个<mark:holder>元件；请参见上文<mark:trademark>一节中的定义。

* Zero or more OPTIONAL <mark:contact> elements; see definition in the <mark:trademark> section above.

* 零个或多个可选<标记：触点>元件；请参见上文<mark:trademark>一节中的定义。

* Zero or more OPTIONAL <mark:label> elements; see definition in the <mark:trademark> section above.

* 零个或多个可选<mark:label>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:goodsAndServices> element; see definition in the <mark:trademark> section above.

* A<mark:goodsAndServices>元素；请参见上文<mark:trademark>一节中的定义。

* A <mark:refNum> element that contains the reference number of the court's opinion.

* 包含法院意见参考号的<mark:refNum>元素。

* A <mark:proDate> element that contains the date of protection of the mark.

* 包含标记保护日期的<mark:proDate>元素。

* A <mark:cc> element that contains the two-character code of the country where the court is located. This is a two-character code from [ISO3166-2].

* 一种<mark:cc>元素，包含法院所在国的两个字符代码。这是[ISO3166-2]中的两个字符代码。

* Zero or more OPTIONAL <mark:region> elements that contain the name of a city, state, province, or other geographic region of <mark:cc> in which the mark is protected. In case <mark:region> is specified, a default-deny approach MUST be assumed regarding the regions of a country.

* 零个或多个可选的<mark:region>元素，其中包含受保护的<mark:cc>的城市、州、省或其他地理区域的名称。如果指定了<mark:region>，则必须对一个国家的地区采用默认的拒绝方法。

* A <mark:courtName> element that contains the name of the court.

* 包含法院名称的<mark:courtName>元素。

2.3. Signed Mark

2.3. 标记

The <smd:signedMark> is a digitally signed XML document using an XML Signature [XMLDSIG]. The <smd:signedMark> XML document (SMD) includes a required "id" attribute of type XML Schema Definition (XSD) ID for use with an IDREF URI from the Signature element. The SMD might be transmitted as part of a protocol already based on XML; therefore, exclusive XML canonicalization as defined in [XMLC14N] MUST be used.

<smd:signedMark>是一个使用XML签名[XMLDSIG]的数字签名XML文档。<smd:signedMark>XML文档（smd）包含一个类型为xmlschema Definition（XSD）id的必需“id”属性，该属性与来自Signature元素的idrefuri一起使用。SMD可以作为已经基于XML的协议的一部分进行传输；因此，必须使用[XMLC14N]中定义的独占XML规范化。

A <smd:signedMark> element substitutes for the <smd:abstractSignedMark> abstract element to define a concrete definition of a signed mark. The <smd:abstractSignedMark> element can be replaced by other signed mark definitions using the XML schema substitution groups feature.

一个<smd:signedMark>元素代替<smd:abstractSignedMark>抽象元素来定义有符号标记的具体定义。使用XMLSchemaSubstitutionGroups功能，<smd:abstractSignedMark>元素可以由其他有符号标记定义替换。

The child elements of the <smd:signedMark> element include:

<smd:signedMark>元素的子元素包括：

o The <smd:id> element that uniquely identifies an SMD in relation to a repository of SMDs potentially maintained by more than one issuer. The <smd:id> value is a concatenation of the local identifier, followed by a hyphen ("-", ASCII value 0x002D), followed by the issuer identifier.

o 与可能由多个发行者维护的smd存储库相关的唯一标识smd的<smd:id>元素。<smd:id>值是本地标识符的串联，后跟连字符（“-”，ASCII值0x002D），后跟颁发者标识符。

o A <smd:issuerInfo> element that contains the information of the issuer of the mark registration. An "issuerID" attribute is used to specify the issuer identifier. The child elements include:

o 包含商标注册发行人信息的<smd:issuerInfo>元素。“issuerID”属性用于指定颁发者标识符。子元素包括：

* A <smd:org> element that contains the organization name of the issuer.

* 包含发行人组织名称的<smd:org>元素。

* A <smd:email> element that contains the issuer customer support email address.

* 包含发卡行客户支持电子邮件地址的<smd:email>元素。

* An OPTIONAL <smd:url> element that contains the HTTP or HTTPS URL of the issuer's site.

* 一个可选的<smd:url>元素，包含发卡机构站点的HTTP或HTTPS url。

* An OPTIONAL <smd:voice> element that contains the issuer's voice telephone number.

* 包含发卡机构语音电话号码的可选<smd:voice>元素。

o A <smd:notBefore> element that contains the creation date and time of the SMD.

o 包含smd创建日期和时间的<smd:notBefore>元素。

o A <smd:notAfter> element that contains the expiration date and time of the SMD.

o 包含smd过期日期和时间的<smd:notAfter>元素。

o A <mark:mark> element that contains the mark information as defined in Section 2.2.

o 包含第2.2节中定义的标记信息的<mark:mark>元素。

The following is an example of an SMD:

以下是SMD的一个示例：

 <?xml version="1.0" encoding="UTF-8"?>
 <smd:signedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
 id="smd1">
   <smd:id>0000001751376056503931-65535</smd:id>
   <smd:issuerInfo issuerID="65535">
     <smd:org>ICANN TMCH TESTING TMV</smd:org>
     <smd:email>notavailable@example.com</smd:email>
     <smd:url>https://www.example.com</smd:url>
     <smd:voice>+32.000000</smd:voice>
   </smd:issuerInfo>
   <smd:notBefore>2013-08-09T13:55:03.931Z</smd:notBefore>
   <smd:notAfter>2017-07-23T22:00:00.000Z</smd:notAfter>
   <mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
     <mark:trademark>
       <mark:id>00052013734689731373468973-65535</mark:id>
       <mark:markName>Test &amp; Validate</mark:markName>
       <mark:holder entitlement="owner">
         <mark:org>Ag corporation</mark:org>
         <mark:addr>
           <mark:street>1305 Bright Avenue</mark:street>
           <mark:city>Arcadia</mark:city>
           <mark:sp>CA</mark:sp>
           <mark:pc>90028</mark:pc>
           <mark:cc>US</mark:cc>
         </mark:addr>
       </mark:holder>
       <mark:contact type="agent">
         <mark:name>Tony Holland</mark:name>
         <mark:org>Ag corporation</mark:org>
         <mark:addr>
           <mark:street>1305 Bright Avenue</mark:street>
           <mark:city>Arcadia</mark:city>
           <mark:sp>CA</mark:sp>
           <mark:pc>90028</mark:pc>
           <mark:cc>US</mark:cc>
         </mark:addr>
         <mark:voice>+1.2025562302</mark:voice>
         <mark:fax>+1.2025562301</mark:fax>
         <mark:email>info@agcorporation.com</mark:email>
       </mark:contact>
       <mark:jurisdiction>US</mark:jurisdiction>
       <mark:class>15</mark:class>
       <mark:label>testandvalidate</mark:label>

 <?xml version="1.0" encoding="UTF-8"?>
 <smd:signedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
 id="smd1">
   <smd:id>0000001751376056503931-65535</smd:id>
   <smd:issuerInfo issuerID="65535">
     <smd:org>ICANN TMCH TESTING TMV</smd:org>
     <smd:email>notavailable@example.com</smd:email>
     <smd:url>https://www.example.com</smd:url>
     <smd:voice>+32.000000</smd:voice>
   </smd:issuerInfo>
   <smd:notBefore>2013-08-09T13:55:03.931Z</smd:notBefore>
   <smd:notAfter>2017-07-23T22:00:00.000Z</smd:notAfter>
   <mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
     <mark:trademark>
       <mark:id>00052013734689731373468973-65535</mark:id>
       <mark:markName>Test &amp; Validate</mark:markName>
       <mark:holder entitlement="owner">
         <mark:org>Ag corporation</mark:org>
         <mark:addr>
           <mark:street>1305 Bright Avenue</mark:street>
           <mark:city>Arcadia</mark:city>
           <mark:sp>CA</mark:sp>
           <mark:pc>90028</mark:pc>
           <mark:cc>US</mark:cc>
         </mark:addr>
       </mark:holder>
       <mark:contact type="agent">
         <mark:name>Tony Holland</mark:name>
         <mark:org>Ag corporation</mark:org>
         <mark:addr>
           <mark:street>1305 Bright Avenue</mark:street>
           <mark:city>Arcadia</mark:city>
           <mark:sp>CA</mark:sp>
           <mark:pc>90028</mark:pc>
           <mark:cc>US</mark:cc>
         </mark:addr>
         <mark:voice>+1.2025562302</mark:voice>
         <mark:fax>+1.2025562301</mark:fax>
         <mark:email>info@agcorporation.com</mark:email>
       </mark:contact>
       <mark:jurisdiction>US</mark:jurisdiction>
       <mark:class>15</mark:class>
       <mark:label>testandvalidate</mark:label>

       <mark:label>test---validate</mark:label>
       <mark:label>testand-validate</mark:label>
       <mark:label>test-et-validate</mark:label>
       <mark:label>test-validate</mark:label>
       <mark:label>test--validate</mark:label>
       <mark:label>test-etvalidate</mark:label>
       <mark:label>testetvalidate</mark:label>
       <mark:label>testvalidate</mark:label>
       <mark:label>testet-validate</mark:label>
       <mark:goodsAndServices>guitar</mark:goodsAndServices>
       <mark:regNum>1234</mark:regNum>
       <mark:regDate>2012-12-31T23:00:00.000Z</mark:regDate>
     </mark:trademark>
   </mark:mark>
  <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
   <SignedInfo>
    <CanonicalizationMethod
 Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <SignatureMethod
 Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
    <Reference URI="#smd1">
     <Transforms>
      <Transform
 Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
     </Transforms>
     <DigestMethod
 Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
 <DigestValue>wgyW3nZPoEfpptlhRILKnOQnbdtU6ArM7ShrAfHgDFg=</DigestValue>
    </Reference>
   </SignedInfo>
   <SignatureValue>
 jMu4PfyQGiJBF0GWSEPFCJjmywCEqR2h4LD+ge6XQ+JnmKFFCuCZS/3SLKAx0L1w
 QDFO2e0Y69k2G7/LGE37X3vOflobFM1oGwja8+GMVraoto5xAd4/AF7eHukgAymD
 o9toxoa2h0yV4A4PmXzsU6S86XtCcUE+S/WM72nyn47zoUCzzPKHZBRyeWehVFQ+
 jYRMIAMzM57HHQA+6eaXefRvtPETgUO4aVIVSugc4OUAZZwbYcZrC6wOaQqqqAZi
 30aPOBYbAvHMSmWSS+hFkbshomJfHxb97TD2grlYNrQIzqXk7WbHWy2SYdA+sI/Z
 ipJsXNa6osTUw1CzA7jfwA==
   </SignatureValue>
   <KeyInfo>
    <X509Data>
    <X509Certificate>
 MIIESTCCAzGgAwIBAgIBAjANBgkqhkiG9w0BAQsFADBiMQswCQYDVQQGEwJVUzEL
 MAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJQ0FO
 TiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0EwHhcNMTMwMjA4MDAw
 MDAwWhcNMTgwMjA3MjM1OTU5WjBsMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex
 FDASBgNVBAcTC0xvcyBBbmdlbGVzMRcwFQYDVQQKEw5WYWxpZGF0b3IgVE1DSDEh
 MB8GA1UEAxMYVmFsaWRhdG9yIFRNQ0ggVEVTVCBDRVJUMIIBIjANBgkqhkiG9w0B
 AQEFAAOCAQ8AMIIBCgKCAQEAo/cwvXhbVYl0RDWWvoyeZpETVZVVcMCovUVNg/sw

       <mark:label>test---validate</mark:label>
       <mark:label>testand-validate</mark:label>
       <mark:label>test-et-validate</mark:label>
       <mark:label>test-validate</mark:label>
       <mark:label>test--validate</mark:label>
       <mark:label>test-etvalidate</mark:label>
       <mark:label>testetvalidate</mark:label>
       <mark:label>testvalidate</mark:label>
       <mark:label>testet-validate</mark:label>
       <mark:goodsAndServices>guitar</mark:goodsAndServices>
       <mark:regNum>1234</mark:regNum>
       <mark:regDate>2012-12-31T23:00:00.000Z</mark:regDate>
     </mark:trademark>
   </mark:mark>
  <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
   <SignedInfo>
    <CanonicalizationMethod
 Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    <SignatureMethod
 Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
    <Reference URI="#smd1">
     <Transforms>
      <Transform
 Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
     </Transforms>
     <DigestMethod
 Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
 <DigestValue>wgyW3nZPoEfpptlhRILKnOQnbdtU6ArM7ShrAfHgDFg=</DigestValue>
    </Reference>
   </SignedInfo>
   <SignatureValue>
 jMu4PfyQGiJBF0GWSEPFCJjmywCEqR2h4LD+ge6XQ+JnmKFFCuCZS/3SLKAx0L1w
 QDFO2e0Y69k2G7/LGE37X3vOflobFM1oGwja8+GMVraoto5xAd4/AF7eHukgAymD
 o9toxoa2h0yV4A4PmXzsU6S86XtCcUE+S/WM72nyn47zoUCzzPKHZBRyeWehVFQ+
 jYRMIAMzM57HHQA+6eaXefRvtPETgUO4aVIVSugc4OUAZZwbYcZrC6wOaQqqqAZi
 30aPOBYbAvHMSmWSS+hFkbshomJfHxb97TD2grlYNrQIzqXk7WbHWy2SYdA+sI/Z
 ipJsXNa6osTUw1CzA7jfwA==
   </SignatureValue>
   <KeyInfo>
    <X509Data>
    <X509Certificate>
 MIIESTCCAzGgAwIBAgIBAjANBgkqhkiG9w0BAQsFADBiMQswCQYDVQQGEwJVUzEL
 MAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJQ0FO
 TiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0EwHhcNMTMwMjA4MDAw
 MDAwWhcNMTgwMjA3MjM1OTU5WjBsMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex
 FDASBgNVBAcTC0xvcyBBbmdlbGVzMRcwFQYDVQQKEw5WYWxpZGF0b3IgVE1DSDEh
 MB8GA1UEAxMYVmFsaWRhdG9yIFRNQ0ggVEVTVCBDRVJUMIIBIjANBgkqhkiG9w0B
 AQEFAAOCAQ8AMIIBCgKCAQEAo/cwvXhbVYl0RDWWvoyeZpETVZVVcMCovUVNg/sw

 WinuMgEWgVQFrz0xA04pEhXCFVv4evbUpekJ5buqU1gmQyOsCKQlhOHTdPjvkC5u
 pDqa51Flk0TMaMkIQjs7aUKCmA4RG4tTTGK/EjR1ix8/D0gHYVRldy1YPrMP+ou7
 5bOVnIos+HifrAtrIv4qEqwLL4FTZAUpaCa2BmgXfy2CSRQbxD5Or1gcSa3vurh5
 sPMCNxqaXmIXmQipS+DuEBqMM8tldaN7RYojUEKrGVsNk5i9y2/7sjn1zyyUPf7v
 L4GgDYqhJYWV61DnXgx/Jd6CWxvsnDF6scscQzUTEl+hywIDAQABo4H/MIH8MAwG
 A1UdEwEB/wQCMAAwHQYDVR0OBBYEFPZEcIQcD/Bj2IFz/LERuo2ADJviMIGMBgNV
 HSMEgYQwgYGAFO0/7kEh3FuEKS+Q/kYHaD/W6wihoWakZDBiMQswCQYDVQQGEwJV
 UzELMAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJ
 Q0FOTiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0GCAQEwDgYDVR0P
 AQH/BAQDAgeAMC4GA1UdHwQnMCUwI6AhoB+GHWh0dHA6Ly9jcmwuaWNhbm4ub3Jn
 L3RtY2guY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQB2qSy7ui+43cebKUKwWPrzz9y/
 IkrMeJGKjo40n+9uekaw3DJ5EqiOf/qZ4pjBD++oR6BJCb6NQuQKwnoAz5lE4Ssu
 y5+i93oT3HfyVc4gNMIoHm1PS19l7DBKrbwbzAea/0jKWVzrvmV7TBfjxD3AQo1R
 bU5dBr6IjbdLFlnO5x0G0mrG7x5OUPuurihyiURpFDpwH8KAH1wMcCpXGXFRtGKk
 wydgyVYAty7otkl/z3bZkCVT34gPvF70sR6+QxUy8u0LzF5A/beYaZpxSYG31amL
 AdXitTWFipaIGea9lEGFM0L9+Bg7XzNn4nVLXokyEB3bgS4scG6QznX23FGk
   </X509Certificate>
   </X509Data>
   </KeyInfo>
  </Signature>
 </smd:signedMark>

 WinuMgEWgVQFrz0xA04pEhXCFVv4evbUpekJ5buqU1gmQyOsCKQlhOHTdPjvkC5u
 pDqa51Flk0TMaMkIQjs7aUKCmA4RG4tTTGK/EjR1ix8/D0gHYVRldy1YPrMP+ou7
 5bOVnIos+HifrAtrIv4qEqwLL4FTZAUpaCa2BmgXfy2CSRQbxD5Or1gcSa3vurh5
 sPMCNxqaXmIXmQipS+DuEBqMM8tldaN7RYojUEKrGVsNk5i9y2/7sjn1zyyUPf7v
 L4GgDYqhJYWV61DnXgx/Jd6CWxvsnDF6scscQzUTEl+hywIDAQABo4H/MIH8MAwG
 A1UdEwEB/wQCMAAwHQYDVR0OBBYEFPZEcIQcD/Bj2IFz/LERuo2ADJviMIGMBgNV
 HSMEgYQwgYGAFO0/7kEh3FuEKS+Q/kYHaD/W6wihoWakZDBiMQswCQYDVQQGEwJV
 UzELMAkGA1UECBMCQ0ExFDASBgNVBAcTC0xvcyBBbmdlbGVzMRMwEQYDVQQKEwpJ
 Q0FOTiBUTUNIMRswGQYDVQQDExJJQ0FOTiBUTUNIIFRFU1QgQ0GCAQEwDgYDVR0P
 AQH/BAQDAgeAMC4GA1UdHwQnMCUwI6AhoB+GHWh0dHA6Ly9jcmwuaWNhbm4ub3Jn
 L3RtY2guY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQB2qSy7ui+43cebKUKwWPrzz9y/
 IkrMeJGKjo40n+9uekaw3DJ5EqiOf/qZ4pjBD++oR6BJCb6NQuQKwnoAz5lE4Ssu
 y5+i93oT3HfyVc4gNMIoHm1PS19l7DBKrbwbzAea/0jKWVzrvmV7TBfjxD3AQo1R
 bU5dBr6IjbdLFlnO5x0G0mrG7x5OUPuurihyiURpFDpwH8KAH1wMcCpXGXFRtGKk
 wydgyVYAty7otkl/z3bZkCVT34gPvF70sR6+QxUy8u0LzF5A/beYaZpxSYG31amL
 AdXitTWFipaIGea9lEGFM0L9+Bg7XzNn4nVLXokyEB3bgS4scG6QznX23FGk
   </X509Certificate>
   </X509Data>
   </KeyInfo>
  </Signature>
 </smd:signedMark>

NOTE: The example shown above includes white space for indentation purposes. It is RECOMMENDED that SMDs do not include white space between the XML elements, in order to mitigate risks of invalidating the digital signature when transferring of SMDs between applications takes place.

注：上述示例包括用于缩进的空白。建议SMD不要在XML元素之间包含空格，以降低在应用程序之间传输SMD时使数字签名无效的风险。

2.4. Encoded Signed Mark

2.4. 编码符号标记

The <smd:encodedSignedMark> element contains an encoded form of an SMD (described in Section 2.3), with the encoding defined by the "encoding" attribute with the default "encoding" value of "base64" [RFC4648].

<smd:encodedSignedMark>元素包含smd的编码形式（如第2.3节所述），编码由“encoding”属性定义，默认“encoding”值为“base64”[RFC4648]。

The following is an example of a <smd:encodedSignedMark> element that uses the default "base64" for encoding a <smd:signedMark> element.

以下是<smd:encodedSignedMark>元素的示例，该元素使用默认的“base64”对<smd:signedMark>元素进行编码。

 <smd:encodedSignedMark
    xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNtZDpzaWduZWRNYXJ
 rIHhtbG5zOnNtZD0idXJuOmlldGY6cGFyYW1zOnhtbDpuczpzaWduZWRNYXJrLTEuMCIgaW
 ... (base64 data elided for brevity) ...
 PC9zbWQ6c2lnbmVkTWFyaz4=
 </smd:encodedSignedMark>

 <smd:encodedSignedMark
    xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNtZDpzaWduZWRNYXJ
 rIHhtbG5zOnNtZD0idXJuOmlldGY6cGFyYW1zOnhtbDpuczpzaWduZWRNYXJrLTEuMCIgaW
 ... (base64 data elided for brevity) ...
 PC9zbWQ6c2lnbmVkTWFyaz4=
 </smd:encodedSignedMark>

3. Formal Syntax

3. 形式语法

Two schemas are presented here. The first schema is the schema for the Signed Mark object. The second schema is the schema for the Mark object.

这里介绍了两种模式。第一个模式是有符号标记对象的模式。第二个模式是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.

这里给出的形式语法是对象映射的完整模式表示，适合于自动验证EPP XML实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。

3.1. Signed Mark Schema

3.1. 符号标记模式

  BEGIN
  <?xml version="1.0" encoding="UTF-8"?>
  <schema
    targetNamespace="urn:ietf:params:xml:ns:signedMark-1.0"
    xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
    xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
    xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
    xmlns="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified">

  BEGIN
  <?xml version="1.0" encoding="UTF-8"?>
  <schema
    targetNamespace="urn:ietf:params:xml:ns:signedMark-1.0"
    xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
    xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
    xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
    xmlns="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified">

    <annotation>
      <documentation>
        Schema for representing a Signed Mark object.
      </documentation>
    </annotation>

    <annotation>
      <documentation>
        Schema for representing a Signed Mark object.
      </documentation>
    </annotation>

    <import namespace="urn:ietf:params:xml:ns:mark-1.0" />
    <import namespace="http://www.w3.org/2000/09/xmldsig#" />

    <import namespace="urn:ietf:params:xml:ns:mark-1.0" />
    <import namespace="http://www.w3.org/2000/09/xmldsig#" />

    <!--
    Abstract Signed Mark object for replacement via substitution.
    -->
    <element name="abstractSignedMark" type="smd:abstractSignedMarkType"
     abstract="true"/>

    <!--
    Abstract Signed Mark object for replacement via substitution.
    -->
    <element name="abstractSignedMark" type="smd:abstractSignedMarkType"
     abstract="true"/>

    <!--
    Empty type for use in extending for a Signed Mark object.
    -->
    <complexType name="abstractSignedMarkType"/>

    <!--
    Empty type for use in extending for a Signed Mark object.
    -->
    <complexType name="abstractSignedMarkType"/>

    <element name="signedMark" type="smd:signedMarkType"
      substitutionGroup="smd:abstractSignedMark"/>

    <element name="signedMark" type="smd:signedMarkType"
      substitutionGroup="smd:abstractSignedMark"/>

    <element name="encodedSignedMark" type="smd:encodedSignedMarkType"/>

    <element name="encodedSignedMark" type="smd:encodedSignedMarkType"/>

    <complexType name="signedMarkType">
      <complexContent>
        <extension base="smd:abstractSignedMarkType">
          <sequence>
            <element name="id" type="mark:idType"/>
            <element name="issuerInfo" type="smd:issuerInfoType"/>
            <element name="notBefore" type="dateTime"/>
            <element name="notAfter" type="dateTime"/>
            <element ref="mark:abstractMark"/>
            <element ref="dsig:Signature"/>
          </sequence>
          <attribute name="id" type="ID" use="required"/>
        </extension>
      </complexContent>
    </complexType>

    <complexType name="signedMarkType">
      <complexContent>
        <extension base="smd:abstractSignedMarkType">
          <sequence>
            <element name="id" type="mark:idType"/>
            <element name="issuerInfo" type="smd:issuerInfoType"/>
            <element name="notBefore" type="dateTime"/>
            <element name="notAfter" type="dateTime"/>
            <element ref="mark:abstractMark"/>
            <element ref="dsig:Signature"/>
          </sequence>
          <attribute name="id" type="ID" use="required"/>
        </extension>
      </complexContent>
    </complexType>

    <complexType name="issuerInfoType">
      <sequence>
        <element name="org" type="token"/>
        <element name="email" type="mark:minTokenType"/>
        <element name="url" type="token" minOccurs="0"/>
        <element name="voice" type="mark:e164Type" minOccurs="0"/>
      </sequence>
      <attribute name="issuerID" type="token" use="required"/>
    </complexType>

    <complexType name="issuerInfoType">
      <sequence>
        <element name="org" type="token"/>
        <element name="email" type="mark:minTokenType"/>
        <element name="url" type="token" minOccurs="0"/>
        <element name="voice" type="mark:e164Type" minOccurs="0"/>
      </sequence>
      <attribute name="issuerID" type="token" use="required"/>
    </complexType>

    <complexType name="encodedSignedMarkType">
      <simpleContent>
        <extension base="token">
          <attribute name="encoding" type="token" default="base64"/>
        </extension>
      </simpleContent>
    </complexType>
  </schema>
  END

    <complexType name="encodedSignedMarkType">
      <simpleContent>
        <extension base="token">
          <attribute name="encoding" type="token" default="base64"/>
        </extension>
      </simpleContent>
    </complexType>
  </schema>
  END

3.2. Mark Schema

3.2. 标记模式

 BEGIN
 <?xml version="1.0" encoding="UTF-8"?>
 <schema
   targetNamespace="urn:ietf:params:xml:ns:mark-1.0"
   xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
   xmlns="http://www.w3.org/2001/XMLSchema"
   elementFormDefault="qualified">

 BEGIN
 <?xml version="1.0" encoding="UTF-8"?>
 <schema
   targetNamespace="urn:ietf:params:xml:ns:mark-1.0"
   xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
   xmlns="http://www.w3.org/2001/XMLSchema"
   elementFormDefault="qualified">

   <annotation>
     <documentation>

   <annotation>
     <documentation>

       Schema for representing a Trademark, also referred to
       as Mark.
     </documentation>
   </annotation>

       Schema for representing a Trademark, also referred to
       as Mark.
     </documentation>
   </annotation>

   <!--
   Abstract Mark object for replacement via substitution.
   -->
   <element name="abstractMark" type="mark:abstractMarkType"
     abstract="true"/>

   <!--
   Abstract Mark object for replacement via substitution.
   -->
   <element name="abstractMark" type="mark:abstractMarkType"
     abstract="true"/>

   <!--
   <mark:mark> element definition
   -->
   <element name="mark" type="mark:markType"
     substitutionGroup="mark:abstractMark"/>

   <!--
   <mark:mark> element definition
   -->
   <element name="mark" type="mark:markType"
     substitutionGroup="mark:abstractMark"/>

   <!--
   Empty type for use in extending for a Mark object.
   -->
   <complexType name="abstractMarkType"/>

   <!--
   Empty type for use in extending for a Mark object.
   -->
   <complexType name="abstractMarkType"/>

   <!--
   <mark:mark> child elements
   -->
   <complexType name="markType">
     <complexContent>
       <extension base="mark:abstractMarkType">
         <sequence>
           <element name="trademark" type="mark:trademarkType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="treatyOrStatute"
             type="mark:treatyOrStatuteType" minOccurs="0"
             maxOccurs="unbounded"/>
           <element name="court" type="mark:courtType" minOccurs="0"
             maxOccurs="unbounded"/>
         </sequence>
       </extension>
     </complexContent>
   </complexType>

   <!--
   <mark:mark> child elements
   -->
   <complexType name="markType">
     <complexContent>
       <extension base="mark:abstractMarkType">
         <sequence>
           <element name="trademark" type="mark:trademarkType"
             minOccurs="0" maxOccurs="unbounded"/>
           <element name="treatyOrStatute"
             type="mark:treatyOrStatuteType" minOccurs="0"
             maxOccurs="unbounded"/>
           <element name="court" type="mark:courtType" minOccurs="0"
             maxOccurs="unbounded"/>
         </sequence>
       </extension>
     </complexContent>
   </complexType>

   <complexType name="holderType">
     <sequence>
       <element name="name" type="token" minOccurs="0"/>
       <element name="org" type="token" minOccurs="0"/>
       <element name="addr" type="mark:addrType"/>
       <element name="voice" type="mark:e164Type" minOccurs="0"/>
       <element name="fax" type="mark:e164Type" minOccurs="0"/>

   <complexType name="holderType">
     <sequence>
       <element name="name" type="token" minOccurs="0"/>
       <element name="org" type="token" minOccurs="0"/>
       <element name="addr" type="mark:addrType"/>
       <element name="voice" type="mark:e164Type" minOccurs="0"/>
       <element name="fax" type="mark:e164Type" minOccurs="0"/>

       <element name="email" type="mark:minTokenType" minOccurs="0"/>
     </sequence>
     <attribute name="entitlement" type="mark:entitlementType"/>
   </complexType>

       <element name="email" type="mark:minTokenType" minOccurs="0"/>
     </sequence>
     <attribute name="entitlement" type="mark:entitlementType"/>
   </complexType>

   <complexType name="contactType">
     <sequence>
       <element name="name" type="token"/>
       <element name="org" type="token" minOccurs="0"/>
       <element name="addr" type="mark:addrType"/>
       <element name="voice" type="mark:e164Type"/>
       <element name="fax" type="mark:e164Type" minOccurs="0"/>
       <element name="email" type="mark:minTokenType"/>
     </sequence>
     <attribute name="type" type="mark:contactTypeType"/>
   </complexType>

   <complexType name="contactType">
     <sequence>
       <element name="name" type="token"/>
       <element name="org" type="token" minOccurs="0"/>
       <element name="addr" type="mark:addrType"/>
       <element name="voice" type="mark:e164Type"/>
       <element name="fax" type="mark:e164Type" minOccurs="0"/>
       <element name="email" type="mark:minTokenType"/>
     </sequence>
     <attribute name="type" type="mark:contactTypeType"/>
   </complexType>

   <complexType name="trademarkType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="jurisdiction" type="mark:ccType"/>
       <element name="class" type="integer" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="apId" type="token" minOccurs="0"/>
       <element name="apDate" type="dateTime" minOccurs="0"/>
       <element name="regNum" type="token"/>
       <element name="regDate" type="dateTime"/>
       <element name="exDate" type="dateTime" minOccurs="0"/>
     </sequence>
   </complexType>

   <complexType name="trademarkType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="jurisdiction" type="mark:ccType"/>
       <element name="class" type="integer" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="apId" type="token" minOccurs="0"/>
       <element name="apDate" type="dateTime" minOccurs="0"/>
       <element name="regNum" type="token"/>
       <element name="regDate" type="dateTime"/>
       <element name="exDate" type="dateTime" minOccurs="0"/>
     </sequence>
   </complexType>

   <complexType name="treatyOrStatuteType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="protection" type="mark:protectionType"

   <complexType name="treatyOrStatuteType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="protection" type="mark:protectionType"

         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="refNum" type="token"/>
       <element name="proDate" type="dateTime"/>
       <element name="title" type="token"/>
       <element name="execDate" type="dateTime"/>
     </sequence>
   </complexType>

         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="refNum" type="token"/>
       <element name="proDate" type="dateTime"/>
       <element name="title" type="token"/>
       <element name="execDate" type="dateTime"/>
     </sequence>
   </complexType>

   <complexType name="courtType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="refNum" type="token"/>
       <element name="proDate" type="dateTime"/>
       <element name="cc" type="mark:ccType"/>
       <element name="region" type="token" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="courtName" type="token"/>
     </sequence>
   </complexType>

   <complexType name="courtType">
     <sequence>
       <element name="id" type="mark:idType"/>
       <element name="markName" type="token"/>
       <element name="holder" type="mark:holderType"
         maxOccurs="unbounded" />
       <element name="contact" type="mark:contactType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="label" type="mark:labelType" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="goodsAndServices" type="token" />
       <element name="refNum" type="token"/>
       <element name="proDate" type="dateTime"/>
       <element name="cc" type="mark:ccType"/>
       <element name="region" type="token" minOccurs="0"
         maxOccurs="unbounded"/>
       <element name="courtName" type="token"/>
     </sequence>
   </complexType>

   <!--
   Address (<mark:addr>) child elements
   -->
   <complexType name="addrType">
     <sequence>
       <element name="street" type="token" minOccurs="1" maxOccurs="3"/>
       <element name="city" type="token"/>
       <element name="sp" type="token" minOccurs="0"/>
       <element name="pc" type="mark:pcType" minOccurs="0"/>
       <element name="cc" type="mark:ccType"/>
     </sequence>
   </complexType>

   <!--
   Address (<mark:addr>) child elements
   -->
   <complexType name="addrType">
     <sequence>
       <element name="street" type="token" minOccurs="1" maxOccurs="3"/>
       <element name="city" type="token"/>
       <element name="sp" type="token" minOccurs="0"/>
       <element name="pc" type="mark:pcType" minOccurs="0"/>
       <element name="cc" type="mark:ccType"/>
     </sequence>
   </complexType>

   <!--
   <mark:protection> child elements
   -->
   <complexType name="protectionType">

   <!--
   <mark:protection> child elements
   -->
   <complexType name="protectionType">

     <sequence>
       <element name="cc" type="mark:ccType"/>
       <element name="region" type="token" minOccurs="0"/>
       <element name="ruling" type="mark:ccType"
         minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
   </complexType>

     <sequence>
       <element name="cc" type="mark:ccType"/>
       <element name="region" type="token" minOccurs="0"/>
       <element name="ruling" type="mark:ccType"
         minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
   </complexType>

   <!--
   Postal code definition
   -->
   <simpleType name="pcType">
     <restriction base="token">
       <maxLength value="16"/>
     </restriction>
   </simpleType>

   <!--
   Postal code definition
   -->
   <simpleType name="pcType">
     <restriction base="token">
       <maxLength value="16"/>
     </restriction>
   </simpleType>

   <!--
   Country code definition
   -->
   <simpleType name="ccType">
     <restriction base="token">
       <length value="2"/>
     </restriction>
   </simpleType>

   <!--
   Country code definition
   -->
   <simpleType name="ccType">
     <restriction base="token">
       <length value="2"/>
     </restriction>
   </simpleType>

   <!--
   Phone number with extension definition
   -->
   <complexType name="e164Type">
     <simpleContent>
       <extension base="mark:e164StringType">
         <attribute name="x" type="token"/>
       </extension>
     </simpleContent>
   </complexType>

   <!--
   Phone number with extension definition
   -->
   <complexType name="e164Type">
     <simpleContent>
       <extension base="mark:e164StringType">
         <attribute name="x" type="token"/>
       </extension>
     </simpleContent>
   </complexType>

   <!--
   Phone number with extension definition
   -->
   <simpleType name="e164StringType">
     <restriction base="token">
       <pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
       <maxLength value="17"/>
     </restriction>
   </simpleType>

   <!--
   Phone number with extension definition
   -->
   <simpleType name="e164StringType">
     <restriction base="token">
       <pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
       <maxLength value="17"/>
     </restriction>
   </simpleType>

<!--

   Id type definition
   -->
   <simpleType name="idType">
     <restriction base="token">
       <pattern value="\d+-\d+"/>
     </restriction>
   </simpleType>

   Id type definition
   -->
   <simpleType name="idType">
     <restriction base="token">
       <pattern value="\d+-\d+"/>
     </restriction>
   </simpleType>

   <!--
   DNS label type definition
   -->
   <simpleType name="labelType">
     <restriction base="token">
       <minLength value="1"/>
       <maxLength value="63"/>
       <pattern value="[a-zA-Z0-9]([a-zA-Z0-9\-]*[a-zA-Z0-9])?"/>
     </restriction>
   </simpleType>

   <!--
   DNS label type definition
   -->
   <simpleType name="labelType">
     <restriction base="token">
       <minLength value="1"/>
       <maxLength value="63"/>
       <pattern value="[a-zA-Z0-9]([a-zA-Z0-9\-]*[a-zA-Z0-9])?"/>
     </restriction>
   </simpleType>

   <!--
   Type used for email addresses
   -->
   <simpleType name="minTokenType">
     <restriction base="token">
       <minLength value="1"/>
     </restriction>
   </simpleType>

   <!--
   Type used for email addresses
   -->
   <simpleType name="minTokenType">
     <restriction base="token">
       <minLength value="1"/>
     </restriction>
   </simpleType>

   <simpleType name="entitlementType">
     <restriction base="token">
       <enumeration value="owner"/>
       <enumeration value="assignee"/>
       <enumeration value="licensee"/>
     </restriction>
   </simpleType>

   <simpleType name="entitlementType">
     <restriction base="token">
       <enumeration value="owner"/>
       <enumeration value="assignee"/>
       <enumeration value="licensee"/>
     </restriction>
   </simpleType>

   <simpleType name="contactTypeType">
     <restriction base="token">
       <enumeration value="owner"/>
       <enumeration value="agent"/>
       <enumeration value="thirdparty"/>
     </restriction>
   </simpleType>
 </schema>
 END

   <simpleType name="contactTypeType">
     <restriction base="token">
       <enumeration value="owner"/>
       <enumeration value="agent"/>
       <enumeration value="thirdparty"/>
     </restriction>
   </simpleType>
 </schema>
 END

4. IANA Considerations

4. IANA考虑

This document uses URNs to describe XML namespaces and XML schemas conforming to the registry mechanism described in [RFC3688]. IANA has registered two URI assignments: signed mark (signedMark-1.0) and mark (mark-1.0).

本文档使用URN来描述符合[RFC3688]中描述的注册表机制的XML名称空间和XML模式。IANA注册了两个URI分配：signedMark（signedMark-1.0）和mark（mark-1.0）。

o The signed mark namespace (signedMark-1.0) has been registered in the "ns" registry.

o 签名标记命名空间（signedMark-1.0）已在“ns”注册表中注册。

      URI: urn:ietf:params:xml:ns:signedMark-1.0

      URI: urn:ietf:params:xml:ns:signedMark-1.0

Registrant Contact: IESG

注册联系人：IESG

XML: None. Namespace URIs do not represent an XML specification.

XML：没有。命名空间URI不表示XML规范。

o The signed mark schema (signedMark-1.0) has been registered in the "schema" registry.

o 已在“schema”注册表中注册签名标记架构（signedMark-1.0）。

      URI: urn:ietf:params:xml:schema:signedMark-1.0

      URI: urn:ietf:params:xml:schema:signedMark-1.0

Registrant Contact: IESG

注册联系人：IESG

XML: See the "Formal Syntax" section of this document.

XML：请参阅本文档的“正式语法”部分。

o The mark namespace (mark-1.0) has been registered in the "ns" registry.

o 标记命名空间（mark-1.0）已在“ns”注册表中注册。

      URI: urn:ietf:params:xml:ns:mark-1.0

      URI: urn:ietf:params:xml:ns:mark-1.0

Registrant Contact: IESG

注册联系人：IESG

XML: None. Namespace URIs do not represent an XML specification.

XML：没有。命名空间URI不表示XML规范。

o The mark schema (mark-1.0) has been registered in the "schema" registry.

o 标记架构（mark-1.0）已在“架构”注册表中注册。

      URI: urn:ietf:params:xml:schema:mark-1.0

      URI: urn:ietf:params:xml:schema:mark-1.0

Registrant Contact: IESG

注册联系人：IESG

XML: See the "Formal Syntax" section of this document.

XML：请参阅本文档的“正式语法”部分。

5. Security Considerations

5. 安全考虑

The security of a Signed Mark object depends on the security of the underlying XML Digital Signature (DSIG) algorithms. As such, all the security considerations from [XMLDSIG] apply here as well.

签名标记对象的安全性取决于底层XML数字签名（DSIG）算法的安全性。因此，[XMLDSIG]中的所有安全注意事项也适用于这里。

The digital signature algorithm used in Signed Mark objects SHOULD be RSA-SHA256 [RFC6931]. The size of the RSA key SHOULD be at least 2048 bits. A valid reason for choosing something else would be if RSA-SHA256 is deemed to not provide sufficient security.

签名标记对象中使用的数字签名算法应为RSA-SHA256[RFC6931]。RSA密钥的大小应至少为2048位。如果RSA-SHA256被认为没有提供足够的安全性，那么选择其他产品的一个合理理由就是。

In the case of the ICANN TMCH, Signed Mark objects use the algorithms for digesting and signing recommended in this document.

在ICANN TMCH的情况下，签名标记对象使用本文档中推荐的算法进行摘要和签名。

Signed Mark objects are used primarily for domain name registrations in gTLDs during the Sunrise Period, but other third parties might be using them. A party using Signed Mark objects should verify that the digital signature is valid based on local policy. In the case of gTLDs, the Rights Protection Mechanism Requirements document [ICANN-TMCH] defines such policy, and the PKI is defined in [TMCH]. Implementations will need to implement such a PKI (or an equivalent) in order for the signatures defined in this document to have any useful semantics.

签名标记对象主要用于日出期间gTLDs中的域名注册，但其他第三方可能正在使用它们。使用签名标记对象的一方应根据本地策略验证数字签名是否有效。对于gTLDs，权利保护机制要求文件[ICANN-TMCH]定义了此类政策，PKI在[TMCH]中定义。为了使本文档中定义的签名具有任何有用的语义，实现将需要实现这样的PKI（或等效物）。

6. References

6. 工具书类

6.1. Normative References

6.1. 规范性引用文件

[ICANN-TMCH] ICANN, "Trademark Clearinghouse; Rights Protection Mechanism Requirements", 2013, <http://newgtlds.icann.org/en/about/ trademark-clearinghouse/rpm-requirements-30sep13-en.pdf>.

[ICANN-TMCH]ICANN，“商标清算所；权利保护机制要求”，2013年<http://newgtlds.icann.org/en/about/ 商标交换所/rpm-requirements-30sep13-en.pdf>。

[ISO3166-2] ISO, "International Standard for country codes and codes for their subdivisions", 2006, <http://www.iso.org/iso/home/standards/country_codes.htm>.

[ISO3166-2]ISO，“国家代码及其细分代码的国际标准”，2006年<http://www.iso.org/iso/home/standards/country_codes.htm>.

[ITU.E164.2005] International Telecommunication Union, "The international public telecommunication numbering plan", ITU-T Recommendation E.164, November 2010, <https://www.itu.int/rec/T-REC-E.164-201011-I/en>.

[ITU.E164.2005]国际电信联盟，“国际公共电信编号计划”，ITU-T建议E.164，2010年11月<https://www.itu.int/rec/T-REC-E.164-201011-I/en>.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.

[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.

[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <http://www.rfc-editor.org/info/rfc3688>.

[RFC3688]Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，DOI 10.17487/RFC3688，2004年1月<http://www.rfc-editor.org/info/rfc3688>.

[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, <http://www.rfc-editor.org/info/rfc4648>.

[RFC4648]Josefsson，S.，“Base16、Base32和Base64数据编码”，RFC 4648，DOI 10.17487/RFC4648，2006年10月<http://www.rfc-editor.org/info/rfc4648>.

[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, <http://www.rfc-editor.org/info/rfc5322>.

[RFC5322]Resnick，P.，Ed.，“互联网信息格式”，RFC 5322，DOI 10.17487/RFC5322，2008年10月<http://www.rfc-editor.org/info/rfc5322>.

[RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, DOI 10.17487/RFC5890, August 2010, <http://www.rfc-editor.org/info/rfc5890>.

[RFC5890]Klensin，J.，“应用程序的国际化域名（IDNA）：定义和文档框架”，RFC 5890，DOI 10.17487/RFC5890，2010年8月<http://www.rfc-editor.org/info/rfc5890>.

[RFC6931] Eastlake 3rd, D., "Additional XML Security Uniform Resource Identifiers (URIs)", RFC 6931, DOI 10.17487/RFC6931, April 2013, <http://www.rfc-editor.org/info/rfc6931>.

[RFC6931]Eastlake 3rd，D.，“其他XML安全统一资源标识符（URI）”，RFC 6931，DOI 10.17487/RFC6931，2013年4月<http://www.rfc-editor.org/info/rfc6931>.

[WIPO-NICE-CLASSES] WIPO, "Nice Classification", January 2016, <http://www.wipo.int/classifications/nice/en>.

[WIPO-NICE-CLASSES]WIPO，“NICE分类”，2016年1月<http://www.wipo.int/classifications/nice/en>.

[WIPO.ST3] WIPO, "Recommended standard on two-letter codes for the representation of states, other entities and intergovernmental organizations", Standard ST.3, February 2015, <http://www.wipo.int/standards/en/pdf/03-03-01.pdf>.

[WIPO.ST3]WIPO，“国家、其他实体和政府间组织代表的双字母代码建议标准”，标准ST.3，2015年2月<http://www.wipo.int/standards/en/pdf/03-03-01.pdf>.

[XMLC14N] W3C, "Exclusive XML Canonicalization Version 1.0", W3C Recommendation, July 2002, <http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718>.

[XMLC14N]W3C，“专用XML规范化版本1.0”，W3C建议，2002年7月<http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718>.

[XMLDSIG] W3C, "XML Signature Syntax and Processing Version 1.1", W3C Recommendation, April 2013, <http://www.w3.org/TR/xmldsig-core1>.

[XMLDSIG]W3C，“XML签名语法和处理版本1.1”，W3C建议，2013年4月<http://www.w3.org/TR/xmldsig-core1>.

6.2. Informative References

6.2. 资料性引用

[EPP-LAUNCH] Gould, J., Tan, W., and G. Brown, "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)", Work in Progress, draft-ietf-regext-launchphase-00, April 2016.

[EPP-LAUNCH]Gould，J.，Tan，W.，和G.Brown，“可扩展资源调配协议（EPP）的启动阶段映射”，正在进行的工作，草稿-ietf-regext-launchphase-00，2016年4月。

[RFC5105] Lendl, O., "ENUM Validation Token Format Definition", RFC 5105, DOI 10.17487/RFC5105, December 2007, <http://www.rfc-editor.org/info/rfc5105>.

[RFC5105]伦德尔，O.，“枚举验证令牌格式定义”，RFC 5105，DOI 10.17487/RFC5105，2007年12月<http://www.rfc-editor.org/info/rfc5105>.

[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, <http://www.rfc-editor.org/info/rfc5730>.

[RFC5730]Hollenbeck，S.，“可扩展资源调配协议（EPP）”，STD 69，RFC 5730，DOI 10.17487/RFC5730，2009年8月<http://www.rfc-editor.org/info/rfc5730>.

[TMCH] Lozano, G., "ICANN TMCH functional specifications", Work in Progress, draft-ietf-regext-tmch-func-spec-00, April 2016.

[TMCH]Lozano，G.，“ICANN TMCH功能规范”，正在进行的工作，草稿-ietf-regext-TMCH-func-spec-00，2016年4月。

Acknowledgements

致谢

Special thanks to Chris Wright for creating the first prototype of an SMD and to James Gould, Wil Tan, and Gavin Brown for creating the mark and SMD definitions in "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)" [EPP-LAUNCH], on which this document is based. Portions of the Security Considerations section were shamefully copied from RFC 5105 [RFC5105]. The author would like to acknowledge the following individuals for their contributions to this document: Scott Hollenbeck and Jan Jansen.

特别感谢Chris Wright创建了SMD的第一个原型，感谢James Gould、Wil Tan和Gavin Brown在本文档所基于的“可扩展资源调配协议（EPP）的启动阶段映射”[EPP-Launch]中创建了标记和SMD定义。安全注意事项部分内容是从RFC 5105[RFC5105]可耻地复制而来的。作者要感谢以下个人对本文件的贡献：Scott Hollenbeck和Jan Jansen。

Author's Address

作者地址

Gustavo Lozano ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90292 United States

Gustavo Lozano ICANN美国加利福尼亚州洛杉矶滨水路12025号300室90292

   Phone: +1.3103015800
   Email: gustavo.lozano@icann.org

   Phone: +1.3103015800
   Email: gustavo.lozano@icann.org