- RDS-WHOIS2-RT - lists.icann.org

Fwd: [Gnso-impl-thickwhois-rt] Thick Whois Policy for .COM, .NET, .JOBS: Versign letter 20180413
by Carlton Samuels April 27, 2018

April 27, 2018

FYI ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* ============================= ---------- Forwarded message ---------- From: Dennis Chang <dennis.chang(a)icann.org> Date: Thu, Apr 26, 2018 at 12:14 PM Subject: [Gnso-impl-thickwhois-rt] Thick Whois Policy for .COM, .NET, .JOBS: Versign letter 20180413 To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Dear Thick IRT, Please note that a letter from Verisign on Thick Whois Consensus Policy has been posted on the ICANN correspondence page. https://www.icann.org/en/system/files/correspondence/ kane-to-atallah-13apr18-en.pdf https://www.icann.org/resources/pages/correspondence — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet" _______________________________________________ Gnso-impl-thickwhois-rt mailing list Gnso-impl-thickwhois-rt(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

1 0

Re: [RDS-WHOIS2-RT] [Ext] RE: CONFIRMATION NEEDED - Questions for ICANN Compliance
by Susan Kawaguchi April 19, 2018

April 19, 2018

Hello All, Thank you Lili for the list of additional questions. These all relate to our discussions at the F2F. Please submit to the compliance team on our behalf. Best regards, Susan On Thu, Apr 19, 2018 at 11:52 AM, Alice Jansen <alice.jansen(a)icann.org> wrote: > Many thanks, Lili and Susan. > > We will send these over to ICANN compliance and will get back to you on > the estimated delivery date. > > Could I ask you to send a note out to your subroups to inform them of the > list of questions? That way, the request will also be official. > > Thanks so much and safe travels! It was great to have you in Brussels! > > Kind regards > > Alice > > > > *From: *SUN Lili <L.SUN(a)interpol.int> > *Date: *Thursday 19 April 2018 at 07:05 > *To: *Susan Kawaguchi <susankpolicy(a)gmail.com>, Alice Jansen < > alice.jansen(a)icann.org> > *Cc: *Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org>, Lisa > Phifer <lisa(a)corecom.com> > *Subject: *[Ext] RE: CONFIRMATION NEEDED - Questions for ICANN Compliance > > > > Hi Alice, hi Susan, > > > > Please check below the updated questions for ICANN Compliance, 2 questions > from Data-Accuracy Subgroup have been solved, I added 3 more questions > relating to compliance for Susan’s consideration. > > > > Thanks and best regards, > > Lili > > > > - *Data-Accuracy Subgroup Follow-up Questions for ICANN Compliance: * > > 1. Does the Compliance Team attempt to identify patterns within > ARS-detected inaccuracies to enable proactive remediation of underlying > causes? > > 2. If a domain registration is suspended due to a reported or > detected WHOIS inaccuracy, can the domain name be un-suspended without the > inaccuracy being remediated? > > 3. Does the WHOIS Quality Review (or any other program) audit how > often un-suspension without accuracy remediation occurs? If so, for how > long after suspension are those follow-up accuracy checks performed? > > 4. Considering ARS compliance metrics: Why are the percentage of > ticketed domains that end up being suspended or cancelled is increasing? > > [image: cid:image002.jpg@01D3D7DE.F0100690] > > 5. ( Solved, delete) What percentage of ARS-initiated WHOIS > Inaccuracy compliance tickets result in updates to correct WHOIS data prior > to 3rd failure & breach notices? > > This is already provided by WHOIS ARS Contractual Compliance > Metrics[whois.icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en_who…> > . > > 6. ( Solved, delete) Is WDRP compliance being audited and reported? > If so where? > > WDRP compliance has been audited since 2012 as one of the many 2009 & 2013 > RAA provisions, see more detail at Contractual Compliance Audit > Program[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. > However, only selected (or sampled) registrars were audited during each > round, and besides a general percentage (20%-35%) of registrars with a > deficiency on this, there was no further detail about the deficiency. See > below the specific audit reports: > > 2016 May Contractual Compliance Registrar Audit Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > [PDF, 372 KB] > > 2016 September Contractual Compliance Registrar Audit Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > [PDF, 238 KB] > > 2015 September Contractual Compliance Registrar Audit Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > [PDF, 258 KB] > > 2014 Contractual Compliance Year Three Audit Program Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_resou…> > [PDF, 851 KB] > > 2013 Contractual Compliance Year Two Audit Program Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > [PDF, 900 KB] > > 2012 Contractual Compliance Year One Audit Program Report[icann.org] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> > [PDF, 322 KB] > > > > - *Compliance Subgroup Follow-up Questions for ICANN Compliance * > > 1. Is it known (or can it be determined from ARS-sampled data) how > often Registrant Contact data elements such as Registrant email address, > Registrant postal address, and Registrant telephone number are absent from > WHOIS records for grandfathered domain names? > > 2. Why are a significant number of WHOIS Inacccuracy Complaints > closed without any action being taken? What does Compliance treat as valid > reasons for immediate ticket closure and are there any metrics for how > often tickets are closed for each of those reasons? > > 3. What additional evidence in WHOIS Inaccuracy Complaints would > Compliance find useful? > > 4. Does Compliance do any analysis of WHOIS Inaccuracy trends? If > not, why not? For example, would a policy be necessary to enable trend > analysis? > > 5. ( Newly added) It shows that one of Compliance activities is > ICANN-initiated monitoring to take proactive actions. What kind of > monitoring programs have been conducted or planned? > > 6. ( Newly added) Is there any monitoring program to check some > common grounds or linkages among ARS, Audit Program, public complaints > received, e.g. from specific registrar, gTLD, region? > > 7. ( Newly added) Does compliance credit-rate registrars or just > treat all of them equally? > > > > *From:* Susan Kawaguchi [mailto:susankpolicy@gmail.com] > *Sent:* Wednesday, 18 April, 2018 7:34 PM > *To:* Alice Jansen <alice.jansen(a)icann.org> > *Cc:* SUN Lili <L.SUN(a)interpol.int>; Jean-Baptiste Deroulez < > jean-baptiste.deroulez(a)icann.org>; Lisa Phifer <lisa(a)corecom.com> > *Subject:* Re: CONFIRMATION NEEDED - Questions for ICANN Compliance > > > > Thanks Alice and Jean-Baptiste, > > > > All the questions seem fine to me. > > > > Susan > > > > On Tue, Apr 17, 2018 at 11:29 AM, Alice Jansen <alice.jansen(a)icann.org> > wrote: > > Hi Lili, Hi Susan, > > Below you will find the list of questions we extracted from the data > accuracy and compliance subgroups related discussions yesterday. > > Please review and let us know if you have any edits at your earliest > convenience. > > We will send to ICANN compliance once we have received your confirmations. > > Thanks, > > Kind regards > > Alice > > > > - *Data-Accuracy Subgroup Follow-up Questions for ICANN Compliance: * > > 1. What percentage of ARS-initiated WHOIS Inaccuracy compliance > tickets result in updates to correct WHOIS data prior to 3rd failure & > breach notices? > > 2. Does the Compliance Team attempt to detect patterns within > ARS-detected inaccuracies to enable proactive remediation of underlying > causes? > > 3. Is WDRP compliance being audited and reported? If so where? > > 4. If a domain registration is suspended due to a reported or > detected WHOIS inaccuracy, can the domain name be un-suspended without the > inaccuracy being remediated? > > 5. Does the WHOIS Quality Review (or any other program) audit how > often un-suspension without accuracy remediation occurs? If so, for how > long after suspension are those follow-up accuracy checks performed? > > 6. Considering ARS compliance metrics: Why are the percentage of > ticketed domains that end up being suspended or cancelled is increasing? > > > > - *Compliance Subgroup Follow-up Questions for ICANN Compliance * > > 1. Is it known (or can it be determined from ARS-sampled data) how > often Registrant Contact data elements such as Registrant email address, > Registrant postal address, and Registrant telephone number are absent from > WHOIS records for grandfathered domain names? > > 2. Why are a significant number of WHOIS Inacccuracy Complaints > closed without any action being taken? What does Compliance treat as valid > reasons for immediate ticket closure and are there any metrics for how > often tickets are closed for each of those reasons? > > 3. What additional evidence in WHOIS Inaccuracy Complaints would > Compliance find useful? > > 4. Does Compliance do any analysis of WHOIS Inaccuracy trends? If > not, why not? For example, would a policy be necessary to enable trend > analysis? > > > > > > > > ************************************************************ > *************************************** > This message, and any attachment contained, are confidential and subject > of legal privilege. It may be used solely for the designated police/justice > purpose and by the individual or entity to whom it is addressed. The > information is not to be disseminated to another agency or third party > without the author’s consent, and must not be retained longer than is > necessary for the fulfilment of the purpose for which the information is to > be used. All practicable steps shall be taken by the recipients to ensure > that information is protected against unauthorised access or processing. > INTERPOL reserves the right to enquire about the use of the information > provided. > If you are not the intended recipient, be advised that you have received > this message in error. In such a case, you should not print it, copy it, > make any use of it or disclose it, but please notify us immediately and > delete the message from any computer. > ************************************************************ > ************************************* >

1 0

USG To ICANN: Investigate GoDaddy for Blocking WHOIS Port 43 Access
by Carlton Samuels April 17, 2018

April 17, 2018

....and even suggesting that un-accredited registrars be authorized to do stuff!! So it appears Uncle Sam is prepared to go nuclear and bring down the whole multistakeholder temple, lock, stock and barrel! https://domainnamewire.com/2018/04/16/u-s-government-asks-icann-to-investig… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

2 1

Written implementation briefing - WHOIS1 rec 1
by Alice Jansen April 15, 2018

April 15, 2018

Dear Review Team Members, Attached to this email you will find the written implementation briefing for WHOIS recommendation 1 on Strategic Priority. All written implementation briefings were submitted. Please be kindly reminded that answers to your briefing requests are compiled on one wiki page for ease of reference – see https://community.icann.org/display/WHO/Briefing+Materials Thank you Kind regards Alice

2 1

Dinner on Sunday
by Alan Greenberg April 15, 2018

April 15, 2018

If anyone is interested in getting together for dinner on Sunday, let me know. Alan

3 2

Re: [RDS-WHOIS2-RT] Art 29 WP response
by Alan Greenberg April 14, 2018

April 14, 2018

In my mind, the real question is whether they are subject to any pressure from their own law enforcement and communications ministries. Alan At 13/04/2018 07:15 PM, Carlton Samuels wrote: >Hate to say I told you so. But its proof of my >own estimation that the response was going to be a yawn. > >I cannot understand why given the history and an >competent understanding of how any bureaucracy, >much less a Eurocrat one, defined in law and >bounded by practice, would suddenly change their collective minds! > >-Carlton > > >============================== >Carlton A Samuels >Mobile: 876-818-1799 >Strategy, Planning, Governance, Assessment & Turnaround >============================= > >On Fri, Apr 13, 2018 at 5:47 AM, Volker Greimann ><<mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net> wrote: >As this may be somewhat relevant to the work we >are doing, here is a link to the response of the Art. 29 WG to ICANNs letter: > ><https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr…>https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr… > >To be sure, there is nothing substantially new >in here, it re-iterates positions that many have >voiced towards ICANN for years now, but it does >provide a clear overview of where ICANNs >proposed interim model falls short, and what the >constrants to tiered access would be. While some >already interpret this as "whois is dead!", I >would not go so far, but for certain uses - >beneficial as they may be - that statement >probably applies. In general, this seems to >provide a solid basis for further work, but >ICANN should not have wasted its time waiting >for this response instead of continuing to >refine their interim model with what everyone >(but ICANN Org apparently) was already expecting. > >-- >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: <mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > >Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net ><http://www.domaindiscount24.com>www.domaindiscount24.com >/ www.BrandShelter.com > >Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems >www.twitter.com/key_systems > >GeschÃ¤ftsfÃ¼hrer: Alexander Siffrin >Handelsregister Nr.: HR B 18835 - Saarbruecken >Umsatzsteuer ID.: DE211006534 > >Member of the KEYDRIVE GROUP ><http://www.keydrive.lu>www.keydrive.lu > >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: <mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > >Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net ><http://www.domaindiscount24.com>www.domaindiscount24.com >/ www.BrandShelter.com > >Follow us on Twitter or join our fan community on Facebook and stay updated: ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems >www.twitter.com/key_systems > >CEO: Alexander Siffrin >Registration No.: HR B 18835 - Saarbruecken >V.A.T. ID.: DE211006534 > >Member of the KEYDRIVE GROUP ><http://www.keydrive.lu>www.keydrive.lu > >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. > > > >_______________________________________________ >RDS-WHOIS2-RT mailing list ><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YTOPR01MB0396;27:Ggpr2nQf8liegfTIYKxZR73kz429rDaCUD9dRGQHbkInGi9J4KWl5iJZ2cjlPeVOTaqvR+w/H+ktERTZgj96/DBS+ewB4+HTft2Zi8Hz9vYw/OUB1WKNcBRnf6TF/AiD >X-Microsoft-Antispam-Message-Info: > >Wqxkf+2rUHbohSb8H8GZo3CZL7mPFMh6DdKksJjjB0+oEKbFMOrsCrkjWZlI0849V5pQEQbWgszcdUDs4Oo16ywu5ajx1RxXP0qBGpoPhNDV42mJ5Zl3rAhpo3pSaSbj4IAespnNm3yrSU6XzKQG/qmee5ftxOOrbPua/pSvvYWMgeLXkRKzmIatQ3pBisZMRZtNlzg1p2GmkR4kGUeR9gjrSgjBbOKkCfJTwgsK07DgPnxvkBFa8Moh/q/G/g0Vbl850En+wCKD9PGjDi5TerW5QpKfef5Xcvlu3qF2IrXu9C+gpXyZVxDoqoAAdDp4gzqkZoGNkcVpFgWROvoYYsZdRB82LjPNURWjCEZxMM/QfI7vYlqV1gRxR0Rzz5UqVfTKfpFqyDeZPCVk6VFM3MrtWZcJiGosRVkC0sDypWH81aWSnMWltCH/5rPZEguDMpoF3lKRl6HkmbSukXyLEvPr7EeXwK70Hv+6Q/ds0vQZjIqxhdFbNGpYOerOX94L > >_______________________________________________ >RDS-WHOIS2-RT mailing list >RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt

3 4

Art 29 WP response
by Volker Greimann April 13, 2018

April 13, 2018

As this may be somewhat relevant to the work we are doing, here is a link to the response of the Art. 29 WG to ICANNs letter: https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr… To be sure, there is nothing substantially new in here, it re-iterates positions that many have voiced towards ICANN for years now, but it does provide a clear overview of where ICANNs proposed interim model falls short, and what the constrants to tiered access would be. While some already interpret this as "whois is dead!", I would not go so far, but for certain uses - beneficial as they may be - that statement probably applies. In general, this seems to provide a solid basis for further work, but ICANN should not have wasted its time waiting for this response instead of continuing to refine their interim model with what everyone (but ICANN Org apparently) was already expecting. -- 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: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu 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: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu 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.

3 2

Draft Safeguard Data slides for Alan to expand
by Alan Greenberg April 13, 2018

April 13, 2018

I have shifted this thread from the Safeguard sub-group to the main mailing list. Volker, I think that treating this a an example of how WHOIS was not made a strategic priority is a MARVELLOUS idea. It shifts the discussion from which data elements need to be protected, and how (where there are still VERY different ideas in the community) to why did ICANN ignore the issue that was well known for so long, and when it did start, why do it so slowly. Alan At 13/04/2018 12:59 PM, Volker Greimann wrote: >Hi Alan, > >I see it in a similar way to the recommendations >of the first RT. When the first RT recommended >that ICANN make Whois a strategic priority, we >can certainly do the same for safeguarding >registration data in the context of data privacy >laws. Years down the road, a new RT can then >review how well ICANN did in that regard. > >I would also recommend that we reference this in >our review of the stratprio recommendation as >ICANN seems to have mainly ignored that aspect >even though the recommendation read that it >should make it a stratprio in ALL of its >aspects. The rush and panic we are experiencing >now is a direct result of this failure and we >should not ignore this in our report. In fact, >it may be the biggest issue ICANN has with the >implementation of the first RT recs, depending >on their interpretation, of course. > >Volker > >Am 13.04.2018 um 18:49 schrieb Alan Greenberg: >>I have no problem with noting this, but I see >>no actionable recommendation. The Board has >>already chartered a PDP and is taking interim (GDPR) corrective action. >> >>At 13/04/2018 12:38 PM, Volker Greimann wrote: >> >>>Not really, we should just analyze for how >>>long ICANN has known about this issue but >>>chosen to ignore it, and recommend that they >>>now take the safeguarding of private data to >>>heart and learn from past mistakes. We will >>>not (and should not) give specific >>>implementation advice or tell them how to do >>>their job. But we can tell them that they >>>should do their job and in fact should have done their jobs years ago. >>> >>>The how and what is ICANNs business and we >>>should not intrude on that, but the fact that >>>action and a re-orientation is needed is >>>something that we very well can recommend. >>>This will re-enforce the requirement but not intrude on any ongoing work. >>> >>>I believe this is one of the single most >>>important issues regarding whois and by >>>ignoring it we risk total irrelevance of our work. >>> >>>Volker >>> >>>Am 13.04.2018 um 17:31 schrieb Alan Greenberg: >>>>It is stating an opinion on how ICANN should >>>>be preceding. We have already agreed that we >>>>will say that the data has been completely >>>>open and that ICANN has provided NO protection against any use or abuse. >>>> >>>>If GDPR and the PDP were not happening, we >>>>could certainly make a recommendation that >>>>ICANN should charter a group to decide on >>>>what data should be protected and how. But >>>>that seems rather moot at this point in time. >>>> >>>>Alan >>>> >>>>At 13/04/2018 10:28 AM, Stephanie Perrin wrote: >>>> >>>>>How is Volkers suggestion getting us >>>>>actively involved in the GDPR frenzy? I think it is a logical thing to do. >>>>> >>>>>Stephanie >>>>>On 2018-04-13 10:17, Alan Greenberg wrote: >>>>>>Volker, we made a decision long ago to not >>>>>>get actively involved in the GDPR frenzy as >>>>>>that directly overlaps with the current >>>>>>process (as faulted as some people may >>>>>>think it is). Moreover, given the timing of >>>>>>our final report, it is not at all obvious what purpose such work would serve. >>>>>> >>>>>>Alan >>>>>> >>>>>>At 13/04/2018 07:12 AM, Volker Greimann wrote: >>>>>> >>>>>>>I think we should, under the shadow of the >>>>>>>oncoming GDPR, expand on the analysis >>>>>>>section under 3 a), stating that in this >>>>>>>respect, ICANN and the community seem to >>>>>>>have failed completely at ensuring >>>>>>>registrant details are safeguarded from >>>>>>>unauthorized or abusive access. We can >>>>>>>then point to the extreme volumes of spam >>>>>>>each new registration generates for the >>>>>>>registrant, the harvesting of data in >>>>>>>historic databases and various examples of >>>>>>>doxxing (if we find any) based on whois data. >>>>>>> >>>>>>>This would then also inform the question >>>>>>>we could ask not only contracted parties, >>>>>>>but also affected members of civil society. >>>>>>> >>>>>>>Our summary of relevant research should >>>>>>>also include every letter DPAs have ever >>>>>>>written to ICANN on this topic, including >>>>>>>the letter from the Dutch DPA Re: .Amsterdam. >>>>>>> >>>>>>>Volker >>>>>>> >>>>>>>Am 12.04.2018 um 21:48 schrieb Alan Greenberg: >>>>>>>>Attached please find the updated draft report and slide deck. >>>>>>>> >>>>>>>>At 10/04/2018 12:48 AM, Lisa Phifer wrote: >>>>>>>> >>>>>>>>>Dear Subgroup 5 (Safeguarding Registrant Data) - >>>>>>>>> >>>>>>>>>As discussed in our plenary call, >>>>>>>>>attached are draft slides for Alan to review/revise on behalf of your subgroup. >>>>>>>>> >>>>>>>>>The content of these slides is based on this draft subgroup report: >>>>>>>>>https://community.icann.org/download/attachments/71604740/Subgroup5-Safegua… >>>>>>>>> >>>>>>>>> >>>>>>>>>As a reminder, here is the timeline for slide completion: >>>>>>>>> Monday 9 April COB - ICANN org support >>>>>>>>>team to send draft slides to subgroup Rapporteurs >>>>>>>>> Thursday 12 April COB - Rapporteurs to >>>>>>>>>send final updates to slides to ICANN org support team >>>>>>>>> Friday 13 April COB - ICANN org >>>>>>>>>support team to circulate final slide-deck with the review team >>>>>>>>> >>>>>>>>>Regards >>>>>>>>>Lisa >>>>>>>>>Content-Type: application/octet-stream; >>>>>>>>>name="RDS - Brussels F2F MTG - Draft Slides - SG5 DataSafe.pptx"; >>>>>>>>> x-mac-type="534C4433"; x-mac-creator="50505433" >>>>>>>>>Content-Disposition: attachment; >>>>>>>>>filename="RDS - Brussels F2F MTG - Draft Slides - SG5 DataSafe.pptx" >>>>>>>>>X-Microsoft-Exchange-Diagnostics: >>>>>>>>> >>>>>>>>>1;YTOPR01MB0396;27:MqKo9F512hQvQz5+v4rhqfuD5de02Qc03fK6EZkp0jXxK1xa0k19wYA53bV1QNYrI07qWY1Q4+B1fgN0Qx7D5GNb75zzNpEMPrk1uNG291ewcsNg1R5F1ccqacMAJNbi >>>>>>>>>X-Microsoft-Antispam-Message-Info: >>>>>>>>> >>>>>>>>>lWmLDC3W3a1iVEzM34JwpUSw3WWqVKn6AoVxKvtTY2isRYpV06AYdWdhg8OQHLYXYJJ0aEVpuTbIpoXW/pBSfmc5q6Tctzt1lS5Ud59u29EM1IVc+/3eWosPPiMW/mfRTjuq4StZdTOafUJjwf/vB7pnxHts9GQjmo9C7F0wW3yx5TbmKeRNkjG2+578NQvHKqtbmYNTaQuJuw/v9yevcJY67kez7190Trd0pYTJva1WQw+S2U7pW6vWlROut5sOEHRUeOeyp1t9cPi/ihnLpz0eLf1CEDo6yagGqtC4uUSL0QIJYEtmlgthYcvvAMt4NCZJUQMhq9Z0u0ASU9P2Yo1YhH7Sdn4sWc2/l3dRFwMbQshKgTx6dOCYisVWTqW3x7N4s4wBaNDodW9HsVu5eyeIvT+fUD8j3yJo+ukp/nQm47T9zJnOFqLuO15tmc/xw76p+ZBz/bJF9BJT0B9N/2mU7VpAUtteXX3VtLT2zoeZ/qf2837YJUJJ09H77WLj >>>>>>>>> >>>>>>>>>Content-Type: text/plain; charset="us-ascii" >>>>>>>>>Content-Transfer-Encoding: 7bit >>>>>>>>>Content-Disposition: inline >>>>>>>>>X-Microsoft-Exchange-Diagnostics: >>>>>>>>> >>>>>>>>>1;YTOPR01MB0396;27:MqKo9F512hQvQz5+v4rhqfuD5de02Qc03fK6EZkp0jXxK1xa0k19wYA53bV1QNYrI07qWY1Q4+B1fgN0Qx7D5GNb75zzNpEMPrk1uNG291ewcsNg1R5F1ccqacMAJNbi >>>>>>>>>X-Microsoft-Antispam-Message-Info: >>>>>>>>> >>>>>>>>>lWmLDC3W3a1iVEzM34JwpUSw3WWqVKn6AoVxKvtTY2isRYpV06AYdWdhg8OQHLYXYJJ0aEVpuTbIpoXW/pBSfmc5q6Tctzt1lS5Ud59u29EM1IVc+/3eWosPPiMW/mfRTjuq4StZdTOafUJjwf/vB7pnxHts9GQjmo9C7F0wW3yx5TbmKeRNkjG2+578NQvHKqtbmYNTaQuJuw/v9yevcJY67kez7190Trd0pYTJva1WQw+S2U7pW6vWlROut5sOEHRUeOeyp1t9cPi/ihnLpz0eLf1CEDo6yagGqtC4uUSL0QIJYEtmlgthYcvvAMt4NCZJUQMhq9Z0u0ASU9P2Yo1YhH7Sdn4sWc2/l3dRFwMbQshKgTx6dOCYisVWTqW3x7N4s4wBaNDodW9HsVu5eyeIvT+fUD8j3yJo+ukp/nQm47T9zJnOFqLuO15tmc/xw76p+ZBz/bJF9BJT0B9N/2mU7VpAUtteXX3VtLT2zoeZ/qf2837YJUJJ09H77WLj >>>>>>>>> >>>>>>>>>_______________________________________________ >>>>>>>>>RDS-WHOIS2-Safeguard mailing list >>>>>>>>><mailto:RDS-WHOIS2-Safeguard@icann.org>RDS-WHOIS2-Safeguard(a)icann.org >>>>>>>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>_______________________________________________ >>>>>>>>RDS-WHOIS2-Safeguard mailing list >>>>>>>><mailto:RDS-WHOIS2-Safeguard@icann.org> >>>>>>>>RDS-WHOIS2-Safeguard(a)icann.org >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>-- >>>>>>>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: >>>>>>><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net >>>>>>> >>>>>>>Web: <http://www.key-systems.net>www.key-systems.net / >>>>>>>www.RRPproxy.net >>>>>>><http://www.domaindiscount24.com>www.domaindiscount24.com / >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.BrandShelter.com >>>>>>> >>>>>>>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.facebook.com/KeySystems >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.twitter.com/key_systems >>>>>>> >>>>>>>Geschäftsführer: Alexander Siffrin >>>>>>>Handelsregister Nr.: HR B 18835 - Saarbruecken >>>>>>>Umsatzsteuer ID.: DE211006534 >>>>>>> >>>>>>>Member of the KEYDRIVE GROUP >>>>>>><http://www.keydrive.lu>www.keydrive.lu >>>>>>> >>>>>>>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: >>>>>>><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net >>>>>>> >>>>>>>Web: <http://www.key-systems.net>www.key-systems.net / >>>>>>>www.RRPproxy.net >>>>>>><http://www.domaindiscount24.com>www.domaindiscount24.com / >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.BrandShelter.com >>>>>>> >>>>>>>Follow us on Twitter or join our fan community on Facebook and stay >>>>>>>updated: >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.facebook.com/KeySystems >>>>>>> >>>>>>> >>>>>>> >>>>>>>www.twitter.com/key_systems >>>>>>> >>>>>>>CEO: Alexander Siffrin >>>>>>>Registration No.: HR B 18835 - Saarbruecken >>>>>>>V.A.T. ID.: DE211006534 >>>>>>> >>>>>>>Member of the KEYDRIVE GROUP >>>>>>><http://www.keydrive.lu>www.keydrive.lu >>>>>>> >>>>>>>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. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>Content-Type: text/plain; charset="us-ascii" >>>>>>>Content-Transfer-Encoding: 7bit >>>>>>>Content-Disposition: inline >>>>>>>X-Microsoft-Exchange-Diagnostics: >>>>>>> >>>>>>>1;YQBPR01MB0385;27:fcoqR4+uQx1cyGOa1rme9k1E26KN5BcsZFadOZrjuGKGe7AHjG/qCOF9GKny6kQC+sknDU0Rmt2EvTh31LI81uGQ5pnN+/OjCIM2R7AqiIlAB8NqeoYIRW0/N4vlidxs >>>>>>>X-Microsoft-Antispam-Message-Info: >>>>>>> >>>>>>>h7DLEGRKssrWt0XZkpU/cfqfkvSlhNZtMdAXGyjy8SBORAWoYaHHuu540i/p+0P4N14ceih+Vh3gGPTomEuWyh0P/jWxWqoeuWrhXet+ZcT/6sBtjai5psejClJGel4KVCF9yjd1zBb5OGZOokf5YK66srrmyE/tDJkRC3DauI6kDTKDbzF6PZnBfJJT8GSYrbSyfNuBSJAMFcj/wtk5QDey8uURQM0POrYKjtbiEXBNUy4H56bfADX8GbwfHOTq1RoIW+j+v42CZCAouCy11Cx4dVDijO0Rj9urFmsbNl1tE8TFx0pNOko1fI36Dhg6O28qRqpUm6SCfRa/kCcd3qp7JTBxgLYlR5mKljhvihMXyscPfxQkULs2FRN7PCpAkNbswO0a7/06nfPwDVQTwqE4ej9vzp5sxw5FKJ1V+6GRlIZRgUOZB1ddGQRwKjGzLrFUfmZ5p9bf63FuoUiv9tVnLVtHRPafG8Tp4ZJCFhI/tdvLTQhivePjc+tGopaU >>>>>>> >>>>>>>_______________________________________________ >>>>>>>RDS-WHOIS2-Safeguard mailing list >>>>>>><mailto:RDS-WHOIS2-Safeguard@icann.org>RDS-WHOIS2-Safeguard(a)icann.org >>>>>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>_______________________________________________ >>>>>>RDS-WHOIS2-Safeguard mailing list >>>>>><mailto:RDS-WHOIS2-Safeguard@icann.org> >>>>>>RDS-WHOIS2-Safeguard(a)icann.org >>>>>> >>>>>> >>>>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>>>>Content-Type: text/plain; charset="us-ascii" >>>>>Content-Transfer-Encoding: 7bit >>>>>Content-Disposition: inline >>>>>X-Microsoft-Exchange-Diagnostics: >>>>> >>>>>1;YQBPR01MB0385;27:TT8NPlVP+/IHoLBf2Ng0SLTFRHHQkQ+/HPYRgOcNmBrJlapLnNNJh7vOyeJ9Ar9/1xf8v5FIvXSMKbfqPtXpmmmfmM4eMGmhrrT6Zn9mY6XQHkQNfPtO9SZ1bFB8N0uS >>>>>X-Microsoft-Antispam-Message-Info: >>>>> >>>>>6p3YdvBEEgNI70W8+jWVUX7dHQiCDN5xLjXjwkJ0br9PDWzEj8S9GNMyetpa0xF8Kycujd3DI33zJzKtQvC0MmAIlSGIIMk5zDpXcevqmxIDPkYeErQWMzwaHUK84SBr7bC6bZiOYCPD5UnTnAb4clYyTFNECyKq88uNg5xeE7meI4VCWpZJODJhKF9BYbWPR9VnFVeB5IR16PDhW+bwRqisxOO/5Zb3VB6aAErPcw+59iRtUvv5hiZ5qRR0o0D/KQPJn5b01CpAB3Ib3aaot0MfemUmjKQjF88vz3IysP41WwihuJYZd5vUziZJqIsqYYrrAaDN+BXjIjxqIved2ktxiJtUErq1FlJN0WAfKvGOPilPKvLA+UKf9S8u/qNOsiqpjzSQU56QOUP7T8IhLaXm7JMgsTXzG4tHSpQyNTL10nGGSi0PdgB2Dc9+cT1/tNEkXjyFk4KZP7xTgvYhnyQ1tDeXwW+r+bcS4k+GlhtC7IiV5AhU9HTxmtPPLQtl >>>>> >>>>>_______________________________________________ >>>>>RDS-WHOIS2-Safeguard mailing list >>>>><mailto:RDS-WHOIS2-Safeguard@icann.org>RDS-WHOIS2-Safeguard(a)icann.org >>>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>>> >>>> >>>> >>>> >>>>_______________________________________________ >>>>RDS-WHOIS2-Safeguard mailing list >>>><mailto:RDS-WHOIS2-Safeguard@icann.org> >>>>RDS-WHOIS2-Safeguard(a)icann.org >>>> >>>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard >>> >>> >>> >>>-- >>>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: >>><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net >>> >>>Web: <http://www.key-systems.net>www.key-systems.net / >>>www.RRPproxy.net >>><http://www.domaindiscount24.com>www.domaindiscount24.com / >>> >>>www.BrandShelter.com >>> >>>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: >>> >>>www.facebook.com/KeySystems >>> >>>www.twitter.com/key_systems >>> >>>Geschäftsführer: Alexander Siffrin >>>Handelsregister Nr.: HR B 18835 - Saarbruecken >>>Umsatzsteuer ID.: DE211006534 >>> >>>Member of the KEYDRIVE GROUP >>><http://www.keydrive.lu>www.keydrive.lu >>> >>>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: >>><mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net >>> >>>Web: <http://www.key-systems.net>www.key-systems.net / >>>www.RRPproxy.net >>><http://www.domaindiscount24.com>www.domaindiscount24.com / >>> >>>www.BrandShelter.com >>> >>>Follow us on Twitter or join our fan community on Facebook and stay >>>updated: >>> >>>www.facebook.com/KeySystems >>> >>>www.twitter.com/key_systems >>> >>>CEO: Alexander Siffrin >>>Registration No.: HR B 18835 - Saarbruecken >>>V.A.T. ID.: DE211006534 >>> >>>Member of the KEYDRIVE GROUP >>><http://www.keydrive.lu>www.keydrive.lu >>> >>>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. >>> >>> >>> >>> >>> >>>Content-Type: text/plain; charset="us-ascii" >>>Content-Transfer-Encoding: 7bit >>>Content-Disposition: inline >>>X-Microsoft-Exchange-Diagnostics: >>> >>>1;YQBPR01MB0385;27:yAq1iFP/95EuszjlQeP2HEv8q8p1/oIS2khTKinG+CgA7k4JoSDJ1eg9sg328rPlJwt4U6sMKSYciajcKtNCCH6aI1TFM66565Fwe2leKb8/RHSQyMp+6eX0exubP2Zf >>>X-Microsoft-Antispam-Message-Info: >>> >>>NVdnEe4F4p+DmqCWNEOUt3rOchoVOZnV5+p5jW+04qscScrrVtn5fW24kdHWSKSM6n+Ip+ow/UgIU9RNb34Kf9lmtljibABVao70wl0+KIe96GContpGgZkVfNDCNJg0iHZWl9fGp6vTg0mLHfaLWrPlULPal5X9xAF/c/94ywBUVh39DM6PYOhI58x7GaWWKRGqFBSQ83GTl9IIbjQz4A6LrewnrPfhbToy02izDK8AbdPW+KzuYMqPp06Y9iiCfRLJw29Gdo0J8sEid6ZKUYcDSIH9ooIu5k6nSQWAcgBscy52fqM1gd4t4WkNkG0zhyh4G2m5HE5BwTgkgcLT74Xrk7UWfQobBQvU002Aly5ZcqaqdgE52+dBgES/LxE4Op9i1fFk+JemWz59601g8oE8OnL8AXCQ6NmiP3pTVfm3Zr2sQzfbuX0DPETGHzHkwhPgr6gBi54eonaxRuSjCz0YgppT3EqVTQwf6Isu+tzUN7RS+sSdIIgcotb6uNg0 >>> >>>_______________________________________________ >>>RDS-WHOIS2-Safeguard mailing list >>><mailto:RDS-WHOIS2-Safeguard@icann.org>RDS-WHOIS2-Safeguard(a)icann.org >>>https://mm.icann.org/mailman/listinfo/rds-whois2-safeguard > > >-- >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: <mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > >Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net ><http://www.domaindiscount24.com>www.domaindiscount24.com >/ www.BrandShelter.com > >Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems >www.twitter.com/key_systems > >Geschäftsführer: Alexander Siffrin >Handelsregister Nr.: HR B 18835 - Saarbruecken >Umsatzsteuer ID.: DE211006534 > >Member of the KEYDRIVE GROUP ><http://www.keydrive.lu>www.keydrive.lu > >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: <mailto:vgreimann@key-systems.net>vgreimann(a)key-systems.net > >Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net ><http://www.domaindiscount24.com>www.domaindiscount24.com >/ www.BrandShelter.com > >Follow us on Twitter or join our fan community on Facebook and stay updated: ><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems >www.twitter.com/key_systems > >CEO: Alexander Siffrin >Registration No.: HR B 18835 - Saarbruecken >V.A.T. ID.: DE211006534 > >Member of the KEYDRIVE GROUP ><http://www.keydrive.lu>www.keydrive.lu > >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. > > >

1 0

RDS Face-to-Face Meeting #2 | 16-17-18 April 2018
by Jean-Baptiste Deroulez April 13, 2018

April 13, 2018

Dear Review Team members, We look forward to seeing you in Brussels on April 16-17-18. Please find attached: - your approved meeting agenda; - slides for the meeting; - the security sheet for Brussels; - a map with metro, train and bus stations located close by the ICANN office (located 6 Rond-Point Schuman 1040 Brussels, Belgium), and the hotel. Please note that your reading list is available on the wiki page : https://community.icann.org/x/kA_8B. Please kindly help us promote community participation for the upcoming RDS-WHOIS2 Review Team face-to-face meeting by sharing an invitation with your networks. To make it easier, we’ve provided a short bullet point to share: * Join the Second Face-to-Face Meeting of the Registration Directory Services Review Team (RDS-WHOIS2) On 16,17,18 of April, observe the RDS-WHOIS2 Review Team from 07:00 - 15:30 UTC for their second face-to-face meeting where they will discuss the subgroups' findings and potential recommendations. Click here<https://community.icann.org/display/WHO/Face+to+Face+Meeting+-+16%2C+17%2C+…> for more information. Until then, safe travels to you all. Kind regards, Jean-Baptiste

1 0

Subgroup Common Interface report
by Susan Kawaguchi April 13, 2018

April 13, 2018

Apologies for this being so late. Please see the attached report for the Common Interface Subgroup. Susan

1 0