[cc-humanrights] Human Rights and ICANN - session description

Sat Dec 6 12:14:27 UTC 2014

Hi

Thanks for the precision Olivier, not absolutely blocked but strongly discouraged, especially for new ‘discretionary’ initiatives as opposed to must-happen-somewhere SO AC meetings.  At least that’s my experience in pitching a couple NCUC workshops over the past years, we were told we needed to do Wednesday.  But maybe if there’s believed to be sufficient oomph behind this one the response would differ.  (Of course I agree about Fridays, but it seems from when you and I tried to raise that in the SOACSGC chairs’ context it is not a conversation that can be had.)

Anyway, there’s really no good solution.  Monday will inevitably get loaded with the big ticket stuff, IANA accountability new gTLD etc.  Wednesday morning presumably would be CCWG IG (have you and Rafik been in discussion with staff to ensure?) and other.  Thursday morning ALAC etc.  So alas the question is, as conflict is inevitable and there will be parts of the community that simply can’t come, which conflict would at least make it possible for the core group here to attend, and then anyone else we can get is gravy.

There might be one other option: they’re moving GAC-Board to Tuesday morning, which might mean open space late afternoon.  I’ve written to David Olive to inquire.

BD

> On Dec 5, 2014, at 2:59 PM, Olivier MJ Crepin-Leblond <ocl at gih.com> wrote:
> 
> Hello all,
> 
> it is possible to program for Monday afternoon. They frown upon it because that takes people out of the main room but the ALAC and other WGs have staged meetings on Monday afternoon with little interference. One of the problems is that by killing Fridays the week has become shorter and with the Thursday circus Thursday is now dead. With Monday risking being filled by the circus too we have Tuesday which is impossible due to Constituency day. But guess what, I'm now told some parts of Constituency day might happen on Wednesday morning too. So Wednesday afternoon? Oh now, that's GNSO wrap up.
> <sigh>
> 
> Olivier
> 
> 
> On 05/12/2014 14:41, William Drake wrote:
> > you can’t program on Monday,
>       they block it out for official stuff they think is more important.
> 
>       >
> 
>       > I’d ask for Wednesday morning.
> 
>       >
> 
>       > BD
> 
>       >
> 
>       >> On Dec 5, 2014, at 2:29 PM, Niels ten Oever
>       <niels at article19.org> <mailto:niels at article19.org> wrote:
> 
>       >>
>> Hi Rafik,
>> 
>> You're right. Tuesday is constituency day, so that is ruled out. Can
>> we do Monday afternoon 13:30 - 16:30 ?
>> 
>> I also found in the archives we agreed earlier on a three hour
>> meeting, so let's go for that.
>> 
>> Best,
>> 
>> Niels
>> 
>> 
>> Niels ten Oever
>> Head of Digital
>> 
>> Article 19
>> www.article19.org <http://www.article19.org/>
>> 
>> PGP fingerprint = 8D9F C567 BEE4 A431 56C4 678B 08B5 A0F2 636D 68E9
>> 
>> On 12/05/2014 02:17 PM, Rafik Dammak wrote:
>> >>> Hi Niels,
>> >>>
>> >>> Wednesday afternoon has the GNSO council public meeting and we had
>> >>> such conflict last time.
>> >>>
>> >>> Rafik
>> >>>
>> >>> 2014-12-05 22:07 GMT+09:00 Niels ten Oever <niels at article19.org <mailto:niels at article19.org> 
>> >>> <mailto:niels at article19.org> <mailto:niels at article19.org>>:
>> >>>
>> >>>
>> >>> On 12/04/2014 06:24 PM, Rafik wrote:
>> >>>> Hi Niels,
>> >>>
>> >>>
>> >>> Hi Rafik,
>> >>>
>> >>>> I am not senior within ICANN
>> >>>
>> >>> Well, at least more senior than me ;)
>> >>>
>> >>>> but I guess I can help for this.
>> >>>
>> >>> That's excellent. I think we agreed on a session on Wednesday 
>> >>> afternoon, as per Bills proposal. I think two hours would suffice. 
>> >>> Three hours seems a but like a an overkill (even though I know we 
>> >>> could easily fill it).
>> >>>
>> >>> What do you people think?
>> >>>
>> >>> Best,
>> >>>
>> >>> Niels
>> >>>
>> >>>> Rafik
>> >>>
>> >>>
>> >>>
>> >>>> Le 5 Dec 2014 à 02:20, Niels ten Oever <niels at article19.org <mailto:niels at article19.org>
>> >>>> <mailto:niels at article19.org> <mailto:niels at article19.org>> a écrit :
>> >>>
>> >>>> Hi all,
>> >>>
>> >>>> It seems there is consensus about the text for the session at 
>> >>>> ICANN52, or does anyone have any issues with this text? All 
>> >>>> comments are very welcome.
>> >>>
>> >>>> _________
>> >>>
>> >>>> Human right and ICANN - continuing the conversation
>> >>>
>> >>>> There is a growing recognition in parts of the community that
>> >>>> some of ICANN’s policies and other actions may have implications
>> >>>> for human rights like freedom of expression and the right to
>> >>>> privacy. While ICANN is not the place to negotiate over such
>> >>>> rights, it would be advisable on political and other grounds to
>> >>>> assess whether our work is fully consistent with internationally
>> >>>> agreed human rights laws and policies, and to identify possible
>> >>>> methods for addressing any incompatibilities.
>> >>>
>> >>>> To date, these issues have been discussed on a case by case
>> >>>> basis. This cross-community workshop will consider options for
>> >>>> starting a process that could address them in a more systemic
>> >>>> manner.
>> >>>
>> >>>> ________
>> >>>
>> >>>> What would be the process to request the room? I would be happy
>> >>>> to send some emails, but given the experiences during last ICANN 
>> >>>> meeting it might be more effective if someone more senior in the 
>> >>>> ICANN hierarchy would send it. Any takers?
>> >>>
>> >>>> Thanks in advance,
>> >>>
>> >>>> Niels
>> >>>
>> >>>
>> >>>>> _______________________________________________ cc-humanrights 
>> >>>>> mailing listcc-humanrights at icann.org <mailto:listcc-humanrights at icann.org>
>> >>>>> <mailto:cc-humanrights at icann.org> <mailto:cc-humanrights at icann.org> 
>> >>>>> https://mm.icann.org/mailman/listinfo/cc-humanrights <https://mm.icann.org/mailman/listinfo/cc-humanrights>
>> >>>
>> >>>
>> >>>
> >>
>       ___
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cc-humanrights/attachments/20141206/4254c5a5/attachment.html>