[Gnso-epdp-team] Updated language for Recommendation #10
gtheo at xs4all.nl
Thu Jan 24 21:00:04 UTC 2019
The problem with this language is, and Alan Woods touched upon this very
subject this week.
//MUST maintain Log Files associated with the transmission of email
communications between the Registry Operator/Registrar and the
Registered Name Holder./
To what end?
For how long?
The registrar must make available some kind of communication (makes sense).
Webform or hashed email address (the latter being personal info).
But unless I am missing something here, what is the registry operator
doing here in this chain of communication? Do registry operators also
have some kind of web form? And if yes, again what is the purpose?
I must say I am puzzled about our recommendations and discussions.
It is like we keep pretending the redacting of the WHOIS never happened,
and we keep discussing how there might be an issue if such things might
become redacted or not available.
The redaction already happened with 175 registrars in the EU for
starters almost a year ago and many more registrars outside the EU.
Theo Geurts CIPP/E
Op 24-01-19 om 21:48 schreef Ayden Férdeline:
> Hi all,
> I have a question here. Could someone please explain what
> information/data elements they would reasonably expect to be contained
> within these log files? Thank you.
> Kind regards,
> Ayden Férdeline
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Thursday, January 24, 2019 3:22 PM, Marika Konings
>> <marika.konings at icann.org <mailto:marika.konings at icann.org>> wrote:
>>> Dear EPDP Team,
>>> In Toronto, we reached agreement in principle on recommendation #10
>>> but did not have time to develop language to which the team agreed.
>>> To move that discussion forward, the support team has developed the
>>> proposed language below for discussion and inclusion in the Final
>>> Report. Note that the bold language below (bullets 2 and 3) are the
>>> new additions, bullet 1 is identical to the language in the Initial
>>> Report. Please review this language with your group to ensure it
>>> aligns with the agreement that was reached. If you are of the view
>>> that it does not conform to the agreement, please:
>>> 1. Outline your concerns, focusing on how the proposed language
>>> does not reflect the principle agreement reached, and;
>>> 2. Propose edits that would address your concerns that are in line
>>> with the agreement reached.
>>> The deadline for doing so is *Monday 28 January* so that there is
>>> sufficient time to review and discuss any concerns. If no concerns
>>> are raised, this language will be incorporated into the draft Final
>>> Report for your review.
>>> Best regards,
>>> Caitlin, Berry and Marika
>>> *Recommendation #10 – Email Communication*
>>> 1) In relation to facilitating email communication between third
>>> parties and the Registered Name Holder, the EPDP Team recommends
>>> that current requirements in the Temporary Specification that
>>> specify that a Registrar MUST provide an email address or a web form
>>> to facilitate email communication with the relevant contact, but
>>> MUST NOT identify the contact email address or the contact itself,
>>> remain in place.
>>> *2) The EPDP Team recommends Registry Operators and Registrars MUST
>>> maintain Log Files associated with the transmission of email
>>> communications between the Registry Operator/Registrar and the
>>> Registered Name Holder.*
>>> *3) The EPDP notes operational difficulties having to do with
>>> contacting registered name holders through webforms (where there is
>>> no confirmation that the message sent was received) and
>>> pseudonymized email addresses (that often can be readily "hacked" to
>>> discover the identity of the addressee), and recommends the GNSO
>>> Council initiates work to develop a reliable, safe ways of
>>> contacting registrants in cases where their email cannot be displayed.*
>>> */Marika Konings/*
>>> /Vice President, Policy Development Support – GNSO, Internet
>>> Corporation for Assigned Names and Numbers (ICANN) /
>>> /Email: marika.konings at icann.org <mailto:marika.konings at icann.org> /
>>> /Follow the GNSO via Twitter @ICANN_GNSO/
>>> /Find out more about the GNSO by taking our interactive courses
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e=> and
>>> visiting the GNSO Newcomer pages
> Gnso-epdp-team mailing list
> Gnso-epdp-team at icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-epdp-team