Hello !

Good morning all

Hi observers!

@Keith +1. Hope you're all safe and keeping safe

Agenda for this meeting: https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+16+April+2020

Project list: https://gnso.icann.org/en/council/project

Action Items: https://community.icann.org/display/gnsocouncilmeetings/Action+Items

Hello all, sorry I’m late.

Welcome Osvaldo!

I’m attending way more webinars than ever

I’m attending way more webinars than ever

Zoom is doing OK

Reminder to councilors: please send your chat comments to All panelists and all attendees

I know who decides to mow there lawn 8:30am on a Thursday?

soundproof helmets with headsets might be needed these times

My next door neighbour has painted his house

he’s bored

One of my neighbours is 8 and learning the flute. I get Christmas medleys.

But she also plays Scotland the Brave. :insert heart emoticon*

@John, there’s always a massive burst of mowing energy (no matter what time of day) when the first glimpse of spring visits my little corner of New England suburbia-verging-on-country … i.e. this week.

@Marie That’s braw!

Here we have a lot of power (jet) washing of balconies and back terraces.

@John, there’s always a massive burst of mowing energy (no matter what time of day) when the first glimpse of spring visits my little corner of New England suburbia-verging-on-country … i.e. it’s the main event this week.

My new AirPod Pros with noise cancellation have worked nicely

Overall traffic across IXPs is up quite a bit

Yes this is not working from home, this is working during a pandemic.

Absolutely it is unsuprisingly, and trafic is on the increase wihtin the ISPs as well.

BE ISPs have all increased data (etc) for all users, for free. (Thanks ISPs!)

Although I should have mentioned that we now see the (unfortunate) difference bw rural areas where we have xDSL (at best) and FTTH covered areas.

Apologies for being late!

design attempts to save money will be more visible now (small IPS especially )

it is certainly visible here (although I realise I somewhat biaised :P )

Apologies for being late!

Most of our staff have good broadband, but some live in areas where their choices are limited / non-existent

Here in Jamaica the ISPs are not holding up. Lockdown was imposed on a conurbation west of Kingston from 5a yesterday Wed 15 April until 5a 22 April. Largely a bedroom community so traffic has spiked. Bandwidth like a yo-yo so y'all fade every now and again.

Welcome Erika!

We always stated that was our worst case date

That’s correct - it was a worse case scenario

audio is a bit choppy

+1

But surely all of this work for inaccurate data...?

definition of ICANN accuracy is not equal to GDPR accuracy

As an EPDP member, I have to agree with Rafik

Agree John - on the BC list we've seen a number of members fighting COVID-related DNS abuse.

devoting more time to deliver less might be a bad strategy

More time so we can do more to stop abuse - not just to chat.

In CPH many if not all members are fighting abuse (also types appeared recently)

It's not making it longer for no reason, it's to ensure time to discuss all items as defined in the charter.

@Marie, more accurate data does not and will not stop abuse.

One concern is the issues of data accuracy and legal/natural are not quick or easy topics.

Of course they're not Keith - that's why they need to be addressed properly.

Legal vs natural was debated to death in the PPSAI

the discussions went absolutely nowhere

Are there other ways forward on accuracy issues other than the already fully-loaded EPDP? RDAP? Compliance?

if it is not doable then adding deadlock items kills the process

exactly Maxim

@Tom, the draft work plan is proposing a scoping team on accuracy

@Pam - surely more accurate data would allow all of us (the goods actors) to stop abuse more effectively, and rapidly?

@Michele, riffing on process, I think the one on Transfer Policy is the poster boy. It seems to me the problem is well defined. Where I come from a good problem definition always project the solution; one set of fellas say the data delivered on a transfer is problematic and could be more so with Temp Spec and GDPR. We know what those are. So, why not just make an alignment adjustment and solve the problem? So now, here we are, contemplating a PDP to take 2 years to solution. Gotta be a better way.

@Marie, but removing ability to use it (via delay in implementation) will not

The bad guys can easily fill out perfectly accurate data when they register a domain name.

formally if bad guys are using real life data of some poor guy - it might be both accurate and totally non suable

Flip: the way where it was 3-4-5 is not good, and PDP 3.0 is the answer

Data accuracy is another one. Is anybody sentient willing to argue that inaccurate data is not worth the keyboard that wrote it?

hi all, sorry for missing the first hour. Teaching schedules are mystery and misery

EPDP is almost in its 2nd year

Welcome Tatiana!

The meaning of the term “expedited” is looking a little strained - albeit for practical reasons.

Draft Work Plan: https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-framework-council-work-plan-14apr20-en.pdf

Maybe it’s a good time to remind that the European Commission started the GDPR first review … maybe there’s a way to connect topics one can’t solve now, closer in alignment with the EC process.

waiving fines would be great (in cases related to accuracy )

Hope the third year on the planning isn't 20222....

without it there is a legal liability and there is no way DPAs take into account just words of EPDP team

@phillipe why not :)

@Rafik :) Just wishful thinking I guess

we won't be there to know anyway... :s

Scoping Team Report: https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-policy-review-scoping-team-06apr20-en.pdf

Thanks Emily

Thanks Pam, & leadership for putting this on hold and defer to the next meeting. Given the circumstances, it woud have been very difficult to consult with our consistuency.

Suggested approach document: http://mm.icann.org/pipermail/council/attachments/20200324/70f17810/Wave1Rec27-Possiblenextsteps-24March2020-0001.docx

GNSO Chair election timeline: https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-council-chair-27mar20-en.pdf

Maybe we can extend Keith’s term given the COVID-19 pandemic?

hah

=)

+1 at least until it ends?

@pam we need to stress it is not a punishment :D

EPDP package is available here: https://community.icann.org/pages/viewpage.action?pageId=105388008

Can we put that doc back up on the screen?

The work plan doc

audio issues?

yup

yes

Keith - can't hear you

you're "fading away" Keith....

Too low

we barely hear you , Keith

faded

You’re faint

difficult

Very faint mic

Little quiet

it is start to yell

better

back

back

On accuracy, as we no longer have the ability to file accuracy reports (no ARS) after data is collected, ensuring accuracy when it is collected seems fundamental.

do we have a URL (beyond mail)?

for the work plan

Maxim: https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-framework-council-work-plan-14apr20-en.pdf

oh god.

@Maxim, yes, it’s the first item listed on the GNSO Drafts page here: https://gnso.icann.org/en/council/drafts

thanks

Keith, what is “core”?

@Marie +1. It is at collection point the tools and requirements needed

The feedback from our constituency was to have as few meetings as possible to not disrupt and make people feel the obligation to attend

is there meant to be something on the screen about the schedule?

@michele we don’t have anything to show yet, this should be coming shortly - next week.

ah ok

thought I was missing something :)

The Board Resolution referenced SO/AC preference for cross-community policy dialogue, topical webinars and regular WG meetings.

4 hours per day?

3 hours for plenary I understand

5am to 8am for us James a chara

A proposed 4-hour block at a time friendly to APAC/KL for the core sessions, yes.

Go h'iontach ar fad

KL time… Will keep us wonderfully awake at night here in Europe.

KL is pn UTC +8

4:00 am UTC start time 8:00 am UTC end time.

Not only Europe, but Africa and Latin America are in trouble. In terms of time zone

Thanks Michele :-)

:-)

Icann67 hours were from midnight to 7:00am :)

Rafik we sympathise.

INdeed @Rafik

audio

barely hear Keith again

I though ICANN tech support was a problem outside the “core” hours?

I wonder how ICANN tech support is gong to work on APAC time at all? and where from?

Singapore hub tech guys?

Distributed model.

@Tatiana, the biggest technical challenge for org staff is that we will not be in a central location. For ICANN67, we had techs and LS in LA. We will not have that for ICANN68 so it will be more challenging to provide interpretation, RTT etc.

And interpreters at 5 am? :)

Apologies for my audio issues, not sure what's going on.

nothing that enough coffee can resolve :p

Sorry, have eto leave now

Can we keep Council at *our* time at least?

@Tatiana, we are working through what our internal capacity is, as regards full-on tech and language services. But as Steve and I said, Policy support staff will be available for all the GNSO sessions.

+1 Marie, it would be great to keep current time

@Mary, thank you.

As the GNSO does not normally require interpreters, that is fortunately not an additional limitation for your scheduling.

Stay safe!

bye all

Bye all...

Thanks all

Thanks all

Thanks bye !

thanks all! Take care. Bye

Thanks All

Bye