[CPWG] [registration-issues-wg] [GTLD-WG] Haunted by Europe's GDPR, ICANN sharpens wooden stake to finally slay the Whois vampire • The Register

Wed Oct 30 14:31:05 UTC 2019

Hadia:

Thanks for the clarification.

-ed

On Wed, Oct 30, 2019 at 6:07 AM Hadia Abdelsalam Mokhtar EL miniawi <
Hadia at tra.gov.eg> wrote:

> Hi Eduardo and All,
>
>
>
> The main focus of the EPDP for gTLD registration data was never on WHOIS.
> WHOIS is a protocol deemed dead some time ago even before the GDPR came
> into effect. There was always a need for a new protocol that could address
> the deficiencies of the WHOIS protocol. When we were talking about
> complying with the GDPR while keeping the current WHOIS to the greatest
> extent possible, we were not talking about the WHOIS protocol or current
> framework but we were actually referring to the benefits of the system.
> WHOIS was only used as a term that refers to the system that deals with the
> registration data, as this is how it was known by the community. RDAP is
> the new protocol that would have replaced WHOIS in all cases with or
> without the GDPR or other similar laws coming into effect. RDAP is a more
> capable protocol that will help us keep the benefits of the system to the
> Internet community and protect the privacy of the registrants, of course if
> we can reach the right policy that can allow for this to happen.
>
>
>
> Best
>
> Hadia
>
>
>
>
>
>
>
> *From:* CPWG [mailto:cpwg-bounces at icann.org] *On Behalf Of *Michele
> Neylon - Blacknight
> *Sent:* Tuesday, October 29, 2019 6:38 PM
> *To:* sivasubramanian muthusamy; Holly Raiche
> *Cc:* CPWG
> *Subject:* Re: [CPWG] [registration-issues-wg] [GTLD-WG] Haunted by
> Europe's GDPR, ICANN sharpens wooden stake to finally slay the Whois
> vampire • The Register
>
>
>
> Whois (the protocol) is going away
>
> That ship has sailed.
>
>
>
>
>
>
>
> --
>
> Mr Michele Neylon
>
> Blacknight Solutions
>
> Hosting, Colocation & Domains
>
> https://www.blacknight.com/
>
> https://blacknight.blog/
>
> Intl. +353 (0) 59  9183072
>
> Direct Dial: +353 (0)59 9183090
>
> Personal blog: https://michele.blog/
>
> Some thoughts: https://ceo.hosting/
>
> -------------------------------
>
> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
>
> Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845
>
>
>
> *From: *registration-issues-wg <
> registration-issues-wg-bounces at atlarge-lists.icann.org> on behalf of
> sivasubramanian muthusamy <6.internet at gmail.com>
> *Date: *Tuesday 29 October 2019 at 12:01
> *To: *Holly Raiche <h.raiche at internode.on.net>
> *Cc: *CPWG <cpwg at icann.org>
> *Subject: *Re: [registration-issues-wg] [CPWG] [GTLD-WG] Haunted by
> Europe's GDPR, ICANN sharpens wooden stake to finally slay the Whois
> vampire • The Register
>
>
>
> Dear Holly,
>
>
>
> For clarity, let me rephrase it: (terminology from Spreadsheet/Sheets)
>
>
>
> 1. There is a need for RDAP and a need for whois.
>
>
>
> 2. The problem with the whois protocol as you said, was that the whois
> protocol wasn't designed for gated access. But the new protocol that is
> being designed for gated access, solves the problem.  The new protocol,
> while solving the old problem, need not create a new problem, which is that
> of making whois unworkable.
>
>
>
> The new protocol could both lock away sensitive data while keeping
> non-sensitive data open for whois queries:
>
>
>
> a) Registrant Data for Law and Order:  to allow layered access based on
> privileges (accorded as timebound or otherwise) to different
> entities/requesters to different clusters of rows/columns of data
>
> and also
>
> b) Registrant Data for All Users: allow permanent access to a central
> whois computer to non-sensitive columns/rows of data, which gets stored for
> access under the name "whois data".
>
>
>
> Sivasubramanian M
>
>
>
> On Tue, Oct 29, 2019, 2:51 PM Holly Raiche <h.raiche at internode.on.net>
> wrote:
>
> I think you mean, RDAP can be configured to provide access based on
> whatever it is configured to provide access to.  Given privacy protections
> globally, I am not sure access to all private data would be granted - not
> because it could not be provided, but because it should not be provided -
> that depends on the regulatory framework.
>
>
>
> On Oct 29, 2019, at 7:52 PM, sivasubramanian muthusamy <
> 6.internet at gmail.com> wrote:
>
>
>
> Dear Holly,
>
>
>
> The Registration data that would provide gated access (possibly to
> different layers based on the degree of authenticity or the levels of
> privilege?) could also concede blanket, open access to the whois to a
> transparent layer of Registrant data.
>
>
>
> Sivasubramanian M
>
>
>
>
>
>
>
> On Tue, Oct 29, 2019, 12:02 PM Holly Raiche <h.raiche at internode.on.net>
> wrote:
>
> Folks
>
>
>
> A bit of history. A few years ago, there was a major review of Whois.  One
> of the many issues identified was simply the term: it has been used to
> refer to the data collected (as required by the RAA), the protocol or the
> service.  In the reforms, what was clarified as the terminology - we are
> talking about registration data (the same stuff required by the RAA), or
> RDAP - the registration data protocol.  In fact the IETF developed the
> protocol - RDAP- to greatly improve the functionality of the old WHOIS
> Protocol - which, amongst other limitations, could not provide gated access
> and therefore, would not permit compliance with privacy regimes such as the
> GDPR.
>
>
>
> So the data is still that required to be collected under the RAA - it is
> now called registration data.  The RDAP can be configured to allow gated
> access to the registration data - as required under the GD
>
> PR. So same data - improved protocol.
>
>
>
> Holly
>
>
>
> On Oct 29, 2019, at 3:52 PM, sivasubramanian muthusamy <
> 6.internet at gmail.com> wrote:
>
>
>
> Why should RDAP be a replacement? Whois ought to co-exist with it's own
> purpose, whois in conformity to GDPR (in an appropriate manner), whois
> redesigned to address concerns also on the need for transparency of
> commercial webspaces to minimize perhaps the most harmful form of DNS abuse.
>
>
>
> On Tue, Oct 29, 2019, 12:01 AM Michael Palage <mike at palage.com> wrote:
>
> Eduardo,
>
>
>
> It should not.  In fact RDAP will provide great flexibility for potential
> solutions for differentiated access.
>
>
>
> Best regards,
>
>
>
> Michael
>
>
>
> *From:* GTLD-WG <gtld-wg-bounces at atlarge-lists.icann.org> *On Behalf Of *Eduardo
> Diaz
> *Sent:* Friday, October 25, 2019 12:17 PM
> *To:* Carlton Samuels <carlton.samuels at gmail.com>
> *Cc:* lac-discuss-en at atlarge-lists icann. org <
> lac-discuss-en at atlarge-lists.icann.org>; CPWG <cpwg at icann.org>; NA
> Discuss <na-discuss at atlarge-lists.icann.org>
> *Subject:* Re: [GTLD-WG] [CPWG] Haunted by Europe's GDPR, ICANN sharpens
> wooden stake to finally slay the Whois vampire • The Register
>
>
>
> Will this affect the current EPDP which its main focus has been Whois?
>
>
>
> -ed
>
>
>
> On Fri, Oct 25, 2019 at 11:37 AM Carlton Samuels <
> carlton.samuels at gmail.com> wrote:
>
> https://www.theregister.co.uk/2019/10/23/icann_kills_whois/
>
>
>
>
>
> Carlton
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
>
> --
>
> *NOTICE:* This email may contain information which is confidential and/or
> subject to legal privilege, and is intended for the use of the named
> addressee only. If you are not the intended recipient, you must not use,
> disclose or copy any part of this email. If you have received this email by
> mistake, please notify the sender and delete this message immediately.
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so
> on._______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
> On Tue, Oct 29, 2019, 12:01 AM Michael Palage <mike at palage.com> wrote:
>
> Eduardo,
>
>
>
> It should not.  In fact RDAP will provide great flexibility for potential
> solutions for differentiated access.
>
>
>
> Best regards,
>
>
>
> Michael
>
>
>
> *From:* GTLD-WG <gtld-wg-bounces at atlarge-lists.icann.org> *On Behalf Of *Eduardo
> Diaz
> *Sent:* Friday, October 25, 2019 12:17 PM
> *To:* Carlton Samuels <carlton.samuels at gmail.com>
> *Cc:* lac-discuss-en at atlarge-lists icann. org <
> lac-discuss-en at atlarge-lists.icann.org>; CPWG <cpwg at icann.org>; NA
> Discuss <na-discuss at atlarge-lists.icann.org>
> *Subject:* Re: [GTLD-WG] [CPWG] Haunted by Europe's GDPR, ICANN sharpens
> wooden stake to finally slay the Whois vampire • The Register
>
>
>
> Will this affect the current EPDP which its main focus has been Whois?
>
>
>
> -ed
>
>
>
> On Fri, Oct 25, 2019 at 11:37 AM Carlton Samuels <
> carlton.samuels at gmail.com> wrote:
>
> https://www.theregister.co.uk/2019/10/23/icann_kills_whois/
>
>
>
>
>
> Carlton
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
>
> --
>
> *NOTICE:* This email may contain information which is confidential and/or
> subject to legal privilege, and is intended for the use of the named
> addressee only. If you are not the intended recipient, you must not use,
> disclose or copy any part of this email. If you have received this email by
> mistake, please notify the sender and delete this message immediately.
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so
> on._______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so
> on._______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
>
>
>
>
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.

-- 
*NOTICE:* This email may contain information which is confidential and/or
subject to legal privilege, and is intended for the use of the named
addressee only. If you are not the intended recipient, you must not use,
disclose or copy any part of this email. If you have received this email by
mistake, please notify the sender and delete this message immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20191030/7f04dd6f/attachment-0001.html>