[UA-discuss] Boilerplate answers for contracted parties

Thu Nov 25 11:53:45 UTC 2021

This is the main problem in general  – we have no lever to force a website operator or a software vendor to resolve the UA issue. 

So the current tactic is to move via small steps and use any opportunity to let them know that UA issue exists. More they hear about it from different sources, more chances they get the message and resolve it.  

Regards,

Maria

From: Michele Neylon - Blacknight <michele at blacknight.com> 
Sent: Wednesday, November 24, 2021 5:11 PM
To: Aman Masjide <aman at radix.email>; Maria Kolesnikova <masha at cctld.ru>
Cc: ua-discuss <ua-discuss at icann.org>; Don Hollander <don.hollander at gmail.com>
Subject: Re: [UA-discuss] Boilerplate answers for contracted parties

While this sounds fine in theory, in reality it’s up to the website operator or software vendor whether the issue is resolved or not. 

ICANN’s staff can’t force them to even reply nevermind getting them to address the issue. 

So while I support the idea I’d be wary about setting reasonable expectations. 

Regards

Michele

--

Mr Michele Neylon

Blacknight Solutions

Hosting, Colocation & Domains

 <https://www.blacknight.com/> https://www.blacknight.com/

 <https://blacknight.blog/> https://blacknight.blog/

Intl. +353 (0) 59  9183072

Direct Dial: +353 (0)59 9183090

Personal blog:  <https://michele.blog/> https://michele.blog/

Some thoughts:  <https://ceo.hosting/> https://ceo.hosting/

-------------------------------

Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty

Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845

From: UA-discuss < <mailto:ua-discuss-bounces at icann.org> ua-discuss-bounces at icann.org> on behalf of Aman Masjide via UA-discuss < <mailto:ua-discuss at icann.org> ua-discuss at icann.org>
Date: Monday, 22 November 2021 at 13:29
To: Maria Kolesnikova < <mailto:masha at cctld.ru> masha at cctld.ru>
Cc: ua-discuss < <mailto:ua-discuss at icann.org> ua-discuss at icann.org>, Don Hollander < <mailto:don.hollander at gmail.com> don.hollander at gmail.com>
Subject: Re: [UA-discuss] Boilerplate answers for contracted parties

[EXTERNAL EMAIL] Please use caution when opening attachments from unrecognised sources.

Hey Maria, 

Some interesting points. Yes,  I think we should have some sort of FAQ for these issues.The messaging could also be that there is nothing wrong with the TLD but the website/software is using outdated directory to map TLDs. Secondly, if UASG support were to receive an escalation from a Registry or Registrar(raising tickets on behalf of the customer), it should be considered critical and given top priority. Effective and efficient handling of such instances would ensure retention of customers and promotion of nTLDs.

Regards,

Aman

On Thu, Nov 18, 2021 at 2:11 PM Maria Kolesnikova via UA-discuss < <mailto:ua-discuss at icann.org> ua-discuss at icann.org> wrote:

Don, I have suggested to log issues on the uasg.tech to them during the call. Hope, it helps.

To make such an outreach mechanism, there can be also published relevant FAQ on the uasg.tech. Or made some promo-materials on "How to fix UA issues" for different audiences/stakeholders. Short and meaningful, listing several practical steps that can be done by each. We will discuss it at UA Comms WG. Any ideas else?

Regards,

Maria Kolesnikova

Скачайте  <https://aka.ms/AAb9ysg> Outlook для Android

  _____  

От: UA-discuss < <mailto:ua-discuss-bounces at icann.org> ua-discuss-bounces at icann.org> от имени Don Hollander via UA-discuss < <mailto:ua-discuss at icann.org> ua-discuss at icann.org>
Отправлено: четверг, 18 ноября 2021 г., 10:55
Кому: Mark Datysgeld
Копия: ua-discuss
Тема: Re: [UA-discuss] Boilerplate answers for contracted parties

They could ask the issue be logged with the UASG HELPdesk 

On 18/11/2021, at 8:37 PM, Mark Datysgeld via UA-discuss < <mailto:ua-discuss at icann.org> ua-discuss at icann.org> wrote:

Everyone,

On today's GNSO Council meeting, Kurt Pritz raised an interesting question: we do not provide a set of standard answers for registries and registrars to respond to their clients when a domain that needs UA fails to be have their email accepted or a website address fails to be recognized.

Thinking about it, we could actually use that as an outreach mechanism. Something along the lines of "We are involved in a global effort to promote the acceptance of all domain names, and ideally you should get in touch with the website that rejected your email and make them aware that there is demand for them to support this technology. You can forward them this link [uasg.tech]" (only a loose idea here).

Something to consider.

Best,

-- 
Mark W. Datysgeld [ <https://markwd.website> markwd.website]
Director at Governance Primer [ <https://governanceprimer.com> governanceprimer.com]
ICANN GNSO Councilor

_______________________________________________
UA-discuss mailing list
 <mailto:UA-discuss at icann.org> UA-discuss at icann.org
 <https://mm.icann.org/mailman/listinfo/ua-discuss> https://mm.icann.org/mailman/listinfo/ua-discuss
_______________________________________________
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> https://www.icann.org/privacy/policy) and the website Terms of Service ( <https://www.icann.org/privacy/tos> 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.

-- 

 <http://www.radix.website/> 

Aman Masjide
Consulting Advisor
Trust and Safety
T: +91 (22) 6196 6300 Extn: 8653 

Skype: amasjide
 <http://bit.ly/2xsTmrn> Google Buys Business.Site for Google My Business

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/mailman/private/ua-discuss/attachments/20211125/72bf1499/attachment.html>