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

Thu Jan 24 13:57:35 UTC 2019

Thanks, Stephanie.

Helpful.

M
________________________________
From: Stephanie Perrin <stephanie.perrin at mail.utoronto.ca>
Sent: Wednesday, January 23, 2019 7:52 PM
To: Marilyn Cade; Tom Barrett
Cc: gnso-sc-budget at icann.org
Subject: Re: [Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

By "sleuth them out"  I simply meant that if you know that 100 individuals were at a given meeting, and you can find travel disclosures for 90 of them, you may be able to figure out who spent what among the remainder, making of course broad assumptions about who accepts travel support, and who might not.  This then is a privacy violation.  You have to not be able to identify the person who matches a given trip disclosure, if the person is asserting privacy rights.

The problem is largely the medical one in my view.  I note that Xavier has just commented on the application of HIPAA here.  I am not familiar with the details of consent, it may be not so simple to ask for consent for public disclosure of the existence of a medical condition under HIPAA....which is, as he says, the only reason folks are supposed to be travelling business class.

However, I agree with you that in principle, individuals who accept travel support should be prepared to accept its disclosure.  When we discussed this a few months ago, though, it became pretty clear that there are those who strongly disagree.  Since ICANN is the controller of this information, it is their risk and their decision, in my view.

Stephanie

On 2019-01-23 19:23, Marilyn Cade wrote:
Stephanie, I am not sure I understand the "sleuth them out" comment
This not about being an ICANN detective but just asking that when ICANN spends $$, anyone receiving the $$ understands that their name, affiliation and total spend is posted -- Board, staff, community member regardless of what stakeholder group

No one "has" to accept ICANN sponsorship. and Yes, I understand that many cannot travel without sponsorship [I too am often in that situation] BUT, if receiving funding, then just understand that transparency is needed.

Let me mention the following example:

The BC has a program to try to encourage and support participation where we have funds -- which are limited.   We publish the recipients within the BC of our BC sponsorship costs and those who receive BC funding expect to have their name, title, organization and amount and purpose publicly shared with the full BC. It would be irresponsible of us to withhold that information from the funding source-- e.g. the BC in this case.  They also have to write reports about the outreach event they are sponsored for.

Of course, anyone can decline the conditions but being publicly acknowledged is part of the funding criteria. Shouldn't that be the case for all ICANN spend?

Whether Board, staff. consultants, community member, regardless of stakeholder --  It is not embarrassing to need funding. Community members do tremendous work and that is probably the most cost effective investment of ICANN in ensuring informed and continual engagement of dedicated members of the various communities.

________________________________
From: Gnso-sc-budget <gnso-sc-budget-bounces at icann.org><mailto:gnso-sc-budget-bounces at icann.org> on behalf of Tom Barrett <tbarrett at encirca.com><mailto:tbarrett at encirca.com>
Sent: Wednesday, January 23, 2019 5:59 PM
To: Stephanie Perrin
Cc: gnso-sc-budget at icann.org<mailto:gnso-sc-budget at icann.org>
Subject: Re: [Gnso-sc-budget] [v.0.5] latest version of our comment on FY20 budget

full disclosure of costs should be required to receive travel support.  Folks can always opt to pay their own way.

On Wed, Jan 23, 2019 at 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 – 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blacknight.com%2F&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352388738&sdata=Kt9r9fCPnCYKtur8Yo7sWnp35%2Be2t26QoAQ7FWSsNTQ%3D&reserved=0>

http://blacknight.blog/<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblacknight.blog%2F&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352388738&sdata=LKt0LYsyTzv5VLSyeYMaRMMNWpetGYkp0rt2tSy5Wu0%3D&reserved=0>

Intl. +353 (0) 59  9183072

Direct Dial: +353 (0)59 9183090

Personal blog: https://michele.blog/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmichele.blog%2F&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352544996&sdata=SluKpbXpG091HmwuaGiXYyTN89cUhvTwY1jkieA56ks%3D&reserved=0>

Some thoughts: https://ceo.hosting/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fceo.hosting%2F&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352544996&sdata=N8E1pkr5w0dw8IvBbWB5qRjnugapuVbfdhaaMUKrkgI%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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-sc-budget&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352544996&sdata=mWRqCi8v%2Fk3GvH9a70h7BKmR6TAAUuJX5OBbSK3r2Fo%3D&reserved=0>

_______________________________________________
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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fgnso-sc-budget&data=02%7C01%7C%7C57de87a3e50c420028ac08d681962e78%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636838879352544996&sdata=mWRqCi8v%2Fk3GvH9a70h7BKmR6TAAUuJX5OBbSK3r2Fo%3D&reserved=0>

--
Thomas Barrett
President
EnCirca, Inc
+1.781.942.9975 (office)
400 W. Cummings Park, Suite 1725
Woburn, MA 01801 USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20190124/4c145ea6/attachment-0001.html>