Cross Community Proposals for ICANN 61

Michael Karanicolas mkaranicolas at GMAIL.COM
Mon Dec 11 10:27:50 EET 2017


Hi Renata,

So, for starters, I don't think it's one or the other: if people want a
cross community session on the .cat case - having an open data session
doesn't prevent that from happening.

But, in terms of the open data discussion: there were two sessions on open
data at ICANN: the Open Data Initiative session, and the session on the
Information Transparency Initiative. The first one, which I believe is the
one you attended - was pretty useless, I agree. But it was also heavily
focused on the utility and applications of ICANN's data to commercial
interests, and it addressed these issues in a very rudimentary way (half
the time was inexplicably taken up by sales pitches from business analytics
firms).

This is obviously not what we're going for, but I think the way the open
data session was handled at ICANN 60 is a good illustration of just why we
need to get into this conversation ourselves - to ensure that there are
non-commercial voices in this process going forward, and that the open data
initiatives are being carried out in a way that suits the overall needs of
ICANN's community (not just the parts of it who want this information to
re-sell). Indeed - my hope is that rather than ICANN providing open data
use cases and guidance to the community, our community will be able to
provide feedback to ICANN to guide their process going forward.

With that being said, I would pose a few questions:

Is there information that you have difficulty finding on ICANN's website?
Is there information that ICANN doesn't publish that you would like to see?
Are there particular research projects that people on the non-commercial
side are undertaking which would be assisted by information ICANN possesses
or has access to?

I'm guessing that a lot of the people in our community would answer yes to
at least one of these questions. If so, this is your chance to provide
feedback which shapes the way ICANN delivers information going forward.
Information is the lifeblood of accountability - if there's anything that
ICANN has that we want, this is the time to raise it, especially since
these programs are being developed right as we speak - so this really is a
pressing issue to address now, as the system is being designed. If we
decline to offer feedback at this stage, it's going to be very difficult to
complain about the website and information delivery systems when they're
relaunched in a year or two.

Best,

Michael


On Mon, Dec 11, 2017 at 10:04 AM, Renata Aquino Ribeiro <raquino at gmail.com>
wrote:

> Hi all
>
> As someone who was in the sessions about Open Data in ICANN, I don't agree
> with this being a cross community session.
> I could not really see any concrete steps an example of open data use
> cases and guidance to the community.
>
> On the other hand, there are pressing topics that still need to be
> addressed.
>
> In preparation to ICANN63, shouldn't we have a cross community session to
> re-examine the .cat case?
> Whatever one's views on the political aspect of it all, the technical and
> legal aspects are certainly of interest to ICANN community and I would
> propose we gather a variety of community members who could speak to this.
> So far governments have spoken a lot about it, but not civil society.
>
> The same goes for the WT5 ongoing work. The GAC has request 3 meetings in
> ICANN60 to discuss the dot-Amazon case. WT5 seems worth at least 1 cross
> community topic. This has also to be an informed debate, with participants
> who have pioneered new gtlds and those who are interested in using them.
> While this seems to me like an important session, I would think it could be
> a challenge for the new PC NCSG representatives from NCUC, when they are
> announced. They could call the session: "Why does GAC wants this so much?"
>
> Best,
>
> Renata
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20171211/cd0eaae3/attachment.htm>


More information about the Ncsg-discuss mailing list