[Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

Mon Jan 28 03:14:38 UTC 2019

Apologies to not have thought about this earlier, but perhaps we can also suggest to the Budget SMEs from the various entities that they take this back for their discussion/inclusion in their comments on Op/Strat/Budget public comments, as this is about both implications for public policy development and larger issues across ICANN.

I think that the discussion has been helpful and informative, so let me just say I appreciate that the discussion has taken place.

I could also support having a statement that the discussion has taken place.  I believe that I recall that in 2018 public comments on the Budget, this issue about transparency and thoroughness of reporting did come up.

At one point the bios of the SSAC were also publicly posted.  I think that being aware of the "credentials" of those appointed to such groups -- and I include those appointed to voting positions in CCWGs, can only help to strengthen the community's trust in ICANN and the capabilities and expertise of such entities.

________________________________
From: Gnso-sc-budget <gnso-sc-budget-bounces at icann.org> on behalf of Ayden F¨¦rdeline <icann at ferdeline.com>
Sent: Wednesday, January 23, 2019 6:52 PM
To: Stephanie Perrin
Cc: gnso-sc-budget at icann.org
Subject: Re: [Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

Hi all,

Thanks for the lively discussion.

I remember that we had this conversation on our mailing list several months back, and at that time found guidance from a government body in the EU on how/why under data protection law one agency had justified publishing the expense reports of civil servants and elected members. I wonder whom we can direct this information to, internally within ICANN?

I share the sentiment that these community travel reports should be published with the same detail as used to be the case, but am not sure we need to add this request to our comment on the FY20 budget. Is there a way we can escalate this request internally informally, or do we need to write a letter?

Ayden

©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Wednesday, January 23, 2019 5:44 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca<mailto:stephanie.perrin at mail.utoronto.ca>> wrote:

On the travel issue, I totally agree.  While it is well known that some folks get more expensive travel for medical reasons, and there is certainly a concern about releasing information about medical conditions, I do think that a lump some and the destination and departure point is still valid.  It is certainly released in most countries which have access to information and privacy legislation, even with details of items charged.

Consent could be obtained, it is reasonable to ask for it and not too burdensome to block if people insist on their privacy.  However, I would caution that if only a few people refuse, we will still be able to sleuth them out because of the dates and amounts...which raises issues about having to black out a few others to avoid this.

Stephanie Perirn

On 2019-01-23 17:10, Michele Neylon - Blacknight wrote:

Marilyn

On travel support ¨C I agree. There needs to be transparency. While I am a strong supporter of privacy and GDPR travel support is like a grant or bursary. It¡¯s important to see who is getting what and what they are actually doing. Yes, some people do plenty of work and I have no issue with them getting financial assistance, but the disclosure helps to keep the system honest.

Regards

Michele

--

Mr Michele Neylon

Blacknight Solutions

Hosting, Colocation & Domains

https://www.blacknight.com/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blacknight.com%2F&data=02%7C01%7C%7C4c0ecf65bdf745bbaf2d08d6818df7cc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838844075534361&sdata=ywGH4VS3Faqtn9maSS1Qf7tvClbma2v356%2FSXx25i1w%3D&reserved=0>

http://blacknight.blog/<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblacknight.blog%2F&data=02%7C01%7C%7C4c0ecf65bdf745bbaf2d08d6818df7cc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838844075534361&sdata=lqwr%2FDHbWrlcvGEZIQmvNW3Am5GIEcW52WCfctZWDTg%3D&reserved=0>

Intl. +353 (0) 59  9183072

Direct Dial: +353 (0)59 9183090

Personal blog: https://michele.blog/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmichele.blog%2F&data=02%7C01%7C%7C4c0ecf65bdf745bbaf2d08d6818df7cc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838844075534361&sdata=AyJXYg3Qwrx%2B%2FJmP41ngS03SELcIg0Lu4NUgXwmik68%3D&reserved=0>

Some thoughts: https://ceo.hosting/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fceo.hosting%2F&data=02%7C01%7C%7C4c0ecf65bdf745bbaf2d08d6818df7cc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838844075534361&sdata=40qC7RE50xfk2kJSKmY45CGWrTYhsInhZjg4MMCHBuM%3D&reserved=0>

-------------------------------

Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty

Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845

From: Gnso-sc-budget <gnso-sc-budget-bounces at icann.org><mailto:gnso-sc-budget-bounces at icann.org> on behalf of Marilyn Cade <marilynscade at hotmail.com><mailto:marilynscade at hotmail.com>
Date: Tuesday 22 January 2019 at 06:33
To: "gnso-sc-budget at icann.org"<mailto:gnso-sc-budget at icann.org> <gnso-sc-budget at icann.org><mailto:gnso-sc-budget at icann.org>, Ayden F¨¦rdeline <icann at ferdeline.com><mailto:icann at ferdeline.com>
Subject: Re: [Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

I have a couple of questions --

First bullet under the chart -- and this may be my fault for not thinking of it earlier. Should this include also regular Board/Liaison travel to ICANN's 3 meetings, so there is a full view of Board/Liaison travel?

Also, in a last few months, ICANN has stopped publishing travel amounts for travelers, noting GDRP as their excuse.  There has been a little chatter but not enough, in my view. If one accepts ICANN funding, then we should tick the box, so to speak, that one understands that name; group affiliated with;  travel location from, and amount of travel  and purpose will be posted in ICANN reports about said event.  Receiving ICANN funding is not a bad thing, as many volunteers do countless hours of work. But publishing details can help to advise on improvements in travel planning. And how those funded contribute to policy engagement -- in the GNSO but also elsewhere as well as to activity that ensure ICANN's successful delivery of its core mission.

This may need referral to the constituencies/SGs,as it might exceed our group's mandate in some aspects.

If we might be over exceeding the mandate of this group then perhaps some questions need to be referred back to the Constituencies/SGs into the overall Budget/Operating Plan comments. For instance, publishing all contracts over a certain amount and noting if they are competed and what the scope of responsibility of said contractor may be out of scope for the Council's comments but belong back at the broader Budget Working Group, where many of the SMEs to this group engage. Those related to policy support are relevant to this group's mandate, of course.

I have forwarded a request to Jimson Olufuye, V..Chair of Finance and Ops for BC and Steve DelBianco, V.Chair, Policy Coordination regarding their view about the Document Drafting and Development Pilot.  I understand that we have a deadline on our response, but it would also be helpful to hear from the other participants in that pilot on whether it was useful, and if not, why not.

I am so appreciative of the great work of this group and want to once again complement Ayden as Chair and Berry as staff, who have guided the work, and I believe we are also helping as the SMEs are then able to share Council's views back into their communities, as they fulfill their broader role in comments on Budget and Ops Plan.

________________________________

From: Gnso-sc-budget <gnso-sc-budget-bounces at icann.org><mailto:gnso-sc-budget-bounces at icann.org> on behalf of Ayden F¨¦rdeline <icann at ferdeline.com><mailto:icann at ferdeline.com>
Sent: Monday, January 21, 2019 11:07 AM
To: gnso-sc-budget at icann.org<mailto:gnso-sc-budget at icann.org>
Subject: [Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

Hi all,

Thank you for joining our call today. I have now updated our draft comment to reflect the discussion on our call as best as I could. Please find attached; and I apologize in advance if I have not accurately captured a change that you requested. We need to get a draft of our comment to the GNSO Council's mailing list by Thursday (and during the Council's meeting in Los Angeles on Thursday I would like to present our draft comment and walk the Council through it, if time permits), so can you please socialize the attached document with your SG/C and advise if you have any concerns, questions, or requested edits. It would be much appreciated if you could raise concerns within the next 24 hours so we have time to deliberate and discuss further on our list, if necessary. Thanks!

Best wishes,

Ayden

_______________________________________________
Gnso-sc-budget mailing list
Gnso-sc-budget at icann.org<mailto:Gnso-sc-budget at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-sc-budget<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-sc-budget&data=02%7C01%7C%7C4c0ecf65bdf745bbaf2d08d6818df7cc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838844075534361&sdata=yTnR89ajjA9xyISYrR0bi4OXmMr0PcuxL1eTpzHfEjk%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20190128/78e0229c/attachment-0001.html>