October 2007 - At-Large - lists.icann.org

Independent Review of the ICANN Nominating Committee
by Danny Younger Oct. 24, 2007

Oct. 24, 2007

"We recommend that the ALAC appoint two policy board Directors, using whatever mechanism it considers to be appropriate." http://www.icann.org/reviews/nomcom-review-report-10oct07.pdf __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 3

RAA: Synthesis of Public Comments Received
by Danny Younger Oct. 24, 2007

Oct. 24, 2007

http://www.icann.org/topics/raa/raa-public-comments-23oct07.pdf __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [At-Large] SoCal Fires (off topic)
by Robert Guerra Oct. 23, 2007

Oct. 23, 2007

Begin forwarded message: > From: Camron Assadi <cassadi(a)sfo.mercycorps.org> > Date: October 23, 2007 12:08:36 PM EDT (CA) > > Here's an interesting article about Jim Forbes, who is 'fire > blogging' from a shelter in Escondido, CA: > > Article: > http://www.networkworld.com/community/node/20911 > > His blog: > http://forbesontech.typepad.com/my_weblog/2007/10/fire-blogging-a.html > > (via /.): > http://hardware.slashdot.org/article.pl?sid=07/10/23/1438211&from=rss > "Retired journalist and mobility expert Jim Forbes is among the > quarter-million San Diego-area residents driven out of their homes > by the horrific wildfires. Forbes has taken the opportunity to > 'fire blog' from his shelter and discuss via e-mail with Network > World how his personal technology and the shelter's wireless > networks are holding up under the strain. 'The shelter set up a > dedicated computer room with an 802.11 a,b, and g network which > worked like a charm. Lots of people brought notebooks when they > left their home, so there was a whole lot of IM traffic in and out > of the shelter. The local cell networks were subsumed by traffic > early in the day so people were texting friends and loved ones a lot." > > Camron >

3 2

Nominations for ALAC Officer, Liaison, and Working Group Chairs
by Jacqueline A. Morris Oct. 23, 2007

Oct. 23, 2007

Dear At Large The time for acceptance of nominations has expired, and as such, this is the final slate of candidates for the officer and liaison positions within the ALAC. Nominations for Officer Positions 2007/8 ALAC Committee Officers Chair Cheryl Langdon-Orr (accepted) Vice Chair Vanda Scartezini (accepted) Sebastien Bachollet (accepted) Robert Guerra (accepted) Rapporteur No nominations Liaisons GNSO Liaison Alan Greenberg (accepted) ccNSO Liaison Jacqueline Morris (accepted) Adam Peake (declined) Vittorio Bertola (did not accept) SSAC Liaison Robert Guerra (accepted) IDNs Xue Hong (accepted) WHOIS No nominations Working Groups IDNs No nominations WHOIS No nominations Registrant/Registrar Relations No nominations IPv4 IPv6 Migration No nominations New GTLDs No nominations Special Adviser on Internet Governance Policy Wolfgang Kleinwachter, Jonathan Zittrain Sincerely Jacqueline A. Morris No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.15.5/1084 - Release Date: 10/21/2007 15:09

1 0

ICANN Meeting & Southern California Fires ..
by Robert Guerra Oct. 23, 2007

Oct. 23, 2007

Dear Colleagues: I've been hearing all sorts of terrible news on and about the wildfires in the LA and southern California area. With news today that schools and even some flights are being cancelled, might I suggest that ALAC recommend that ICANN publish an information alert so those coming to the city will know a. how to prepare for health issues that might arise due to the poor air quality, and b. change any plans they may have made to travel to and/ or visit the surrounding area. regards Robert --

2 1

Schedule Conflicts Matrix
by Nick Ashton-Hart Oct. 23, 2007

Oct. 23, 2007

Dear All: I asked a colleague to draw up a document showing the conflicts between the At-Large schedule and the rest of the ICANN LA schedule - it is attached. Hopefully this will help all of you planning on attending the meeting. Fly safe and I'll look forward to seeing you all in a few days! -- Regards, Nick Ashton-Hart Director, At-Large ICANN Main Tel: +33 (450) 40 46 88 USA Tel: +1 (202) 657-5460 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart(a)icann.org Win IM: ashtonhart(a)hotmail.com / AIM/iSight: nashtonhart(a)mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart

3 2

Preliminary Report of the new gTLDs ad hoc Working Group
by Danny Younger Oct. 23, 2007

Oct. 23, 2007

"We need input RIGHT NOW on the new gTLD document from the GNSO". This appeal to the ALAC community from Ms. Jacqueline A. Morris, Chair of the At-Large Advisory Committee, prompted the formation of the ad hoc Working Group on new gTLDs. A formal invitation to join the Working Group was provided by the Trinidad and Tobago Computer Society, and the formation of the Working Group was announced on the General Assembly discussion list, on the CPSR Governance list, on the ICANN Public Participation website, on each Regional At-Large Organization mailing list, and on the ALAC mailing list. The work plan of the Working Group: (1) Timeframe of ad-hoc WG: ends on Thursday 25 Oct. (2) Links to reference documents are provided (3) The 20 GNSO new gTLD recommendations are cited (4) WG members will each draft comments on whatever issues they might have with certain recommendations (5) Initial comments due by 22 October (6) First draft of Final Document (incorporating all comments) by 23 October (7) Final Document by 25 October (8) ALAC reviews WG effort in LA and provides Statement to accompany the Final Document for transmission to the ICANN board. Summary conclusions: The Working Group (as of the close of the initial comment period) received no contributions from any member of the ALAC nor any contributions from any of the ninety-four currently certified At-Large structures. Contributions were received from the following members of the community (all of whom spoke in their individual capacity): Wendy Seltzer Vittorio Bertola Jeff Williams Dan Krimm Danny Younger Links to the comments: Wendy Seltzer: http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… Vittorio Bertola: http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… Jeff Williams: http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… and http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… Dan Krimm: http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… Danny Younger: http://atlarge-lists.icann.org/pipermail/gnso-liaison_atlarge-lists.icann.o… In deference to the possibility of late submissions, the Working Group will allow another 24 hours for final submissions prior to submitting the First Draft of the Final Document. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Bulletin on the Internet Shutdown in Burma
by Robert Guerra Oct. 23, 2007

Oct. 23, 2007

Thought the following report of the recent internet shutdown in Burma might be of interest to the At-Large list. regards, Robert --- Robert Guerra <rguerra(a)privaterra.ca> Managing Director, Privaterra Tel +1 416 893 0377 Begin forwarded message: > From: Sally Walkerman <huridocs-tech(a)lists.hrea.org> > Date: October 23, 2007 5:42:16 AM EDT (CA) > Subject: Bulletin on the Internet Shutdown in Burma > > Friends, > > The OpenNet Initiative has compiled a bulletin on the recent > demonstrations in Burma and the Burmese government's shutdown of > the Internet there. ONI conducted a technical analysis of the > Internet's uptime, documenting a complete shutdown in Burma, > followed by intermittent periods of up-time throughout early > October, with an apparent return to full connection on October 13 > for one of the two ISPs and on October 16 for the other. This > bulletin presents these results and investigates the impact that > the use of communication technologies had on shaping these key events. > > The report, "Pulling the Plug: A Technical Review of the Internet > Shutdown in Burma," is available for download at: http:// > opennet.net/research/bulletins/013 . > > Best Wishes, > the ONI team > http://opennet.net >

1 0

Domain Name Front Running
by Robert Guerra Oct. 22, 2007

Oct. 22, 2007

SSAC Advisory on Domain Name Front Running has just been published. URL of complete report is below. Executive summary follows > > http://www.icann.org/committees/security/sac022.pdf > regards Robert -- Executive Summary This Advisory considers the opportunity for a party with some form of insider information to track an Internet user’s preference for registering a domain name and preemptively register that name. SSAC likens this activity to front running in stock and commodities markets and calls this behavior domain name front running. In the domain name industry, insider information would be information gathered from the monitoring of one or more attempts by an Internet user to check the availability of a domain name. When the domain name of interest for which an availability check is made is registered shortly after such a check, the individuals making the availability check may reasonably assume that the organization operating the web site or service they used to determine the availability of the name preemptively registered the name. Registrants have filed complaints with ICANN, registrars, and with Intellectual Property attorneys that suggest domain name front running incidents may have occurred. SSAC does not yet have any hard data to draw conclusions regarding the frequency (if any) of the occurrence of domain name front running. SSAC acknowledges that a perception exists within the community that monitoring or spying is taking place when would-be registrants check the availability of a domain name. Much of the information presented before SSAC regarding domain name front running is anecdotal and incomplete. The information SSAC has reviewed allows us to observe that some part of the community believes monitoring practices that result in preemptive registration of domain names have occurred and that such practices are not acceptable. SSAC is concerned that, whether real or perceived, preemptive registration portrays an unfavorable image of the domain name industry. This Advisory is therefore a preliminary study and is intended to put the issue before the community for discussion and to solicit well-documented incidents, if any can be obtained. In this Advisory, SSAC begins with a premise that checking the availability of a domain name can be a sensitive act which may disclose an interest in or a value ascribed to a domain name. SSAC suggests that any such domain name availability lookups should be performed with care. Our premise is that a registrant may ascribe a value to a domain name; that unintended or unauthorized disclosure, or disclosure of an availability check by a third party without notice may pose a security risk to the would- be registrant; and that availability checks may create opportunities for a party with access to availability check data to acquire a domain name at the expense of the party that performed an availability check, or to the benefit of the party that monitored the check. We attempt to assess these risks and suggest ways that information could be collected and used to engage in domain name front running activities. SSAC observes that there does not appear to be a strong set of standards and practices to conclude whether monitoring availability checks is an acceptable or unacceptable practice. We conclude this Advisory with a call for public comment; specifically, we invite registrants, registrars and other parties who have information regarding possible domain name front running incident to report that incident to the committee with as much information as possible to assist SSAC in studying this matter further.

2 1

FW: ccTLD IDN
by Jacqueline A. Morris Oct. 22, 2007

Oct. 22, 2007

Resending. From: Jacqueline A. Morris [mailto:jam@jacquelinemorris.com] Sent: Friday, October 19, 2007 20:55 To: alac(a)atlarge-lists.icann.org Cc: afri-discuss(a)atlarge-lists.icann.org; lac-discuss(a)atlarge-lists.icann.org; 'NA Discuss'; 'Discussion for At-Large Europe'; 'Asia-Pacific Discuss' Subject: [AFRI-Discuss] FW: ccTLD IDN Importance: High Dear At Large Please take notice of the communication from the ccNSO Chairman below. IDNs are a very important issue, especially to the individual internet user who uses other scripts. The At Large also has a working group on IDNs, chaired by Hong Xue, and you are encouraged to join. At Large IDN Policy work can be found at https://st.icann.org/alac/index.cgi?idn_policy_formation Thanks Jacqueline A. Morris ALAC Chair From: Chris Disspain [mailto:ceo@auda.org.au] Sent: Thursday, October 18, 2007 21:06 To: 'Jacqueline A. Morris' Cc: Boswinkel, Bart Subject: ccTLD IDN Importance: High Greetings Jacqueline, As you are aware, the ICANN Board resolved in San Juan on 29 June 2007, inter alia, that the ICANN community including the GNSO, ccNSO, GAC, and ALAC continue to work collaboratively, taking the technical limitations and requirements into consideration, to explore both an interim and an overall approach to IDN ccTLDs associated with the ISO 3166-1 two-letter codes and recommend a course of action to the Board in a timely manner. Since San Juan, the ccNSO Council has undertaken a considerable program of work to determine the best way to respond to the Boards request. Overall approach At a meeting on 12 September 2007, in accordance with ICANN bylaws, the ccNSO Council requested an Issue Report be prepared to establish whether the ccNSO should launch a PDP to develop the policy for the selection and delegation of IDN ccTLDs associated with the ISO 3166-1 two letter codes. In preparing the Issue Report the Issue Manager (Bart Boswinkel) should take into account the joint ccNSO GAC Issues Paper, the technical limitations and requirements, and any other matters that the Issues Manager considers to be of relevance. The Issues Report is the first step in the process of launching ccPDP and at large input will be sought throughout the preparation of the Report. Should a ccPDP be launched following the Issues Report, the ccNSO will seek to work closely with the at large community. Interim approach The ccNSO Council agreed that the first step in considering an interim approach should be to determine the extent of the pressing need claimed by some in the community. On 5 October 2007 I sent a letter to all ccTLD managers seeking answers to three questions. I anticipate that the responses to this letter will provide guidance as to whether an interim fast-track approach to enable the introduction of a limited number of IDN ccTLDs is a desirable and necessary step. As there is no pre-defined process to deal with such an interim approach, the ccNSO has released two discussion documents (attached) regarding a possible interim approach to IDN ccTLDs. The Designing an Interim Approach document considers how an interim approach could be managed and canvasses time lines. The Charter IDNC document is a first draft of what the charter for an interim approach committee might look like. The principle of having an interim approach, the results of my letter to ccTLD managers, and these two documents will be discussed by the ccNSO in Los Angeles. As you will appreciate there is some urgency to resolve the issue of an interim approach and this is why the ccNSO is working to a tight schedule. I would hope, in the event that an interim fast-track approach can be developed to enable the deployment of a limited number of IDN ccTLDs into the root, that the timing for this be closely aligned with the release of gTLD IDNs. I shall be grateful if you will forward this email to the ALAC, At Large and RALO lists for their information. Kind Regards, Chris Disspain Chair ccNSO Important Notice - This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately. Please consider the environment before printing this email.

1 0