<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I think this is a very "creative" way to define the word optional
that goes against the very meaning of that word. I do not support
this unnatural definition.</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 03.09.2017 um 06:18 schrieb Greg
Shatan:<br>
</div>
<blockquote type="cite"
cite="mid:CA+aOHURuuZ5V=CPJ-jSztA4GVVA_YqWTjssqrahAj3A_e265BA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">If this definition of
optional made it all the way through to consensus policy, I
don't think we can simply reject it even if it seems
"unnatural." Policy should be conceptually consistent with
past policy wherever possible.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">I don't think "optional
to collect" is quite the right characterization. It's more
"mandatory to collect if present, but not a field that must be
filled out in order to complete the process [because the field
will be empty if there is no answer (or the answer will be
"none")].</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style=""><span
style="font-family:verdana,sans-serif">I also don't agree
with the statement that </span><font face="verdana,
sans-serif">"<span style="font-size:12.8px">the collection
side of the rds is whatever the registry does," for two
reasons. First, registries collect information for their
business purposes that are not part of the RDS. Second,
the RDS is being collected for directory purposes --
ultimately for the registrants and other users of the RDS,
so the RDS is not an outgrowth of registry collection
purposes; it's an effort that the registries undertake
because the policy requires it (which in turn is because
it is highly useful for a variety of reasons). </span></font></div>
<div class="gmail_default" style=""><font face="verdana,
sans-serif"><span style="font-size:12.8px"><br>
</span></font></div>
<div class="gmail_default" style=""><font face="verdana,
sans-serif"><span style="font-size:12.8px">Greg</span></font></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Sep 2, 2017 at 4:59 PM, John
Bambenek via gnso-rds-pdp-wg <span dir="ltr"><<a
href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I
understand that but what information a registrar collects
and what information is required or may be asked for is the
same list. So I'm unclear as to the confusion.<br>
<br>
--<br>
John Bambenek<br>
<div class="HOEnZb">
<div class="h5"><br>
> On Sep 2, 2017, at 12:08, "<a
href="mailto:benny@nordreg.se" moz-do-not-send="true">benny@nordreg.se</a>"
<<a href="mailto:benny@nordreg.se"
moz-do-not-send="true">benny@nordreg.se</a>> wrote:<br>
><br>
> Well for your 2. Phrase we are still talking
collection, not displaying<br>
><br>
> Sent from my iPhone<br>
><br>
>> On 2 Sep 2017, at 18:10, John Bambenek via
gnso-rds-pdp-wg <<a
href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>>
wrote:<br>
>><br>
>> I think the point is optional to collect,
mandatory to display if present.<br>
>><br>
>> So there are two sets of requirements.<br>
>><br>
>> 1- what information domain registrants give<br>
>> 2- what information RDS displays<br>
>><br>
>> --<br>
>> John Bambenek<br>
>><br>
>>> On Sep 2, 2017, at 10:11, Andrew Sullivan
<<a href="mailto:ajs@anvilwalrusden.com"
moz-do-not-send="true">ajs@anvilwalrusden.com</a>>
wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>>> On Fri, Sep 01, 2017 at 04:50:41PM
-0700, jonathan matkowsky wrote:<br>
>>>> It may be important to note from the
April 27 advisory<br>
>>>> <<a
href="https://www.icann.org/resources/pages/registry-agreement-raa-rdds-2015-04-27-en"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.icann.org/<wbr>resources/pages/registry-<wbr>agreement-raa-rdds-2015-04-27-<wbr>en</a>><br>
>>>> on that Consensus Policy that if data
exists for a given optional field,<br>
>>>> the data MUST be shown. So I would
suggest we define optional in that way.<br>
>>><br>
>>> That is a pretty unnatural definition of
"optional", and certainly not<br>
>>> one that I expect will be understood by any
implementer. Such a<br>
>>> redefinition away from the plain English
meaning of the word is just<br>
>>> asking for bugs. "Optional" means "you
don't have to fill it in", not<br>
>>> "someone might not have collected this".<br>
>>><br>
>>> A<br>
>>><br>
>>> --<br>
>>> Andrew Sullivan<br>
>>> <a href="mailto:ajs@anvilwalrusden.com"
moz-do-not-send="true">ajs@anvilwalrusden.com</a><br>
>>> ______________________________<wbr>_________________<br>
>>> gnso-rds-pdp-wg mailing list<br>
>>> <a href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
>>> <a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> gnso-rds-pdp-wg mailing list<br>
>> <a href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
>> <a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</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>