
22:56
Hello all

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

23:07
It is afternoon here

23:55
afternoon here, too :)

25:12
Brian, you mean accuracy question?

25:24
Yes! thanks

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

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

26:29
Thank you. ;-)

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

28:34
Hadia - will go to you next

28:39
Great, thanks Tatiana

28:46
This is an old hand

28:51
ok

29:02
I am not able to put my hand down

29:51
@Hadia, it is showing down on our side

30:26
The participants list is frozen at my end

30:35
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?

32:29
My hand is up

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

32:45
I have some suggestions so hand up too

33:23
Sorry, I hope that was clear!

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

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

38:06
Right, I think so

38:18
It's an additional input that's not automated

42:56
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.

43:22
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?

43:49
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?

43:57
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)?

47:26
hands up

49:26
I'd like to speak to that question

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

52:37
My legal hat: agree with Thomas. :)

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

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

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

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

56:40
old hand

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

01:00:12
+1 to retaining all scenarios

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

01:02:15
Right, I wouldn't presuppose controllership

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

01:09:39
+1 Brian

01:14:10
whwere "possibility"?

01:14:23
instead of "existence" right where your mouse was

01:14:24
second line

01:14:31
bingo

01:16:01
Thanks, I think that's good

01:20:27
I think I need instruction on how to best organize C now.

01:20:44
Berry I am lost more than you!

01:20:50
I have to drop off the call-

01:21:23
So those two should go together, as new 1-2 in section C

01:22:54
thanks Matthew and Brian and all

01:23:12
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?

01:23:13
Thanks for the comments Tatiana, helpful additions

01:23:29
Thank you, Tatiana

01:23:50
Thank you to Matt too for setting all this up and drafting. Much appreciated.

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

01:24:43
Fine with me

01:25:01
Summary looks fine, thanks

01:25:25
Representative group

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

01:26:11
Thanks, Berry. Your track changes skills on the fly are impressive.

01:26:18
Agreed, thanks

01:26:51
Thx. Brian.

01:28:09
The RRSG still has issues with most the use cases

01:28:18
Do not represent EPDP consensus

01:28:26
Volker, we do have issues, too :)

01:28:34
this is why I asked!

01:28:37
thanks all

01:28:42
Great call, thanks all.

01:28:47
Thanks!

01:28:50
bye