Zoom Enhanced Security & Feature Updates

Following a number of updates to Zoom in the past weeks, we felt that this would be a good time to review both ICANN org’s and the ICANN community’s usage of the application. You may recall our message last month alerting you to some of the coming changes to Zoom, including their move to GCM encryption as their new standard. Zoom has switched all meetings to GCM encryption as of 30 May and is requiring all users to update to Zoom 5.0 or later. This change to the software’s encryption method was vital, and it has increased our confidence in the platform immensely.

Another recent change ICANN has made is enabling recording disclaimers by default. This prompts a small pop-up when a recording is started in Zoom, which includes an acceptance of our privacy policy, terms of service, and consent to be recorded. It is our hope that this small change empowers attendees by providing quick access and more control over the acceptance of our policies as it relates to attending virtual meetings.

Finally, embedded password links for password protected sessions have been brought back by popular demand. In May, these were disabled out of an abundance of caution. However, after examining Zoom’s recent updates, along with our own settings configuration, we’ve decided it is acceptable to re-enable the links. Please use these links cautiously, only share them on secure channels such as encrypted chat or encrypted e-mail, and never post them publicly.

As Zoom continues to change and evolve as a platform, ICANN will continue to discover and define our “new normal” for virtual meetings. We welcome your feedback on Zoom and meeting security. Please reach out to mts@icann.org with any comments, observations, or questions.
Domain Name SystemInternationalized 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.”

Source link