[NCSG-PC] Fwd: [council] For your review - EPDP Initiation Request and EPDP Team Charter Templates

Thu Jun 14 12:01:27 EEST 2018

Hi,

Le jeu. 14 juin 2018 à 17:56, Arsène Tungali <arsenebaguma at gmail.com> a
écrit :

> 2018-06-14 10:17 UTC+02:00, Rafik Dammak <rafik.dammak at gmail.com>:
> > Hi ,
> >
>
> I AGREE. Maybe have Chair and co-chair from the community and have the
> facilitator as the 3rd person in leadership (from outside).
>

my proposal was to have the facilitator and/or mediator as resource to be
called when needed, they are not part of leadership

>
> > There is also the idea of legal counsel we should introduce more in the
> > discussion. that is important to be agreed in term of resourcing.
>
> Is this position of legal councel be considered as part of the
> leadership and be permanent? Or just someone we can look up to when
> needed?
>

 no legal counsel is a resource not a leaderhsip. based on CWG/CCWG
experiences, they are only called when there is agreement on what to ask
them for advices (for budgeting reasons) .

>
>
> > for board, 1 liaison will be enough as board wll organize its work via a
> > board caucus and monitor the discussion. we need to be careful about the
> > number as we also want to keep representation from SO/AC to 1 and so
> > keeping the overall EPDP team size small.
>
> Have we ever agreed on the number of reps per SG here? I still think
> we need at least 2 members per SG. One of the reasons is a back up but
> also, two members can discuss a point of view and agree rather than
> having the point of view of one. That's my opinion.
>

we discussed that and I think we have agreement among us that 3 per SG is
ok for us.

Best,

Rafik

>
>
> > Best,
> >
> > Rafik
> >
> > Le jeu. 14 juin 2018 à 16:47, Ayden Férdeline <icann at ferdeline.com> a
> > écrit :
> >
> >> Initial thoughts on EPDP leadership:
> >>
> >> 1 chair (from community)
> >> 1 vice chair (external facilitator / mediator)
> >> no more than that
> >> leadership not counted as part of the stakeholder group appointees
> (3/SG)
> >>
> >> but I can be persuaded otherwise... happy to hear other options.
> >>
> >> Best wishes, Ayden
> >>
> >>
> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >> On 14 June 2018 4:39 AM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> other than the standard language in template in certain sections that is
> >> found usually in other charters, we are not supposed to be constrained
> >> and
> >> the council as drafting team will have to discuss them.
> >> So better as group we get to agree on some points. I think for the
> >> composition/membership we have clear position as we discussed that in
> our
> >> calls. for leadership, we need to discuss that further.
> >> for the scope, we need to go through the temporary specification
> >> including
> >> the annex, identify areas related policy to separate from
> implementation,
> >> and do a triage of what is priorirty for this EPDP from our standpoint.
> >> We
> >> will see later if there are commonalities with other groups.
> >> We can create a working document we can populate and do that in
> >> collaborative manner, not just discussing here. I understand some points
> >> about picket fence were made but we have to do our homework to identify
> >> the
> >> issues .
> >>
> >> Best,
> >>
> >> Rafik
> >>
> >>
> >> Le mer. 13 juin 2018 à 08:08, Ayden Férdeline <icann at ferdeline.com> a
> >> écrit :
> >>
> >>> For further discussion...
> >>>
> >>> Ayden
> >>>
> >>> Sent from ProtonMail Mobile
> >>>
> >>> ---------- Forwarded message ----------
> >>> From: Marika Konings<marika.konings at icann.org>
> >>> Date: On Wed, Jun 13, 2018 at 01:01
> >>> Subject: Fwd: [council] For your review - EPDP Initiation Request and
> >>> EPDP Team Charter Templates
> >>> To: council at gnso.icann.org <council at gnso.icann.org>
> >>> Cc:
> >>>
> >>> Dear All,
> >>>
> >>>
> >>>
> >>> As discussed during today’s extraordinary Council meeting, staff has
> >>> gone
> >>> ahead and prepared a template for the EPDP Initiation Request as well
> as
> >>> the EPDP Team Charter (see attached). As there is some duplication
> >>> between
> >>> the Initiation Request and the Charter, staff would like to suggest
> that
> >>> you focus your attention on the EPDP Team charter for now. Once
> elements
> >>> such as scope and team composition have been agreed on, these can then
> >>> be
> >>> lifted from the charter into the EPDP Initiation Request. Also note
> that
> >>> staff has taken the liberty to prepopulate some of the sections of the
> >>> charter to facilitate your deliberations. These entries are either
> based
> >>> on
> >>> existing charter language / practices / procedures and/or aspects that
> >>> have
> >>> come up in the context of the discussions to date, including the PDP
> 3.0
> >>> conversations. In addition, staff has flagged some items highlighted in
> >>> yellow that will require further feedback before draft language can be
> >>> added. Of course, it is up to you to edit / delete / add as you deem
> >>> appropriate. If there is anything further that staff can do to
> >>> facilitate
> >>> your deliberations and drafting, please let me know.
> >>>
> >>>
> >>>
> >>> Best regards,
> >>>
> >>>
> >>>
> >>> Marika
> >>>
> >>>
> >>>
> >>> *Marika Konings*
> >>>
> >>> *Vice President, Policy Development Support – GNSO, Internet
> Corporation
> >>> for Assigned Names and Numbers (ICANN) *
> >>>
> >>> *Email: marika.konings at icann.org <marika.konings at icann.org>  *
> >>>
> >>>
> >>>
> >>> *Follow the GNSO via Twitter @ICANN_GNSO*
> >>>
> >>> *Find out more about the GNSO by taking our interactive courses
> >>> <http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer
> >>> pages
> >>> <
> http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers
> >.
> >>> *
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> NCSG-PC mailing list
> >>> NCSG-PC at lists.ncsg.is
> >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >>>
> >>
> >>
> >
>
>
> --
> ------------------------
> **Arsène Tungali* <http://about.me/ArseneTungali>*
> Co-Founder & Executive Director, *Rudi international
> <http://www.rudiinternational.org>*,
> CEO,* Smart Services Sarl <https://www.smart-kitoko.com/>*, *Mabingwa
> Forum
> <http://www.mabingwa-forum.com>*
> Tel: +243 993810967
> GPG: 523644A0
> *Goma, Democratic Republic of Congo*
>
> 2015 Mandela Washington Felllow
> <
> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html
> >
> (YALI) - ISOC Ambassador (IGF Brazil
> <
> http://www.internetsociety.org/what-we-do/education-and-leadership-programmes/next-generation-leaders/igf-ambassadors-programme/Past-Ambassadors
> >
> & Mexico
> <
> http://www.internetsociety.org/what-we-do/education-and-leadership-programmes/next-generation-leaders/Current-Ambassadors
> >)
> - AFRISIG 2016 <http://afrisig.org/afrisig-2016/class-of-2016/> - Blogger
> <http://tungali.blogspot.com> - ICANN's GNSO Council
> <https://gnso.icann.org/en/about/gnso-council.htm> Member. AFRINIC Fellow
> (
> Mauritius
> <http://www.afrinic.net/en/library/news/1907-afrinic-25-fellowship-winners
> >)*
> - *IGFSA Member <http://www.igfsa.org/> - Internet Governance - Internet
> Freedom.
>
> Check the *2016 State of Internet Freedom in DRC* report (English
> <http://cipesa.org/?wpfb_dl=234>) and (French
> <http://cipesa.org/?wpfb_dl=242>)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20180614/eeaba4fb/attachment.htm>