Shepherd writeup
draft-ietf-regext-data-escrow-05

Technical Summary

This document describes the Registry Data Escrow Specification
(draft-ietf-regext-data-escrow) that specifies the format and contents
of data escrow deposits primarily for domain name registries.

Working Group Summary

draft-ietf-regext-data-escrow is on standards track.  This document
specifies a format for data escrow deposits independent of the objects
being escrowed.  A specification is required for each type of
registry/set of objects that is expected to be escrowed, such as
draft-ietf-regext-dnrd-objects-mapping for Domain Name Registration
Data (DNRD).

Document Quality

This document has been widely discussed on the ire mailing list,
has been broadly implemented by members
of the domain name industry (registries and data escrow agents), and
has been adopted and discussed in the regext working group.
The author has addressed all comments and many
changes have been incorporated in the document.

The ICANN Base Registry Agreement requires registries, data escrow agents,
and ICANN to implement the document.  ICANN receives daily notifications
from data from data escrow agents confirming that more than 1,200 gTLDs
are sending deposits that comply with this document.  ICANN receives on a
weekly basis per gTLD, from more than 1,200 gTLD registries, a
Bulk Registration Data Access file that also complies with this document.
In addition, ICANN is aware of Registry Service Provider transitions using
data files that conform to this document.


Personnel

Document shepherd is James Gould, jgould@verisign.com
Area Director is Barry Leiba, barryleiba@computer.org

Shepherd Comments

As document shepherd I have verified all of the XML examples against
the XML schema included in this document.  Example
"urn:ietf:params:xml:ns:rdeObj1-1.0" and "urn:ietf:params:xml:ns:rdeObj2-1.0"
XML schemas were created to fully validate the examples using a
validating XML parser.

The author has confirmed following BCP78 and BCP79 in the document header.

No IPR disclosures have been submitted for this document.

The IANA considerations follow the defined format for the submission to the XML
Registry for the XML namespace and XML schema for this document.

All normative and informative references have been verified.

After carefully reviewing the ire, the non-WG Internet Registration Escrow discussion 
list (https://mailarchive.ietf.org/arch/browse/ire), and the regext working group 
mailing lists, I found no objections for this document that were not resolved.
I believe that there is broad consensus for this document.

As document shepherd I believe this document is ready for publication.
Back