AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large FY25 Strategic Priority Activities

Versions Compared

Old Version 16

changes.mady.by.user Dev Anand Teelucksingh

Saved on

compared with

New Version Current

changes.mady.by.user Dev Anand Teelucksingh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

This page seeks to track possible technology related issues noted by the At-Large Technology Taskforce Working Group and the At-Large Community for raising with ICANN Staff.

Current Technology Issues


Advanced Tables - Table Plus


Description of IssueStatus of IssueUpdatedSolution / Workarounds

LACRALO mailing list issues

(See discussion-of-LACRALO-mailing-list-issues for a deeper background behind this issue.)

Status
colourYellow
titlein Progress


 

To resolve the critical issues, ICANN did a complete rewrite of the tool which is scheduled to be deployed to the lists mid December 2019


2019 - Two critical issues have been noted on the discussion-of-LACRALO-mailing-list-issues page : missing emails from the lacralo-es to lacralo-en list ; and the general error message "Sentence punctuation must be followed by a space" not specifiying where in emails the error occurs.

ICANN IT has a new developer looking at the code to see the bugs.

The discussion-of-LACRALO-mailing-list-issues page has other ideas / workarounds for the tool.







Issues regarding Zoom

Include Page
Questions to ICANN regarding Zoom
Questions to ICANN regarding Zoom

Resolved Technology Issues

The following table are for RESOLVED Technology Issues

Advanced Tables - Table Plus


Status of IssueUpdatedDescription of IssueSolution / Workarounds
Status
colourGreen
titleRESOLVED


 

Turn on Collaboration Capabilities in Confluence

The current version of Confluence allows for collaborative capabilities in writing pages and this would be very helpful to At Large members as we write policy statements and other documents that are stored on our wiki.

We also asked for the current version of Confluence to be updated to the new version

We discussed this on the February 2019 TTF call and were told that the reason it was not turned on and that the version of Confluence was not updated was because this feature caused several breaks in links on the current version and that IT was looking at this issue. We asked Mark Segall to update us on this issue.

After the wiki hack incident around April 2019, the latest version of Confluence was installed and the collaborative editing feature turned on.

Status
colourGreen
titleResolved

 
Having server resources available to test open source solutions like Mattermost, eXo

Whilst several tools have been identified as potential tools that could be useful for At-Large, currently we have to ask volunteers to donate hosting and to configure such server resources. Such persons are rare in At-Large and are typically busy persons to assist with the deployment of such tools for At-Large Testing.

Whilst Mattermost testing has now begun thanks to a volunteer, the more complex eXo platform testing has not started.

Can ICANN assist with proving server resources?

Workaround : use Amazon Web Services (AWS) - Cloud Computing Services that provides 1 year for new Amazon customers.

Status
colourGreen
titleResolved

 

While working on the ICANN Stakeholder Analysis Tool , it was noted that a lack of consistent HTML used to display ALSes information on the At-Large website (https://atlarge.icann.org/alses/afralo ; https://atlarge.icann.org/alses/apralo ; https://atlarge.icann.org/alses/euralo ; https://atlarge.icann.org/alses/lacralo ; https://atlarge.icann.org/alses/naralo ) hampered retrieval of information into the tool.

See Lack of consistent HTML on ICANN At-Large website (ALS information) .pdf which documents the missing HTML pairs when ALS information was missing.



ICANN IT noted the issue and scheduled a fix in late July / early August 2018. The fix was deployed and the ICANN Stakeholder Analysis Tool is now able to retrieve all At-Large information automatically.

Status
colourGreen
titleResolved

 
When At-Large persons with Yahoo email addresses post to At-Large mailing lists, their emails are received as spam messages by other persons on the mailing list.
In Gmail, the emails recevied from Yahoo email addresses have his message in the spam folder
"Why is this message in Spam? It has a from address in yahoo.com but has failed yahoo.com's required tests for authentication. Learn more		ICANN Staff plans to install updates to mailman to support DMARC. See http://atlarge-lists.icann.org/pipermail/at-large/2015q4/004153.html

...

Currently there is NOT an option to have more than one audio channel within Adobe Connect.  I have explored many options to try to resolve this issue, as I understand the concerns this group has, and I too would like to see these features with adobe connect.  Some options I have tried, utilizing the breakout sessions, which DOES split up the audio into difference bridges, however, there is no option for an interpreter to be able to bridge across two language breakouts to be able to do their job. The only way to have multi channel audio currently with adobe connect is to link to an outside service, similar to how we are currently managing multi-language streaming.  There is a bit of a flaw in this thought process to have multiple languages all in the English based adobe connect room.  The true way this is intended to work, and was utilized by ICANN with NETmundial, is to provide each adobe connect room in the native language.  For example, you have English, French and Spanish Adobe Connect rooms (all separate dedicated rooms), which are tied to the phone bridge for the respective languages.  This allows when a Spanish speaking person logs into the Spanish Adobe Connect, they hear, read and see Spanish, and when a user speaks in English, the Spanish room hears the Spanish interpreters.  Having done this myself for NETmundial, this is logistically very challenging, and requires many staff to make this happen.  In my example, you would need three operators (one for each language), three Remote Participation managers, one for each room, and fluent in the respective room language to answer chat comments etc. You would also need the three interpreters, one for each room.  Not to mention, the content to be shared in each room, also needs to be translated into the respective room language.  This is an example of a perfect world, but at this point is not technically feasible nor manageable from a labor standpoint.

So to round this conversation point, currently the technology provided by Adobe Connect does not permit the feature you are looking for.

...

Status
colourGreen
titleRESOLVED
 

Remote participation in ICANN F2F meetings. There are significant challenges for remote participation

  • The Adobe Connect room can only stream one audio channel, and typically its the raw audio, meaning interpretation is not heard.
  • Similarly, persons wanting to speak have to dial Adigo but still can only hear raw audio, meaning the remote participants cannot hear interpretation.
  • The different language audio streams are delayed by up to 30-40 seconds. If the computer was used to dial Adigo (using programs like Skype), this results in two audio streams, one from the Adigo bridge, one from the language stream which makes it hard to understand speakers in the room being interpreted in the language of the remote participant
Mark Segall has responded to this issue in May 2016 :


  • Re:

Remote participation in ICANN F2F meetings. There are significant challenges for remote participation

  • The Adobe Connect room can only stream one audio channel, and typically its the raw audio, meaning interpretation is not heard.
    • This was originally how we had it where it was raw audio, but now as of 3-4 meetings ago, we stream the English line, which means adobe connect always has English, whether via floor speaker or interpreter.
  • Re: Similarly, persons wanting to speak have to dial Adigo but still can only hear raw audio, meaning the remote participants cannot hear interpretation.
    • Same as above, they will hear English as the primary adobe language and on the phone.  If they want to hear the interpretation, they do have to listen to a separate stream.  We are looking into alternatives to this, but so far have not found any viable options.
  • Re: The different language audio streams are delayed by up to 30-40 seconds. If the computer was used to dial Adigo (using programs like Skype), this results in two audio streams, one from the Adigo bridge, one from the language stream which makes it hard to understand speakers in the room being interpreted in the language of the remote participant

...

Status
titleIn Progress

...

  • Streams are no longer delayed 30-40 seconds – at most they are delayed 3-5 seconds.  In some cases there is a delay in Interpretation, due to the interpreter listening to the speaker for the full phrase before interpreting into another language.  This is the nature of interpretation, and will add a small delay.
Status
colourGreen
titleRESOLVED
Sept 21, 2016

The RALO literature is devoid of speciality email addresses ie.

chair@naralo.org and secretariat@naralo.org

Staff has said for security reasons it can't be done.

Resolved this issue by creating a list serve Naralo-Leadership@icann.org.

From Mark Segall :

I followed up internally on the request for aliased email addresses (the last recorded issue on the AL-TTF Issues page dated 21 Sep) they have provided confirmation that these email addresses do still exist in the form of a mailman distribution list.....

....However, what has changed is the ability to “Send As” this address.  The security team has made several changes to this function throughout our services ecosystem to reduce risk of phishing.  So if anyone wishes to be able to send as chair@naralo.org, we will need to work with the individual(s) to configure VPN.

Resolved--


Status
colourYellow
titleUNRESOLVED

Adigo dial out quality

(submitted by  Sarah Kiden Feb. 20) Adigo Call quality has really be dropping. Sarah reports that in some calls her call has dropped several times and in the past the quality was not so bad.

Many other people have reported a significant increase in the number of calls dropped by adigo

...

Status
titlein Progress

...

Filed a budget request to the At-Large FBSC for ICANN to finance the hiring of a programmer to assist the volunteer ICANN staff member to fix outstanding bugs - see At-Large FY17 Budget Development Workspace , this was approved by the At-Large FBSC and filed with ICANN.

Call for volunteers to help test the latest version of the translation engine - several persons have joined and several new bugs identified at discussion-of-LACRALO-mailing-list-issues page

...

(submitted by Satish Babu) - the dial-out quality for most conference calls are quite poor and practically unintelligeble for 60-70% of the time. The device used at my end is my mobile phone, which works ok for normal calls. Can something be done about this? The AC room audio is much better (in listen-only mode), although it's somewhat noisy if I try to speak at peak hours.

...

@Olivier COlivier Crepin Leblond also has had numerous problems with the quality of the calls

We asked Mark Segall to follow up on these issues with the Meetings team



Adobe Connect


Since ICANN has stopped using Adobe Connect, the technology issues noted here have been moved to the Adobe Connect Issues Page

...