<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hello All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I apologize for my silence as of late, but I wanted to provide the UA list a basis for why I advocated in support of a UA Logging Project. Over the last 15 years I have been working with UA issues in connection with various registry clients. Over the last several months I have dealt with a number of UA issues with a variety of companies, e.g. Facebook, Twitter, Adobe, and local ISPs.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>While I believe many of these examples justify the potential development of a UA Logging Project, I would like to share the details of a recent success story to highlight my support for this initiative. A registrant in a new gTLD which had recently migrated from their .COM to their new TLD extension was informed by one of their third party vendors that their extension was not working with Adobe’s Connect Event Manager. This third party vendor on behalf of the registrant contacted Adobe which generated a support ticket and a bug tracking reference ID. The specific UA issue was associated with the use of <span style='font-size:10.5pt;color:black'>Commons Validator API 1.4.1.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After some period of time with no proposed resolution, I on behalf of the Registry Operator reached out to J Scott Evans who is an Adobe employee active in the ICANN community. J Scott was then able to track down an appropriate person within Adobe to help expedite resolution of the problem. Within days of getting to the right person, Adobe was able to resolve the issue by incorporating Commons Validator API <span style='font-size:10.5pt;color:black'>1.5.1 into the next release of the Adobe software scheduled for later this month.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'>Now in dealing with Adobe and other software/service companies there are common practices that most follow in documenting UA issues, i.e. detailed instructions on what the user was doing when encountering the UA issue; screen shots of the error; OS/hardware; etc. I have found that the more detail you provide these companies the quicker they are about to troubleshoot and resolve the issue. By having a UA logging system it would allow UA WG or ICANN the ability to contact appropriate individuals in each company more quickly. I do NOT propose to make this contact information publicly available in any UA Logging system unless the person consents.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'>I think by identifying the Commons Validator issue it could provide a means to alert other software providers of this issue to proactive address it before other new gTLD registrants experience this problem. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michael Palage <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>