[tld-global-acceptance] Fwd: RE: A specific Inquiry on .coop domain name not accessible & ISP Constituency Progress?

[Barbara Roseman <roseman@xxxxxxxxx>]

> Subject: RE: A specific Inquiry on .coop domain name not accessible &  ISP 
> Constituency Progress?
> Date: Wed, 21 Apr 2004 10:53:03 -0400
> From: "Hoover, Carolyn" <choover@xxxxxxxxxxxx>
> To: "Antonio Harris" <harris@xxxxxxxxxxxxx>
> Cc: <mcfadden@xxxxxxxxxxxxxxxxxxxxxx>, <roseman@xxxxxxxxx>,
>    <tony.ar.holmes@xxxxxx>
>
>
> Are there some specific questions I should put in the questionnaire on 
> "mail platforms" that would be most useful in this case?
>
> Thanks,
>
> Carolyn T. Hoover
> dotCoop Operations Center
> 1401 New York Avenue, Suite 1100
> Washington, DC  20005
> Tel:   +1.202.383.5453
> Fax:  +1.202 347.1968
> Toll-Free: +1.866.288.3154 (Intl Callers - Check www.att.com/traveler for 
> your local toll free number)
> -----Original Message-----
> From: Antonio Harris [mailto:harris@xxxxxxxxxxxxx]
> Sent: Wednesday, April 21, 2004 11:05 AM
> To: Hoover, Carolyn
> Cc: mcfadden@xxxxxxxxxxxxxxxxxxxxxx; roseman@xxxxxxxxx; tony.ar.holmes@xxxxxx
> Subject: Re: A specific Inquiry on .coop domain name not accessible & ISP 
> Constituency Progress?
>
> Carolyn,
>
> Thanks for contacting me on this important matter.
>
> Briefly, when we ran some tests to new gTLD mail
> addresses, including .coop, no problems were
> detected from the use of Telnet in ISPs. However,
> as per the information we supplied to Marie Zitkova
> at the end of March, one ISP did encounter some
> problems when attempting e-mails from webmail
> and mail client applications (such as Eudora).
>
> The original conclusion by the Registry Constituency,
> as voiced during the ICANN Montreal GNSO meeting,
> considered that ISPs were "filtering" the new gTLD
> strings (specially those with more than 3 characters).
> This would not appear to be true, and work seems to
> be required in identifying limitations running on software
> platforms that precede the ISP handling of these e-mails.
>
> I am not too sure if having users contact their dial-up ISPs
> would produce results, as these ISPs most probably would
> find no problem in their own operations. Perhaps it would
> be more fruitful if you sent these users a short questionnaire
> asking what mail platforms they are using.
>
> A working group has been established, and that information
> could be useful to kickstart analysis of these problems by
> this working group.
>
> I have copied this to Mark McFadden who coordinates the
> working group. Mark, perhaps you could take the lead in
> helping Carolyn with this issue.
>
> Regards
>
> Tony Harris
> ----- Original Message -----
> From: <mailto:choover@xxxxxxxxxxxx>Hoover, Carolyn
> To: <mailto:harris@xxxxxxxxxxxxx>harris@xxxxxxxxxxxxx
> Sent: Wednesday, April 21, 2004 10:08 AM
> Subject: A specific Inquiry on .coop domain name not accessible & ISP 
> Constituency Progress?
>
> Tony,
>
> I had been meaning to contact you this week, and this prompted me to do 
> so.  Here is an issue that arrived at the .coop registry yesterday:
>
> We have recently put into service <http://www.uda.coop>www.uda.coop. Some 
> of our customers are
> experiencing problems getting to the site unless they use the IP address.
> These users are generally users of MSN dial up and use Internet Explorer.
> Others using Internet Explorer or Netscape on high speed lines have no
> problem. Even AOL users are fine.
>
> I spoke with XO Communications to confirm that the DNS was entered
> correctly. Is there a known problem with .coop extensions? Any help you
> can provide would be greatly appreciated.
>
> Jim Chenoweth
> United Dairymen of Arizona
> 602-625-4116
>
> I had wanted to let you know that I had volunteered to "shepherd" this 
> issue from the Registry Constituency since Marie Zitkova of .aero is now 
> the chair of that group and needs to pass off some of the other 
> issues.  When we last heard from your group in Rome, the testing in South 
> America had raised some issues that had prevented you from providing a 
> report on the results at the meeting.  In the meantime, based on support 
> from Vint C. and other Board members, ICANN has set up a listserv to 
> address this issue, but I am not sure who besides the registry 
> constituency members are on this "circuit?"  Are you and others in the ISP 
> group?
>
> So, first I would ask your advice on what might be done to track down the 
> problems for the users that are noted by the registrant.  Should we have 
> the users with the problems contact their dial up providers?  Your help on 
> this would be appreciated so that I can respond to my user.
>
> And then if you would give me an update on efforts to date on this issue 
> from the perspective of the ISP Constituency, that also would be 
> appreciated.  If there is someone else that I should be contacting, please 
> let me know.
>
> If it would be easier, please do not hesitate to call me!
>
> Yours in cooperation,
>
> Carolyn T. Hoover
> dotCoop Operations Center
> 1401 New York Avenue, Suite 1100
> Washington, DC  20005
> Tel:   +1.202.383.5453
> Fax:  +1.202 347.1968
> Toll-Free: +1.866.288.3154 (Intl Callers - Check 
> <file://www.att.com/traveler>www.att.com/traveler for your local toll free 
> number)