August 2008 - At-Large - lists.icann.org

Re: [At-Large] [AfrICANN-discuss] Conférence ICANN : se protéger du phishing - Briefing session on Registrar Impersonation in Phishing Attacks
by Khaled KOUBAA Sept. 2, 2008

Sept. 2, 2008

It's really a nice initiative that ICANN is doing here. It's an interesting and very important subject. I recommend that ICANN repeat such capacity building actions for other issues related to our work. Khaled Anne-Rachel Inné a écrit : > Conférence ICANN : se protéger du phishing > > > Demain 26 août, l'ICANN organise une web conférence d'information sur > les cas d'usurpation d'identité des bureaux d'enregistrement lors > d'attaques de phishing. > > > De quoi s'agit-il ? Un pirate usurpe l'identité d'un registrar et > envoie à un client de ce dernier un faux message au sujet de ses noms > de domaine. Un avis d'expiration par exemple. > > C'est ni plus, ni moins du phishing. Le pirate a créé un site > frauduleux, similaire à celui du bureau d'enregistrement, pour inciter > le client à accéder à son compte de gestion du domaine concerné et à > révéler involontairement ses informations d'identification. > > Cette technique surtout connue dans le milieu bancaire sera expliquée > de manière préventive par Dave Piscitello de la division Sécurité et > Stabilité du Comité Consultatif de l'ICANN, lors d'une web conférence > (en français et en anglais) dont vous trouverez ici tous les détails. > > https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_att… > ENGLISH VERSION -- > > As announced at the last policy unit call on Monday, At-Large is going > to have a briefing session with Dave Piscitello this coming week on > Registrar Impersonation in Phishing Attacks and other stakeholder > communities are most welcome to join. > > The SSAC Advisory on Registrar Impersonation has recently been > translated into French and Spanish. They have not been uploaded to the > SSAC website yet but we have it linked to the meeting page for the > briefing session: > > https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_att… > > You can find the English, French and Spanish versions of the briefing > invitations attached to this email for your use. If you have questions > regarding this Briefing, please get in contact with somebody from the > At-Large staff. > https://st.icann.org/alac/index.cgi?registrar_impersonation_in_phishing_att… > _______________________________________________ > AfrICANN mailing list > AfrICANN(a)afrinic.net > https://lists.afrinic.net/mailman/listinfo.cgi/africann > >

15 22

Weekly posting summary for alac@atlarge-lists.icann.org
by Thomas Narten Aug. 29, 2008

Aug. 29, 2008

Total of 35 messages in the last 7 days. script run at: Fri Aug 29 00:53:03 EDT 2008 Messages | Bytes | Who --------+------+--------+----------+------------------------ 11.43% | 4 | 35.83% | 153321 | nick.ashton-hart at icann.org 14.29% | 5 | 10.21% | 43701 | khaled.koubaa at gmail.com 8.57% | 3 | 10.16% | 43467 | jefsey at jefsey.com 8.57% | 3 | 4.20% | 17973 | evan at telly.org 5.71% | 2 | 5.16% | 22093 | alan.greenberg at mcgill.ca 5.71% | 2 | 4.40% | 18809 | brenbe at consumer.org 5.71% | 2 | 3.07% | 13136 | ocl at gih.com 5.71% | 2 | 2.86% | 12238 | dannyyounger at yahoo.com 5.71% | 2 | 2.84% | 12165 | ajp at glocom.ac.jp 2.86% | 1 | 3.01% | 12879 | denise.michel at icann.org 2.86% | 1 | 2.80% | 11962 | rafik.dammak at gmail.com 2.86% | 1 | 2.50% | 10710 | patrick at vande-walle.eu 2.86% | 1 | 2.38% | 10185 | staff at atlarge.icann.org 2.86% | 1 | 2.12% | 9062 | carlosaguirre62 at hotmail.com 2.86% | 1 | 2.05% | 8763 | presidencia at internauta.org.ar 2.86% | 1 | 1.99% | 8525 | cheryl at hovtek.com.au 2.86% | 1 | 1.65% | 7064 | jam at jacquelinemorris.com 2.86% | 1 | 1.45% | 6185 | joly at punkcast.com 2.86% | 1 | 1.34% | 5716 | derek at aa419.org --------+------+--------+----------+------------------------ 100.00% | 35 |100.00% | 427954 | Total

1 0

Re: [At-Large] Re-engineering the Internet
by Olivier MJ Crepin-Leblond Aug. 29, 2008

Aug. 29, 2008

"JFC Morfin" <jefsey(a)jefsey.com> said: > We have committed to remain fully interoperable with IETF solutions > when they are clearly defined (we are not going to read 5500 RFCs, it > is not our hobby). Our basis is ISO 3166, which is the very structure > of the International network since 1978. It has documented the > national scripts and languages since its ISO-3166-1:2006 version. We > will base ourself on the Open Source LS640 Linguasphere series that > served as the basis for the current ISO 639-6 standard preparation of > an exhaustive listing of all the language names. 1. If you wish to be "fully interoperable with IETF solutions", may I recommend that if you're serious about your proposal, you read those "5500 RFCs". I am surprised how many people are trying to re-invent the wheel, starting from the guy at IETF that presented a protocol which basically did what AlohaNet did back in 1970 & Packet Radio henceforth. 2. I'm afraid that ISO 3166 has nothing to do with national scripts & languages. The official name is Codes for the representation of names of countries and their subdivisions. You're speaking solely of ISO 639. You're also missing ISO 15924 - Codes for Writing Systems, aka Codes for the representation of names of scripts. As for the rest of the post, I'm sorry but I can't understand it. O.

2 1

Re: [At-Large] Follow-up to conference call on travel support
by Alan Greenberg Aug. 28, 2008

Aug. 28, 2008

Dear Denise and Doug, As one of the more vocal people who have pointed out what we perceived as problems with the new travel funding approach, I would like to thank you for these adjustments. I look forward to working together to continue to refine both travel issues as well as the other inhibitors to At-Large participation. Although it may not always sound like it, we do understand that we are talking about large amounts of money here. I cannot speak on behalf of the ALAC or At-large, but I believe that we do understand that as At-Large matures and evolves, we will need to deliver benefits to ICANN justifying these expenditures. Regards, Alan At 28/08/2008 04:50 PM, Denise Michel wrote: >Dear At-Large Community Members: > >We would like to thank those of you who shared your views with us last week >on the conference call on the new community travel procedure, as well as >those who have shared their perspectives online. We know that every time you >engage with ICANN, you are doing so as a volunteer, which makes the >contribution all the more valuable. > >We understand there is concern that the ICANN Board, community and Staff >does not grasp the participation requirements of At-Large, and that At-Large >believes similar funding of travel for various communities is not an >equitable approach. Specifically, that ICANN travel funding should be based >on equalising the opportunity for participation across stakeholder groups in >proportion to their need. > >Our goal is support a travel funding approach that the ICANN community deems >appropriate to lower the barrier to participation, broaden the group of >ICANN participants and advance the "work" of ICANN. We acknowledge that >there are many differences of opinion on the meaning of "appropriate," and >are committed to continuing this dialogue and reviewing and if necessary >revising the travel procedures for FY 2010. > >We also are striving to ensure that At-Large (and all other stakeholder >participants in ICANN's work) has the necessary tools and resources to >support your work on ICANN issues. At-Large is a highly valued member of >the ICANN community, and we want to make sure your continued productivity is >supported. >It is for these reasons that ICANN has always dedicated considerable >resources to At-Large, including: > >1. A tripling of staff resources dedicated to At-Large in the past year; >2. Substantial year-on-year increases in funding dedicated to At-Large; >3. A significant amount of extra resources in this fiscal year and the >last for translation and interpretation driven in large part by At-Large's >needs; >4. Continuing development of your online participation mechanisms for >example, the website at http://atlarge.icann.org is the most technically >advanced in ICANN, the most multilingual, and will be the first site to >support direct contributions of content from the community and it is being >continually enhanced. > >We could go on about this subject, but we trust you are aware of these and >other efforts to increase your ability to participate as you are >experiencing the benefits of them directly. We continue to look for more >and better ways to ensure that the individual Internet user is represented >in decisions affecting them, and we value your ongoing guidance and >commitment to this endeavour, which is a fundamental part of the ICANN >model. > >Of course, other communities are essential too. Other communities have said >that they need support to attend ICANN meetings for the same reason that you >have stated because the meetings are an important part of the ICANN >process and some of their members cannot afford to attend. ICANN cannot >provide travel support for all communities at the level of funding all of >their members consider ideal. Budgetary realities require compromises to be >made. > >However, we would like to propose the following ideas as a way not just to >address the level of travel support for At-Large, but to go beyond that and >deal with some of the underlying issues you have raised. > >What we propose is the following: >* >1. We will work with the community throughout this fiscal year to review >the provisions of the travel procedure as they affect At-Large, especially >participation of the RALOs. It would useful to have an At-Large proposed >plan completed at the At-Large Summit in Mexico City to factor the >community's needs into the year-end review of the community travel procedure >and related FY2009-2010 budget process. *We understand your point that the >current travel procedure, if applied to At-Large in the next fiscal year, >does not take into sufficient account the needs of the RALOs to be able to >participate at face-to-face meetings. In particular, from the time spent >with you on an interpreted teleconference where a sizable portion of the >participants were speaking Spanish, we understand that At-Large is the >community which has the greatest needs for translation and interpretation >support at this time, and that until reliable remote participation that >facilitates multilingual participation is available for face-to-face >meetings, face-to-face attendance is more important than it would otherwise >be. We also understand your view that even English-speaking RALO >participants benefit from face-to-face interaction. Indeed, the purpose of >the travel procedure is to expand participation at face-to-face meetings >because we understand how valuable these opportunities are. Of course, the >whole ICANN community will get the opportunity to review the travel >procedure at the end of this fiscal year, along with ICANN's strategic and >operational plans and budget. These consultations offer important >opportunities for discussion and input on a range of issues that may relate >to RALOs (besides travel) including translation and interpretation, ICANN >regional meetings, etc. We encourage you to discuss your needs with the >other communities as well. > >2. *We will recommend that the eligibility of various communities for >participation in the Fellowship Program be reviewed in light of the new >community travel procedure. * It may be appropriate to update this program >after we evaluate the effect of the shared goals and support provided >through both the travel procedures and the Fellowship Program. Up to now, >this program has excluded At-Large from participating since At-Large travel >has been funded separately, and it has targeted members of the ccNSO and >Government Advisory Committee from eligible countries for priority support. >The ccNSO now receives some support under the travel procedures and GAC will >be considered for inclusion in the travel procedures for the next fiscal >year. It seems to us that the changes being made to travel for various >communities makes this step a sensible one. > >3. *GNSO Improvement initiatives offer opportunities to improve support >for At-Large, as well. * As part of the GNSO Improvements work recently >approved by the Board, a number of initiatives will be undertaken to: > >a. Review and improve the tools, processes, procedures, and GNSO >constituency support mechanisms; >b. Design and implement a global recruitment effort to increase >participation in all GNSO constituencies. > >This work will include a dialogue with constituencies about how to achieve >this and should take into account the different consultation and >collaboration needs of our global communities to advance policy-development. > > >Given the integral role At-Large plays in policy development, we would like >to explore ways to involve At-Large in this dialogue and planning, and >extend the results to At-Large, as appropriate. > >4. *To ensure that the progress made by the regional Secretariats in >creating structures and processes for working together and with the ALAC >continues, ICANN will provide travel support for the Secretariats for the >ICANN Cairo meeting and the final (June 2009) ICANN meeting for this fiscal >year. * The regional Secretariats will be funded on the same basis as they >were in the last fiscal year. We understand the value of having a periodic >opportunity for regional leaders and ALAC members to meet face-to-face, and >recognize that the whole community has benefited from the Secretariats' >attendance at ICANN meetings. > >We hope that you will look at these proposals and see in them a way not just >to deal with the issue of face-to-face attendance at ICANN meetings, but as >a way to go beyond that to advance At-Large involvement overall. > >We look forward to hearing from you, and working with you further. > >Regards, >Doug Brent, COO >Denise Michel, VP Policy

1 0

Follow-up to conference call on travel support
by Denise Michel Aug. 28, 2008

Aug. 28, 2008

Dear At-Large Community Members: We would like to thank those of you who shared your views with us last week on the conference call on the new community travel procedure, as well as those who have shared their perspectives online. We know that every time you engage with ICANN, you are doing so as a volunteer, which makes the contribution all the more valuable. We understand there is concern that the ICANN Board, community and Staff does not grasp the participation requirements of At-Large, and that At-Large believes similar funding of travel for various communities is not an equitable approach. Specifically, that ICANN travel funding should be based on equalising the opportunity for participation across stakeholder groups in proportion to their need. Our goal is support a travel funding approach that the ICANN community deems appropriate to lower the barrier to participation, broaden the group of ICANN participants and advance the "work" of ICANN. We acknowledge that there are many differences of opinion on the meaning of "appropriate," and are committed to continuing this dialogue and reviewing – and if necessary revising – the travel procedures for FY 2010. We also are striving to ensure that At-Large (and all other stakeholder participants in ICANN's work) has the necessary tools and resources to support your work on ICANN issues. At-Large is a highly valued member of the ICANN community, and we want to make sure your continued productivity is supported. It is for these reasons that ICANN has always dedicated considerable resources to At-Large, including: 1. A tripling of staff resources dedicated to At-Large in the past year; 2. Substantial year-on-year increases in funding dedicated to At-Large; 3. A significant amount of extra resources in this fiscal year and the last for translation and interpretation – driven in large part by At-Large's needs; 4. Continuing development of your online participation mechanisms – for example, the website at http://atlarge.icann.org is the most technically advanced in ICANN, the most multilingual, and will be the first site to support direct contributions of content from the community – and it is being continually enhanced. We could go on about this subject, but we trust you are aware of these and other efforts to increase your ability to participate as you are experiencing the benefits of them directly. We continue to look for more and better ways to ensure that the individual Internet user is represented in decisions affecting them, and we value your ongoing guidance and commitment to this endeavour, which is a fundamental part of the ICANN model. Of course, other communities are essential too. Other communities have said that they need support to attend ICANN meetings for the same reason that you have stated – because the meetings are an important part of the ICANN process and some of their members cannot afford to attend. ICANN cannot provide travel support for all communities at the level of funding all of their members consider ideal. Budgetary realities require compromises to be made. However, we would like to propose the following ideas as a way not just to address the level of travel support for At-Large, but to go beyond that and deal with some of the underlying issues you have raised. What we propose is the following: * 1. We will work with the community throughout this fiscal year to review the provisions of the travel procedure as they affect At-Large, especially participation of the RALOs. It would useful to have an At-Large proposed plan completed at the At-Large Summit in Mexico City to factor the community's needs into the year-end review of the community travel procedure and related FY2009-2010 budget process. *We understand your point that the current travel procedure, if applied to At-Large in the next fiscal year, does not take into sufficient account the needs of the RALOs to be able to participate at face-to-face meetings. In particular, from the time spent with you on an interpreted teleconference where a sizable portion of the participants were speaking Spanish, we understand that At-Large is the community which has the greatest needs for translation and interpretation support at this time, and that until reliable remote participation that facilitates multilingual participation is available for face-to-face meetings, face-to-face attendance is more important than it would otherwise be. We also understand your view that even English-speaking RALO participants benefit from face-to-face interaction. Indeed, the purpose of the travel procedure is to expand participation at face-to-face meetings because we understand how valuable these opportunities are. Of course, the whole ICANN community will get the opportunity to review the travel procedure at the end of this fiscal year, along with ICANN's strategic and operational plans and budget. These consultations offer important opportunities for discussion and input on a range of issues that may relate to RALOs (besides travel) including translation and interpretation, ICANN regional meetings, etc. We encourage you to discuss your needs with the other communities as well. 2. *We will recommend that the eligibility of various communities for participation in the Fellowship Program be reviewed in light of the new community travel procedure. * It may be appropriate to update this program after we evaluate the effect of the shared goals and support provided through both the travel procedures and the Fellowship Program. Up to now, this program has excluded At-Large from participating since At-Large travel has been funded separately, and it has targeted members of the ccNSO and Government Advisory Committee from eligible countries for priority support. The ccNSO now receives some support under the travel procedures and GAC will be considered for inclusion in the travel procedures for the next fiscal year. It seems to us that the changes being made to travel for various communities makes this step a sensible one. 3. *GNSO Improvement initiatives offer opportunities to improve support for At-Large, as well. * As part of the GNSO Improvements work recently approved by the Board, a number of initiatives will be undertaken to: a. Review and improve the tools, processes, procedures, and GNSO constituency support mechanisms; b. Design and implement a global recruitment effort to increase participation in all GNSO constituencies. This work will include a dialogue with constituencies about how to achieve this and should take into account the different consultation and collaboration needs of our global communities to advance policy-development. Given the integral role At-Large plays in policy development, we would like to explore ways to involve At-Large in this dialogue and planning, and extend the results to At-Large, as appropriate. 4. *To ensure that the progress made by the regional Secretariats in creating structures and processes for working together and with the ALAC continues, ICANN will provide travel support for the Secretariats for the ICANN Cairo meeting and the final (June 2009) ICANN meeting for this fiscal year. * The regional Secretariats will be funded on the same basis as they were in the last fiscal year. We understand the value of having a periodic opportunity for regional leaders and ALAC members to meet face-to-face, and recognize that the whole community has benefited from the Secretariats' attendance at ICANN meetings. We hope that you will look at these proposals and see in them a way not just to deal with the issue of face-to-face attendance at ICANN meetings, but as a way to go beyond that to advance At-Large involvement overall. We look forward to hearing from you, and working with you further. Regards, Doug Brent, COO Denise Michel, VP Policy

1 0

ALAC list archives
by Adam Peake Aug. 28, 2008

Aug. 28, 2008

Hi, The ALAC website <http://www.atlarge.icann.org/> has a menu section "Mailing Lists" and "See All Lists" <http://atlarge-lists.icann.org/mailman/listinfo>. But that list of list does not include the ALAC members list <http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org>, surely the most important as it's the one most of us can only read via the archives. Think it would be a good idea to correct this. Hope a link to the ALAC list archives will be included soon in the list of all lists. Thanks, Adam

2 1

FW: Report of the WHOIS Study Hypothesis Group attached
by Nick Ashton-Hart Aug. 27, 2008

Aug. 27, 2008

Dear Working Group Members and At-Large Community Members: Attached please find the report of the WHOIS Study Hypothesis Group to the GNSO Council as requested by the Council in its resolution of 26 June 2008. -- Regards, Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 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

1 0

More than half of the ALAC will be encouraged to resign
by Danny Younger Aug. 25, 2008

Aug. 25, 2008

Dear all, A few days ago ICANN Staff posted a document on the At-Large Announce list entitled, "Perfomance overview ALAC and Liaisons final.pdf" which details the abysmal degree of ALAC member participation. Under the terms of the ALAC Internal Rules of Procedure committee members are required to (1) cast a vote (including abstention) in at least 3/4 of ALS accreditations (2) Participate in at least 2/3 of the ALAC conference calls in any 6 month period (3) Attend at least one physical ICANN meeting in any 9 month period The rules (20.10) stipulate that in case of failure to meet the requirements, the Chair will privately encourage the member to resign, and if that doesn't happen within 14 days that other measures leading to a recall may be taken. As anticipated, more than half of the ALAC have not achieved their participatory requirements -- in total eight members plus one liaison are in formal default of their very minimal obligations. I'm looking forward to seeing these rules enforced by the ALAC Chair. It's long past time to get rid of the dead wood. P.S. The Staff document is attached to their letter on the Global ALAC election process -- you may read it here: http://atlarge-lists.icann.org/pipermail/alac-announce_atlarge-lists.icann.…

6 5

Comprehensive Study Shows IPv6 Shift Isn't Happening
by Danny Younger Aug. 25, 2008

Aug. 25, 2008

[excerpt] Despite predictions that the Internet's IPv4 protocol will run out of addresses sometime in 2011, little seems to have been done to transition to IPv6, the new protocol that will provide enough Internet addresses for the near future, according to an Arbor Networks study. The study found that the there were only about 600 Mbps of inter-domain IPv6 traffic between June 2007 and June of this year, or just 0.0026 percent of the amount of overall IPv4 traffic. The study also found that IPv6 traffic peaked twice between Nov. 4 and Dec. 25 of last year. Arbor's Scott Iekel-Johnson says the largest of these spikes happened when 1,168 people in attendance at a meeting of the Internet Engineering Task Force were asked to turn off IPv4 functionality on their network connections and routers and test to see which sites could be accessed. Iekel-Johnson says the fact that just under 1,200 people caused the largest spike in IPv6 traffic over the last 12 months "speaks volumes" about the lack of adoption of the new protocol. Synopsis courtesy of ACM TechNews http://technews.acm.org/#375298 Full article at http://www.extremetech.com/article2/0,2845,2328258,00.asp

1 0

An Illustrated Guide to the Kaminsky DNS Vulnerability
by Robert Guerra Aug. 16, 2008

Aug. 16, 2008

I came across the following article that I think could be of interest to At-Large. regards Robert --- An Illustrated Guide to the Kaminsky DNS Vulnerability http://www.unixwiz.net/techtips/iguide-kaminsky-dns-vuln.html The big security news of Summer 2008 has been Dan Kaminsky's discovery of a serious vulnerability in DNS. This vulnerability could allow an attacker to redirect network clients to alternate servers of his own choosing, presumably for ill ends. This all led to a mad dash to patch DNS servers worldwide, and though there have been many writeups of just how the vulnerability manifests itself, we felt the need for one in far more detail. Hence, one of our Illustrated Guides. This paper covers how DNS works: first at a high level, then by picking apart an individual packet exchange field by field. Next, we'll use this knowledge to see how weaknesses in common implementations can lead to cache poisoning. By fully understanding the issues at play, the reader may be better equipped to mitigate the risks in his or her own environment.

1 0