PS: The .pdf 'track changes' texts referred to are to be found right at the bottom of the below thread. CW Begin forwarded message:
From: CW Mail <mail@christopherwilkinson.eu> Subject: Fwd: [CCWG-ACCT] Proposed WHOIS language Date: 3 Sep 2015 21:52:34 GMT+02:00 To: "accountability-cross-community@icann.org Accountability" <accountability-cross-community@icann.org> Cc: "whois-iag-volunteers@icann.org" <whois-iag-volunteers@icann.org>
Good evening:
With all my admiration for this excursion into 'track-changes' and many thanks to Greg for the .pdf formats:
a) I have not understood why these texts need to be agreed upon now. Isn't this par excellence a case to be referred to "work stream 2" - ?
b) WHOIS policy is being addressed in ICANN through several parallel processes, to the point that I have every expectation that they will give rise to inconsistent outcomes. We do not need CCWG to add to the process.
c) In any event, I absolutely disagree to including anywhere the repeated references to " … a commitment that becomes part of ICANN Bylaws, regarding enforcement of the current WHOIS … "
1. Current WHOIS policy has proven to be unenforceable for more than a decade.
2. Current WHOIS policy, should it be enforced, jeopardises Registrars and Registrants in jurisdictions where the policy conflicts with applicable local law.
3. All of the above will have to be reviewed by the community as soon as ICANN proposes how to implement the recommendations for a new gTLD Directory Service.
I suggest that CCWG drop the whole topic for the time being pending ICANN's proposals for new gTLD Directory Services.
Regards
CW
Begin forwarded message:
From: Greg Shatan <gregshatanipc@gmail.com> Subject: Re: [CCWG-ACCT] Proposed WHOIS language Date: 3 Sep 2015 21:05:18 GMT+02:00 To: Carlos Raúl Gutiérrez <crg@isoc-cr.org> Cc: "accountability-cross-community@icann.org" <accountability-cross-community@icann.org>
This seems to fall into the "no good deed goes unpunished" category. In any event, and in spite of not being asked, I have taken my time to convert the three documents to the PDF format, because I'm a nice guy.
Greg
On Thu, Sep 3, 2015 at 2:54 PM, Carlos Raúl Gutiérrez <crg@isoc-cr.org> wrote: My linux based, open source, FREE word processor opens/saves MS Word documents without any trouble………. So I don’t know what the issue is With Dr. Lisse´s IPad mini...
Carlos Raúl Gutiérrez _____________________
email: crg@isoc-cr.org Skype: carlos.raulg +506 8837 7173 (cel) +506 4000 2000 (home) +506 2290 3678 (fax) _____________________ Apartado 1571-1000 San Jose, COSTA RICA
On Sep 3, 2015, at 12:49 PM, Nigel Roberts <nigel@channelisles.net> wrote:
To be Frank, it's pretty rude to expect everyone to use the same software supplier. (In fact, in some circumstances it's even anti-competitive).
Why can't we use open standards, again?
On 09/03/2015 07:46 PM, Carlos Raúl Gutiérrez wrote:
I welcome your increasing flexibility the Apple store a a free app to read MS word documents now that should work in you iPad mini
Good luck
Carlos Raúl Gutiérrez _____________________
email: crg@isoc-cr.org <mailto:crg@isoc-cr.org> Skype: carlos.raulg +506 8837 7173 (cel) +506 4000 2000 (home) +506 2290 3678 (fax) _____________________ Apartado 1571-1000 San Jose, COSTA RICA
On Sep 3, 2015, at 11:56 AM, Dr Eberhard W Lisse <el@lisse.na <mailto:el@lisse.na>> wrote:
I am not even going to bother to ask, for, the umpteenth time, that documents are posted in an open format.
el
-- Sent from Dr Lisse's iPad mini
On Sep 3, 2015, at 17:24, Greg Shatan <gregshatanipc@gmail.com <mailto:gregshatanipc@gmail.com>> wrote:
All:
For what it's worth, I prepared track changes comparisons of the following:
CCWG Proposal vs. AoC language Board Proposal vs. AoC language Board Proposal vs. CCWG Proposal
These are attached.
Greg
On Thu, Sep 3, 2015 at 11:51 AM, Malcolm Hutty <malcolm@linx.net <mailto:malcolm@linx.net>> wrote:
On 03/09/2015 13:27, Bruce Tonkin wrote: > Hello Malcolm, > > On 02/09/2015 02:24, Bruce Tonkin wrote: >> ICANN commits to enforcing its policy relating to the current WHOIS >> and any future gTLD Directory Service, > > To be clear - we are not talking about any specific service here with any pre-conceived set of requirements.
Indeed. But I did think there was a risk that wording could be (mis)interpreted to suggest that we are - and then used to that effect when discussing what that future Directory Service might look like.
> We are talking about a new service that is established as a result of a policy development process in the GNSO. If it helps you could add the text: > > "any future gTLD DIrectory Service, established via ICANN's bottom up policy development process".
I think that would help.
The only point that I'm making is that we aren't trying to pre-empt that process or use this insertion into the Bylaws to direct certain outcomes from it. On that, I think we're all agreed; it's just a matter of being clear in the language we choose.
-- Malcolm Hutty | tel: +44 20 7645 3523 <tel:%2B44%2020%207645%203523> Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/
London Internet Exchange Ltd 21-27 St Thomas Street, London SE1 9RY
Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> https://mm.icann.org/mailman/listinfo/accountability-cross-community
<CCWG vs AoC Whois Review Comparison.docx> <Board vs AoC Whois Review Comparison.docx> <Board vs CCWG Whois Review Comparison.docx> _______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> https://mm.icann.org/mailman/listinfo/accountability-cross-community
Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org <mailto:Accountability-Cross-Community@icann.org> https://mm.icann.org/mailman/listinfo/accountability-cross-community
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community