Registry Data Escrow Specification
draft-arias-noguchi-registry-data-escrow-08
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-06-09
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group G. Lozano
Internet-Draft ICANN
Intended status: Standards Track June 09, 2017
Expires: December 11, 2017
Registry Data Escrow Specification
draft-arias-noguchi-registry-data-escrow-08
Abstract
This document specifies the format and contents of data escrow
deposits targeted primarily for domain name registries. However, the
specification was designed to be independent of the underlying
objects that are being escrowed, therefore it could be used for
purposes other than domain name registries.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 11, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Lozano Expires December 11, 2017 [Page 1]
Internet-Draft Registry Data Escrow June 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 4
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5
5. Protocol Description . . . . . . . . . . . . . . . . . . . . 5
5.1. Root element <deposit> . . . . . . . . . . . . . . . . . 5
5.2. Child <watermark> element . . . . . . . . . . . . . . . . 6
5.3. Child <rdeMenu> element . . . . . . . . . . . . . . . . . 7
5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 7
5.5. Child <contents> element . . . . . . . . . . . . . . . . 8
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 9
7. Internationalization Considerations . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
11. Change History . . . . . . . . . . . . . . . . . . . . . . . 14
11.1. Changes from version 00 to 01 . . . . . . . . . . . . . 14
11.2. Changes from version 01 to 02 . . . . . . . . . . . . . 15
11.3. Changes from version 02 to 03 . . . . . . . . . . . . . 15
11.4. Changes from version 03 to 04 . . . . . . . . . . . . . 15
11.5. Changes from version 04 to 05 . . . . . . . . . . . . . 16
11.6. Changes from version 05 to 06 . . . . . . . . . . . . . 16
11.7. Changes from version 06 to 07 . . . . . . . . . . . . . 16
11.8. Changes from version 07 to 08 . . . . . . . . . . . . . 16
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
12.1. Normative References . . . . . . . . . . . . . . . . . . 16
12.2. Informative References . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
Registry Data Escrow is the process by which an Registry periodically
submits data deposits to a third party called an Escrow Agent. These
deposits comprise the minimum data needed by a third party to resume
operations if the registry can not function and is unable or
unwilling to facilitate an orderly transfer of service. For example,
Show full document text