<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>+1 to Stephanie. Leaving it as "to provide access" may create an
expectation that cannot (or should not) be met.<br>
</p>
<br>
<div class="moz-cite-prefix">Am 04.10.2016 um 15:53 schrieb
Stephanie Perrin:<br>
</div>
<blockquote
cite="mid:2d32bce5-515b-ffa2-fac8-6d562109ff62@mail.utoronto.ca"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p><font size="+1"><font face="Lucida Grande">I would suggest that
if you boil it down to this, you need to say "</font></font>
<font size="+2"><font size="+1">The Purpose of RDS is to <b><i>manage</i></b>
access to information about Domain Names, Name Servers and
Registrars in a TLD. (I would also be tempted to add "in
accordance with policy and relevant law" but I realize we
need to limit the hobby horses we let into this corral)</font></font></p>
<p><font size="+2"><font size="+1">I appreciate this effort to
condense the thing.</font></font></p>
<p><font size="+2"><font size="+1">Stephanie</font><br>
</font></p>
<br>
<div class="moz-cite-prefix">On 2016-10-04 09:40, Gomes, Chuck
wrote:<br>
</div>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E4B04FC78@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 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:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{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:595.0pt 842.0pt;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1082987889;
mso-list-type:hybrid;
mso-list-template-ids:2101913428 67698713 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
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;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Marc,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">In your
last suggestion, are you suggesting that all four purpose
statements (1, 2, 3a and 3b) could be replaced with your
suggested statement?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span style="font-size:11.0pt"><o:p> </o:p></span></a></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"> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Anderson, Marc<br>
<b>Sent:</b> Thursday, September 29, 2016 12:38 PM<br>
<b>To:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] For your review
- updated RDS Statement of Purpose<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I appreciate the concerns Chuck and
others have raised that we are spending too much time on the
RDS statement of purpose. I know many of us (myself
included) are anxious to get to get to the requirements
deliberation phase. That said it’s important that we do a
proper job drafting the RDS statement of purpose. As a PDP
we’ll be judged on the quality of our work and the statement
of purpose will be a very visible output. Rushing through
this will not serve us well in the long run<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With a goal of wrapping this up quickly
and efficiently in mind, I’ll skip the intro and goals
section and get right to the purpose section.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Purpose 1: A
purpose of gTLD registration data is to provide information
about the lifecycle of a domain name (as specified by
ICANN’s Diagram of gTLD Lifecycle) to enable management of a
domain name registration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree that the first part of that
statement “…provide information about the lifecycle of a
domain name (as specified by ICANN’s Diagram of gTLD
Lifecycle)” is a purpose of RDS. The second part however
“to enable management of a domain name registration” does
not belong in a purpose statement. This deals with a
potential use case which I’m sure we’ll discuss in the
requirements deliberation phase. I would suggest an updated
purpose 1 read: “A purpose of gTLD registration data is to
provide information about the lifecycle of a domain name (as
specified by ICANN’s Diagram of gTLD Lifecycle).”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Purpose 2: A
purpose of a system to collect, maintain, and provide access
to gTLD registration data (hereafter referred to as “the
RDS”) is to provide information that is needed by authorized
parties to operate a gTLD generic top-level domain name in
the DNS.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have concerns with this second purpose
statement. Purpose 2 provides a definition of RDS and one
that I don’t feel is accurate. RDS does not collect or
maintain gTLD registration data. It does provide access to
that data, but as I said on the call the Registration system
itself that registries make accessible to registrars via EPP
is the system that collects and maintains gTLD registrations
data. For purpose 2 how about: “A purpose of RDS is to
provide information that is needed by authorized parities to
operate a generic top-level domain name in the DNS”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Purpose 3:
Further specific purposes of the RDS include:<o:p></o:p></p>
<p class="MsoListParagraphCxSpFirst"
style="margin-left:1.0in;mso-add-space:auto;text-indent:-.25in;mso-list:l0
level1 lfo2">
<!--[if !supportLists]--><span style="mso-list:Ignore">a.<span
style="font:7.0pt "Times New Roman""> </span></span><!--[endif]-->To
enable contact with registrants, registrars, (registries?),
and proxy/privacy service providers associated with gTLD
domain names, for specific policy-defined purposes.<o:p></o:p></p>
<p class="MsoListParagraphCxSpLast"
style="margin-left:1.0in;mso-add-space:auto;text-indent:-.25in;mso-list:l0
level1 lfo2">
<!--[if !supportLists]--><span style="mso-list:Ignore">b.<span
style="font:7.0pt "Times New Roman""> </span></span><!--[endif]-->To
enable release of accurate gTLD registration data that may
not otherwise be publicly available, under specific and
explicit policy-defined conditions<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m not sure why this is broken into a 3a
and 3b. They don’t appear related and should be purpose 3
and 4 respectively. RDS doesn’t include registry data, so
only registrants, registrars and proxy/privacy providers
apply. The “for specific policy-defined purposes” doesn’t
belong in a RDS purpose statement, it’s more appropriate to
the requirements deliberation phase. An updated Purpose 3
would read: “A purpose of RDS is to facilitate contact with
registrants, registrars and proxy/privacy service providers
associated with generic top-level domain names.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For 3b I don’t necessarily agreed with
“accurate” in the purpose statement. Having accurate data
may be a goal, but the purpose is to display the data of
record. In fact a potential use case is to facilitate the
correction of inaccurate data. The “under specific and
explicit policy-defined conditions” again refers to a
potential requirement of RDS but not a purpose. A new
purpose 4 would read: “A purpose of RDS is to enable the
release of gTLD registration data that may not otherwise be
publicly available.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Looking at these 4 purposes I think there
is a theme. You could say that they could all be rolled up
in the statement “The purpose of RDS is to provide access to
information about domain names in a TLD.” As Whois today
also provides information about Registrars and Name Servers,
perhaps a more fulsome consolidated RDS purpose statement
could be:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">The Purpose of
RDS is to provide access to information about Domain Names,
Name Servers and Registrars in a TLD.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Marc Anderson<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> <a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Wednesday, September 28, 2016 1:12 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [gnso-rds-pdp-wg] For your review -
updated RDS Statement of Purpose<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Please
find attached for your review the updated statement of
purpose which aims to reflect the changes discussed during
yesterday’s meeting. You are all encouraged to review this
version, especially the section ‘<span style="color:black">Specific
Purposes for Registration Data and Registration
Directory Services’, and share your input with the
mailing list prior to next week’s meeting. Also note
that a couple of WG members (Marc & Fabrizio)
volunteered to provide updated language for two specific
parts of the document which have been flagged
accordingly, so please hold your comments on those parts
until the proposed language has been circulated. <o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:black">Marika</span><span
style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span
style="font-size:10.0pt">Marika Konings</span></b><span
style="font-size:10.0pt;font-family:"Cambria",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt">Senior Policy Director & Team
Leader for the GNSO, Internet Corporation for Assigned
Names and Numbers (ICANN) </span><span
style="font-size:10.0pt;font-family:"Cambria",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt">Email: <a moz-do-not-send="true"
href="mailto:marika.konings@icann.org">marika.konings@icann.org</a> </span><span
style="font-size:10.0pt;font-family:"Cambria",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><i><span
style="font-size:10.0pt"> </span></i><span
style="font-size:10.0pt;font-family:"Cambria",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><i><span
style="font-size:10.0pt">Follow the GNSO via Twitter
@ICANN_GNSO<o:p></o:p></span></i></p>
<p class="MsoNormal" style="text-autospace:none"><i><span
style="font-size:10.0pt">Find out more about the GNSO by
taking our <a moz-do-not-send="true"
href="http://learn.icann.org/courses/gnso">interactive
courses</a> and visiting the <a moz-do-not-send="true"
href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">GNSO
Newcomer pages</a>.</span></i><span
style="font-size:10.0pt;font-family:"Cambria",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a moz-do-not-send="true" 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>
<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>