<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:11297493;
mso-list-type:hybrid;
mso-list-template-ids:-1649796688 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1768574561;
mso-list-template-ids:1689041440;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt">My comments:<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt"><o:p> </o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">Is it worth including Original Registration Date in the RDS and its output? Is it an acceptably high priority?<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">No. There are many, many things that an RDS system can conceivably do, but not all are worth doing. The argument for inclusion is “it might be useful to a limited
number of specialty users,” which is not compelling. It is a “nice-to-have”, a bell-and-whistle that overloads RDS output. If we are to publish the Original Create Date, why not also publish all the string’s Create Dates between original and now, and all
of the domain’s previous Registrants? Those things would also be useful to certain users, but IMHO they are not worth doing.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt"><o:p> </o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">Is Original Registration Date potentially confusing?
<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">Yes. Can we expect that users (such as registrants) will know the difference between the
<i>Original Registration Date </i>and the <i> Create Date</i>?<i> </i> It is better to show one Create date rather than two. In this case we should choose simplicity over complexity.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt"><o:p> </o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">Is Original Registration Date practical to implement? It is even possible?<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">No, there are several practical problems.
<o:p></o:p></span></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">This data must come from the domain registry. And a domain registry not the same as a data warehouse. A domain
registry’s database usually does not contain a record of every Create transaction ever made in the registry.
</span></i></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"> This is vital for the WG members to understand.<i><o:p></o:p></i></span></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">Instead, a domain registry tends to contain records for the currently registered domains (only). Deleted records
(such as expired and then purged domains) are often not stored in the active registry database, for performance reasons. Instead, these historical records might be in a data warehouse or on a backup disk somewhere. That is, if they are kept somewhere at all.
Registries are not required to save those old records in perpetuity.<o:p></o:p></span></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">So Original Create Date may not even be available for most of the domains currently in the gTLD registries. This
reduces the value of the <i>Original Registration Date</i> idea considerably.<o:p></o:p></span></span></li><li class="MsoNormal" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">Original Create Date</span></i></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">
may be incompatible with the SLA requirements in the registry contracts. When a domain is created in a registry, the registry operator will have to then retrieve the Original Create date and put that into the active RDS record. But again, that’s data’s probably
stored somewhere other than the registry, and the retrieval process may be slow, if it is even possible. And creating domains is required to be a high-speed, high-availability operation. The entire registry-registrar paradigm is predicated on that, based
on business needs and designed into the technology. Doing a historical hunt for and population of this data sounds like a nightmare for registry operators to perform.
<o:p></o:p></span></span></li></ol>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-size:11.0pt">Can users get along without Original Registration Date? Can these users get what they need elsewhere?<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">Users have gotten along without Original Registration Date in WHOIS for the last twenty years. That is an argument against future inclusion.<i>
</i></span></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">There are services that provide domain histories for the purposes (domain name purchase or sale, etc.). <i><o:p></o:p></i></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">One of the justifications in the draft was “domain name control”. That is irrelevant.
<i>Original Registration Date </i>provides no data about the current iteration/lifetime of the domain. And one can’t control a version of a domain that no longer exists.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">Ideas like
<i>Original Registration Date</i> start to turn registries into things they were not designed to be. Domain registries have certain well-designed goals and functions. Being historical data warehouses is not one of them.</span></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">All best,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt">--Greg<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:10.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Amr Elsadr<br>
<b>Sent:</b> Wednesday, September 20, 2017 4:07 PM<br>
<b>To:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [gnso-rds-pdp-wg] Proposed Agreement for Original Registration Date<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Working Group Members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In follow-up to an action item from the 29 August WG call in which the
<a href="https://community.icann.org/display/gTLDRDS/2017-08-29+Next+Gen+RDS+PDP+Working+Group?preview=/66086750/69279984/SummaryResults-Poll-from-22AugustCall.pdf">
22 August poll results</a> were discussed, a drafting team was formed to assist with proposing an alternative WG agreement regarding
<b>“Original Registration Date”</b> to help the WG discuss and reach rough consensus with respect to this data element.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On today’s WG call, a proposed agreement on the data element regarding Original Registration Date was presented by one of the members (Andrew Sullivan) of the drafting team that had been deliberating on it. In follow-up to the action item
from today’s call: <i>“Staff to distribute drafting team output on Original Registration Date to WG mailing list; all WG members invited to review and comment”</i>,
<b>all WG members are now invited to review and comment on the drafting team’s proposal</b>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The proposal, as well as the recording of today’s call, were posted on today’s meeting wiki page here:
<a href="https://community.icann.org/x/ZGfwAw">https://community.icann.org/x/ZGfwAw</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Direct links to the proposal in <a href="https://community.icann.org/display/gTLDRDS/2017-09-20+Next+Gen+RDS+PDP+Working+Group?preview=/66086756/69284003/Volunteer%20Team%20on%20Action%20Item%20regarding%20Original%20Registration%20Date%20-%2018%20Sep%20Update.docx">
MS Word</a> and <a href="https://community.icann.org/display/gTLDRDS/2017-09-20+Next+Gen+RDS+PDP+Working+Group?preview=/66086756/69284004/Volunteer%20Team%20on%20Action%20Item%20regarding%20Original%20Registration%20Date%20-%2018%20Sep%20Update.pdf">
pdf</a> formats are also available.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Amr<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>