RFC3915 日本語訳
3915 Domain Registry Grace Period Mapping for the ExtensibleProvisioning Protocol (EPP). S. Hollenbeck. September 2004. (Format: TXT=45467 bytes) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
英語原文
Network Working Group S. Hollenbeck Request for Comments: 3915 VeriSign, Inc. Category: Standards Track September 2004
Hollenbeckがコメントのために要求するワーキンググループS.をネットワークでつないでください: 3915年のベリサインInc.カテゴリ: 標準化過程2004年9月
Domain Registry Grace Period Mapping for the
Extensible Provisioning Protocol (EPP)
広げることができる食糧を供給するプロトコルのためのドメイン登録据置期間のマッピング(エップ)
Status of this Memo
この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.
このドキュメントは、インターネットコミュニティにインターネット標準化過程プロトコルを指定して、改良のために議論と提案を要求します。 このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」(STD1)の現行版を参照してください。 このメモの分配は無制限です。
Copyright Notice
版権情報
Copyright (C) The Internet Society (2004).
Copyright(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.
このドキュメントはドメインネームシステム(DNS)の管理のためにアイキャン(ICANN)によって定義された「据置期間」方針を条件としてドメイン名を写像するExtensible Provisioningプロトコル(EPP)拡大について説明します。 据置期間の方針は、プロトコル動作が実行された後にプロトコル動作が逆にされるか、または別の方法で短期間の間、取り消されるのを許容するために存在しています。 XMLで指定されていて、このマッピングは、据置期間の処理に必要である付加的な機能を提供するためにEPPドメイン名マッピングを広げています。
Hollenbeck Standards Track [Page 1] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[1ページ]RFC3915EPP据置期間
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. 序論. . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1。 本書では使用されるコンベンション。 . . . . . . . . . . . 4 2. 償却据置期間の州のダイヤグラム. . . . . . . . . . . . 4 3。 物の属性. . . . . . . . . . . . . . . . . . . . . . 6 3.1。 状態値. . . . . . . . . . . . . . . . . . . . . 6 3.2。 登録データと情報. . . . . . 7 3.3を支持すること。 日付と回. . . . . . . . . . . . . . . . . . . . 7 3.4。 クライアント声明. . . . . . . . . . . . . . . . . . . 8 4。 EPPコマンドマッピング. . . . . . . . . . . . . . . . . . . . . 8 4.1EPPは.1にコマンド. . . . . . . . . . . . . . . . . . . 8 4.1について質問します。 EPP<チェック>命令. . . . . . . . . . . . . . 8 4.1.2。 EPP<インフォメーション>コマンド. . . . . . . . . . . . . . . 8 4.1.3。 EPP<転送>命令. . . . . . . . . . . . . 11 4.2。 EPPは.1にコマンド. . . . . . . . . . . . . . . . . 11 4.2を変えます。 EPP<は>コマンド. . . . . . . . . . . . . . 12 4.2.2を作成します。 EPP<は>コマンド. . . . . . . . . . . . . . 12 4.2.3を削除します。 EPP<は>コマンド. . . . . . . . . . . . . . 12 4.2.4を更新します。 EPP<転送>命令. . . . . . . . . . . . . 12 4.2.5。 EPP<アップデート>命令. . . . . . . . . . . . . . 12 5。 正式な構文. . . . . . . . . . . . . . . . . . . . . . . . 16 6。 国際化問題. . . . . . . . . . . . . 19 7。 IANA問題. . . . . . . . . . . . . . . . . . . . . 20 8。 セキュリティ問題. . . . . . . . . . . . . . . . . . . 20 9。 承認. . . . . . . . . . . . . . . . . . . . . . . 20 10。 参照. . . . . . . . . . . . . . . . . . . . . . . . . . 21 10.1。 引用規格. . . . . . . . . . . . . . . . . . 21 10.2。 有益な参照. . . . . . . . . . . . . . . . . 21作者のアドレスの.22の完全な著作権宣言文. . . . . . . . . . . . . . . . . . . . . 23
Hollenbeck Standards Track [Page 2] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[2ページ]RFC3915EPP据置期間
1. Introduction
1. 序論
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]).
このドキュメントはExtensible Provisioningのバージョン1.0のためにRFC3730[1]で説明されたプロトコル(EPP)を写像する拡大について説明します。 このマッピング(RFC3731[2]で説明されたドメイン名マッピングの拡大)は拡張マークアップ言語(XML)1.0[3]とXML Schema記法([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)のための「据置期間」ドメイン名回復を供給するという実現提案(または、償却)を開発しました。 このマッピングはRedemptionグレースPeriod(RGP)に入ったドメイン名のために償却の過程に着手するEPPドメイン<アップデート>命令を広げています、そして、それはICANN方針で定義された様々な据置期間に入ったドメインの状態を特定するためにEPPドメイン<インフォメーション>応答を広げています。
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 ドメイン名登録の期間の後の「据置期間を更新してください」は記録係によって明らかに広げられます(更新されます)。 ドメイン名がこの期間、記録係によって削除されるなら、登録は更新の費用でクレジットを記録係に提供します。
Hollenbeck Standards Track [Page 3] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[3ページ]RFC3915EPP据置期間
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 ドメイン名登録スポンサーシップのうまくいっている1人の記録係から別の記録係までの転送の後の「転送据置期間。」 ドメイン名がこの期間、記録係を後援する新しさによって削除されるなら、登録は転送の費用でクレジットを記録係に提供します。
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.
各据置期間は何日も通常測定される特定の期間の間、存在しています。 それぞれの据置期間の持続時間は本書では記述されない登録運用政策の問題です。
1.1. Conventions Used In This Document
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 BCP 14, RFC 2119 [6].
キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTはBCP14(RFC2119[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:」 線はプロトコルサーバで戻りました。表す、刻み目と白いスペースは、例に提供しますが、要素関係を例証して、この仕様のREQUIREDの特徴ではありません。
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仕様と例を解釈しなければなりません。
2. Redemption Grace Period State Diagram
2. 償却据置期間の州のダイヤグラム
The Redemption Grace Period (RGP) involves several domain state transitions as a domain name moves through the redemption process:
ドメイン名が償却の過程で動くとき、RedemptionグレースPeriod(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<のある他の状態が>コマンドを削除します。
2. A <delete> command is received and processed for the domain name.
2. <は受け取られた>コマンドを削除して、ドメイン名のために処理されました。
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. <がいったん>コマンドを削除すると、RGPは始まります。首尾よく処理されます。 EPP状態は"pendingDelete"に変化します、そして、RGP状態は"redemptionPeriod"に初期化されます。 <が>操作を復元するまで、この状態のドメインの残りが要求されているか、または償却の期間は経過します。
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<アップデート>命令であったかもしれないなら>操作を復元します。 <が受け取られた>要求を復元する前に償却の期間が経過するなら、ステップ8に行ってください。
Hollenbeck Standards Track [Page 4] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[4ページ]RFC3915EPP据置期間
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. <が回復する、>がうまくいっている、aを受けるRegistry待ちはしばらくRegistryによって定義されている記録係からのレポートを復元します。 EPP状態は"pendingRestore"への"pendingDelete"とRGP状態変化のままで残っています。 この拡大がaを渡す方法を定義している間、EPPを通してレポートを復元してください、そして、また、バンドで出ているメカニズム(ウェブサイトなどの)は使用されて、配送するのがレポートを復元するということであるかもしれません。
6. The domain name returns to the redemption period state (state 3)
if a restore report is not received.
6. aがレポートを復元するなら、償却の期間へのリターンが述べるドメイン名(状態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. aが受け取られたレポートを復元するなら、EPP状態は「OK」に戻ります、そして、(何でも<を処理しながらある前なら>コマンドを削除してください)RGP状態は完全に移されます。
8. The redemption period elapses before a <restore> request is
received.
8. <が受け取られた>要求を復元する前に償却の期間は経過します。
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"への"pendingDelete"とRGP状態変化のままで残っています。 しばらくRegistryによって定義されていたままで、ドメイン名はこの州に残っています。
10. The domain name is purged once the pending delete period elapses.
10. ドメイン名は一度掃除されて、未定が期間を削除するということです。経過します。
11. The domain name is available for re-registration.
11. ドメイン名は再登録に利用可能です。
Hollenbeck Standards Track [Page 5] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[5ページ]RFC3915EPP据置期間
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)|
| |
+----------------------+
| +に対して----------------------+ (2) +----------------------+ |エップ: OK(1)| <は>を削除します。|エップ: pendingDelete(3)| |RGP: なし|、-、-、-、-、-、-、-、--、>|RGP: redemptionPeriod| +----------------------+ +----------------------+ ^ (4) | ^ | | <は>を返します。| | (8)がありません。| | +-----------+ | <は>を返します。| | | | | | v| v| +----------------------+ | +----------------------+ | |エップ: pendingDelete(5)| | |エップ: pendingDelete(9)| | |RGP: pendingRestore|---------+ |RGP: pendingDelete| | +----------------------+ レポート+----------------------+ | | (6)でない| | (7) | 容認されたパージ(10)| | レポートは受信されました。| | +--------------------+ +に対して----------------------+ | (11)を掃除します。| | | +----------------------+
3. Object Attributes
3. 物の属性
This extension adds additional elements to the EPP domain name mapping [2]. Only new element descriptions are described here.
この拡大は[2]を写像するEPPドメイン名に追加要素を追加します。 新しい要素記述だけがここで説明されます。
3.1. Status Values
3.1. 状態値
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: この据置期間は、ドメイン名登録の期間が期限が切れた後に提供されて、登録によって自動的に延ばされます(更新されます)。 ドメイン名がこの期間、記録係によって削除されるなら、登録は更新の費用でクレジットを記録係に提供します。
Hollenbeck Standards Track [Page 6] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[6ページ]RFC3915EPP据置期間
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.
renewPeriod: ドメイン名登録の期間が明らかに延ばされた(更新されます)後にこの据置期間は記録係によって提供されます。 ドメイン名がこの期間、記録係によって削除されるなら、登録は更新の費用でクレジットを記録係に提供します。
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.
transferPeriod: ドメイン名登録スポンサーシップのうまくいっている1人の記録係から別の記録係までの転送の後にこの据置期間を提供します。 ドメイン名がこの期間、記録係を後援する新しさによって削除されるなら、登録は転送の費用でクレジットを記録係に提供します。
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: この状態値は使用されて、<が>コマンドを削除するドメインについて説明するのが受け取られていますが、機会がドメインを回復して、削除の過程を中止するために存在しているのでドメインがまだ掃除されていないということです。
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状態を完成した後にパージ処理状態に入ったドメインについて説明するのに使用されます。 また、この状態のドメインが、[2]を写像しながら、EPPドメインで説明されたpendingDelete状態にあるに違いありません。
3.2. Registration Data and Supporting Information
3.2. 登録データと情報を支持すること。
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]データ)とaで情報を支持すると返される登録のコピーにレポートを供給できます。 どんな特定の形式もこの拡大で必要ではありません。 無料のテキストと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.
登録データを提供するサーバのオペレータは、クライアント質問への彼らの応答に据置期間の状態値を提供するのが役に立つのがわかるかもしれません。 だれが、いずれでもドメイン名に実行できる操作が時間を与えるのを理解したがっているかというこの情報は人々の役に立つ場合があります。
3.3. Dates and Times
3.3. 日付と回
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.
グレゴリオ暦を使用して、Universal Coordinated Time(UTC)に日時の属性値を表さなければなりません。 XML図式が端が欠けている日付-時間フォームか小文字「T」と「Z」キャラクタを支持しないとき日付時間的価値を表すのに大文字「T」を使用する拡張日付-時間書式とRFC3339[7]で定義された「Z」キャラクタを使用しなければなりません。
Hollenbeck Standards Track [Page 7] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[7ページ]RFC3915EPP据置期間
3.4. Client Statements
3.4. クライアント声明
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の過程は、クライアントがaにデータを含むことに関する2つの声明にレポートを復元させるのを必要とします。 どんな特定の形式もこの拡大で必要ではありません。 無料のテキストとXMLマーク付けの両方が使用されるかもしれません。 英語は声明の中で使用されたデフォルト言語ですが、他の言語は使用されるかもしれません。
4. EPP Command Mapping
4. EPPコマンドマッピング
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コアプロトコル仕様[1]でEPP構文と意味論の詳述を見つけることができます。 ここで説明されたコマンドマッピングは特にEPPを通して償却据置期間の過程を実行することにおける使用のためのものです。
4.1. EPP Query Commands
4.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は物の情報を検索する3つのコマンドを提供します: 物がサーバに知られているかどうか決定する<チェック>、物に関連している詳細な情報を検索する<インフォメーション>、および<は、物の転送状態情報を検索するために>を移します。
4.1.1. EPP <check> Command
4.1.1. EPP<チェック>命令
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ドメインで説明された>コマンドか<チェック>応答をチェックすると言い足しません。
4.1.2. EPP <info> Command
4.1.2. EPP<インフォメーション>コマンド
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.
この拡大は[2]を写像するEPPドメインで説明されたEPP<インフォメーション>コマンドにどんな要素も追加しません。 追加要素は<インフォメーション>応答のために定義されます。
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.
首尾よく<インフォメーション>コマンドを処理してあるとき、EPP<resData>要素は[2]で説明されるように子供要素を含まなければなりません。 さらに、EPP<拡大>要素は子供<rgpを含まなければなりません: 登録据置期間の名前空間と登録据置期間の図式の位置を特定するinfData>要素。 <rgp: infData>要素は単一の<rgpを含んでいます: 値がドメインの現在の据置期間の状態について説明するただ一つの属性「s」を含むrgpStatus>要素。 可能な状態値はセクションセクション3.1で説明されます。
Hollenbeck Standards Track [Page 8] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[8ページ]RFC3915EPP据置期間
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バージョン=「=「UTF-8インチのスタンドアロン=」ノー、をコード化する1インチ」?>S: <epp xmlnsが等しい、「つぼ:ietf:params:xml:ナノ秒: epp-1インチS:、」 xmlns: xsiは" http://www.w3.org/2001/XMLSchema-instance "Sと等しいです: xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: epp-1.0秒間:、」 epp-1.0.xsd、「>S:」 <応答>S: <結果コードが等しい、「1000、「>S:」 <msg>Commandは首尾よく</msg>Sを完成しました: </結果>S: <resData>S: <ドメイン: infData S: xmlns: ドメイン=、「つぼ:ietf:params:xml:ナノ秒: ドメイン1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: ドメイン1.0秒間:、」 ドメイン-1.0.xsd、「>S:」 <ドメイン: 名前>example.com</ドメイン: >をSと命名してください: <ドメイン: roid>EXAMPLE1-レップ</ドメイン: roid>S: <ドメイン: 状態sは「OK」/>Sと等しいです: <ドメイン: 記入者>jd1234</ドメイン: 記入者>S: <ドメイン: タイプ=に連絡してください、「アドミン、「>sh8013</ドメイン: >Sに連絡してください」 <ドメイン: タイプ=に連絡してください、「科学技術、「>sh8013</ドメイン: >Sに連絡してください」 <ドメイン: ナノ秒>S: <ドメイン: hostObj>ns1.example.com</ドメイン: hostObj>S: <ドメイン: hostObj>ns1.example.net</ドメイン: hostObj>S: </ドメイン: ナノ秒>S: <ドメイン: ホスト>ns1.example.com</ドメイン: >Sを接待してください: <ドメイン: ホスト>ns2.example.com</ドメイン: >Sを接待してください: <ドメイン: clID>ClientX</ドメイン: clID>S: <ドメイン: crID>ClientX</ドメイン: crID>S: <ドメイン: crDate>2003-11-26T22:00:00.0Z</ドメイン: crDate>S: <ドメイン: exDate>2005-11-26T22:00:00.0Z</ドメイン: exDate>S: <ドメイン: authInfo>S: <ドメイン: pw>2fooBAR</ドメイン: pw>S: </ドメイン: authInfo>S: </ドメイン: infData>S: </resData>S: <拡大>S: <rgp:infData xmlns:rgpが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1.0秒間:、」 rgp-1.0.xsd、「>S:」 <rgp: rgpStatus sは"addPeriod"/>Sと等しいです: </rgp: infData>S: </拡大>S: <trID>S: <clTRID>ABC-12345</clTRID>S: <svTRID>54322-XYZ</svTRID>S: </trID>。
Hollenbeck Standards Track [Page 9] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[9ページ]RFC3915EPP据置期間
S: </response> S:</epp>
S: </応答>S: </epp>。
Example <info> response for "redemptionPeriod" status:
"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: <?xmlバージョン=「=「UTF-8インチのスタンドアロン=」ノー、をコード化する1インチ」?>S: <epp xmlnsが等しい、「つぼ:ietf:params:xml:ナノ秒: epp-1インチS:、」 xmlns: xsiは" http://www.w3.org/2001/XMLSchema-instance "Sと等しいです: xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: epp-1.0秒間:、」 epp-1.0.xsd、「>S:」 <応答>S: <結果コードが等しい、「1000、「>S:」 <msg>Commandは首尾よく</msg>Sを完成しました: </結果>S: <resData>S: <ドメイン: infData S: xmlns: ドメイン=、「つぼ:ietf:params:xml:ナノ秒: ドメイン1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: ドメイン1.0秒間:、」 ドメイン-1.0.xsd、「>S:」 <ドメイン: 名前>example.com</ドメイン: >をSと命名してください: <ドメイン: roid>EXAMPLE1-レップ</ドメイン: roid>S: <ドメイン: 状態sは"pendingDelete"/>Sと等しいです: <ドメイン: 記入者>jd1234</ドメイン: 記入者>S: <ドメイン: タイプ=に連絡してください、「アドミン、「>sh8013</ドメイン: >Sに連絡してください」 <ドメイン: タイプ=に連絡してください、「科学技術、「>sh8013</ドメイン: >Sに連絡してください」 <ドメイン: ナノ秒>S: <ドメイン: hostObj>ns1.example.com</ドメイン: hostObj>S: <ドメイン: hostObj>ns1.example.net</ドメイン: hostObj>S: </ドメイン: ナノ秒>S: <ドメイン: ホスト>ns1.example.com</ドメイン: >Sを接待してください: <ドメイン: ホスト>ns2.example.com</ドメイン: >Sを接待してください: <ドメイン: clID>ClientX</ドメイン: clID>S: <ドメイン: crID>ClientY</ドメイン: crID>S: <ドメイン: crDate>1999-04-03T22:00:00.0Z</ドメイン: crDate>S: <ドメイン: upID>ClientX</ドメイン: upID>S: <ドメイン: >1999-12-03T09:00:00.0Z</ドメインをアップデートしてください: >Sをアップデートしてください: <ドメイン: exDate>2005-04-03T22:00:00.0Z</ドメイン: exDate>S: <ドメイン: trDate>2000-04-08T09:00:00.0Z</ドメイン: trDate>S: <ドメイン: authInfo>S: <ドメイン: pw>2fooBAR</ドメイン: pw>S: </ドメイン: authInfo>S: </ドメイン: infData>S: </resData>S: <拡大>S: <rgp:infData xmlns:rgpが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1.0秒間:、」 rgp-1.0.xsd、「>S:」 <rgp: rgpStatus sは"redemptionPeriod"/>と等しいです。
Hollenbeck Standards Track [Page 10] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[10ページ]RFC3915EPP据置期間
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: </拡大>S: <trID>S: <clTRID>ABC-12345</clTRID>S: <svTRID>54322-XYZ</svTRID>S: </trID>S: </応答>S: </epp>。
Example <info> response extension for "pendingRestore" status (note that only the extension element changes from the first example):
"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: <拡大>S: <rgp:infData xmlns:rgpが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1.0秒間:、」 rgp-1.0.xsd、「>S:」 <rgp: rgpStatus sは"pendingRestore"/>Sと等しいです: </rgp: infData>S: </拡大>。
Example <info> response extension for "pendingDelete" status (note that only the extension element changes from the first example):
"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: <拡大>S: <rgp:infData xmlns:rgpが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1インチS:、」 xsi: schemaLocationが等しい、「つぼ:ietf:params:xml:ナノ秒: rgp-1.0秒間:、」 rgp-1.0.xsd、「>S:」 <rgp: rgpStatus sは"pendingDelete"/>Sと等しいです: </rgp: infData>S: </拡大>。
4.1.3. EPP <transfer> Command
4.1.3. EPP<転送>命令
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [2].
この拡大は[2]を写像するEPPドメインで説明されたEPP<転送>命令か<転送>応答にどんな要素も追加しません。
4.2. EPP Transform Commands
4.2. EPP変形コマンド
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は物を変える5つのコマンドを提供します: <は物の例を作成するために>を作成して、<は物の例を削除するために>を削除して、<は、<転送の物、物のスポンサーシップ変化を管理する>、および<アップデート>の有効期間を物に関連している変化情報に延ばすために>を取り替えます。
Hollenbeck Standards Track [Page 11] RFC 3915 EPP Grace Period Mapping September 2004
2004年9月を写像するHollenbeck標準化過程[11ページ]RFC3915EPP据置期間
4.2.1. EPP <create> Command
4.2.1. EPP<は>コマンドを作成します。
This extension does not add any elements to the EPP <create> command or <create> response described in the EPP domain mapping [2].
This extension does not add any elements to the EPP <create> command or <create> response described in the EPP domain mapping [2].
4.2.2. EPP <delete> Command
4.2.2. EPP <delete> Command
This extension does not add any elements to the EPP <delete> command or <delete> response described in the EPP domain mapping [2].
This extension does not add any elements to the EPP <delete> command or <delete> response described in the EPP domain mapping [2].
4.2.3. EPP <renew> Command
4.2.3. EPP <renew> Command
This extension does not add any elements to the EPP <renew> command or <renew> response described in the EPP domain mapping [2].
This extension does not add any elements to the EPP <renew> command or <renew> response described in the EPP domain mapping [2].
4.2.4. EPP <transfer> Command
4.2.4. EPP <transfer> Command
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [2].
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [2].
4.2.5. EPP <update> Command
4.2.5. EPP <update> Command
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.
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.
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.
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.
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.
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.
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>
Hollenbeck Standards Track [Page 12] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 12] RFC 3915 EPP Grace Period Mapping September 2004
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.
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.
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.
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.
The <rgp:report> element contains the following child elements:
The <rgp:report> element contains the following child elements:
- 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.
- 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.
- 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.
- 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.
- An <rgp:delTime> element that contains the date and time when the
domain name delete request was sent to the server.
- An <rgp:delTime> element that contains the date and time when the domain name delete request was sent to the server.
- An <rgp:resTime> element that contains the date and time when the
original <rgp:restore> command was sent to the server.
- An <rgp:resTime> element that contains the date and time when the original <rgp:restore> command was sent to the server.
- An <rgp:resReason> element that contains a brief explanation of
the reason for restoring the domain name.
- An <rgp:resReason> element that contains a brief explanation of the reason for restoring the domain name.
- 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.
- 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.
- 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.
- 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.
Hollenbeck Standards Track [Page 13] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 13] RFC 3915 EPP Grace Period Mapping September 2004
- 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.
- 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.
More detailed information describing the information required to be provided in a restore report is available from ICANN.
More detailed information describing the information required to be provided in a restore report is available from ICANN.
Example <update> command without a restore report:
Example <update> command without a restore report:
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:
Example <update> command with a restore report:
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">
Hollenbeck Standards Track [Page 14] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 14] RFC 3915 EPP Grace Period Mapping September 2004
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.
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.
Hollenbeck Standards Track [Page 15] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 15] RFC 3915 EPP Grace Period Mapping September 2004
Example "restore request" <update> response:
Example "restore request" <update> response:
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.
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.
5. Formal Syntax
5. Formal Syntax
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.
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.
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">
Hollenbeck Standards Track [Page 16] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 16] RFC 3915 EPP Grace Period Mapping September 2004
<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"/>
Hollenbeck Standards Track [Page 17] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 17] RFC 3915 EPP Grace Period Mapping September 2004
<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>
<!--
<!--
Hollenbeck Standards Track [Page 18] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 18] RFC 3915 EPP Grace Period Mapping September 2004
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
<!-- End of schema. --> </schema> END
6. Internationalization Considerations
6. Internationalization Considerations
EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8 [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 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.
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.
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.
Hollenbeck Standards Track [Page 19] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 19] RFC 3915 EPP Grace Period Mapping September 2004
7. IANA Considerations
7. IANA Considerations
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.
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.
Registration request for the registry grace period namespace:
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.
Registrant Contact: See the "Author's Address" section of this document.
XML: None. Namespace URIs do not represent an XML specification.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the registry grace period XML schema:
Registration request for the registry grace period XML schema:
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.
Registrant Contact: See the "Author's Address" section of this document.
XML: See the "Formal Syntax" section of this document.
XML: See the "Formal Syntax" section of this document.
8. Security Considerations
8. Security Considerations
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.
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.
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.
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.
9. Acknowledgements
9. Acknowledgements
The author would like to thank the following people who have provided significant contributions to the development of this document:
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.
James Gould, Antony Perkov, and Janusz Sienkiewicz.
Hollenbeck Standards Track [Page 20] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 20] RFC 3915 EPP Grace Period Mapping September 2004
10. References
10. References
10.1. Normative References
10.1. Normative References
[1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC
3730, March 2004.
[1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 3730, March 2004.
[2] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain
Name Mapping", RFC 3731, March 2004.
[2] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", RFC 3731, March 2004.
[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., and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, <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., and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, <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. and A. Malhotra, "XML Schema Part 2: Datatypes", W3C REC-xmlschema-2, May 2001, <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., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[7] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, July 2002.
[7] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002.
[8] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January
2004.
[8] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
10.2. Informative References
10.2. Informative References
[9] Harrenstien, K., Stahl, M., and E. Feinler, "NICNAME/WHOIS", RFC
954, October 1985.
[9] Harrenstien, K., Stahl, M., and E. Feinler, "NICNAME/WHOIS", RFC 954, October 1985.
[10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD
63, RFC 3629, November 2003.
[10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646",
RFC 2781, February 2000.
[11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000.
Hollenbeck Standards Track [Page 21] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 21] RFC 3915 EPP Grace Period Mapping September 2004
Author's Address
Author's Address
Scott Hollenbeck VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166-6503 US
Scott Hollenbeck VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166-6503 US
EMail: shollenbeck@verisign.com
EMail: shollenbeck@verisign.com
Hollenbeck Standards Track [Page 22] RFC 3915 EPP Grace Period Mapping September 2004
Hollenbeck Standards Track [Page 22] RFC 3915 EPP Grace Period Mapping September 2004
Full Copyright Statement
Full Copyright Statement
Copyright (C) The Internet Society (2004).
Copyright (C) The Internet Society (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.
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.
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.
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
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.
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.
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.
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.
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.
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.
Acknowledgement
Acknowledgement
Funding for the RFC Editor function is currently provided by the Internet Society.
Funding for the RFC Editor function is currently provided by the Internet Society.
Hollenbeck Standards Track [Page 23]
Hollenbeck標準化過程[23ページ]
一覧
スポンサーリンク
