
58:19
Question: Is this the same zoom meeting room Councilors are using? Do we get to see their chat? :-)

58:30
Yup special session Amr =)

58:32
…, oh…, and hi all. :-)

58:38
@James: Thanks.

58:42
@Amr, they use invisible font

58:57
@Maxim: Of course “they” do. How silly of me. :-)

58:58
You'll see how utterly fascinating we are, Amr :-).

59:15
@Marie: Oh…, I already know, of course. ;-)

59:16
Hello, my name is Steve Chan and I will be monitoring this chat room. There is an open mic session at the very end of this meeting for comments and questions for participants who are not Councilors.

01:00:56
Comments or questions outside the open mic session will not be read out loud. However, If you want your question read out loud, start your sentence with <QUESTION> and end it with <QUESTION>. If you want your comment read aloud, start your sentence with a <COMMENT> and end it with <COMMENT>.

01:01:06
please use only parliamentary language :)

01:01:13
Those of us who have spent years “virtually attending” welcome all who are new to this experience.

01:06:15
Full agenda can be found here: https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+11+March+2020

01:07:28
Action item list: https://community.icann.org/display/gnsocouncilmeetings/Action+Items

01:07:38
I have a note about project list PDF

01:08:46
GNSO Project List: https://gnso.icann.org/sites/default/files/file/field-file-attach/projects-list-09mar20-en.pdf

01:12:27
Where are we on the outside consultation report on the Consensus Building tools?

01:12:50
Good question, Jeff!

01:12:58
@Jeff try <QUESTION> </Question>

01:13:21
<Questions> Where are we on the outside consultation report on the Consensus Building tools?<QUestion>

01:14:29
Indeed we were (ALAC/At-Large)

01:17:53
asap :-D

01:20:07
GNSO Project list: https://gnso.icann.org/sites/default/files/file/field-file-attach/projects-list-09mar20-en.pdf

01:25:40
@Berry: in your presentation, would you please remind us of how %comp is measured (deliverables, milestones etc.). eg 81% for EPDP (not 80, not 82.. :s) Thanks.

01:26:23
@Philippe, I will talk to that when turned over to me.

01:26:34
@Phillippe I think it is the ‘sense of the progress’

01:28:30
Thanks Maxim that's the question: _81_ doesn't reflect a "sense" to me... (but maybe that's just me....)

01:29:10
blurry logics

01:32:20
<COMMENT> Now that SubPro got approval for an extension, shouldn't that now be Green for on target as opposed to at risk?</Comment>

01:32:58
@Jeff, it is still beyond pervious expectations

01:33:00
Well noted @Jeff (with my clear biase obviously)

01:33:28
@Maxim, if that is the standard, then everything would be "at risk"

01:33:34
or "in trouble"

01:33:57
@Jeff, I think it means attention

01:34:07
@jeff and cheryl - yes !

01:35:56
@Maxim - with all due respect, I don't believe SubPro needs attention or is at risk

01:37:11
@Jeff, if something slipped timelines couple of times, it is worth looking at … from the project management point of view, we are not PR agency

01:37:20
I am a fan of using GANTT chart/project Mx

01:37:48
@Cheryl , representation does not change substance

01:38:56
@Maxim - it has been looked at, we did a request for extension, it was approved, and as the 2 Co-Chairs believe we are on target, that should be controlling. We are "not at risk".

01:39:09
Thanks Berry. Very clear, forgot about EPDP trailblazing the application of PDP3.0

01:39:25
indeed @Keff

01:39:35
@Jeff, I think it is a good point of view, but the manager of the PDPs is the Council , not PDP WG

01:40:00
We are * Well Aware* of that @Maxim...

01:40:12
let's agree to disagree on this at this stage

01:40:12
so I hope it is updated to at least yellow

01:40:28
@Maxim - and what is the basis when the 2 co-chairs and the Council Liaison are of the same view which is different than yours

01:41:09
@Jeff, definetely, that is why I think it might not be need to be red, but not necessary green, probably yellow

01:41:34
this PDF is internal Council document

01:42:55
@Berry - maybe light blue for the items in hands of the Board?

01:44:35
We will move to a review of each project next...and shortly.

01:44:45
with RPMs there was a delay caused by one of the members

01:47:21
A couple of the PDPs have had issues

01:48:22
There is a qualitative as well as a quantitative element to assessing progress and issues. Both need to be taken into account.

01:49:13
I think it is more about deliverables and milestones (about %)

01:49:21
Thank you Tom. qualitative vs. quantitative was what I was trying to say earlier.

01:51:39
Cool sounds like Im not too far off the mark then good work

01:51:54
RACI Matrix = Responsible, Accountable, Consulted, and Informed

01:52:31
Or it could be the unrated director’s cut of Keanu Reeves’ greatest movie.

01:52:50
Thanks Greg, sorry got caught up in project management speak there =)

01:53:12
targeting and execution ? thanks

01:53:38
@Greg: A Walk in the Clouds?

01:54:03
I was impressed @James. I’ve been saying there’s not enough Project Mgmt expertise in the ICANN ecosystem....

01:54:39
Been suggesting a PMP approach since 2015 =) https://www.icann.org/en/system/files/files/report-comments-aoc-org-reviews-13jul15-en.pdf

01:55:05
@Amr, I was thinking of Bill & Ted’s Excellent Adventure, but okay.

01:55:23
(Also that makes me feel old now 5 years ago)

01:55:24
@Greg: Oh…, you win!! :-)

01:57:28
https://forum.icann.org/lists/comments-proposed-aoc-org-reviews-process-15may15/pdfRH97TBOsi7.pdf Detailed comments on Program Management approach here for those interested

01:57:56
Sorry about audio issues…

01:59:08
@James, if you want to feel old, consider that The Matrix came out over 20 years ago and Bill & Ted came out over 30 years ago (and for @Amr, A Walk in the Clouds came out 25 years ago).

01:59:29
@James, ICANN org is currently evaluating its approach to project/program management as well as CRM.

02:00:08
Council comment on icann budget asking for FTE PgM and PM in addition to tools

02:00:20
Excellent Mary, super happy to hear that, please let folks know I have been commenting on this for many years so if I can be of help please pass my name along.

02:00:29
it looks to be JUst Do it TM approach

02:00:58
@James , CRM can not replace need in actual work

02:01:21
Correct, but it can help with capacity planning and management for sure.

02:02:27
we can not use enterprise approach and kill stale projects firing people … so not necessary

02:03:02
We could fire up stale project killing people...

02:03:06
Note this procedure is also identified in the Rec 27 Wave 1 Report

02:03:17
Thanks Marika

02:03:47
@James, thank you, will do! And yes, improving our PM & CRM approach is in service to facilitating effective and efficient community work, not a replacement.

02:06:44
“wave” being used interchangeably with “phase”?

02:07:20
Or is wave 1 of the EPDP something other than phase 1?

02:07:22
When is the call for volunteers going out for the IGOs - any idea?

02:07:22
wave is more about shell-shock after the blast [phase]

02:07:26
@amr no “wave" is more used for the Rec 27 context :)

02:07:40
Ah…, ok. Thanks, Rafik.

02:08:05
There will be a Wave 2 report for other consensus policies impacted from the EPDP-P1.

02:08:52
@Keith, is chair for RPMs 2 a work for SSC?

02:10:01
I guess it should

02:10:05
Music to my ears Berry =)

02:10:15
Aren't we generally asking a WG to choose its Chair?

02:10:32
toothpick tossed?

02:10:52
Marie: we didn't for the EPDP

02:11:13
but the EPDP is of course special in many ways

02:11:21
@marie for that work track, council will do the selection as indicated in the charter.

02:11:41
@Marie, EPDP Chairs were chosen by the Council leaership with the help of SSC

02:11:48
Sure - but yes, difference. Don't think we specified that in the IGO charter?

02:11:52
more consultaion of SSC

02:12:10
Ah - sorry Rafik, missed that. Thanks!

02:12:19
Or actually use SSC for what it is there for? :)

02:13:00
@Julf, it was during my term

02:13:26
in SSC

02:13:41
Much better audio Marika

02:13:42
@maxim indeed

02:14:19
@Marie - the GNSO WG Guidelines foresee that “Unless a Chair has already been named by the Chartering Organization, normally a Chair will be selected at the first meeting of the WG.” So it is within the remit of the Council to appoint to Chair should it decide too, like it did for the EPDP.

02:16:15
in RPMs the pace changed to better than it was (personal opinion as a member of that WG)

02:16:48
+1, Maxim.

02:17:52
@Keith: We are on track for 18 March, at which point the status will change.

02:19:00
Also I was remiss to not mention a huge thanks to staff that worked hard to keep the RPM WG on track during three intense meetings.

02:19:11
Nothing from me

02:19:14
whatgoodlookslike.com is for sale for $5500.00

02:19:24
@Greg, no ads

02:19:47
Re RPM WG - really good to hear all the positive developments.

02:20:01
I’m not selling, @Maxim. Must be Keith.

02:20:17
whatgoodlookslike.ie only 5.99 =)

02:20:45
Who filled this in

02:21:21
Shouldn't the Co-Chairs be consulted on this?

02:21:34
Council should

02:21:42
@Steve - I completely disagree with these determinations

02:22:42
the counsultation should be with the GNSO Leadership

02:22:46
I think the term is *consulting at all* @Steve ;-)

02:23:36
We are surprised if Flip is seeing this condition but so be it...

02:26:46
RySG delivered the rating of the issues

02:27:56
In order to provide some more context to this list, it may be worth trying to quantify what the possible impact is of not addressing the issue?

02:30:57
<comment> That’s not true - RrSG polled its members

02:31:08
RySG represents more that 3 councillorsm it was opinion of members

02:31:10
@Marika That is a very helpful suggestion

02:31:13
So did IPC

02:31:20
RySG used poll

02:31:51
RySG+RrSG = 90% of CPH

02:32:04
And 95%+ of domain registrations

02:34:09
The RrSG polled its members on this

02:34:12
As did other groups

02:34:28
We also polled our members just for the record.

02:34:31
To say that the “vote” only reflects the input of the councillors is simply not true

02:34:43
We represent our SGs + Cs

02:34:49
We channel their views

02:36:13
At least for RySG, RrSG and CSG. NCSG councillors are not bound, although sometimes guided.

02:36:31
NCAs also not bound.

02:40:03
As Rubens has suggested, sometimes NCSG is a wee bit misguided…..

02:40:23
(That was supposed to be a joke, in case anyone is wondering)

02:40:54
Stephanie, every family has a problem child... ;-)

02:41:25
Audio problem

02:41:28
I'll pass

02:41:31
Yes, in the NCSG we fight over that role a lot....

02:41:32
Thx

02:41:49
<QUESTION> To Rafik’s point, is there a reason why IRD is not on this list at all? Not even at the bottom? <QUESTION>

02:42:33
IRD?

02:43:15
The phase 1 final report also stated that requirements regarding data accuracy are not affected by any of the phase 1 recommendations.

02:43:48
“EPDP Team Recommendation #4.The EPDP Team recommends that requirements related to the accuracy of registration data under the current ICANN contracts and consensus policies shall not be affected by this policy.”

02:43:52
@Amr - What is the open item on IRD? The expert report was forwarded to the RDS PDP WG, as per the letter. it was just input provided to the RDS PDP WG, no specific policy issues were identified, as far as I recall. If there are specific issues that the Council should consider, it would be good to frame these up?

02:44:09
I strongly support what Keith is saying about accuracy. I do not recall including it as a topic in scoping the Charter.

02:44:10
@Pam: Thanks. :-)

02:44:27
We should note that GDPR definition of accuracy is data subject-centric, not 3rd-party-centric.

02:44:28
No worries, @Amr

02:44:53
Accuracy is vital and is being debated by the legal team in the EPDP, including asking Bird & Bird more questions.

02:44:57
@Marika: There were 3 high-level policy issues identified by the IRD-EWG.

02:45:04
So we need to keep GDPR definition and ICANN-sphere definition apart and reflect which one we are talking about.

02:45:13
Precisely Rubens, and trust me I have pointed that out so many times my head is getting flat from hammering against the wall...

02:45:18
@Marika: 1. Registrants should only be required to input registration data in a language(s) or script(s) with which they are skilled.2. A Registry must be able to accept and store any language or script that might reasonably be expected to be used in its target market.3. Unless explicitly stated otherwise, all data elements should be tagged with the language(s) and script(s) in use, and this information should always be available with the data element.

02:45:28
I’ve invited Amr to the April meeting to discuss the open IRD topics (Marika its on the google doc if u want to see the background mail from Amr)

02:45:35
Aplogies for the audio issue. For the record, re prioritisation, the ISPCP identified two areas of importance to them: a) structural/PM reform: PDP 3.0 and evolution of the MS model and b) the follow-up on IDN scoping

02:45:43
Accuracy has continuously been brought up by the GAC, including he European Commission.

02:45:50
Note that some issues were deferred from phase 1 to phase 2, although for this one it did not specifically mention phase 2 but “is expected to be considered further”.

02:45:57
Bird & Bird has given answers on this,

02:46:27
The EPDP's questions on accuracy are very narrow,

02:46:27
If some people are still getting confused about the term “vote” and “views” I used, please don’t get me wrong, I was only tackling the statistic validity of the survey, but The chair corrected that it was not a binding survey. So all is clear.

02:46:32
Both accuracies might be important... but they are like water and oil.

02:47:47
I am told that many - most? - of the legal team did agree that these questions should be addressed, Taya,

02:47:57
GDPR-wise, if I type "Mickey Mouse" as the registrant, it's accurate. If someone changes to "Donald Duck", no longer accurate.

02:48:10
Rubens - exactly

02:48:17
Correct Rubens

02:48:19
Nice example

02:48:23
@James / @Amr - are you proposing to commence a PDP on that topic or does it belong in one of the ongoing efforts? I would need to refresh my mind, but I recall that the Board passed the report on to the Council which passed it on to the RDS PDP WG which did not produce any recommendations in response.

02:48:44
There are only a few minutes left on the call? When will the floor open up to non-councilors to offer comments?

02:48:52
8

02:48:57
And neither Mickey Mouse or Donald Duck is the real person registering the domain, so it fails ICANN-accuracy.

02:49:02
data accuracy is not relevant for our work

02:49:05
This accuracy issue is a classic case of a Review team’s recommendations being dropped into a pdp in my opinion…..there was undue focus on accuracy in the WHOIS review team 2 exercise.

02:49:08
@Marika: I’d say it needs to stay on the Council’s radar for a future PDP.

02:49:21
it is already regulated in the RAA sufficiently

02:49:22
@Rubens, people can change IDs to those names

02:49:25
Thanks but disagree: if it's outside the scope, why was it mentioned in the Phase 1 report?

02:49:46
Not of course to imply that accuracy did not exist as a priority for data requestors forever

02:49:56
@Maxim, in some jurisdictions, yes. In mine it would put me in trouble.

02:50:11
Noting Marie's disagreement for the record.

02:50:50
Unless I get a court order to change my name, which will likely not happen with those examples.

02:51:00
Thanks Keith - given the comments above, better make that "noting the BC's disagreement". We've polled/asked/discussed/delete as appropriate...

02:51:16
Right, thanks Marie.

02:51:39
surprise surprise

02:51:53
@volker kinder surprise :)

02:52:46
quite a bit of side chatter

02:53:25
that is a Flag for action

02:53:25
Do I understand it right that Jeff is asking for escalation?

02:53:40
No Maxim not at all

02:53:42
for formal reasons

02:53:59
It did trigger the action. That was the PCR the PDP just went through.

02:54:11
no not at all Maxim

02:54:13
then it should be there is not need for escalation, because the PDP is back on track

02:54:17
@Jeff, maybe there are even worse categories that would trigger escalation.

02:54:26
he is asking if our PDP *is* Ät-Risk"what does that mean to our work and in PD Action

02:54:37
please paint it yellow

02:54:38
The PDP3.0 contain definition of the Status / Health. There is also a change procedure.

02:55:13
PDP3.0 Final Report.

02:55:18
@Berry - THe request is approved, yet it is still labeled at yellow

02:55:22
and so we will expect that action to occur now Berry …

02:55:28
which means it should have further escalation, right?

02:55:37
4 Years, 8 previous date changes.

02:55:43
FOr the record, I disagree completely with the designation

02:55:44
“In trouble” should include rushing ahead and ignoring buried land mines, in my opinion. Making progress is great, parking difficult issues in order to get ahead is buying trouble. Those charts are excellent, I am sure Berry has a code in there somewhere for these buried treasures, but I missed it…

02:55:54
Please check PDP 3.0 Final Report page 100 about the meaning of the various status/condition: http://go.icann.org/pdp3dot0

02:56:06
@Ariel - of course I have read it

02:56:12
The procedure here, is PDP leadership should work with support staff and liaison to discuss what the codes should be.

02:56:18
“Dumpster Fire” or “Clown Show” status levels will trigger escalation.

02:56:19
but something is broken

02:56:34
If there is disagreement, the Liaison should take it back to the Council.....as managers of the process.

02:56:39
That's the escalation.

02:56:47
He is NOT alone in that @Keith

02:56:51
Its not the color...it should have meaning

02:57:00
that's all, it should trigger action

02:57:11
and I would love suggestions as to what we can do better

02:57:12
I like the in scope part best

02:57:26
we have arranged to follow up with Flip on Monday so we *WILL* get back to you

02:57:49
Yes and Flip does not agree

02:58:43
Thanks Flip. But Again I don't want to make this about the color. I want to make sure that when something has a status, it has meaning and triggers action

02:58:48
Also some local laws might have penalties for misrepresenting one's identity.

02:59:07
GDPR states: Personal data shall be: … rate and, where necessary, kept up to date; every reasonable step must be taken to ensure that personal data that are inaccurate, having regard to the purposes for which they are processed, are erased or rectified without delay (‘accuracy’). (Art. 5).

02:59:07
It's in the Temp Spec, Amr.

02:59:13
The GDPR does not define the word ‘accurate’. However, the Data Protection Act 2018 does say that ‘inaccurate’ means “incorrect or misleading as to any matter of fact”.

02:59:45
Sorry above quote from GDPR was cut off at the beginning… “Personal data shall be … accurate and, where necessary….."

03:00:09
Data Protection Act 2018 is UK, not EU.

03:00:35
UK is not there anymore

03:00:35
It’s just an example of how to interpret… I can probably find other examples if not doing it on the fly

03:00:36
So, it's applicable to UK registrants.

03:00:58
TempSpec was in response to GDPR

03:01:34
Temp Spec was used to scope EPDP

03:01:42
And Temp Spec includes accuracy.

03:01:55
@Marie, not ICANN Accuracy

03:02:01
Amr said it like it is

03:02:27
context, Greg, context.

03:02:32
Temp Spec 4.1, 4.3, 4.4.2 and Appendix C all reference accuracy.

03:02:40
Bye for n0w

03:02:41
Thank you all

03:02:45
thanks all!

03:02:45
Thanks all. Bye.

03:02:45
Thanks. Bye all.

03:02:45
Thank you all. Thanks staff!

03:02:45
Thanks all

03:02:46
thanks all , good night

03:02:51
Slan!