Hi, like John and Wendy before me, I ask that my name be taken off pages 2 and 3. This document was developed by a consultant in fall of 2006. As John says, it was dropped on us Oct 31 2006 for a THREE DAY COMMENT PERIOD so as to have translation and publication time before the early Dec. Sao Paulo conference (I have the email to prove it). A third of the committee was busy at IGF in Athens at this time. I don't think Wendy will mind me quoting from an email of hers from Nov 1: "I'm sorry, but I agree with John that this can't be put out under the ALAC name until ALAC members have an opportunity to offer more substantial review and revisions. Those ALAC members on the cc list here are not even the full committee, so we couldn't commit "ALAC" in any event before review by the committee. Miriam provided a slightly longer window for comment, but the sense of the committee was-- Why are we trying to push this guide through in a hurry to gain few weeks, when it is years late anyway? The worst thing we could do is to get something done that is both terribly late and incorrect. Since we cannot fix the lateness, let's at least make sure it will be done right! My own comment at the time was "I agree with Wendy. I would prefer that ALAC's name be taken off this entirely. I would prefer a much more engaging document that would provide some real-world examples. No offense meant, Miriam, I'm sure you were just asked to write a FAQ, but there are more than enough FAQs [on this topic] and they don't seem to get the important messages across to end-users, whom the ALAC serves. It's time for a new, fresh approach that doesn't even look like the document you sent for editing. I think there should be illustrations too. Just my two cents on the topic." I stand by the same comment today and I don't want my name on this. I see by the 2006 mail I have on this topic that several other members did provide specific feedback and changes. I don't see that any of these changes have been incorporated. Even some if not all of Nick's own suggestions aren't in here: "> Perhaps the following specifics could be helpful in addressing some of
the most recently-stated issues:
1) decide that a subsequent guide will address ccTLDs, but that this one will only address gTLDs.
2) ensure the name is changed to "A Guide to Generic Top-Level Domain Names"
3) add a preamble noting that the guide focuses only on gTLDs and there are 250 country code tld's and these will be addressed in an upcoming "A Guide to Country Code Top-Level Domain Names"
And then also, in SP show the draft guide to members of the ccNSO Council and invite them to work with the ALAC in creating such a guide focussed on .
I would be surprised if ALAC wanted it published under its name. Jean At 5:30 PM -0500 1/25/08, John L recently said:
Please see e-mail below and send me and comments that you may have on same so that I can ensure that they are incorporated into this document.
Please take my name off pages 2 and 3. I suspect the other former ALAC members will feel the same way.
In fact, the Interim ALAC had nothing to do with this thing. ICANN hired a consultant to write it and dropped it on us. Miriam is a nice lady but she doesn't know much about registering domains.
R's, John
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ica... Visit the NA-RALO Wiki at https://st.icann.org/naralo/ ------