 |
Virus-free. www.avast.com |
_______________________________________________There is stated in the file:Version 1: 17 November 2020Note: this is a living document being put out for public comment. A final version will be published 3
weeks after IGF ends. For any questions or feedback regarding the IGF 2020 Messages, please write
to igf@un.orgSo I can assume that this text could be formed on the basis of several short reports which had to be provided in 12 hours after each session. Or on the reports made by the Diplo Foundation staff for each session. Or from the "discussions" themselves.The short reports were provided to IGF staff by the reporter of each session.And it seems there were no other way to contribute to exactly this text...What is a problem with it?Отправлено с устройства Galaxy-------- Исходное сообщение --------От: "Mark Svancarek (CELA)" <marksv@microsoft.com>Дата: 09.12.2020 23:10 (GMT+03:00)Тема: RE: [EXTERNAL] RE: [UA-comms] IGF Inclusion MessagesYes, the sessions were good I thought.
I was only wondering about the text of the Inclusion Messages that had been published. I think you are confirming that we were involved (“discussions”) but I wanted to be certain.
From: Maria Kolesnikova <masha@cctld.ru>
Sent: Tuesday, December 8, 2020 10:04 PM
To: Mark Svancarek (CELA) <marksv@microsoft.com>; ua-admin@icann.org; ua-comms@icann.org
Subject: [EXTERNAL] RE: [UA-comms] IGF Inclusion Messages
Hi Mark,
UASG community (UASG Leadership, members of local initiatives and UA Ambassadors) with support of ICANN team and ALAC members have contributed to the IFG 2020 agenda and its discussions.
And it was well reflected in the following reports after IGF 2020.
There were organized two sessions with UASG members support at IGF 2020 with different approaches to UA topic but contributing to Inclusion thematic both:
November 16 - IGF 2020 WS #267 Universal Acceptance of Domain Names and Email Addresses (+Report)
Recording: https://www.youtube.com/watch?v=iEUJbMXBmJw&t=9s
November 17 - IGF 2020 WS #271 Multilingualism online: old challenges and new perspectives (+Report)
Recording: https://www.youtube.com/watch?v=3jma7BchOOg&t=118s
BR,
Maria
From: UA-comms [mailto:ua-comms-bounces@icann.org] On Behalf Of Mark Svancarek (CELA) via UA-comms
Sent: Wednesday, December 9, 2020 1:24 AM
To: ua-admin@icann.org; ua-comms@icann.org
Subject: [UA-comms] IGF Inclusion Messages
We were reviewing the IGF Messages for each of the four tracks. For the Inclusion Messages, my colleague Ben came across this helpful section on UA which I wanted to make sure you had seen:
Promoting multilingualism online requires the nternationa of more institutional and financial resources. Governments, the private sector and nonprofit entities should empower local communities and indigenous people to produce digital content in their languages, and manage the associated intellectual property rights. The tech community can also help by developing technologies that enable the digital inclusion of low resource languages (oral languages, endangered languages, etc.). In addition, governments and tech companies should be more active in enabling the universal acceptance (UA) of nternationalized domain names (IDNs) and email addresses within their services and technologies. More awareness raising and capacity development are needed – on both the demand and supply side – to enable stakeholders to better understand the social benefits and long-term business benefits of supporting UA-readiness.
Did UASG contribute to this text?
/marksv
UA-comms mailing list
UA-comms@icann.org
https://mm.icann.org/mailman/listinfo/ua-comms
_______________________________________________
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.