
31:54
Please review ICANN Expected Standards of Behavior here: https://www.icann.org/resources/pages/expected-standards-2016-06-28-en**Members: reminder, when using chat, please select all panelists and attendees in order for everyone to see chat.

34:40
And now for the benefit of panellists and attendees: I like the language, Becky.

34:50
becky I have my hand

34:52
up

36:00
@Hadia we can barely hear you.

36:15
ok I shall re join

37:12
+1 Melina

37:49
This is what I wanted to say

39:36
+1 Melina’s point

40:31
So what is the merit of being so precise - just accurately describing what we want serves the purpose

41:43
@Stephan even if this is the case - whether we mention it or not has no benefit

42:13
+1 Margie

43:15
Agree to me too makes more sense

43:56
Reminder that these definitions are not the only definitions in the Google Doc.

44:41
https://docs.google.com/document/d/1vofZIqnY-xCaKMte1q_tiAwAfGwkwsu1/edit

44:58
As Becky has noted, the GDPR definitions are already captured in the terminology table.

47:26
Why are we reopening this? We have the GDPR terminology in it and use that as the basis for policy language. Exactly as it should be done

47:42
indeed, so we maintain GDPR definitions mentioned in the table and only add a line for 'emails anonymized vis-a-vis third parties"

47:52
I don't believe is misleading

47:58
On the contrary

49:54
a unique contact shall refer to the registrant not the registration

51:13
precisely. This is why I suggested deleting the B& B definitions

51:26
**Members: reminder, when using chat, please select all panelists and attendees in order for chat to be capture after the meeting.

55:33
sorry have to leave for another meeting - will go to mute / no sound mode and will try to come back

01:03:18
@ Margie: agree

01:07:15
I like: What risks remain?

01:09:12
Agree Margie

01:12:11
@Becky sorry - I was disconnected , please go ahead and rewritre the question

01:12:25
Note: Melina has to drop for another call.

01:14:33
I believe B&B stated in the prior memo that the current obligations appeared sufficient to meet the Accuracy principle

01:15:43
@Mathew this was before the new eu propsal

01:18:23
Margie, let’s deal with that then and not conflate it with a question on the adequacy of measures taken. The question to be asked here is what should be done to limit the risk of wrong self-identification and unlawful publication resulting thereof. It’s not about the data quality provided by the registrant.

01:23:34
That’s not how the B& B memo approaches accuracy

01:25:45
Just as a reminder, Becky cannot see the chat today, so I might suggest that comments be made verbally over text in the chat.

01:27:46
I am back

01:28:08
Hi melina

01:28:17
@Melina: we're on Q4 which is the one you submitted.

01:28:24
ok thanks

01:28:35
what is the debate?

01:29:34
Let’s not go KYC - the account holder would usually be the customer having the contract with the registrar.

01:31:03
Confirm - scheduled to go 30 more minutes

01:33:46
The current requirements are minimal - - email validation and formatting checks — no cross field validation or other verification

01:42:53
Yes-- I think that’s what I was lookin g for in this question

01:46:13
Thanks Keith

01:47:45
Melina and Margie - can you commit to rewriting this question by COB Friday so that the Legal Committee has time to review it prior to Tuesday’s meeting?

01:47:51
yes

01:48:07
Noted - although this question is already linked to the legal v. natural discussion we will try to further refine it

01:48:31
They are not disclosing based on consent

01:48:53
RIPE NCC is disclosing data based on 6(1)(f)

01:49:02
legitimate interest

01:49:21
RIPE NCC is relying on legitimate interest

01:49:31
With all due respect, I think the RIPE approach is questionable…

01:52:09
@Hadia, we are unable to hear you

01:52:19
Hadia, having trouble hearing you again.

01:52:30
I can’t. Hear Hadia

01:52:36
@Hadia, it sounds like your mic is very far away

01:52:42
Sorry, your arguments are lost to me

01:53:02
I am sorry no I won't be able to

01:54:30
Just because there boy next door jumps out of the window does not mean I have to...

01:56:04
RIPE-NCC states: [f]aciliaing coodinaion beeen neok operators (network problem resolution, outage notification etc.)i he one[purpose] that justifies the publication of personal data in the RIPE-NCC Daabae, and ha i i clea ha he oceing of eonal daa efeing oa resource holder is necessary for the performance of the registry function, which is carried out in the legitimate interest of the RIPE community andhe mooh oeaion of he Inene globall (and i heefoe in accodance ih Aicle 6.1.f of he GDPR)

01:56:15
the study page 51

01:56:25
???

01:57:02
Sorry I just copied and pasted a paragraph which ended up as shown

01:57:51
Page 51 of the study says that RIPE NCC relies on 6(1)(f) for the publication of the data

01:57:58
Hi all, as we approach the end of today's special call, I respectfully request that members and alternates on the Legal Committee conduct work and homework in between the scheduled meetings, over email, or in separate conversations. With very limited time for the full group's work, it's critical for this group to advance its work in a timely manner. I think good progress is being made, but we need to be more focused and efficient in our use of time. Thanks for all your work!

01:58:29
Thank you Keith, thank you everyone

01:58:32
Had, I have my doubt that the blanket balancing test would pass legal review

02:00:49
Q3 = Becky

02:00:57
Q4 = Melina + Margie

02:04:45
Ok thank you all - bye for now