ICANN/GNSO GNSO Email List Archives

[ispcp]


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

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

  • To: "'Mike O'Connor'" <mike@xxxxxxxxxx>, <ispcp@xxxxxxxxx>
  • Subject: RE: [ispcp] Draft: statement in support of Thick Whois WG recommendation
  • From: "Tony Holmes" <tonyarholmes@xxxxxxxxxxxxxx>
  • Date: Thu, 25 Jul 2013 20:47:07 +0100
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1374781627; bh=A2fq56IOEgFLAdkqgn9pPoPS99QE5lv0LOvV9QslZi4=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language; b=N1rOgL8Jzl6GynIBKehYXtXAnd5edAnbcgw7aTywflxy5SF9TC9hR/Qu0hWPFy4JUBEe41uRY308dWikfkXQsVJOM2qL+m3AxMINA0qXPtXvzgpQ8e0be9xlaGsyIejaCQAndh5z/G/ltHkBtL/H3hXgabNDMHQ6FHIIMkduoTo=
  • In-reply-to: <451C8B5B-51B7-4EA0-92D7-153A1BD29E7B@haven2.com>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <451C8B5B-51B7-4EA0-92D7-153A1BD29E7B@haven2.com>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx
  • Thread-index: AQGnnK1XOseyS440PRISm0c4xtF695nDpgRw

Thanks MIkey - looks good to me.

Tony

 

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.) 

 



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