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

FOR CONFIRMATION - BRU Wrap-up
by Alice Jansen May 4, 2018

May 4, 2018

See attached. Thanks Kind regards Alice

3 2

Reminder: REVIEW BY 25 APR - RT Agreements/Action Item(s) from Brussels Meeting
by Alice Jansen May 2, 2018

May 2, 2018

Dear Review Team Members, This is to kindly remind you that Wednesday – close of business – is the deadline for you to send any additional comments you may have on the Brussels agreements and action items. Past this deadline, the conclusions will be confirmed as final. Thanks, Kind regards Alice From: Alice Jansen <alice.jansen(a)icann.org> Date: Thursday 19 April 2018 at 14:24 To: "rds-whois2-rt(a)icann.org" <rds-whois2-rt(a)icann.org> Subject: REVIEW BY 25 APR - RT Agreements/Action Item(s) from Brussels Meeting Dear Review Team Members, Attached to this email, you will find agreements and actions items confirmed in Brussels. Action is needed from you: please review and raise any objections/concerns you may have by Wednesday, 25 April – COB. Past this deadline, conclusions will be confirmed as final. We also invite you to search for your name in the document. All action items from the meeting are included in the attached. As always, thank you for your hard work and dedication! Meeting archives can be found at: https://community.icann.org/display/WHO/Face+to+Face+Meeting+-+16%252C+17%2…. Safe travels! Kind regards Alice

5 5

REVIEW BY 25 APR - RT Agreements/Action Item(s) from Brussels Meeting
by Alice Jansen May 2, 2018

May 2, 2018

Dear Review Team Members, Attached to this email, you will find agreements and actions items confirmed in Brussels. Action is needed from you: please review and raise any objections/concerns you may have by Wednesday, 25 April – COB. Past this deadline, conclusions will be confirmed as final. We also invite you to search for your name in the document. All action items from the meeting are included in the attached. As always, thank you for your hard work and dedication! Meeting archives can be found at: https://community.icann.org/display/WHO/Face+to+Face+Meeting+-+16%252C+17%2…. Safe travels! Kind regards Alice

3 3

Krebs on Security - Security Tradeoffs Occasioned by GDPR
by Carlton Samuels April 30, 2018

April 30, 2018

An interesting read you might find useful. https://krebsonsecurity.com/2018/04/security-trade-offs-in-the-new-eu-priva… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

1 0

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 16, 2018

April 16, 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