[NCSG-PC] Fwd: [council] Update: Optional Meeting with GAC on IGO CRP

Tue Jun 25 18:08:44 EEST 2019

Elsa, you have my support to jump to action in a united front if we have one. 

Best,

Martín

From: NCSG-PC <ncsg-pc-bounces at lists.ncsg.is> on behalf of Elsa S <elsa.saade at gmail.com>
Date: Tuesday, June 25, 2019 at 4:00 PM
To: Arsène Tungali <arsenebaguma at gmail.com>
Cc: ncsg-pc <ncsg-pc at lists.ncsg.is>
Subject: Re: [NCSG-PC] Fwd: [council] Update: Optional Meeting with GAC on IGO CRP

Hi Arsene,

We’ve been reactive most times. Proactivity could help in a way.

My two cents.

E.

—

On Tue, Jun 25, 2019 at 10:48 AM Arsène Tungali <arsenebaguma at gmail.com> wrote:

Elsa, i think for now, let’s follow the conversation closely and use every opportunity to not miss any of these conversations.

As Rafik said yesterday, there is nothing we can do for now. But with this new agreement, let’s make sure we are part of the drafting team that will be tasked to scope this new WG and get our members ready to be represented there

Sent from my iPhone

On 25 Jun 2019, at 15:01, Elsa S <elsa.saade at gmail.com> wrote:

This GAC situation has been very frustrating and I’ve been extremely vocal already about it in several of our meetings. Can we make a decision about our stance on this ASAP? What do we think is best for this WG? Maybe we should consult with our members too about the situation?

I know we’ve talked about it on several of our policy calls, and we’ve already discussed this several times, but we haven’t made a decision on a pathway forward. Any thoughts?

Best,

Elsa

—

On Tue, Jun 25, 2019 at 9:48 AM Arsène Tungali <arsenebaguma at gmail.com> wrote:

Hi all,

I am sure this will not be new for Council members but here is what
was pushed by the Council and was able to get from this small meeting:

-       Recommendations 1-4 are in Board hands and no one knows what will be
the outcome or their decision: it is either rejection (sent back to
Council) or adoption and then it becomes a consensus policy. We should
not focus on this now.

-       GAC seems to not be happy with what has been done so far (Rec #1 to
#4) and I think they would give everything they can to have a say on
these or even see the Board bring them back to Council for discussion.

-       Agreed on chartering a new group to work on Rec #5, under the
umbrella of RPMs WG, but with its full autonomy.

-       With the experience of the EPDP in terms of WG composition, timeline
as well as the flexibility and liability that comes with the PDP 3.0,
GNSO Council should be able to lead this work.

-       This new group should be formed of people with the right expertise
and interest in the topic. Should be limited in number and be
time-bound to deliver in a timely fashion. NCSG should start thinking
about who we will send there.

-       Start a small group to keep on discussing: formed with GAC members,
interested IGOs and Council members, including Paul who is Council
liaison to RPMs WG. When this is formed, NCSG needs to be there as
well.

This is purely procedural, I cannot report on the substance of the
work done and what needs to be done since I am not following this WG
closely.

@Avri was in the room (from the Board side), maybe you can say something?

Thanks,
Arsene

2019-06-24 12:19 UTC+02:00, Arsène Tungali <arsenebaguma at gmail.com>:
> Hi Rafik,
>
> I hate that I did not follow closely this discussion but since we need
> someone to be there, I am planning to join and will let you know
> anything I get from that informal meeting.
>
> Thanks,
> Arsene
>
> 2019-06-24 10:37 UTC+02:00, Rafik Dammak <rafik.dammak at gmail.com>:
>> Hi all,
>>
>> as I mentioned before I won't be able to attend that session as I will be
>> chairing EPDP sessions.
>> can someone volunteer who won't be at EPDP or another PDP session to
>> attend
>> and take notes. while it is about informal discussion, we need to note
>> what
>> was discussed and suggested there.
>> the latest letter from the board is not bad with regard about following
>> process by having the public comment for input and not initiating any
>> facilitated dialogue yet.
>>
>> Best,
>>
>> Rafik
>>
>>
>> ---------- Forwarded message ---------
>> De : Drazek, Keith via council <council at gnso.icann.org>
>> Date: lun. 24 juin 2019 à 08:50
>> Subject: [council] Update: Optional Meeting with GAC on IGO CRP
>> To: council at gnso.icann.org <council at gnso.icann.org>
>> Cc: gnso-secs at icann.org <gnso-secs at icann.org>
>>
>>
>> Hi all,
>>
>>
>>
>> This is a quick update on Tuesday’s 13:30 meeting between interested
>> members of the GNSO Council and GAC on the IGO CRP topic. Thanks to those
>> of you who have volunteered to attend and contribute to this optional
>> session.
>>
>>
>>
>> As you’ve seen, the ICANN Board sent a letter to both groups indicating
>> they will soon be posting Recommendations 1-4 for public comment. In the
>> meantime, the Council will continue to explore next steps for
>> re-chartering
>> the RPM PDP WG to include a dedicated sub-group to consider
>> Recommendation
>> 5 and the IGO protections issue.
>>
>>
>>
>> As part of this effort, as scheduled, we will meet with interested
>> parties
>> from the GAC on Tuesday. I spoke with Manal yesterday and we agreed that
>> the session would be most productive if it was informal and focused on
>> how
>> best to ensure the dedicated sub-team is scoped appropriately. Anyone is
>> welcome to attend and observe this session, but we do not plan to record
>> it
>> and hope an informal dialogue at this time will help to inform our work.
>>
>>
>>
>> Please let me know if you have any questions or if you’d like to
>> participate as a contributor to the discussion. We will of course report
>> out on the conversation.
>>
>>
>>
>> Thanks,
>>
>> Keith
>>
>>
>>
>>
>> _______________________________________________
>> council mailing list
>> council at gnso.icann.org
>> https://mm.icann.org/mailman/listinfo/council
>>
>> _______________________________________________
>> By submitting your personal data, you consent to the processing of your
>> personal data for purposes of subscribing to this mailing list accordance
>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
>> the website Terms of Service (https://www.icann.org/privacy/tos). You can
>> visit the Mailman link above to change your membership status or
>> configuration, including unsubscribing, setting digest-style delivery or
>> disabling delivery altogether (e.g., for a vacation), and so on.
>>
>
>
> --
> ------------------------
> **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/>*,
> Tel: +243 993810967 (DRC)
> GPG: 523644A0
>
> 2015 Mandela Washington Fellow
> <
> http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html>
>
> (YALI) - ICANN GNSO Council Member
> <https://gnso.icann.org/en/about/gnso-council.htm> Member. UN IGF MAG
> <https://www.un.org/press/en/2018/pi2247.doc.htm> Member
>

-- 
------------------------
**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/>*,
Tel: +243 993810967 (DRC)
GPG: 523644A0

2015 Mandela Washington Fellow
<
http://tungali.blogspot.com/2015/06/selected-for-2015-mandela-washington.html>

(YALI) - ICANN GNSO Council Member
<https://gnso.icann.org/en/about/gnso-council.htm> Member. UN IGF MAG
<https://www.un.org/press/en/2018/pi2247.doc.htm> Member
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is
https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-- 

--

Elsa Saade
Consultant

Gulf Centre for Human Rights

Twitter: @Elsa_Saade

-- 

--

Elsa Saade
Consultant

Gulf Centre for Human Rights

Twitter: @Elsa_Saade

_______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190625/565d290f/attachment.htm>