Hello all

No, but where most of our members are ;-)

It is afternoon here

afternoon here, too :)

Brian, you mean accuracy question?

Yes! thanks

Yes, we did send the questions as no one objected by the deadline.

It is part of scope, but decoupled from work of the SSAD to a final report.

Thank you. ;-)

I have several comments and suggestions for the questions, just heads up :) I will put my hand up later

Hadia - will go to you next

Great, thanks Tatiana

This is an old hand

ok

I am not able to put my hand down

@Hadia, it is showing down on our side

The participants list is frozen at my end

Matthew, one clarifying question concerning A (1): does the wording “this recommendation” refers to the non-binding recommendation by the Central Gateway to automate the decision to disclose the Registration Data in question?

My hand is up

Thanks, Matthew! I thought if not, then it should be reworded — but all good then

I have some suggestions so hand up too

Sorry, I hope that was clear!

https://community.icann.org/display/EOTSFGRD/EPDP+-P2+Legal+subteam

So the B&B advice sounds like a type "self-certification"?

Right, I think so

It's an additional input that's not automated

A (1). Please describe the risk of liability for the Central Gateway and Contracted Parties related to automating this recommendation, and to automating the decision to disclose personal information to a third-party.

2. Is the automated decision to disclose personal information to a third-party a decision “which produces legal effects concerning [the data subject] or similarly significantly affects him or her” within the scope of Article 22?

5. In what manner must the Controller(s) provide the registrant with information concerning the existence of automated decision-making in processing of his or her personal information? How should this information be communicated to the registrant, and what information pertaining to the automated decision-making must be communicated to the registrant in order to ensure fair and transparent processing pursuant to Article 13?

6. Does the provision of the information in the answer to question 5 by the Controller(s) affect the registrant’s right to obtain confirmation as to whether or not automated decision-making to disclose his or her personal information to a third-party has taken place, in addition to obtaining associated meaningful information as per Article 15.1(h)?

hands up

I'd like to speak to that question

Thomas, do you ever remove your legal hat? ;-)

My legal hat: agree with Thomas. :)

@Thomas I totally agree it is very difficult at this point to define the liabilities

Sorry for the legal hat thing and Berry, I try to take it off whenever I can, but it seems glued to my head :-)

Thomas, as long as that glued hat doesn’t look like a sombrero….

I would support adding that. I resisted the urge to suggest it myself, but if the group wants it, I support.

old hand

More so, they are "preliminary" and not "final" recommendations that have yet to go through a consensus call.

+1 to retaining all scenarios

I am fine with retaining all scenarios, I just did not want to reopen something I thought was already settled

Right, I wouldn't presuppose controllership

I think it is most likely ICANN will outsource that function and it might have an impact on the liability situation

+1 Brian

whwere "possibility"?

instead of "existence" right where your mouse was

second line

bingo

Thanks, I think that's good

I think I need instruction on how to best organize C now.

Berry I am lost more than you!

I have to drop off the call-

So those two should go together, as new 1-2 in section C

thanks Matthew and Brian and all

I have to join another call. Might we please add recognition that certain LEA requests require confidentiality which would preclude disclosing the request to the data subject?

Thanks for the comments Tatiana, helpful additions

Thank you, Tatiana

Thank you to Matt too for setting all this up and drafting. Much appreciated.

I can hang for a few minutes to do next agenda item

Fine with me

Summary looks fine, thanks

Representative group

I'd like for us to be able to sign off on this and send it to B&B

Thanks, Berry. Your track changes skills on the fly are impressive.

Agreed, thanks

Thx. Brian.

The RRSG still has issues with most the use cases

Do not represent EPDP consensus

Volker, we do have issues, too :)

this is why I asked!

thanks all

Great call, thanks all.

Thanks!

bye