<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Greg,</p>
<p>in the industry, the life cycle of a domain refers to the stages
a domain goes through from birth to death, err, from registration
to deletion. See also:</p>
<p><a class="moz-txt-link-freetext" href="https://www.icann.org/resources/pages/gtld-lifecycle-2012-02-25-en">https://www.icann.org/resources/pages/gtld-lifecycle-2012-02-25-en</a></p>
<p>This may vary from TLD to TLD and on the terms of your registrar.
<br>
</p>
<p>The minimum standard would in this context be a display of the
current status of the domain in its life cycle, for example:
pending delete for a domain about to die, err, deleted. As a
primary purpose, the domain registration data minimum should
include everything necessary to the management of the domain
lifecycle.</p>
<p>Best,</p>
<p>Volker<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 08.09.2016 um 21:21 schrieb Greg
Shatan:<br>
</div>
<blockquote
cite="mid:CA+aOHURdxbtbGHxxXLpTJseLFY543tTsHH96BbT3iQxr+hJAXQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">I expressed a concern
about this on the call (it may have been in the chat), along
the following lines: What exactly is meant by "the life-cycle
of a domain name"?</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Also, is this meant to
be a minimum standard (i.e., RDS must, at a minimum, support
the life-cycle of a domain name), to which other elements can
be added?</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Or is this meant to be
a limiting standard (i.e., RDS must not do more than support
the life-cycle of a domain name), to which other elements can
be added only if they fit within the "life-cycle of a domain
name"?</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Or is this meant to be
a "primary purpose" standard, where other elements can be
added, but they would not be considered a "primary purpose"
(which has a significant downstream effect, e.g., in certain
privacy legislation)?</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Finally, I would ask
which of the use cases that we have on our list fall within
"the life-cycle of a domain name" and which do not? (I
suppose this last question is intertwined with my first
question above.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Depending on what other
participants believe the answers to these questions should be,
and what their effect may be, I may have significant concerns
about this statement. </div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Greg</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Sep 8, 2016 at 2:52 PM, Gomes,
Chuck <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal">In our call earlier this week there
seemed to be support for one element of a RDS
Statement of Purpose as suggested by Jim Galvin: “The
RDS should support the life cycle of a domain name.”
No one on the call disagreed with this; if anyone not
on the call has comments on this please communicate so
on this list prior to our call next week. Also, if any
one who was on the call has comments that you did not
share, please do so before next week’s meeting.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Also, it would be helpful if
everyone could be thinking about answers to the
following questions:</p>
<p class="MsoNormal"
style="margin-left:.5in;text-autospace:none">
<span style="font-family:Symbol">·</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span>What are the criteria for a statement of
purpose?</p>
<p class="MsoNormal"
style="margin-left:.5in;text-autospace:none">
<span style="font-family:Symbol">·</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span>What elements, if any, from the EWG statement
of purpose should be reflected in the statement of
purpose?</p>
<p class="MsoNormal" style="margin-left:.25in"><span
style="font-family:Symbol">·</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span>What other elements need to be reflected in the
statement of purpose?</p>
<p class="MsoNormal">We plan to discuss these questions
in next week’s meeting but comments would be
appreciated on the list before then.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Chuck</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Here’s the EWG statement of purpose
that we discussed in our meeting earlier this week:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:10.0pt">To
help guide the EWG in its deliberations, the group
developed a high-level statement of purpose from which
to test its conclusions and recommendations, as
follows:
</p>
<table style="border:outset 3.0pt" border="1"
cellpadding="0" cellspacing="3">
<tbody>
<tr>
<td style="width:6.15in;padding:0in 5.4pt 0in
5.4pt" valign="top" width="590">
<p class="MsoNormal" style="margin-top:12.0pt"><span
style="color:#7f7f7f">In support of ICANN’s
mission to coordinate the global Internet’s
system of unique identifiers, and to ensure
the stable and secure operation of the
Internet’s unique identifier system,
information about gTLD domain names is
necessary to promote trust and confidence in
the Internet for all stakeholders.</span><span
style="font-size:12.0pt;color:#7f7f7f"></span></p>
<p class="MsoNormal"><span style="color:#7f7f7f">Accordingly,
it is desirable to design a system to
support domain name registration and
maintenance which:</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:6.0pt;margin-left:.25in;line-height:115%"><span
style="line-height:115%;font-family:Symbol;color:#7f7f7f"><span>·<span
style="font:7.0pt "Times New
Roman"">
</span></span></span><span
style="line-height:115%;color:#7f7f7f">Provides
appropriate access to accurate, reliable,
and uniform registration data</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:6.0pt;margin-left:.25in;line-height:115%"><span
style="line-height:115%;font-family:Symbol;color:#7f7f7f"><span>·<span
style="font:7.0pt "Times New
Roman"">
</span></span></span><span
style="line-height:115%;color:#7f7f7f">Protects
the privacy of personal information
</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:6.0pt;margin-left:.25in;line-height:115%"><span
style="line-height:115%;font-family:Symbol;color:#7f7f7f"><span>·<span
style="font:7.0pt "Times New
Roman"">
</span></span></span><span
style="line-height:115%;color:#7f7f7f">Enables
a reliable mechanism for identifying,
establishing and maintaining the ability to
contact Registrants</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:6.0pt;margin-left:.25in;line-height:115%"><span
style="line-height:115%;font-family:Symbol;color:#7f7f7f"><span>·<span
style="font:7.0pt "Times New
Roman"">
</span></span></span><span
style="line-height:115%;color:#7f7f7f">Supports
a framework to address issues involving
Registrants, including but not limited to:
consumer protection, investigation of
cybercrime, and intellectual property
protection</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:6.0pt;margin-left:.25in;line-height:115%"><span
style="font-size:12.0pt;line-height:115%;font-family:Symbol;color:#7f7f7f"><span>·<span
style="font:7.0pt "Times New
Roman"">
</span></span></span><span
style="line-height:115%;color:#7f7f7f">Provides
an infrastructure to address appropriate law
enforcement needs</span><span
style="line-height:115%;font-family:"Arial
Rounded MT
Bold","sans-serif";color:#7f7f7f">
</span><span
style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif";color:#7f7f7f"></span></p>
</td>
</tr>
</tbody>
</table>
<h2 style="text-indent:0in"><span lang="EN-GB"> </span></h2>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>