ICANN/GNSO GNSO Email List Archives

[ispcp]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ispcp] Draft: statement in support of Thick Whois WG recommendation

  • To: ispcp@xxxxxxxxx
  • Subject: Re: [ispcp] Draft: statement in support of Thick Whois WG recommendation
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Fri, 26 Jul 2013 07:08:55 -0500
  • In-reply-to: <003701ce896f$bed94bd0$3c8be370$@btinternet.com>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <451C8B5B-51B7-4EA0-92D7-153A1BD29E7B@haven2.com> <003701ce896f$bed94bd0$3c8be370$@btinternet.com>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx

just checking to see if there's any opposition or suggested edits.  if i don't hear any by the end of the weekend, i will go ahead and post this to the comments forum.

thanks,

mikey


> From: owner-ispcp@xxxxxxxxxxxxxx [mailto:owner-ispcp@xxxxxxxxxxxxxx] On Behalf Of Mike O'Connor
> Sent: 25 July 2013 17:04
> To: <ispcp@xxxxxxxxx>
> Subject: [ispcp] Draft: statement in support of Thick Whois WG recommendation
>  
> hi all,
>  
> i rummaged through some of our earlier comments on Whois and found this little snippet from our 2005 comment on the Whois Staff Report that seemed like a good lead-in to our support of the recommendation of the Thick Whois WG work.  so here's a proposed draft comment for your collective review/edit/approval.
>  
> mikey
>  
> - - - -
>  
> As noted in previous statements, ISPCP members rely on Whois data in a variety of ways:
>  
> 1. to research and verify domain registrants that could vicariously cause liability for ISPs because of illegal, deceptive or infringing content.
> 2. to prevent or detect sources of security attacks of their networks and servers
> 3. to identify sources of consumer fraud, spam and denial of service attacks and incidents
> 4. to effectuate UDRP proceedings
> 5. to support technical operations of ISPs or network administrators
>  
> The ISPCP believes that requiring a consistent technical model across all TLDs advances our ability to use Whois in all these ways and strongly supports the recommendation by the Thick Whois Working Group to require the use of Thick Whois across all gTLD registries.
>  
>  
> 
> PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)
>  


PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)



<<< Chronological Index >>>    <<< Thread Index >>>