Shepherd writeup

Technical Summary

This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the provisioning and management of domain name
registrations and applications during the launch of a domain name

Working Group Summary

draft-ietf-regext-launchphase is on standards track.  This extension adds 
additional elements to the EPP domain name mapping  defined in RFC 5731, 
which is an internet standard.

Document Quality

This document has been widely discussed on the mailing lists of the regext, eppext 
and provreg. working groups. The authors have addressed all comments and many
changes have been incorporated in the document. 

At IETF 97 the working group came up with a solution to remove the dependency on 
a normative reference to a draft document. 

ICANN has required of all participants in the newGTLD program to implement some 
version of this document. 

Verisign, Neustar, CentralNIC and others have working implementations of
this specification. 


Document shepherd  is Ulrich Wisser,
Area Director is Adam Roach,

Shepherd Comments

As document shepherd I have verified that all XML examples against the provided  
schema and EPP schemas from RFC 5730 and RFC 5371. Some examples have left 
out part of the XML to be more concise and better show the point of the introduced 
changes. These examples have been verified by the document shepherd with added 
XML data.

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 and 
EPP registries.

All normative and informative references have been verified.

After carefully reviewing the mailings lists of the regext, eppext and provreg working 
groups I have found no objections to this document. From IETF meetings I recall 
broad consensus that this document is ready for publication.

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