[registration-issues-wg] [CPWG] [GTLD-WG] Reminder - Today by 17:00 UTC: ACTION/ALAC and CPWG Members: Statement on Evolving ICANN’s Multistakeholder Model

Carlton Samuels carlton.samuels at gmail.com
Sun Jun 9 19:16:37 UTC 2019


+1 to Holly's, especially wrt Board representation.

I'm afraid board membership in context of an American corporation in
general and a California public benefit corporation in particular,  is
hardly understood.

-Carlton

==============================
*Carlton A Samuels*

*Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround*
=============================


On Sat, Jun 8, 2019 at 2:27 AM Holly Raiche <h.raiche at internode.on.net>
wrote:

> Hi Marita
>
> I do have to agree with Bastiaan on this one.  Both Alan and Hadia have
> put in enormous time and effort on the EPDP and our viewpoints have been
> heard, if not necessarily agreed with.  I am not convinced that having more
> people on the EPDP would make any difference to being heard - but I bow to
> both Alan and Hadia’s opinion on that.  On Board representation, at the end
> of the day, once you are a member of any Board, you are just that - a Board
> member - NOT a representative of anything.  Yes, you bring a particular
> perspective to the Board,.  But that is all any Board member should do.  If
> ALAC is to sway  decisions of the Board, it will be done by us as ALAC
> members arguing well; it will not be done by a Board member (or two)
> arguing the ALAC case on the Board
>
> Holly
>
> > On Jun 6, 2019, at 10:57 PM, Bastiaan Goslings <
> bastiaan.goslings at ams-ix.net> wrote:
> >
> > Thanks, Marita - you have not misunderstood my point, and I see the
> challenge here when trying to strike a balance. I very much respect and
> appreciate your efforts.
> >
> > If we think 'The issues themselves, the things that need fixing, have
> mostly already been identified’ then fine. My comment was purely based on
> the text we are now working on - and just in case, I do not feel the issues
> are sufficiently substantiated in the other At-Large doc (from 2012?)
> either that is being referred to. And that we can therefore cannot
> convincingly conclude, again based on the text as is, that there is an
> imbalance of power. And that e.g. we should be able to appoint more
> boardmembers or that there is an unfair lack of At-Large representation in
> the EPDP.
> >
> > cheers
> > Bastiaan
> >
> >
> >
> >> On 6 Jun 2019, at 14:39, Marita Moll <mmoll at ca.inter.net> wrote:
> >>
> >> Bastiaan -- thanks for your comments. I don't want to agree or disagree
> with anything you are saying but I have to point out that this request for
> comment specifically asked that we give examples of where and how these
> issues affected us. There are probably many examples, but these stood out.
> This part of the process is looking for concrete examples of things that
> need fixing. The issues themselves, the things that need fixing, have
> mostly already been identified.
> >>
> >> So, the fact that we have only one seat on a board of 16 -- ccNSO and
> GNSO both have two (we did not add that detail) --  EPDP representation is
> worse - are examples of imbalance. This way we substantiate the "power
> imbalance"statement with respect to the identified issue of roles and
> responsibilities.
> >>
> >> There are many in our group who feel the comment is not aggressive
> enough. Our team was just trying to strike a balance.
> >>
> >> I hope I haven't misunderstood your point.
> >>
> >> Marita
> >>
> >> On 6/6/2019 4:34 AM, Jonathan Zuck wrote:
> >>> Agree we shouldn't just assert things, especially without showing
> consequences. We need to get the conversation going, not end it prematurely
> >>>
> >>> Jonathan Zuck
> >>> Executive Director
> >>> Innovators Network Foundation
> >>> www.Innovatorsnetwork.org
> >>>
> >>> From: GTLD-WG <gtld-wg-bounces at atlarge-lists.icann.org> on behalf of
> Bastiaan Goslings <bastiaan.goslings at ams-ix.net>
> >>> Sent: Thursday, June 6, 2019 12:50:45 AM
> >>> To: ICANN At-Large Staff
> >>> Cc: Bartlett Morgan; Joanna Kulesza; cpwg at icann.org
> >>> Subject: Re: [GTLD-WG] [CPWG] Reminder - Today by 17:00 UTC:
> ACTION/ALAC and CPWG Members: Statement on Evolving ICANN’s
> Multistakeholder Model
> >>>
> >>> All,
> >>>
> >>> Thanks for the efforts that have been put into drafting the statement.
> >>>
> >>> I understand that we’re finalising our contribution, although we still
> have a week before the deadline. I just want to note for the record that,
> following comments during yesterday’s call that ALAC/At-Large should not
> only be more forceful in conveying its message but should also be as
> ’S.M.A.R.T.’ as possible when doing so (both of which I agree with), text
> like the one on page 4:
> >>>
> >>> 'What we have currently is an unbalanced multistakeholder model in
> which some parties have far more power than others. For an example of how
> our community is affected, At-Large works in the best interests of more
> than 4 billionend users on the Internet, but has only one seat on the ICANN
> Board. We have also been underrepresented in the current EPDP, which may
> well carry through to other applications of the “PDP 3.0” model’
> >>>
> >>> in my opinion is quite ‘aggressive’ however it lacks substantiation.
> Both when it comes to the ‘some parties have far more power than others’
> and the ‘examples’ that follow. Without stating an opinion whether I agree
> or not, I think that making these bold type of statements while not being
> S.M.A.R.T. and rational in our argumentation, brings a risk that our
> suggestions are not taken on board and into consideration. And can have an
> undesired effect on how the At-Large, as the representative of end-users,
> is perceived as a serious counterpart in deliberations within an ICANN
> governance context.
> >>>
> >>> thanks
> >>> Bastiaan
> >>>
> >>>
> >>>
> >>>
> >>> ***  Please note that this communication is confidential, legally
> privileged, and subject to a disclaimer:
> https://www.ams-ix.net/ams/email-disclaimer  ***
> >>>
> >>>
> >>>
> >>>> On 3 Jun 2019, at 08:59, ICANN At-Large Staff <
> staff at atlarge.icann.org> wrote:
> >>>>
> >>>> Dear All,
> >>>>
> >>>> A kind reminder to please make final comments on the ALAC Statement
> on Evolving ICANN’s Multistakeholder Model today, Monday, June 03 by 17:00
> UTC.
> >>>>
> >>>> Please make any final comments, if needed, by edits on the Word Doc
> (attached), comments to the At-Large workspace, or by replying to
> staff/Evin.
> >>>>
> >>>> Thank you,
> >>>>
> >>>> ICANN Policy Staff in support of the At-Large Community
> >>>> Website: atlarge.icann.org
> >>>> Facebook: facebook.com/icannatlarge
> >>>> Twitter: @ICANNAtLarge
> >>>>
> >>>>
> >>>> From: Evin Erdogdu <evin.erdogdu at icann.org> on behalf of ICANN
> At-Large Staff <staff at atlarge.icann.org>
> >>>> Date: Sunday, June 2, 2019 at 2:43 PM
> >>>> To: Maureen Hilyard <maureen.hilyard at gmail.com>, John Laprise <
> jlaprise at gmail.com>, Tijani BEN JEMAA <tijani.benjemaa at topnet.tn>,
> Sebastien Bachollet <sebicann at bachollet.fr>, Ricardo Holmquist <
> rihogris at gmail.com>, Marita Moll <mmoll at ca.inter.net>, Javier Rua <
> javrua at gmail.com>, Bartlett Morgan<bartlett.morgan at gmail.com>, Humberto
> Carrasco <hcarrascob at gmail.com>, Joanna Kulesza <joannakulesza at gmail.com>,
> Bastiaan Goslings <bastiaan.goslings at ams-ix.net>, Holly Raiche <
> h.raiche at internode.on.net>, Kan Kaili <kankaili at gmail.com>, Seun Ojedeji <
> seun.ojedeji at gmail.com>, Hadia Abdelsalam Mokhtar EL miniawi <
> Hadia at tra.gov.eg>, "cpwg at icann.org" <cpwg at icann.org>
> >>>> Cc: ICANN At-Large Staff <staff at atlarge.icann.org>, Evin Erdogdu <
> evin.erdogdu at icann.org>
> >>>> Subject: ACTION/ALAC and CPWG Members by 03 June 17:00 UTC: Statement
> on Evolving ICANN’s Multistakeholder Model
> >>>>
> >>>> Dear ALAC and CPWG Members,
> >>>>
> >>>> The Google Doc has been closed for the ALAC Statement on Evolving
> ICANN’s Multistakeholder Model, and the final draft of the version is
> attached in Word for final comment by Monday, June 03 at 17:00 UTC.
> >>>>
> >>>> Please make any final comments, if needed, by edits on the Word Doc
> (attached), comments to the At-Large workspace, or by replying to
> staff/Evin.
> >>>>
> >>>> Kind Regards,
> >>>>
> >>>> ICANN Policy Staff in support of the At-Large Community
> >>>> Website: atlarge.icann.org
> >>>> Facebook: facebook.com/icannatlarge
> >>>> Twitter: @ICANNAtLarge
> >>>>
> >>>> <ALAC Statement on Evolving ICANN’s Multistakeholder Model.docx>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> CPWG mailing list
> >>>
> >>> CPWG at icann.org
> >>> https://mm.icann.org/mailman/listinfo/cpwg
> >>>
> >>>
> >>> _______________________________________________
> >>> 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.
> >
> > _______________________________________________
> > CPWG mailing list
> > CPWG at icann.org
> > https://mm.icann.org/mailman/listinfo/cpwg
> >
> > _______________________________________________
> > 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.
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> 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.
> _______________________________________________
> registration-issues-wg mailing list
> registration-issues-wg at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/registration-issues-wg
>
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/registration-issues-wg/attachments/20190609/5ad9a736/attachment-0001.html>
-------------- next part --------------
_______________________________________________
CPWG mailing list
CPWG at icann.org
https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________
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.


More information about the registration-issues-wg mailing list