<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Its a policy bit but the ccNSO has to deal with that. I have to agree with Chuck. </div><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 21, 2017, at 19:40, Chuck <<a href="mailto:consult@cgomes.com" class="">consult@cgomes.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Please remember that our work relates to gTLDs not ccTLDs.<br class=""><br class="">Chuck<br class=""><br class="">-----Original Message-----<br class="">From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" class="">gnso-rds-pdp-wg-bounces@icann.org</a><br class="">[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" class="">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Paul Keating<br class="">Sent: Thursday, September 21, 2017 8:22 AM<br class="">To: Maxim Alzoba <<a href="mailto:m.alzoba@gmail.com" class="">m.alzoba@gmail.com</a>>; Volker Greimann<br class=""><<a href="mailto:vgreimann@key-systems.net" class="">vgreimann@key-systems.net</a>><br class="">Cc: <a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">Subject: Re: [gnso-rds-pdp-wg] Proposed Agreement for Original Registration<br class="">Date<br class=""><br class="">And, of course there is the issue of obtaining the data to fill the field<br class="">with a meaningful data element. It would require a link to historical data<br class="">that may or may not exist, particularly at the ccdld level.<br class=""><br class="">Paul<br class=""><br class="">On 9/21/17, 5:10 PM, "Maxim Alzoba" <<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" class="">gnso-rds-pdp-wg-bounces@icann.org</a> on<br class="">behalf of <a href="mailto:m.alzoba@gmail.com" class="">m.alzoba@gmail.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Is it better to make it list of previous periods of registration?<br class="">like dd/mm/yy-dd1/mm1/yy1 ?<br class=""><br class="">the bad thing is, most of old domain names will have something like <br class="">unknown, dd/mm/yy-dd1/mm1/yy1 (if we decide to have this field at all)<br class=""><br class="">Sincerely Yours,<br class=""><br class="">Maxim Alzoba<br class="">Special projects manager,<br class="">International Relations Department,<br class="">FAITID<br class=""><br class="">m. +7 916 6761580(+whatsapp)<br class="">skype oldfrogger<br class=""><br class="">Current UTC offset: +3.00 (.Moscow)<br class=""><br class=""><blockquote type="cite" class="">On Sep 21, 2017, at 17:54, Volker Greimann <br class=""><<a href="mailto:vgreimann@key-systems.net" class="">vgreimann@key-systems.net</a>><br class="">wrote:<br class=""><br class="">My issue with the counter is that it is just as prone to errors than <br class="">the originally proposed date. If you overlooked an old registration, <br class="">the count is wrong. So i prefer the y/n/u approach (if we take in the <br class="">field at all).<br class=""><br class="">Volker<br class=""><br class=""><br class="">Am 21.09.2017 um 16:48 schrieb Andrew Sullivan:<br class=""><blockquote type="cite" class="">On Thu, Sep 21, 2017 at 02:28:39PM +0000, Greg Aaron wrote:<br class=""><blockquote type="cite" class="">The alternate proposal is a simple marker that says whether there <br class="">has been a known previous iteration of the domain string, having <br class="">been registered with a different ROID.<br class=""><br class=""></blockquote>Or a counter, of course, rather than just the marker. From the <br class="">point of view of implementation in a database, I think these two <br class="">options are approximately the same, so I prefer the counter because <br class="">it provides an additional bit of data (that is, that the domain is <br class="">changing -- you can watch it happen).<br class=""><br class=""><blockquote type="cite" class="">And it still presents the same operational problem: the registry <br class="">has to figure out whether a string has existed before. That is <br class="">something registries are not designed to do. And they may not have <br class="">the necessary historical records. See the notes below.<br class=""><br class=""></blockquote>Well, no, that's part of the point of the new proposal: the registry <br class="">_doesn't_ have to figure that out, because the counter can be set to <br class="">"unknown" (in a SQL database, you'd probably use NULL). To support <br class="">this feature, however, the registry would have to track deletions of <br class="">domain names in the future. So it wouldn't be free, but it also <br class="">wouldn't be hard to implement. (Any real SQL database, for <br class="">instance, could do this with an ON DELETE trigger.)<br class=""><br class="">Best regards,<br class=""><br class="">A<br class=""><br class=""></blockquote><br class="">--<br class="">Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<br class=""><br class="">Mit freundlichen Grüßen,<br class=""><br class="">Volker A. Greimann<br class="">- Rechtsabteilung -<br class=""><br class="">Key-Systems GmbH<br class="">Im Oberen Werk 1<br class="">66386 St. Ingbert<br class="">Tel.: +49 (0) 6894 - 9396 901<br class="">Fax.: +49 (0) 6894 - 9396 851<br class="">Email: <a href="mailto:vgreimann@key-systems.net" class="">vgreimann@key-systems.net</a><br class=""><br class="">Web: <a href="http://www.key-systems.net" class="">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" class="">www.RRPproxy.net</a> <a href="http://www.domaindiscount24.com" class="">www.domaindiscount24.com</a> <br class="">/ <a href="http://www.BrandShelter.com" class="">www.BrandShelter.com</a><br class=""><br class="">Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<br class=""><a href="http://www.facebook.com/KeySystems" class="">www.facebook.com/KeySystems</a><br class="">www.twitter.com/key_systems<br class=""><br class="">Geschäftsführer: Alexander Siffrin<br class="">Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: <br class="">DE211006534<br class=""><br class="">Member of the KEYDRIVE GROUP<br class="">www.keydrive.lu<br class=""><br class="">Der Inhalt dieser Nachricht ist vertraulich und nur für den <br class="">angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, <br class="">Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist <br class="">unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so <br class="">bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu<br class=""></blockquote></blockquote>setzen.<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><br class="">--------------------------------------------<br class=""><br class="">Should you have any further questions, please do not hesitate to <br class="">contact us.<br class=""><br class="">Best regards,<br class=""><br class="">Volker A. Greimann<br class="">- legal department -<br class=""><br class="">Key-Systems GmbH<br class="">Im Oberen Werk 1<br class="">66386 St. Ingbert<br class="">Tel.: +49 (0) 6894 - 9396 901<br class="">Fax.: +49 (0) 6894 - 9396 851<br class="">Email: <a href="mailto:vgreimann@key-systems.net" class="">vgreimann@key-systems.net</a><br class=""><br class="">Web: <a href="http://www.key-systems.net" class="">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" class="">www.RRPproxy.net</a> <a href="http://www.domaindiscount24.com" class="">www.domaindiscount24.com</a> <br class="">/ <a href="http://www.BrandShelter.com" class="">www.BrandShelter.com</a><br class=""><br class="">Follow us on Twitter or join our fan community on Facebook and stay<br class="">updated:<br class=""><a href="http://www.facebook.com/KeySystems" class="">www.facebook.com/KeySystems</a><br class="">www.twitter.com/key_systems<br class=""><br class="">CEO: Alexander Siffrin<br class="">Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534<br class=""><br class="">Member of the KEYDRIVE GROUP<br class="">www.keydrive.lu<br class=""><br class="">This e-mail and its attachments is intended only for the person to <br class="">whom it is addressed. Furthermore it is not permitted to publish any <br class="">content of this email. You must not use, disclose, copy, print or rely <br class="">on this e-mail. If an addressing or transmission error has misdirected <br class="">this e-mail, kindly notify the author by replying to this e-mail or <br class="">contacting us by telephone.<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class="">gnso-rds-pdp-wg@icann.org<br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg<br class=""></blockquote><br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg<br class=""></blockquote><br class=""><br class="">_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg<br class=""><br class="">_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class="">gnso-rds-pdp-wg@icann.org<br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg<br class=""></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Kris Seeburn</div><div class=""><a href="mailto:seeburn.k@gmail.com" class="">seeburn.k@gmail.com</a></div><div class=""><ul style="margin: 0px; padding: 0px 0px 8px; border: 0px; outline: 0px; font-family: Helvetica, Arial, sans-serif; vertical-align: baseline; list-style: none; line-height: 17px; display: table-cell; width: 504px; color: rgb(51, 51, 51);" class=""><li style="margin: 0px; padding: 8px 12px 2px 0px; border: 0px; outline: 0px; font-style: inherit; font-size: 11px; font-family: inherit; vertical-align: baseline; font-variant: inherit; line-height: 1.2em;" class=""><dl class="public-profile" style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: baseline; font-variant: inherit; line-height: inherit; word-wrap: break-word;"><dd style="margin: 0px; padding: 2px 9px 1px 0px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: top; font-variant: inherit; line-height: inherit; display: inline-block; zoom: 1;" class=""><a href="http://www.linkedin.com/in/kseeburn/" title="View public profile" name="webProfileURL" style="margin: 0px 10px 0px 0px; padding: 0px 0px 0px 19px; border: 0px; outline: 0px; font-style: inherit; font-family: inherit; vertical-align: middle; text-decoration: none; color: rgb(102, 102, 102); font-variant: inherit; line-height: inherit; display: inline-block; zoom: 1; background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/apps/profile/sprite/sprite_profile_top_card_v8.png); background-position: 0px -249px; background-repeat: no-repeat no-repeat;" class="">www.linkedin.com/in/kseeburn/</a></dd></dl></li></ul></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>