NCSG-DISCUSS Archives

NCSG-Discuss

NCSG-DISCUSS@LISTSERV.SYR.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Apple Message framework v1257)
Content-Type:
text/plain; charset=us-ascii
Date:
Fri, 6 Apr 2012 13:13:43 -0400
Reply-To:
Avri Doria <[log in to unmask]>
Subject:
From:
Avri Doria <[log in to unmask]>
Message-ID:
In-Reply-To:
Content-Transfer-Encoding:
quoted-printable
Sender:
NCSG-Discuss <[log in to unmask]>
Parts/Attachments:
text/plain (32 lines)
hi,

I am still oping for a way to make this about the question of whether any registry should be forced into Thick whois.  Thick whois is fine for the willing but it should not be enforced by ICANN, and there was never a GNSO policy process on Thick Whois - it is another one of the Board mandated policies for all applicants gTLDs.

Since the whole PDP is about forcing .com to adopt the thick whois, delaying the PDP is good.  But while it is delayed, it may also be good to find a way to turn the PDP on its head so that the general idea of thick for all is reviewed.  At his point we have thick for most all.

I have no idea how one would go about doing it.

avri

On 6 Apr 2012, at 12:38, Milton L Mueller wrote:

> Sorry, that should be "thin" whois not "think" whois. ;-)
> 
>> -----Original Message-----
>> From: NCSG-Discuss [mailto:[log in to unmask]] On Behalf
>> Of Milton L Mueller
>> Sent: Friday, April 06, 2012 12:38 PM
>> To: [log in to unmask]
>> Subject: [NCSG-Discuss] .COM renewal and thick Whois
>> 
>> Just read the GNSO Council meeting agenda for April 12.
>> Is the .COM renewal being used as an excuse to force or pressure the last
>> redoubt of think Whois into thick Whois?
>> If so, what can we do about it?
>> 
>> Milton L. Mueller
>> Professor, Syracuse University School of Information Studies
>> Internet Governance Project
>> http://blog.internetgovernance.org
> 

ATOM RSS1 RSS2