nanog mailing list archives
Re: BGP Experiment
From: Filip Hruska <fhr () fhrnet eu>
Date: Wed, 23 Jan 2019 18:16:31 +0000
This experiment should be continued. It's the only way to get people to patch stuff. And if all it takes to break things is a single announcement, than that's something that should be definitely fixed. Blacklisting an ASN is not a solution, that's ignorance. Regards, Filip Hruska On 23 January 2019 18:19:09 CET, Italo Cunha <cunha () dcc ufmg br> wrote:
Ben, NANOG, We have canceled this experiment permanently. On Wed, Jan 23, 2019 at 12:00 PM Ben Cooper <ben () packet gg> wrote:Can you stop this? You caused again a massive prefix spike/flap, and as the internet isnotcentered around NA (shock horror!) a number of operators in Asia and Australia go effected by your “expirment” and had no idea what was happening or why. Get a sandbox like every other researcher, as of now we have blackholedand filtered your whole ASN, and have reccomended others do the same. On Wed, 23 Jan 2019 at 1:19 am, Italo Cunha <cunha () dcc ufmg br>wrote:NANOG, This is a reminder that this experiment will resume tomorrow (Wednesday, Jan. 23rd). We will announce 184.164.224.0/24 carrying a BGP attribute of type 0xff (reserved for development) between 14:00 and 14:15 GMT. On Tue, Dec 18, 2018 at 10:05 AM Italo Cunha <cunha () dcc ufmg br>wrote:NANOG, We would like to inform you of an experiment to evaluatealternativesfor speeding up adoption of BGP route origin validation (research paper with details [A]). Our plan is to announce prefix 184.164.224.0/24 with a valid standards-compliant unassigned BGP attribute from routers operatedbythe PEERING testbed [B, C]. The attribute will have flags 0xe0 (optional transitive [rfc4271, S4.3]), type 0xff (reserved for development), and size 0x20 (256bits). Our collaborators recently ran an equivalent experiment with no complaints or known issues [A], and so we do not anticipate any arising. Back in 2010, an experiment using unassigned attributesbyRIPE and Duke University caused disruption in Internet routing duetoa bug in Cisco routers [D, CVE-2010-3035]. Since then, this andothersimilar bugs have been patched [e.g., CVE-2013-6051], and new BGP attributes have been assigned (BGPsec-path) and adopted (large communities). We have successfully tested propagation of the announcements on Cisco IOS-based routers running versions12.2(33)SRAand 15.3(1)S, Quagga 0.99.23.1 and 1.1.1, as well as BIRD 1.4.5and1.6.3. We plan to announce 184.164.224.0/24 from 8 PEERING locations forapredefined period of 15 minutes starting 14:30 GMT, from Monday to Thursday, between the 7th and 22nd of January, 2019 (full scheduleandlocations [E]). We will stop the experiment immediately in caseanyissues arise. Although we do not expect the experiment to cause disruption, we welcome feedback on its safety and especially on how to make itsafer.We can be reached at disco-experiment () googlegroups com. Amir Herzberg, University of Connecticut Ethan Katz-Bassett, Columbia University Haya Shulman, Fraunhofer SIT Ítalo Cunha, Universidade Federal de Minas Gerais Michael Schapira, Hebrew University of Jerusalem Tomas Hlavacek, Fraunhofer SIT Yossi Gilad, MIT [A] https://conferences.sigcomm.org/hotnets/2018/program.html [B] http://peering.usc.edu [C] https://goo.gl/AFR1Cn [D]https://labs.ripe.net/Members/erik/ripe-ncc-and-duke-university-bgp-experiment[E] https://goo.gl/nJhmx1-- Ben Cooper Chief Executive Officer PacketGG - Multicast M(Telstra): 0410 411 301 M(Optus): 0434 336 743 E: ben () packet gg & ben () multicast net au W: https://packet.gg W: https://multicast.net.au -- You received this message because you are subscribed to the GoogleGroups"DISCO Experiment" group. To unsubscribe from this group and stop receiving emails from it,send anemail to disco-experiment+unsubscribe () googlegroups com. To post to this group, send email todisco-experiment () googlegroups com.To view this discussion on the web visithttps://groups.google.com/d/msgid/disco-experiment/CAPZQKs8aVT%3D7gJdGcoC-KOPDR0F4Ms33KAKKG5-4k96SVCSFEw%40mail.gmail.com<https://groups.google.com/d/msgid/disco-experiment/CAPZQKs8aVT%3D7gJdGcoC-KOPDR0F4Ms33KAKKG5-4k96SVCSFEw%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Current thread:
- Re: BGP Experiment, (continued)
- Re: BGP Experiment Italo Cunha (Jan 23)
- Re: BGP Experiment Job Snijders (Jan 23)
- Re: BGP Experiment Eric Kuhnke (Jan 23)
- RE: BGP Experiment Naslund, Steve (Jan 23)
- Re: BGP Experiment Aled Morris via NANOG (Jan 23)
- Re: BGP Experiment Töma Gavrichenkov (Jan 23)
- RE: BGP Experiment Naslund, Steve (Jan 23)
- RE: BGP Experiment Naslund, Steve (Jan 23)
- Re: BGP Experiment Töma Gavrichenkov (Jan 23)
- Re: BGP Experiment Nick Hilliard (Jan 23)
- Re: BGP Experiment Filip Hruska (Jan 23)
- RE: BGP Experiment Naslund, Steve (Jan 23)
- Re: BGP Experiment Owen DeLong (Jan 23)
- Re: BGP Experiment William Herrin (Jan 23)
- Re: BGP Experiment Christoffer Hansen (Jan 23)
- Re: BGP Experiment Nikolas Geyer (Jan 23)
- Re: BGP Experiment James Jun (Jan 23)
- Re: BGP Experiment Christoffer Hansen (Jan 23)
- Re: BGP Experiment Mark Tinka (Jan 23)
- RE: BGP Experiment adamv0025 (Jan 24)
- Re: BGP Experiment Brian Kantor (Jan 24)