
40:19
Thanks Heather

40:36
Not me

41:09
Again - none here

44:50
That’s fine David :-)

45:17
zoom mute perplexes me

45:37
Easy to double mute :-(

45:37
i do the same -

48:47
Special IFR, yes

49:31
ok David, thanks

50:48
and I haven't seen anything on this on the GRC list

50:56
Yes, will do Heather.

51:02
lost Heather

51:08
is anyone speaking

51:15
Yes, Heather is speaking

51:24
I will have to dial back in - sorry

51:25
David you may need to rejoin.

55:33
Practical exampe is super helpful, Julie - good thinking

58:44
Yes, we have received a request to hold a Community Action Forum in Montreal.

59:14
@Mary - just to confirm, the request received relates to teh ccNSO's fundamental bylaw change?

59:22
yes

59:49
thanks - good we don't have anything else brewing. I agree with David that this is a good one to experiment on.

01:00:21
An Approval Action Community Forum can be held 30 days after the Board approval, if so requested by the EC Admin.

01:00:42
And if it’s at the next scheduled ICANN meeting - hence the request for Montreal.

01:00:56
Understood, Mary -thanks

01:05:29
Right Heather, so we should make it “Representative to the EC Admin”

01:06:24
I don’t have the details about the document in question, but that sounds eminently sensible to me, including Julie’s suggestion.

01:06:39
Let's come back to it when Maxim is on the call

01:07:15
I think it depends on the role this person is being asked to play in the document in question - is it the role of the GNSO Chair or of the GNSO rep to the ECA (who may or may not happen to be the GNSO Chair)?

01:09:10
excellent

01:09:14
When we send the next draft we can call out that change to see if there are comments (say from Maxim)

01:11:31
Here’s the link to the document if you want to scroll yourselves: https://docs.google.com/document/d/1tR6YeATOl-_6ig7XKKluR3jwY8cLPYKoLCB-t6GhVNc/edit?usp=sharingAOB

01:12:04
Yes

01:12:08
Los Angeles.

01:12:17
Annex D, Bylaws.

01:12:32
Understood - good to know

01:14:08
Bylaws again :)

01:14:46
Hmmm... I'm sure Steve D would put me right here

01:16:52
California Corp Code requires a Secretary and yes, in ICANN’s case it’s our GC (JJ).

01:21:06
i havew a comment on 4.2

01:21:10
Could also say, “matter under consideration”?

01:22:57
Looks good Heather

01:25:23
I understand that if Forum 1 isn't sufficient to discuss in full, there could be more

01:25:31
Additional Forums can be held at discretion of Board or ECA

01:25:47
But if Board, Julie is correct - needs rationale. And Bylaws say “one or two” Forums.

01:25:59
As long as ECA has the power to do this, that's good

01:26:05
And yes, must be “during the Approval Action Community Forum Period"

01:27:00
Yes, correct, Heather. All this starts with the triggering of the EC’s Approval Action power.

01:28:01
Yes - in that case, the period will be longer than 30 days.

01:28:48
hand up

01:28:57
i have timing comment in 4.3 also

01:30:58
Correct - 21 days

01:31:02
that’s right David

01:31:09
So we’ll need to check the timing

01:31:46
Very helpful point David

01:34:30
“occurs”?

01:34:46
“If such a consultation occurs”?

01:34:50
Are you saying “should” consult or “must” consult?

01:35:00
+1 occurs

01:36:15
Staff might need to put in a little timing chart?

01:36:41
T minus etc.

01:36:46
counting back

01:37:44
I think we can be flexible — it’s not Bylaws timing — but we need to account for the 21 days.

01:38:37
A Decisional Participant is “deemed to have abstained” if it doesn’t inform the ECA of a decision.

01:38:59
that’s why a timing chart would help

01:39:07
;-)

01:39:14
Basically, you have flexibility WITHIN the 21 days, but not ABOUT the 21-day limit.

01:39:21
exactly Mary

01:41:04
Correct, David.

01:42:18
And yes, the Bylaws does speak of approval thresholds from the Decisional Participants - basically, combination of support plus non-objection. So abstentions matter.

01:42:26
Thank you all for joining and thanks Heather for sharing!

01:42:34
Chairing LOL
Zoom would like to update your account settings. When joining a meeting or webinar by entering a meeting ID, participants will be required to enter a password. Participants joining using a meeting invite link will not be required to enter a password. Learn More
This change will be effective on . If approved or declined, the change will take effect immediately.