In my opinion SSC = can only make recommendations to GNSO Council, and definitely can = not manage GNSO process.

The current SSC process = it is a preparation of a set of suggestions for GNSO Council (and only = GNSO Council takes it into account or returns it back for fixing if = required)

on procedural side of such a hypothetical selection = of Empowered Community Administration representative from = GNSO

(currently it is Chair of GNSO = Council).

SSC members took into consideration = suggestions of James Bladel, who attended the call, so SSC will make a = note

that procedure of fast removal of = GNSO EC Admin. Rep. might be needed (without words on who is going to = develop it and how,

due to it is being quite outside of = the SSC rights and obligations))

- in case he/she does = something really bad/ not working in the community(changed jobs)/ not = supported by GNSO Council anymore.

and = procedure of fast replacement (when the current GNSO EC ADM. Rep. got = ill, broke leg or needs to be substituted, for = example

due to high load/ or most probably scheduling = conflicts with GNSO Council activities.

Also = there going to be a short simple list of qualifications, which might be = taken into account in case

when GNSO Council decides to = choose someone instead of the GNSO Chair (like understanding of Council = workflow, experience of moderation/leading of a = panel,

being able understand financial docs). All those = qualifications relevant to what Empowered Community Administration will = need to do

(for example experience in moderation derived from = necessity of moderation of = public

P.s: I finally = found the slides with the current reading of the = suggestions

(I recommended that before the SSC conducts = the poll of particular reading of the items

- SSC = members can add "other" to answers and add additional = text)

Sincerely = Yours,

Maxim Alzoba
Special projects manager,
International = Relations Department,
FAITID

m. +7 916 = 6761580(+whatsapp)
skype oldfrogger

Current UTC offset: +3.00 = (.Moscow)

On May = 31, 2017, at 21:13, Austin, Donna <Donna.Austin@neustar.biz> = wrote:

Paul, I'll check with Marika on the timing = issue.

Maxim, perhaps you can shed some light on how the SSC = intend to manage the GNSO process.

-----Original = Message-----
From: rysg-executive-committee@googlegroups.com = [mailto:rysg-executive-committee@googlegroups.com] On Behalf Of Paul = Diaz
Sent: Wednesday, May 31, 2017 8:20 AM
To: Maxim Alzoba = <m.alzoba@gmail.com>; RySG Ex Coms 2017 = <rysg-executive-committee@googlegroups.com>
Subject: [EXTERNAL] = FW: an update on SSC progress with reccomendations on Empowered = Community Administration GNSO rep. selection (mostly = procedural suggestions)

Thanks, Maxim.

Does = anyone know when the SSC will be asked to review/recommend candidates = for the ATRT3? When the Council will ratify our slate? How many will = be selected? Do we need to distinguish between members and experts? = I've raised these questions with ICANN staff. We'll need to consider our = options with the RrSG - especially since they didn't have a rep on = ATRT2

-----Original Message-----
From: Maxim Alzoba = [mailto:m.alzoba@gmail.com]
Sent: Wednesday, May 31, 2017 11:16 = AM
To: Paul Diaz <pdiaz@pir.org>
Cc: Reg Levy = <reglevy@mac.com>; Samantha Demetriou = <samantha.demetriou@fairwindspartners.com>
Subject: an update = on SSC progress with reccomendations on Empowered Community = Administration GNSO rep. selection (mostly procedural = suggestions)

Hello Paul,

I wanted to keep RySG ExCom = informed on SSC progress with recommendations on Empowered Community = Administration GNSO rep. selection processes e.t.c.

Sorry = for my brevity (I am on PTO).

This confcall was quite = productive,
we had a good conversation with James Bladel(Current EC = Adm. Rep. from GNSO) and I think that SSC delivers what was requested by = GNSO Council on time (prior to 19th Jun 2017).

Also I = attached slides we discussed. Most probably SSC will have a poll with = the same questions and additional fields for suggestions (Frederic = and Poncelet were not able to attend on the call).

Sincerely = Yours,

Maxim Alzoba
Special projects manager,
International = Relations Department,
FAITID

m. +7 916 = 6761580(+whatsapp)
skype oldfrogger

Current UTC offset: +3.00 = (.Moscow)

=3D=3D=3D

SSC 31 may 2017, 17.00 = MSK
=3D=3D=3D
GNSO Standing Selection Committee meeting on = Wednesday 31 May at 14.00 UTC for 60 minutes

Apologies: = Fr=C3=A9d=C3=A9ric Guillemaut, Marika Konings (staff)

On Audio = only:

Agenda wiki page: = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__community.icann.org= _x_5yPwAw&d=3DDwIFaQ&c=3DMOptNlVtIETeDALC_lULrw&r=3D4A3LwUUER9= _CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=3DW1CaeaEVVNTsVWeYKYGX-qGJ-TVXZzki= GOuYIQvLLKk&s=3DSsBz0mjAAidzytoONvHX3SoIhOKYxp6IsMzahNrF324&e=3D&n= bsp;

Audio Passcode: SSC

Agenda:
1. Roll Call = / SOI
2. = Exchange of views with the current representative to the = Empowered Community Administration (James Bladel, GNSO Chair)
3. Review of = questions and possible responses in view of possible poll
4. Schedule = of upcoming calls
5. AOB
=3D=3D=3D
GNSO Standing = Selection Committee meeting on Wednesday 31 May at 14.00 = UTC

notes:

1. Roll Call / SOI
- SSC members: = Susan, Maxim, Julf, Lori, Osvaldo, Renata
- Guest: James Bladel
- = Apologies: Frederik, Marika (staff)

2. Exchange = of views with the current representative to the Empowered Community = Administration (James Bladel, GNSO Chair)
- What have you done so = far? What will be required from the role?
- This committee has yet to = define criteria and make selection, therefore James is interim = representative.
- Experiences so far are limited in brief. The = EC Admin was quiet for some time, and is still feeling out its processes = and operations, particularly routine items like reviewing budget or = nominations to the Board of Directors. These are items that the EC Admin = has a role in managing.
- Bigger functions as part of EC = accountability mechanisms - these will not be used regularly if at = all.
- Most participants are Chairs or similar designation of SOs or = ACs. All agree that they are mouthpieces of their community, and don't = have the ability to act independently unless instructed by their = communities.
- Qualifications - someone who understands the role. It = is not to be a member of an "uber board or council." They are speaking = on behalf of the entire GNSO community and do not act unless = authorized to do so.
- At this stage, it should be someone who can = think down the road as processes are developed and set.
- Someone who = gets along well with byzantine processes. The role needs to be = approached carefully and be sure to take a step back when something = needs further input from GNSO.
- Time committment - = initially zero, but has picked up moving towards ICANN59, developing = processes. The time committment will likely drop again. Even at the = worst case, this is not likely a significant burden - at most an hour or = two a week. It's almost entirely email. There will be one session = at ICANN59, because of proposed revision to the Bylaws. Anyone = coming from the GNSO should have perfect attendance.
- = Currently all EC reps are Chairs of their communities. Will that = continue with other SOs and ACs?
- Presume that they have considered = this to be a function of the Chair. They have bolted this role to the = Chair role. There is not currently any indication otherwise.
- = Would it make sense to appoint an alternate?
- The GNSO might want to = designate an ad hoc alternate. May not need a standing alternate. More = important would be the process around what happens if the person = changes jobs, leaves ICANN, or does something out of order.
- = For example the Chairs and Vice-Chairs could quickly appoint a = substitute if need.
- If the rep was a Council member, there could be = immediate correction if the rep "went rogue." If the rep was someone = else, would there be less control or wouldn't it matter?
- = Either way is ok.
- Do we need a process for removing a person?
- = Some of this is more appropriately taken up by the GNSO Council. The SSC = should view it's role narrowly. Process for selecting applicants --> = selection of applicants. Process for handling issues with rep may = be better handled by the Council.
- Is it better to say that = such processes should be developed without providing specifics?
- = Yes, identifying gaps to fill may be helpful.
- What would James like = to see in the criteria?
- This should at minimum be someone on = Council, and perhaps Chairs and Vice-Chairs on a rotating basis.
- If = we open up the process, harder to manage the rep and requires = duplication of processes that already exist for Council (appointments, = terms, etc). Opening up the process may fuel the incorrect = impression that this something other than a microphone for the EC. By = connecting it to an existing role, the role will be more = sustainable in the long term.

Chat excerpt:
Maxim = Alzoba: Could we suggest that ICANN provides remote connection (private) = for remote participants?
Maxim Alzoba: for EC meetings
Maxim = Alzoba: since travel is not suggested Julf Helsingius: remote = connection?
Maxim Alzoba: I mean if there is a f2f EC Adm. meeting - = ans someone is not there Maxim Alzoba: during the ICANN meeting Maxim = Alzoba: I mean if there is a f2f EC Adm. meeting - ans someone is = not there Maxim Alzoba: I think we might mention that we thin that those = procedures are to be developed (not saying how and by whom) James = Bladel: +1 Maxim Maxim Alzoba: *think (sorry for typos ... sitting in = uncommon place) Julf Helsingius: James: would it be too much = workload if we simply had the GNSO chair perform this function?
Lori = Schulman: I think that first test will be budget review

- In = response to Julf's question about time committment, no, as things = currently stand, it would not be too much work for the Chair to take = on.
- Is there any sort of coordination or reporting that goes = to the community more generally?
- There is a website being set up = where the mailing lists, discussions, reports, will be published. The = representative could come back to the Council or GNSO to relay a = request from the EC. In the other direct, if an SG wants the EC to = consider, for example, an issue with the budget, they would raise = it with Council, which would instruct the rep how to = proceed.
- Would it be in the scope of this role to develop = comms plan?
- No, this role is just to develop criteria for selecting = the rep and then selecting the rep. While we might want to point to = procedures that need to be developed, the GNSO will develop those = processes and procedures.

Chat excerpt:
Maxim Alzoba: my = question for James: it is not just time consumption, but also scheduling = conflicts (with GNSO Council activities), could we ask James if he = is sure that there is not going to be an overlap (so during the ICANN = meeting ,ICANN always provides EC Adm with the non-conflicting slots, so = Chair can be there) Maxim Alzoba: *about the burden of being GNSO = EC rep.
Lori Schulman: Thanks, I heard James supporting the narrow = task of identifying candidates but I agree about sending notes of some = issues that we have considered that may be out of scope for this = group but in scope for another group Lori Schulman: Maxim's point about = time overlaps is a good one Maxim Alzoba: if such slots can not be = granted ... then standby Rep should be in place Julf Helsingius: james = pointed out that scheduling is done by doodle Lori Schulman: = Excellent point Maxim.
Lori Schulman: and there are still = conflicts

3. Review of questions and possible = responses in view of possible poll

Chat excerpt:
Maxim Alzoba: = I have a suggestion for page 2: Term and Renewal - that the person = is still affiliated with/supported by GNSO Council or at = least affiliated with GNSO (for example - member of NCSG, RrSG = e.t.c).
Lori Schulman: is Heather the alternate? [if James is not = available] Lori Schulman: I think that finding out if there is an = "official" alternate would be helpful so we understand what is = acutally happening Maxim Alzoba: issue of Term will be resolved via = "fast removal" procedure we might suggets to invent Julf = Helsingius: Current arrangement is temporary in any case

- = Suggestion - maybe outgoing or former Chair (one to two terms) would be = a good candidate -- understands how the system works but has more = time.
- Suggestion: poll of choices provided plus an additional = field to write in responses.
- Any additional questions or possible = answers to add to the poll?
- Suggestion -- if there is a quick = mechanism for replacement, perhaps term is less important to focus = on.
- Suggestion - Make the leadership team of the Council the = default for serving as rep. Leave it to them to decide which one serves = and which one stands in as alternate.

Chat = excerpt:
Julf Helsingius: I like "anyone in the leadership = team"
Maxim Alzoba: I think that scheduling conflicts usually happen = at moments of high load, like right prior to Fin Plan discussions = deadline e.t.c Julf Helsingius: "anyone in the leadership team" = avoids us having to come up with new procedures Maxim Alzoba: @Julf, do = you think we might add " with approval of GNSO Chair, and if not = possible for natural reasions - by GNSO Council) ?
Julf Helsingius: = Sure!

- Add as one option in the poll -- SSC recommends to use = GNSO leadership as a pool for EC Admin reps. The leadership team decides = among themselves who is rep, alternate, etc.
Lori Schulman: = agree with Maxim. SSC nominates Lori Schulman: not = chooses

4.= Schedule of upcoming calls
- Suggestion to keep = Wednesday at 14:00 UTC.

5. AOB
ACTION ITEM: Ask James = about RDS Review Team.

=3D=3D=3D CHAT = =3D=3D=3D
Michelle DeSmyter: Welcome to the GNSO Standing Selection = Committee meeting on Wednesday 31 May at 14.00 UTC

Michelle = DeSmyter: Agenda wiki page: = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__community.icann.org= _x_5yPwAw&d=3DDwIFaQ&c=3DMOptNlVtIETeDALC_lULrw&r=3D4A3LwUUER9= _CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=3DW1CaeaEVVNTsVWeYKYGX-qGJ-TVXZzki= GOuYIQvLLKk&s=3DSsBz0mjAAidzytoONvHX3SoIhOKYxp6IsMzahNrF324&e=3D&n= bsp;

Michelle DeSmyter: HI there Maxim!!

Michelle = DeSmyter: Yes

Maxim Alzoba: quality issues?

Maxim Alzoba: = good

Maxim Alzoba: I have a suggestion for page 2:Term and = Renewal - that the person is still affiliated with GNSO Council or = at least with GNSO

Emily Barabas: Great. I will add to the notes = and we can discuss when we get to that agenda item.

Maxim Alzoba: = Please add to my suggestion (afiliated/supported by) , so in case where = the person was approved by the GNSO Council and formally have = no current affiliation, the Council can still use the services of = the person

Maxim Alzoba: and the ending - or at least = affiliatedwith GNSO

Julf Helsingius: Not sure of how "affiliated = with GNSO" is defined/interpreted

Maxim Alzoba: My thinking was = to show that the person still have some degree of connection with = GNSO

James Bladel: Thanks! Connecting = audio.....

Maxim Alzoba: for example - member of NCSG, RrSG = e.t.c

Maxim Alzoba: Hello James

Lori Schulman: Hi Folks. = I should be on more regularly now that INTA Annual Meeting is = over.

Maxim Alzoba: Hi Lori

Osvaldo Novoa: Hello all, = sorry I am a bit late

Julf Helsingius: I was going to ask the = same

Emily Barabas: :)

Emily Barabas: Thanks = James

Maxim Alzoba: Could we suggest that ICANN provides remote = connection (private) for remote participants?

Maxim Alzoba: for = EC meetings

Maxim Alzoba: since travel is not = suggested

Julf Helsingius: remote connection?

Maxim = Alzoba: I mean if there is a f2f EC Adm. meeting - ans someone is not = there

Maxim Alzoba: during the ICANN meeting

Julf = Helsingius: Ok, thanks for the clarification

Julf Helsingius: You = can never be sure about a cat....

Susan Kawaguchi: especially = this cat

Renata Aquino: hi

Maxim Alzoba: I think we might = mention that we thin that those procedures are to be developed (not = saying how and by whom)

James Bladel: +1 Maxim

Maxim = Alzoba: *think (sorry for typos ... sitting in uncommon = place)

Julf Helsingius: James: would it be too much workload if = we simply had the GNSO chair perform this function?

Lori = Schulman: I think that first test will be budget review

Renata = Aquino: thanks

Emily Barabas: Thanks for joining, = James

Maxim Alzoba: my question for James: it is not just time = consumption, but also scheduling conflicts (with GNSO Council = activities), could we ask James if he is sure that there is not = going to be an overlap (so during the ICANN meeting ,ICANN always = provides EC Adm with the non-conflicting slots, so Chair can be = there)

Maxim Alzoba: *about the burden of being GNSO EC = rep.

Lori Schulman: Thanks, I heard James supporting the narrow = task of identifying candidates but I agree about sending notes of some = issues that we have considered that may be out of scope for this = group but in scope for another group

Lori Schulman: Maxim's point = about time overlaps is a good one

Maxim Alzoba: if such slots can = not be granted ... then standby Rep should be in place

Julf = Helsingius: james pointed out that scheduling is done by = doodle

Lori Schulman: Excellent point Maxim.

Lori = Schulman: and there are still conflicts

Maxim Alzoba: be back in = a minute

Maxim Alzoba: back

Lori Schulman: is Heather the = alternate?

Julf Helsingius: I pretty much asked that

Maxim = Alzoba: I suggest we need voices of all members - so we could discuss = the list, but will need a poll (preferrably choices and - "other answer" = with suggestion in the text field)

Maxim Alzoba: *the = current list of questions in PDF

Emily Barabas: Staff can = certainly set up a poll if the group would like to do that

Julf = Helsingius: I support keeping things simple

Emily Barabas: @Lori, = I'm not sure if there is an official standing alternate, but I will find = out.

Lori Schulman: Sorry Julf, my recall is failing me today and = I apologize for repeating the question

Julf Helsingius: Lori: no = prob, it wasn't entirely clear

Lori Schulman: I think that = finding out if there is an "official" alternate would be helpful so we = understand what is acutally happening

Maxim Alzoba: issue of Term = will be resolved via "fast removal" procedure we might suggets to = invent

Julf Helsingius: Current arrangement is temporary in any = case

Julf Helsingius: I like "anyone in the leadership = team"

Maxim Alzoba: I think that scheduling conflicts usually = happen at moments of high load, like right prior to Fin Plan discussions = deadline e.t.c

Julf Helsingius: "anyone in the leadership team" = avoids us having to come up with new procedures

Maxim Alzoba: = @Julf, du you think we might add " with approval of GNSO Chair, and if = not possible for natural reasions - by GNSO Council) ?

Maxim = Alzoba: *do

Julf Helsingius: Sure!

Maxim Alzoba: I = am not sure "SSC selects GNSO leaders" is correct ... I thought is was = more like "recommends to use GNSO leadership as an pool for EC = ADM reps"

Lori Schulman: agree with Maxim. SSC = nominates

Lori Schulman: not chooses

Maxim Alzoba: Thanks = all, see you next time

Lori Schulman: how do we handle members = who are nominated to other teams?

Lori Schulman: = thanks

Maxim Alzoba: @Lori, I think they usually step down for a = moment

Julf Helsingius: Thank you = all!

=3D=3D=3D

--
You received = this message because you are subscribed to the Google Groups "2017 RySG = Executive Committee" group.
To unsubscribe from this group and stop = receiving emails from it, send an email to = rysg-executive-committee+unsubscribe@googlegroups.com.
To post to = this group, send email to = rysg-executive-committee@googlegroups.com.
To view this discussion on = the web visit = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__groups.google.com_d= _msgid_rysg-2Dexecutive-2Dcommittee_BY1PR10MB04549046725C2B03B87D7FF0A3F10= -2540BY1PR10MB0454.namprd10.prod.outlook.com&d=3DDwIFaQ&c=3DMOptNl= VtIETeDALC_lULrw&r=3D4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m= =3DW1CaeaEVVNTsVWeYKYGX-qGJ-TVXZzkiGOuYIQvLLKk&s=3DAf05_hbkP-c_1LDWJdM= qBjUCTMztnHJrggakCz4ti60&e=3D .
For more options, visit = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__groups.google.com_d= _optout&d=3DDwIFaQ&c=3DMOptNlVtIETeDALC_lULrw&r=3D4A3LwUUER9_C= ePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=3DW1CaeaEVVNTsVWeYKYGX-qGJ-TVXZzkiGO= uYIQvLLKk&s=3Dur-sPqKXj9R7lvw26WxMlsFDJ8I-tnjwW6h-J3Z7lx4&e=3D = .