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>
  • Subject: Re: [ispcp] Draft: statement in support of Thick Whois WG recommendation
  • From: "Novoa, Osvaldo" <onovoa@xxxxxxxxxxxx>
  • Date: Fri, 26 Jul 2013 09:17:08 -0300
  • Accept-language: es-ES, es-UY
  • Acceptlanguage: es-ES, es-UY
  • Cc: "ispcp@xxxxxxxxx" <ispcp@xxxxxxxxx>
  • In-reply-to: <AC23F94A-FD78-4A3E-B6FF-DF2C5E609E36@haven2.com>
  • List-id: ispcp@xxxxxxxxxxxxxx
  • References: <451C8B5B-51B7-4EA0-92D7-153A1BD29E7B@haven2.com> <003701ce896f$bed94bd0$3c8be370$@btinternet.com> <AC23F94A-FD78-4A3E-B6FF-DF2C5E609E36@haven2.com>
  • Sender: owner-ispcp@xxxxxxxxxxxxxx
  • Thread-index: Ac6J+g4vBIC3v8WmRwmUjJBDReVmPA==
  • Thread-topic: [ispcp] Draft: statement in support of Thick Whois WG recommendation

Mikey,
It's fine with me.
Best regards,
Osvaldo

El 26/07/2013, a las 07:11, "Mike O'Connor" <mike@xxxxxxxxxx<mailto:mike@xxxxxxxxxx>> escribió:

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> [mailto:owner-ispcp@xxxxxxxxxxxxxx<mailto:ispcp@xxxxxxxxxxxxxx>] On Behalf Of Mike O'Connor
Sent: 25 July 2013 17:04
To: <ispcp@xxxxxxxxx<mailto: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<http://www.haven2.com>, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)



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


________________________________
El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información


This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.




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