Network Working Group S. Hollenbeck
Request for Comments: 3915 VeriSign, Inc.
Category: Standards Track September 2004
Network Working Group S. Hollenbeck
Request for Comments: 3915 VeriSign, Inc.
Category: Standards Track September 2004
Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)
可扩展配置协议（EPP）的域注册表宽限期映射
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the management of Domain Name System (DNS) domain names subject to "grace period" policies defined by the Internet Corporation for Assigned Names and Numbers (ICANN). Grace period policies exist to allow protocol actions to be reversed or otherwise revoked during a short period of time after the protocol action has been performed. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for grace period processing.
本文档描述了一种可扩展配置协议（EPP）扩展映射，用于管理域名系统（DNS）域名，该域名受互联网名称和数字分配公司（ICANN）定义的“宽限期”政策的约束。宽限期策略允许在协议操作执行后的短时间内撤销或撤销协议操作。在XML中指定，此映射扩展了EPP域名映射，以提供宽限期处理所需的其他功能。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used In This Document. . . . . . . . . . . . 4
2. Redemption Grace Period State Diagram . . . . . . . . . . . . 4
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Status Values . . . . . . . . . . . . . . . . . . . . . 6
3.2. Registration Data and Supporting Information . . . . . . 7
3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . 7
3.4. Client Statements . . . . . . . . . . . . . . . . . . . 8
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.1 EPP Query Commands . . . . . . . . . . . . . . . . . . . 8
4.1.1. EPP <check> Command . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . 8
4.1.3. EPP <transfer> Command . . . . . . . . . . . . . 11
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
4.2.1. EPP <create> Command . . . . . . . . . . . . . . 12
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . 12
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . 12
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . 12
4.2.5. EPP <update> Command . . . . . . . . . . . . . . 12
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Internationalization Considerations . . . . . . . . . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8. Security Considerations . . . . . . . . . . . . . . . . . . . 20
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. Normative References . . . . . . . . . . . . . . . . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used In This Document. . . . . . . . . . . . 4
2. Redemption Grace Period State Diagram . . . . . . . . . . . . 4
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Status Values . . . . . . . . . . . . . . . . . . . . . 6
3.2. Registration Data and Supporting Information . . . . . . 7
3.3. Dates and Times . . . . . . . . . . . . . . . . . . . . 7
3.4. Client Statements . . . . . . . . . . . . . . . . . . . 8
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.1 EPP Query Commands . . . . . . . . . . . . . . . . . . . 8
4.1.1. EPP <check> Command . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . 8
4.1.3. EPP <transfer> Command . . . . . . . . . . . . . 11
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11
4.2.1. EPP <create> Command . . . . . . . . . . . . . . 12
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . 12
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . 12
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . 12
4.2.5. EPP <update> Command . . . . . . . . . . . . . . 12
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Internationalization Considerations . . . . . . . . . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8. Security Considerations . . . . . . . . . . . . . . . . . . . 20
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. Normative References . . . . . . . . . . . . . . . . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 23
This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) described in RFC 3730 [1]. This mapping, an extension of the domain name mapping described in RFC 3731 [2], is specified using the Extensible Markup Language (XML) 1.0 [3] and XML Schema notation ([4], [5]).
本文档描述了RFC 3730[1]中描述的可扩展资源调配协议（EPP）1.0版的扩展映射。此映射是RFC 3731[2]中描述的域名映射的扩展，使用可扩展标记语言（XML）1.0[3]和XML模式符号（[4]，[5]）指定。
The EPP core protocol specification [1] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document.
EPP核心协议规范[1]提供了EPP命令和响应结构的完整描述。要理解本文档中描述的映射，必须彻底理解基本协议规范。
Over the course of several months in 2002, The Internet Corporation for Assigned Names and Numbers (ICANN) developed an implementation proposal to provide a "grace period" for Domain Name System (DNS) domain name recovery (or redemption) before a domain name is purged from the repository of the authoritative registry for the domain name. This mapping extends the EPP domain <update> command to initiate the redemption process for a domain name that has entered the Redemption Grace Period (RGP) and it extends the EPP domain <info> response to identify the status of domains that have entered various grace periods defined by ICANN policy.
在2002年的几个月里，互联网名称和数字分配公司（ICANN）制定了一项实施方案，在域名从权威域名注册库中清除之前，为域名系统（DNS）域名恢复（或赎回）提供“宽限期”。此映射扩展了EPP domain<update>命令，以启动已进入赎回宽限期（RGP）的域名的赎回过程，并扩展了EPP domain<info>响应，以识别已进入ICANN策略定义的各种宽限期的域的状态。
In March 2003, ICANN published a task force report describing other domain registry grace periods related to EPP operations. This mapping describes extension status values to note the grace periods described in the report, including:
2003年3月，ICANN发布了一份工作组报告，描述了与EPP操作相关的其他域注册宽限期。此映射描述扩展状态值，以记录报告中描述的宽限期，包括：
o An "add grace period" after the initial registration of a domain name. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the registration.
o 域名初始注册后的“添加宽限期”。如果域名在此期间被注册官删除，注册官将向注册官支付注册费用。
o An "auto-renew grace period" after a domain name registration period expires and is extended (renewed) automatically by the registry. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the renewal.
o 域名注册期到期后的“自动续订宽限期”，由注册中心自动延长（续订）。如果域名在此期间被注册官删除，注册官将向注册官提供续期费用贷项。
o A "renew grace period" after a domain name registration period is explicitly extended (renewed) by the registrar. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the renewal.
o 域名注册期被注册人明确延长（续期）后的“续期宽限期”。如果域名在此期间被注册官删除，注册官将向注册官提供续期费用贷项。
o A "transfer grace period" after the successful transfer of domain name registration sponsorship from one registrar to another registrar. If the domain name is deleted by the new sponsoring registrar during this period, the registry provides a credit to the registrar for the cost of the transfer.
o 域名注册赞助从一个注册商成功转让给另一个注册商后的“转让宽限期”。如果域名在此期间被新的发起注册机构删除，注册机构将向注册机构支付转让费用。
Each grace period exists for a specific period of time that is typically measured in days. The duration of each grace period is a matter of registry operational policy that is not addressed in this document.
每个宽限期都有一段特定的时间，通常以天为单位。每个宽限期的期限是本文件未涉及的注册中心运营政策问题。
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 BCP 14, RFC 2119 [6].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[6]中的描述进行解释。
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 is provided only to illustrate element relationships and is not a REQUIRED feature of this specification.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空白仅用于说明元素关系，而不是本规范的必需功能。
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.
XML区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须按照提供的字符大小写进行解释，以开发一致的实现。
The Redemption Grace Period (RGP) involves several domain state transitions as a domain name moves through the redemption process:
赎回宽限期（RGP）涉及域名在赎回过程中的几个域状态转换：
1. A domain is initially in the EPP "ok" status, or some other status that allows processing of the EPP <delete> command.
1. 域最初处于EPP“ok”状态，或其他允许处理EPP<delete>命令的状态。
2. A <delete> command is received and processed for the domain name.
2. 接收并处理域名的<delete>命令。
3. RGP begins once the <delete> command is processed successfully. The EPP status changes to "pendingDelete", and the RGP status is initialized to "redemptionPeriod". The domain remains in this state until either a <restore> operation is requested or the redemption period elapses.
3. 成功处理<delete>命令后，RGP开始。EPP状态更改为“pendingDelete”，RGP状态初始化为“redemptionPeriod”。域将保持此状态，直到请求<restore>操作或赎回期结束。
4. A <restore> operation can be requested using the extended EPP <update> command. Go to step 8 if the redemption period elapses before a <restore> request is received.
4. 可以使用扩展的EPP<update>命令请求<restore>操作。如果在收到<restore>请求之前赎回期已过，请转至步骤8。
5. If the <restore> is successful, the Registry waits to receive a restore report from the registrar for a period of time defined by the Registry. The EPP status remains "pendingDelete" and the RGP status changes to "pendingRestore". While this extension defines a method to deliver a restore report via EPP, an out-of-band mechanism (such as a web site) can also be used to deliver restore reports.
5. 如果<restore>成功，注册表将在注册表定义的一段时间内等待从注册器接收恢复报告。EPP状态保持为“pendingDelete”，RGP状态更改为“PendingStore”。虽然此扩展定义了通过EPP交付恢复报告的方法，但带外机制（如网站）也可用于交付恢复报告。
6. The domain name returns to the redemption period state (state 3) if a restore report is not received.
6. 如果未收到恢复报告，域名将返回到赎回期状态（状态3）。
7. If a restore report is received the EPP status returns to "ok" (or whatever it was prior to processing the <delete> command), and the RGP status is removed completely.
7. 如果收到恢复报告，EPP状态将返回到“ok”（或处理<delete>命令之前的任何状态），并且RGP状态将完全删除。
8. The redemption period elapses before a <restore> request is received.
8. 赎回期在收到<restore>请求之前结束。
9. The EPP status remains "pendingDelete" and the RGP status changes to "pendingDelete". The domain name remains in this state for a period of time defined by the Registry.
9. EPP状态保持为“pendingDelete”，RGP状态更改为“pendingDelete”。域名在注册中心定义的一段时间内保持此状态。
10. The domain name is purged once the pending delete period elapses.
10. 一旦挂起的删除期结束，域名将被清除。
11. The domain name is available for re-registration.
11. 该域名可重新注册。
Figure 1: RGP State Diagram
图1:RGP状态图
|
v
+----------------------+ (2) +----------------------+
|EPP: ok (1)| <delete> |EPP: pendingDelete (3)|
|RGP: N/A |--------->|RGP: redemptionPeriod |
+----------------------+ +----------------------+
^ (4) | ^ |
| <restore> | | No (8) |
| +-----------+ | <restore> |
| | | |
| v | v
| +----------------------+ | +----------------------+
| |EPP: pendingDelete (5)| | |EPP: pendingDelete (9)|
| |RGP: pendingRestore |---------+ |RGP: pendingDelete |
| +----------------------+ Report +----------------------+
| | not (6) |
| (7) | Received Purge (10) |
| Report Received | |
+--------------------+ v
+----------------------+
| Purged (11)|
| |
+----------------------+
|
v
+----------------------+ (2) +----------------------+
|EPP: ok (1)| <delete> |EPP: pendingDelete (3)|
|RGP: N/A |--------->|RGP: redemptionPeriod |
+----------------------+ +----------------------+
^ (4) | ^ |
| <restore> | | No (8) |
| +-----------+ | <restore> |
| | | |
| v | v
| +----------------------+ | +----------------------+
| |EPP: pendingDelete (5)| | |EPP: pendingDelete (9)|
| |RGP: pendingRestore |---------+ |RGP: pendingDelete |
| +----------------------+ Report +----------------------+
| | not (6) |
| (7) | Received Purge (10) |
| Report Received | |
+--------------------+ v
+----------------------+
| Purged (11)|
| |
+----------------------+
This extension adds additional elements to the EPP domain name mapping [2]. Only new element descriptions are described here.
此扩展将向EPP域名映射添加其他元素[2]。这里只描述新元素描述。
This extension defines new status values to represent the different states that a domain name can be in as a result of grace period processing. These are:
此扩展定义了新的状态值，以表示由于宽限期处理，域名可能处于的不同状态。这些是：
addPeriod: This grace period is provided after the initial registration of a domain name. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the registration.
addPeriod：此宽限期在域名首次注册后提供。如果域名在此期间被注册官删除，注册官将向注册官支付注册费用。
autoRenewPeriod: This grace period is provided after a domain name registration period expires and is extended (renewed) automatically by the registry. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the renewal.
autoRenewPeriod：此宽限期在域名注册期到期后提供，并由注册中心自动延长（续订）。如果域名在此期间被注册官删除，注册官将向注册官提供续期费用贷项。
renewPeriod: This grace period is provided after a domain name registration period is explicitly extended (renewed) by the registrar. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the renewal.
续展期：该宽限期是在域名注册机构明确延长（续展）域名注册期后提供的。如果域名在此期间被注册官删除，注册官将向注册官提供续期费用贷项。
transferPeriod: This grace period is provided after the successful transfer of domain name registration sponsorship from one registrar to another registrar. If the domain name is deleted by the new sponsoring registrar during this period, the registry provides a credit to the registrar for the cost of the transfer.
转让期：此宽限期在域名注册赞助从一个注册商成功转让给另一个注册商后提供。如果域名在此期间被新的发起注册机构删除，注册机构将向注册机构支付转让费用。
redemptionPeriod: This status value is used to describe a domain for which a <delete> command has been received, but the domain has not yet been purged because an opportunity exists to restore the domain and abort the deletion process.
redemptionPeriod：此状态值用于描述已接收到<delete>命令的域，但该域尚未被清除，因为存在还原该域并中止删除过程的机会。
pendingRestore: This status value is used to describe a domain that is in the process of being restored after being in the redemptionPeriod state.
pendingRestore：此状态值用于描述处于redemptionPeriod状态后正在恢复的域。
pendingDelete: This status value is used to describe a domain that has entered the purge processing state after completing the redemptionPeriod state. A domain in this status MUST also be in the pendingDelete status described in the EPP domain mapping [2].
pendingDelete：此状态值用于描述在完成redemptionPeriod状态后已进入清除处理状态的域。处于此状态的域还必须处于EPP域映射[2]中描述的pendingDelete状态。
This extension allows a client to provide copies of registration data (whois [9] data, for example) and supporting information in a restore report as required by the RGP process. No specific format is required by this extension; both free text and XML markup MAY be used.
此扩展允许客户端根据RGP过程的要求在还原报告中提供注册数据（例如whois[9]数据）和支持信息的副本。此扩展不需要特定格式；可以同时使用自由文本和XML标记。
Operators of servers that provide registration data might find it useful to provide grace period status values in their responses to client queries. This information can be useful to people who want to understand the operations that can be performed on a domain name at any give time.
提供注册数据的服务器的操作员可能会发现，在其对客户端查询的响应中提供宽限期状态值很有用。这些信息对于希望了解在任何给定时间可以对域名执行的操作的人都很有用。
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 RFC 3339 [7] 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.
日期和时间属性值必须使用公历以世界协调时间（UTC）表示。使用RFC 3339[7]中定义的大写“T”和“Z”字符的扩展日期时间表单必须用于表示日期时间值，因为XML模式不支持截断日期时间表单或小写“T”和“Z”字符。
The RGP process requires a client to make two statements regarding the data included in a restore report. No specific format is required by this extension; both free text and XML markup MAY be used. English is the default language used within the statements, but other languages MAY be used.
RGP过程要求客户端对还原报告中包含的数据进行两次声明。此扩展不需要特定格式；可以同时使用自由文本和XML标记。英语是语句中使用的默认语言，但也可以使用其他语言。
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [1]. The command mappings described here are specifically for use in implementing redemption grace period processes via EPP.
EPP语法和语义的详细描述可在EPP核心协议规范[1]中找到。这里描述的命令映射专门用于通过EPP实现赎回宽限期过程。
EPP provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information.
EPP提供了三个命令来检索对象信息：<check>来确定服务器是否知道对象，<info>来检索与对象相关的详细信息，<transfer>来检索对象传输状态信息。
This extension does not add any elements to the EPP <check> command or <check> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<check>命令或<check>响应添加任何元素。
This extension does not add any elements to the EPP <info> command described in the EPP domain mapping [2]. Additional elements are defined for the <info> response.
此扩展不向EPP域映射[2]中描述的EPP<info>命令添加任何元素。为<info>响应定义了其他元素。
When an <info> command has been processed successfully, the EPP <resData> element MUST contain child elements as described in [2]. In addition, the EPP <extension> element MUST contain a child <rgp:infData> element that identifies the registry grace period namespace and the location of the registry grace period schema. The <rgp:infData> element contains a single <rgp:rgpStatus> element that contains a single attribute "s" whose value describes the current grace period status of the domain. Possible status values are described in section Section 3.1.
成功处理<info>命令后，EPP<resData>元素必须包含子元素，如[2]所述。此外，EPP<extension>元素必须包含一个子<rgp:infData>元素，该元素标识注册表宽限期命名空间和注册表宽限期架构的位置。<rgp:infData>元素包含单个<rgp:rgpStatus>元素，该元素包含单个属性“s”，其值描述域的当前宽限期状态。第3.1节描述了可能的状态值。
Example <info> response for "addPeriod" status:
“addPeriod”状态的响应示例：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientX</domain:crID>
S: <domain:crDate>2003-11-26T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2005-11-26T22:00:00.0Z</domain:exDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="addPeriod"/>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientX</domain:crID>
S: <domain:crDate>2003-11-26T22:00:00.0Z</domain:crDate>
S: <domain:exDate>2005-11-26T22:00:00.0Z</domain:exDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="addPeriod"/>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: </response>
S:</epp>
Example <info> response for "redemptionPeriod" status:
“赎回期”状态的响应示例：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingDelete"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="redemptionPeriod"/>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingDelete"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="redemptionPeriod"/>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: </rgp:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
Example <info> response extension for "pendingRestore" status (note that only the extension element changes from the first example):
示例<info>针对“pendingRestore”状态的响应扩展（注意，只有扩展元素与第一个示例不同）：
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:infData>
S:</extension>
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:infData>
S:</extension>
Example <info> response extension for "pendingDelete" status (note that only the extension element changes from the first example):
示例<info>针对“pendingDelete”状态的响应扩展（注意，只有扩展元素与第一个示例不同）：
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingDelete"/>
S: </rgp:infData>
S:</extension>
S:<extension>
S: <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingDelete"/>
S: </rgp:infData>
S:</extension>
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<transfer>命令或<transfer>响应添加任何元素。
EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.
EPP提供了五个转换对象的命令：<create>创建对象实例，<delete>删除对象实例，<renew>延长对象有效期，<transfer>管理对象更改，以及<update>更改与对象关联的信息。
This extension does not add any elements to the EPP <create> command or <create> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<create>命令或<create>响应添加任何元素。
This extension does not add any elements to the EPP <delete> command or <delete> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<delete>命令或<delete>响应添加任何元素。
This extension does not add any elements to the EPP <renew> command or <renew> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<renew>命令或<renew>响应添加任何元素。
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [2].
此扩展不向EPP域映射[2]中描述的EPP<transfer>命令或<transfer>响应添加任何元素。
This extension defines additional elements to extend the EPP <update> command and response described in the EPP domain mapping [2] for redemption grace period processing.
此扩展定义了其他元素，以扩展EPP域映射[2]中描述的用于赎回宽限期处理的EPP<update>命令和响应。
The EPP <update> command provides a transform operation that allows a client to change the state of a domain object. The registry grace period extension modifies base update processing to support redemption of domain names for which a <delete> command has been processed, but the name has not yet been purged.
EPP<update>命令提供转换操作，允许客户端更改域对象的状态。注册表宽限期扩展修改基本更新处理，以支持已处理<delete>命令但名称尚未清除的域名的赎回。
Section 3.2.5 of the EPP domain mapping describes the elements that have to be specified within an <update> command. The requirement to provide at least one <domain:add>, <domain:rem>, or <domain:chg> element is updated by this extension such that at least one empty <domain:add>, <domain:rem>, or <domain:chg> element MUST be present if this extension is specified within an <update> command. This requirement is updated to disallow the possibility of modifying a domain object as part of redemption grace period recovery processing.
EPP域映射的第3.2.5节描述了必须在<update>命令中指定的元素。提供至少一个<domain:add>、<domain:rem>或<domain:chg>元素的要求通过此扩展进行更新，如果在<update>命令中指定了此扩展，则必须至少存在一个空的<domain:add>、<domain:rem>或<domain:chg>元素。此要求已更新，不允许在赎回宽限期恢复处理过程中修改域对象。
In addition to the EPP command elements described in the EPP domain
mapping [2], the <update> command MUST contain an <extension>
element. The <extension> element MUST contain a child <rgp:update>
element that identifies the registry grace period namespace and the
location of the registry grace period schema. The <rgp:update>
In addition to the EPP command elements described in the EPP domain
mapping [2], the <update> command MUST contain an <extension>
element. The <extension> element MUST contain a child <rgp:update>
element that identifies the registry grace period namespace and the
location of the registry grace period schema. The <rgp:update>
element contains a single <rgp:restore> element that contains an OPTIONAL <rgp:report> element that MAY be used to deliver a redemption grace period restore report.
元素包含一个<rgp:restore>元素，该元素包含一个可选的<rgp:report>元素，可用于交付赎回宽限期还原报告。
The <rgp:restore> element contains a REQUIRED "op" attribute that describes the redemption grace period operation being requested. Two values are defined: "request" is used to identify a restore request that does not include a restore report, and "report" is used to identify a restore request that contains a restore report. A report MAY be submitted more than once if corrections are required. If the value of the "op" attribute is "request" an <rgp:report> element MUST NOT be present. If the value of the "op" attribute is "report" an <rgp:report> element MUST be present.
<rgp:restore>元素包含一个必需的“op”属性，该属性描述所请求的赎回宽限期操作。定义了两个值：“请求”用于标识不包含还原报告的还原请求，“报告”用于标识包含还原报告的还原请求。如果需要更正，可多次提交报告。如果“op”属性的值为“request”，则<rgp:report>元素不得存在。如果“op”属性的值为“report”，则必须存在<rgp:report>元素。
The <rgp:report> element contains the following child elements:
<rgp:report>元素包含以下子元素：
- An <rgp:preData> element that contains a copy of the registration data that existed for the domain name prior to the domain name being deleted. This element MAY contain both text and XML markup.
- 一个<rgp:preData>元素，其中包含删除域名之前存在的域名注册数据的副本。此元素可能同时包含文本和XML标记。
- An <rgp:postData> element that contains a copy of the registration data that exists for the domain name at the time the restore report is submitted. This element MAY contain both text and XML markup.
- 一个<rgp:postData>元素，包含提交还原报告时存在的域名注册数据的副本。此元素可能同时包含文本和XML标记。
- An <rgp:delTime> element that contains the date and time when the domain name delete request was sent to the server.
- 包含域名删除请求发送到服务器的日期和时间的<rgp:delTime>元素。
- An <rgp:resTime> element that contains the date and time when the original <rgp:restore> command was sent to the server.
- 一个<rgp:resTime>元素，包含原始<rgp:restore>命令发送到服务器的日期和时间。
- An <rgp:resReason> element that contains a brief explanation of the reason for restoring the domain name.
- 一个<rgp:resReason>元素，包含恢复域名原因的简要说明。
- An <rgp:statement> element that contains a text statement that the client has not restored the domain name in order to assume the rights to use or sell the domain name for itself or for any third party. Supporting information related to this statement MAY be supplied in the <rgp:other> element described below. An OPTIONAL "lang" attribute MAY be present to identify the language if English (value "en") is not used to represent the statement.
- 一种<rgp:statement>元素，其中包含一条文本语句，表明客户端没有还原域名，以便为自己或任何第三方使用或出售域名。与本声明相关的支持信息可在下文所述的<rgp:other>元素中提供。如果不使用英语（值“en”）表示语句，则可能会出现可选的“lang”属性来标识语言。
- A second <rgp:statement> element that contains a text statement that the information in the restore report is factual to the best of the client's knowledge. An OPTIONAL "lang" attribute MAY be present to identify the language if English (value "en") is not used to represent the statement.
- 第二个<rgp:statement>元素，其中包含一个文本语句，该语句表示恢复报告中的信息就客户所知是真实的。如果不使用英语（值“en”）表示语句，则可能会出现可选的“lang”属性来标识语言。
- An OPTIONAL <rgp:other> element that contains any information needed to support the statements provided by the client. This element MAY contain both text and XML markup.
- 可选的<rgp:other>元素，包含支持客户端提供的语句所需的任何信息。此元素可能同时包含文本和XML标记。
More detailed information describing the information required to be provided in a restore report is available from ICANN.
ICANN提供了更详细的信息，说明恢复报告中需要提供的信息。
Example <update> command without a restore report:
不带还原报告的<update>命令示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="request"/>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="request"/>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
Example <update> command with a restore report:
带有还原报告的<update>命令示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="report">
C: <rgp:report>
C: <rgp:preData>Pre-delete registration data goes here.
C: Both XML and free text are allowed.</rgp:preData>
C: <rgp:postData>Post-restore registration data goes here.
C: Both XML and free text are allowed.</rgp:postData>
C: <rgp:delTime>2003-07-10T22:00:00.0Z</rgp:delTime>
C: <rgp:resTime>2003-07-20T22:00:00.0Z</rgp:resTime>
C: <rgp:resReason>Registrant error.</rgp:resReason>
C: <rgp:statement>This registrar has not restored the
C: Registered Name in order to assume the rights to use
C: or sell the Registered Name for itself or for any
C: third party.</rgp:statement>
C: <rgp:statement>The information in this report is
C: true to best of this registrar's knowledge, and this
C: registrar acknowledges that intentionally supplying
C: false information in this report shall constitute an
C: incurable material breach of the
C: Registry-Registrar Agreement.</rgp:statement>
C: <rgp:other>Supporting information goes
C: here.</rgp:other>
C: </rgp:report>
C: </rgp:restore>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C: <domain:name>example.com</domain:name>
C: <domain:chg/>
C: </domain:update>
C: </update>
C: <extension>
C: <rgp:update xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
C: rgp-1.0.xsd">
C: <rgp:restore op="report">
C: <rgp:report>
C: <rgp:preData>Pre-delete registration data goes here.
C: Both XML and free text are allowed.</rgp:preData>
C: <rgp:postData>Post-restore registration data goes here.
C: Both XML and free text are allowed.</rgp:postData>
C: <rgp:delTime>2003-07-10T22:00:00.0Z</rgp:delTime>
C: <rgp:resTime>2003-07-20T22:00:00.0Z</rgp:resTime>
C: <rgp:resReason>Registrant error.</rgp:resReason>
C: <rgp:statement>This registrar has not restored the
C: Registered Name in order to assume the rights to use
C: or sell the Registered Name for itself or for any
C: third party.</rgp:statement>
C: <rgp:statement>The information in this report is
C: true to best of this registrar's knowledge, and this
C: registrar acknowledges that intentionally supplying
C: false information in this report shall constitute an
C: incurable material breach of the
C: Registry-Registrar Agreement.</rgp:statement>
C: <rgp:other>Supporting information goes
C: here.</rgp:other>
C: </rgp:report>
C: </rgp:restore>
C: </rgp:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an extended <update> command without a restore report has been processed successfully, the EPP response is as described in the EPP domain mapping [2] except that an extension element is added to describe grace period status as a result of processing the <update> command. The extension element contains a single child element (<upData>) that itself contains a single child element (<rgpStatus>) that contains a single attribute "s" whose value MUST be "pendingRestore" if the <restore> request has been accepted.
成功处理没有还原报告的扩展<update>命令时，EPP响应如EPP域映射[2]中所述，但添加扩展元素以描述处理<update>命令后的宽限期状态。扩展元素包含一个子元素（<updatea>），该子元素本身包含一个子元素（<rgpStatus>），该子元素包含一个属性“s”，如果已接受<restore>请求，则该属性的值必须为“pendingerstore”。
Example "restore request" <update> response:
示例“还原请求”<update>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <extension>
S: <rgp:upData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:upData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <extension>
S: <rgp:upData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:rgp-1.0
S: rgp-1.0.xsd">
S: <rgp:rgpStatus s="pendingRestore"/>
S: </rgp:upData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
When an extended <update> command with a restore report has been processed successfully, the EPP response is as described in the EPP domain mapping [2] with no registry grace period extension. Registry grace period extension is not required because acceptance of the restore report completes redemption grace period processing.
成功处理带有还原报告的扩展<update>命令时，EPP响应如EPP域映射[2]中所述，没有注册表宽限期扩展。不需要注册表宽限期扩展，因为接受还原报告即可完成赎回宽限期处理。
An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.
EPP对象映射是用XML模式表示法指定的。这里给出的形式语法是对象映射的完整模式表示，适合于自动验证EPP XML实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<schema targetNamespace="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for registry grace period
processing.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for registry grace period
processing.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="update" type="rgp:updateType"/>
<!--
Child elements found in EPP commands.
-->
<element name="update" type="rgp:updateType"/>
<!--
Child elements of the <update> command for the
redemption grace period.
-->
<complexType name="updateType">
<sequence>
<element name="restore" type="rgp:restoreType"/>
</sequence>
</complexType>
<!--
Child elements of the <update> command for the
redemption grace period.
-->
<complexType name="updateType">
<sequence>
<element name="restore" type="rgp:restoreType"/>
</sequence>
</complexType>
<complexType name="restoreType">
<sequence>
<element name="report" type="rgp:reportType"
minOccurs="0"/>
</sequence>
<attribute name="op" type="rgp:rgpOpType" use="required"/>
</complexType>
<complexType name="restoreType">
<sequence>
<element name="report" type="rgp:reportType"
minOccurs="0"/>
</sequence>
<attribute name="op" type="rgp:rgpOpType" use="required"/>
</complexType>
<!--
New redemption grace period operations can be defined
by adding to this enumeration.
-->
<simpleType name="rgpOpType">
<restriction base="token">
<enumeration value="request"/>
<enumeration value="report"/>
</restriction>
</simpleType>
<!--
New redemption grace period operations can be defined
by adding to this enumeration.
-->
<simpleType name="rgpOpType">
<restriction base="token">
<enumeration value="request"/>
<enumeration value="report"/>
</restriction>
</simpleType>
<complexType name="reportType">
<sequence>
<element name="preData" type="rgp:mixedType"/>
<element name="postData" type="rgp:mixedType"/>
<element name="delTime" type="dateTime"/>
<element name="resTime" type="dateTime"/>
<complexType name="reportType">
<sequence>
<element name="preData" type="rgp:mixedType"/>
<element name="postData" type="rgp:mixedType"/>
<element name="delTime" type="dateTime"/>
<element name="resTime" type="dateTime"/>
<element name="resReason" type="rgp:reportTextType"/>
<element name="statement" type="rgp:reportTextType"
maxOccurs="2"/>
<element name="other" type="rgp:mixedType"
minOccurs="0"/>
</sequence>
</complexType>
<element name="resReason" type="rgp:reportTextType"/>
<element name="statement" type="rgp:reportTextType"
maxOccurs="2"/>
<element name="other" type="rgp:mixedType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="mixedType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</restriction>
</complexContent>
</complexType>
<complexType name="mixedType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</restriction>
</complexContent>
</complexType>
<complexType name="reportTextType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="lang" type="language" default="en"/>
</restriction>
</complexContent>
</complexType>
<complexType name="reportTextType">
<complexContent mixed="true">
<restriction base="anyType">
<sequence>
<any processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="lang" type="language" default="en"/>
</restriction>
</complexContent>
</complexType>
<!--
Child response elements.
-->
<element name="infData" type="rgp:respDataType"/>
<element name="upData" type="rgp:respDataType"/>
<!--
Child response elements.
-->
<element name="infData" type="rgp:respDataType"/>
<element name="upData" type="rgp:respDataType"/>
<!--
Response elements.
-->
<complexType name="respDataType">
<sequence>
<element name="rgpStatus" type="rgp:statusType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Response elements.
-->
<complexType name="respDataType">
<sequence>
<element name="rgpStatus" type="rgp:statusType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
<!--
Status is a combination of attributes and an optional
human-readable message that may be expressed in languages
other than English.
-->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute name="s" type="rgp:statusValueType"
use="required"/>
<attribute name="lang" type="language" default="en"/>
</extension>
</simpleContent>
</complexType>
Status is a combination of attributes and an optional
human-readable message that may be expressed in languages
other than English.
-->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute name="s" type="rgp:statusValueType"
use="required"/>
<attribute name="lang" type="language" default="en"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="addPeriod"/>
<enumeration value="autoRenewPeriod"/>
<enumeration value="renewPeriod"/>
<enumeration value="transferPeriod"/>
<enumeration value="pendingDelete"/>
<enumeration value="pendingRestore"/>
<enumeration value="redemptionPeriod"/>
</restriction>
</simpleType>
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="addPeriod"/>
<enumeration value="autoRenewPeriod"/>
<enumeration value="renewPeriod"/>
<enumeration value="transferPeriod"/>
<enumeration value="pendingDelete"/>
<enumeration value="pendingRestore"/>
<enumeration value="redemptionPeriod"/>
</restriction>
</simpleType>
<!-- End of schema. --> </schema> END
<!-- 架构结束。--></架构>结束
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 [10]. Conformant XML processors recognize both UTF-8 and UTF-16 [11]. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED in environments where parser encoding support incompatibility exists.
EPP以XML表示，它为使用Unicode字符集及其更紧凑的表示（包括UTF-8）编码信息提供了本机支持[10]。一致性XML处理器同时识别UTF-8和UTF-16[11]。尽管XML包含通过在<？XML？>声明中使用“encoding”属性来识别和使用其他字符编码的规定，但在解析器编码支持不兼容的环境中，建议使用UTF-8。
As an extension of the EPP domain mapping [2], the elements, element content, attributes, and attribute values described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension.
作为EPP域映射[2]的扩展，本文档中描述的元素、元素内容、属性和属性值必须继承用于表示包含此扩展的XML实例中存在的更高层域和核心协议结构的国际化约定。
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in RFC 3688 [8]. Two URI assignments were requested and have been registered by the IANA.
本文档使用URN来描述符合RFC 3688[8]中描述的注册表机制的XML名称空间和XML模式。请求了两个URI分配，并已由IANA注册。
Registration request for the registry grace period namespace:
注册表宽限期命名空间的注册请求：
URI: urn:ietf:params:xml:ns:rgp-1.0
URI: urn:ietf:params:xml:ns:rgp-1.0
Registrant Contact: See the "Author's Address" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
Registration request for the registry grace period XML schema:
注册表宽限期XML架构的注册请求：
URI: urn:ietf:params:xml:schema:rgp-1.0
URI: urn:ietf:params:xml:schema:rgp-1.0
Registrant Contact: See the "Author's Address" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML: See the "Formal Syntax" section of this document.
XML：请参阅本文档的“正式语法”部分。
The mapping extensions described in this document do not provide any security services beyond those described by EPP [1], the EPP domain name mapping [2], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.
本文档中描述的映射扩展不提供EPP[1]、EPP域名映射[2]和EPP使用的协议层之外的任何安全服务。这些其他规范中描述的安全注意事项也适用于本规范。
As with other domain object updates, redemption of a deleted domain object MUST be restricted to the sponsoring client as authenticated using the mechanisms described in sections 2.9.1.1 and 7 of RFC 3730 [1]. Any attempt to recover a deleted domain object by any client other than the sponsoring client MUST be rejected with an appropriate EPP authorization error.
与其他域对象更新一样，已删除域对象的赎回必须限于使用RFC 3730[1]第2.9.1.1和7节所述机制进行身份验证的发起客户端。除发起客户端以外的任何客户端恢复已删除域对象的任何尝试都必须被拒绝，并出现相应的EPP授权错误。
The author would like to thank the following people who have provided significant contributions to the development of this document:
作者要感谢为本文件的编写做出重大贡献的以下人员：
James Gould, Antony Perkov, and Janusz Sienkiewicz.
詹姆斯·古尔德、安东尼·珀科夫和亚努斯·辛凯维奇。
[1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 3730, March 2004.
[1] Hollenbeck，S.，“可扩展资源调配协议（EPP）”，RFC3730，2004年3月。
[2] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", RFC 3731, March 2004.
[2] Hollenbeck，S.，“可扩展供应协议（EPP）域名映射”，RFC 37312004年3月。
[3] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, <http://www.w3.org/TR/REC-xml>.
[3] Bray，T.，Paoli，J.，Sperberg McQueen，C.，和E.Maler，“可扩展标记语言（XML）1.0（第二版）”，W3C REC XML，2000年10月<http://www.w3.org/TR/REC-xml>.
[4] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, <http://www.w3.org/TR/xmlschema-1/>.
[4] Thompson，H.，Beech，D.，Maloney，M.，和N.Mendelsohn，“XML模式第1部分：结构”，W3C REC-xmlschema-12001年5月<http://www.w3.org/TR/xmlschema-1/>.
[5] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes", W3C REC-xmlschema-2, May 2001, <http://www.w3.org/TR/xmlschema-2/>.
[5] Biron，P.和A.Malhotra，“XML模式第2部分：数据类型”，W3C REC-xmlschema-2，2001年5月<http://www.w3.org/TR/xmlschema-2/>.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[6] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[7] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002.
[7] Klyne，G.和C.Newman，“互联网上的日期和时间：时间戳”，RFC 33392002年7月。
[8] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[8] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[9] Harrenstien, K., Stahl, M., and E. Feinler, "NICNAME/WHOIS", RFC 954, October 1985.
[9] K.Harrenstien、M.Stahl和E.Feinler，“NICNAME/WHOIS”，RFC 954，1985年10月。
[10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[10] Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000.
[11] Hoffman，P.和F.Yergeau，“UTF-16，ISO 10646编码”，RFC 2781，2000年2月。
Author's Address
作者地址
Scott Hollenbeck VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166-6503 US
Scott Hollenbeck VeriSign，Inc.美国弗吉尼亚州杜勒斯Ridgetop Circle 21345，邮编20166-6503
EMail: shollenbeck@verisign.com
EMail: shollenbeck@verisign.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、其代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。