[[--Translated text (es -> en)--]] Subject: Re: = utf-8 q B3n_de_Servicios Ataque_de_Denegaci = C3 = = = utf-8 _a_root_servers_de_ICANN q =???????? From: asoto@ibero-americano.org Thanks Fátima and Alejandro. For those interested to see cyber attacks, he sent them this link. They can take several minutes to traverse, but is very interesting and gives us a very specific idea of \u200b\u200bthe number of attacks, not only suffers ICANN. CYBERTHREAT REAL-TIME MAP: https://cybermap.kaspersky.com/ Besides the tools to generate these attacks are very accessible and the tools to prevent or minimize these attacks, often not, also an entire security engineering, security management, scattered tools is not necessary. And a significant cost, no one wants to take it as an investment, and if they take it as an expense. In particular, it would be very interesting that all aboquemos us to the proposal of Alexander, could generate a map of our region. From there it would be very important what we do, may achieve changes in policies that protect the end user. Best regards Alberto Soto From: Alejandro Pisanty [mailto: apisanty@gmail.com] Posted on: Monday, December 14, 2015 4:32 a.m. To: Fatima Cambronero <fatimacambronero@gmail.com> CC: Alberto Soto <asoto@ibero-americano.org> ; LACRALO <lac-discuss-es@atlarge-lists.icann.org> Subject: Re: [lac-discuss-en] denial of services to ICANN root servers Colleagues, the issue of denial of service attempt to DNS servers should be of interest to general users especially their representatives, as understood also appreciate that Alberto and Fatima for their messages. The more detailed answer all calls ICANN network operators to use BCP 38, a document from the IETF that provides considerations and ways to filter certain types of traffic entering the networks with fake IP addresses ("spoofed"). The application of this practice is not sufficiently extensive. There are some tools to test whether the networks to which we are connected the applied but are not reliable when we're behind a NAT or DHCP as usual in domestic connections; connection is required from a fixed IP address. Many of you. Operating own or leased this feature servers. Can you identify for us to explore how to support users in general by first measuring compliance of this practice and then recommending that apply to the operators from our respective organizations or even from LACRALO as a whole? Alejandro Pisanty On Sun, Dec 13, 2015 at 24:44, Fatima Cambronero <fatimacambronero@gmail.com <mailto:fatimacambronero@gmail.com> > Wrote: FYI, ---------- Forwarded message ---------- From: Olivier MJ Crepin-Leblond <ocl@gih.com <mailto:ocl@gih.com> > Date: 12/12/2015 20:00 GMT-06: 00 Subject: [technical-issues] Fwd: [SOAC-InfoAlert] Statement and ICANN Root Server Blog To: technical issues <technical-issues@atlarge-lists.icann.org <mailto:technical-issues@atlarge-lists.icann.org> > Forwarded Message -------- -------- Subject: [SOAC-InfoAlert] Statement and ICANN Root Server Blog Date: Fri, 11 Dec 2015 19:54:39 \u200b\u200b+0000 From: David Olive <mailto:david.olive@icann.org><david.olive@icann.org> A: soac-infoalert@icann.org <mailto:soac-infoalert@icann.org><mailto:soac-infoalert@icann.org><soac-infoalert@icann.org> ICANN has published a blog Regarding last weekâ € ™ s Root Server attacks, Which Expands upon the statement released by the Root Server Operators <http://root-servers.org/news/events-of-20151130.txt> . You can read the blog here: https://www.icann.org/news/blog/root-server-operators-diversity-is-the-key Sent from my iPhone David A. Olive Senior Vice President Policy Development Support General Manager, ICANN Regional Headquarters â € "Istanbul Selenium Square Yeten Hakki Cad. No: 10 / CK 10 34349 <tel:10%2034349> Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 <tel:+90.212.999.6212> Mobile + 1.202.341.3611 <tel:+%201.%20202.341.3611> Mobile: +90.533.341.6550 <tel:+90.533.341.6550> Email: david.olive@icann.org <mailto:david.olive@icann.org> www.icann.org <http://www.icann.org/> _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/f7f513bef0.html --]]