Skip to main content

让 ICANN 公共会议为您服务

在我们筹备 ICANN69 届虚拟年度大会之时,我想到了公共会议在多利益相关方模型中所扮演的重要角色。会议期间,我们会编制用于构建互联网的未来的各项政策。公共会议还为培养社群基础、增进社群关系提供了一个空间。尽管 2019 冠状病毒病 (COVID-19) 疫情改变了我们相会的方式,但它并未改变我们对 ICANN 的使命做出的承诺,或我们的相互承诺。

针对 COVID-19 的响应措施

看到 ICANN 社群、董事会和组织联合起来,确保我们能够在 3 月通过虚拟方式继续召开社群论坛,我倍感自豪。在极短的时间内,所有人都被动员起来,创建并部署了各项工具,构建了在线环境,供大家能够实现会议目标。在 6 月召开的政策论坛中,我们对所用工具进行了扩展和创新,并且为即将召开的年度大会再次做出了各项调整。实现这一切并非易如反掌。每当我们面临着一项挑战时,我们都会通力合作、迎头而上。

在召开了一整年的虚拟公共会议后,从这些会议中吸取的教训将帮助我们审视这类会议的效果、还有哪些地方可以加以改进、以及我们可以吸取哪些经验,改进我们日后召开的面对面会议。现在我们启动这一流程是因为有很多人都跟我提到希望针对这个主题召开一次论坛。我相信这个流程将提供大家所需要的论坛。

征询社群反馈意见

ICANN 董事会正在与社群展开交流用以评估:虚拟公共会议的效果;本组织应该进行哪些改进来支持社群在会议期间的工作;日后的面对面会议战略中,应当纳入哪些方面。我们得以迅速转向虚拟公共会议的形式,使得我们在面对当前的形势,能够继续尽可能地高效工作。现在,我们希望大家能够建言献策,告诉我们这种调整对大家参与工作、实现会议目标的能力到底意味着什么。

会议战略创新

本流程的第一步是审视我们的过往会议经验。鉴于此,我们将向支持组织 (Supporting Organization, SO) 和咨询委员会 (Advisory Committee, AC) 的主席们发送一份调查,从而鼓励每个团体能够发起讨论。因为这类讨论应当在社群层面中进行。然后,各位主席将协调并整合各自团体的反馈意见。董事会将在 ICANN69 届会议上召开一次会议,继续与社群探讨我们的会议战略。这份调查将给这类讨论起到抛砖引玉的作用。

接着,本组织将编辑社群的反馈意见并编写一份摘要报告,根据这份报告的内容制定建议。我们将与 SO/AC 的主席们分享这些建议,确保建议精准地反映了社群关注的重点事务和期望。然后,我们将把这些建议提交给 ICANN 董事会供其考量。

在评估阶段,能够听到大家的心声是至关重要的。请联系您的领导人,确保您的观点已被纳入到这份调查之中。ICANN 公共会议对于我们的工作至关重要,我们致力于持续改善和提高参会体验。毫无疑问,今年是颇具挑战性的一年,但这也给我们带来了一次独特的机会。我们能以全新的方式审视 ICANN 公共会议,纳入新的合作方式,让我们的社群更加牢固,从而保护互联网的安全性、稳定性和互用性。

如果您还存有疑问,请在下方评论区输入。

敬请参与 ICANN69 董事会/社群针对会议的关注事项这节会议。

世界协调时 2020 年 10 月 19 日 12:30 时,Zoom 6 会议室

Comments

    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."