<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi all,</p>
<p>going back to the new policy, it actually merely specifies where
existing data fields must be placed, it does not create an
obligation to fill optional fields though as the pühone number was
not formally required. As such, the provision of data for the
registrar abuse phone was and still is completely voluntary, but
if it is provided, it must be placed where this new policy states.
Compare also section 3.18.1 of the 2013 RAA which only requires
the creation of an abuse email contact for general use. I
therefore propose that our agreement be rephrased to be compatible
with the RAA:</p>
<p>RDS MUST support email and phone<br>
Registrars MUST provide email<br>
Registrars MAY provide phone</p>
<p>(And potentially alternatives could be included too. If a
registrar accepts complaints by smoke signals, why not have a
field for "other abuse contacts"?)<br>
</p>
<p>Based on this, we may also want to consider additional fields for
the RDS however that currently are not in whois, .e.g. the LEA
abuse contacts. with the RDS, it may make sense to include them
(with access limited only to LEAs of the registrars'
jurisdiction).</p>
<p>Best,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 30.08.2017 um 15:22 schrieb Greg
Aaron:<br>
</div>
<blockquote type="cite"
cite="mid:BN6PR13MB18434B74A279314FDE824C74D99C0@BN6PR13MB1843.namprd13.prod.outlook.com">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{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;}
--></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"><a name="_MailEndCompose"
moz-do-not-send="true">The first question of this poll asks
whether Reseller Name must be supported by the RDS, and
whether it MUST or MAY be provided for inclusion in the RDS
by Registrars.<o:p></o:p></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">This
issue was decided by the Registry Registration Data
Directory Services Consistent Labeling and Display Policy, a
Consensus Policy that went into effect 1 August 2017. It
says:
<span style="color:#333333;background:white">“In responses
to domain name object queries the following fields are
considered optional … Reseller.”
</span></span><a
href="https://www.icann.org/resources/pages/rdds-labeling-policy-2017-02-01-en"
moz-do-not-send="true"><span
style="mso-bookmark:_MailEndCompose"><span
style="background:white">https://www.icann.org/resources/pages/rdds-labeling-policy-2017-02-01-en</span></span><span
style="mso-bookmark:_MailEndCompose"></span></a><span
style="mso-bookmark:_MailEndCompose"> The policy says that
the system must support this field, it’s optional for
registrars to fill in that field, and the field is displayed
in output if the registrar provided the data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">The</span><span
style="mso-bookmark:_MailEndCompose"><span
style="color:#333333;background:white"> WG is accepting
the results of that Consensus Policy regarding Registrar
Abuse contacts. So I suggest it also follow what that
that same Consensus Policy says about for Reseller Name.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="color:#333333;background:white"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="color:#333333;background:white">Thanks,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="color:#333333;background:white">--Greg</span></span><span
style="mso-bookmark:_MailEndCompose"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<div>
<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:10.0pt">Greg Aaron<o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="mso-bookmark:_MailEndCompose"><span
style="font-size:10.0pt">Vice-President, Product
Management<o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="mso-bookmark:_MailEndCompose"><span
style="font-size:10.0pt">iThreat Cyber Group /
Cybertoolbelt.com<o:p></o:p></span></span></p>
<p class="MsoNormal"><span
style="mso-bookmark:_MailEndCompose"><span
style="font-size:10.0pt">mobile: +1.215.858.2257<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:10.0pt">The information contained in
this message is privileged and confidential and
protected from disclosure. If the reader of this message
is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended
recipient, you are hereby notified that any
dissemination, distribution or copying of this
communication is strictly prohibited. If you have
received this communication in error, please notify us
immediately by replying to the message and deleting it
from your computer.<o:p></o:p></span></span></p>
</div>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></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>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a 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>Lisa Phifer<br>
<b>Sent:</b> Wednesday, August 30, 2017 12:25 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [gnso-rds-pdp-wg] IMPORTANT: Invitation
for Poll from 29 August Meeting<br>
<b>Importance:</b> High<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In follow-up to this week’s WG meeting, <b>all
RDS PDP WG Members</b> are encouraged to participate in the
following poll:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a
href="https://www.surveymonkey.com/r/DKQTQHP"
moz-do-not-send="true"><span style="background:white">https://www.surveymonkey.com/r/DKQTQHP</span></a><strong><span
style="font-family:"Calibri",sans-serif;color:#333333;background:white"><o:p></o:p></span></strong></p>
<p class="MsoNormal"><strong><span
style="font-family:"Calibri",sans-serif;color:#333333;background:white"><o:p> </o:p></span></strong></p>
<p class="MsoNormal">Responses should be submitted through the
above URL. For offline reference, a PDF of poll questions can
also be found at:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a
href="https://community.icann.org/download/attachments/66086750/Poll-from-29AugustCall.pdf"
moz-do-not-send="true">https://community.icann.org/download/attachments/66086750/Poll-from-29AugustCall.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>This poll will close at COB Saturday 2
September. Poll results will be discussed in our 5
September WG meeting.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please note that you <u>must be a WG
Member</u> to participate in polls. If you are a WG Observer
wishing to participate in polls, you must first contact
<a href="mailto:gnso-secs@icann.org" moz-do-not-send="true">gnso-secs@icann.org</a>
to upgrade to WG Member.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Lisa<o:p></o:p></p>
</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>