At the ccNSO-Council prep day I committed to provide feedback to the ccNSO Council on what happened at the Universal Acceptance session - which coincided with the ccNSO Council meeting.

There is an action item for the ccNSO council to make sure that papers that it has approved are monitored on a regular basis as they flow through the rest of the ICANN community.

Here’s my report which will be in the APTLD report on the ICANN51 meeting:

—

Universal Acceptance

At the Universal Acceptance session we heard that ICANN has started development work on a roadmap with some ideas, but no execution.   Their plans include:

·       Developing some presentation decks and related collateral that different members of the community can use locally.

·       Going to software development conferences to raise the issue.

·       Planning for a help-desk where problems associated with Universal Access can be received, recorded, and forwarded to the relevant party.

None of these initiatives are actually in place.

 

Mozilla has maintained a Public Suffice List for some time.  This list is used by many applications to validate top and 2^nd level domain space.   IANA appears to be providing a CSV file with a copy of TLDs for validation.  While ICANN update this four times a day, Mozilla – which maintains the Public Suffix List through a volunteer effort – keeps their file update once a month or so as volunteer time becomes available.

 

We also heard how the JIG report, which was a cooperative agreement between the ccNSO and the gNSO, remains unadopted by the Board.

 

The comment that ICANN was looking to raise Universal Acceptance to the same level as IPv6 and DNSSEC was met with alarm – because both those initiatives have been underway for nearly two decades.

 

There is a group outside of ICANN who are keen to see Universal Acceptance sorted and APTLD will be building a ‘coalition of the willing’ to identify paths to solution – with a possible meeting in Morocco in conjunction with ICANN52.

------